Technical field
[0001]
　The present invention relates to communication technology small data.
Background technique
[0002]
　Currently, in 3GPP (3rd Generation Partnership Project), study of the communication system is being carried out for housing a large number of IoT (Internet of Things) device.
[0003]
　IoT devices, for example, the Internet connected sensor device, a smart meter may be a home appliance, or a vending machine or the like. Furthermore, IoT device may be referred to as MTC (Machine Type Communication) device or M2M (Machine to Machine) device or the like. For example, IoT device, general mobile phone or a smart phone or the like is periodically sent to the server device or the like very little volume of data compared to the data to be communicated. For example, IoT device, data of about several tens of bytes may be an apparatus for periodically sending.
CITATION
Non-Patent Document
[0004]
Non-Patent Document 1: 3GPP TS 25.331 V12.5.0 (2015-03 ) 8.1.3 RRC connection establishment
Non-Patent Document 2: 3GPP TS 23.401 V13.3.0 (2015-06 ) 5.3.2 Attach procedure
Summary of the Invention
Problems that the Invention is to Solve
[0005]
　Against IoT devices, it is desired to operate a long time by realizing power saving. For example, a company, when managing a large number of IoT devices, the number of times in terms of management cost charging operation and battery replacement or the like of the battery, it is desirable that small. However, in a communication system defined currently in 3GPP, for example, as specified in non-patent documents 1 and 2, communication is assumed to accommodate a predominantly mobile phone or smartphone procedure is defined. Mobile phone or a smart phone, etc., IoT devices frequently send and receive data of large data capacity than the data to be transmitted. That is, a problem that a communication system that is currently defined in 3GPP is not a optimal communication system for accommodating the IoT devices are desired power saving can not be realized power savings of IoT device there is.
[0006]
　An object of the present invention, a network device capable of performing the communication procedure suitable for receiving the IoT device, communication terminal, communication system, receiving method is to provide a transmission method, and a program.
Means for Solving the Problems
[0007]
　Network device according to the first aspect of the present invention includes a communication unit that receives the profile information of the communication terminal transmitted from the communication terminal, the procedure for establishing the communication terminal and the wireless link, depending on the profile information , and a determination section for determining whether or not to omit at least one of the security setup procedure between the user configuration instructions of the radio resources used for data communication, and the communication terminal in between the communication terminal wherein the communication unit is configured to receive the small data transmitted from the communication terminal via the wireless link.
[0008]
　Communication terminal according to the second aspect of the present invention includes a communication unit for transmitting the profile information of the own terminal to the network device, from said network device, in the procedure of establishing the network device and the wireless links, according to the profile information Te, receiving information about whether it is possible to omit the setting procedure of radio resource used for communication of user data, and at least one of the security setup procedure between the network device between the said network device comprising a receiving unit for the said communication unit is for transmitting a small data to the network device via the wireless link.
[0009]
　Communication system according to a third aspect of the present invention, the core network for controlling a communication terminal, a base station that performs the communication terminal and the wireless communication, the establishment procedure of the wireless link between the communication terminal and the base station and a device, the core network device receives the profile information of the communication terminal transmitted from said communication terminal, the establishment procedure of the radio link used for communication of user data in between the communication terminal send setting procedure of radio resources, and an indication message indicating to omit at least one of the security setup procedure between the communication terminal to the base station, the base station, in response to the instruction message, setting procedure of radio resource used for communication of user data in between the communication terminals, and between the communication terminal Omitted at least one of Kyuriti configuration steps to perform the establishment procedure of the radio link, the communication terminal is configured to transmit the small data to the base station over the wireless link.
[0010]
　Receiving method according to a fourth aspect of the present invention is a procedure for receiving the profile information of the communication terminal transmitted from the communication terminal, establishing the communication terminal and the radio link, according to the profile information, the communication setting procedure of radio resource used for communication of user data between the terminals, and determines whether to omit at least one of the security setup procedure between the communication terminal, wherein via said wireless link it is intended to receive the small data transmitted from the communication terminal.
[0011]
　Transmission method according to a fifth aspect of the present invention transmits the profile information of the own terminal to the network device, from said network device, in the procedure of establishing the network device and the wireless links, according to the profile information, the receives information about whether it is possible to omit the setting procedure of radio resource used for communication of user data, and at least one of the security setup procedure between the network device between the network devices, wherein via a radio link is to transmit a small data to the network device.
[0012]
　Program according to a sixth aspect of the present invention receives the profile information of the communication terminal transmitted from the communication terminal, the procedure for establishing the communication terminal and the radio link, according to the profile information, the communication terminal at least one of determining whether to omit the communication via the radio link of the security setup procedure between the user configuration instructions of the radio resources used for data communication, and the communication terminal between the it is intended to execute to receive the small data transmitted from the terminal to the computer.
Effect of the invention
[0013]
　The present invention can provide a network device which can perform a communication procedure suitable for receiving the IoT device, communication terminal, communication system, receiving method, transmission method, and a program.
BRIEF DESCRIPTION OF THE DRAWINGS
[0014]
It is a configuration diagram of a network device according to [1] Embodiment 1.
FIG. 2 is a configuration diagram of a communication system according to the second embodiment.
3 is a block diagram of a UE according to the second embodiment.
4 is a diagram for explaining a category information according to the second embodiment.
5 is a configuration diagram of a MME according to the second embodiment.
6 is a block diagram of an eNB according to the second embodiment.
7 is a diagram showing the flow of the Attach process according to the second embodiment.
8 is a diagram showing the flow of transmission processing of small data according to the second embodiment.
9 is a diagram illustrating the establishment procedure of a radio link are defined in 3GPP.
Is a diagram illustrating the establishment procedure of a radio link are defined in FIG. 10] 3GPP.
11 is a block diagram of an eNB according to the respective embodiments.
12 is a configuration diagram of a communication terminal and a UE according to the embodiments.
13 is a configuration diagram of a network device and a MME according to the respective embodiments.
DESCRIPTION OF THE INVENTION
[0015]
　(Embodiment 1)
　Hereinafter, with reference to the drawings will be described embodiments of the present invention. Introduction configuration of a network device 10 according to the first embodiment of the present invention will be described with reference to FIG. Network device 10 may be a computer system that operates by the processor executing the program stored in the memory. For example, the network device 10 may be a device communication carrier is arranged on the communication network to be managed. Network device 10 includes a base station, a server device may be a communication device of the exchange and the like. Or, the network device 10 may be a router device or the like.
[0016]
　Network device 10 includes a communication unit and a (Note that the communication unit is transmitting and may translate into the receiving portion) 11 and a determination section 12. A component which is a communication unit 11 and the judging unit of the network device 1012, the processor may be a software or module operates by executing a program stored in the memory. Or, the components of network device 10 may be a hardware or chips.
[0017]
　The communication unit 11 receives the profile information of the communication terminal 20 transmitted from the communication terminal 20. Communication terminal 20 may be a IoT devices running autonomously communicate without user operation. IoT devices, M2M (Machine to Machine) device or MTC (Machine Type Communication) may be a device or the like. Further, the communication terminal 20, the Internet connected sensor device, a smart meter may be a home appliance, or a vending machine or the like. In addition, the data that IoT device sends a small data. Small data, since the transmission capacity is small, it can also be transmitted in a radio resource control data. Therefore, when transmitting using the radio resource control data the small data, the radio resources for user data becomes unnecessary.
[0018]
　Profile information of the communication terminal 20 may be information processing and the like is defined to be executed in the operation or the communication terminal 20 of the communication terminal 20.
[0019]
　Determination unit 12, the procedure for establishing a communication terminal 20 and radio link in accordance with the profile information transmitted from the communication terminal 20, the setting procedure and the radio resource used for communication of the user data between the communication terminal 20 It determines whether to omit at least one of the security setup procedure between the communication terminal 20.
[0020]
　Network device 10, when performing the communication terminal 20 and radio communication, establishes a wireless link between the communication terminal 20. For example, the network device 10, a timing source of the communication terminal 20 transitions from OFF state to ON state, the predetermined period, or the communication terminal 20 is a wireless link between the communication terminal 20 to the time of data transmission Establish.
[0021]
　Establishment of the radio link is performed according to a predetermined procedure. A predetermined procedure may be defined by the wireless service provider that manages the network device 10. Or, a defined procedure previously, it may be defined in 3GPP or the like. Also, establishment of the radio link may be paraphrased as setting of set or wireless communication line radio bearer.
[0022]
　Radio resources used and the communication of the user data (transmission and reception), for example, a user data between the communication terminal 20 with the network device 10, text data, to send and receive voice data or image data, etc. it may be a wireless channel used. The radio resource is a frequency band allocated to the communication terminal 20 to communicate, it may be a communication timing or transmission power, etc.,. To communicate user data, usually, U-Plane (User Plane) is used.
[0023]
　The radio resource used for communication of the user data, there radio resource used for communication of control data. Control data, the communication terminal 20 starts communication is data used to terminate or maintain. Generally, control data, data capacity is less data in comparison with the user data. The communication of control data, typically, C-Plane (Control Plane) is used.
[0024]
　For example, the determination unit 12, the profile information of the communication terminal 20, when the communication terminal 20 is shown not to transmit and receive user data, may be omitted setup procedure of a radio resource used for communication of user data . Furthermore, the determination unit 12, the profile information of the communication terminal 20, when the communication terminal 20 is shown not to require high security, may be omitted security setting procedure.
[0025]
　Here, the communication unit 11 via a radio link established on the basis of the result of the judgment made by the judging unit 12, receives the small data transmitted from the communication terminal 20. Small data is, for example, data IoT device generates. Small data is data of sufficiently small capacity compared with the user data, such as call or image. For example, small data, sensor data, or regular small capacity to be transmitted to the network device 10 (e.g., about several tens of bytes) may be data or the like. The communication unit 11 also performs data transmission to the communication terminal 20 from the network device 10. Determination unit 12 determines from the capacity of the small data is small, and its small data rather than radio resources for user data communication (U-Plane), and can communicate with radio resource control data communication (C-Plane) If it can be omitted setting procedure of radio resources for user data communication. Further, since a small data, if you do not require high security, the determination unit 12 may be omitted setting procedure of security.
[0026]
　As described above, the network device 10 in accordance with the profile information of the communication terminal 20, it is possible to change the procedure for establishing a communication terminal 20 and the radio link. Specifically, the network device 10 may be in accordance with the profile information, omit some steps in establishing communication terminal 20 and the radio link.
[0027]
　Communication terminal 20, when establishing a network device 10 and the radio link, by some of the procedures are omitted, it is possible to reduce the power consumption. Thus, the frequency of battery replacement or the like of the communication terminal 20 can be reduced. Therefore, even when one of the companies or organizations are connected a number of communication terminal 20 to the network device 10, it is possible to suppress an increase in costs associated with battery replacement of the communication terminal 20.
[0028]
　(Second Embodiment)
　Subsequently, a configuration example of a communication system according to Embodiment 2 of the present invention will be described with reference to FIG. Communication system of FIG. 2 is constituted by a node device as defined in 3GPP.
[0029]
　UE (User Equipment) 30 is used as a general term for a communication terminal in 3GPP. UE30 corresponds to the communication terminal 20 of FIG. 1. In the following description the UE30 as IoT devices.
[0030]
　The base station apparatus eNB (evolved NodeB) 40 performs UE30 and wireless communications. For example, eNB 40 performs UE30 and wireless communication using the LTE (Long Term Evolution) as a wireless communication system. Further, eNB 40 relays the control data to be transmitted and received between the mobile management device MME (Mobility Management Entity) 50 and UE 30. Incidentally, eNB can, CIoT (Cellular IoT) RAN for (Radio Access Network) and RNC (Radio Network Controller), may be a BSC (Base Station Controller) and the like. Further, MME, the mobile management device and a packet switch for CIoT, may be a SGSN or the like. Further, UE is, 2G wireless technology, 3G wireless technology may be a terminal that communicates with the LTE radio technology or CIoT dedicated wireless technology.
[0031]
　MME50 the mobility management of the UE 30, performs setting processing such as authentication and the user data transfer path. MME50 relays control data exchanged between the eNB40 and SGW (Serving Gateway) 60. MME50 or eNB40 corresponds to the network device 10 of FIG. Or functions provided to the network device 10 may be disposed dispersed in MME50 and eNB 40.
[0032]
　SGW60 receives control data relating to UE30 transmitted from MME50. Furthermore, SGW60 sets a communication path for transmitting user data related to UE30 between PGW (Packet Data Network Gateway) 70. SGW60 receives the small data transmitted in the resource of the control data communication through MME50 from UE30 (C-Plane). SGW60 is a small data received using the C-Plane, or transmits to the PGW70 using the user data resources for communication (U-Plane). Further, SGW60 may transmit to MME50 the small data relating UE30 transmitted from PGW70 in C-Plane.
[0033]
　PGW70 transmits the user data to the UE30 transmitted from IoT server 80 or the like destined to SGW60. Further, PGW70 transmits small data transmitted from SGW60 to IoT server 80 or the like. Here, MME50, SGW60 and PGW70 may be referred to as EPC as defined in 3GPP (Evolved Packet Core). Further, MME50, SGW60 and PGW70 may be referred to as a core network device.
[0034]
　IoT server 80 may be a server company or the like different from the communication carrier that manages the EPC manages, may be a server communication carrier that manages the EPC manages. The IoT server 80 and PGW70, may communicate via the Internet is a public IP network. IoT server 80 manages the UE30 used as IoT device. Furthermore, IoT server 80 receives the small data transmitted from the UE30 used as IoT device may analyze such small data.
[0035]
　Next, an example of the configuration of the UE30 according to the second embodiment of the present invention will be described with reference to FIG. UE30 includes a IoT application 31, NAS (Non-Access Stratum) control unit 32, AS (Access Stratum) control unit 33, U-Plane (User-Plane) control unit 34 and the wireless communication unit 35,. Each component constituting the UE30, the processor may be a software or modules such as processing by executing a program stored in the memory is executed. Or, the components constituting the UE30 may be hardware or chips.
[0036]
　IoT application 31 generates a small data to be transmitted to the IoT server 80. Here, a specific example of small data. For example, UE 30 is, if a smart meter, IoT application 31, as small data may generate data indicating an amount of electric power used. Furthermore, UE 30 is temperature, when a sensor device for detecting the humidity, and the like, IoT application 31, as small data may generate data indicating the detected temperature or humidity. That in addition, the small data may be information such as information or UE30 UE30 managed has been detected.
[0037]
　NAS control unit 32 generates a NAS message to be transmitted and received between the MME50 through the eNB 40. Furthermore, NAS control unit 32 receives the NAS message sent via the eNB40 from MME50, executes the processing specified in the NAS message. eNB40 without executing the processing related NAS message, transmits a NAS message received to UE30 or MME50. In other words, eNB 40 is transmitted through transfer NAS message sent from UE30 or MME50. Incidentally, NAS message is a control data.
[0038]
　NAS control unit 32 generates a NAS message including profile information about the UE 30. Furthermore, NAS control unit 32, when transmitting using the C-Plane with the control data to small data, generates a NAS message including the small data.
[0039]
　AS control unit 33 generates an AS messages transmitted and received between the eNB 40. Furthermore, AS control unit 33 receives the AS message transmitted from eNB 40, it executes the processing specified in the AS message. AS control unit 33 generates an AS message including profile information about the UE 30.
[0040]
　U-Plane control unit 34 executes a process for establishing a communication line or channel is used to transmit and receive user data between the eNB 40. Here, it may be referred to as the combined NAS controller 32 and the AS control unit 33 C-Plane (Control-Plane) controller (not shown). C-Plane control unit executes a process for establishing a communication line or channel is used to transmit and receive control data between the eNB 40.
[0041]
　The wireless communication unit 35 executes processing for performing eNB40 and wireless communications. For example, wireless communication unit 35, a signal including the transmission data and generates a radio signal by modulating a desired frequency, and transmits the generated wireless signal to the eNB 40. Or, the radio communication unit 35 demodulates a radio signal transmitted from the eNB 40, and outputs the demodulated signal to the NAS controller 32, AS controller 33 or U-Plane control unit 34.
[0042]
　Here will be described the profile information included in the NAS message or AS message. Profile information UE 30 may be information processing and the like is defined to be executed in the operation and contract information or UE 30, the UE 30.
[0043]
　For example, the UE30 profile information is IoT devices may contain the following information. Further, the following information UE30 is may be information that is set each time to send small data.
(1) for transmission by using also the C-Plane and the control data small data, information indicating that unnecessary the Traffic Channel for transmitting user data (U-Plane) (hereinafter, the Traffic Channel unnecessary information shown)
(2) information indicative of a request for a lower security level than that used in a general smartphone (hereinafter, low-security request information indicating a)
to (3) UE 30 does not move, the handover process information indicating that the required (hereinafter, referred to as handover processing unnecessary information)
[0044]
　(1) Traffic Channel unnecessary information in may be information indicating the amount of information of small data (size). In this case, the amount of information (Size) eNB 40 or MME50 the reference small data performs Traffic Channel (U-Plane) must determine whether or not. The low security level in (2) may be, for example, by performing an encryption unnecessary or simple level encryption small data.
[0045]
　Further, the handover processing in (3), the handover process between base stations using the same radio communication scheme (Intra RAT (Radio Access Technology) HO (Hand Over)) and handover process between base stations using different radio communication systems including the (Inter RAT HO (Hand Over)).
[0046]
　Further, the profile information, whether to transmit using a C-Plane as control data the small data, whether to request a low security level, further, whether unnecessary handover process, the UE30 category information of the show may be set.
[0047]
　For example, the category information of the UE30, as shown in FIG. 4, may be indicated using a bit sequence of 3 bits. When transmitting with a small data C-Plane (Control Plane) "1", it sets the small data in the first bit to "0" when transmitting using the U-Plane (User Plane). Furthermore, when requesting a low security level "1" is set to 2 bit "0" if requiring high security level. Further, when the unnecessary handover process "1" is set to the third bit "0" if you require handover process. UE30 category information is not limited to the example of FIG. 4, according to the number of information to be set, 4 or more bits or 2 bits or less bit string may be used. Incidentally, "0", "1" may be referred to as the presence or absence of the flag.
[0048]
　Next, an example of the configuration of the MME50 according to a second embodiment of the present invention will be described with reference to FIG. MME50 has a base station communication unit 51, determination unit 52, the control unit 53 and the network communication unit 54,. Each component constituting the MME50, the processor may be a software or modules such as processing by executing a program stored in the memory is executed. Or, the components constituting the MME50 can be a hardware or chips.
[0049]
　Base station communication unit 51 receives the NAS message sent by UE30 via the eNB 40. Base station communication unit 51 outputs the NAS message received to the decision unit 52. The base station communication unit 51, if they contain small data in the NAS message may output the small data to the network communication unit 54. The base station communication unit 51 receives the S1 message sent from the eNB 40. Incidentally, S1 is a reference point defined by the 3GPP. And it outputs the received S1 message to the determining unit 52. Information eNB40, the operation can change the setting procedure of radio resources, showing security setting procedure operation is omitted, or instruction eNB indicating that it is able to support operation of stopping the process related to the handover by the type of MME50 a (eNB capabilities of also may) as .NodeB type, it may be transmitted to the MME50 using S1 message.
[0050]
　Determination unit 52 omits at least one of the security setup procedure between the setting procedure and UE30 radio resource used for communication of user data between the UE30 according to the profile information of the UE30 included in NAS message determines whether or not the. Determination unit 52 outputs the determination result to the control unit 53. The determination unit 52 obtains the subscriber information from HSS90, information about IoT contained in the subscriber information may be used for the determination.
[0051]
　Control unit 53, for example, when receiving a determination result has been shown to skip setting procedure of radio resources to the eNB40 via the base station communication unit 51, instructing to skip setting procedure of radio resources to send a message. Alternatively, if it is determined that can be omitted setting procedure when receiving the information indicating the information of small data (size) to be transmitted, it analyzes the information radio resource from UE30 is via the base station communication unit 51 Te to eNB 40, sends a message for instructing to skip setting procedure of radio resources. The control unit 53, when receiving the judgment result that has been shown to omit the security setup procedure, the eNB40 via the base station communication unit 51 transmits a message instructing to skip security setting procedure . The control unit 53, when receiving the judgment result that has been shown to skip setting procedure and security setting procedure of radio resources to the eNB40 via the base station communication unit 51, an instruction to skip both steps to send a message to. The control unit 53, when receiving the determination result handover process has been shown to be unnecessary, the eNB40 via the base station communication unit 51 transmits a message instructing to stop processing regarding handover .
[0052]
　Further, the control unit 53, depending on the profile information, setting of a radio resource procedures and EPC indicating that a message indicating that the skip security setting procedure can be transmitted to the eNB 40 type (information indicating the EPC capacity) and transmits to the UE30 through the eNB40. The control unit 53 may transmit to the eNB40 using the S1 message EPC type.
[0053]
　The network communication unit 54, and transmits to the SGW60 using small data outputted from the base station communication unit 51 GTP a (General Packet Radio Service Tunneling Protocol) -C message message.
[0054]
　Next, an example of the configuration of the eNB40 according to a second embodiment of the present invention will be described with reference to FIG. eNB40 includes a radio communication unit 41, the control unit 42 and the network communication unit 43,. Each component constituting the eNB40, the processor may be a software or modules such as processing by executing a program stored in the memory is executed. Or, the components constituting the eNB40 may be hardware or chips.
[0055]
　The wireless communication unit 41 executes processing for performing UE30 and wireless communications. For example, wireless communication unit 41, a signal including the transmission data and generates a radio signal by modulating a desired frequency, and transmits the generated radio signal to the UE 30. Or, the radio communication unit 41 demodulates a radio signal transmitted from the UE 30, and outputs the demodulated signal to the control unit 42.
[0056]
　Network communication unit 43 is used as an interface for communicating with MME50. For example, the network communication unit 43 transmits and receives control data between the MME50.
[0057]
　Control unit 42, based on the instruction transmitted from MME50, executes the steps of establishing a radio link between the UE 30. Specifically, the control unit 42 establishes a radio link by transmitting and receiving control data between the UE 30. At this time, the control unit 42 controls the message relates instructed processing to be omitted from MME50 not to send to the UE 30.
[0058]
　Further, the control unit 42, depending on the profile information, the eNB type indicating that it is possible to omit the setting procedure and security setting procedure of radio resources of the processing for establishing the wireless link via the wireless communication unit 41 UE 30 control to send to.
[0059]
　Here, the establishment procedure of a general radio link is defined in 3GPP as a comparative example of the present invention will be described with reference to FIGS. UE30, by not running a predetermined period communication, it is assumed that the transition of the IDLE mode. In the IDLE mode, the UE30 and eNB40 a state that is not synchronized.
[0060]
　First, UE 30 in order to initiate communication with the eNB 40, sends a RRC (Radio Resource Control) Connection Request message to the eNB 40 (S11). Then, eNB 40 as a response to the RRC Connection Request message, transmits a RRC Connection Setup message to the UE 30 (S12).
[0061]
　Then, UE 30 transmits an RRC Connection Setup Complete message to the eNB 40 (S13). UE30 transmits a RRC Connection Setup Complete message containing an NAS message to be used in the NAS protocol to eNB 40. In other words, UE 30 transmits an RRC message obtained by multiplexing the NAS message to the eNB 40. RRC Connection Setup Complete message specifically includes a Service Request message as a NAS message. UE30, when starting communication, transmits a Service Request message to MME50.
[0062]
　Then, eNB 40 transmits an Initial UE message to MME50. eNB40 sets the Service Request message in the RRC Connection Setup Complete message to the Initial UE message (S14).
[0063]
　Then, MME50, in order to instruct the Traffic Channel settings used for transmitting and receiving user data between the UE30 and eNB 40, sends the Initial Context Setup Request message to the eNB 40 (S15). MME50 may, for example, including security Key used for security setting between UE30 and eNB40 the Initial Context Setup Request message. Initial Context Setup Request Security Key to be included in the message may be a different security Key is a security Key used when performing the security setting between the previously UE30 and eNB 40. By using different security Key each time to set the RRC connection between the UE30 and eNB 40, and to achieve high security.
[0064]
　Then, eNB 40 transmits a Security Mode Command message to the UE 30 in order to perform the security setting between the UE 30 (S16). UE30 as a response to the Security Mode Command message, transmits a Security Mode Complete message to the eNB 40 (S17). In steps S16 and S17, the security Key transmitted from MME50 in step S15 is used.
[0065]
　Then, eNB 40 in order to transmit and receive user data using the RRC connection between the UE 30, and transmits the RRC Connection Reconfiguration message to the UE 30 (S18). Then, UE 30 transmits a RRC Connection Reconfiguration Complete message to eNB40 in response to RRC Connection Reconfiguration message.
[0066]
　Then, eNB 40 transmits an Initial Context Setup Response message to the MME50 response to Initial Context Setup Request message in step S15 (S20). Then, MME50, to indicate the setting of the path for transmitting and receiving user data between the eNB40 and SGW60, it sends a Modify Bearer Request message to the SGW60 (S21). SGW60 further in order to set a path for transmitting and receiving user data between the PGW70, sends a Modify Bearer Request message to the PGW70.
[0067]
　In the process up to step S21, the transmission path of the user data is established, UE 30 transmits a UDP (User Datagram Protocol) / IP (Internet Protocol) packets to eNB 40 (S22). Further, eNB 40 transmits the UDP / IP packet to SGW60 (S23). Further, MME50 receives the Modify Bearer Response message from SGW60 as a response to the Modify Bearer Request message in step S21 (S24).
[0068]
　Then, SGW60 is to eNB 40, sends the UDP / IP packets destined for UE 30 (S25). Then, eNB 40 transmits the received UDP / IP packet to the UE 30 (S26).
[0069]
　Then, UE 30 transmits a Measurement Report message indicating the results of measuring the reception quality or the like of a signal transmitted from the eNB around the eNB 40 to the eNB 40 (S27).
[0070]
　Then, eNB 40 releases the Inactivity Timer showing a radio communication period between the UE 30, or detects that the Inactivity Timer has expired (S28).
[0071]
　Then, eNB 40, in order to request to release the radio bearer is set between the UE 30, and transmits a UE Context Release Request message to MME50 (S29). Then, MME50 sends a UE Context Release Command message instructing to release the radio bearer between UE30 and the eNB 40 to the eNB 40 (S30). Then, eNB 40, in order to release the radio bearer between the UE 30, and transmits the RRC Connection Release message to the UE 30 (S31). Then, eNB 40 transmits a UE Context Release Complete message indicating that it has released the radio bearer between the UE30 to MME50 (S32).
[0072]
　When following the flow of the processing shown in FIGS. 9 and 10, a IoT device UE30 transmits small data as user data. That, UE 30 transmits small data as UDP / IP packet in step S22. Further, even UE30 is IoT devices, in between UE30 and eNB 40, as if UE30 is smartphone, security setting is performed in step S16 and S17.
[0073]
　Subsequently, the flow of Attach processing according to the second embodiment of the present invention will be described with reference to FIG. Attach process, when the power source of the UE30 is shifted to the ON state, a process that is performed to register the UE30 to the network.
[0074]
　First, UE 30, when the power is turned on by the user, and transmits the RRC Connection Request message to the eNB 40 (S41). Then, eNB 40 transmits an RRC Connection Setup message to UE30 as a response to the RRC Connection Request message (S42).
[0075]
　Then, UE 30 transmits an RRC Connection Setup complete message to the eNB 40 (S43). UE 30 is a NAS message in the RRC Connection Setup complete message, NAS: the ATTACH message, sets the profile information about the UE 30. ATTACH message may be a ATTACH REQUEST message.
[0076]
　UE30, for example, Traffic Channel (U-Plane) garbage, low security request information, and at least one of handover processing garbage NAS: set to ATTACH message.
[0077]
　Or, UE 30 as profile information, category information indicated by the bit string of 3 bits NAS: may be set to ATTACH message. Moreover, the presence or absence of the flag may indicate them.
[0078]
　Then, eNB 40 may, NAS: sends the Initial UE message that sets the ATTACH message to MME50 (S44). NAS: ATTACH message, NAS is transmitted from the UE 30: it is a ATTACH message.
[0079]
　MME50 is, NAS is transmitted from the eNB 40: When receiving the ATTACH message, executes an Attach process between the UE 30 (S45). Attach processing executed in step S45, the procedure defined in 3GPP (TS 23.401 5.3.2.1 Section, etc.) it is executed. Here will be omitted the detailed procedure of the Attach process.
[0080]
　MME50 completes the Attach processing relating UE30 in step S45, sends an ATTACH the accept message to UE30 via eNB 40 (S46 and S47). Here, MME50 is, NAS received in step S44: ATTACH message to Traffic Channel unnecessary information, if at least one of the low-security request information and the handover process required information has been set, the radio resource used for communication of user data setting procedure, it determines whether the omission of security setup procedure between the UE 30, and the handover process is at least one of be eliminated can be indicated to the eNB 40.
[0081]
　MME50 the setting procedure of radio resource used for communication of user data, if the security setting omission of steps between the UE 30, that and the handover process is at least one of be eliminated can be indicated to the eNB 40, ATTACH setting the EPC type to S1 message carrying the accept message. EPC type are setting procedure of radio resource used for communication of user data, indicate that the security setting omission of steps between the UE 30, that and the handover process is at least one of be eliminated can be indicated to the eNB40 ing. Also, if MME50 the setting procedure of radio resource used for communication of user data, which can indicate security settings omission of steps between the UE 30, and the handover process is at least one of be unnecessary to UE 30 , sets the EPC type to ATTACH the accept message. EPC type are setting procedure of radio resource used for communication of user data, indicate that the security setting omission of steps between the UE 30, that and the handover process is at least one of be eliminated can be indicated to the UE 30 ing.
[0082]
　Then, eNB 40 transmits an ATTACH the accept message sent from MME50 to UE 30 (S47).
[0083]
　As described above, UE 30 by executing an Attach process, it is possible to receive the ATTACH the accept message EPCtype is set. Than this, UE 30 can grasp whether it is possible to instruct the omission of security setup procedure between the wireless resource configuration instructions and UE 30 to be used for communication MME50 user data to eNB 40.
[0084]
　Further, in FIG. 7, UE 30 does not set the profile information of UE 30 in the RRC message in step S41. Therefore, UE 30, at step S42, eNB 40 does not receive the eNB type indicating whether it is possible to omit part of the processing of the process for establishing the wireless link. Part of the process of establishing a radio link, for example, a security setting procedure between the radio resource configuration procedure and UE30 used for communication of the user data.
[0085]
　UE30 simultaneously with the execution of the Attach process, there is a possibility that the UE30 is not performed transmission of small data. Than this, UE 30, at the time of Attach processing, as there is no need to receive the eNB type from eNB 40, may not transmit the profile information in step S41.
[0086]
　On the other hand, when performing the small data transmission during Attach process, UE 30 may set the profile information of UE 30 in step S41. Furthermore, UE 30 is, NAS in step S43: Apart from the profile information set in ATTACH message may set the profile information can be processed RRC message in eNB 40.
[0087]
　ENB to communicate with UE30 during Attach process, the case is identical to the eNB to communicate with UE30 when small data transmission, for example, the following situation.
(1) UE 30 situation does not move
(2) UE 30 is present in very close to the eNB 40, even if the wireless environment around the UE 30 is changed, eNB communication destination UE 30 does not change status
[0088]
　eNB40, when the profile information UE30 is set in step S41, the RRC Connection Setup message set the eNB type may be sent to UE30 in step S42. Further, eNB 40, even if the profile information of the UE30 is not set in step S41, the RRC Connection Setup message set the eNB type may be sent to UE30 in step S42. Or, eNB 40, when the profile information UE30 is set to RRC messages step S43, the ATTACH the accept message set the eNB type may be sent to UE30 in step S47. Further, eNB 40, even if the profile information of the UE30 to RRC message in step S43 is not set, the RRC message that carries the ATTACH the accept message set the eNB type may be sent to UE30 in step S47 .
[0089]
　Subsequently, the flow of transmission processing of small data according to the second embodiment of the present invention will be described with reference to FIG. In Figure 8, Attach processing related UE30 is completed, it is assumed that UE30 is IDLE state.
[0090]
　First, UE 30 transmits an RRC Connection Request message to the eNB 40 (S51). Then, eNB 40 transmits an RRC Connection Setup message to UE30 as a response to the RRC Connection Request message (S52).
[0091]
　UE30 is an RRC Connection Request message may be sent to the eNB40 set the profile information in step S51. In this case, eNB 40 sets the eNB type in RRC Connection Setup message in step S52.
[0092]
　Then, UE 30 transmits an RRC Connection Setup Complete message to the eNB 40 (S53). Here, UE 30, when receiving the eNB type and EPC type, NAS sets the profile information and small data: sets the Service Request message to the RRC Connection Setup Complete message. For example, UE 30 as profile information, and setting the Traffic Channel unnecessary information and low security request information.
[0093]
　UE30, at step S51, if not set the profile information to the RRC message, to set the profile information to RRC Connection Setup Complete message. That, UE 30 sets profile information to both the RRC message and the NAS message.
[0094]
　Then, eNB 40 may, NAS is transmitted from the UE 30: transmits the Initial UE message that sets the Service Request message to MME50 (S54).
[0095]
　Then, MME50 sends the Initial Context Setup Request message to the eNB 40 (S55). MME50 by sending an Initial Context Setup Request message, the setting procedure of radio resource used for communication of user data, omitting the security setting procedure between the UE 30, and the handover process is that the unnecessary eNB40 it may be notified to.
[0096]
　Omission of the radio resource configuration procedure used to communicate user data, for example, may be to omit the processing of steps S18 ~ S32 of FIG. 9. Optional security setup procedure, may be to omit the processing of step S16 and step S17.
[0097]
　MME50 is the Initial Context Setup Request message by not setting the updated security Key Canada, may notify the omission of security setup procedure to eNB 40. Furthermore, MME50 by setting a flag or the like, may notify the eNB40 to omit the setting procedure of radio resource used for communication of user data.
[0098]
　eNB40 is, after receiving the Initial Context Setup Request message in step S55, the processing in step S16 and subsequent FIGS. 9 and 10 are omitted.
[0099]
　Then, MME50 sends a GTP-C message set the small data received in step S54 to SGW60 (S56). GTP-C message is a control data transmitted and received between the MME50 and SGW60. Then, SGW60 transmits the GTP-U message set the small data received in step S56 to PGW70 (S57). GTP-U message is user data to be transmitted and received between the SGW60 the PGW70. SGW60 is may be transmitted to the PGW70 a GTP-C message set the small data received in step S56 (S57).
[0100]
　UE 30, if not received eNB type and EPC type, without transmitting the profile information, UE 30, eNB 40, and the processing of FIG. 9 and FIG. 10 may be performed by MME50. That is, the setting procedure and security setting procedure of radio resource used for communication of user data is performed without omitting. And if UE30 has not received the eNB type and EPC type, when eNB40 and MME50 does not correspond to the default security setting procedure between the radio resource configuration procedure and UE30 used for communication of the user data it is.
[0101]
　Further, UE 30 has received the eNB type, when having not received the EPC type, transmits the profile information, security setting procedure between the wireless resource configuration instructions and UE 30 to be used for communication with the user data it may request the omission.
[0102]
　And if UE30 is receiving only eNB type are eNB 40 is corresponds to the default security setting procedure between the radio resource configuration procedure and UE30 used for communication of the user data, is MME50, the omission of security setup procedure between the wireless resource configuration instructions and UE30 used for communication of the user data is not be compatible.
[0103]
　In this case, for example, eNB 40 is omitted, in step S55, even if updated security Key is sent, by not transmitting the Security Mode Command at step S16 in FIG. 9, the processing in step S16 and S17 it may be so.
[0104]
　Further, eNB 40 is the profile information transmitted from the UE 30, recognizes that UE 30 to send small data. Therefore, UE 30, at step S30, even if the skip instruction for setting procedure of radio resource used for communication of user data is not notified, may be omitted the step S18 and subsequent steps in FIG.
[0105]
　Further, eNB 40, as the profile information from the UE 30, if the handover process unnecessary information is transmitted, it is possible to omit the handover processing relating to UE 30. The handover process regarding UE 30, for example, include processing for monitoring the radio quality such as the UE 30. Therefore, eNB 40, by omitting the handover processing relating to UE 30, it is possible to reduce the processing load of the apparatus.
[0106]
　As described above, the eNB 40 and MME50, can be in accordance with the profile information of UE 30, omit the messages transmitted and received between the UE 30 and eNB 40. Thus, it is possible to reduce the number of messages that UE 30 to send and receive, it is possible to suppress the power consumption of the UE 30. As a result, it is possible to reduce the frequency of battery replacement battery charging operation and UE 30 of UE 30.
[0107]
　Furthermore, UE 30 is, eNB 40 and MME50 is, if the omission of security setup procedure between the wireless resource configuration instructions and UE 30 to be used to communicate user data does not correspond, the procedure of transmitting a small data as user data it can be executed.
[0108]
　This, in the communication system, even when the eNB40 and MME50 which the omission of security setting procedure is not compatible between the setting procedure and UE 30 radio resources are mixed, UE 30 is, IoT server small data it can be sent to 80.
[0109]
　Furthermore, UE 30 is, by using the handover processing unnecessary information as profile information, it is possible to realize a reduction in processing load in the eNB 40.
[0110]
　Then hereinafter, the network device 10 described in multiple embodiments described above, the communication terminal 20, UE 30, eNB 40, and, a configuration example of MME50. Figure 11 is a block diagram showing a configuration example of eNB 40. Referring to FIG. 11, eNB 40 includes an RF transceiver 1001, a network interface 1003, a processor 1004, and memory 1005. RF transceiver 1001 performs an analog RF signal processing to communicate with the UEs. RF transceiver 1001 may include a plurality of transceivers. RF transceiver 1001 is coupled to antenna 1002 and the processor 1004. RF transceiver 1001 receives the modulated symbol data (or OFDM symbol data) from the processor 1004, generates a transmission RF signal and provides a transmit RF signal to the antenna 1002. Also, RF transceiver 1001 to generate a baseband received signal based on the reception RF signal received by an antenna 1002, and supplies it to the processor 1004.
[0111]
　Network interface 1003, network node (eg, other eNBs, Mobility Management Entity (MME), Serving Gateway (S-GW), and TSS or ITS servers) is used to communicate with. Network interface 1003 may include, for example, a network interface card that complies with the IEEE 802.3 series (NIC).
[0112]
　The processor 1004, performs data plane processing and control plane processing including digital baseband signal processing for wireless communication. For example, in the case of LTE and LTE-Advanced, a digital baseband signal processing by the processor 1004, PDCP layer, RLC layer may include a signal processing of the MAC layer, and the PHY layer. Further, the signal processing by the processor 1004 may include signal processing GTP-U · UDP / IP layer in the X2-U interface and S1-U interface. The control plane processing by the processor 1004, X2AP protocol may include a process of S1-MME protocol and the RRC protocol.
[0113]
　Processor 1004 may include multiple processors. For example, the processor 1004 is a modem processor that performs digital baseband signal processing (eg, DSP), X2-U interface and S1-U interface of the GTP-U · UDP / IP layer processor for performing signal processing (eg, DSP), and a protocol stack processor for performing control plane processing (eg, may include a CPU or MPU).
[0114]
　Memory 1005 is constituted by a combination of volatile and nonvolatile memory. Memory 1005 may include a physically independent plurality of memory devices. Volatile memory may be, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof. The non-volatile memory, a mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof. Memory 1005 may include a storage that is remotely located from the processor 1004. In this case, the processor 1004 may access the memory 1005 via the I / O interfaces that are not network interface 1003 or illustrated.
[0115]
　Memory 1005 may store software modules (computer program) including instructions and data for processing by eNB40 described in several embodiments described above. In some implementations, the processor 1004, the software module that executes from the memory 1005 may be configured to perform processing of eNB40 described in the above embodiments.
[0116]
　Figure 12 is a block diagram showing a configuration example of the communication terminal 20 and UE 30. Radio Frequency (RF) transceiver 1101 performs an analog RF signal processing to communicate with the eNB 40. Analog RF signal processing performed by the RF transceiver 1101 includes a frequency up-conversion, the frequency down-conversion, and amplification. RF transceiver 1101 is coupled to antenna 1102 and the base band processor 1103. That, RF transceiver 1101 receives the modulated symbol data (or OFDM symbol data) from the baseband processor 1103, generates a transmission RF signal and provides a transmit RF signal to the antenna 1102. Also, RF transceiver 1101 to generate a baseband received signal based on the reception RF signal received by an antenna 1102, and supplies it to the baseband processor 1103.
[0117]
　Baseband processor 1103 performs control plane processing and digital baseband signal processing for wireless communication (data plane processing). Digital baseband signal processing, (a) data compression / decompression, (b) segmentation / concatenation of data, generation / decomposition of (c) transmission format (transmission frame), (d) transmission channel coding / decoding , including generation of (e) modulation (symbol mapping) / demodulation, and OFDM symbol data by (f) Inverse Fast Fourier Transform (IFFT) (baseband OFDM signal). On the other hand, the control plane processing, layer 1 (eg, transmission power control), Layer 2 (eg, radio resource management, and hybrid automatic repeat request (HARQ) process), and layer 3 (eg, attach, mobility and call management including communication management signaling) related.
[0118]
　For example, in the case of LTE and LTE-Advanced, a digital baseband signal processing by a baseband processor 1103, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, includes a signal processing of the MAC layer, and a PHY layer But good. Further, the control plane processing by baseband processor 1103, Non-Access Stratum (NAS) protocol, RRC protocol, and may include a process of MAC CE.
[0119]
　Baseband processor 1103, a modem processor that performs digital baseband signal processing (eg, Digital Signal Processor (DSP)) and protocol stack processor for performing control plane processing (eg, Central Processing Unit (CPU), or Micro Processing Unit it may include (MPU)). In this case, the protocol stack processor for performing control plane processing may be shared with an application processor 1104 which will be described later.
[0120]
　The application processor 1104, CPU, MPU, also referred to as a microprocessor or processor cores. The application processor 1104 may include a plurality of processors (multiple processor cores). The application processor 1104, a memory 1106 or illustrated which do not result system read from the memory a software program (Operating System (OS)) and various application programs (e.g., call application, WEB browser, a mailer, a camera operation application, music playback by running the application), to implement the various functions of the communication terminal 20 and UE 30.
[0121]
　In some implementations, as indicated by the dashed line (1105) in FIG. 12, the baseband processor 1103 and an application processor 1104 may be integrated on a single chip. In other words, the baseband processor 1103 and an application processor 1104 may be implemented as a single System on Chip (SoC) device 1105. SoC devices, sometimes referred to as system Large Scale Integration (LSI) or chipset.
[0122]
　Memory 1106 is a volatile memory or nonvolatile memory, or a combination thereof. Memory 1106 may include a physically independent plurality of memory devices. Volatile memory may be, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof. The non-volatile memory, a mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof. For example, memory 1106, a baseband processor 1103, an application processor 1104, and may contain accessible external memory device from SoC1105. Memory 1106, within baseband processor 1103, within the application processor 1104, or may include an integrated chip memory device within SoC1105. Furthermore, memory 1106 may include a memory in the Universal Integrated Circuit Card (UICC).
[0123]
　Memory 1106 may store software modules (computer program) including instructions and data for processing by the UE40 described in several embodiments described above. In some implementations, the baseband processor 1103 or the application processor 1104, the software module that executes from the memory 1106 is configured to perform processing of the communication terminal 20 and UE30 that are described in the above embodiment it may be.
[0124]
　Figure 13 is a block diagram showing a configuration example of a network device 10 and MME50. Referring to FIG. 13, the network device 10 and MME50 a network interface 1201, a processor 1202, and memory 1203. Network interface 1201, network node (eg, eNodeB130, MME, P-GW,) is used to communicate with. Network interface 1201 may include, for example, a network interface card that complies with the IEEE 802.3 series (NIC).
[0125]
　The processor 1202 reads and executes the software from the memory 1203 (a computer program), the processing of the network device 10 and MME50 described with reference to sequence diagrams and flowcharts in the above embodiments. The processor 1202, e.g., a microprocessor, MPU, or a CPU. Processor 1202 may include multiple processors.
[0126]
　Memory 1203 is constituted by a combination of volatile and nonvolatile memory. Memory 1203 may include a storage that is remotely located from the processor 1202. In this case, the processor 1202 may access the memory 1203 via the I / O interface (not shown).
[0127]
　In the example of FIG. 13, the memory 1203 is used for storing software modules. Processor 1202, these software modules that run from the memory 1203, it is possible to perform the processing of the network device 10 and MME50 described in the above embodiment.
[0128]
　As described with reference to FIGS. 11 to 13, the network apparatus 10 in the above embodiment, the communication terminal 20, UE 30, eNB 40, and each of the processors included in MME50 a computer algorithm which is described with reference to the drawings executing one or more programs including instructions for causing a.
[0129]
　In the above example, the program may be stored using a non-transitory computer readable media of various types (non-transitory computer readable medium), it can be supplied to the computer. Non-transitory computer readable media include with various types of entities (tangible storage medium). Examples of non-transitory computer readable media include magnetic storage media (such as floppy disks, magnetic tape, hard disk drive), magneto-optical recording medium (e.g. optical disk), CD-ROM (Read Only Memory), CD-R, CD-R / W, a semiconductor memory (e.g., a mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access memory)) includes a. The program may be provided to a computer using a temporary computer readable media of various types (transitory computer readable medium). Examples of transitory computer readable media include electric signals, optical signals, and electromagnetic waves. Transitory computer readable media, wired communication path such as electrical wires and optical fibers, or via a wireless communication path can provide the program to a computer.
[0130]
　The present invention is not limited to the above embodiments, but can be appropriately changed without departing from the spirit.
[0131]
　Although the present invention has been described with reference to the embodiments, the present invention is not limited by the foregoing. Configuration and details of the present invention, it is possible to make various modifications that those skilled in the art can understand within the scope of the invention.
[0132]
　This application claims priority based on Japanese Patent Application No. 2015-146266, filed on July 24, 2015, the entire disclosure of which is incorporated herein.
[0133]
　Some or all of the above embodiments, can be described as the following notes, not limited to the following.
　(Supplementary Note 1)
　and a communication unit that receives profile information of the communication terminal transmitted from the communication terminal,
　the procedure for establishing the communication terminal and the radio link, according to the profile information, the user between the said communications terminal setting procedure of radio resource used for communication of data, and and a determination section for determining whether or not to omit at least one of the security setup procedure between the communication terminal,
　the communication unit,
　the radio receiving a small data transmitted from the communication terminal via a link, network device.
　(Supplementary Note 2)
　The determination unit,
　where indicated be transmitted using the radio resources for the control of small data data in the profile information, the procedure for establishing the communication terminal and the wireless link, wherein omitted setting procedure of radio resource used for communication of user data between a communication terminal, a network device according to Appendix 1.
　(Supplementary Note 3)
　The determination unit,
　as the security level information to the profile information, the case where it has been shown to encrypt unnecessary or simple level encryption of small data, establishing the communication terminal and the wireless link in steps, omitted the security setting procedure between the communication terminal, the network device according to Appendix 1 or 2.
　(Supplementary Note 4)
　The determination unit,
　by stopping the update of the security key used between said communication terminal is omitted the security setting procedure between the communication terminal, the network device according to note 3.
　(Supplementary Note 5)
　The communication unit
　upon receiving the profile information, sends the information indicating that it is possible to omit the setting procedure and the security setting procedure of the radio resource to the communication terminal, any Supplementary Notes 1 to 4 the network device according to (1).
　(Supplementary Note 6)
　The communication unit
　sets information indicating that it is possible to omit the setting procedure and the security setting procedure of the radio resource to the RRC Connection Setup message or ATTACH Accept message, the network device according to Appendix 5.
　(Supplementary Note 7)
　and a communication unit for transmitting the profile information of the own terminal to the network device,
　from said network device, in the procedure of establishing the network device and the wireless links, according to the profile information, between the said network device setting procedure of radio resource used for communication of user data, and a receiving unit for receiving information on whether it is possible to omit at least one of the security setup procedure between the network device includes,
　the communication unit
　sends the small data to the network device via the wireless link, communication terminal.
　(Supplementary Note 8)
　The communication unit
　receives information indicating that it is possible to omit the setting procedure of radio resource used for communication of the user data, the using the radio resource for small data control data network and transmits to the device, the communication terminal according to Appendix 7.
　(Supplementary Note 9)
　The communication unit
　receives information indicating that it can not be omitted the radio resource setup procedure, and transmits to the network device by using the radio resource for the user data of the small data, Appendix communication terminal according to 7 or 8.
　(Supplementary Note 10)
　The communication unit
　transmits the RRC message and the NAS message sets the profile information of the own terminal to the network device, the communication terminal according to any one of Appendices 7-9.
　(Supplementary Note 11)
　and a communication terminal,
　a base station that performs the communication terminal and the wireless communication,
　and a core network apparatus for controlling the establishment procedure of the wireless link between the base station and the communication terminal,
　the core network device is
　when receiving the profile information of the communication terminal transmitted from said communication terminal, said at establishment procedure of the radio link, the setting procedure of radio resource used for communication of user data between the said communications terminal, and the communication an indication message indicating to omit at least one of the security setup procedure between the terminal transmits to the base station,
　the base station,
　in response to the indication message, the user data between said communication terminal procedure set of radio resources used in communication, and little of the security setup procedure between the communication terminal And perform the establishment procedure of the omitted radio links one,
　the communication terminal
　transmits a small data to the base station via the radio link, communication system.
　(Supplementary Note 12)
　receives the profile information of the communication terminal transmitted from the communication terminal,
　the procedure for establishing the communication terminal and the radio link, according to the profile information, the communication of user data in between the communication terminal setting procedure of radio resources used, and determines whether to omit at least one of the security setup procedure between the communication terminal,
　the small data transmitted from the communication terminal via the wireless link incoming, receiving method.

