DE112016005590T5 - Device, method and program - Google Patents

Abstract

[Task] Setting a communication path between servers in a more appropriate form at the MEC is provided.
[Solution] An apparatus includes: a detection unit configured to detect a connection request assigned to an access point name (APN) indicating a connection destination; and a control unit configured to set a carrier between a request source of the connection request and a server designated by the APN to which the connection request is assigned based on management information in which the APN is assigned to a gateway Connecting to the server designated by the APN.

Description

Technical area

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

State of the art

In recent years, a mobile edge computing (MEC) technology for performing data processing in a server (hereinafter also referred to as an edge server) has attracted attention that is physically provided at a position near a terminal such as a smart phone. For example, a standard of technology relating to MEC is examined in Non-Patent Literature 1 cited below, which is cited below.

In the MEC, an edge server is physically located at a location close to a terminal, thus reducing communication delay as compared to a general cloud server that is concentrated, and it is possible to use an application that has high real-time Performance must have. Further, in the MEC, the edge server in the vicinity of the terminal is caused to perform distributed processing of a function which has been processed on the terminal side so far, so that high-speed network / application processing can be realized regardless of the terminal's performance. The edge server may have various functions, such as a function serving as an application server and a function serving as a content server, and may provide various services to the terminal.

List of known fonts

Non-patent literature

Non-Patent Literature 1: ETSI, "Mobile-Edge Computing-Introductory Technical White Paper", September, 2014, [searched November 19, 2015], the Internet <https://portal.etsi.org/Portals/0/TBpages / MEC / Docs / Mobile edge_Computing _-_ Introductory_Technical_White_Paper_V1% 2018-09-14.pdf>

Disclosure of the invention

Technical problem

On the other hand, it is difficult to say that the study of non-patent literature 1 or the like has produced sufficient proposals for technology related to MEC, since such studies have recently begun. For example, a technique for appropriately setting a communication path between servers in a more appropriate form has not been sufficiently proposed in the MEC.

In this regard, the present disclosure provides a device, method, and program that can establish a communication path between servers in a more appropriate form at the MEC.

the solution of the problem

According to the present disclosure, there is provided an apparatus comprising: a detection unit configured to detect a connection request assigned to an access point name (APN) indicating a connection destination; and a control unit configured to set a carrier between a request source of the connection request and a server designated by the APN to which the connection request is assigned based on management information in which the APN is assigned to a gateway Connecting to the server designated by the APN.

In addition, according to the present disclosure, there is provided an apparatus comprising: a transmission unit configured to transmit a connection request assigned to an access point name (APN) indicating a connection destination to an external device; and a processing unit configured to communicate with a server designated by the APN via a carrier that is in communication with the server is determined, which is designated by the APN to which the connection request is assigned, based on management information in which the APN is assigned to a gateway that is passed when connecting to the one from the server.

In addition, according to the present disclosure, there is provided a method comprising: detecting a connection request assigned to an access point name (APN) indicating a connection destination; and determining, by a processor, a bearer between a request source of the connection request and a server designated by the APN to which the connection request is assigned, based on management information in which the APN is assigned to a gateway when establishing a connection request Connection with the server designated by the APN.

In addition, according to the present disclosure, there is provided a method comprising: transmitting a connection request assigned to an access point name (APN) indicating a connection destination to an external device; and executing, by a processor, communication with a server designated by the APN via a bearer established to connect to the server designated by the APN to which the connection request is assigned the basis of management information in which the APN is assigned to a gateway that is passed when connecting to the server.

In addition, according to the present disclosure, a program is provided that causes a computer to perform: detecting a connection request assigned to an access point name (APN) indicating a connection destination; and determining a bearer between a request source of the connection request and a server designated by the APN to which the connection request is assigned based on management information in which the APN is assigned to a gateway that is in connection with the one of the APN APN designated server is passed.

In addition, according to the present disclosure, a program is provided that causes a computer to: transmit a connection request assigned to an access point name (APN) indicating a connection destination to an external device; and performing communication with a server designated by the APN via a bearer set to make a connection with the server designated by the APN to which the connection request is assigned based on management information; where the APN is assigned to a gateway that will be passed when connecting to the server.

Advantageous effects of the invention

As described above, according to the present disclosure, there is provided an apparatus, a method, and a program that can set a communication path between servers in a more appropriate form at the MEC.

It is noted that the effects described above are not necessarily limiting. With or instead of the above effects, any of the effects described in this specification or other effects that can be obtained from this description can be achieved.

list of figures

• [ 1 ] 1 Fig. 10 is an explanatory view for describing an MEC overview.
• [ 2 ] 2 Fig. 10 is an explanatory view for describing a platform of an MEC server.
• [ 3 ] 3 Fig. 10 is an explanatory diagram for describing an example of a basic architecture of an EPC.
• [ 4 ] 4 FIG. 10 is an explanatory diagram for describing an example of a configuration of a carrier. FIG.
• [ 5 ] 5 FIG. 10 is an explanatory diagram for describing an example of a configuration of a carrier in a case where a wireless relay station is installed. FIG.
• [ 6 ] 6 illustrates an example of a protocol stack that communicates with an eNB, a DeNB, and an RN.
• [ 7 ] 7 FIG. 10 is a sequence diagram illustrating an example of a flow of an attaching operation of the UE executed in the EPS. FIG.
• [ 8th ] 8th Fig. 10 is an explanatory diagram for describing an example of a network configuration of LTE in which an MEC server is introduced.
• [ 9 ] 9 Fig. 12 is an explanatory diagram for describing another example of a network configuration of LTE in which an MEC server is introduced.
• [ 10 ] 10 FIG. 10 is an explanatory diagram for describing an example of a schematic configuration of a system 1 according to an embodiment of the present disclosure.
• [ 11 ] 11 FIG. 10 is a block diagram illustrating an example of a configuration of an MEC server 300 according to the embodiment.
• [ 12 ] 12 FIG. 12 is a block diagram illustrating an example of a configuration of an application server 60 according to the embodiment.
• [ 13 ] 13 FIG. 10 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.
• [ 14 ] 14 Figure 12 is a sequence diagram illustrating an example of a flow of a process associated with the release of a default carrier.
• [ 15 ] 15 Figure 12 is a sequence diagram illustrating an example of a flow of a process associated with the release of a default carrier.
• [ 16 ] 16 Figure 12 is a sequence diagram illustrating an example of a flow of a process associated with the release of a default carrier.
• [ 17 ] 17 Figure 12 is a sequence diagram illustrating an example of a flow of a process associated with the release of a default carrier.
• [ 18 ] 18 FIG. 10 is an explanatory diagram for describing an example of a configuration for implementing connectivity between MEC servers by a DPI. FIG.
• [ 19 ] 19 Fig. 10 is an explanatory diagram for describing an example of an architecture of an MEC server.
• [ 20 ] 20 Fig. 10 is an explanatory diagram for describing an example of a configuration of a system into which an MEC server is inserted.
• [ 21 ] 21 FIG. 10 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.
• [ 22 ] 22 illustrates an example of information recorded in a GW allocation list.
• [ 23 ] 23 illustrates another example of information recorded in a GW allocation list.
• [ 24 ] 24 Fig. 10 is an explanatory diagram for describing an outline of a carrier set between MEC servers.
• [ 25 ] 25 Figure 13 is a diagram illustrating an example of a protocol stack of communication between MEC servers.
• [ 26 ] 26 Figure 13 is a diagram illustrating an example of a protocol stack of communication between MEC servers.
• [ 27 ] 27 FIG. 12 is a diagram illustrating an example of a configuration of an MEC carrier.
• [ 28 ] 28 FIG. 12 is a diagram illustrating an example of a configuration of an MEC carrier.
• [ 29 ] 29 FIG. 12 is a diagram illustrating an example of a configuration of an MEC carrier.
• [ 30A ] 30A FIG. 12 is a diagram illustrating an example of a configuration of an MEC carrier.
• [ 30B ] 30B FIG. 12 is a diagram illustrating an example of a configuration of an MEC carrier.
• [ 30C ] 30C FIG. 12 is a diagram illustrating an example of a configuration of an MEC carrier.
• [ 31 ] 31 FIG. 10 is an explanatory diagram for describing an example of a carrier configuration in a system 1 according to the embodiment. FIG.
• [ 32 ] 32 FIG. 12 is a sequence diagram illustrating an example of a flow of a carrier setting process executed in the system according to a first example of the embodiment. FIG.
• [ 33 ] 33 FIG. 10 is a sequence diagram illustrating an example of a flow of a carrier setting process executed in the system according to a second example of the embodiment. FIG.
• [ 34 ] 34 FIG. 10 is a sequence diagram illustrating an example of a flow of a carrier setting process executed in the system according to a third example of the embodiment. FIG.
• [ 35 ] 35 Figure 13 is a diagram illustrating an example of a protocol stack of communication between MEC servers.
• [ 36 ] 36 Figure 13 is a diagram illustrating an example of a protocol stack of communication between MEC servers.
• [ 37 ] 37 Figure 13 is a diagram illustrating an example of a protocol stack of communication between MEC servers.
• [ 38 ] 38 Figure 13 is a diagram illustrating an example of a protocol stack of communication between MEC servers.
• [ 39 ] 39 Figure 13 is a diagram illustrating an example of a protocol stack of communication between MEC servers.
• [ 40 ] 40 Figure 13 is a diagram illustrating an example of a protocol stack of communication between MEC servers.
• [ 41 ] 41 Fig. 10 is an explanatory diagram for describing an outline of a fourth example of the embodiment.
• [ 42 ] 42 Fig. 10 is an explanatory diagram for describing an outline of a fourth example of the embodiment.
• [ 43 ] 43 Fig. 10 is an explanatory diagram for describing an example of an interface implemented by the application of a SCEF.
• [ 44 ] 44 Fig. 10 is an explanatory diagram for describing another example of an interface implemented by the application of a SCEF.
• [ 45 ] 45 Fig. 10 is an explanatory diagram for describing another example of an interface implemented by the application of a SCEF.
• [ 46 ] 46 Fig. 10 is an explanatory diagram for describing another example of an interface implemented by the application of a SCEF.
• [ 47 ] 47 Fig. 10 is an explanatory diagram for describing another example of an interface implemented by the application of a SCEF.
• [ 48 ] 48 illustrates an example of an architecture for applying an ADC to an MEC server.
• [ 49 ] 49 illustrates an example of an architecture for applying an ADC to an MEC server.
• [ 50A ] 50A Figure 12 is a diagram illustrating an example of a protocol stack in a communication between MMEs.
• [ 50B ] 50B is a diagram illustrating an example of an EPC network architecture.
• [ 51 ] 51 Fig. 10 is a block diagram illustrating an example of a schematic configuration of a server.
• [ 52 ] 52 FIG. 12 is a block diagram illustrating a first example of a schematic configuration of an eNB. FIG.
• [ 53 ] 53 FIG. 12 is a block diagram illustrating a second example of a schematic configuration of the eNB. FIG.
• [ 54 ] 54 Fig. 10 is a block diagram illustrating an example of a schematic configuration of a smartphone.
• [ 55 ] 55 FIG. 10 is a block diagram illustrating an example of a schematic configuration of a car navigation device. FIG.

Embodiment (s) of the invention

Hereinafter, a preferred embodiment (s) of the present disclosure will be described in detail with reference to the attached drawings. It should be noted that in this specification and the appended drawings, structural elements having substantially the same function and structure are denoted by the same reference numerals, and a repeated explanation of these structural elements will be omitted.

1. 1. Einleitung
   • 1,1. MEC
   • 1,2. Träger
   • 1,3. Technisches Problem
2. 2. Konfigurationsbeispiel
   • 2,1. Konfigurationsbeispiel des Systems
   • 2,2. Konfigurationsbeispiel des MEC-Servers
   • 2,3. Konfigurationsbeispiel des Anwendungsservers
3. 3. Erste Ausführungsform
   • 3,1. Technische Merkmale
   • 3,2. Auswertung
4. 4. Zweite Ausführungsform
   • 4,1. Technische Merkmale
   • 4,2. Erstes Beispiel
   • 4,3. Zweites Beispiel
   • 4,4. Drittes Beispiel
   • 4,5. Viertes Beispiel
   • 4,6. Fünftes Beispiel
   • 4,7. Auswertung
5. 5. Anwendungsbeispiele
   • 5,1. Anwendungsbeispiel in Bezug auf Server
   • 5,2. Anwendungsbeispiel in Bezug auf Basisstation
   • 5,3. Anwendungsbeispiel in Bezug auf Endgerät
6. 6. Schlussfolgerung

Furthermore, the description will take place in the following order.

1. 1 Introduction
   • 1.1. MEC
   • 1.2. carrier
   • 1.3. Technical problem
2. 2. Configuration example
   • 2.1. Configuration example of the system
   • 2.2. Configuration example of the MEC server
   • 2.3. Configuration example of the application server
3. 3. First embodiment
   • 3.1. technical features
   • 3.2. evaluation
4. 4. Second embodiment
   • 4.1. technical features
   • 4.2. First example
   • 4.3. Second example
   • 4.4. Third example
   • 4.5. Fourth example
   • 4.6. Fifth example
   • 4.7. evaluation
5. 5. Application examples
   • 5.1. Example of application in relation to servers
   • 5.2. Example of application in relation to base station
   • 5.3. Application example relating to terminal
6. 6. Conclusion

<< Introduction >>

<MEC>

overview

First, an overview of the MEC with reference to 1 described.

1 Fig. 10 is an explanatory view for describing an MEC overview. An upper part of 1 Fig. 12 illustrates an example of a communication path to enable a user equipment (UE) to access an application and content in a current (MEC is not established) mobile communication represented by long-term development (LTE). Further, a lower part thereof illustrates an example of a communication path to allow the UE to access an application and contents in a case where MEC is introduced.

As in the upper part of 1 In the current mobile communication, an application and content are arranged in IP networks that exist outside of an evolved packet core (EPC) (a side remote from the UE). Thus, to execute an application or capture content, the UE performs communication over an entire relay network (eg, backbone network), the EPC, a backhaul connection, a base station, and an access connection that exist on a path to a data center , Therefore, enormous network costs and delays occur.

As in the lower part of 1 As shown, the MEC holds an application and content within the EPC (a page near the UE). For example, in the example that works in 1 an MEC server (ie, an edge server) provided integrally with a base station as an application server and a content server. Thus, the UE only has to perform a substantial (strictly speaking, since an exchange can take place with a server other than the EPC) communication within the EPC to execute an application or to capture content. Therefore, by introducing MEC, it is possible not only to perform communication with extremely short delay, but also to reduce the traffic that is not the access connection (for example, the backhaul connection, the EPC, and the relay network). Further, reducing the delay of the communication and reducing the traffic that is not the access connection may also help to improve the throughput and reduce the power consumption at the UE and at the network side. As described above, the introduction of MEC can have several advantages for a user, a network provider, and a service provider. In the MEC, data is subjected to distributed processing on a page closer to a local page (ie, a page near the UE), and therefore it is expected that the MEC will be particularly applied to an application rooted in an area and a distributed computer ,

It should be made clear that 1 an example in which the MEC server is provided integral with the base station. However, the present technology is not limited to such an example. The MEC server may be provided as a device other than the base station, or may be physically separate from the base station.

platform

Next, a platform of an MEC server will be described with reference to FIG 2 described.

2 Fig. 4 is an explanatory view for describing the platform of the MEC server. A 3GPP radio network element that is the lowest constituent element is a base station equipment such as an antenna and an amplifier. A hosting infrastructure thereon consists of hardware resources such as server equipment and a virtualization layer constituted by software that virtualizes these hardware resources, and can provide general virtual server technology. On this virtual an application platform is operated. Further, a physical server running hardware resources such as server equipment corresponds to an example of a "physical server".

A virtualization manager executes an administration, such as a virtual machine (VM) generation and deletion, which serves as an environment in which a highest application (MEC App) operates. Each application may be executed by different companies, and therefore, the virtualization manager must consider the security, the allocation of a resource to be allocated, and the like, but it is possible to adopt a general cloud infrastructure technology.

An application platform service is a collection of common services that are characteristic of MEC. A traffic offload function performs a switching control such as routing between a case where a request from the UE is processed by an application on the MEC server and a case where the request is processed by an application on the Internet (Master application on a data server). In a case where each application on the MEC server requires wireless status information, such as an intensity of a radio wave between a base station corresponding to (for example, integrally provided with) the MEC server and the UE, radio network information services acquire information from a lower one wireless network and provide the information of the application. Communication services provide a path to allow any application on the MEC server to communicate with the UE or an application on the Internet. In a case where a request for generation or operation of each application is received on the MEC server, a service register authenticates whether the application is legitimate or not, registers the application and responds to a request from other entities.

