WO2017094360A1

WO2017094360A1 - Device, method and program

Info

Publication number: WO2017094360A1
Application number: PCT/JP2016/080451
Authority: WO
Inventors: 高野　裕昭
Original assignee: ソニー株式会社
Priority date: 2015-11-30
Filing date: 2016-10-13
Publication date: 2017-06-08
Also published as: DE112016005454T5

Abstract

[Problem] To provide a structure in which data transmitted to or transmitted from a terminal can be properly cached by an edge server. [Solution] This device provided with a processing unit which uses system information to broadcast capability information about an application server, which is provided in an Evolved Packet System (EPS) and provides content to a terminal device or acquires content from the terminal device.

Description

Apparatus, method, and program

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

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

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

The contents of the study in Non-Patent Document 1 and the like are still short after the study was started, and it is hard to say that MEC-related technologies have been sufficiently proposed. For example, a technique for appropriately caching data transmitted to or from a terminal by an edge server is one that has not been sufficiently proposed.

Therefore, the present disclosure provides a mechanism capable of appropriately caching data transmitted to or transmitted from a terminal by an edge server.

According to the present disclosure, a processing unit that is provided in an EPS (Evolved Packet System) and that provides content information to a terminal device or broadcasts capability information of an application server that acquires content from the terminal device using system information; An apparatus comprising:

Further, according to the present disclosure, data is obtained based on capability information of an application server that is broadcast using system information and that is provided in the EPS and that provides content to the terminal device or acquires content from the terminal device. An apparatus including a processing unit for transmitting is provided.

In addition, according to the present disclosure, an apparatus provided in the EPS, which provides a content to a terminal device or acquires content from the terminal device, and its capability broadcast using system information A notification unit for notifying information to the base station;
An apparatus is provided comprising:

In addition, according to the present disclosure, the capability information of an application server provided in the EPS and providing content to the terminal device or acquiring content from the terminal device is broadcast using the system information by the processor. A method is provided.

In addition, according to the present disclosure, the processor based on the capability information of the application server that is broadcast using the system information and that provides the content to the terminal device provided in the EPS or acquires the content from the terminal device. Transmitting the data.

Further, according to the present disclosure, including providing content to a terminal device or acquiring content from the terminal device, notifying the base station of own capability information broadcast using system information, A method is provided that is performed by a device provided within the EPS.

In addition, according to the present disclosure, a computer provided in the EPS provides a processing unit that provides content to a terminal device or obtains content from the terminal device, and own capability information broadcast using system information. A notification unit for notifying the base station;
A program for functioning as a server is provided.

As described above, according to the present disclosure, data transmitted to or transmitted from a terminal can be appropriately cached by an edge server. Note that the above effects are not necessarily limited, and any of the effects shown in the present specification, or other effects that can be grasped from the present specification, together with or in place of the above effects. May be played.

2 is an explanatory diagram illustrating an example of a schematic configuration of a system 1 according to an embodiment of the present disclosure. FIG. It is a figure which shows an example of a structure of the LTE network in which MEC is not introduced. It is a figure which shows an example of a structure of the LTE network in which MEC was introduce | transduced. It is a figure which shows an example of a structure of the LTE network in which MEC was introduce | transduced. It is a figure which shows an example of the data flow of DL cache data. It is a figure which shows an example of the data flow of UL cache data. It is explanatory drawing for demonstrating the architecture of a bearer. It is explanatory drawing for demonstrating the architecture of an EPS bearer. It is explanatory drawing for demonstrating ID for UL and ID for DL set to a bearer. It is a sequence diagram which shows an example of the flow of the procedure for establishing a default bearer. It is a sequence diagram which shows an example of the flow of the procedure for establishing a dedicated bearer. It is a block diagram which shows an example of a structure of the base station which concerns on the same embodiment. It is a block diagram which shows an example of a structure of the terminal device which concerns on the same embodiment. It is a block diagram which shows an example of a structure of the MEC server which concerns on the embodiment. It is a sequence diagram which shows an example of the flow of the 1st bearer establishment process performed in the system which concerns on 1st Embodiment. It is a sequence diagram which shows an example of the flow of the 2nd bearer establishment process performed in the system which concerns on the embodiment. It is a figure which shows roughly the data flow which concerns on the same embodiment. It is explanatory drawing for demonstrating the bearer mapping performed in eNodeB which concerns on the embodiment. It is a flowchart which shows an example of the flow of the judgment process performed in eNodeB for the bearer mapping shown in FIG. It is explanatory drawing for demonstrating the bearer mapping performed in eNodeB which concerns on the embodiment. [Fig. 21] Fig. 21 is a flowchart illustrating an example of a flow of determination processing performed in the eNodeB for the bearer mapping illustrated in Fig. 20. It is a block diagram which shows an example of a schematic structure of a server. It is a block diagram which shows the 1st example of schematic structure of eNB. It is a block diagram which shows the 2nd example of schematic structure of eNB. It is a block diagram which shows an example of a schematic structure of a smart phone. It is a block diagram which shows an example of a schematic structure of a car navigation apparatus.

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

In the present specification and drawings, elements having substantially the same functional configuration may be distinguished by adding different alphabets after the same reference numerals. For example, a plurality of elements having substantially the same functional configuration are differentiated as necessary, such as

base stations

100A, 100B, and 100C. However, when there is no need to particularly distinguish each of a plurality of elements having substantially the same functional configuration, only the same reference numerals are given. For example, when it is not necessary to distinguish the

base stations

100A, 100B, and 100C, they are simply referred to as the base station 100.

The description will be made in the following order.
1. 1. Introduction 1.1. Schematic configuration of system 1.2. MEC
1.3. Bearer Configuration example of each device 2.1. Configuration example of base station 2.2. Configuration of terminal device 2.3. 2. Configuration example of MEC server First embodiment 3.1. Technical issues 3.2. Technical features 4. Application example 5. Summary

<< 1. Introduction >>
<1.1. Schematic configuration of system>
First, a schematic configuration of a system 1 according to an embodiment of the present disclosure will be described with reference to FIG. FIG. 1 is an explanatory diagram illustrating an example of a schematic configuration of a system 1 according to an embodiment of the present disclosure. Referring to FIG. 1, the system 1 includes a wireless communication device 100, a terminal device 200, and an MEC server 300.

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

Here, the base station 100 is also called eNodeB (or eNB). The eNodeB here may be an eNodeB defined in LTE or LTE-A, and may more generally mean a communication device.

The base station 100A is logically connected to other base stations through, for example, an X2 interface, and can transmit and receive control information and the like. The base station 100A is logically connected to the core network 40 through, for example, an S1 interface, and can transmit and receive control information and the like. Note that communication between these devices can be physically relayed by various devices.

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

wireless communication devices

100B and 100C are master devices that operate the

small cells

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

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

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

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

master device

100B, or 100C) of the cellular system. For example, the terminal device 200A receives a downlink signal from the base station 100A and transmits an uplink signal to the base station 100A.

Here, the terminal device 200 is also called a user. The user may also be referred to as a UE (User Equipment). The wireless communication device 100C is also referred to as UE-Relay. The UE here may be a UE defined in LTE or LTE-A, and the UE-Relay may be Prose UE to Network Relay, which is discussed in 3GPP, and more generally communicated. It may mean equipment.