[Claim 1]
　CIoT A (Cellular Internet of Things) mobile communication system for optimizing small data communication,
　indicating use the one U-Plane using C-plane in the small data communication (control plane) (user plane) the terminal carrying the information,
　and a MME (Mobility Management Entity) which the ATTACH REQUEST message including the information received via the base station from the terminal,
　the MME is the in the small data communication on the basis of the information C- determining whether to support communication using plane, mobile communication system to be transmitted to the terminal the ATTACH ACCEPT message via the base station.
[Claim 2]
　A CIoT (Cellular Internet of Things) MME for use in a mobile communication system for optimizing small data communication (Mobility Management Entity),
　wherein either use C-plane in the small data communication (control plane) U-Plane and the base station communication unit from the terminal carrying the information indicating whether use (user plane) via the base station receives the ATTACH REQUEST message including the information,
　the C-plane in the small data communication on the basis of the information a determination section for determining whether to support communications using,
　MME with the basis of the determination of the determination result, and the base station communication unit that transmits the ATTACH ACCEPT message to the terminal via the base station.
[Claim 3]
　A terminal for use in a mobile communication system to optimize the small data communication CIoT (Cellular Internet of Things),
　wherein either U-Plane using C-plane in the small data communication (Control plane) a (user plane) and IoT application unit, carrying the information indicating whether to use
　a wireless communication unit for transmitting via the base station ATTACH REQUEST message including the information on the MME (Mobility Management Entity),
　said in the small data communication on the basis of the information terminals having from C-plane of the MME where it is determined whether to support communication using, said wireless communication unit for receiving via the ATTACH ACCEPT message the base station.
[Claim 4]
　CIoT A (Cellular Internet of Things) communication method of the mobile communication system to optimize the small data communication,
　or U-Plane terminal uses a C-plane (control plane) in the small data communication (user plane) holds information indicating whether use,
　MME a (Mobility Management Entity) is ATTACH REQUEST message including the information received via the base station from the terminal,
　wherein the MME is in the small data communication on the basis of the information C determining whether the communication supports using -plane, communication method for a mobile communication system for transmitting to the terminal the ATTACH ACCEPT message via the base station.
[Claim 5]
　CIoT A (Cellular Internet of Things) communication method MME used in the mobile communication system (Mobility Management Entity) to optimize the small data communication,
　either use the C-plane (control plane) in the small data communication U-Plane (user plane) via the base station from a terminal carrying the information indicating whether use receives the ATTACH REQUEST message including the information,
　using the C-plane in the small data communication on the basis of the information to determine whether they support the communication,
　based on said determination result, and transmits the ATTACH ACCEPT message to the terminal via the base station, MME communication method.
[Claim 6]
　CIoT A (Cellular Internet of Things) terminal of a communication method used in a mobile communication system to optimize the small data communication,
　the or U-Plane using C-plane in the small data communication (control plane) (user It holds information indicating whether use plane),
　the ATTACH REQUEST message including the information via the base station transmits to the MME (Mobility Management Entity),
　use the C-plane in the small data communication on the basis of the information from the MME, which determines whether to support communications had receives, via the base station ATTACH ACCEPT message, the method of communication terminals.