Each VM or application in each VM operates on the application platform described above and provides the UE with different types of services instead of using it on the Internet or in cooperation with the application.

The MEC server is expected to be installed in a large number of base stations, and therefore it is also necessary to study a structure for managing and linking a large number of MEC servers. A hosting infrastructure management system, an application platform management system and an application management system manage entities on the MEC server and associate the entities.

Tendency of standardization

In Europe, Industry Specification Groups (ISGs) have been set up in the ETSI and MEC standardization activities started in October 2014. The standardization work is currently being carried out with a view to the preparation of a first specification by the end of 2016. In particular, the standardization of the application programming interface (API) for implementing MEC has been carried out mainly with the aid of ETSI Network Function Virtualization (NFV) and 3GPP.

<Carrier>

Next, a carrier with reference to 3 to 7 described. First, an architecture of a core network will be described with reference to FIG 3 described.

3 Fig. 10 is an explanatory diagram for describing an example of a basic architecture of the EPC. An UE is a terminal and is also called a "user". An evolved NodeB (eNB) is a base station. A packet data network (PDN) gateway (P-GW) is a connection point between the EPC and a PDN (for example, a concept including the Internet, an external IP network, a cloud, or the like) and exchanges a user packet with the PDN out. A serving gateway (S-GW) is a connection point between a developed universal terrestrial radio access network (E-UTRAN) and the EPC and provides a routing function and a transfer function for the user packet. An online accounting system (OCS) is a functional entity that performs account control in real time. An offline accounting system (OFCS) is a functional entity that performs accounting control offline. A rules and billing rules function (PCRF) is a functional entity that performs rules and billing control. A Mobility Management Entity (MME) is a functional entity that manages mobility. A Home Subscriber Server (HSS) is a functional entity that manages subscriber information. In 3 Solid lines indicate a user plane and dashed lines indicate a control plane.

The UE is connected to the eNB and connected to the EPC via the S-GW based on the control of the MME and the HSS. Further, the UE is connected to the Internet (ie, the PDN) via the P-GW and connected to a content server or the like on the Internet based on a request of an application on the UE. The connection between the UE and the PDN is performed according to a determination of a bearer. The bearer specifies a number of physical or logical paths for transmitting user data. A configuration example of the carrier in an end-to-end service from the UE to a device on the Internet is in FIG 4 shown.

4 FIG. 10 is an explanatory diagram for describing an example of a configuration of a carrier. FIG. As in 4 As shown, a carrier defined between a UE and an eNB is also referred to as a radio carrier. The bearer established between the eNB and the UE is also referred to as an S1 bearer. Further, a bearer established between the UE and the S-GW is also commonly referred to as an E-UTRAN Radio Access Bearer (E-RAB). Further, the carrier set between the S-GW and the P-GW is also called S5 / S8 carrier. Further, the carrier established between the UE and the P-GW is also commonly referred to as an Evolved Packet System (EPS) carrier. Further, the carrier set between the P-GW and the device on the Internet is also called an external carrier.

Further, in an LTE-Advanced (LTE-A) standard, there has also been proposed a configuration in which a relay relay (RN) station is relayed, which forwards wireless transmission between the UE and the eNB. 5 FIG. 10 is an explanatory diagram for describing an example of a configuration of a carrier in a case where the wireless relay station is installed. FIG. Further, in the following description, particularly in the case of an explicit indication of an eNB with which an RN is connected between eNBs, it is also referred to as "donor eNodeB (DeNB)". As in 5 As shown, a carrier defined between the UE and the DeNB is also referred to as an S1 / Un carrier.

6 further illustrates an example of a protocol stack that communicates with an eNB, a DeNB, and an RN. As shown in FIG. Shown in Figures 5 and 6, a carrier between the DeNB and the DeNB and a carrier between the RN and the DeNB are equivalent to a carrier used for an X2 interface assigned in a one-to-one fashion becomes.

Here, an EPS support of interest in the present technology will be described in further detail. For example, the EPS bearer is defined between a UE and one or more P-GWs designated by an access point name (APN). As EPS carriers that can be established between the UE and an APN, there is a standard carrier and one or more adjustable individual carriers (dedicated carriers). Further, a service data flow (SDF) is exchanged in each carrier. Table 1 and Table 2 below show an overview of carrier QoS.

[Table 1] Classification LTE QoS Dedicated Bearer Default bearer Non-GBR GBR Non GBR Relevant conccpt QCI 5-9 QCI 1-4 QCI 5-9 APN-AMBR GBR APN-AMBR UE-AMBR MBR UE-AMBR TFT TFT APN ARP ARP IP Address L-EBI L-EBI ARP

[Table 2] QCI Bearer Type Priority Packet Delay Budget Packet Error Loss Example services 1 GBR 2 100ms 10 ^-2 VoIP call 2 4 150ms 10 ^-3 Video call 3 3 50ms Online Gaming (Real Time) 4 5 300ms 10 ^-6 Streaming video 5 non-GBR 1 100ms IMS signaling 6 6 300ms Video, TCP-based services eg email, chat, ftp etc. 7 7 100ms 10 ^-3 Voice, Video, Interactive gaming 8th 8th 300ms 10 ^-6 Video, TCP-based services eg email, chat, ftp etc. 9 9 300ms

7 FIG. 10 is a sequence diagram illustrating an example of a flow of an attaching operation of the UE executed in the EPS. FIG.

First, the UE transmits an attach request signal designating an APN for the MME (step S11). Here, the designated APN is also referred to as "standard APN". Then, various kinds of 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 obtained from the HSS and acquires and manages contract information needed for a bearer designation from the HSS. Then, the MME transmits a location registration request (location request) signal to the HSS (step S13), and receives a location registration reply (location request response) signal from the HSS (step S14).

Then, the MME selects an S-GW and a P-GW of a carrier designation destination based on the APN notified by the UE, and transmits a carrier designation request (carrier request) signal to the selected S-GW (step S15). At that time, the MME will execute a Fully Qualified Domain Name (FQDN) APN domain name, for example, by a Domain Name System (DNS) resolver, and select a P-GW that is connectable to the PDN with which it is required to connect. Further, the MME selects the S-GW based on a strategy such as a collocation basis based on a tracking area identification (TAI) described in a cell ID detected by the eNB.

Then, the S-GW carries out carrier establishment processes for the P-GW designated in the carrier designation request signal (step S16). In the host setup process, the P-GW acquires accounting information to be applied with the assistance of the PCRF and further implements a connection process with the PDN. When the setting of the carrier with the P-GW is completed, the S-GW transmits a carrier designation request response (carrier request response) signal to the MME (step S17).

The MME transmits a Radio Bearer Request Request (Radio Bearer) signal having information received from the S-GW, i. H. Information indicating that the attach request is accepted is sent to the eNB (step S18). The eNB sends a radio bearer designation request (radio bearer) signal having information indicating that the attachment request is accepted to the UE and sets up the radio bearer with the UE (step S19). After receiving the radio bearer set response (radio bearer response) signal from the UE (step S20), the eNB transmits a radio bearer set response (radio bearer response) signal to the MME (step S21). Then, the UE transmits an attach completion signal to the MME. The corresponding carrier is the standard carrier.

Accordingly, uplink user plane traffic data may be transmitted via the S-GW and the P-GW from the UE to the PDN (eg, to an application server on the PDN). Further, it is possible to transmit downlink user plane traffic data from the PDN via the S-GW and the P-GW to the PDN.

When the carrier update request (carrier update request) signal is transmitted from the MME to the S-GW (step S23), the S-GW performs a carrier update process (step S24) and transmits a carrier update request response signal (carrier update request response) to the MME (step S25 ).

Then the process ends. Further, this process is described in detail in "3GPP, 3GPP TS24.301 V8.1.0, 'March 2009, [Access on Nov. 19, 2015], Internet <http://www.arib.or.jp/IMT-2000/ V730Jul09 / 5_Appendix / Rel8 / 24 / 24301-810.pdf> ".

<Technical problem>

Next, a technical problem according to an embodiment of the present disclosure will be described.

8th Fig. 10 is an explanatory diagram for describing an example of a network configuration of LTE in which an MEC server is introduced. As in 8th As shown, the network configuration of LTE includes an E-UTRAN serving as a wireless network and an EPC serving as a core network. Such a configuration may also be referred to as "EPS". The UE accesses the Internet via the P-GW designated by the APN. In a case where the UE communicates with the content server on the Internet, user data typically traverses the eNB, the S-GW, and the P-GW.

Similarly, in the in 8th For example, even in a case where the UE accesses the MEC server, the UE accesses the MEC server via the P-GW designated by the APN. In other words, in a case where the UE communicates with the MEC server, user data typically traverses the eNB, the S-GW, and the P-GW.

An operation for setting the communication path will be described in more detail. First, the UE establishes a connection with the MEC server, which may be designated by performing the attach operation from a Uniform Resource Identifier (URI) or an IP address. Here, the user-level traffic is first transmitted from the UE to the P-GW. The P-GW removes a header (for example, a General Packet Radio Service (GPRS) - Tunneling Protocol (GTP) header) used in the EPC by the user packet. Then, the P-GW transmits the user data to a destination address specified by a URI or an IP address designated by the UE.

If a URI here is a URI and tries to establish a connection, the UE normally activates the DNS resolver, captures the IP address displayed by the URI, and then tries to connect. Specifically, after establishing a connection with the P-GW, the UE detects an IP address from a DNS server in the PDN or a DNS server in the EPC. Furthermore, the MME can take over a DNS resolver function in the EPC. Since the detected IP address of the MEC server is an address in the EPC, a connection is established via the EPC from the P-GW to the MEC server.

As described above, even in a case where MEC is introduced, according to a current mobile communication network mechanism, the redundant communication path is set, and it is difficult to obtain an expected effect.

On the other hand, as expected, a response is implemented with a lesser delay by installing the MEC server at a location closer to a user of an application (ie, the UE) such as the eNB, recognizing a radio wave condition or use state of radio access, and a so-called QoS is provided. For example 9 an explanatory diagram for describing another example of a network configuration of LTE in which the MEC server is introduced, and an example of a method for implementing connectivity from the UE to the MEC server, which is arranged in the eNB. In other words, as the method of implementing the connectivity from the UE to the MEC server located in the eNB, a switch (SW) function such as a virtualization technique or a packet switching technique may be used.

On the other hand, in a case where an application on the MEC server is used by the UE, a case in which the MEC server is used in cooperation with the MEC server located at another location becomes an application server in FIG Internet or the like considered. As a specific example, in an example that is in 9 a case is contemplated in which an MEC server identified by the reference MEC- 1 , communicates with an application server operating on the Internet.

On the other hand, currently in 3GPP policies, a method for establishing a communication path between MEC servers that are not entities of the core wireless network has not been clearly specified. Specifically, for example, in the guidelines specified by 3GPP, no interface has been specified for establishing a communication path between MEC servers via devices such as an eNB, RN, or S-GW. In this regard, the present disclosure proposes a mechanism for establishing the communication path between the MEC servers in a more appropriate form.

Further, in this specification, the present technology is described on the assumption that the EPS is used in LTE as the network architecture. However, the present technology can also be applied to a universal mobile telecommunications system (UMTS) in 3G or can be applied to any network architecture.

<< Configuration example >>

<Configuration example of the system>

First, an example of a schematic configuration of a system 1 according to an embodiment of the present disclosure with reference to 10 described. 10 Fig. 12 is an explanatory diagram showing an example of a schematic configuration of the system 1 in accordance with an embodiment of the present disclosure. As in 10 shown, the system instructs 1 a wireless communication device 100 , a terminal 200 and an MEC server 300 on. Here is the terminal 200 also referred to as a "user". The user may also be referred to as a "UE". In other words, the above-mentioned UE 200 the terminal 200 match that in 10 is shown. The wireless communication device 100C is also referred to as a "UE relay". Here, the UE may be a UE defined in LTE or LTE-Advanced (LTE-A), the UE relay may be a Prose UE to Network Relay explained in 3GPP or, more generally, a communication device.

( 1 ) Wireless communication device 100

The wireless communication device 100 is a device that provides a wireless communication service to subordinate devices. For example, a wireless communication device 100A is a base station of a cellular system (or a mobile communication system). The base station 100A performs wireless communication with a device (e.g., a terminal 200A) located within a cell 10A of the base station 100A. For example, the base station 100A transmits a downlink signal to the terminal 200A and receives an uplink signal from the terminal 200A.

The base station 100A is logically connected to other base stations, for example via an X2 interface, and can perform the transmission and reception of control information and the like. Further, the base station 100A is logical with a core network 40 For example, connected via an S1 interface and can perform the transmission and reception of control information and the like. Furthermore, the communication between these devices may be physically transmitted by different devices.

Here is the wireless communication device 100A used in 10 a microcell base station and a cell 10 is a microcell. On the other hand, the wireless communication devices 100B and 100C are master devices that operate the small cells 10B and 10C. As an example, the master device 100B is a small cell base station that is permanently installed. The small cell base station 100B establishes a wireless backhaul connection with the microcell base station 100A and establishes an access connection with one or more terminals (e.g., the terminal 200B) in a small cell 10B. It should be understood that the wireless communication device 100B may also be a relay node defined in 3GPP. The master device 100C is a dynamic access point (AP). The dynamic one AP 100C is a mobile device that dynamically operates the small cell 10C. The dynamic one AP 100C establishes a wireless backhaul connection with the microcell base station 100A and establishes an access connection with one or more terminals (e.g., the terminal 200C) in the small cell 10C. The dynamic one AP 100C For example, it may be a terminal equipped with hardware or software that can act as a base station or a wireless access point. In this case, the small cell 10C is a localized network (dynamic cell).

The cell 10 can operate according to any wireless communication scheme, such as LTE, LTE-A, GSM (R), UMTS, W-CDMA, CDMA 200 , WiMAX, WiMAX 2 or IEEE 802.16.

Further, the small cell may be a concept including various types of cells arranged to overlap or not overlap with the micro cell and smaller than the micro cell (for example, a femto cell, a nanocell, a picocell, a microcell or the like). In one example, the small cell is powered by a dedicated base station. In another example, the small cell is operated as a terminal acting as a master device which temporarily acts as a small cell base station. A so-called relay node can also be considered as a form of small cell base station. The wireless communication device, which functions as a master station of the relay node, is also referred to as a "donor base station". The donor base station may refer to a donor eNodeB (DeNB) in LTE or more generally refer to a master station of a relay node.

Terminal 200

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

Application Server 60

An application server 60 is a device that provides a service to the user. The application server 60 is with a packet data network (PDN) 50 connected. On the other hand, the base station 100 with the core network 40 connected. The core network 40 is via a gateway device (the P-GW in 7 ) with the PDN 50 connected. Therefore, the wireless communication device 100 that from the application server 60 provided service to the MEC server 300 and the user via the packet data network 50 , the core network 40 and the wireless communication path.

MEC server 300

The MEC server 300 is a service providing device that provides the user with a service (an application, content or the like). The MEC server 300 can in the wireless communication device 100 be provided. In this case, the wireless communication device 100 provides the user with the service provided by the MEC server 300 via the wireless communication path. The MEC server 300 may be implemented as a logical function entity or may be integral with the wireless communication device 100 or the like, as in 10 shown.

For example, the base station 100A provides the service provided by the MEC server 300A to the terminal 200A that is connected to the microcell 10 connected is. Further, the base station 100A provides the service provided by the MEC server 300A to the terminal 200B which is 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 200B connected to the small cell 10B. Similarly, the master device 100C provides the service provided by the MEC server 300C to the terminal 200C connected to the small cell 10C.

complement

The schematic configuration of the system 1 has been described above, however, the present technology is not on the in 10 illustrated example limited. For example, as a configuration of the system 1 a configuration that does not include a master device, a small-cell enhancement (SCE), a heterogeneous network (HetNet), a machine-communication-type network (MTC), or the like may be used.

<Configuration example of the MEC server>

Next is an example of a configuration of the MEC server 300 according to an embodiment of the present disclosure with reference to 11 described. 11 is a block diagram illustrating an example of a configuration of the MEC server 300 in accordance with an embodiment of the present disclosure. With reference to 11 instructs the MEC server 300 a communication unit 310 , a storage unit 320 and a processing unit 330 on.

( 1 ) Communication unit 310