(3) Application server 60
The application server 60 is a device that provides services to users. The application server 60 is connected to a packet data network (PDN) 50. On the other hand, the base station 100 is connected to the core network 40. The core network 40 is connected to the PDN 50 via a gateway device. For this reason, the wireless communication apparatus 100 provides the service provided by the application server 60 to the MEC server 300 and the user via the packet data network 50, the core network 40, and the wireless communication path.

(4) MEC server 300
The MEC server 300 is a device that provides a service (for example, content) to a user. The MEC server 300 can be provided in the wireless communication device 100. In that case, the wireless communication device 100 provides the service provided by the MEC server 300 to the user via the wireless communication path. The MEC server 300 may be realized as a logical functional entity, and may be formed integrally with the wireless communication device 100 or the like as shown in FIG. Of course, the MEC server 300 may 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 device 200A connected to the macro cell 10. Also, the base station 100A provides the service provided by the MEC server 300A to the terminal device 200B connected to the small cell 10B via the master device 100B.

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

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

<1.2. MEC>
Next, the MEC will be described with reference to FIGS.

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

The PDN includes, for example, an original server and a cache server. The original server stores the original application provided to the UE. 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 the processing load on the original server and the communication load related to the access to the original server. However, since the cache server is located outside the RAN and the EPC (ie, PDN), the communication delay (ie, response delay to the request from the UE) generated between the UE and the cache server is still a problem. It was.

The UE request includes, for example, a static request such as downloading content stored in an http server and a dynamic request such as an operation for a specific application. In any case, it is obvious that the response to the request becomes faster when the cache data and the application are arranged in an entity closer to the UE. Here, typically, the response speed depends on the number of passing entities rather than the distance between the entities. This is because the processing delays in the input unit, processing unit, and output unit in each passing entity are accumulated by the number of entities. The content means data in an arbitrary format such as an application, an image (moving image or still image), sound, or text.

MEC was devised to solve this problem. In the MEC, an application server that provides content to the UE or acquires content from the UE is provided in an Evolved Packet System (EPS). Note that EPS is a network including EPC and eUTRAN (ie, eNodeB). An application server provided in the EPS may be referred to as an edge server or an MEC server. The application server is a concept including a cache server.

3 and 4 are diagrams illustrating an example of a configuration of an LTE network in which an MEC is introduced. In FIG. 3, an MEC server that caches content is provided in the eNodeB. According to this configuration, since the number of entities existing between the UE and the MEC server is reduced as compared with the example illustrated in FIG. 2, the UE can quickly acquire content. In FIG. 4, MEC servers that store content are provided in the eNodeB and the S-GW. For example, the UE obtains content from the MEC server located in the eNodeB, and obtains content from the MEC server located in the S-GW when there is no cache data requested from the MEC server located in the eNodeB. To do. In any case, since access to the original server can be avoided, the UE can quickly acquire the content.

(2) Each Entity Hereinafter, the entities appearing in FIGS. 2 to 4 will be described. The S-GW is an entity serving as a handover anchor point. The P-GW is a connection point between the mobile network and the outside (ie, PDN), assigns an IP address to the UE, and provides an IP address to be accessed outside the mobile network. The P-GW also performs filtering of data coming from the outside. The HSS is a database that stores subscriber information. The MME processes various control signals, accesses the HSS, and performs processing such as authentication and authorization of each UE.

The EPC network is separated into a control plane and a user plane. S-GW and P-GW are mainly related to the user plane, and MME and HSS are mainly related to the control plane.

Here, the S-GW has a function of storing user data in order to be an anchor point for handover even in the configuration before the introduction of the MEC. On the other hand, the eNodeB has no function of storing user data in the configuration before the introduction of the MEC, only has a function such as packet retransmission corresponding to a packet loss occurring in the Uu interface, and no content is stored. The X2 interface has been used for data exchange during handover and cooperative control of interference.

(3) Application caches in the MEC server include a stream cache that performs caching at the IP level and a content cache that performs caching at the application layer level. The MEC server is assumed to support any type of cache. Since the content cache is mainly used at present, it is assumed that the MEC server particularly supports the content cache.

Here, it is important that the application is activated and can be operated in the MEC server. First, since the cache data is recognized by the HTTP header, it is desirable that an application capable of handling HTTP can be operated in the MEC server. Second, if the MEC server provides a specific application, it is desirable that the application be deployed and activated to be operational.

∙ There are a wide variety of applications that support MEC. With respect to a cache application that caches data, even if it is activated and operable in the MEC server, if the target data is not cached, the UE will retrieve the data to the original server. Therefore, it is desirable to cache data in advance in a cache application.

(4) Data to be cached The data cached in the MEC server 300 includes data transmitted to the UE in the DL (Downlink) direction (hereinafter also referred to as DL data flow) and uploaded from the UE in the UL (Uplink) direction. There are two types of data (hereinafter also referred to as UL data flow).

As a use case for caching the DL data flow, for example, when the UE accesses a web application and acquires some http data, if the same data is cached in the MEC server, the cache data is acquired. Can be mentioned.

An example of a use case for caching the UL data flow is described below.

The first use case is a case of uploading data such as photos generated by the UE itself. Specifically, the UE uploads a photo generated by itself, and the MEC server caches this photo. Then, the MEC server may transfer the cached photo to the server that stores the photo on the PDN, for example, at a timing when the transmission capacity in the core network has a margin. By shifting the transfer timing, the communication load of the core network is reduced. In addition, the MEC server may transfer the cached photo to another UE, for example. The sharing of the UL data flow cache with other UEs is useful, for example, in the case where a photograph taken by a spectator at a stadium is shared between spectators at the stadium.

The second use case is a case of uploading data acquired by the UE. For example, the UE uploads data acquired by D2D (Device to Device) communication or Wi-Fi (registered trademark), and the MEC server caches this data. As a specific example of this use case, for example, a store broadcasts product information by D2D communication or Wi-Fi, and the UE acquires the information and uploads it to the MEC server. In that case, other UEs in the area of the store (for example, within the range of the cell of the eNodeB where the MEC server is provided) can obtain the cached product information.

The third use case is a case where data received from a different eNodeB is uploaded. For example, the UE uploads the data received from the eNodeB connected before the handover to the MEC server provided in the eNodeB connected after the handover.

The fourth use case is a case where the MTC terminal uploads data. As such data, for example, sales data of vending machines, gas use status data detected by a gas meter, and the like can be considered. There are cases where the number of MTC terminals is very large, and there is a problem that congestion occurs on the core network side when the MTC terminals try to upload data to the server on the PDN all at once. On the other hand, since these data do not require real-time properties, it is sufficient to arrive even after one hour, for example. That is, it can be said that the application regarding the data from the MTC terminal is resistant to delay. Therefore, the MEC server may cache the data uploaded from the MTC terminal, and transfer the cached data to the server on the PDN at a timing when there is a margin in the transmission capacity in the core network, for example. In particular, the transmission capacity of the core network has a problem with the capacity of the control signal rather than the capacity of the user data. This is because many round trips of signaling are required to create a session. If a large number of MTC terminals simultaneously upload data, the signaling of the core network increases excessively.

