DE112016005741T5 - Device, method and program - Google Patents

Abstract

[Problem] Providing a mechanism for appropriately setting a route for transferring data to an edge server or for transferring data from an edge server. [Solution] A device has a processing unit configured to communicate using a server executing the first EPS bearer established between a packet data network gateway (P-GW) and a terminal and passing through an application server installed in an EPS and configured to provide content to the terminal or to acquire content from the terminal.

Description

Technical area

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

State of the art

In recent years, mobile edge computing (MEC) technology for performing data processing in a server (hereinafter also referred to as an edge server) has been attracting attention at a position physically close to a terminal such as a smart phone , For example, a standard of technology related to MEC is examined in Non-Patent Literature 1 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 3 September 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

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 only recently begun. For example, one technique for properly determining a route for transferring data to an edge server or for transferring data from an edge server is a technique that has not been sufficiently suggested.

the solution of the problem

According to the present disclosure, an apparatus is provided that includes a processing unit configured to perform communication using a first EPS carrier configured between a packet data network gateway (P-GW) and a terminal and passing through an application server, installed in an EPS and configured to provide content to the terminal or to capture content from the terminal.

In addition, according to the present disclosure, there is provided a method including executing, by a processor, communication using a first EPS bearer established between a packet data network gateway (P-GW) and a terminal and passing through an application server, installed in an EPS and configured to provide content to the terminal or to capture content from the terminal.

In addition, according to the present disclosure, there is provided a program that causes a computer to function as a processing unit configured to perform communication using a first EPS carrier connected between a packet data network gateway (P-GW) and a terminal is set up and passes through an application server installed in an EPS and configured to provide content to the terminal or to capture content from the terminal.

Advantageous effects of the invention

As described above, according to the present disclosure, there is provided a mechanism for appropriately setting a route for transferring data to an edge server or for transferring data from an edge server. 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 diagram illustrating an example of a schematic configuration of a system 1 according to an embodiment of the present disclosure.
• [ 2 ] 2 FIG. 13 is a diagram illustrating an example of a configuration of an LTE network in which MEC is not introduced.
• [ 3 ] 3 Fig. 10 is a block diagram illustrating an example of a configuration of a network in which MEC is introduced.
• [ 4 ] 4 Fig. 10 is a diagram illustrating an example of a configuration of an LTE network in which MEC is introduced.
• [ 5 ] 5 Figure 11 is a diagram illustrating an example of a data stream of DL cache data.
• [ 6 ] 6 Figure 12 is a diagram illustrating an example of a data stream of UL caching data.
• [ 7 ] 7 Fig. 10 is an explanatory diagram for describing a architecture of a carrier.
• [ 8th ] 8th Fig. 10 is an explanatory diagram for describing an architecture of an EPS carrier.
• [ 9 ] 9 Fig. 10 is an explanatory diagram for describing a UL ID and a DL ID set in a carrier;
• [ 10 ] 10 FIG. 14 is a sequence diagram illustrating an example of a flow of a process for setting up a standard carrier. FIG.
• [ 11 ] 11 FIG. 10 is a sequence diagram illustrating an example of a flow of a process for setting up a dedicated carrier. FIG.
• [ 12 ] 12 Fig. 10 is an explanatory diagram for describing a TFT.
• [ 13 ] 13 Fig. 10 is an explanatory diagram for describing a TFT in more detail.
• [ 14 ] 14 FIG. 10 is a block diagram illustrating an example of a logical configuration of a base station according to the embodiment. FIG.
• [ 15 ] 15 FIG. 10 is a block diagram illustrating an example of a logical configuration of a terminal according to the embodiment. FIG.
• [ 16 ] 16 FIG. 10 is a block diagram illustrating an example of a logical configuration of an MEC server according to the embodiment. FIG.
• [ 17 ] 17 FIG. 10 is an explanatory diagram for describing an MEC carrier according to a first embodiment. FIG.
• [ 18 ] 18 FIG. 10 is an explanatory diagram for describing an architecture of an MEC carrier according to the embodiment. FIG.
• [ 19 ] 19 FIG. 10 is a sequence diagram illustrating an example of an MEC carrier setup process according to the embodiment. FIG.
• [ 20 ] 20 FIG. 10 is a sequence diagram illustrating an example of an MEC carrier setup process according to the embodiment. FIG.
• [ 21 ] 21 Fig. 10 is an explanatory diagram for describing a carrier allocation by a TFT according to a second embodiment.
• [ 22 ] 22 FIG. 10 is an explanatory diagram for describing an example of a user traffic copying process according to the embodiment. FIG.
• [ 23 ] 23 FIG. 10 is an explanatory diagram for describing an example of a user traffic copying process according to the embodiment. FIG.
• [ 24 ] 24 FIG. 10 is an explanatory diagram for describing an architecture of an MEC carrier according to a third embodiment. FIG.
• [ 25 ] 25 FIG. 10 is a sequence diagram illustrating an example of an MEC carrier setup process according to the embodiment. FIG.
• [ 26 ] 26 Fig. 10 is a block diagram illustrating an example of a schematic configuration of a server.
• [ 27 ] 27 FIG. 12 is a block diagram illustrating a first example of a schematic configuration of an eNB. FIG.
• [ 28 ] 28 FIG. 12 is a block diagram illustrating a second example of a schematic configuration of the eNB. FIG.
• [ 29 ] 29 Fig. 10 is a block diagram illustrating an example of a schematic configuration of a smartphone.
• [ 30 ] 30 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.

Further, in this specification and drawings, there are cases in which elements having substantially the same function are distinguished by appending different letters to the end of the same reference number. For example, a plurality of elements having substantially the same functional configuration as the base stations 100A, 100B and 100C are discriminated as necessary. However, in a case where it is not necessary to distinguish each of the plurality of elements having substantially the same functional configuration, only the same reference numeral is added. For example, in a case where it is not necessary to particularly distinguish the base stations 100A, 100B and 100C, they are simply referred to as a "base station 100".

• 1. Einleitung
  • 1,1. Schematische Systemkonfiguration
  • 1,2. MEC
  • 1,3. Träger
  • 1.4 TFT und SDF
• 2. Konfigurationsbeispiele von Vorrichtungen
  • 2,1. Konfigurationsbeispiel von Basisstation
  • 2,2. Konfiguration des Endgeräts
  • 2,3. Konfigurationsbeispiel des MEC-Servers
• 3. Erste Ausführungsform
  • 3,1. Technisches Problem
  • 3,2. Technische Merkmale
• 4. Zweite Ausführungsform
  • 4,1. Technisches Problem
  • 4,2. Technische Merkmale
• 5. Dritte Ausführungsform
  • 5,1. Technisches Problem
  • 5,2. Technische Merkmale
• 6. Anwendungsbeispiele
• 7. Schlussfolgerung

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

• 1 Introduction
  • 1.1. Schematic system configuration
  • 1.2. MEC
  • 1.3. carrier
  • 1.4 TFT and SDF
• 2. Configuration examples of devices
  • 2.1. Configuration example of base station
  • 2.2. Configuration of the terminal
  • 2.3. Configuration example of the MEC server
• 3. First embodiment
  • 3.1. Technical problem
  • 3.2. technical features
• 4. Second embodiment
  • 4.1. Technical problem
  • 4.2. technical features
• 5. Third embodiment
  • 5.1. Technical problem
  • 5.2. technical features
• 6. Application examples
• 7. Conclusion

<< 1. Introduction >>

<Schematic system configuration>

First, a schematic configuration of a system 1 according to an embodiment of the present disclosure with reference to 1 described. 1 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. With reference to 1 instructs the system 1 a wireless communication device 100 , a terminal 200 and an MEC server 300 on.