The communication unit 310 is an interface for performing communication with other devices. For example, the communication unit performs 310 a communication with the corresponding wireless communication device 100 out. In a case where the MEC server 300 is formed as a logical entity and included in the wireless communication device 100, the communication unit performs 310 a communication with, for example, a control unit of the wireless communication device 100 out. The MEC server 300 may have an interface for communicating directly with a device other than an integrally formed device.

Memory unit 320

The storage unit 320 temporarily or permanently saves a program and various data for the operation of the MEC server 300 , For example, the MEC server 300 store various content and applications to be provided to the user.

Processing unit 330

The processing unit 330 provides various functions of the MEC server 300 ready. The processing unit 330 has an MEC platform 331, a virtual network function (VNF) 333 and a service providing unit 335. Furthermore, the processing unit 330 further include components other than such components. In other words, the processing unit 330 may perform other operations than the operations of such components.

The MEC platform 331 is similar to one described above with reference to FIG 2 has been described.

The VNF 333 is a software package for implementing a network function. The VNF 333 operates on a virtual machine called the Network Function Virtualization Infrastructure (NFVI). For the VNF and NFVI, specifications are reviewed by the ETSI Network Function Virtualization Industry Group (NFV ISG). The details of this are, for example, in "ETSI", "GSNFV-SWA 001 V1.1.1 (2014-12)", December 2014, [accessed 19 November 2015], 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 a VNF whose specification is being verified, or more generally may mean a virtualized network function.

The service providing unit 335 has a function of providing various services. Typically, the service providing unit 335 is implemented as an MEC application operating on the MEC platform 331. Further, in this specification, an application is included in the MEC server 300 is also referred to as an "MEC application". For example, the MEC application running on the MEC server 300 is an instance of an application used by the application server 60 is copied, or can be an application directly on the MEC server 300 is implemented.

<Configuration example of the application server>

Thereafter, an example of a configuration of the application server 60 according to an embodiment of the present disclosure with reference to 12 described. 12 Figure 12 is a block diagram illustrating an example of the application server configuration 60 in accordance with an embodiment of the present disclosure. With reference to 12 instructs the application server 60 a communication unit 61 , a storage unit 62 and a processing unit 63 on.

( 1 ) Communication unit 61

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

Memory unit 62

The storage unit 62 Temporarily or permanently stores a program and various data for operating the application server 60 , For example, the application server 60 store various content and applications to be provided to the user.

Processing unit 63

The processing unit 63 represents different functions of the application server 60 ready. The processing unit 63 corresponds for example to a central processing unit (CPU) or the like. The processing unit 63 has a service delivery unit 64 on. Furthermore, the processing unit 330 further include components other than such components. In other words, the processing unit 330 perform other operations than the workflows of such components.

The service delivery unit 64 has a function to provide various services. Typically, the service delivery unit 64 implemented as an application.

There will also be an application running on the application server 60 is operated and has a correspondence relationship with an MEC application running on the MEC server 300 is also referred to as an "MEC application". Similarly, an application that is on the terminal 200 is operated and has a correspondence relationship with an MEC application running on the MEC server 300 is also referred to as "MEC application".

The configuration examples of the respective devices have been described above. Hereinafter, to simplify the description, the wireless communication device will be described 100 also referred to as "eNB 100", and the terminal 200 is also referred to as "UE 200".

<< First Embodiment >>

As a solution to the above problems, a mechanism for implementing the connectivity with the UE by placing the MEC server anywhere (for example, an RN, an eNB, an S-GW, or the like) and switching a packet path by a switching function (SW) as Deep Packet Inspection (DPI) tested. In this regard, an example of a mode for switching the packet path by the DPI will be described as the present embodiment.

<Technical features>

For example 13 an explanatory diagram for describing an example of a schematic configuration of the system 1 according to the present embodiment, and illustrates an example of a configuration for implementing the connectivity between the MEC server 300 and the UE 200 through the DPI. As in 13 shown, the system instructs 1 an eNB 100, a UE 200 , an MEC server 300 , an S-GW 41, a P-GW 42, a MME 43 , an HSS 44 , a PDN 50 and an application server 60 on. In the example that is in 13 3, an MEC-DPI 333A and an MEC router 333B are shown on the MEC server 300 operated as the VNF. Further, an MEC application 335 will be on the MEC server 300 operated. It should be made clear that in 13 solid lines indicate the user plane (also referred to as data plane) and dashed lines indicate the control plane.

The DPI 333A has a function to cast a glance (for example, DPI) on the detected packet. For example, the MEC-DPI 333A removes a GTP for the user-level (GTP-U) header of a packet to be transmitted from the eNB 100 to the S-GW 41, looks at an IP header, and detects in the IP header stored information (for example, a destination IP address of the packet).

The MEC router 333B has a function of switching the packet path. For example, in a case where the destination IP address detected by the MEC-DPI 333A indicates the MEC application 335, the MEC router 333B transmits the packet directly to the MEC application 335 other than the S-GW 41 is. At this time, the MEC router 333B may add a GTP-U header to the MEC server 300 for the package and transmits the resulting packet. Meanwhile, in a case where the destination IP address detected by the MEC-DPI 333A does not indicate the MEC application 335, the MEC router 333B reassigns the once-removed GTP-U header to the packet and transmits it resulting package to the S-GW 41.

Therefore, the MEC router 333B holds the GTP-U header for each UE 200 and information specifying the S-GW 41 until the standard bearer (that is, the tunneling) between the eNB 100 and the S-GW 41 is released. Typically, the MEC router 333B holds such information until the release of the default bearer between the eNB 100 and the S-GW 41 is detected. Here, the release of the standard carrier can be detected by a plurality of methods. For example 14 to 17 Sequence diagrams showing examples of a flow of a process related to the release of a standard carrier. As a specific example, as in 14 For example, in a case where the UE performs a disconnect operation, the default bearer release may be recognized when the UE receives a disconnect accept signal from the MME, and thereafter the eNB 100 receives a disconnect enable (signal connection enable) signal. Further, in a case where the MME, the HSS or the P-GW performs the detaching operation, the release of the default bearer may be recognized when the eNB 100 likewise receives the link enable signal. For example, illustrated 15 an example in which the MME performs a detach operation. Further notes 16 an example in which the HSS performs the separation process. In a similar way 17 an example in which the P-GW performs the separation process. Further, the examples of the flow of the process associated with the release of the standard carrier incorporated in the 14 to 17 is generally known and therefore a detailed description thereof will be omitted. Furthermore, the release of the default bearer may be detected when the eNB 100 detects the UE 200 fails, as in a case where the energy of the UE 200 is off.

Next, attention is paid to a connection method between the MEC servers in a case where the connectivity from the UE to the MEC server is implemented by a scheme based on the DPI. 18 For example, FIG. 10 is an explanatory diagram for describing an example of a configuration for implementing the connectivity between MEC servers by the DPI. 18 shows an example of establishing a connection between a first MEC server 300 - 1 , which is installed in an eNB 100, and a second MEC server 300 -2, which is installed in an S-GW 41. In 17 For example, a path indicated by a bold line corresponds to a communication path between an MEC application running on the first MEC server 300 - 1 operated, and an MEC application running on the second MEC server 300 -2 is operated.

An overview of a process for establishing a communication path between the first MEC server 300 - 1 and the second MEC server 300 -2, which is in 18 is indicated by a bold line is described.

First, the first MEC server captures 300 - 1 Identification information specifying another MEC server located nearby (ie, a higher-level aggregation point) (for example, an IP address or the like containing the second MEC server 300 -2 specified), a service discovery function provided by an MEC platform. Further, in the following description, an IP address of another MEC server than the identification information specifying another MEC server will be obtained.

Then the first MEC server adds 300 - 1 add a GTP header specifying the detected IP address and the S-GW 41 to a packet serving as a transmission destination (for example, a packet from an MEC application 335-1) and transmit the result packet to one MEC Router 333B-1. The MEC router 333B-1 transmits that from the first MEC server 300 - 1 transferred package to the S-GW 41.

The S-GW 41 replaces the GTP header of the packet transmitted from the MEC router 333B-1 with a GTP header to connect to a P-GW 42 and transmits the resulting packet to an MEC DPI 333A-2 of the second MEC server 300 -2.

The MEC-DPI 333A-2 removes the GTP header from the received packet and detects the IP address indicating the transmission destination of the packet. Then, an MEC router 333B-2 switches the path of the packet in accordance with the destination indicated by the detected IP address. For example, in a case where the detected IP address indicates an MEC application 335-2 residing on the second MEC server 300 -2, the MEC router 333B-2 transmits the packet directly to the MEC application 335-2 and not the P-GW 42. Further, in a case where the detected IP address becomes the MEC application 335 -2, on the second MEC server 300 -2 is operated, does not specify to transfer the package to the P-GW 42.

Accordingly, the transmission of the packet from the first MEC server 300 - 1 to the second MEC server 300 -2 executed. Furthermore, one will appreciate that the transfer of the package from the second MEC server 300-2 to the first MEC server 300 - 1 is also implemented by a similar process. Furthermore, the example that was presented in 18 is described in consideration of the case where the connection between the MEC servers installed in the eNB and the S-GW is made, but it is not necessarily limited to the same mode. As a specific example, it is also possible to establish a connection between the MEC servers through a similar process between the RN and the eNB, between the eNB and the eNB, and between the RN and the S-GW.

<Evaluation>

According to the present embodiment, the shortest communication path which does not pass through the P-GW 42 becomes between the UE 200 and the MEC application 335. Further, according to the present embodiment, it is also possible to set the communication path between the MEC servers. On the other hand, as above with reference to 18 10, it is considered that a case where the connection between the MEC servers based on the DPI is made as in the present embodiment has the following disadvantages.

First, in the system 1 According to the present embodiment, the DPI is executed on all packets sent from the UE 200 or the MEC server 300 transmitted by the MEC-DPI 333A. Therefore, a processing load for the DPI increases, and a processing delay time increases. Further, a function for removing a header group (for example, the IP header, the UDP header, the GTP-U header, and the like), a function for storing the removed header group, is a management function for managing the UE 200 and the MEC server 300 and a header group list and a function to add the header group. Such incidents cause scalability problems. Further, a mechanism is required for preventing problems with the security and confidentiality of the user data that may be caused by the DPI function.

In a case where the eNB 100 connected to a relay node and the MEC server 300 or a wireless backhaul that forwards the user packet wirelessly is also integrally formed, it is also required that the MEC server 300 has a wireless communication interface.

In this regard, in order to solve the above-mentioned disadvantages, a second embodiment has been developed, which will be described below.

. "4 Second embodiment »

Hereinafter, the second embodiment of the present disclosure will be described in detail.

<Technical features>

Virtualization of the network health entity

First, an example of an architecture of the MEC server will be described with reference to FIG 19 described. 19 Fig. 10 is an explanatory diagram for describing an example of an architecture of the MEC server. As in 19 As shown, the MEC server has hardware such as a standard commercial (COTS) device, a computer, main memory, and an input / output (I / O) interface. Further, a kernel-based virtual machine (KVM) hypervisor or container engine is operated on such hardware, and the MEC platform and a plurality of VMs, a plurality of VNFs, and a plurality of applications become on the KVM hypervisor operated. As a more specific example, a KVM hypervisor may be caused to operate on a host operating system, and an MEC platform, a VM, a VNF, and an application may be caused to operate on the KVM hypervisor. Further, as another example, a container engine may be caused to operate on the host operating system, and the MEC platform, the VM, the VNF, and the application may be caused to operate on the container engine. As another example, the KVM hypervisor and the container engine may be caused to operate on the host operating system, and the MEC platform, the VM, the VNF, and the application may reside on the KVM hypervisor and the container engine. Engine operated.

For example, a virtual MME (vMME) implemented by virtualizing an MME is considered a VNF 1 on a virtual machine (VM) - 1 operated. Furthermore, a vS-GW that is virtualized by The S-GW is implemented as a VNF-2 operated on a VM-2. Further, a vP-GW implemented by virtualizing the P-GW is operated as a VNF-3 on a VM-3. Further, a vHSS implemented by virtualizing the HSS operates as a VNF-4 on a VM-4. Further, a vPCRF implemented by virtualizing the PCRF is operated as VNF-5 on a VM-5. Further, a vRAN implemented by virtualizing a Radio Access Network (RAN) operates as a VNF-6 on a VM-6. Further, a functional entity providing a Radio Network Information Services (RNIS) function operates as VNF-7 on a VM-7. Further, a functional entity providing a location function is operated as VNF-8 on a VM-8. Further, a functional entity providing a mobility function is operated as VNF-9 on a VM-9. Furthermore, a functional entity that provides a management function is called a VNF 10 on a VM 10 operated. Further, a functional entity providing the service discovery function operates as VNF-11 on a VM-11. Here, the service discovery function is a function provided by a function delivery platform on the MEC server (for example, the MEC platform) and provides information specifying another MEC server whose connection destination is an application or the like (eg, IP Address or the like), a search result for an available service and the like.

Furthermore, the MEC application can operate as an application on a VM-12. Furthermore, the MEC application can be operated on the KVM hypervisor. For example, in the example that is in 19 a first MEC application (application 1 ) and a second MEC application (Anw-2) as applications on the KVM hypervisor.

In addition, a VNF responds to requests such as responses to a transmission band (a transmission speed), a delay request, an optimization of a transmission speed of TCP / IP or the like, and Operations System Supports (OSS) / Business System Supports (BSS). In a case where communication with an existing device (for example, a base station, PCRF, HHS, MME, or the like) is necessary, the VNF is operated via an API and and performs a communication exchange. Further, a protocol and interface will be described separately below with an embodiment of the present disclosure. Further, in the following description, "v", which stands for (virtual), is assigned names of functional entities that are virtualized on the MEC server, such as a vMME, a vP-GW, and a vS-GW.

Next, an example of a network architecture including the MEC server will be explained with reference to FIG 20 described. 20 Fig. 10 is an explanatory diagram for describing an example of a network architecture having the MEC server. As in 20 For example, access from a network management function such as an OSS or BSS to a functional entity virtualized on the MEC server is managed by the MEC platform much like access to an existing functional entity.

Further, a VNF manager and an MEC manager monitor an operation of an application operating on a virtualization layer such as the functional entity virtualized on the MEC server, the MEC application, or the like, and control the operation of the application according to one monitoring result. Similarly, a virtualization platform manager monitors workflows of hardware such as a standard commercial machine (COTS), a computer, main memory and an input / output (I / O) interface, and the KVM hypervisor and container engine running on the hardware is operated. Further, the virtualization platform manager controls the operations of the hardware and the KVM hypervisors and the container engine that operates on the hardware according to a monitoring result. In addition, the VNF manager and the MEC manager are operated in cooperation with the virtualization platform manager. Further, the operations of the network management function, the VNF manager, the MEC manager, and the virtualization platform manager may be autonomous based on management by an orchestrator.

Example of the system configuration

In order to facilitate the understanding of the features of the present embodiment, an example of a schematic configuration of a system will next be described 1 described according to the present embodiment.

21 Fig. 10 is an explanatory diagram for describing a schematic configuration of the system 1 according to the present embodiment. In the example that is in 21 shows system features 1 an eNB 100, DeNBs 110-1 and 110-2, RNs 120-1 and 120-2, a UE 200 , MEC server 300 -0 to 300-5, an S-GW 41, a P-GW 42, a MME 43 , an HSS 44 , an OCS 45, an OFCS 46, a PCRF 47 PDN 50 and an application server 60 on. Further, information described in parentheses in the blocks indicating the respective nodes of the eNB 100, the DeNBs 110-1 and 110-2 and the RNs 120-1 and 120-2 indicate the identification information of the corresponding node.

In the example that is in 21 is the MEC server 300 -0 of the base station 100 assigned (for example, integrally formed). Similarly, the MEC servers 300 - 1 and 300 -3 assigned to RNs 120-1 and 120-2. Further, the MEC servers 300 -2 and 300-4 are assigned to DeNBs 110-1 and 110-2. Further, the MEC server 300 -5 assigned to the S-GW 41.

In each of the MEC servers 300 -0 to 300-5, the VNF corresponding to the characteristic of the MEC server is operated on the MEC platform. In particular, in the MEC server 300 - 1 assigned to RN 120-1, a vDeNB, a vS-GW, a vP-GW, and an MEC storage 1 operated on the MEC platform. Furthermore, the MEC memory 1 a location where an MEC application and an instance such as an application server operated on the MEC server 300-1 are stored. Furthermore, the MEC memory 1 a place where a VM and a container are stored. Unless otherwise stated, it will be assumed in the following description that a simply written "MEC application" has an operating platform of the MEC application operating on the MEC server, such as the application server. Further, in the following description, in a case where the vDeNB, the vS-GW, and the vP-GW residing in the MEC server 300 - 1 are explicitly specified, they are also referred to as vDeNB_1, vS-GW_1 and vP-GW_1. Furthermore