In the above, an example of a use case for caching the UL data flow has been described. In the present specification, such a cache of UL data flow will be mainly described.

The cache data of the UL data flow may be transferred in the DL direction (for example, UE) as described above, or may be transferred in the UL direction (for example, a server on the P-GW or 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.

FIG. 5 is a diagram showing an example of the data flow of DL cache data. As shown in FIG. 5, the MEC server caches data uploaded by the UE, and transmits the cache data to the UE (typically, a UE different from the uploaded UE).

FIG. 6 is a diagram showing an example of the data flow of UL cache data. As shown in FIG. 6, the MEC server caches the data uploaded by the UE and transmits the cache data to the original server on the PDN.

Note that some data may not be permitted to be handled as DL cache data. For example, it is considered that data that can be shared with other UEs is allowed to be handled as DL cache data, and personal data is not allowed to be handled as DL cache data. Similarly, it is considered that some data is not permitted to be handled as UL cache data. For example, it is considered that data that requires aggregation such as data from an MTC terminal is permitted as UL cache data, and local data such as region limitation is not permitted as UL cache data.

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

<1.3. Bearer>
Next, bearers used in EPS, particularly EPS bearers, will be described with reference to FIGS. The bearer is a session and is a so-called earthen pipe for performing data transmission.

FIG. 7 is an explanatory diagram for explaining the architecture of the bearer. As shown in FIG. 7, the end-to-end service provided from the original server to the UE is provided by data transmission using an EPS bearer and an external bearer. One EPS bearer is established corresponding to one kind of QoS. For example, when the UE wants to use two types of QoS at the same time, the UE establishes two EPS bearers corresponding to the two types of QoS with the P-GW.

The EPS bearer is a logical session (Virtual Connection), and actually includes a radio bearer, an S1 bearer, and an S5 bearer. A radio bearer is a bearer established on the LTE-Uu interface between the UE and the eNodeB. The S1 bearer is a bearer established on the S1 interface between the eNodeB and the S-GW. The S5 bearer is a bearer established on the S5 interface between the S-GW and the P-GW.

FIG. 8 is an explanatory diagram for explaining the architecture of the EPS bearer. As shown in FIG. 8, the EPS bearer includes a default bearer and a dedicated bearer. When establishing a bearer by exchanging signals with the MME, the UE first sets a default bearer corresponding to the QoS determined as the default. Thereafter, the UE establishes a bearer corresponding to the necessary QoS as a dedicated bearer. A dedicated bearer cannot be established without a default bearer.

Each bearer is set with an ID for identifying the bearer. This ID is used to identify a bearer used by one UE. Accordingly, by using both the UE ID and the bearer ID, each entity (eg, P-GW, S-GW, eNodeB, etc.) can identify each bearer. This ID includes UL and DL.

FIG. 9 is an explanatory diagram for explaining the ID for UL and the ID for DL set in the bearer. As shown in FIG. 9, in an EPS bearer, a UL session and a DL session are distinguished from each other by different IDs. For example, the ID set for the radio bearer includes “UL RB ID” for UL and “DL RB ID” for DL. In addition, in the S1 bearer, there is a session (session exchanged by GTP Tunneling Protocol) distinguished by TEID (Tunneling End point ID), and the UL ID “UL S1 TEID” or the DL ID “ “DL S1 TEID” is set. Further, the S5 bearer has a session that is distinguished by TEID, and “UL S5 TEID” that is an ID for UL or “DL S5 TEID” that is an ID for DL is set.

The table below shows which entity assigns each ID. This means that the entity assigned the ID has established the corresponding session responsibly.

Referring to the above table, TEID is assigned by the entity on the endpoint side. On the other hand, regarding RB ID, both UL and DL are allocated by eNodeB.

The following table shows a list of data flow using ID. As shown in the table below, the UL data flow is transmitted in a session to which a UL ID is assigned, and the DL data flow is transmitted in a session to which a DL ID is assigned. Each session ID has a one-to-one mapping relationship, and one ID is mapped to one ID. That is, one ID is not mapped to a plurality of IDs.

Subsequently, a procedure for establishing a bearer will be described with reference to FIG. 10 and FIG.

FIG. 10 is a sequence diagram showing an example of a procedure flow for establishing a default bearer. This sequence involves UE, eNodeB, MME, S-GW, P-GW, and PCRF (Policy and Charging Rules Function). As shown in FIG. 10, the default bearer is established with a request from the UE as a starting point. Requests are sent in the order of eNodeB, MME, S-GW, and P-GW, and approval is sent back in the opposite direction. The PCRF is an entity that provides information related to QoS.

】 This sequence will be explained 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). Next, the MME transmits a default 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 communicates with the PCRF to establish an IP-CAN (IP Connectivity Access Network) session (step S15). Next, the P-GW transmits a default bearer generation response to the S-GW (step S16), and the S-GW transmits the message to the MME (step S17). Next, the MME transmits an attach accept to the eNodeB (step S18), and the eNodeB transmits RRC (Radio Resource Control) connection resetting to the UE (step S19). Next, the UE transmits RRC connection reconfiguration completion to the eNodeB (step S20), and the eNodeB transmits attachment completion to the MME (step S21). Next, 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).

FIG. 11 is a sequence diagram showing an example of a procedure flow for establishing a dedicated bearer. This sequence involves UE, eNodeB, MME, S-GW, P-GW and PCRF. As shown in FIG. 11, the establishment of the dedicated bearer is performed starting from a request from the PCRF, contrary to the default bearer. When the UE wants to create a dedicated bearer, the UE transmits a message to that effect to the application layer, and the application layer conveys the QoS necessary for the PCRF, thereby establishing the dedicated bearer starting from the UE.

】 This sequence will be explained in detail. First, the PCRF transmits an IP-CAN session change start to the P-GW (step S31). Next, 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). Next, the MME transmits a dedicated bearer setup request to the eNodeB (step S34), and the eNodeB transmits RRC connection reconfiguration to the UE (step S35). Next, the UE transmits RRC connection reconfiguration completion to the eNodeB (step S36), and the eNodeB transmits a dedicated bearer setup response to the MME (step S37). Next, 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). Next, the P-GW transmits an IP-CAN session change end to the PCRF (step S40).

<< 2. Configuration example of each device >>
<2.1. Example of base station configuration>
First, the configuration of the base station 100 according to an embodiment of the present disclosure will be described with reference to FIG. FIG. 12 is a block diagram illustrating an exemplary configuration of the base station 100 according to an embodiment of the present disclosure. Referring to FIG. 12, the base station 100 includes an antenna unit 110, a radio communication unit 120, a network communication unit 130, a storage unit 140, and a processing unit 150.

(1) Antenna unit 110
The antenna unit 110 radiates a signal output from the wireless communication unit 120 to the space as a radio wave. Further, the antenna unit 110 converts radio waves in space into a signal and outputs the signal to the wireless communication unit 120.

(2) Wireless communication unit 120
The wireless communication unit 120 transmits and receives signals. For example, the radio communication unit 120 transmits a downlink signal to the terminal device and receives an uplink signal from the terminal device.

