The SCEF disclosed in Non Patent Literature 1 is disposed in a core network, and has an interface or a reference point for communicating with an application server. Thus, inflow of a large amount of data from the application server into the core network can be prevented by performing traffic control independently defined by the SCEF. As a result, consumption of a large amount of a resource in the core network can be prevented. However, in the traffic control independently implemented by the SCEF, the SCEF determines, based on the independent definition, transmission refusal of data generated by the application server, and therefore, there is a possibility that the application server performs retransmission of data. As a result, there is a concern that a further increase in traffic is incurred. On the other hand, even when data are transmitted from a communication terminal to the application server, information relating to the traffic control independently defined by the SCEF is previously sent to the communication terminal. Thus, inflow of a large amount of data from the communication terminal into the core network can be prevented. As a result, consumption of a large amount of a resource in the core network can be prevented. However, independent traffic control implemented by the communication terminal is only determination, by the communication terminal, of transmission refusal of data to be transmitted as an application. In this case, a service itself provided by the application may not function normally. Hence, a related art disclosed in Non Patent Literature 1 has a problem that traffic or a data amount transferred on the core network is not controlled in consideration of a traffic characteristic of an application operating between the application server and the communication terminal.