are similar in the MEC server 300 -3 assigned to the RN 120-2, a vDeNB_3, a vS-GW_3, a vP-GW_3, and an MEC application running on the MEC platform. Further, in the MEC server 300-0 assigned to the eNB 100, a vS-GW_0, a vP-GW_0 and an MEC application are operated on the MEC platform. Further, in the MEC server 300 -2 assigned to the DeNB 110-1, a vS-GW_2, a vP-GW_2 and an MEC application running on the MEC platform. Similarly, in the MEC server 300 -4 assigned to the DeNB 110-2, a vS-GW_4, a vP-GW_4 and an MEC application running on the MEC platform. Further, in the MEC server 300 -5 assigned to the S-GW 41, a vP-GW_5 and an MEC application running on the MEC platform. Further, a VNF obtained by virtualizing other functional entities in the mobile communication network, such as a vMME, a vHSS and a vPCRF, may be in each of the MEC servers 300 -0 to 300-5 are operated. In 21 Solid lines indicate a user plane and a dashed line indicates a control plane. Further, under the solid lines in 21 Specifically, a portion indicated by a thick line indicates a communication path that is set virtually (a virtual bear to be described later). The virtualized VNF (the vDeNB, the vS-GW / the vP-GW) and the like can operate on the NFV platform or other virtual platforms.

Determination of the carrier

In the system 1 According to the present embodiment, the MME 43 places the carrier between the MEC servers 300 fixed (ie, set this up).

Determination of the MEC carrier

In particular, the MME generates 43 First, administrative information showing the connection path between the MEC servers 300 (hereinafter also referred to as "GW allocation list") to specify in advance. In the GW allocation list, there are one APN to connect to each MEC server 300 (ie an APN that hosts the vP-GW of the MEC server 300 specified) and a list of gateways that will be passed when connected to the MEC server 300 (for example, a P-GW, an S-GW, a vP-GW, and a vS-GW) are recorded in conjunction with each other.

For example, illustrated 22 an example of information recorded in a GW allocation list. In the example that is in 22 is an identification information of a node of a wireless network (for example, an RN, an eNB, a DeNB or the like), an APN indicating a connection destination, and a list of gateways that are passed when a connection between the node and a server designated by the APN (for example, the MEC servers) in association with each other. In addition, a numeric value in brackets indicates the number of physical hops. Specifically, as a specific example, a case is considered in which a connection between the RN 120-1 indicated by "RN_1" and the MEC server designated by "vAPN # 5" 300 -5 in the system 1 is made in 21 is shown. In this case, in the GW Mapping List Information, which is the DeNB 110-1, the S-GW 41, and the vP-GW_5 in the MEC server 300 5, recorded in an entry indicating a connection relationship between a note indicated by "RN_1" and a server designated by "vAPN # 5".

23 further illustrates another example of information recorded in a GW allocation list. In the example that is in 23 That is, APNs indicating a connection source and a connection destination and a list of gateways passed when establishing a connection between servers designated by the APNs are recorded in association with each other. In addition, a numeric value in brackets indicates the number of physical hops. As a specific example, the main focus is placed on a case where there is a connection 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 allocation list, the RN 120-1, information is respectively the DeNB 110-1 and the vS-GW_2 and the vP-GW_2 in the MEC server 300 -2, which are passed at the time of connection, recorded in an entry indicating the connection relationship between the servers specified by "APN # 1" and "vAPN # 2".

Further, in the GW allocation list, information such as identification information (an ID of the P-GW or the like) indicating each node and identification information (an ID of a vAPN, PDN or the like) designating each server are obtained in advance, for example, in FIG HSS 44 recorded and managed (provided / commissioned). In other words, for example, the MME 43 the GW allocation list based on the HSS 44 Generate captured information.

In a case where the MME 43 receives a connection request assigned to an APN, which is the connection destination from the MEC server 300 indicates a carrier is between the MME 43 serving as a request source and another MEC server 300 which is designated by the APN to which the connection request is assigned based on the GW allocation list. Here is an overview of the MME 43 specified carrier described in conjunction with an example in which the carrier between the MEC server 300 - 1 (MEC server 1 ) and the MEC server 300 -2 (MEC server 2) in 21 with reference to 24 is fixed. 24 Figure 12 is an explanatory diagram for describing an overview of the bearer established between the MEC servers.

For example, in a case where the MME 43 receives a connection request that is assigned to an APN representing the MEC server 300 -2 from the MEC server 300 - 1 specifies the MME 43 a list of gateways that connect to the MEC servers 300 - 1 and 300 -2, based on the GW allocation list. Accordingly, for example, the vP-GW_1 and the 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 vS-GW_2 and the vP-GW_2 of the MEC server 300 -2 specified. Further, physical components such as the RN, the eNB, the DeNB, the P-GW and the S-GW among the specified gateways correspond to an example of a "first gateway". Further, virtual components such as the vP-GW and the vS-GW correspond to the MEC server 300 an example of a "second gateway".

Then put the MME 43 the bearer between the two components of the vP-GW_1, the vS-GW_2, the DeNB_1 (ie RN 120-1), the DeNB_1 (ie DeNB 110-1), the vS-GW_2 and the vP-GW_2, the are specified. Further, a flow of a series of processes relating to the setting of each carrier will be described in detail later by way of example.

Then the MME 43 define a set of carriers between the two components of vP-GW_1, vS-GW_2, DeNB_1 (ie RN 120-1), DeNB_1 (ie DeNB 110-1), vS-GW_2 and vP -GW_2 are defined as virtual bearers. For example, a number of carriers may be 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) as a carrier. Further, in the following description, the virtual carrier will also be referred to as an "MEC carrier".

Extension of the MEC carrier

Furthermore, it is in the system 1 For example, according to the present embodiment, it is possible to switch the MEC carrier between services running on a plurality of MEC servers 300 by virtualizing a path to the vP-GW in the MEC server 300 as a VNF and deploy the VNF to expand. Further, examples of the service in the present description include a service that is for each over-the-top (OTT) such as a service provider and an application, a VM, a container and the like that are operated individually.

As a specific example, the main focus is on a case where the MME 43 sets the carrier between services that are in the MEC servers 300 - 1 and 300 -2 are operated. In this case, the MME captures 43 in addition to the connection request assigned to the APN indicating the connection destination, information (for example, a URI, an IP address or the like) specifying a service included in the MEC server 300 -2, acting as the connection destination from the MEC server 300 - 1 serves. It can also provide information on the MEC server 300 2 service, using, for example, the service discovery function provided by the MEC platform.

Then specify the MME 43 Based on the GW Mapping list, a list of gateways that will be passed when connecting between the MEC servers 300 - 1 and 300 -2 based on the GW allocation list. Then put the MME 43 the carrier between the specified gateways. Accordingly, a number of carriers will be 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).

Furthermore, the MME lays down 43 by virtualizing the path from the vP-GW_2 to the service running in the MEC server 300 -2 as the VNF operates, based on the information that identifies the captured service in the MEC server 300 -2 specify. The same applies to the MEC server side 300 -1.

Furthermore, the MME lays down 43 the carrier received by virtualizing the path from the vP-GW for the service in each of the MEC servers 300 - 1 and 300 - 1 and a number of carriers that use the vP-GWs of the MEC server 300 - 1 and 300 -2, as the virtual bearer (that is, the MEC bearer). Further, in the following description, the virtual carrier in a case where it is particularly different from an "MEC carrier" will also be referred to as an "extended MEC carrier". With such a configuration, the carrier can be identified by virtualizing a series of carriers between the vP-GW_1 of the MEC server 300 - 1 and the vP-GW_2 of the MEC server 300 -2, will continue to be extended between the services available in the MEC servers 300 - 1 and 300 -2 are operated.

For example 25 and 26 Diagrams illustrating an example of a protocol stack of communication between the MEC servers and an example of setting the carrier between the MEC servers 300 - 1 and 300 -2 correspond to in 21 are shown. Further illustrated 25 an example of an architecture in a case where the GTP-U is not in the protocol stack of the MEC server 300 is included. In the example that is in 25 A GTP and a Generic Routing Encapsulation (GRE) protocol are presented in the vP-GW of the MEC server 300 completed. Further illustrated 26 an example of an architecture in a case where the GTP-U in the protocol stack of the MEC server 300 is included. In the case of the example which is in 26 is shown, the GTP and the GRE protocol are terminated at a point (for example, an IP address or the like) representing the MEC server 300 specified.

As described above, in the system 1 According to the present embodiment, since the path to the vP-GW is virtualized and provisioned as the VNF in the MEC server 300, the carrier up to the MEC server 300 be extended. Further, in the system 1 According to the present embodiment, the 3GPP-specified scheme of the carrier is extended to the MEC server 300 and used, and thus, for example, it is also possible to extend a flow-based QoS to a two-way communication between the MEC servers 300.

Configuration example of the carrier

27 and 28 For example, diagrams illustrating an example of a configuration of an MEC carrier are shown. More specifically illustrated 27 an example of a configuration of the MEC carrier in a case where the GTP and the GRE protocol are terminated at a point (for example, an IP address or the like) that the MEC server 300 specified as in 26 shown. Further notes 28 an example of a configuration of the MEC carrier in a case where the GTP and the GRE protocol in the vP-GW of the MEC server 300 be ended, as in 25 shown.

Furthermore, a destination to which the APN is assigned is not necessarily limited to the MEC server 300 limited. As a specific example, for example, the APN may be assigned for each OTT, such as the service provider or for each application. In this case, for example, even in a situation where services (ie, applications) of a plurality of OTTs are operated on an MEC server 300, each service provided by the OTT may be individually specified based on the APN. In addition, it is also possible to assign the APN for each VM in which an application is installed, or for each container.

For example 29 and 30A Diagrams illustrating an example of a configuration of the MEC carrier. In the example that is in 29 and 30A is shown, the MEC carrier (for example, the extended MEC carrier) is set for each OTT in a situation where a plurality of OTT services are on the MEC server 300 operate. Further illustrated 29 an example of a configuration of the MEC carrier in a case where the GTP and the GRE protocol are terminated at a point (for example, an IP address or the like) that the MEC server 300 specified as in 26 shown. Further illustrated 30A an example of a configuration of the MEC carrier in a case where the GTP and the GRE protocol in the vP-GW of the MEC server 300 be ended, as in 25 shown. For example, with such a configuration it is also possible to provide independent QoS for each OTT, for each VM or for each container. For example 30B Fig. 12 is a diagram illustrating an example of a configuration of the MEC carrier and illustrating an example in which the MEC carrier is set for each container. Further is 30C FIG. 12 is a diagram illustrating an example of a configuration of the MEC carrier and illustrating an example in which the MEC carrier is set for each VM.

Further shows 31 an explanatory diagram for describing an example of a carrier configuration in the system 1 according to the present embodiment and illustrates an example in which the MEC server 300 provides a service to the UE. For example, in an example that is in an upper part of 31 shown is the MEC server 300 - 1 (MEC server 1 ) the UE with the help of another MEC server 300 -2 (MEC server 2) ready a service. In this case, the EPS carrier becomes between the UE and the MEC server 300 - 1 and the MEC carrier is placed between the MEC server 300 - 1 and the MEC server 300 -2 set. Further, the lower part of FIG 31 an example in which the MEC server 300 - 1 (MEC server 1 ) service to the UE with the help of the application server 60 provides. In this case, the EPS carrier becomes between the UE and the MEC server 300 - 1 and the MEC carrier is placed between the MEC server 300 - 1 and the application server 60 established. With such a configuration, the system can 1 According to the present embodiment, provide the carrier that satisfies the QoS required by the service in a more appropriate form.

<First example>

Next, an example of setting the MEC carrier between the MEC servers 300 on the basis of a request from a network management function such as an OSS or a BSS (hereinafter simply referred to as "OSS") as a first example of the present embodiment. Further, the present description will be described with particular attention to a case in which information of an application from the MEC server 300 - 1 to the MEC server 300 -2 are moved by the MEC carrier between the MEC server 300 - 1 and the MEC server 300 -2 in 21 is determined on the basis of the request by the OSS.

32 For example, FIG. 10 is a sequence diagram illustrating an example of a flow of a carrier designation process used in the system 1 is executed according to the first example of the present embodiment. As in 32 shown are the OSS, the HSS 44 , the MME 43 , the MEC server 300-1 (MEC Server 1 ), the RN 120-1 (RN_1), the DeNB 110-1 (DeNB_1), the S-GW 41, and the MEC server 300 -2 (MEC Server-2) involved in the present sequence.

First, a list of identification information (an ID of the P-GW or the like) indicating each node, identification information (an ID of the APN, PDN or the like) designating each server, and the like in the HSS 44 registered on the basis of a statement from the OSS (S301). The MME 43 generates the GW allocation list based on the information contained in the HSS 44 are registered (S303). Further, it is preferable to perform the generation of the GW allocation list in advance, and the same process does not have to be performed each time the MEC carrier is interposed between the MEC servers 300 is determined.

Next, the description will be directed to the process of setting an MEC carrier between the MEC servers 300 focus on a statement from the OSS. For example in a case where the information of an application is between the MEC servers 300 be moved, the network administrator or the like the MEC server 300 , which serves as a moving target of the information of the application, and gives an instruction to move the information to the OSS via a UI (eg, a GUI).

As a specific example, it is assumed that the network administrator or the like has an instruction for moving the information of the application from the MEC server 300 - 1 to the MEC server 300-2 to the OSS via the UI (for example, the GUI). In this case, the OSS transmits a request to set the MEC carrier between the MEC server 300-1 and the MEC server 300 -2 to the MME 43 , Accordingly, an MEC carrier designation request signal from the OSS to the MME 43 transferred (S305). Further, the MEC carrier designation request corresponds to an example of a "connection request".

Upon receipt of the MEC bearer setup request from the OSS, the MME checks 43 the APN for establishing a connection with each of the MEC servers 300-1 and 300-2 and the GW allocation list and specifies a list of gateways when connecting from the MEC server 300 - 1 with the MEC server 300 -2 (S307). In the example that is in 32 are the vP-GW_1, the vS-GW_1 and the vDeNB_1, the RN 120-1, the DeNB 110-1, the S-GW 41 and the vS-GW_2 and the vP-GW_2 in the MEC server 300 - 1 specified.

Further, the P-GW corresponding to the APN is specified on the basis of, for example, a mechanism such as a Fully Qualified Domain Name (DNS) or the like. It is preferable to use the GW in which every MEC server 300 is installed to specify based on information previously registered on the basis of an instruction from an OTT or the like such as a service provider, similar to a TAI list allocation policy or the like. Using the function provided by the MEC platform (eg API), the MEC server can 300 Further, position information from connected nodes (eg, radio nodes such as eNodeB, NodeB, relay node, DeNodeB, or the like) can be captured and transmitted by the MME 43 inform about the recorded position information.

Then the MME points 43 vS-GW_1 of the MEC server 300 - 1 to set up the S5 / S8 bearer with the vP-GW_1. Upon receiving the instruction, the vS-GW_1 sets up the S5 / S8 bearer with the vP-GW_1. Furthermore, the MME 43 the vDeNB_1 of the MEC server 300 - 1 to set up the S1-U carrier with the RN 120-1. After receiving the instruction, the vDeNB_1 sets the S1-U carrier with the RN 120-1 (S309). Further, in a case where the setting of each carrier is completed, a response to the MEC carrier designation request from the MEC server becomes 300 - 1 to the MME 43 transferred (S311).

Similarly, the MME 43 the vS-GW_2 of the MEC server 300 -2 to set up the S5 / S8 carrier with the vP-GW_2. After receiving the instruction, the vS-GW_2 sets up the S5 / S8 bearer with the vP-GW_2. Furthermore, the MME 43 the vS-GW_2 of the MEC server 300 -2 to set up the S1-U carrier with the DeNB 110-1. Upon receiving the instruction, the S-GW_2 sets the S1-U carrier with the DeNB 110-1 (S313). Further, when the determination of the carrier is completed, a response to the MEC carrier request from the MEC server becomes 300 -2 to the MME 43 transmitted (S315).