(3) Network communication unit 130
The network communication unit 130 transmits and receives information. For example, the network communication unit 130 transmits information to other nodes and receives information from other nodes. For example, the other nodes include other base stations and core network nodes.

(4) Storage unit 140
The storage unit 140 temporarily or permanently stores a program for operating the base station 100 and various data.

(5) Processing unit 150
The processing unit 150 provides various functions of the base station 100. The processing unit 150 includes a notification unit 151 and a communication processing unit 153. The processing unit 150 may further include other components other than these components. That is, the processing unit 150 can perform operations other than the operations of these components.

The operations of the notification unit 151 and the communication processing unit 153 will be described in detail later.

<2.2. Configuration of terminal device>
Subsequently, an example of a configuration of the terminal device 200 according to the embodiment of the present disclosure will be described with reference to FIG. FIG. 13 is a block diagram illustrating an exemplary configuration of the terminal device 200 according to an embodiment of the present disclosure. Referring to FIG. 13, the terminal device 200 includes an antenna unit 210, a wireless communication unit 220, a storage unit 230, and a processing unit 240.

(1) Antenna unit 210
The antenna unit 210 radiates the signal output from the wireless communication unit 220 to the space as a radio wave. Further, the antenna unit 210 converts a radio wave in the space into a signal and outputs the signal to the wireless communication unit 220.

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

(3) Storage unit 230
The storage unit 230 temporarily or permanently stores a program for operating the terminal device 200 and various data.

(4) Processing unit 240
The processing unit 240 provides various functions of the terminal device 200. The processing unit 240 includes an acquisition unit 241 and a communication processing unit 243. Note that the processing unit 240 may further include other components other than these components. That is, the processing unit 240 can perform operations other than the operations of these components.

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

<2.3. Configuration example of MEC server>
Next, an example of the configuration of the MEC server 300 according to an embodiment of the present disclosure will be described with reference to FIG. FIG. 14 is a block diagram illustrating an exemplary configuration of the MEC server 300 according to an embodiment of the present disclosure. Referring to FIG. 14, the MEC server 300 includes a communication unit 310, a storage unit 320, and a processing unit 330.

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

(2) Storage unit 320
The storage unit 320 temporarily or permanently stores a program for operating the MEC server 300 and various data. For example, the storage unit 320 may store various contents and applications provided to the user.

(3) Processing unit 330
The processing unit 330 provides various functions of the MEC server 300. The processing unit 330 includes a notification unit 331 and a content processing unit 333. Note that the processing unit 330 may further include other components other than these components. That is, the processing unit 330 can perform operations other than the operations of these components.

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

<< 3. First Embodiment >>
<3.1. Technical issues>
As described above, whether or not cache data can be transmitted in the DL direction (ie, to the UE) and whether or not the cache data can be transmitted in the UL direction (ie, to the PDN) is appropriately managed in the MEC server. desirable. However, it has not been determined how to cache the data flow in the DL direction and the data flow in the UL direction in the MEC server.

Also, as described above, different IDs are assigned to the UL bearer and the DL bearer, and are completely separated. However, there are cases where data uploaded by the UE to the MEC server using the UL bearer is transferred to the server on the PDN, and other UEs may want to download and use the DL bearer. It is done. That is, the data uploaded by the UE to the MEC server using the UL bearer may be handled as UL cache data or may be handled as DL cache data. However, in the current architecture, since the UL data flow and the DL data flow are completely separated, it is difficult to handle the cache of the UL data flow as DL cache data.

Therefore, an architecture that allows the UL data flow and the DL data flow to cross each other is desirable. Specifically, it is desirable that data uploaded by the UE to the MEC server using the UL bearer can be transferred to other UEs using the DL bearer. Of course, transferring the UL data flow to the DL against the intention of the UE side (that is, transferring data uploaded from one UE to another UE without permission) can be a privacy issue and should be prevented. It is.

Realizing such an architecture at the application layer is not realistic. This is because inspecting application layer information to determine a transmission path is inefficient. Therefore, it is desirable that such an architecture is realized in a layer that handles bearers.

On the other hand, with respect to data that does not require real-time properties, such as data uploaded from an MTC terminal, a bearer from the terminal to the destination server on the PDN has been established in the current architecture. In this regard, it is desirable to allow the bearer up to the MEC server and the bearer from the MEC server to the server on the PDN at different timings. As a result, the MEC server can cache the uploaded data and transfer it to the server on the PDN at different timings.

In the current architecture, data can be uploaded from the terminal only when a bearer from the terminal to the destination server on the PDN is established. Therefore, even when uploading to the MEC server, if the MTC terminals upload data all at once, an excessive increase in signaling in the core network will still occur. In this regard, it is desirable that the bearer up to the MEC server and the bearer from the MEC server to the server on the PDN are established separately. Thereby, even if the MTC terminals upload data to the MEC server all at once, it is possible to prevent an increase in signaling on the core network side.

<3.2. Technical features>
(1) Capability information The eNodeB 100 (for example, the notification unit 151) broadcasts capability information of the MEC server 300. For example, the eNodeB 100 broadcasts capability information to the subordinate UE 200 using the system information. UE200 (for example, acquisition part 241) acquires capability information from system information. Then, the UE 200 (for example, the communication processing unit 243) transmits data to the MEC server 300 based on the capability information. As a result, the UE 200 can transmit data required by the MEC server 300, and can transmit data to the MEC server 300 having the capability corresponding to the data to be uploaded. For this purpose, the MEC server 300 (for example, the notification unit 331) notifies the eNodeB 100 of its capability information in advance.

For example, the capability information may include information indicating whether the MEC server 300 can store (for example, cache) information transmitted from the UE 200 via UL. Thereby, UE200 can avoid uploading data accidentally to MEC server 300 which does not have a cache function.

For example, the capability information may include information indicating the use of information stored in the MEC server 300. This application may be transmitted from the MEC server 300 to the uplink. That is, the capability information may include information indicating whether or not the MEC server 300 can handle UL cache data. Moreover, this use may be transmitted from the MEC server 300 to the downlink. That is, the capability information may include information indicating whether or not the MEC server 300 can handle DL cache data. The UE 200 can upload data to the MEC server 300 in accordance with the use based on such information indicating the use.

For example, capability information may include information indicating a disclosure range. Specifically, whether or not the data uploaded by the UE 200 is disclosed to other UEs 200, and attribute information of other UEs 200 to be disclosed (for example, limited within the same cell) are included in the capability information. May be included. In addition, the capability information may include information indicating the processing content of data for disclosure (for example, whether or not to perform mosaic processing). As a result, the UE 200 (for example, the communication processing unit 243) can upload data while ensuring privacy to be protected. Note that the information indicating the disclosure range may be expressed in a level such that the higher the value, the higher the value is disclosed to the unspecified number, and the lower the value, the specific number is disclosed.

(2) 1st bearer eNodeB100 (for example, communication processing part 153) performs the 1st procedure which establishes the 1st bearer for acquiring the information memorized by MEC server 300 from UE200. That is, a bearer for uploading the UL data flow to be cached in the MEC server 300 from the UE 200 to the eNodeB 100 is established by the first procedure. When the MEC server 300 is provided in the eNodeB 100, the first bearer is a radio bearer.