( 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 sends a downlink signal to the terminal 200A and receives an uplink signal from the terminal 200A.

This is the base station 100 also referred to as an eNodeB (or eNB). Here, the eNodeB may be an eNodeB, as defined in LTE or LTE-A, or it may be more generally interpreted as a communication device.

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 1 a microcell base station and a cell 10A 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. The master device 100C is a dynamic access point (AP). The dynamic AP 100C is a mobile device that dynamically operates the small cell 10C. The dynamic 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. For example, the dynamic AP 100C may be a terminal equipped with hardware or software that may act as a base station or a wireless access point. In this case, the small cell 10C is a localized network (dynamic cell).

Cell 10 may operate in accordance with 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 with the micro cell or not overlap with the micro cell, and smaller than the microcell (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 serving as a master device that 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 sends an uplink signal to the base station 100A.

Here is the terminal 200 also referred to as a "user". The user may also be referred to as a user equipment (UE). In addition, 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.

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 to 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 (for example, 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 the user over the wireless communication path from the MEC server 300 provided service. 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 1 shown. Of course, the MEC server can 300 be formed as an independent device as a physical entity.

For example, the base station 100A provides the service provided by the MEC server 300A to the terminal 200A connected to the microcell 10. 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 1 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.

<MEC>

Next, the MEC will be referred to 2 to 6 described.

( 1 ) Network configuration

2 FIG. 13 is a diagram illustrating an example of a configuration of an LTE network in which MEC is not introduced. As in 2 1, a radio access network (RAN) has a UE and an eNodeB. The UE and the eNodeB are connected via a Uu interface and the eNodeBs are connected via an X2 interface. An Evolved Packet Core (EPC) also has a Mobility Management Entity (MME), a Home Subscriber Server (HSS), a Serving Gateway (S-GW) and a PDN Gateway (P-GW). The MME and the HSS are connected via an S6a interface, the MME and the S-GW are connected via an S11 interface and the S-GW and the P-GW are connected via an S5 interface. The eNodeB and the MME are connected via a S1-MME interface, the eNodeB and the S-GW are connected via a S1-U interface, and the P-GW and the PDN are connected via an SGi interface.

For example, the PDN has an original server and a cache server. An original application to be provided to the UE is stored in the original server. For example, an application or cache data is stored in the cache server. By accessing the cache server instead of the original server, the UE can reduce a processing load on the original server and a communication load corresponding to the access to the original server. However, since the cache server is outside the RAN and the EPC (i.e., the PDN), a communication delay that occurs between the UE and the cache server (i.e., a response delay to a request from the UE) is still a problem.

Examples of the UE's request include a static request such as downloading content stored in an HTTP server and a dynamic request such as a workflow in a specific application. In any case, it is clear that if cache data and an application are placed in an entity near the UE, the response to the query is fast. Typically, the response speed here depends on the number of units to be traversed and not on the distance between units. This is because a processing delay in an input unit, a processing unit, and an output unit in each entity that is traversed is accumulated in accordance with the number of units. Further, the content indicates data of any format, such as an application, a picture (a moving picture or a still picture), a sound, text or the like.

The MEC was invented to solve such a problem. At the MEC, an application server providing content to or from the UE is installed in an evolved packet system (EPS). Further, the EPS is a network having an EPC and an eUTRAN (i.e., an eNodeB). The application server installed in the EPS can also be referred to as an edge server or MEC server. Further, the application server is a concept that includes a cache server.

3 and 4 FIGs. are diagrams illustrating an example of a configuration of an LTE network into which MEC is introduced. In 3 An MEC server that caches content is installed in an eNodeB. According to this configuration, the number of entities arranged between the UE and the MEC server is smaller than that in FIG 2 and thus the UE can quickly grasp the content. In 4 the MEC server storing the content is installed in eNodeB and S-GW. For example, the UE detects the content of the MEC server located in the eNodeB and detects the content of the MEC server located in the S-GW in a case where no cache data is requested from the MEC server arranged in the eNodeB , Since access to the original server can be avoided, the UE can quickly capture the content in any case.

entities

In the 2 to 4 Entities shown are described below. The S-GW is an entity serving as an anchor point of delivery. The P-GW is a connection point between a mobile network and the outside (ie, a PDN), assigns an IP address to the UE, and provides an IP address that can be accessed from the exterior of the mobile network. The P-GW also performs filtering or the like on data arriving from the outside. The HSS is a database that stores subscriber information. The MME accesses the HSS to process various control signals, and performs a process such as authentication of each UE and authorization.

The EPC network is divided into a control level and a user level. The S-GW and the P-GW mainly relate to the user level, and the MME and HSS mainly relate to the control plane.

Here, the S-GW has a function of storing user data because, even in the configuration before MEC is introduced, it serves as the anchor point of the handover. On the other hand, the eNodeB has no function of storing the user data in the configuration before MEC is introduced, and has only functions such as a packet retransmission according to a packet loss that has occurred in the Uu interface, and thus is unable to store content , Further, the X2 interface is used for data exchange at the time of handover and cooperative control of the interference.

Application in MEC server

Examples of the cache include a stream cache that performs caching at an IP level and a content cache that performs caching at an application layer level. It is assumed that the MEC server supports both types of caches. Since the content cache is mainly used, it is currently assumed that the MEC server in particular supports the content cache.

Here in the MEC server it is important that an application is activated and enters an operational state. This is firstly due to the fact that cache data is detected based on an HTTP header, which is why it is desirable in the MEC server that an application capable of handling the HTTP enters the operational state. Second, in a case where the MEC server provides a specific application, it is desirable for the application to be placed and activated to enter the operational state.

Types of applications that correspond to MEC are manifold. In the case of the cache application, which caches data even though it is activated and enters the operating state in the MEC server, in a case where no destination data is cached, the UE goes to an original server to acquire data. Therefore, it is desirable to cache data in the cache application in advance.

Cache target data

As in the MEC server 300 There are two types of cached data, namely, data to be transmitted to the UE in a downlink (DL) direction (also referred to as a DL data flow hereinafter) and data received from the UE in an uplink (UL). Direction (hereafter referred to as UL data flow).

As an instance of caching the DL data flow, for example, there is a case where, when the UE accesses a Web application and detects certain http data, if the same data is cached in the MEC server, the caching data is detected.

An example of the use case for latching the UL data flow will be described below.

A first use case is a case of uploading data such as an image generated by the UE. In particular, the UE uploads an image generated by the UE, and the MEC server intermediately saves the image. Then, the MEC server may transmit the cached image to a server that stores the image on the PDN, for example, at a time when there is room in a transmission capacity in the core network. A communication load of the core network is reduced by shifting the transmission time. Further, for example, the MEC server may transmit the cached image to another UE. The sharing of the UL data cache with other UEs is useful, for example, in a case where pictures taken by onlookers in a stadium are shared among the audience in the stadium.

A second use case is a case of uploading data detected by the UE. For example, the UE uploads data detected via the device-to-device (D2D) or Wi-Fi (registered trademark) communication, and the MEC server temporarily stores the data. As a specific example of this use case, consider, for example, an example in which a store transmits information about products via D2D communication or Wi-Fi, and the UE collect the information and upload the information to the MEC server. In this case, other UEs within an area of the store (eg, within a cell of the eNodeB in which the MEC server is installed) may capture the cached information of the products.

A third use case is the uploading of data received from another eNodeB. For example, the UE uploads the data received from the eNodeB that is connected before handover to the MEC server installed in the eNodeB that will be connected after handover.

A fourth use case is a case where the MTC terminal is uploading data. As such data, for example, sales data of a vending machine and gas use status data are considered, which are detected by a gas meter. In some cases, the number of MTC terminals is very large, and if the MTC terminals try to upload all data to the server on the PDN, there is a problem that congestion occurs on the core network side. On the other hand, since such data does not require a real-time property, they are sufficient, although they arrive after one hour, for example. In other words, an application that relates to data from the MTC terminal may be considered to be delay resistant. Therefore, the MEC server can cache the data uploaded from the MTC terminal and transmit the cached data to the server on the PDN, for example, at the time when there is room in the transmission capacity in the core network. In particular, in the transmission capacity of the core network, the capacity of the control signal is more problematic than the capacity of the user data. To establish a session, it is necessary to signal several rounds. When a large number of MTC terminals are uploading all the data together, the signaling of the core network is excessively increased.

The example of the use case of caching the UL data flow has been described. In this specification, the description continues with the cache of the UL data flow.

The cache data of the UL data flow may be transmitted in the DL direction (for example, the UE) as described above, or may be transmitted in the UL direction (for example, the server on the P-GW or the PDN). The former cache data is also referred to as DL cache data and the latter cache data is also referred to as UL cache data.

5 is a diagram illustrating an example of the data flow of the DL cache data. As in 5 As shown, the MEC server temporarily stores the data uploaded by the UE and transmits the caching data to the UE (typically another UE than the uploading UE).

6 is a diagram illustrating an example of a data flow of UL caching data. As in 6 1, the MEC server stores the data uploaded by the UE and transmits the cache data to the original server on the PDN.

Further, depending on the data, there are cases in which the data may not be treated as DL cache data. For example, data that can be shared with other UEs may be treated as the DL caching data, and personal data may not be treated as DL caching data. Similarly, depending on the data, there are cases where the data may not be treated as UL caching data. For example, data that needs to be aggregated, such as data from the MTC terminal, is allowed as the UL caching data, and local data such as data having a regional restriction is not allowed as the UL caching data.

Under such circumstances, it is desirable in the MEC server to appropriately manage whether or not the cache data can be transmitted in the DL direction (ie, the UE) and whether the cache data is in the UL direction (that is, to the PDN) or not.

<Carrier>

Next, a carrier used in the EPS, particularly the EPS carrier, will be described with reference to FIG 7 to 11 described. The carrier refers to a session, that is, a drain pipe for data transmission.

7 Fig. 10 is an explanatory diagram for describing the architecture of the carrier. As in 7 an end-to-end service provided to the UE by the original server is performed Data transmission provided using the EPS carrier and an external carrier. An EPS bearer is set up in conjunction with some sort of QoS. For example, the UE sets up two EPS carriers that correspond to two types of QoS with the P-GW, if two kinds of QoS are to be used simultaneously.

The EPS bearer is a logical session (a virtual connection) and actually comprises a radio bearer, an S1 bearer, and an S5 bearer. The radio bearer is a bearer established on the LTE-Uu interface between the UE and the eNodeB. The S1 carrier is a carrier established at the S 1 interface between the eNodeB and the S-GW. The S5 carrier is a carrier established on the S5 interface between the S-GW and the P-GW.

8th Fig. 12 is an explanatory diagram for describing the architecture of the EPS carrier. As in 8th explained, the EPS carrier has a standard carrier and a dedicated carrier. When the carrier is established by exchanging signals with the MME, the UE first sets up the standard carrier corresponding to a QoS which is decided as standard. Thereafter, the UE establishes a carrier corresponding to a necessary QoS as a dedicated carrier. The dedicated carrier can not be set up without a standard carrier.

An ID identifying the bearer is set in each bearer. The ID is used to identify the bearer used by an UE. Therefore, if both the ID of the UE and the ID of the bearer are used, it is possible that each entity (for example, the P-GW, the S-GW, the eNodeB, or the like) identifies each bearer. The ID is a UL-ID and a DL-ID.

9 Fig. 10 is an explanatory diagram for describing a UL ID and a DL ID set in a carrier. As in 9 In the EPS carrier, a UL session and a DL session are distinguished by separate IDs. For example, as the ID set in the radio bearer, there is a "UL RB ID" for the UL and a "DL RB ID" for the DL. Further, in the S1 bearer, there is a session (a session exchanged according to a GTP tunneling protocol) discriminated by a tunnel endpoint ID (TEID) and "UL S1 TEID" which is a UL ID, or "DL S1 TEID" which is a DL ID is set. Further, in the S5 bearer, there is a session discriminated by TEID, and "UL S5 TEID" which is a UL ID or "DL S5 TEID" which is a DL ID is set.

The following table shows entities that assign IDs. This means that an entity that assigns an id builds a relevant responsible session.

[Table 1] entity UL DL UE eNodeB UL RB ID DL DL RB S1 ID, TEID S-GW UL S1 TEID DL S5 TEID P-GW UL S5 TEID

In the above table, the TEID is assigned by an entity on an endpoint page. On the other hand, both the UL RB ID and the DL RB ID are assigned by the eNodeB.

The following table shows a list of data flows with IDs. As shown in the following table, the UL data flow is transferred in a session assigned the UL ID, and the DL data flow is transferred in a session assigned the DL ID. Further, the ID of each session has a one-to-one mapping relationship with an ID associated with an ID. In other words, an ID is never assigned to a plurality of IDs.

[Table 2] entity UL DL UE UP IP flow → UL RB ID eNodeB UL RB ID DL S1 TEID → UL S1 TEID → DL RB ID S-GW UL S1 TEID DL S5 TEID → UL S5 TEID → DL S1 TEID P-GW DL IP flow → DLS5 TEID

Next, an operation for setting up the carrier will be described with reference to FIG 10 and 11 described.

10 FIG. 14 is a sequence diagram illustrating an example of a flow of a process for setting up the default bearer. FIG. The sequence includes a UE, an eNodeB, an MME, an S-GW, a P-GW and a Rules and Charges Collection Function (PCRF). As in 10 the device of the standard bearer is initiated according to a request from the UE. The request is transmitted in the order of the eNodeB, the MME, the S-GW and the P-GW, and a permit is transmitted in an opposite direction. Further, the PCRF is an entity that provides information about a QoS.

The present sequence will be described in detail. First, the UE transmits an attach request to the eNodeB (step S11), and the eNodeB transmits the message to the MME (step S12). Then, the MME transmits a standard bearer generation request to the S-GW (step S13), and the S-GW transmits the message to the P-GW (step S14). Then, the P-GW exchanges with the PCRF to establish an IP-Connectivity Access Network (IP-CAN) session (step S15). Then, the P-GW transmits a standard bearer generation response to the S-GW (step S16), and the S-GW transmits the message to the MME (step S17). Then, the MME transmits an attach acceptance to the eNodeB (step S18), and the eNodeB transmits a radio resource control (RRC) connection reconfiguration to the UE (step S19). Then, the UE transmits an RRC connection reconfiguration termination to the eNodeB (step S20), and the eNodeB transmits an attachment completion to the MME (step S21). Then, the MME transmits a bearer update request to the S-GW (step S22), and the S-GW transmits a bearer update response to the MME (step S23).

11 FIG. 12 is a sequence diagram illustrating an example of a flow of an operation for setting up the dedicated carrier. FIG. The present sequence includes the UE, the eNodeB, the MME, the S-GW, the P-GW and the PCRF. As in 11 1, the device of the dedicated carrier is initiated according to the request from the PCRF in contrast to the standard carrier. If the UE desires to set up the dedicated bearer, the UE further transmits a message indicating that the UE wishes to set up the dedicated application layer bearer, and the application layer transmits a necessary QoS to the PCRF, so that the UE initiated dedicated Carrier is implemented.

The present sequence will be described in detail. First, the PCRF sends an IP-CAN session change start to the P-GW (step S31). Then, the P-GW transmits a dedicated bearer generation request to the S-GW (step S32), and the S-GW transmits the message to the MME (step S33). Then, the MME transmits a dedicated carrier setup request to the eNodeB (step S34), and the eNodeB transmits an RRC connection reconfiguration to the UE (step S35). Then, the UE transmits an RRC connection reconfiguration termination to the eNodeB (step S36), and the eNodeB transmits a dedicated carrier setup response to the MME (step S37). Then, the MME transmits a dedicated bearer generation response to the S-GW (step S38), and the S-GW transmits the message to the P-GW (step S39). Then, the P-GW transmits an IP-CAN session change end to the PCRF (step S40).

<1.4 TFT and SDF>

As a technique for performing QoS control, there is a Traffic Flow Template (TFT). The TFT will be described below with reference to 12 described.

12 Fig. 10 is an explanatory diagram for describing the TFT. As in 12 1, a TFT is arranged in a P-GW for communication in a downlink direction, and a TFT is arranged in a UE for communication in an uplink direction. An IP flow flowing in an EPS is arranged such that the TFT performs filtering taking into account a QoS.

Functions performed on the TFT include mapping the IP flow to the EPS bearer and QoS control. Here, the QoS control is a function of restricting traffic within a specified maximum bit rate. For the IP flow associated with the EPS carrier, priority control corresponding to QoS is performed not only in the UE and the P-GW but also in the eNodeB and the S-GW. The TFT also performs the QoS control, while the IP flow is assigned to the EPS bearer, which is a unit of QoS control that is executed in different entities.

13 Fig. 10 is an explanatory view for describing the TFT in more detail. As in 13 The TFT maps the IP flow to a service data flow (SDF). At this time, the TFT orders the IP flow to an SDF of QoS corresponding to the IP flow (that is, a desired QoS) based on information for QoS control provided by the PCRF and a transmission source address (FIG. Source address), a transmission destination address (destination address), a port number or the like of an IP packet. Furthermore, the SDF is assigned to the corresponding EPS carrier. Further, the SDF and the EPS bearer have a one-to-one mapping relationship. An SDF is assigned to an EPS. Here, a plurality of SDFs may be allocated to the EPS carrier.

In detail with respect to the TFT, the TFT has a plurality of service data flow templates (SDF templates). The SDF templates are generated in conjunction with the QoS, but there are cases where the same QoS is set in a majority of SDF templates. In this case, the IP flow filtered by a plurality of SDF templates in which the same QoS is set is assigned to an EPS carrier. The SDF templates also carry out the carrier mapping and QoS control as described above.

<< Configuration example of each device >>

<Configuration example of base station>

First, a configuration of the base station 100 according to an embodiment of the present disclosure with reference to 14 described. 14 is a block diagram illustrating an example of a base station configuration 100 in accordance with an embodiment of the present disclosure. With reference to 14 assigns the base station 100 an antenna unit 110 , a wireless communication unit 120 , a network communication unit 130 , a storage unit 140 and a processing unit 150 on.

( 1 ) Antenna unit 110

The antenna unit 110 emits one of the wireless communication unit 120 outputted signal into a room as a radio wave. Furthermore, the antenna unit converts 110 the radio wave in the room into a signal and gives the signal to the wireless communication unit 120 out.

Wireless communication device 120

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

Network communication unit 130

The network communication unit 130 transmits and receives signals. For example, the network communication unit transmits 130 Information to other nodes and receives information from other nodes. For example, the other nodes include other base stations and core network nodes.

Storage unit 140

The storage unit 140 temporarily or permanently stores a program and various data for operation of the base station 100 ,

Processing unit 150

The processing unit 150 provides various functions of the base station 100 ready. The processing unit 150 has a carrier unit 151 and a communication processing unit 153 on. Furthermore, the processing unit 150 further include other components than the components described above. In other words, the processing unit 150 perform other operations than the operations of the components described above.

The carrier device unit 151 performs a process of setting up an MEC carrier, which will be described later. The communication processing unit 153 performs a process of performing communication using the MEC carrier or the existing EPS carrier. Workflows of the carrier unit 151 and the communication processing unit 153 will be described later in detail.

<Configuration of the terminal>

First, an example of a configuration of the terminal 200 according to the embodiment of the present disclosure with reference to 15 described. 15 is a block diagram illustrating an example of a configuration of the terminal 200 in accordance with an embodiment of the present disclosure. With reference to 15 has the terminal 200 an antenna unit 210 , a wireless communication unit 220 , a storage unit 230 and a processing unit 240 on.

( 1 ) Antenna unit 210

The antenna unit 210 emits one of the wireless communication unit 220 outputted signal into a room as a radio wave. Furthermore, the antenna unit converts 210 the radio wave in the room into a signal and gives the signal to the wireless communication unit 220 out.

Wireless communication unit 220

The wireless communication unit 220 transmits and receives signals. For example, the wireless communication unit receives 220 a downlink signal from the base station and transmits an uplink signal to the base station.

Storage unit 230

The storage unit 230 temporarily or permanently stores a program and various data for operation of the terminal 200 ,

Processing unit 240

The processing unit 240 represents different functions of the terminal 200 ready. The processing unit 240 has a carrier unit 241 and a communication processing unit 243 on. Furthermore, the processing unit 240 further include other components than the components described above. In other words, the processing unit 240 perform other operations than the operations of the components described above.

The carrier device unit 241 performs a process of setting up an MEC carrier, which will be described later. The communication processing unit 243 performs a process of performing communication using the MEC carrier or the existing EPS carrier. Workflows of the carrier unit 241 and the communication processing unit 243 will be described later in detail.

<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 16 described. 16 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 16 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 a corresponding device. For example, the communication unit performs 310 in a case where the MEC server 300 is formed as a logical unit and in the base station 100 is included, a communication with, for example, a control unit of the base station 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 storage unit 320 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 a carrier unit 331 and a communication processing unit 333 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 carrier device unit 331 performs a process of setting up an MEC carrier, which will be described later. The communication processing unit 333 performs a process of performing communication using the MEC carrier or the existing EPS carrier. Workflows of the carrier unit 331 and the communication processing unit 333 will be described later in detail.

The configuration examples of the respective devices have been described above. In the following, to simplify the description, the base station 100 also referred to as "eNodeB 100", and the terminal 200 is also referred to as "UE 200".

"3rd First embodiment »

<Technical problem>

In the EPS, data to be provided to the UE is managed in units of bearers. A carrier is assigned to a QoS. Thus, in a case where another QoS is used, another bearer is newly established. Here is the carrier of the EPS carrier. Three carriers constituting the EPS carrier, that is, an S5 carrier, an S1 carrier, and a radio carrier have a one-to-one mapping relationship. Further, in the existing architecture, a carrier passing through the MEC server is not included in the EPS carrier. As an example of a method of transmitting data to the MEC server or the MEC server, the eNodeB or the like may switch a destination of data transmitted from the EPS carrier to the MEC server. However, such a method has a great influence on the architecture of the EPS carrier and is not considered to be a suitable method. For example, if a data stream flows to a plurality of paths due to the switching, a principle that the EPS carrier corresponds to QoS becomes invalid, so that it is difficult to allocate the QoS to the EPS carrier.

Therefore, the present embodiment provides a new EPS carrier that supports the MEC server 300 passes.

<Technical features>

( 1 ) MEC carrier

17 FIG. 12 is an explanatory diagram for describing a carrier newly defined in the present embodiment. FIG. As in 17 represented, each entity performs (an eNodeB 100, a UE 200 , an MEC server 300 , an S-GW 41 and a P-GW 42) operating in the system 1 contained a communication using a carrier (corresponding to a first EPS carrier), the between the P-GW 42 and the UE 200 is set up and the MEC server 300 passes. Furthermore, each of the entities (the eNodeB 100, the UE 200 , the S-GW 41 and the P-GW 42) operating in the system 1 to perform communication using a carrier (a second EPS carrier) connected between the P-GW 42 and the UE 200 is set up without the MEC server 300 to go through. Each of the entities performs a communication by selectively sending a new EPS carrier to the MEC server 300 goes through, and uses an existing EPS carrier that supports the MEC server 300 does not go through. As the carrier, the MEC server 300 not going through, currently referred to as EPS carrier, will be the carrier that owns the MEC server 300 passes through, not designated as EPS carrier. In this regard, the new EPS carrier is also referred to as MEC carrier. In contrast, the EPS carrier that is the MEC server 300 does not pass, also referred to as an existing EPS carrier.

The MEC carrier has a carrier that houses the MEC server 300 used as the end section. Further, the carrier that owns the MEC server 300 as the end portion, a first MEC carrier for communicating with the UE 200 (MEC carrier 1 : corresponds to a first carrier) and a second MEC carrier for communication with the P-GW 42 (MEC carrier 2: corresponds to a second carrier). The MEC carrier has both a carrier in an uplink direction and a carrier in a downlink direction. The same applies to the existing EPS carrier.

An IP packet provided by the carrier for input to the MEC server 300 is worn temporarily in the MEC server 300 cached and goes through different types of processes. Further, the cached IP packet at any time is owned by a carrier for an output from the MEC server 300 transfer. Therefore, in a case where a protocol assigned to the retransmission control according to a transmission of ACK / NACK such as a transmission control protocol (TCP) occurs, a problem arises when the MEC server 300 not set as the endpoint. This is because ACK / NACK is not transmitted while it is being cached. In this regard, since the MEC carrier is a carrier, it becomes the MEC server 300 as the end portion (that is, the end point), a carrier for an end-to-end service is separated into two. Therefore, the MEC server can 300 according to the present embodiment, transmit ACK / NACK and perform a retransmission control.

18 Fig. 10 is an explanatory diagram for describing an architecture of the MEC carrier. An eNodeB 100A through which the first MEC carrier passes and an eNodeB 100B through which the second MEC carrier passes are in FIG 18 however, they may in practice be the same eNodeB 100. As in 18 1, each of the first MEC carrier and the second MEC carrier has a carrier that supports the MEC server 300 and the eNodeB 100 is used as both ends. A carrier, the MEC server 300 and the eNodeB 100A used at both ends is referred to as an M1 carrier and a carrier which is the MEC server 300 and the eNodeB 100B used at both ends is called M2 carrier. As in 18 explained, the MEC carrier has the radio carrier and the M1 carrier. Further, the second MEC carrier has the M2 carrier, the S1 carrier, and the S5 carrier.

The MEC server 300 and the eNodeB 100A are connected via an M1 interface. Further, the MEC server 300 and the eNodeB 100B is connected via an M2 interface. Here, for a UL data flow, it is desirable to have a carrier in one direction of an input to the MEC server 300 and a carrier in a direction of output from the MEC server 300 to set up. Similarly, for a DL data flow, it is preferable to have a bearer in a direction of input to the MEC server 300 and a carrier in a direction of output from the MEC server 300 to set up. To uniquely set up the four types of carriers, it is desirable to individually set up the M1 carrier and the M2 carrier.

The S5 carrier, the S1 carrier, the M2 carrier, the M1 carrier and the radio carrier constituting the MEC carrier have a one-to-one mapping relationship. In practice, however, it depends on a higher level application whether the M1 carrier immediately transmits data to the M2 carrier. In other words, carrier allocation is a one-to-one mapping, whereas it depends on an application if a data flow is continuous in time. In this regard, it is in the carrier architecture that in 18 is possible to cope with different application requirements because the MEC carrier is the MEC server 300 used as endpoint.

Carrier setup process

The MEC carrier is a dedicated carrier. Further, the MEC carrier becomes unique for each UE 200 in a form assigned to a standard carrier. This is the existing EPS carrier similarly, where a dedicated bearer is individual to each UE 200 in a form assigned to a standard bearer. In other words, the carrier architecture according to the present embodiment can be considered to have little change from the existing architecture.

As in 11 1, the existing dedicated carrier is established from the back of the EPC (ie, the P-GW side) using the PCRF that controls the QoS as the starting point. This is because it is desirable for the PCRF to perform a trigger because a newly established dedicated carrier is established based on a new QoS. Conveniently, the PCRF re-establishes the dedicated bearer based on the QoS request from the application server and the application server and the UE exchange at the application level. Therefore, the dedicated carrier can be interpreted as being established using the UE as a starting point.

In this regard, the M1 carrier and the M2 carrier may be set up using a request to the eNodeB 100 as a trigger or may be made using a request to the MEC server 300 be set up as a trigger. Typically, the M1 carrier and the M2 carrier are preferably set up using a request to the eNodeB 100 as a trigger. This is because a majority of MEC servers 300 considered to be connected to the eNodeB 100. Further, it is desirable that the M1 carrier and the M2 carrier be established in accordance with a single request to the eNodeB 100. An example of a process of setting up the M1 carrier and the M2 carrier by using a request from an MME 43 to the eNodeB 100 as a trigger will be described with reference to FIG 19 described.

19 FIG. 14 is a sequence diagram illustrating an example of an MEC carrier setup process. FIG. In the present sequence are the MEC server 300 , the UE 200 , the eNodeB 100, the MME 43, the S-GW 41, the P-GW 42 and a PCRF 44 involved.

First, the PCRF 44 transmits an IP-CAN session change start to the P-GW 42 (step S 102). Then, the P-GW 42 transmits an MEC carrier generation request to the S-GW 41 (step S104), and the S-GW 41 transmits the message to the MME 43 (step S106). Then, the MME 43 transmits a carrier request to the eNodeB 100 (step S108), and the eNodeB 100 transmits the message to the MEC server 300 (Step S110). The M1 carrier and the M2 carrier are set up at this time. Then the MEC server transmits 300 an MEC bearer response to the eNodeB 100 (step S112). Then, the eNodeB 100 transmits an RRC connection reconfiguration to the UE 200 (Step S114). The radio bearer is set up at this time and the first MEC bearer is set up accordingly. As described above, the first MEC carrier is set up by setting up a radio bearer comprising the eNodeB 100 and the UE 200 used as both ends after the M1 carrier is established. Then the UE transmits 200 an RRC connection reconfiguration termination to the eNodeB 100 (step S116), and the eNodeB 100 transmits a carrier response to the MME 43 (step S118). Then, the MME 43 transmits an MEC carrier generation response to the S-GW 41 (step S120), and the S-GW 41 transmits the message to the P-GW 42 (step S122). Then, the P-GW 42 transmits an IP-CAN session change end to the PCRF 44 (step S124).

On the other hand, cases in which it is desirable to consider the M1 carrier and the M2 carrier using the request to the MEC server are considered 300 as a trigger. For example, the MEC server 300 connected to a plurality of eNodeBs 100. In this case, one aspect is that the eNodeB 100 is the MEC server 300 managed, thinned. In this regard, an example of an operation for setting up the M1 carrier and the M2 carrier using a request from the MME 43 to the MEC server 300 as a trigger with reference to 20 described.

20 FIG. 14 is a sequence diagram illustrating an example of an MEC carrier setup process. FIG. The MEC server 300 , the UE 200 , eNodeB 100, MME 43, S-GW 41, P-GW 42 and PCRF 44 are involved in the present sequence.

First, the PCRF 44 transmits the IP-CAN session change start to the P-GW 42 (step S202). Then, the P-GW 42 transmits the MEC carrier generation request to the S-GW 41 (step S204), and the S-GW 41 transmits the message to the MME 43 (step S206). Next, the MME 43 transmits the MEC carrier request to the MEC server 300 (Step S208). The M1 carrier and the M2 carrier are set up at this time. After that, the MEC server transmits 300 the MEC bearer request to the MME 43 (step S210). Then the MME 43 transmits the MEC bearer request to the eNodeB 100 (step S212), and the eNodeB 100 transmits the RRC connection reconfiguration to the UE 200 (Step S214). The radio bearer is set up at this time and the first MEC bearer is set up accordingly. Then the UE transmits 200 the RRC connection reconfiguration termination to the eNodeB 100 (step S216), and the eNodeB 100 transmits the MEC carrier response to the MME 43 (step S218). Then, the MME 43 transmits the MEC carrier generation response to the S-GW 41 (step S220), and the S-GW 41 transmits the message to the P-GW 42 (step S222). Then, the P-GW 42 transmits an IP-CAN session change end to the PCRF 44 (step S224).

<< Second Embodiment >>

<Technical problem>

The MEC carrier is defined in the first embodiment. However, with the existing TFTs performing the carrier assignment, it is difficult to effectively use the MEC carrier. In particular with reference to 12 the existing TFT allocates only the IP flow to the EPS bearer so that the QoS is satisfied and has no mapping function to the MEC bearer.

In this regard, the present embodiment provides an architecture capable of allocating the IP flow to the MEC carrier.

<Technical features>

As described above in the first embodiment, each entity of the system performs 1 Make a communication by selectively selecting the new EPS carrier that hosts the MEC server 300 goes through, and uses the existing EPS carrier that the MEC server 300 does not go through. The switching performed to use one of the MEC carrier and the existing EPS carrier may be through the UE's filter 200 or P-GW 42. The filter is typically the TFT.

The TFT maps user traffic to the MEC server 300 is addressed to the SDF corresponding to the MEC carrier. Further, the TFT assigns user traffic to another device (such as the UE 200 , the P-GW 42 or the like), the SDF corresponding to the existing EPS carrier. Accordingly, the switching between the MEC carrier and the existing EPS carrier can be performed. This point is made with reference to 21 described in detail.

21 FIG. 12 is an explanatory diagram for describing the carrier allocation by the TFT according to the present embodiment. FIG. As in 21 As shown, the TFT assigns the IP flow to one of the SDF corresponding to the EPS carrier or the SDF corresponding to the MEC carrier. For example, the switching is performed on the basis of the transmission source address, the transmission destination address, the port number or the like of the IP packet. The TFT controls the SDF to which the IP flow is to be assigned based on the information for QoS control provided by the PCRF among a plurality of SDFs corresponding to the existing EPS carrier. The same applies to the MEC carrier.

The MEC server 300 can be used as a cache server. As an example of the purpose of the MEC server 300 Further, there is a purpose of caching the same data as the user traffic passing through the eNodeB 100, which is used as the cache server. In this case, the TFT copies the P-GW 42 or the UE 200 The user traffic on one of the MEC carrier and the existing EPS carrier and assigns the original traffic to the other. Accordingly, the same DL data flow from the P-GW 42 to the UE 200 be transferred and in the MEC server 300 be cached. Furthermore, the same UL data flow may be from the UE 200 be transferred to the P-GW 42 and in the MEC server 300 be cached. An example of a user traffic copying process will be described with reference to FIG 22 and 23 described.

22 Fig. 10 is an explanatory diagram for describing an example of the user traffic copying process. As in 22 The TFT copies and assigns the entered original user traffic. In the in 22 As illustrated, the TFT allocates the copied IP flow to the MEC bearer and maps the original IP flow to the existing EPS bearer. For example, the TFT associates the original IP flow with the existing EPS bearer and copies the original IP flow, and allocates the original IP flow to the MEC bearer only in a case where information for instructing caching is input. With such a mechanism, the influence on the existing EPS carrier is minimized. The TFT also controls the SDF to which the IP flow is to be assigned the basis of the information for QoS control provided by the PCRF among a plurality of SDFs corresponding to the existing EPS carrier. The same applies to the MEC carrier.

23 Fig. 10 is an explanatory diagram for describing an example of the user traffic copying process. As in 23 The TFT may map to the original user traffic entered and the user traffic entered. In other words, copying may be performed before the TFT. For example, the original IP flow is copied and entered into the TFT only when information instructing the caching is input, and otherwise can not be copied. Then, the TFT may associate the IP flow with the existing EPS bearer and associate the copied IP flow with the MEC bearer when the copied IP flow is entered. The TFT controls the SDF to which the IP flow is to be assigned based on the information for QoS control provided by the PCRF among a plurality of SDFs corresponding to the existing EPS carrier. The same applies to the MEC carrier.

In the above copying process of the above example, an IP packet within the P-GW 42 or the UE 200 copied. At this time, write the P-GW 42 or the UE 200 the destination address information (IP address, port number or the like) of the copied user traffic in the MEC server 300 around. Because the P-GW 42 and the UE 200 are not completely contained in the EPS, as in the S-GW 41 and the eNodeB 100, it is possible to rewrite the IP address or the like, wherein the switching of the transmission destination is implemented by the rewriting.

Of course, the P-GW 42 or the UE 200 Control whether the copying process is executed or not. For example, the P-GW 42 or the UE 200 the copying process in a case where the caching is performed simultaneously with the transmission of user traffic, and allocates the user traffic to the existing EPS carrier without performing the copying process in a case where caching is unnecessary. In a case where pre-caching is performed, the P-GW 42 or the UE orders 200 Furthermore, the user traffic to the MEC carrier without performing the copying process. As the purpose of the pre-buffering, for example, data associated with data obtained from the UE 200 downloaded, cached in advance.

. "5 Third embodiment »

<Technical problem>

In each of the above embodiments, the example was described in which the MEC server 300 where eNodeB 100 is installed, however, the present technology is not limited to this example.

For example, the MEC server 300 be installed in any device such as the S-GW 41. In this case, it is preferable to replace the eNodeB 100 in the description of each of the above embodiments with the device in which the MEC server 300 is installed.

In addition, the MEC server can 300 be installed between entities. As an example, in this case, a case is described in which the MEC server 300 between the eNodeB 100 and the S-GW 41 is installed. Of course, this arrangement is just an example, and the MEC server 300 can be installed between any entities.

<Technical features>

( 1 ) MEC carrier

The present embodiment has similar technical features as the first and second embodiments. For example, each of the entities running in the system performs 1 a communication using the carrier, between the P-GW 42 and the UE 200 is set up and goes through the MEC server 300 , Further, the MEC carrier includes carriers that the MEC server 300 as the end portion, more specifically, the first MEC carrier for communicating with the UE 200 and the second MEC carrier for communication with the P-GW 42. In this regard, a description of the technical features similar to those in the first and second embodiments will be omitted and the technical features specific to the present embodiment are mainly described below. First, an architecture of the MEC carrier according to the present embodiment will be described with reference to FIG 24 described.

24 Fig. 10 is an explanatory diagram for describing an architecture of the MEC carrier. As in 24 1, the first MEC carrier has the M1 carrier that hosts the MEC server 300 and the eNodeB 100 is used at both ends. Furthermore, the second MEC carrier has the S1 carrier which is the MEC server 300 and the S-GW 41 is used at both ends. As in 24 shown, the MEC carrier has the radio carrier and the M1 carrier. Further, the second MEC carrier has the S1 carrier and the S5 carrier. As above with reference to 12 in the architecture of the existing carrier, the carrier using the eNodeB 100 and the S-GW 41 as both ends is the S1 carrier, whereas in the present embodiment, the carrier is the MEC server 300 and the S-GW 41 is used as both ends, which is S1 carrier. Accordingly, if the eNodeB 100 and the MEC server 300 be considered as integrated with each other.

Even in the present embodiment, each of them leads in the system 1 entities contained in a communication by selectively selecting the MEC carrier that hosts the MEC server 300 goes through, and uses the existing EPS carrier that the MEC server 300 does not go through. In architecture, in 24 is shown, all IP flows go through the MEC server 300 regardless of whether he is in the MEC server 300 cached or not. As in 24 in the MEC carrier, the S-GW 41 and the eNodeB 100 are over the S1 carrier, which is the S-GW 41 and the MEC server 300 used as both ends, and the M1 carrier, which is the MEC server 300 and eNodeB 100 used as both ends. Because the MEC server 300 Serving the endpoint can be the MEC server 300 cache or transmit the IP flow while performing the retransmission control or the like. On the other hand, as in 12 In the present EPS carrier, the S-GW 41 and the eNodeB 100 are connected via the S1 carrier using the S-GW 41 and the eNodeB 100 as both ends. Because the MEC server 300 does not serve as the endpoint, the IP flow goes through the MEC server 300 ,

In the 24 The architecture shown is simpler in terms of configuration than that in FIG 18 illustrated architecture. In architecture, in 24 is shown, the MEC server 300 be provided with a function relating to the S1 carrier.

As an example of another architecture, the MEC server 300 between the eNodeB 100 and the UE 200 be arranged. In this case, it is difficult to say that this is a desirable architecture because of various wireless access features in the MEC server 300 must be installed. As another example, the MEC server 300 be arranged between the S-GW 41 and the P-GW 42. In this case, a distance between the UE increases 200 and the MEC server 300 to (more precisely, the number of existing entities between the UE increases 200 and the MEC server 300 and it is difficult to achieve an initial task of speeding up the delivery of content with the introduction of MEC, and therefore it is difficult to say that it is a desirable architecture. From such facts it follows that the architecture in 18 and 24 can be considered appropriate.

Carrier setup process

25 FIG. 14 is a sequence diagram illustrating an example of an MEC carrier setup process. FIG. The UE 200 , the eNodeB 100, the MEC server 300 , the MME 43, the S-GW 41, the P-GW 42 and the PCRF 44 are involved in the present sequence.

First, the PCRF 44 transmits the IP-CAN session change start to the P-GW 42 (step S302). Then, the P-GW 42 transmits the MEC carrier generation request to the S-GW 41 (step S304), and the S-GW 41 transmits the message to the MME 43 (step S306). Then, the MME 43 transmits the MEC carrier request to the MEC server 300 (Step S308), and the MEC server 300 transmits the message to the eNodeB 100 (step S310). The M1 carrier is set up at this time. Then, the eNodeB 100 transmits the RRC connection reconfiguration to the UE 200 (Step S312). The radio bearer is set up at this time and the first MEC bearer is set up accordingly. Then the UE transmits 200 an RRC connection reconfiguration termination to the eNodeB 100 (step S314). Then the eNodeB 100 transmits the MEC bearer generation response to the MEC server 300 (Step S316), and the MEC server 300 transmits the message to the MME 43 (step S318). Then, the MME 43 transmits the MEC carrier generation response to the S-GW 41 (step S320), and the S-GW 41 transmits the message to the P-GW 42 (step S322). Then, the P-GW 42 transmits the IP-CAN session change end to the PCRF 44 (step S324).

<< Examples >>

The technology according to the present disclosure can be applied to various products. For example, the MEC server 300 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 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 base station 100 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 base station 100 be implemented as another type of base station, such as a Node B or a base transceiver station (BTS). The base station 100 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 used as the base station 100 operate by performing the base station function temporarily or semi-permanently. Furthermore, at least a part of components of the base station 100 be implemented in the base station device or a module for the base station device.

In addition, the terminal may 200 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. In addition, the terminal can 200 be implemented as a terminal that performs machine-to-machine (M2M) communication (also referred to as Machine Communication Type (MTC) terminal). Furthermore, at least a part of the components of the terminal 200 in a module mounted in such a terminal (for example, an IC module configured in a chip).

<Application example regarding MEC server>

26 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. The main memory 702 includes a random access memory (RAM) and a read only memory (ROM) and stores programs executed by the 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. 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 26 can represent one or more components used in the processing unit 330 are included with reference to 16 is described (the carrier device unit 331 and / or the communication processing unit 333 ) 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 the processor 701 and the memory 702 may be mounted in the server 700, and the one or more components may be replaced by the one or more components Be implemented 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.

Further, in the in 26 illustrated server 700, the communication unit 310 referring to above 16 may be mounted in the network interface 704. Furthermore, the storage unit 320 be mounted in the main memory 702 or the memory 703.

<Example of use with base station>

(First application example)

27 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 27 shown. For example, the multiple antennas 810 may be compatible with multiple frequency bands used by the eNB 800. Although 27 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 can 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 via the network interface 823 with a core network node or other 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 27 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 27 shown. For example, the multiple RF circuits 827 may be compatible with multiple antenna elements. Although 27 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 27 can represent one or more components used in the processing unit 150 (the carrier unit 151 and / or the communication processing unit 153 ) which are related to 14 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.

Further, in the in 27 eNB 800 illustrated the wireless communication unit 120 referring to above 14 described in the wireless communication interface 825 (for example, the RF circuit 827) to be mounted. Furthermore, the antenna unit 110 be mounted in the antenna 810. Furthermore, the network communication unit 130 be mounted in the controller 821 and / or the network interface 823. Furthermore, the storage unit 140 be mounted in the main memory 822.

(Second example of use)

28 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 28 shown. For example, the multiple antennas 840 may be compatible with multiple frequency bands used by the eNB 830. Although 28 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 27 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 27 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 28 shown. For example, the multiple BB processors 856 may be compatible with multiple frequency bands used by the eNB 830. Although 28 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 28 shown. For example, the multiple RF circuits 864 may support multiple antenna elements. Although 28 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 28 can represent one or more components used in the processing unit 150 (the carrier unit 151 and / or the communication processing unit 153 ) which are related to 14 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 become. In addition, a readable recording medium in which the program is recorded may be provided.

Further, in the in 28 For example, eNB 830 illustrated the wireless communication unit 120 referring to above 14 is described in the wireless Be mounted communication interface 863 (for example, the RF circuit 864). Furthermore, the antenna unit 110 be mounted on the antenna 840. Furthermore, the network communication unit 130 be mounted in the controller 851 and / or the network interface 853. Furthermore, the storage unit 140 be mounted in the main memory 852.

<Application example relating to terminal>

(First application example)

29 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 29 shown. Although 29 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 29 shown. Although 29 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 29 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 29 can represent one or more components used in the processing unit 240 (the carrier unit 241 and / or the communication processing unit 243 ) which are related to 15 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.

In the in 29 For example, the smartphone 900 illustrated may be the wireless communication unit 220 referring to above 15 described in the wireless communication interface 912 (for example, the RF circuit 914) to be mounted. Furthermore, the antenna unit 210 be mounted on the antenna 916. Furthermore, the storage unit 230 be mounted in the main memory 902.

(Second example of use)

30 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 comprise 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 30 shown. Although 30 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 30 shown. Although 30 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 30 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 30 may be one or more components included in the processing device unit 240 (the carrier unit 241 and / or the communication processing unit 243 ) which are related to 15 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 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 may program To run. 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.

Furthermore, in the in 30 The vehicle navigation device 920 shown in FIG. 1, for example, the wireless communication unit 220 referring to above 15 described in the wireless communication interface 933 (for example, the RF circuit 935) to be mounted. Furthermore, the antenna unit 210 be mounted on the antenna 937. Furthermore, the storage unit 230 be mounted in the main memory 922.

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 including the carrier device unit 241 and / or the communication processing unit 243 having. 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.

<< Conclusion >>

An embodiment of the present disclosure is described above with reference to FIG 1 to 30 has been described in detail. As described above, each of the units (the eNodeB 100, the UE 200 , the MEC server 300 , the S-GW 41 and the P-GW 42) operating in the system 1 include communication using the MEC carrier that is between the P-GW 42 and the UE 200 is set up and the MEC server 300 which is installed in the EPS and the UE 200 Provides content or content from the UE 200 detected. By using the MEC bearer, each entity can send the IP flow to the MEC server 300 or the IP flow from the MEC server 300 to transfer.

Further, the switching between the existing EPS carrier and the MEC carrier by the TFT of the UE 200 or P-GW 42. Therefore, it is possible to implement the MEC carrier without modifying the architecture of the existing EPS carrier.

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.

It should be noted that the processes described in this specification with reference to the flowchart and the sequence diagram must be performed in the order illustrated in the flowchart. Some processing steps can be performed in parallel. Further, some additional steps may be used or some processing steps may be omitted.

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 beinhaltet:
   • eine Verarbeitungseinheit, die konfiguriert ist, eine Kommunikation unter Verwendung eines ersten EPS-Trägers auszuführen, der zwischen einem Paketdatennetzwerk-Gateway (P-GW) und einem Endgerät eingerichtet ist und einen Anwendungsserver durchläuft, der in einem EPS installiert und konfiguriert ist, dem Endgerät Inhalt bereitzustellen oder Inhalt von dem Endgerät zu erfassen.
2. (2) Vorrichtung nach (1), wobei der erste EPS-Träger einen Träger aufweist, der den Anwendungsserver als einen Endabschnitt verwendet.
3. (3) Vorrichtung nach (2), wobei der Träger, der den Anwendungsserver als den Endabschnitt verwendet, einen ersten Träger zur Kommunikation mit dem Endgerät und einen zweiten Träger zur Kommunikation mit dem P-GW aufweist.
4. (4) Vorrichtung nach (3), wobei jeder des ersten Trägers und des zweiten Trägers einen Träger aufweist, der den Anwendungsserver und eine Basisstation als beide Enden verwendet.
5. (5) Vorrichtung nach (4), wobei der erste Träger durch Einrichten eines Trägers eingerichtet wird, der die Basisstation und das Endgerät als beide Enden verwendet, nachdem der Träger, der den Anwendungsserver und die Basisstation als beide Enden verwendet, eingerichtet wird.
6. (6) Vorrichtung nach (4) oder (5), wobei der Träger, der den Anwendungsserver und die Basisstation als beide Enden verwendet, unter Verwendung einer Anfrage an die Basisstation als Auslöser eingerichtet wird.
7. (7) Vorrichtung nach (4) oder (5), wobei der Träger, der den Anwendungsserver und die Basisstation als beide Enden verwendet, unter Verwendung einer Anfrage an die Basisstation als Auslöser eingerichtet wird.
8. (8) Vorrichtung nach (3), wobei der erste Träger einen Träger aufweist, der den Anwendungsserver und eine Basisstation als beide Enden verwendet, und der zweite Träger einen Träger aufweist, der den Anwendungsserver und ein bedienendes Gateway (S-GW) als beide Enden verwendet.
9. (9) Vorrichtung nach einem von (1) bis (8), wobei der erste EPS-Träger ein dedizierter Träger ist.
10. (10) Vorrichtung nach (9), wobei der erste EPS-Träger für jedes Endgerät einzeln eingerichtet ist.
11. (11) Vorrichtung nach einem von (1) bis (10), wobei die Verarbeitungseinheit die Kommunikation unter Verwendung eines zweiten EPS-Trägers ausführt, der zwischen dem P-GW und dem Endgerät eingerichtet ist und den Anwendungsserver nicht durchläuft, und das Umschalten durch einen Filter des Endgeräts oder des P-GW ausgeführt wird, um zu bestimmen, ob der erste oder der zweite EPS-Träger verwendet werden soll.
12. (12) Vorrichtung nach (11), wobei der Filter Benutzerverkehr, der an den Anwendungsserver adressiert ist, einem Dienstdatenfluss (Service Data Flow - SDF) zuordnet, der dem ersten EPS-Träger entspricht, und Benutzerverkehr, der an eine andere Vorrichtung adressiert ist, einem SDF zuordnet, der dem zweiten EPS-Träger entspricht.
13. (13) Vorrichtung nach (11) oder (12), wobei der Filter kopierten Benutzerverkehr einem des ersten EPS-Trägers und des zweiten EPS-Trägers zuordnet und ursprünglichen Benutzerverkehr dem anderen EPS-Träger zuordnet.
14. (14) Vorrichtung nach (13), wobei der Filter den kopierten Benutzerverkehr dem ersten EPS-Träger zuordnet und den ursprünglichen Benutzerverkehr dem zweiten EPS-Träger zuordnet.
15. (15) Vorrichtung nach (13) oder (14), wobei die Verarbeitungseinheit die Zieladresseninformationen des kopierten Benutzerverkehrs als eine Adresse umschreibt, die für den Anwendungsserver vorgesehen ist.
16. (16) Vorrichtung nach einem von (13) bis (15), wobei der Filter ursprünglichen Benutzerverkehr, der eingegeben wurde, kopiert und zuordnet.
17. (17) Vorrichtung nach einem von (13) bis (15), wobei der Filter ursprünglichen Benutzerverkehr, der eingegeben wurde, und kopierten Benutzerverkehr zuordnet, der eingegeben wurde.
18. (18) Vorrichtung nach einem von (11) bis (17), wobei der Filter eine Verkehrsflussvorlage (Traffic Flow Template - TFT) ist.
19. (19) Verfahren, das Folgendes aufweist:
    • Ausführen, von einem Prozessor, einer Kommunikation unter Verwendung eines ersten EPS-Trägers, der zwischen einem Paketdatennetzwerk-Gateway (P-GW) und einem Endgerät eingerichtet ist und einen Anwendungsserver durchläuft, der in einem EPS installiert und konfiguriert ist, dem Endgerät Inhalt bereitzustellen oder Inhalt von dem Endgerät zu erfassen.
20. (20) Programm, das einen Computer veranlasst, wie folgt zu fungieren:
    • als eine Verarbeitungseinheit, die konfiguriert ist, eine Kommunikation unter Verwendung eines ersten EPS-Trägers auszuführen, der zwischen einem Paketdatennetzwerk-Gateway (P-GW) und einem Endgerät eingerichtet ist und einen Anwendungsserver durchläuft, der in einem EPS installiert und konfiguriert ist, dem Endgerät Inhalt bereitzustellen oder Inhalt von dem Endgerät zu erfassen.

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

1. (1) Device including:
   • a processing unit configured to perform communication using a first EPS carrier set up between a packet data network gateway (P-GW) and a terminal and traversing an application server installed and configured in an EPS to the terminal To provide content or to capture content from the terminal.
2. (2) Device according to ( 1 ), wherein the first EPS carrier has a carrier that uses the application server as an end portion.
3. (3) The apparatus of (2), wherein the carrier using the application server as the end portion has a first carrier for communicating with the terminal and a second carrier for communicating with the P-GW.
4. (4) The apparatus of (3), wherein each of the first carrier and the second carrier has a carrier using the application server and a base station as both ends.
5. (5) The apparatus of (4), wherein the first carrier is established by setting up a carrier that uses the base station and the terminal as both ends after the carrier using the application server and the base station as both ends is established.
6. (6) The apparatus of (4) or (5), wherein the carrier using the application server and the base station as both ends is set as a trigger by using a request to the base station.
7. (7) The apparatus of (4) or (5), wherein the bearer using the application server and the base station as both ends is set as a trigger by using a request to the base station.
8. (8) The apparatus of (3), wherein the first carrier has a carrier that uses the application server and a base station as both ends, and the second carrier has a carrier that the application server and a serving gateway (S-GW) as both Used ends.
9. (9) Device according to one of 1 ) to (8), wherein the first EPS carrier is a dedicated carrier.
10. (10) The device according to (9), wherein the first EPS carrier is set up individually for each terminal.
11. (11) Device according to one of 1 ) to (10), wherein the processing unit executes the communication using a second EPS carrier established between the P-GW and the terminal and not passing through the application server, and the switching by a filter of the terminal or the P-GW is executed to determine whether the first or the second EPS carrier is to be used.
12. (12) The apparatus of (11), wherein the filter associates user traffic addressed to the application server with a service data flow (SDF) corresponding to the first EPS carrier and user traffic addressed to another device to an SDF corresponding to the second EPS carrier.
13. (13) The apparatus of (11) or (12), wherein the filter maps copied user traffic to one of the first EPS bearer and the second EPS bearer and maps original user traffic to the other EPS bearer.
14. (14) The apparatus of (13), wherein the filter associates the copied user traffic with the first EPS carrier and associates the original user traffic with the second EPS carrier.
15. (15) The apparatus of (13) or (14), wherein the processing unit rewrites the destination address information of the copied user traffic as an address provided for the application server.
16. (16) The apparatus of any of (13) to (15), wherein the filter copies and maps original user traffic that has been entered.
17. (17) The apparatus of any one of (13) to (15), wherein the filter associates original user traffic entered and copied user traffic entered.
18. (18) The apparatus of any one of (11) to (17), wherein the filter is a Traffic Flow Template (TFT).
19. (19) Method comprising:
    • Performing, by a processor, a communication using a first EPS bearer established between a packet data network gateway (P-GW) and a terminal and traversing an application server installed in an EPS and configured to provide content to the terminal or to capture content from the terminal.
20. (20) Program that causes a computer to function as follows:
    • as a processing unit configured to perform communication using a first EPS carrier set up between a packet data network gateway (P-GW) and a terminal and traversing an application server installed and configured in an EPS Terminal to provide content or to capture content from the terminal.

LIST OF REFERENCE NUMBERS

1

system

40

Core network

50

Packet data network

60

application server

100

wireless communication device, base station, eNodeB

110

antenna unit

120

wireless communication unit

130

Network communication unit

140

storage unit

150

processing unit

151

Carrier device unit

153

Communication processing unit

200

Terminal, UE

210

antenna unit

220

wireless communication unit

230

storage unit

240

processing unit

241

Carrier device unit

243

Communication processing unit

300

server

310

communication unit

320

storage unit

330

processing unit

331

Carrier device unit

333

Communication processing unit

Claims (20)

Apparatus comprising: a processing unit configured to perform communication using a first EPS carrier set up between a packet data network gateway (P-GW) and a terminal and traversing an application server installed and configured in an EPS to the terminal To provide content or to capture content from the terminal. Device after Claim 1 wherein the first EPS carrier has a carrier that uses the application server as an end portion. Device after Claim 2 wherein the carrier using the application server as the end portion has a first carrier for communicating with the terminal and a second carrier for communicating with the P-GW. Device after Claim 3 wherein each of the first carrier and the second carrier comprises a carrier that uses the application server and a base station as both ends. Device after Claim 4 wherein the first carrier is established by establishing a carrier that uses the base station and the terminal as both ends after the carrier using the application server and the base station as both ends is established. Device after Claim 4 wherein the bearer using the application server and the base station as both ends is set up as a trigger using a request to the base station. Device after Claim 4 wherein the bearer using the application server and the base station as both ends is set up using a request to the application server as a trigger. Device after Claim 3 wherein the first carrier comprises a carrier that uses the application server and a base station as both ends, and the second carrier has a carrier that uses the application server and a serving gateway (S-GW) as both ends. Device after Claim 1 wherein the first EPS carrier is a dedicated carrier. Device after Claim 9 , wherein the first EPS carrier is set up individually for each terminal. Device after Claim 1 wherein the processing unit performs the communication using a second EPS bearer established between the P-GW and the terminal and not passing through the application server, and the switching is performed by a filter of the terminal or the P-GW to determine whether the first or the second EPS carrier should be used. Device after Claim 11 wherein the filter associates user traffic addressed to the application server with a service data flow (SDF) corresponding to the first EPS carrier, and assigns user traffic addressed to another device to an SDF corresponding to the second EPS carrier corresponds. Device after Claim 11 wherein the filter maps copied user traffic to one of the first EPS bearer and the second EPS bearer and maps original user traffic to the other EPS bearer. Device after Claim 13 wherein the filter associates the copied user traffic with the first EPS carrier and associates the original user traffic with the second EPS carrier. Device after Claim 13 wherein the processing unit rewrites the destination address information of the copied user traffic as an address intended for the application server. Device after Claim 13 where the filter copies and maps original user traffic that was entered. Device after Claim 13 where the filter maps original user traffic that was entered and copied user traffic that was entered. Device after Claim 11 , where the filter is a traffic flow template (TFT). A method, comprising: executing, by a processor, a communication using a first EPS carrier established between a packet data network gateway (P-GW) and a terminal, and a An application server that is installed in an EPS and configured to provide content to the terminal or to capture content from the terminal. Program that causes a computer to act as follows: as a processing unit configured to perform communication using a first EPS carrier set up between a packet data network gateway (P-GW) and a terminal and traversing an application server installed and configured in an EPS Terminal to provide content or to capture content from the terminal.

Images