Furthermore, the MME 43 instruct the DeNB 110-1 to set up the S1-U / Un bearer between the DeNB 110-1 and the RN 120-1 via the S-GW 41 (S317). Upon receipt of the instruction, the DeNB_1 sets the S1-U / Un bearer between the DeNB 110-1 and the RN 120-1 (S319). Further, when the setting of the carrier is completed, a response to the MEC carrier designation request from the S-GW 41 to the MME becomes 43 transferred (S321).

Further, a case may be considered in which at least some of the above-described carriers have already been set. In this way, in a case where there is a carrier already set, it is not necessary to set a new carrier, and the already set carrier can be used.

Accordingly, a number of carriers will be the MEC server 300 - 1 and the MEC server 300 -2 connect, set, and transfer data between the MEC server 300 - 1 and the MEC server 300 -2 and the communication between the applications can be carried out via the carrier. Then, if the identification information (for example, an IP address or the like) of a communication point of the MEC server 300 - 1 and 300 -2 will be a new bearer (tunnel) at each communication point between the vP-GW_1 and the MEC server 300 - 1 and a communication point between the vP-GW_2 and the MEC server 300 -2 as the default carrier. Furthermore, the MME lays down 43 the MEC carrier by virtualizing a set of carriers stuck between the MEC server 300 - 1 and the MEC server 300 -2 are set.

If then the completion of the determination of each carrier between the MEC server 300 - 1 and the MEC server 300 -2 (ie, the bearers between the gateways specified on the basis of the GW allocation list) is confirmed transmits the MME 43 a response to the MEC carrier determination request to the OSS (S323).

Accordingly, the MEC server 300 - 1 and the MEC server 300 -2 connected via the MEC carrier (S325). As a result, the MEC server can 300 - 1 the information of the application via the specified MEC carrier to the MEC server 300 -2 (S327).

Further, the protocol stack is in communication between the MEC server 300-1 and the MEC server 300 -2 in the first example, similar to the protocol stack described above with reference to FIG 25 and 26 has been described.

<Second example>

Next is an example where an application running on the MEC server 300 operated, with the assistance of an application operating on another MEC server 300 in a situation where the UE 200 communicates with the application is described as a second example of the present embodiment. Further, the present description will focus on a case in which, in 21 configuration shown, the MEC carrier between the MEC server 300 - 1 and the MEC server 300 -2, on which an application Anw-2 is based on a request from an application. 1 is operated on the MEC server 300 - 1 is operated.

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

First, a list of identification information specifying each node, identification information specifying each server, and the like in the HSS 44 registered on the basis of the instruction from the OSS (S401), the MME 43 generates the GW allocation list based on the information (S403). Further, the present process is similar to the process represented by reference symbols S301 and S303 in FIG 32 is specified.

Furthermore, a workflow of the application 1 on the MEC server 300-1 based on the request from the UE 200 (S405).

Here it is assumed that it is for the application 1 necessary with the on the MEC server 300 -2 operated application Anw-2 to cooperate with the UE 200 to provide the service. In this case, the application covers application 1 Information (for example, the APN) to connect to the MEC server 300 -2, in which the application Anw-2 is stored, using the service discovery function provided by the MEC platform (S407).

Then the application transmits 1 the MEC carrier determination request to set the MEC carrier between the MEC server 300 - 1 and the MEC server 300 -2 to the MME 43 based on the recorded APN. Accordingly, the determination request signal for the MEC bearer assigned to the APN is received from the MEC server 300 - 1 to the MME 43 transmit (S409). Furthermore, a counterpart to which the application is 1 the MEC bearer setup request transmits to be an vMME acting as the VNF in the MEC server 300 - 1 is implemented. Furthermore, an interface (ie a communication path) between the application 1 and the MME 43 so that the vS-GW implemented as the VNF is implemented. Furthermore, as another example of the interface, the application may 1 to the MME 43 an interface provided by a function called a Service Capability Exposure Function (SCEF). Further, the SCEF will be described later in detail.

Further, the processes indicated by the reference symbols S411 to S425 are similar to the processes represented by the reference symbols S307 to S321 in FIG 32 are indicated. In other words, the MME checks 43 the APN to which the connection request from the application 1 and the GW allocation list, and specifies a list of gateways that will be passed when the connection is from the MEC server 300 - 1 to the MEC server 300 -2 is produced (S411). Then there is the MME 43 an instruction to set up the carrier to each of the vS-GW_1 and vDENB_1 of the MEC server 300 - 1 , the vS-GW_2 of the MEC server 300 -2 and S-GW 41. Accordingly, a set of bearers is set up to use the MEC server 300 - 1 and the MEC server 300 -2 connect. Then, if the identification information (for example, an IP address or the like) of a communication point of the MEC server 300 - 1 and 300 -2 will be a new bearer (tunnel) at each communication point between the vP-GW_1 and the MEC server 300 - 1 and a communication point between the vP-GW_2 and the MEC server 300 -2 as the default carrier. Furthermore, the MME lays down 43 Detect the MEC carrier by virtualizing a set of carriers running between the MEC server 300 - 1 and the MEC server 300 -2 are set (S413 to S425).

If so, then complete the determination of each carrier between the MEC server 300 - 1 and the MEC server 300 -2 confirms transmits the MME 43 a response to the MEC carrier determination request to the application 1 on the MEC server 300 - 1 (S427) is operated.

Accordingly, the MEC server 300 - 1 and the MEC server 300 -2 connected via the MEC carrier (S429). As a result, the communication between the on the MEC server 300 - 1 operated application 1 and the one on the MEC server 300 -2 operated application Anw-2 via the specified MEC carrier. In other words, the application can 1 Cooperate with the Anw-2 application via the specified MEC carrier (S431).

Further, the MEC bearer set forth in the present example may be, for example, the MEC bearer that is between the MEC servers 300 - 1 and 300-2, or the extended MEC carrier used between applications. 1 and Anw-2 (ie between the VMs or between the containers).

Furthermore, in the above description, the cooperation between the MEC servers 300 - 1 and 300 -2, but this is not necessarily limited to the same configuration. As a specific example, three or more MEC servers can be made to cooperate with each other. In this case, for example, the three or more MEC carriers may be caused to operate together by setting the MEC carrier between any two of the three or more MEC servers.

Also, the protocol stack is in communication between the MEC server 300 - 1 and the MEC server 300 -2 in the second example, similar to the protocol stack described above with reference to FIG 25 and 26 has been described.

<Third example>

Next is an example in which the MEC server 300 providing the service 200 in collaboration with another MEC server 300 operating, assuming a situation in which the UE 200 between cells provided by different nodes (eNB, RN and the like) is described as a third example of the present embodiment. Further, the present description will focus on a case in which, in 21 configuration, the MEC carrier is established between the two MEC servers (that is, between the MEC servers 300-1 and 300-3) to cause the MEC server 300 - 1 and the MEC server 300 -3 cooperate, assuming a situation that the UE 200 moves between the cells provided by the RNs 120-1 and 120-2.

For example 34 3 is a sequence diagram illustrating an example of a flow of a carrier designation process used in the system 1 is carried out according to the third example of the present embodiment. As in 34 shown are the OSS, the HSS 44 , the MME 43 , the UE 200 , the MEC server 300 - 1 (MEC server 1 ), RN 120-1 (RN_1), DeNB 110-1 (DeNB_1), S-GW 41, DeNB110-2 (DeNB2), RN120-2 (RN_2), and the MEC server 300 -3 (MEC Server-3) involved in the present sequence.

First, a list of identification information specifying each node, identification information specifying each server, and the like in the HSS 44 registered on the basis of the instruction of the OSS (S501), the MME 43 generates the GW allocation list based on the information (S503). Further, the present process is similar to the process represented by reference symbols S301 and S303 in FIG 30 is specified.

Furthermore, a workflow of the application 1 on the MEC server 300 - 1 based on the request from the UE 200 (S505).

If here is the UE 200 from a cell provided by the RN 120-1 to a cell provided by the RN 120-2, it is assumed that a state in which it is preferable to use another MEC server 300 to detect the one Service to the UE 200. To the UE 200 to deploy the service, the application tries to 1 in this case, the MEC server 300 that can provide a more suitable environment (eg, an environment in which a maximum delay, a guaranteed minimum bandwidth, or the like is satisfied) using the service discovery function provided by the MEC platform. To the MEC server 300 who can provide a more suitable environment to discover at this time, the application may 1 for example, position information of the UE 200 that is in a connected state, information of a node that is currently connected (for example, the RN, the eNB, the DeNB, the NB, or the like), and the like. As a result, the application covers 1 Information about connecting to the MEC server 300 -3 (for example, vAPN) (S507). Furthermore, in the following description, the application has 1 the APN as the information to connect to the MEC server 300 -3, however, one kind of information to be acquired is not particularly limited as long as it is possible to connect to the MEC server 300 -3. As a specific example, the application may 1 a URI or IP address as information to connect to the MEC server 300 -3 record.

Then the application 1 (or another application providing the service) an MEC carrier determination request to set the MEC carrier between the MEC server 300 - 1 and the MEC server 300 -3 to the MME 43 on the basis of the covered APN. As a result, the commit request signal for the MEC bearer assigned to the APN is assigned and received from the MEC server 300 - 1 to the MME 43 transmit (S509). It also becomes an interface from the MEC server 300 - 1 to the MME 43 implemented, for example, through an S1-MME interface via a node such as an eNB or an RN or an S11 interface via the S-GW.

Further, as another example, the interface from the MEC server 300-1 to the MME 43 the interface provided by the SCEF is used. In this case, for example, the MEC server 300 - 1 (or the application running in the MEC server 300 - 1 operated) using the SCEF a connection with the MME 43 establish and transmit the carrier determination request. Furthermore, the MEC server can 300 - 1 at this time also monitor a carrier setting state (for example, whether the setting of the carrier is completed or not) using the SCEF. Further, the SCEF will be described later in detail.

Upon receipt of the MEC carrier designation request from the application 1 checks the MME 43 the APN to connect to each of the MEC servers 300 - 1 and 300 -3 and the GW allocation list and specifies a list of gateways that will be used when connecting from the MEC server 300 - 1 with the MEC server 300 -3 (S511). In the example that is in 34 are the vP-GW_1, the vS-GW_1 and the vDeNB_1, the RN 120-1, the DeNB 110-1, the S-GW 41, the DeNB110-2, the RN120-2 and the vDeNB_3, the vS -GW_3 and the vP-GW_3 in the MEC server 300 - 1 specified.

Then the MME points 43 vS-GW_1 of the MEC server 300 - 1 to set up the S5 / S8 bearer with the vP-GW_1. Upon receiving the instruction, the vS-GW_1 sets up the S5 / S8 bearer with the vP-GW_1. Furthermore, the MME 43 the vDeNB_1 of the MEC server 300 - 1 to set up the S1-U carrier with the RN 120-1. After receiving the instruction, the vDeNB_1 sets the S1-U carrier with the RN 120-1 (S513). Further, in a case where the setting of each carrier is completed, a response to the MEC carrier designation request from the MEC server becomes 300 - 1 to the MME 43 transmit (S515).

Similarly, the MME 43 the vS-GW_3 of the MEC server 300 -3 to set up the S5 / S8 bearer with the vP-GW_2. After receiving the instruction, the vS-GW_3 sets up the S5 / S8 bearer with the vP-GW_3. Furthermore, the MME 43 the vDeNB_3 of the MEC server 300 -3 on, the S1-U carrier with to set up the DeNB 110-1. After receiving the instruction, the vS-GW_2 sets the S1-U carrier with the RN120-2 (S517). Further, when the determination of the carrier is completed, a response to the MEC carrier request from the MEC server becomes 300 -3 to the MME 43 transmitted (S519).

Furthermore, the MME 43 DeNB 110-1 to set up the S1-U / Un bearer between DeNB 110-1 and RN 120-1 via S-GW 41. Upon receiving the instruction, the DeNB_1 sets the S1-U / Un bearer between the DeNB 110-1 and the RN 120-1 (S523). Similarly, the MME 43 DeNB 110-2 via S-GW 41 to set up the S1-U / Un bearer between DeNB 110-2 and RN 120-2. Upon receipt of the instruction, the DeNB_2 sets the S1-U / Un bearer between the DeNB 110-2 and the RN 120-2 (S529). Furthermore, the MME 43 the S-GW 41 sets up the S1-U / Un bearer between the DeNB 110-1 and the S-GW 41 and between the DeNB 110-2 and the S-GW 41. Upon receipt of the instruction, the S-GW 41 sets the S1-U / Un bearer between the DeNB 110-1 and the S-GW 41 and between the DeNB 110-2 and the S-GW 41 (S525 and S527). Further, in a case where the setting of a series of carriers is completed, a response to the MEC carrier designation request from the S-GW 41 to the MME 43 transmit (S531).

Then, if the identification information (for example, an IP address or the like) of a communication point of the MEC server 300 - 1 and 300 -3, a new bearer (tunnel) will be created at each communication point between the vP-GW_1 and the MEC server 300 - 1 and a communication point between the vP-GW_3 and the MEC server 300 -3 as the standard carrier. Furthermore, the MME lays down 43 Detect the MEC carrier by virtualizing a set of carriers running between the MEC server 300 - 1 and the MEC server 300 -3 are set.

Further, a case may be considered in which at least some of the above-described carriers have already been set. In this way, in a case where there is a carrier already set, it is not necessary to set a new carrier, and the already set carrier can be used. Further, in the process, the carrier defined between the DeNB 110-1 and the DeNB 110-2 is the carrier defined between the RN 120-1 and the DeNB 110-1, and the carrier interposed between the RN 120-2 and the DeNB 110-2, equivalent to the bearer used for the X2 interface allocated in a one-to-one fashion.

If so, then complete the determination of each carrier between the MEC server 300 - 1 and the MEC server 300 -3 confirms, transmits the MME 43 a response to the MEC carrier determination request to the application 1 on the MEC server 300 - 1 (S533) is operated.

Accordingly, the MEC server 300 - 1 and the MEC server 300 -3 connected via the MEC carrier (S535). As a result, the application information between the MEC server 300 - 1 and the MEC server 300 -3 are transmitted via the specified MEC carrier.

As a more specific example, it is also possible to use the application Anw-3, which contains the information of the applica- 1 has taken on the MEC server 300 -3 by using the information of the application 1 from the MEC server 300 - 1 to the MEC server 300 -3 transmitted. Further, as another example, the application Anw-3 may be caused to run on the MEC server 300-3, and the application Anw-3 and the application Appln. 1 on the MEC server 300 - 1 can be made to work together.

Further, in a case where the UE 200 that starts on the new MEC server 300 -3 operated application Appl-3 from the applica- 1 to use the bearer of the UE 200 to the application 1 based on an instruction from the MME 43 be released. In this case, the MME 43 for example, upon receipt of the instruction from the UE 200 or give the application an instruction to release the vehicle.

Further, the MEC bearer set forth in the present example may be, for example, the MEC bearer that is between the MEC servers 300 - 1 and 300-3, or the extended MEC carrier used between applications. 1 and app-3 (for example, between the VMs or between the containers).

With the configuration described above, the UE 200 for example, even in a case where the UE 200 to a cell provided by the RN 120-2, the application providing the service 1 to the application 1 switch over this and continuously from the application Anw-3 received. Furthermore, the UE 200 even in a situation where the UE 200 between the cells provided by the RNs 120-1 and 120-2 are provided with the service in a more suitable environment (e.g., an environment in which the maximum delay, guaranteed minimum bandwidth, or the like is met).

Further, an example of the protocol stack is in communication between the MEC server 300 - 1 and the MEC server 300 -3 in the third example in 35 to 37 and 38 to 40 shown. 35 to 37 and 38 to 40 are diagrams illustrating an example of the protocol stack of communication between MEC servers. For example, illustrate 35 to 37 an example of an architecture in a case where the GTP-U is not in the protocol stack of the MEC server 300 is included. In the example that is in 35 to 37 A GTP and a GRE protocol are shown in the vP-GW of the MEC server 300 completed. Further illustrate 38 to 40 an example of an architecture in a case where the GTP-U in the protocol stack of the MEC server 300 is included. In the example that is in 38 to 40 GTP and the GRE protocol are terminated at a point that causes the MEC server 300 specified or at a point specifying the VM or the container (for example, an IP address or the like).

<Fourth example>

Next, an example in which the so-called access control is executed when the MEC carrier is set between the MEC servers located in various Public Land Mobile Networks (PLMNs) will be described as a fourth example of the present embodiment. 41 For example, FIG. 10 is an explanatory diagram for describing an outline of a fourth example of the present embodiment.