The first bearer is established for each use of information stored in the MEC server 300. That is, a bearer for uploading DL cache data may be established as the first bearer. Moreover, the bearer for uploading UL cache data may be established as a 1st bearer.

Here, in the first procedure, information indicating the use of information transmitted using the first bearer (that is, information cached as DL cache data or information cached as UL cache data) is provided. Sent from UE 200. This information can be transmitted in an attach request, for example. Thereby, eNodeB100 becomes possible to establish the 1st bearer according to a use.

The procedure for establishing the first bearer can follow the existing attach procedure. This procedure may involve the UE 200 (for example, the communication processing unit 243), the eNodeB 100 (for example, the communication processing unit 153), and related entities. Hereinafter, an example of the procedure for establishing the first bearer will be described with reference to FIG.

FIG. 15 is a sequence diagram illustrating an example of a flow of first bearer establishment processing executed in the system 1 according to the present embodiment. In this sequence, eNodeB 100, UE 200, MME, S-GW, P-GW, and PCRF are involved.

As shown in FIG. 15, first, the eNodeB 100 notifies the UE 200 of capability information of the MEC server 300 (step S102). Next, the UE 200 refers to the received capability information and starts an upload procedure described below when there is data that can be transmitted (step S104). First, the UE 200, the eNodeB 100, the MME, the S-GW, the P-GW, and the PCRF establish a default bearer by a normal attach procedure (Attach Procedure) shown in FIG. 10 (step S106).

Then, unlike the normal procedure for establishing a dedicated bearer starting from the PCRF shown in FIG. 11, a procedure for establishing a dedicated bearer starting from the UE 200 is performed. Specifically, first, the UE 200 transmits an attach request to the eNodeB 100 including information indicating the use of data to be uploaded using the dedicated bearer to be established (step S108). Next, the eNodeB 100 transmits RRC connection reconfiguration to the UE 200 (step S110). Next, the UE 200 transmits RRC connection reconfiguration completion to the eNodeB 100 (step S112).

And UE200 transmits UL data flow corresponding to the said dedicated bearer to eNodeB100 using the established dedicated bearer (step S114). Here, the UL data flow corresponding to the dedicated bearer is data cached as DL cache data or data cached as UL cache data corresponding to the information indicating the use included in the attach request in step S108. . Thereafter, the eNodeB 100 transfers the received UL data flow to the MEC server 300 via bearer mapping described later (step S116).

The process shown in FIG. 15 can be regarded as a process in which the data requested by the MEC server 300 is notified by the capability information, and the UE 200 transmits the requested data. Typically, data for DL cache data is required. In this case, the notification of capability information can be regarded as a request for data transmission to the UE 200. Further, it can be said that bearer establishment and data transmission are started from the eNodeB 100.

In addition, the process illustrated in FIG. 15 can be regarded as a process for transmitting data that matches the capability of the MEC server 300 indicated by the capability information, among the data that the UE 200 desires to transmit. Typically, data for UL cache data is transmitted. In this case, the notification of capability information can be regarded as well-known data that can be handled. Moreover, it can be said that bearer establishment and data transmission are started from UE200.

Note that a bearer for transferring data received by the eNodeB 100 from the UE 200 to the MEC server 300 may be established between the eNodeB 100 and the MEC server 300, or any other connection may be established. In this specification, it is assumed that a bearer is established between the eNodeB 100 and the MEC server 300. The first bearer and the bearer established between the eNodeB 100 and the MEC server 300 are associated by bearer mapping described later. The same applies to the second bearer described below.

(3) Second bearer The eNodeB 100 (for example, the communication processing unit 153) performs a second procedure for establishing a second bearer for transferring information stored in the MEC server 300. That is, a bearer for transferring the UL data flow cached in the MEC server 300 from the eNodeB 100 to another device is established by the second procedure. For example, a bearer for transmitting UL cache data to the P-GW may be established. When the MEC server 300 is provided in the eNodeB 100, the second bearers are the S1 bearer and the S5 bearer. Further, for example, a bearer for transmitting DL cache data to the UE 200 may be established. When the MEC server 300 is provided in the eNodeB 100, the second bearer is a radio bearer.

The eNodeB 100 (for example, the communication processing unit 153) performs the first procedure and the second procedure separately. That is, the first bearer and the second bearer are established separately. Thereby, for example, the bearer up to the MEC server and the bearer from the MEC server to the server on the PDN are established separately. Therefore, for example, it is possible to prevent an increase in signaling on the core network side, which occurred when MTC terminals uploaded data to the MEC server all at once.

Here, the eNodeB 100 (for example, the communication processing unit 153) may perform the first procedure and the second procedure at intervals. For example, the eNodeB 100 establishes the first bearer by the first procedure and acquires the UL cache data, establishes the second bearer at an interval, and transfers the UL cache data to the server on the PDN. Also good. By providing such an interval, it becomes possible to establish a bearer and transfer UL cache data at an appropriate timing such as a timing when there is a margin in the transmission capacity in the core network. The same applies to DL cache data.

The procedure for establishing the second bearer can follow the existing attach procedure. This procedure may involve the eNodeB 100 (for example, the communication processing unit 153) and related entities. Hereinafter, an example of the procedure for establishing the first bearer will be described with reference to FIG.

FIG. 16 is a sequence diagram showing an example of the flow of the second bearer establishment process executed in the system 1 according to the present embodiment. The eNodeB 100, MME, S-GW, P-GW and PCRF are involved in this sequence. In this sequence, the exchange between the eNodeB and the UE is omitted from the procedure for establishing a dedicated bearer starting from the PCRF shown in FIG.

Specifically, first, the PCRF transmits an IP-CAN session change start to the P-GW (step S202). Next, the P-GW transmits a dedicated bearer generation request to the S-GW (step S204), and the S-GW transmits the message to the MME (step S206). Next, the MME transmits a dedicated bearer setup request to the eNodeB (step S208). Next, the eNodeB transmits a dedicated bearer setup response to the MME (step S210). Next, the MME transmits a dedicated bearer generation response to the S-GW (step S212), and the S-GW transmits the message to the P-GW (step S214). Then, the P-GW transmits an IP-CAN session change end to the PCRF (step S216).

Note that the dedicated bearer is established starting from the PCRF. However, similar to the supplement described with reference to FIG. 11, the eNodeB 100 transmits to the application layer that it wants to create a dedicated bearer, and the application layer informs the QoS necessary for the PCRF, thereby establishing the dedicated bearer starting from the eNodeB 100. Realize.

(4) Bearer Mapping FIG. 17 is a diagram schematically illustrating a data flow according to the present embodiment. As illustrated in FIG. 17, the UL data flow from the UE 200 is transmitted to the MEC server 300A (MEC Server for DL Cache) for DL cache data or the MEC server 300B (MEC Server for UL Cache) for UL cache data by the eNodeB 100. Transferred. The UL data flow transferred and cached to the MEC server 300A for DL cache data is then transferred to the UE. Further, the UL data flow transferred and cached to the MEC server 300B for UL cache data is then transferred to the original server (that is, the original application server) 60 on the PDN.

The MEC server 300A for DL cache data and the MEC server 300B for UL cache data may actually be one MEC server 300. However, logically dividing the search location of the cache data (for example, http data) contributes to an improvement in the hit rate of the content cache and prevents, for example, a mistake between UL cache data and DL cache data.

As described above, the first bearer is established for each use (for example, for uploading data cached as DL cache data or for uploading data cached as UL cache data). The identification information of the first bearer is associated with this application. The UE 200 (for example, the communication processing unit 243) transmits a UL data flow using a radio bearer to which identification information corresponding to the application is assigned. And eNodeB100 (for example, the communication process part 153) switches the MEC server 300 of the transfer destination of the information acquired from UE200 based on the identification information of a 1st bearer. That is, the eNodeB 100 identifies the usage of the UL data flow acquired from the UE 200 based on the identification information of the radio bearer used for uploading, and corresponds to the usage (that is, for DL cache data or for UL cache data). Transfer to the MEC server 300.

The transfer destination switching based on the bearer identification information is performed in the same manner for the second bearer. That is, the second bearer is established for each use (for example, for transferring DL cache data or for transferring UL cache data), and the identification information of the second bearer is associated with this use. The eNodeB 100 (for example, the communication processing unit 153) uses the bearer to which the identification information corresponding to the application is assigned to the data acquired from the MEC server 300 (that is, DL cache data or UL cache data). -Transfer to GW.

4 types of bearers can be established between the eNodeB 100 and the MEC server 300. The first type is a bearer for inputting data cached as DL cache data to the MEC server 300. The second type is a bearer for inputting data cached as UL cache data to the MEC server 300. The third type is a bearer for outputting DL cache data to the eNodeB 100. The fourth type is a bearer for outputting UL cache data to the eNodeB 100. The identification information assigned to them is “IMAS (Input MEC Application Server) ID for DL Cache”, “IMAS ID for UL Cache”, “OMAS (Output MEC Application Server) ID for DL Cache”, and “OMAS ID for UL”. Cache ”. The former two may be collectively referred to as IMAS ID, and the latter two may be collectively referred to as OMAS ID. Note that the identification information can be assigned to these bearers by the eNodeB 100.

The switching of the transfer destination by the eNodeB 100 (for example, the communication processing unit 153) can be realized by bearer mapping regarding these four types of bearers.

First, input to the MEC server 300 will be described. The eNodeB 100 (for example, the communication processing unit 153) uses the bearer to which the identification information corresponding to the same application is assigned to the MEC server 300 using the data received by the first bearer to which the identification information corresponding to the application is assigned. Forward to. Through such bearer mapping, data cached as UL cache data is transferred to the MEC server 300 for UL cache data. Similarly, data cached as DL cache data is transferred to the MEC server 300 for DL cache data. In this way, the MEC server 300 (for example, the content processing unit 333) acquires and caches data from the UE 200.

Next, output from the MEC server 300 will be described. The MEC server 300 (for example, the content processing unit 333) transmits the content cached in the MEC server 300 (that is, UL cache data or DL cache data) to the eNodeB 100 using a bearer corresponding to the application. The eNodeB 100 (for example, the communication processing unit 153) transmits the acquired data using the second bearer to which identification information corresponding to the same application is assigned. Through such bearer mapping, UL cache data is transferred to the server on the PDN, and DL cache data is transferred to the UE 200.

In the following, bearer mapping related to input to the MEC server 300 will be described first with reference to FIGS. 18 and 19.

FIG. 18 is an explanatory diagram for explaining bearer mapping executed in the eNodeB 100 according to the present embodiment. The identification information assigned to the radio bearer established for uploading data cached as DL cache data is “UL RB ID for DL Cache”. Also, the identification information assigned to the radio bearer established for uploading data cached as UL and cache data is “UL RB ID for UL Cache”. In addition, the identification information assigned to the radio bearers constituting the normal EPS bearer is “UL RB ID for EPS”. As illustrated in FIG. 18, the eNodeB 100 maps “UL RB ID for DL Cache” to “IMAS ID for DL Cache”, and transfers the data transmitted from the UE 200 to the MEC server 300A for DL cache data. Further, the eNodeB 100 maps “UL RB ID for UL Cache” to “IMAS ID for UL Cache”, and transfers the data transmitted from the UE 200 to the MEC server 300B for UL cache data. Further, the eNodeB 100 maps “UL RB ID for EPS” to “UL S1 TEID” and transfers the data transmitted from the UE 200 to the S-GW.

FIG. 19 is a flowchart illustrating an example of a flow of determination processing performed in the eNodeB 100 for the bearer mapping illustrated in FIG. As shown in FIG. 19, first, the eNodeB 100 determines whether “UL RB ID” is bearer identification information for uploading data to be cached (step S302). The bearer identification information for uploading cached data is “UL RB ID for DL Cache” and “UL RB ID for UL Cache”. When it is determined that the “UL RB ID” is identification information of a bearer for uploading cached data (step S302 / YES), the eNodeB 100 stores data in which the “UL RB ID” is cached as DL cache data. It is determined whether it is the bearer identification information for uploading (ie, “UL RB ID for DL Cache”) (step S304). If it is determined that the identification information is a bearer for uploading data cached as DL cache data (step S304 / YES), the eNodeB 100 maps to “IMAS ID for DL Cache” (step S306). On the other hand, when it is determined that it is not the identification information of the bearer for uploading data cached as DL cache data (step S304 / NO), the eNodeB 100 maps to “IMAS ID for UL Cache” (step S308). . When it is determined that “UL RB ID” is not identification information of a bearer for uploading cached data (step S302 / NO), the eNodeB 100 maps to “UL S1 TEID” (step S310).

The bearer mapping related to the input to the MEC server 300 has been described above. Next, bearer mapping regarding output from the MEC server 300 will be described with reference to FIGS.

FIG. 20 is an explanatory diagram for explaining bearer mapping executed in the eNodeB 100 according to the present embodiment. As illustrated in FIG. 20, the eNodeB 100 maps “OMAS ID for DL Cache” to “DL RB ID” and transfers data transmitted from the MEC server 300A for DL cache data to the UE 200. In addition, the eNodeB 100 maps “OMAS ID for UL Cache” to “UL S1 TEID” and transfers the data transmitted from the MEC server 300B for UL cache data to the S-GW.

FIG. 21 is a flowchart illustrating an example of a flow of determination processing performed in the eNodeB 100 for the bearer mapping illustrated in FIG. As shown in FIG. 21, first, the eNodeB 100 determines whether or not “OMAS ID” is bearer identification information for DL cache data (ie, “OMAS ID for DL Cache”) (step S402). . When it is determined that the identification information of the bearer for the DL cache data (step S402 / YES), the eNodeB 100 maps to “DL RB ID” (step S404). On the other hand, when it is determined that it is not bearer identification information for DL cache data (step S402 / NO), the eNodeB 100 maps to “UL S1 TEID” (step S406).

The bearer mapping related to the output from the MEC server 300 has been described above.

As described above, since the transfer destination is switched by bearer mapping, the inspection of the HTTP header in the application layer becomes unnecessary, and the processing load of the eNodeB 100 is reduced. In addition, the timing for transferring the UL cache data to the original server and the timing for establishing the bearers (S1 bearer and S5 bearer) are determined in the layer handling the bearers. This can prevent a decrease in efficiency due to the judgment related to the operation of the EPC depending on the analysis result of the HTTP header in the application layer. It is desirable that the EPC operation is determined in a layer that handles EPS bearers, and it can be said that switching of the transfer destination by bearer mapping is reasonable.

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

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