For example, illustrated 41 an example of a configuration in a case where access to the MEC server, which is located on a home PLMN page, from the MEC server 300 who is on a visited PLMN page is controlled. Further, the visited PLMN refers to a PLMN provided by another service provider (eg, a carrier) different from a service provider to which the UE is contractually connected (ie, a roaming connected PLMN). Further, the home PLMN refers to a PLMN provided by a service provider with which the UE has contacted.

As in 41 1, the access to the service operated in the MEC server on the home PLMN side by the MEC server located on the visited PLMN side is accessed by the vS GW on the visited PLMN side. Page executed via the vP-GW on the Home PLMN page. At this time controls in the system 1 For example, according to the present example, the MME on the visited PLMN side accesses the MEC server 300 on the home PLMN page of the MEC server located on the visited PLMN page, based on an access policy registered in the HSS on the home PLMN page.

As a specific example, in the access policy at the time of roaming, which is specified as an "HSS Provisioning APN List", a service having a "vAPN-H1" as the APN (ie, the service designated by a " OTT-1 ") is accessed from the visited PLMN page. Further, a service assigned a "vAPN-H 2" as the APN (a service provided by an "OTT-2") may not be accessed from the visited PLMN-side. Further, in the access policy, access is made to the service on the visited PLMN page assigned a "vAPN-V1" as the APN and access to a service on the home PLMN page assigned a "vAPN-H1" is, individually allowed.

In other words, on the visited PLMN page, for example, the MME prohibits access to the service that is assigned a "vAPN-H2" and that is provided by an "OTT-2" from the MME server on the visited PLMN page , based on an access policy at the time of roaming, which is registered in the HSS on the Home PLMN page. Further, on the visited PLMN page, the MME allows access to the service assigned the "vAPN-H1" provided by the "OTT-1" from the MEC server on the visited PLMN page, on the Basis of the access policy.

Further, in the system 1 For example, according to the present example, setting the MEC carrier between the MEC server (or service) operating on the visited PLMN side and the MEC server (or service) operating on the home PLMN Page is controlled based on the access policy at the time of roaming.

As a specific example, the MME on the visited PLMN page allows the MEC bearer for the service to be assigned to which the "vAPN-H1" is assigned and that of the "OTT-1" from the MEC server on the visited PLMN Page, based on the access policy at the time of roaming, which is registered in the HSS on the Home PLMN page. Furthermore, on the visited PLMN page, the MME prohibits the setting of the MEC bearer for the service to which the "vAPN-H 2" is assigned, and which is assigned by the "MEC-Server" on the visited PLMN-side of the "OTT". 2 ", based on the access policy.

Further, the above-described access control at the time of roaming is also applicable to the access control between MEC servers installed in networks of different carriers or to access control in which an MEC server implemented in a relay base station with mobility is considered becomes. Furthermore, the access control described above can be applied to a so-called local breakout.

<Fifth example>

Next is an example in which a mechanism of regulation and settlement control (PCC) in the system 1 is introduced according to the present embodiment, described as a fifth example of the present embodiment.

42 For example, FIG. 10 is an explanatory diagram for describing an outline of the fourth example of the present embodiment, and illustrates an example of a PCC architecture. As described above, a rules and billing enforcement (PCRF) function is a functional entity that performs rules and billing control. For example, as a more specific example, the PCRF performs the switching of QoS in accordance with a billing state in cooperation with an online accounting system (OCS) or an offline accounting system (OFCS). Further, a traffic recognition function (TDF) is, for example, a function for identifying and measuring traffic in a network or applying a rule for securing traffic.

Further, the PCEF is a functional entity that performs policy control and billing on an IP flow basis in accordance with information communicated by the PCRF. The PCEF can be mounted in the P-GW, for example. Furthermore, similar to the PCEF, the Bearer Biding and Event Reporting (BBERF) functions execute the rules control in accordance with information communicated by the PCRF. Further, the BBERF performs a cooperative process with a QoS controller that is specific to an access system, such as specifying a wireless access bearer for communicating a packet received from the P-GW to the eNB. For example, the BBERF can be mounted in the S-GW. Furthermore, the MEC server may correspond to an application function (AF) that is in 42 is shown.

In architecture, in 42 only one Rx interface for sharing (notifying) information, such as QoS, is defined as an interface from an AF (ie the MEC server) to the PCRF. For this reason, an interface for requesting the QoS from the AF to the PCRF is not specified, and the PCRF merely switches the QoS in accordance with information notified from the AF.

On the other hand, the application of a new function called SCEF is under review. The SCEF provides an interface for accessing a network function in the EPC from a Service Capability Server (SCS) or an Application Server (AS) and allows the exchange of information.

For example 43 an explanatory diagram for describing an example of an interface, which is implemented by the application of the SCEF. As in 43 For example, when the SCEF is applied, an interface for requesting QoS is provided from the SCS or the AS of the PCRF. Accordingly, for example, it is also possible to set a policy (for example, QoS or the like) in the PCRF from the MEC server (or the application running on the MEC server).

44 Figure 12 is also an explanatory diagram for describing another example of an interface implemented by the application of a SCEF. As in 44 For example, when the SCEF is applied, an interface is provided between the SCS and the AS and the HSS. Accordingly, for example, a connection request (ie, the MEC carrier designation request) may be issued another MEC server from the MEC server (or the application running in the MEC server) is transmitted directly to the MME via the SCEF and the HSS.

Further are 45 to 47 Illustrative diagrams for describing another example of an interface implemented by the application of the SCEF. For example, as in 45 For example, when the SCEF is applied, for example, the setup request for the bearer (eg, MEC bearer) may be transmitted to the MME from the MEC server (or the application running on the MEC server). Further, in a case where the carrier designation request is transmitted from the MEC server to the MME, it is possible to monitor the carrier designation state (for example, whether the vehicle designation is completed or not) via the interface provided by the application of the SCEF. For example, illustrated 46 an example of a flow of a series of processes related to the monitoring request. Further illustrated 47 an example of a flow of a series of processes associated with a report of the monitoring event.

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

As described above, when the ADC is applied to, for example, the MEC server, detection and control (e.g., start and stop) of a defined application may be reported from the MEC server to the PCRF without intervention of the Rx interface become. Accordingly, for example, in a situation where a plurality of MEC servers cooperate to provide a service (for example, cloud gaming or the like), it is possible to sequentially allocate resources such as the carrier from the MEC server to the PCRF to secure the QoS (for example, the delay, the guaranteed bandwidth, or the like) needed between the MEC servers.

In a case where there are a plurality of MMEs in the network, a plurality of MMEs may optionally share or refer to each other after an appropriate authentication process, the GW allocation list or the like in cooperation with each other. In addition, at this time, it is also possible to use the S10 interface currently specified in 3GPP. For example, illustrated 50A an example of the protocol stack in the communication between the MMEs.

<Evaluation>

The examples according to the present embodiment have been described above in detail.

According to the present embodiment, it is possible to implement the communication path between the servers (the MEC servers) installed in the wireless communication network that has not previously been specified while redirecting the existing network protocol for the MEC server as much as possible without modifying the existing network equipment.

Further, according to the present embodiment, it is possible to make a plurality of MEC servers cooperate with each other regardless of whether they are inside or outside the wireless communication network. Therefore, for example, the applications that have limitations in providing the service may provide the service to the user in a more appropriate form through the cooperation of the MEC servers. Also, since it is possible to cause a plurality of MEC servers having different computation resources to cooperate with each other, it is also possible to provide so-called distributed processing services over the wireless communication network.

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

Further, according to the present embodiment, it is possible to provide the EBS bearer specified in LTE to the inside of the MEC server for connection between the MEC servers. Accordingly, for example, the QoS mechanism in LTE can also be applied to communication between the MEC servers (eg, two-way communication).

Further, according to the present embodiment, it is possible to use both the software-defined network (SDN) / NFV mechanism and the existing 3GPP mechanism. Therefore, the present disclosure may be applied to, for example, the IoT network that is expected to be developed in the future, and a 5G network to be implemented in the future.

Further, according to the present embodiment, it is possible to implement the communication between the servers (between the MEC servers) without executing the DPI on all the packets, since the network function is virtualized by the SDN / NFV's VNF. Therefore, for example, it is possible to reduce the burden on the system associated with the execution of the DPI. Further, since it is not necessary to perform the DPI, the MEC server does not necessarily have to be installed between the network devices, and thus the MEC server can be more easily installed in the existing network.

Further, according to the present embodiment, for example, it is possible to authenticate and specify a connectable MEC server for each OTT providing a service (for example, to each service provider) by the MEC server by instructing the MEC server APN assigns and uses the mechanisms such as HSS, MME, PCRF and the like.

Further, according to the present embodiment, it is possible to use the EPS carrier which is an existing framework of 3GPP for each APN. Therefore, it is possible, for example, to provide suitable QoS for each service.

Further, according to the present embodiment, it is possible to acquire the information specifying the MEC server (for example, the APN or the like) using the service discovery function provided by the MEC platform. Therefore, for example, it is possible to set up the communication path between the MEC servers based on an instruction from the OSS, the UE or the application (for example, the application running on the MEC server) and the information of the application between the MEC servers to move. Further, with such a mechanism, for example, it is possible to provide the UE with a service from the MEC server having a more suitable environment (e.g., an environment in which the maximum delay, the guaranteed minimum band or the like is satisfied) even in can provide a situation in which the UE moves between the cells.

Further, according to the present embodiment, it is possible to perform the billing and directory control for each application on the MEC server for each VM or for each container using the 3 GPP framework.

According to the present embodiment, since the access policy of each server (eg, for each MEC server), each VM, or each container (ie, each APN) is registered in the HSS, it is possible to control access at the time of roaming at the time of local breakout to implement the server.

Further, the example in which the MME sets the MEC carrier between the MEC servers operated in the eNB, the DeNB, the RN, or the like for a Wireless Communication Access Accommodation Network of LTE has been described above. Further, an application target of the present embodiment is not necessarily limited to the Wireless Communication Access Accommodation Network of LTE. For example, the APN is applicable not only to the name of the P-GW, but also, for example, to a GPRS support node (GGSN). Therefore, the present embodiment can also be applied, for example, to a system in which the GGSN is used.

As a more specific example, the present embodiment may be applied to a so-called Wireless Communication Access Accommodation Network of 3G. For example 50B a diagram illustrating an example of an EPC network architecture. As in 50B represented, the SGSN of the Wireless Communication Access Accommodation Network of 3G plays a role similar to the MME in the Wireless Communication Access Accommodation Network of LTE. Therefore, for example, the SGSN may generate the GW allocation list based on information recorded and managed in the HSS and set the MEC carrier between the MEC servers operating on the RNC and the Node B based on the GW allocation list ,

<< Examples >>

The technology according to the present disclosure can be applied to various products. For example, the MEC server 300 or the application server 60 be realized as a server of any type such as a tower server, a rack server, a blade server or the like. In addition, at least part of the components of the MEC server 300 or the application server 60 in a module mounted in a server (eg, an integrated circuit module configured in a chip, card, or blade inserted into a slot of a blade server).

Furthermore, the MEC server can 300 be implemented as any kind of Evolved Node B (eNB), for example as a macro eNB, a small eNB or the like. A small eNB may be an eNB covering a smaller cell than a macrocell, such as a pico eNB, a micro eNB, or a home (femto) nNB. Alternatively, the MEC server 300 be implemented as another type of base station, such as a Node B or a base transceiver station (BTS). The MEC server 300 may include a main body that controls wireless communication (also referred to as a base station device) and one or more remote radio heads (RRHs) located at a location other than the main body. In addition, various types of terminals described below may be considered the MEC server 300 operate by performing the base station function temporarily or semi-permanently. Furthermore, at least a part of components of the MEC server 300 be implemented in the base station device or a module for the base station device.

In addition, the MEC server can 300 for example, as a mobile terminal such as a smart phone, a tablet personal computer (PC), a notebook PC, a portable game terminal, a portable / dongleartiger mobile router or a digital camera or an in-vehicle terminal, such as a car navigation device or the like may be implemented. Furthermore, the MEC server can 300 in surveillance cameras, gateway terminals of various sensor devices, vehicles for implementing means of movement such as cars, buses, trains or aircraft or the like as a terminal (also referred to as machine type communication (MTC) terminal), which is a machine-to-machine communication ( M2M). Furthermore, at least part of the components of the MEC server 300 in a module mounted in such a terminal (for example, an IC module configured in a chip).

<Application example regarding server>

51 FIG. 10 is a block diagram showing an example of a schematic configuration of a server 700 to which the technology of the present disclosure can be applied. The server 700 includes a processor 701, a main memory 702, a memory 703, a network interface 704, and a bus 706.

The processor 701 may be, for example, a central processing unit (CPU) or a digital signal processor (DSP) and control various functions of the server 700. Main memory 702 includes random access memory (RAM) and read only memory (ROM) and stores programs executed by processor 701 and data. The memory 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 wireless access point 700 to a wired communication network 705. The wired communication network 705 may be a core network such as an evolved packet core (EPC) or a packet data network (PDN) such as the Internet.

Bus 706 interconnects processor 701, main memory 702, memory 703, and network interface 704. The bus 706 may have two or more buses operating at different speeds (eg, a high speed bus and a low speed bus).

In the server 700, the in 51 can represent one or more components included in the MEC server 300 contained by reference to 11 (the MEC platform 331, the VNF 333 and / or the service providing unit 335) are implemented by the processor 701. For example, a program may cause a processor as the one or more components (ie, a program to cause a processor to run one or more of the processes Components) may be installed in the server 700 and the processor 701 may execute the program. As another example, a module including processor 701 and memory 702 may be mounted in server 700, and the one or more components may be implemented by the module. In this case, the module may store a program to cause a processor to function as the one or more components in main memory 702, and the program may be executed by processor 701. The server 700 or module may be provided as devices having the one or more components described above, as described above, or 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.

In the server 700, the in 51 can represent one or more components in the application server 60 are included with reference to 12 is described (the service delivery unit 64 ) can be implemented by the processor 701. For example, a program for causing a processor as the one or more components (ie, a program to cause a processor to perform operations of the one or more components) may be installed in the server 700, and the processor 701 may program To run. As another example, a module including processor 701 and memory 702 may be mounted in server 700, and the one or more components may be implemented by the module. In this case, the module may store a program to cause a processor to function as the one or more components in main memory 702, and the program may be executed by processor 701. The server 700 or module may be provided as devices having the one or more components described above, as described above, or 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.

<Example of use with base station>

(First application example)

52 FIG. 10 is a block diagram showing a first example of a schematic configuration of an eNB to which the technology of the present disclosure can be applied. An eNB 800 has one or more antennas 810 and a base station device 820. Each antenna 810 and the base station device 820 may be connected to each other via an RF cable.

Each of the antennas 810 has a single or multiple antenna elements (such as a plurality of antenna elements included in a MIMO antenna) and is used for the base station device 820 for transmitting and receiving radio signals. The eNB 800 may include the plurality of antennas 810, as in FIG 52 shown. For example, the multiple antennas 810 may be compatible with multiple frequency bands used by the eNB 800. Although 52 Illustrating the example in which the eNB 800 has the multiple antennas 810, the eNB 800 may also include a single antenna 810.

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

The processor 821 may be, for example, a CPU or a DSP, and controls various higher layer functions of the base station device 820. For example, the controller 821 generates a data packet of data in signals processed by the wireless communication interface 825 and transmits the generated packet via the network interface 823. The controller 821 may bundle data from multiple baseband processors to generate the bundled packet and transmit the generated bundled packet. The controller 821 may include logic functions for performing control such as radio resource control, radio bearer control, mobility management, access control, and scheduling. The controller may be executed in cooperation with an eNB or a core network node nearby. The main memory 822 includes a RAM and a ROM, and stores a program executed by the controller 821 and various types of control data (such as a terminal list, transmission power data, and scheduling data).

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

The wireless communication interface 825 supports any cellular communication scheme, such as Long Term Evolution (LTE) and LTE Advanced, and provides a radio connection to a terminal positioned in a cell of the eNB 800 via the antenna 810. The wireless communication interface 825 may typically include, for example, a baseband (BB) processor 826 and an RF circuit 827. For example, BB processor 826 may perform encoding / decoding, modulating / demodulating, and multiplexing / demultiplexing, and performs various types of signal processing of layers (such as L1, Media Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP)) , The BB processor 826 may have some or all of the logic functions described above in place of the controller 821. The BB processor 826 may be a memory storing a communication control program or a module having a processor and associated circuitry configured to execute the program. Updating the program may allow the functions of BB processor 826 to be changed. The module may be a card or a blade inserted into a slot of the base station device 820. Alternatively, the module may be a chip mounted on the card or blade. Meanwhile, the RF circuit 827 may include, for example, a mixer, a filter, and an amplifier, and transmits and receives radio signals via the antenna 810.