Further, for example, the terminal device 200 is a smartphone, a tablet PC (Personal Computer), a notebook PC, a portable game terminal, a mobile terminal such as a portable / dongle type mobile router or a digital camera, or an in-vehicle terminal such as a car navigation device. It may be realized as. The terminal device 200 may be realized as a terminal (also referred to as an MTC (Machine Type Communication) terminal) that performs M2M (Machine To Machine) communication. Furthermore, at least a part of the components of the terminal device 200 may be realized in a module (for example, an integrated circuit module configured by one die) mounted on these terminals.

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

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

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

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

In the server 700 illustrated in FIG. 22, one or more components (notification unit 331 and / or content processing unit 333) included in the processing unit 330 described with reference to FIG. 14 may be implemented in the processor 701. Good. As an example, a program for causing a processor to function as the one or more components (in other words, a program for causing the processor to execute the operation of the one or more components) is installed in the server 700, and the processor 701 is The program may be executed. As another example, the server 700 may include a module including the processor 701 and the memory 702, and the one or more components may be mounted in the module. In this case, the module may store a program for causing the processor to function as the one or more components in the memory 702 and execute the program by the processor 701. As described above, the server 700 or the module may be provided as an apparatus including the one or more components, and the program for causing a processor to function as the one or more components may be provided. . In addition, a readable recording medium in which the program is recorded may be provided.

Further, in the server 700 shown in FIG. 22, the communication unit 310 described with reference to FIG. 14 may be implemented in the network interface 704. Further, the storage unit 320 may be implemented in the memory 702 or the storage 703.

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

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

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

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

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

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

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

In the eNB 800 illustrated in FIG. 23, one or more components (notification unit 151 and / or communication processing unit 153) included in the processing unit 150 described with reference to FIG. 12 are implemented in the wireless communication interface 825. Also good. Alternatively, at least some of these components may be implemented in the controller 821. As an example, the eNB 800 includes a module including a part (for example, the BB processor 826) or all of the wireless communication interface 825 and / or the controller 821, and the one or more components are mounted in the module. Good. In this case, the module stores a program for causing the processor to function as the one or more components (in other words, a program for causing the processor to execute the operation of the one or more components). The program may be executed. As another example, a program for causing a processor to function as the one or more components is installed in the eNB 800, and the radio communication interface 825 (eg, the BB processor 826) and / or the controller 821 executes the program. Good. As described above, the eNB 800, the base station apparatus 820, or the module may be provided as an apparatus including the one or more components, and a program for causing a processor to function as the one or more components is provided. May be. In addition, a readable recording medium in which the program is recorded may be provided.

23, the radio communication unit 120 described with reference to FIG. 12 may be implemented in the radio communication interface 825 (for example, the RF circuit 827). Further, the antenna unit 110 may be mounted on the antenna 810. The network communication unit 130 may be implemented in the controller 821 and / or the network interface 823. In addition, the storage unit 140 may be implemented in the memory 822.

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

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

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

The wireless communication interface 855 supports a cellular communication method such as LTE or LTE-Advanced, and provides a wireless connection to a terminal located in a sector corresponding to the RRH 860 via the RRH 860 and the antenna 840. The wireless communication interface 855 may typically include a BB processor 856 and the like. The BB processor 856 is the same as the BB processor 826 described with reference to FIG. 23 except that the BB processor 856 is connected to the RF circuit 864 of the RRH 860 via the connection interface 857. The wireless communication interface 855 includes a plurality of BB processors 856 as illustrated in FIG. 24, and the plurality of BB processors 856 may respectively correspond to a plurality of frequency bands used by the eNB 830, for example. 24 shows an example in which the wireless communication interface 855 includes a plurality of BB processors 856, the wireless communication interface 855 may include a single BB processor 856.

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

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

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

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

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

24, for example, the radio communication unit 120 described with reference to FIG. 12 may be implemented in the radio communication interface 863 (for example, the RF circuit 864). The antenna unit 110 may be mounted on the antenna 840. The network communication unit 130 may be implemented in the controller 851 and / or the network interface 853. The storage unit 140 may be mounted in the memory 852.

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

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

The camera 906 includes, for example, an image sensor such as a CCD (Charge Coupled Device) or a CMOS (Complementary Metal Oxide Semiconductor), and generates a captured image. The sensor 907 may include a sensor group such as a positioning sensor, a gyro sensor, a geomagnetic sensor, and an acceleration sensor. The microphone 908 converts sound input to the smartphone 900 into an audio signal. The input device 909 includes, for example, a touch sensor that detects a touch on the screen of the display device 910, a keypad, a keyboard, a button, or a switch, and receives an operation or information input from a user. The display device 910 has a screen such as a liquid crystal display (LCD) or an organic light emitting diode (OLED) display, and displays an output image of the smartphone 900. The speaker 911 converts an audio signal output from the smartphone 900 into audio.

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

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

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

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

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

The bus 917 connects the processor 901, the memory 902, the storage 903, the external connection interface 904, the camera 906, the sensor 907, the microphone 908, the input device 909, the display device 910, the speaker 911, the wireless communication interface 912, and the auxiliary controller 919 to each other. . The battery 918 supplies power to each block of the smartphone 900 illustrated in FIG. 25 via a power supply line partially illustrated by a broken line in the drawing. For example, the auxiliary controller 919 operates the minimum necessary functions of the smartphone 900 in the sleep mode.

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

25, for example, the wireless communication unit 220 described with reference to FIG. 13 may be implemented in the wireless communication interface 912 (for example, the RF circuit 914). The antenna unit 210 may be mounted on the antenna 916. The storage unit 230 may be mounted in the memory 902.

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

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

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

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

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

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

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

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

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

The battery 938 supplies power to each block of the car navigation device 920 shown in FIG. 26 through a power supply line partially shown by broken lines in the drawing. Further, the battery 938 stores electric power supplied from the vehicle side.

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

In the car navigation device 920 shown in FIG. 26, for example, the wireless communication unit 220 described with reference to FIG. 13 may be implemented in the wireless communication interface 933 (for example, the RF circuit 935). The antenna unit 210 may be mounted on the antenna 937. Further, the storage unit 230 may be implemented in the memory 922.

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

<< 5. Summary >>
The embodiment of the present disclosure has been described in detail above with reference to FIGS. As described above, the eNodeB 100 broadcasts the capability information of the MEC server 300 provided in the EPS and providing the content to the terminal device 200 using the system information. Thereby, the terminal device 200 can upload data to the MEC server 300 using an appropriate bearer, and the MEC server 300 can appropriately cache the uploaded data. More specifically, the terminal device 200 can upload data using the first bearer to which identification information corresponding to the application is assigned. And eNodeB100 can transfer the uploaded data to the appropriate MEC server 300 by performing bearer mapping based on the identification information of a bearer.

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

For example, in the above embodiment, the eNodeB has been described as performing bearer mapping, but the present technology is not limited to such an example. For example, as shown in FIG. 4, when the MEC server is provided in the S-GW, the S-GW may perform bearer mapping. In this case, the processing unit 150 is included in the S-GW. The same applies to any entity other than the S-GW.

In the above-described embodiment, the relationship between the procedure for establishing the first bearer and the second bearer and the procedure for establishing the bearer between the eNodeB 100 and the MEC server 300 is not particularly mentioned. These procedures may be performed integrally or separately. In the former case, a bearer for transferring data from the eNodeB 100 to the MEC server 300 is established in the first procedure described above. In this case, it can also be understood that the first bearer includes a bearer for transferring data from the eNodeB 100 to the MEC server 300. Further, in the second procedure described above, a bearer for transmitting data from the MEC server 300 to the eNodeB 100 is established. In this case, it can be understood that the second bearer includes a bearer for transmitting data from the MEC server 300 to the eNodeB 100. On the other hand, in the latter case, a bearer for transferring data from the eNodeB 100 to the MEC server 300 is established at an arbitrary timing before or after the first procedure described above. Further, a bearer for transmitting data from the MEC server 300 to the eNodeB 100 is established at an arbitrary timing before or after the second procedure described above.

In the above embodiment, the UL data flow cache has been mainly described. However, a similar technique can be provided for a DL data flow cache.

In addition, the processes described using the flowcharts and sequence diagrams in this specification do not necessarily have to be executed in the order shown. Some processing steps may be performed in parallel. Further, additional processing steps may be employed, and some processing steps may be omitted.

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

The following configurations also belong to the technical scope of the present disclosure.
(1)
A processing unit that is provided inside an EPS (Evolved Packet System) and provides capability information of an application server that provides content to a terminal device or acquires content from the terminal device, using system information,
A device comprising:
(2)
The said capability information is an apparatus as described in said (1) including the information which shows whether the said application server can memorize | store the information transmitted by the uplink from the said terminal device.
(3)
The apparatus according to (1) or (2), wherein the capability information includes information indicating a use of information stored in the application server.
(4)
The apparatus according to (3), wherein the use is to be transmitted from the application server to the uplink.
(5)
The apparatus according to (3) or (4), wherein the use is to be transmitted from the application server to a downlink.
(6)
The apparatus according to any one of (1) to (5), wherein the capability information includes information indicating a disclosure range.
(7)
The processing unit performs the first procedure for establishing a first bearer for acquiring information to be stored in the application server from the terminal device, according to any one of (1) to (6). Equipment.
(8)
The device according to (7), wherein the first bearer is established for each use of information stored in the application server.
(9)
The apparatus according to (8), wherein in the first procedure, information indicating a use of information transmitted using the first bearer is transmitted from the terminal apparatus.
(10)
The apparatus according to (9), wherein the information indicating the use is included in an attach request.
(11)
The processing unit according to any one of (8) to (10), wherein the processing unit switches the application server that is a transfer destination of information acquired from the terminal device based on identification information of the first bearer. apparatus.
(12)
The apparatus according to (11), wherein the identification information of the first bearer is associated with the application.
(13)
The apparatus according to any one of (7) to (12), wherein the processing unit performs a second procedure for establishing a second bearer for transferring information stored in the application server.
(14)
The apparatus according to (13), wherein the processing unit performs the first procedure and the second procedure at an interval.
(15)
A processing unit that transmits data based on capability information of an application server that is broadcasted using system information and that is provided in the EPS and provides content to the terminal device or acquires content from the terminal device;
A device comprising:
(16)
An apparatus provided inside the EPS,
A processing unit that provides content to a terminal device or acquires content from the terminal device;
A notification unit for notifying the base station of its capability information broadcast using system information;
An apparatus comprising:
(17)
Broadcasting capability information of an application server provided in the EPS and providing content to the terminal device or acquiring content from the terminal device using the system information by the processor;
Including methods.
(18)
Transmitting data by a processor based on capability information of an application server that is broadcast using system information and that provides content to or obtains content from a terminal device provided within an EPS;
Including methods.
(19)
Providing content to a terminal device or obtaining content from the terminal device;
Notifying the base station of its capability information broadcast using system information;
A method performed by a device provided within the EPS, comprising:
(20)
A computer installed inside the EPS
A processing unit that provides content to a terminal device or acquires content from the terminal device;
A notification unit for notifying the base station of its capability information broadcast using system information;
Program to function as.

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 notification unit 153 communication processing unit 200 terminal device, UE
210 Antenna unit 220 Wireless communication unit 230 Storage unit 240 Processing unit 241 Acquisition unit 243 Communication processing unit 300 Server 310 Communication unit 320 Storage unit 330 Processing unit 331 Notification unit 333 Content processing unit

Claims

A processing unit that is provided inside an EPS (Evolved Packet System) and provides capability information of an application server that provides content to a terminal device or acquires content from the terminal device, using system information,
A device comprising:
The apparatus according to claim 1, wherein the capability information includes information indicating whether or not the application server can store information transmitted on the uplink from the terminal apparatus.
The apparatus according to claim 1, wherein the capability information includes information indicating a use of information stored in the application server.
The apparatus according to claim 3, wherein the use is to be transmitted from the application server to the uplink.
The apparatus according to claim 3, wherein the use is to be transmitted from the application server to a downlink.
The apparatus according to claim 1, wherein the capability information includes information indicating a disclosure range.
The apparatus according to claim 1, wherein the processing unit performs a first procedure for establishing a first bearer for acquiring information to be stored in the application server from the terminal device.
The apparatus according to claim 7, wherein the first bearer is established for each use of information stored in the application server.
The apparatus according to claim 8, wherein in the first procedure, information indicating a use of information transmitted using the first bearer is transmitted from the terminal apparatus.
The apparatus according to claim 9, wherein the information indicating the use is included in an attach request.
The device according to claim 8, wherein the processing unit switches the application server to which the information acquired from the terminal device is transferred based on the identification information of the first bearer.
The apparatus according to claim 11, wherein the identification information of the first bearer is associated with the application.
The apparatus according to claim 7, wherein the processing unit performs a second procedure for establishing a second bearer for transferring information stored in the application server.
14. The apparatus according to claim 13, wherein the processing unit performs the first procedure and the second procedure at an interval.
A processing unit that transmits data based on capability information of an application server that is broadcasted using system information and that is provided in the EPS and provides content to the terminal device or acquires content from the terminal device;
A device comprising:
An apparatus provided inside the EPS,
A processing unit that provides content to a terminal device or acquires content from the terminal device;
A notification unit for notifying the base station of its capability information broadcast using system information;
An apparatus comprising:
Broadcasting capability information of an application server provided in the EPS and providing content to the terminal device or acquiring content from the terminal device using the system information by the processor;
Including methods.
Transmitting data by a processor based on capability information of an application server that is broadcast using system information and that provides content to or obtains content from a terminal device provided within an EPS;
Including methods.
Providing content to a terminal device or obtaining content from the terminal device;
Notifying the base station of its capability information broadcast using system information;
A method performed by a device provided within the EPS, comprising:
A computer installed inside the EPS
A processing unit that provides content to a terminal device or acquires content from the terminal device;
A notification unit for notifying the base station of its capability information broadcast using system information;
Program to function as.