The wireless communication interface 825 may include the plurality of BB processors 826, as in FIG 52 shown. For example, the multiple BB processors 826 may be compatible with multiple frequency bands used by the eNB 800. The wireless communication interface 825 may include the plurality of RF circuits 827, as in FIG 52 shown. For example, the multiple RF circuits 827 may be compatible with multiple antenna elements. Although 52 For example, where wireless communication interface 825 includes multiple BB processors 826 and multiple RF circuits 827, wireless communication interface 825 may also include a single BB processor 826 or a single RF circuit 827.

In the eNB 800, which is in 52 can represent one or more components included in the MEC server 300 (the MEC platform 331, the VNF 333 and / or the service providing unit 335) included with respect to 11 described by the wireless communication interface 825. Alternatively, at least some of these components may be implemented by the controller 821. For example, a module having a portion (eg, the BB processor 826) or the entire wireless communication interface 825 and / or the controller 821 may be mounted in the eNB 800, and the one or more components may be from the module be implemented. In this case, the module may store a program to cause the processor to function as the one or more components (ie, a program to cause the processor to perform operations of the one or more components) and execute the program , As another example, the program may cause the processor to function as the one or more components in which eNB 800 may be installed, and wireless communication interface 825 (eg, BB processor 826) and / or controller 821 run the program. As described above, the eNB 800, the base station device 820, or the module may be provided as one device having the one or more components, and the program for causing the processor to function as the one or more components may be provided become. In addition, a readable recording medium in which the program is recorded may be provided.

(Second example of use)

53 FIG. 10 is a block diagram showing a second example of a schematic configuration of an eNB to which the technology of the present disclosure can be applied. An eNB 830 includes one or more antennas 840, a base station device 850 and an RRH 860. Each antenna 840 and the RRH 860 may be connected to each other via an RF cable. The base station apparatus 850 and the RRH 860 may 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 multiple antenna elements (such as a plurality of antenna elements included in a MIMO antenna) and is used for the RRH 860 for transmitting and receiving radio signals. The eNB 830 may include the plurality of antennas 840, as in FIG 53 shown. For example, the multiple antennas 840 may be compatible with multiple frequency bands used by the eNB 830. Although 53 Illustrating the example in which the eNB 830 has the multiple antennas 840, the eNB 830 may also include a single antenna 840.

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

The wireless communication interface 855 supports any cellular communication scheme such as LTE and LTE-Advanced, and provides wireless communication to a terminal positioned in a sector corresponding to the RRH 860 via the RRH 860 and the antenna 840. The wireless communication interface 855 may typically include, for example, a BB processor 856. 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 via the connection interface 857 to the RF circuit 864 of the RRH 860. The wireless communication interface 855 may include the plurality of BB processors 856, as in FIG 53 shown. For example, the multiple BB processors 856 may be compatible with multiple frequency bands used by the eNB 830. Although 53 For example, where the wireless communication interface 855 includes the multiple BB processors 856, the wireless communication interface 855 may also 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 also be a communication module for communication in the high-speed line described above, the base station device 850 (wireless communication interface 855) with the RRH 860 combines.

The RRH 860 has 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 also be a communication module for communication in the high-speed line described above.

The wireless communication interface 863 transmits and receives radio signals via the antenna 840. The wireless communication interface 863 may typically include the RF circuitry 864, for example. For example, the RF circuit 864 may include a mixer, a filter, and an amplifier, and transmits and receives radio signals via the antenna 840. The wireless communication interface 863 may include a plurality of RF circuits 864, as in FIG 53 shown. For example, the multiple RF circuits 864 may support multiple antenna elements. Although 53 For example, where wireless communication interface 863 includes multiple RF circuits 864, wireless communication interface 863 may include a single RF circuit 864.

In the eNB 830, the in 53 can represent one or more components included in the MEC server 300 (the MEC platform 331, the VNF 333 and / or the service providing unit 335) included in relation to 11 described be implemented by the wireless communication interface 855 and / or the wireless communication interface 863. Alternatively, at least some of these components may be implemented by the controller 851. For example, a module having a portion (eg, the BB processor 856) or the entire wireless communication interface 855 and / or the controller 851 may be mounted in the eNB 830, and the one or more components may be from the module be implemented. In this case, the module may store a program to cause the processor to function as the one or more components (ie, a program to cause the processor to perform operations of the one or more components) and execute the program , As another example, the program may cause the processor to function as the one or more components in which eNB 830 may be installed, and wireless communication interface 855 (eg, BB processor 856) and / or controller 851 run the program. As described above, the eNB 830, the base station device 850 or the module may be provided as a device having the one or more components and the program for causing the 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.

<Application example relating to terminal>

(First application example)

54 FIG. 10 is a block diagram showing an example of a schematic configuration of a smartphone 900 to which the technology of the present disclosure can be applied. Smartphone 900 includes processor 901, main memory 902, memory 903, external connection interface 904, camera 906, sensor 907, microphone 908, input device 909, display 910, speaker 911, 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.

The processor 901 may be, for example, a CPU or a system-on-a-chip (SoC), and controls functions of an application layer and other layers of the smartphone 900. The memory 902 includes a RAM and a ROM and stores a program executed by the Processor 901 is executed, and data. The memory 903 may include a storage medium such as a semiconductor memory and a hard disk. The external connection interface 904 is an interface for connecting an external device such as a memory card and a universal serial bus (USB) device to the smartphone 900.

The camera 906 has an image sensor such as a charge-coupled device (CCD) and a complementary metal-oxide semiconductor (CMOS), and takes a captured image. The sensor 907 may include a group of sensors, such as a measurement sensor, a gyrosensor, a geomagnetic sensor, and an acceleration sensor. The microphone 908 converts sounds input to the smartphone 900 into audio signals. The input device 909 includes, for example, a touch sensor configured to detect touches on a screen of the display device 910, a key pad, a keyboard, a knob, or a switch to receive a workflow or information input from a user. The display device 910 has a screen such as a liquid crystal display (LCD) or an OLED (Organic Light Emitting Diode) display for displaying output images of the smartphone 900. The speaker 911 converts audio signals output from the smartphone 900 into sound.

The wireless communication interface 912 supports any cellular communication scheme such as LTE and LTE-Advanced, and performs wireless communication. The wireless communication interface 912 may typically include, for example, a BB processor 913 and an RF circuit 914. The BB processor 913 may perform, for example, encoding / decoding, modulating / demodulating, and multiplexing / demultiplexing, and executes various types of signal processing for wireless communication. Meanwhile, the RF circuit 914 may include, for example, a mixer, a filter and an amplifier, and transmits and receives radio signals via the antenna 916. The wireless communication interface 912 may also be a one-chip module on which the BB processor 913 and the RF circuit 914 are integrated. The wireless communication interface 912 may include the plurality of BB processors 913 and the plurality of RF circuits 914, as in FIG 54 shown. Although 54 For example, where wireless communication interface 912 includes multiple BB processors 913 and multiple RF circuits 914, wireless communication interface 912 may also include a single BB processor 913 or a single RF circuit 914.

Further, in addition to a cellular communication scheme, the wireless communication interface 912 may support another type of wireless communication scheme, such as a short distance wireless communication scheme, a near field communication scheme, and a wireless local area network (LAN) scheme. In this case, the wireless communication interface 912 may include the BB processor 913 and the RF circuitry 914 for each wireless communication scheme.

Each of the antenna switches 915 switches connection destinations of the antennas 916 between a plurality of circuits (such as circuits for different wireless communication schemes) included in the wireless communication interface 912.

Each of the antennas 916 has a single or multiple antenna elements (such as a plurality of antenna elements included in a MIMO antenna) and is used for the wireless communication interface 912 for transmitting and receiving radio signals. The smartphone 900 may include the plurality of antennas 916, as in FIG 54 shown. Although 54 Illustrating the example in which the smartphone 900 has the plurality of antennas 916, the smartphone 900 may also include a single antenna 916.

Further, the smartphone 900 may include the antenna 916 for each wireless communication scheme. In this case, the antenna switches 915 in the configuration of the smartphone 900 may be omitted.

The bus 917 connects the processor 901, the main memory 902, the memory 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 control 919 with each other. The battery 918 supplies power to 54 illustrated blocks of the smartphone 900 via power supply lines, which are partially shown by dashed lines in the figure. The auxiliary controller 919 operates a minimum necessary function of the smartphone 900, for example, in a sleep mode.

In the smartphone 900, which in 54 can represent one or more components included in the MEC server 300 (the MEC platform 331, the VNF 333 and / or the service providing unit 335) included in relation to 11 described by the wireless communication interface 912. Alternatively, at least some of these components may be implemented by the processor 901 or the auxiliary controller 919. For example, a module that includes a portion (eg, the BB processor 913) or the entire wireless communication interface 912, the processor 901, and / or the auxiliary controller 919 may be mounted in the smartphone 900 and the one or more components can be implemented by the module. In this case, the module may store a program to cause the processor to function as the one or more components (ie, a program to cause the processor to perform operations of the one or more components) and execute the program , As another example, the program may be installed in the smartphone 900 to cause the processor to function as the one or more components and the wireless communication interface 912 (eg, the BB processor 913), the processor 901, and / or the auxiliary controller 919 may execute the program. As described above, the smartphone 900 or module may be provided as a device having the one or more components, and the program for causing the 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 example of use)

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

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

The GPS module 924 uses GPS signals received from a GPS satellite to measure a position (such as latitude, longitude, and altitude) of the car navigation device 920. The sensor 925 may include a group of sensors, such as a gyrosensor, a geomagnetic sensor, and a barometric sensor. For example, the data interface 926 is connected to an in-vehicle network 941 via a terminal, not shown, and acquires data generated by the vehicle, such as vehicle speed data.

The content player 927 reproduces content stored in a storage medium (for example, a CD and a DVD) inserted in the storage media interface 928. For example, the input device 929 includes a touch sensor configured to detect touches on a screen of the display device 930, a button or a switch, and receives a workflow or information input from a user. The display device 930 has a screen, such as an LCD or an OLED display, and displays an image of the navigation function or reproduced content. The speaker 931 outputs sounds of the navigation function or reproduced content.

The wireless communication interface 933 supports any cellular communication scheme such as LET and LTE-Advanced, and performs wireless communication. The wireless communication interface 933 may typically include, for example, a BB processor 934 and an RF circuit 935. The BB processor 934 may perform, for example, encoding / decoding, modulating / demodulating, and multiplexing / demultiplexing, and executes various types of signal processing for wireless communication. Meanwhile, the RF circuit 935 may include, for example, a mixer, a filter and an amplifier, and transmits and receives radio signals via the antenna 937. The wireless communication interface 933 may be a one-chip module on which the BB processor 934 and the RF Circuit 935 are integrated. The wireless communication interface 933 may include the plurality of BB processors 934 and the plurality of RF circuits 935, as in FIG 55 shown. Although 55 For example, where the wireless communication interface 933 includes the multiple BB processors 934 and the multiple RF circuits 935, the wireless communication interface 933 may also include a single BB processor 934 or a single RF circuit 935.

Further, in addition to a cellular communication scheme, the wireless communication interface 933 may support another type of wireless communication scheme, such as a short distance wireless communication scheme, a near field communication scheme, and a wireless LAN scheme. In this case, the wireless communication interface 933 may include the BB processor 934 and the RF circuitry 935 for each wireless communication scheme.

Each of the antenna switches 936 switches connection destinations of the antennas 937 between a plurality of circuits (such as circuits for different wireless communication schemes) included in the wireless communication interface 933.

Each of the antennas 937 has a single or multiple antenna elements (such as a plurality of antenna elements included in a MIMO antenna) and is used for the wireless communication interface 933 for transmitting and receiving radio signals. The car navigation device 920 may include the plurality of antennas 937, as in FIG 55 shown. Although 55 For example, in which the car navigation device 920 has the plurality of antennas 937, the car navigation device 920 may include a single antenna 937.

Further, the vehicle navigation device 920 may include the antenna 937 for each wireless communication scheme. In this case, the antenna switches 936 may be omitted from the configuration of the car navigation device 920.

The battery 938 supplies power to 55 illustrated blocks of the car navigation device 920 via power supply lines, which are partially shown by dashed lines in the figure. The battery 938 accumulates power supplied by the vehicle.

In the car navigation device 920 included in 55 can represent one or more components included in the MEC server 300 (the MEC platform 331, the VNF 333 and / or the service providing unit 335) included in relation to 11 described be implemented by the wireless communication interface 933. Alternatively, at least some of these components may be implemented by the processor 921. For example, a module having a portion (eg, the BB processor 934) or the entire wireless communication interface 933 and / or the processor 921 may be mounted in the car navigation device 920, and the one or more components may be from the module be implemented. In this case, the module may store a program to cause the processor to function as the one or more components (ie, a program to cause the processor to perform operations of the one or more components) and execute the program , As another example, the program may be installed in the car navigation device 920 to cause the processor to function as the one or more components, and the wireless communication interface 933 (eg, the BB processor 934), the processor 921 can run the program. As described above, the car navigation device 920 or module may be provided as a device having the one or more components, and the program for causing the 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.

The technology of the present disclosure may also be implemented as an in-vehicle system (or vehicle) 940 including one or more blocks of the car navigation device 920, the in-vehicle network 941, and a vehicle module 942. In other words, the in-vehicle system (or vehicle) 940 may be provided as a device having the MEC platform 331, the VNF 333, and / or the service providing unit 335. The vehicle module 942 generates vehicle data such as vehicle speed, engine speed, and error information, and outputs the generated data to the in-vehicle network 941.

. "6 Conclusion"

An embodiment of the present disclosure is described above with reference to FIG 1 to 55 has been described in detail. As described above, the MME captures 43 According to the present embodiment, a connection request assigned to an APN indicating a connection destination. Then put the MME 43 identify a carrier between a request source of the connection request and a server designated by the APN to which the connection request is assigned based on management information in which the APN is assigned to a gateway that is in connection with that of the APN designated server is passed. With such a configuration, it is according to the system 1 According to the present embodiment, it is possible to set the communication path between the servers in MEC (ie, between the MEC servers) in a more appropriate form.

The preferred embodiment (s) of the present disclosure has been described above with reference to the accompanying drawings, although the present disclosure is not limited to the above examples. A person skilled in the art may find various changes and modifications within the scope of the appended claims, and it should be understood that they will, of course, be within the technical scope of the present disclosure.

Furthermore, the effects described in this specification are merely illustrative or exemplary effects and are not limiting. That is, with or instead of the above effects, the technology according to the present disclosure can achieve other effects that will be apparent to those skilled in the art from the description of this specification.

1. (1) Vorrichtung, die Folgendes aufweist:
   • eine Erfassungseinheit, die konfiguriert ist, eine Verbindungsanfrage zu erfassen, die einem Zugangspunktnamen (Access Point Name - APN) zugewiesen ist, der ein Verbindungsziel angibt; und
   • eine Steuereinheit, die konfiguriert ist, einen Träger zwischen einer Anfragequelle der Verbindungsanfrage und einem Server, der von dem APN bezeichnet wird, dem die Verbindungsanfrage zugewiesen ist, auf der Grundlage von Verwaltungsinformationen festzulegen, in denen der APN einem Gateway zugewiesen ist, das bei Herstellen einer Verbindung mit dem von dem APN bezeichneten Server passiert wird.
   • (2) Vorrichtung nach (1), wobei die Steuereinheit mindestens ein Gateway, das bei Herstellen einer Verbindung mit dem Server passiert wird, der von dem APN bezeichnet wird, dem die Verbindungsanfrage zugewiesen ist, auf der Grundlage der Verwaltungsinformationen spezifiziert, und die Steuereinheit einen Träger zwischen jeweils zwei der Anfragequelle, des Servers und des mindestens einen spezifizierten Gateways festlegt.
   • (3) Vorrichtung nach (2), wobei die Steuereinheit als ein virtueller Träger, der die Anfragequelle mit dem Server verbindet, eine Reihe von Trägern festlegt, die zwischen den jeweils zwei der Anfragequelle, des von dem APN bezeichneten Servers und des Gateways, das bei Herstellen der Verbindung mit dem Server passiert wird, festgelegt ist.
   • (4) Vorrichtung nach (2) oder (3), wobei der von dem APN bezeichnete Server ein virtueller Server ist, der auf einem physischen Server eines mobilen Kommunikationsnetzwerks betrieben wird, die Steuereinheit ein erstes Gateway in dem mobilen Kommunikationsnetzwerk, das beim Herstellen einer Verbindung mit dem physischen Server passiert wird, auf dem der von dem APN bezeichnete virtuelle Server betrieben wird, und ein virtuelles zweites Gateway zum Herstellen einer Verbindung zwischen dem physischen Server und dem virtuellen Server als das mindestens eine Gateway auf der Grundlage der Verwaltungsinformationen spezifiziert, und die Steuereinheit einen Träger zwischen mindestens jeweils zwei des spezifizierten ersten Gateways, des physischen Servers, des spezifizierten zweiten Gateways und des virtuellen Servers festlegt.
   • (5) Vorrichtung nach einem von (1) bis (4), wobei der APN dem Server zugewiesen ist; und die Steuereinheit einen Träger zwischen der Anfragequelle der Verbindungsanfrage und dem Server, der von dem APN angegeben wird, dem die Verbindungsanfrage zugewiesen ist, auf der Grundlage der Verwaltungsinformationen festlegt.
   • (6) Vorrichtung nach einem von (1) bis (4), wobei der APN einer Anwendung zugewiesen ist, die auf dem von dem APN bezeichneten Server betrieben wird, die Erfassungseinheit die Verbindungsanfrage erfasst, in der dem APN Identifikationsinformationen zum Spezifizieren der Anwendung zugewiesen sind, die auf dem Server betrieben wird, und die Steuereinheit einen Träger zwischen dem Server, der von dem APN bezeichnet wird, dem die Verbindungsanfrage zugewiesen ist, und der Anwendung, die von dem APN angegeben ist, auf der Grundlage der Identifikationsinformationen festlegt.
   • (7) Vorrichtung nach einem von (1) bis (4), wobei der APN einem Dienstanbieter zugewiesen ist; und die Steuereinheit den Träger zwischen der Anfragequelle und dem Server, durch den der Anbieter, der von dem APN angegeben wird, dem die Verbindungsanfrage zugewiesen ist, den Dienst bereitstellt, auf der Grundlage der Verwaltungsinformationen festlegt.
   • (9) Vorrichtung nach einem von (1) bis (4), wobei der APN einer Anwendung einer virtuellen Maschine zugewiesen ist, die auf dem von dem APN bezeichneten Server betrieben wird, die Erfassungseinheit die Verbindungsanfrage erfasst, in der dem APN Identifikationsinformationen zum Spezifizieren der virtuellen Maschine zugewiesen sind, die auf dem Server betrieben wird, und die Steuereinheit einen Träger zwischen dem von Server, der von dem APN bezeichnet wird, dem die Verbindungsanfrage zugewiesen ist, und der virtuellen Maschine, die von dem APN angegeben ist, auf der Grundlage der Identifikationsinformationen festlegt.
   • (9) Vorrichtung nach einem von (1) bis (4), wobei der APN einem Container zugewiesen ist, der auf dem von dem APN bezeichneten Server betrieben wird, die Erfassungseinheit die Verbindungsanfrage erfasst, in der dem APN Identifikationsinformationen zum Spezifizieren des Containers zugewiesen sind, der auf dem Server betrieben wird, und die Steuereinheit einen Träger zwischen dem Server, der von dem APN bezeichnet wird, dem die Verbindungsanfrage zugewiesen ist, und dem Container, der von dem APN angegeben ist, auf der Grundlage der Identifikationsinformationen festlegt.
   • (10) Vorrichtung nach einem von (1) bis (9), wobei die Steuereinheit einen Typ eines Trägers steuert, der für jeden APN festgelegt werden soll.
   • (11) Vorrichtung nach einem von (1) bis (10), wobei die Steuereinheit selektiv eine Verbindung zu dem von dem APN spezifizierten Server für jeden APN beschränkt.
   • (12) Vorrichtung, die Folgendes aufweist:
     • eine Übertragungseinheit, die konfiguriert ist, eine Verbindungsanfrage, die einem Zugangspunktnamen (Access Point Name - APN) zugewiesen ist, der ein Verbindungsziel angibt, an eine externe Vorrichtung zu übertragen; und
     • eine Verarbeitungseinheit, die konfiguriert ist, eine Kommunikation mit einem Server, der von dem APN bezeichnet wird, über einen Träger, der zum Herstellen einer Verbindung mit dem Server festgelegt ist, der von dem APN bezeichnet wird, dem die Verbindungsanfrage zugewiesen ist, auf der Grundlage von Verwaltungsinformationen auszuführen, in denen der APN einem Gateway zugewiesen ist, das bei Herstellen einer Verbindung mit dem Server passiert wird.
   • (13) Verfahren, das Folgendes aufweist:
     • Erfassen einer Verbindungsanfrage, die einem Zugangspunktnamen (Access Point Name - APN) zugewiesen ist, der ein Verbindungsziel angibt; und
     • Festlegen, von einem Prozessor, eines Trägers zwischen einer Anfragequelle der Verbindungsanfrage und einem Server, der von dem APN bezeichnet wird, dem die Verbindungsanfrage zugewiesen ist, auf der Grundlage von Verwaltungsinformationen, in denen der APN einem Gateway zugewiesen ist, das bei Herstellen einer Verbindung mit dem von dem APN bezeichneten Server passiert wird.
   • (14) Verfahren, das Folgendes aufweist:
     • Übertragen einer Verbindungsanfrage, die einem Zugangspunktnamen (Access Point Name - APN) zugewiesen ist, der ein Verbindungsziel angibt, an eine externe Vorrichtung; und
     • Ausführen, von einem Prozessor, einer Kommunikation mit einem Server, der von dem APN bezeichnet wird, über einen Träger, der zum Herstellen einer Verbindung mit dem Server, der von dem APN bezeichnet wird, dem die Verbindungsanfrage zugewiesen ist, festgelegt ist, auf der Grundlage von Verwaltungsinformationen, in denen der APN einem Gateway zugewiesen ist, das bei Herstellen einer Verbindung mit dem Server passiert wird.
   • (15) Ein Programm, das bewirkt, dass ein Computer Folgendes ausführt:
     • Erfassen einer Verbindungsanfrage, die einem Zugangspunktnamen (Access Point Name - APN) zugewiesen ist, der ein Verbindungsziel angibt; und
     • Festlegen eines Trägers zwischen einer Anfragequelle der Verbindungsanfrage und einem Server, der von dem APN bezeichnet wird, dem die Verbindungsanfrage zugewiesen ist, auf der Grundlage von Verwaltungsinformationen, in denen der APN einem Gateway zugewiesen ist, das bei Herstellen einer Verbindung mit dem von dem APN bezeichneten Server passiert wird.
   • (16) Ein Programm, das bewirkt, dass ein Computer Folgendes ausführt:
     • Übertragen einer Verbindungsanfrage, die einem Zugangspunktnamen (Access Point Name - APN) zugewiesen ist, der ein Verbindungsziel angibt, an eine externe Vorrichtung; und
     • Ausführen einer Kommunikation mit einem Server, der von dem APN bezeichnet wird, über einen Träger, der zum Herstellen einer Verbindung mit dem Server, der von dem APN bezeichnet wird, dem die Verbindungsanfrage zugewiesen ist, festgelegt ist, auf der Grundlage von Verwaltungsinformationen, in denen der APN einem Gateway zugewiesen ist, das bei Herstellen einer Verbindung mit dem Server passiert wird.

In addition, the present technology may also be configured as described below.

1. (1) Apparatus comprising:
   • a detection unit configured to detect a connection request assigned to an access point name (APN) indicating a connection destination; and
   • a control unit configured to set a bearer between a request source of the connection request and a server designated by the APN to which the connection request is assigned based on management information in which the APN is assigned to a gateway when made a connection with the server designated by the APN.
   • (2) Device according to ( 1 ), wherein the control unit specifies at least one gateway that is passed upon establishing a connection with the server designated by the APN to which the connection request is assigned based on the management information, and the control unit specifies a carrier between every two of the request source , the server and the at least one specified gateway.
   • (3) The device according to (2), wherein the control unit, as a virtual bearer connecting the request source to the server, specifies a series of bearers connecting between each two of the request source, the server designated by the APN, and the gateway when the connection to the server is made.
   • (4) The apparatus according to (2) or (3), wherein the server designated by the APN is a virtual server operating on a physical server of a mobile communication network, the control unit having a first gateway in the mobile communication network when establishing a Connection is made with the physical server on which the virtual server designated by the APN is operated, and specifies a virtual second gateway for establishing a connection between the physical server and the virtual server as the at least one gateway based on the management information, and the controller determines a carrier between at least two of each of the specified first gateway, the physical server, the specified second gateway, and the virtual server.
   • (5) Device according to one of ( 1 ) to (4), wherein the APN is assigned to the server; and the control unit specifies a bearer between the request source of the connection request and the server designated by the APN to which the connection request is assigned based on the management information.
   • (6) Device according to one of 1 ) to (4), wherein the APN is assigned to an application operating on the server designated by the APN, the detection unit detects the connection request in which the APN is assigned identification information for specifying the application operating on the server, and the control unit specifies a bearer between the server designated by the APN to which the connection request is assigned and the application specified by the APN based on the identification information.
   • (7) Device according to one of 1 ) to (4), wherein the APN is assigned to a service provider; and the control unit determines the carrier between the request source and the server by which the provider designated by the APN to which the connection request is assigned provides the service based on the management information.
   • (9) Device according to one of 1 ) to (4), wherein the APN is assigned to a virtual machine application operating on the server designated by the APN, the detection unit detects the connection request in which the APN is assigned identification information for specifying the virtual machine that is located on the APN Server, and the control unit specifies a carrier between that of the server designated by the APN to which the connection request is assigned and the virtual machine specified by the APN based on the identification information.
   • (9) Device according to one of 1 ) to (4), wherein the APN is assigned to a container operated on the server designated by the APN, the detection unit detects the connection request in which the APN is assigned identification information for specifying the container operated on the server, and the control unit specifies a bearer between the server designated by the APN to which the connection request is assigned and the container designated by the APN based on the identification information.
   • (10) Device according to one of 1 ) to (9), wherein the control unit controls a type of a carrier to be set for each APN.
   • (11) Device according to one of 1 ) to ( 10 ), wherein the control unit selectively limits a connection to the server specified by the APN for each APN.
   • (12) Apparatus comprising:
     • a transmission unit configured to transmit a connection request assigned to an access point name (APN) indicating a connection destination to an external device; and
     • a processing unit configured to communicate with a server designated by the APN via a bearer established to establish a connection with the server designated by the APN to which the connection request is assigned, on the Based on management information in which the APN is assigned to a gateway that will be passed when connecting to the server.
   • (13) A method comprising:
     • Detecting a connection request assigned to an access point name (APN) indicating a connection destination; and
     • Determining, by a processor, a carrier between a request source of the connection request and a server designated by the APN to which the connection request is assigned based on management information in which the APN is assigned to a gateway when establishing a connection with the server designated by the APN.
   • (14) Method comprising:
     • Transmitting a connection request assigned to an access point name (APN) indicating a connection destination to an external device; and
     • Executing, by a processor, communication with a server designated by the APN via a bearer established to connect to the server designated by the APN to which the connection request is assigned, on the Based on management information in which the APN is assigned to a gateway that will be passed when connecting to the server.
   • (15) A program that causes a computer to do the following:
     • Detecting a connection request assigned to an access point name (APN) indicating a connection destination; and
     • Specifying a bearer between a request source of the connection request and a server designated by the APN to which the connection request is assigned based on management information in which the APN is assigned to a gateway that is in connection with that of the APN designated server is passed.
   • (16) A program that causes a computer to do the following:
     • Transmitting a connection request assigned to an access point name (APN) indicating a connection destination to an external device; and
     • Performing a communication with a server designated by the APN via a bearer set to make a connection with the server designated by the APN to which the connection request is assigned, based on management information the APN is assigned to a gateway that will be passed when connecting to the server.

LIST OF REFERENCE NUMBERS

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 entity

100

wireless communication device

200

terminal

300

MEC server

310

communication unit

320

storage unit

330

processing unit

QUOTES INCLUDE IN THE DESCRIPTION

This list of the documents listed by the applicant has been generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Cited patent literature

• AP 100 C [0057]

Claims (16)

Apparatus comprising: a detection unit configured to detect a connection request assigned to an access point name (APN) indicating a connection destination; and a control unit configured to set a bearer between a request source of the connection request and a server designated by the APN to which the connection request is assigned based on management information in which the APN is assigned to a gateway when made a connection with the server designated by the APN. Device after Claim 1 wherein the control unit specifies at least one gateway that is passed upon establishing the connection with the server designated by the APN to which the connection request is assigned based on the management information, and the control unit carries a carrier between every two of the request source; of the server and the at least one specified gateway. Device after Claim 2 in that the control unit, as a virtual bearer connecting the request source to the server, specifies a number of bearers that pass between the two respective ones of the request source, the server designated by the APN, and the gateway that passes when connecting to the server is set. Device after Claim 2 wherein the server designated by the APN is a virtual server operating on a physical server of a mobile communication network, the control unit is a first gateway in the mobile communication network that is passed when establishing a connection with the physical server on which the operating the virtual server designated APN, and specifying a virtual second gateway for establishing a connection between the physical server and the virtual server as the at least one gateway based on the management information, and the control unit carries a carrier between at least two each of the specified first gateway , the physical server, the specified second gateway, and the virtual server. Device after Claim 1 wherein the APN is assigned to the server and the control unit specifies a bearer between the request source of the connection request and the server designated by the APN to which the connection request is assigned based on the management information. Device after Claim 1 wherein the APN is assigned to an application operating on the server designated by the APN, the capture unit detects the connection request, in which the APN is assigned identification information for specifying the application operating on the server, and the control unit is a bearer between the server designated by the APN to which the connection request is assigned and the application specified by the APN based on the identification information. Device after Claim 1 wherein the APN is assigned to a service provider, and the control unit determines the carrier between the request source and the server through which the provider designated by the APN to which the connection request is assigned provides the service based on the management information. Device after Claim 1 wherein the APN is assigned to a virtual machine operated on the server designated by the APN, the detection unit detects the connection request in which the APN is assigned identification information for specifying the virtual machine operated on the server, and the control unit specify a carrier between the server designated by the APN to which the connection request is assigned and the virtual machine specified by the APN based on the identification information. Device after Claim 1 wherein the APN is assigned to a container operated on the server specified by the APN, the detection unit detects the connection request in which the APN is assigned identification information for specifying the container operated on the server, and the control unit is a carrier between the server designated by the APN to which the connection request is assigned and the container specified by the APN, based on the identification information. Device after Claim 1 wherein the control unit controls a type of carrier to be set for each APN. Device after Claim 1 wherein the control unit selectively limits a connection to the server specified by the APN for each APN. Apparatus comprising: a transmission unit configured to transmit a connection request assigned to an access point name (APN) indicating a connection destination to an external device; and a processing unit configured to communicate with a server designated by the APN via a bearer established to establish a connection with the server designated by the APN to which the connection request is assigned, on the Based on management information in which the APN is assigned to a gateway that will be passed when connecting to the server. A method comprising: Detecting a connection request assigned to an access point name (APN) indicating a connection destination; and Determining, by a processor, a carrier between a request source of the connection request and a server designated by the APN to which the connection request is assigned based on management information in which the APN is assigned to a gateway when establishing a connection with the server designated by the APN. A method comprising: Transmitting a connection request assigned to an access point name (APN) indicating a connection destination to an external device; and Executing, by a processor, communication with a server designated by the APN via a bearer established to connect to the server designated by the APN to which the connection request is assigned, on the Based on management information in which the APN is assigned to a gateway that will be passed when connecting to the server. Program that causes a computer to do the following: Detecting a connection request assigned to an access point name (APN) indicating a connection destination; and Specifying a bearer between a request source of the connection request and a server designated by the APN to which the connection request is assigned based on management information in which the APN is assigned to a gateway that is in connection with that of the APN designated server is passed. Program that causes a computer to do the following: Transmitting a connection request assigned to an access point name (APN) indicating a connection destination to an external device; and Performing a communication with a server designated by the APN via a bearer set to make a connection with the server designated by the APN to which the connection request is assigned, based on management information the APN is assigned to a gateway that will be passed when connecting to the server.

Images