0001]The present disclosure relates to a wireless communication system that supports multiple communication architecture types for data transmission.
Background technique
[0002]3rd Generation Partnership standardization of Project in (3GPP) Cellular Internet of Things (CIoT) has been carried out. CIoT the 3GPP is targeted, including Long Term Evolution enhanced Machine to Machine (LTE eMTC) and Narrowband IoT (NB-IoT). LTE emtc and NB-IoT includes very low User Equipment (UE) power consumption (Ultra low UE power consumption), a number of devices per cell, narrow-band spectrum, the features of such extended coverage. In LTE eMTC (Category M), UE reception radio frequency (Radio Frequency (RF)) band is defined as 1.4 MHz. In contrast, in the NB-IoT, further cost optimization, low power consumption, and for coverage expansion, the peak rate of the downlink and uplink are 200 kbps or 144 kbps, the received RF band of the UE it is assumed in both uplink and downlink is about 200 kHz (effective 180 kHz).
[0003]
　Non-Patent Document 1 describes some communication architecture solution for small data transmission infrequent in NB-IoT (infrequent small data transmission). These solutions include a data transmission architecture of the control plane (Solution 2), suspend the RRC Connection (suspension) and resume data transmission architecture for the user plane with (resumption) (solution 18). Non-Patent Document 1, the support solution 2 are essential for both the UE and network support solution 18 is optional in both the UE and the network.
[0004]
　Solution 2 is based on the lightweight core network (CN) architecture for CIoT. The lightweight CN architecture, in view of the typical use cases CIoT device, the core network, the existing LTE the CN entity (ie, Mobility Management Entity (MME), Serving Gateway (S-GW), and Packet Data Network Gateway (P-GW)) and to support only limited functionality compared. Figure 1 shows a network architecture for CIoT in non-roaming case.
[0005]
　CIoT Serving Gateway Node (C-SGN) is a new logical network entity. C-SGN is a CN node that combines the control plane (CP) and user plane (UP). C-SGN is limited mobility management (Mobility Management (MM)) procedure for CIoT devices, small data transmission procedure, security procedures for small data transmission, the end of the SGi interface for non-roaming case provide. Incidentally, P-GW functionality may be separated from the C-SGN. In this case, S5 interface is used between the C-SGN and P-GW. For roaming case, C-SGN provides an S8 interface.
[0006]
　S1-lite interface is optimized version of S1-C (S1-MME). S1-lite interface supports S1 Application Protocol (S1AP) messages and information elements required (Information Elements (IEs)) in the procedure for CIoT, supports optimized security procedures. For efficient small data transmission, the user data is carried in S1AP layer.
[0007]
　More specifically, in the case of Mobile Originated (MO) small data transmission of the non-roaming case, UE is small data packet uplink carrying (eg, Internet Protocol (IP), non-IP, short message service (SMS)) to send Non-Access Stratum the (NAS) message. The uplink NAS message reaches the C-SGN through CIoT Base Station (CIoT BS). The uplink NAS message is transmitted on a signaling radio bearer (Signaling Radio Bearer (SRB). Thus, the setup of the data radio bearer (Data Radio Bearer (DRB)) is not required. Also, Access Stratum (AS) security may be omitted.
[0008]
　C-SGN, in order to obtain a small data packet, decodes the uplink NAS message (decrypt). C-SGN, depending on the data type of small data packets, and forwards the small data packets. For IP small data, C-SGN does this transmission over SGi interface. For SMS, C-SGN, this entity regarding SMS (eg, SMS Gateway Mobile Services Switching Center (SMS-GMSC), SMS Interworking Mobile Services Switching Center (SMS-IWMSC), SMS router) sends to. For Non-IP small data, C-SGN is and transmits to the Service Capability Exposure Function (SCEF).
[0009]
　For Mobile Terminated (MT) small data transmission of the non-roaming case, C-SGN transmits downlink NAS message carrying the small data packets via the CIoT BS to the UE. DRB is not needed even in small data packets transmitted on the downlink, AS security may be omitted.
[0010]
　CIoT BS shown in FIG. 1 is a base station in CIoT Radio Access Network (CIoT RAN). Instead of CIoT BS in FIG. 1, LTE eNB configured to connect the C-SGN may be used. The LTE eNB may be an eNB that supports LTE emtc.
[0011]
　Meanwhile, the architecture of the solution 18 provides a transmission on the user plane of the small data infrequent. However, in order to reduce the signaling associated with the Radio Resource Control (RRC) state transition UE, architecture of the solution 18, the previous (previous previous) after the information from the RRC Connection RRC connection setup of (Subsequent) wherein the reused for.
[0012]
　Specifically, UE transitions from RRC-Connected to RRC-Idle mode, information about the RRC connection in RRC-Idle mode, eg, Access Stratum Security Context, bearer related information (incl. RoHC state information) and L2 / hold 1 parameters the when applicable Accept to (the retain). Similarly, eNB also maintains information about the RRC connection of the UE, eg, Access Stratum Security Context, the bearer related information (incl. RoHC state information) and L2 / 1 parameters when applicable. Further, eNB and MME holds S1AP UE Contexts. Furthermore, eNB holds S1-U tunnel addresses.
[0013]
　To return to RRC-Connected mode, UE sends a RRC Connection Resume Request to eNB. eNB based on the information about the RRC connection has been held, DRB, security context, S1AP connection, to restore the S1-U tunnel. Further, eNB, a new S1AP message (ie, S1AP UE Context Active) using informs UE status change (state change) to MME. MME returns the Evolved Packet System (EPS) Connection Management (ECM) state of the UE in ECM-Connected state, and sends a Modify Bearer Request message to the S-GW. Thus, S-GW recognizes that the UE is in the Connected state, a state capable of transmitting the downlink data directed to the UE.
[0014]
　In Solution 18, UE is, NAS message (ie, Service Request) without transmitting, can return to RRC-Connected and ECM-Connected. Further, as compared to existing (legacy) RRC connection setup procedure, it can be reduced following RRC message:
- RRC Connection Setup Complete;
- RRC Security Mode Command;
- RRC Security Mode Complete;
- RRC Connection Reconfiguration; and
& RRC Connection Reconfiguration Complete.
[0015]
　Non-Patent Document 2 describes that they want to use either of the architecture of the architecture and solution 18 of the above solution 2 UE may determine the attachment procedure. Further, Non-Patent Document 2 describes that the information for making it possible to select the solution 2 or solution 18 for data transmission to the network may include an AS procedure or NAS procedure.
CITATION
Non-Patent Document
[0016]
非特許文献1 : 3GPP TR 23.720 V1.2.0 (2015-11), “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for Cellular Internet of Things (Release 13)”, November 2015
非特許文献2 : 3GPP R2-156645, Qualcomm Incorporated, “NB-IoT SA2 architecture implications”, 3GPP TSG RAN WG2 #92, Anaheim, USA, 16-20 November 2015
Summary of the Invention
Problems that the Invention is to Solve
[0017]
　Inventors have conducted a study regarding communication architecture or communication architecture for power saving of the wireless terminal for CIoT, we found several problems. For example, Non-Patent Documents 1 and 2 are concrete to determine the architectural type used for the UE data packets transmitted from a plurality of communication architecture type (eg, solution 2 and solution 18) It does not show the procedure. Inventors have examined the specific communication procedures involving the determination of the communication architecture used for the UE as CIoT devices (or selection), the efficiency of communication procedure, reducing the signaling message, or an appropriate CN It has devised a number of improvements that contribute to such selection.
[0018]
　Further, for example, Non-Patent Documents 1 and 2 do not adequately account for the UE mobility as CIoT device. Here, mobility CIoT devices, idle mode (eg, RRC-Idle) cell change in (idle mode mobility) and Connected mode (eg, RRC-Connected mode) cell change in a (Connected mode mobility) including. Inventors have devised several improvements regarding mobility procedures of CIoT device.
[0019]
　Therefore, one of the objective to be achieved is the embodiment disclosed herein, with respect to the specific communication procedures involving the determination of the communication architecture used for the UE as CIoT devices (or selection), efficient communication procedure, reducing the signaling message, or contributes device to the appropriate CN selection is to provide a method, and a program. Incidentally, this objective should more embodiments disclosed herein is noted that only one of several objects of it and to achieve. Other objects or problems and novel features will become apparent from the description, or the accompanying drawings of this specification.
Means for Solving the Problems
[0020]
　In a first aspect, the radio terminal includes a memory, and at least one processor coupled to said memory. Wherein the at least one processor, Cellular Internet of Things (CIoT) regarding desires to any use of the plurality of communication architecture types for data packet transmission, one or supported, or any is set It is configured to transmit to the radio station a radio Resource Control (RRC) connection request message including the establishment cause, or other information elements indicating the dolphin.
[0021]
　In a second aspect, a method in a wireless terminal, Cellular Internet of Things (CIoT) regarding desires to any use more of the communication architecture types for data packet transmission, one or supported, or any comprises sending a radio Resource Control (RRC) connection request message including the establishment cause, or other information elements indicating whether the set to the radio station.
[0022]
　In a third aspect, the radio station includes a memory, and at least one processor coupled to said memory. Wherein the at least one processor is configured to receive a Radio Resource Control (RRC) connection request message from the wireless terminal. Furthermore, the at least one processor, Cellular Internet of Things whether the wireless terminal among the plurality of communication architecture types for data packet transmissions for (CIoT) wishes to any use, one or supported, or any is to establish factors or other information elements indicating whether the set is configured to retrieve from the RRC connection request message.
[0023]
　In a fourth aspect, a method in a wireless station, (a) from the wireless terminal to receive a Radio Resource Control (RRC) connection request message, and (b) Cellular Internet of Things (CIoT) for data packet transmissions for whether the wireless terminal among the plurality of communication architecture type wishes to any use, one or supported, or any is to establish factors or other information elements indicating whether the set from the RRC connection request message retrieve it, including the.
[0024]
　In a fifth aspect, the radio terminal includes a memory, and at least one processor coupled to said memory. Wherein the at least one processor, Cellular Internet of Things (CIoT) regarding desires to any use of the plurality of communication architecture types for data packet transmission, one or supported, or any is set the radio Resource Control (RRC) connection setup complete message containing the UE assistance information element indicating dolphin is configured to transmit to the radio station.
[0025]
　In a sixth aspect, a method in a wireless terminal, Cellular Internet of Things (CIoT) regarding desires to any use more of the communication architecture types for data packet transmission, one or supported, or It comprises transmitting a radio Resource Control (RRC) connection setup complete message containing the UE assistance information element indicating which is set in the wireless station.
[0026]
　In a seventh aspect, the wireless station includes a memory, and at least one processor coupled to said memory. Wherein the at least one processor is configured to receive a Radio Resource Control (RRC) connection setup complete message from the wireless terminal. Furthermore, the at least one processor, Cellular Internet of Things whether the wireless terminal among the plurality of communication architecture types for data packet transmissions for (CIoT) wishes to any use, one or supported, or any is a UE assistance information element indicating whether it is set is configured to retrieve from the RRC connection setup complete message.
[0027]
　In an eighth aspect, a method in a radio station, (a) from the wireless terminal Radio Resource Control (RRC) Connection Setup Complete message to receive, and (b) Cellular Internet of Things (CIoT) about a data packet transmission a plurality of either the wireless terminal in the communication architecture type wishes to any use, one or supports, or UE assistance said information elements RRC connection setup complete message indicating which is set for It is removed from, including.
[0028]
　In a ninth aspect, the wireless station includes a memory, and at least one processor coupled to said memory. Wherein the at least one processor is configured to receive a Radio Resource Control (RRC) connection setup complete message from the wireless terminal. Furthermore, the at least one processor, a second communication architecture types that data packets are transmitted over the user plane of the plurality of communication architecture types for data packet transmissions for Cellular Internet of Things (CIoT) when used for the wireless terminal, the RRC connection setup complete initial Non-Access Stratum (NAS) retrieved from the message downlink used message in the second communication architecture type tunnel It is configured to generate an encompassing initial UE message and the endpoint identifier. Furthermore, the at least one processor is configured to transmit the initial UE message to the core network.
[0029]
　In a tenth aspect, a method in a radio station,
(a) Radio Resource Control receiving a (RRC) connection setup complete message from the wireless terminal,
(b) Cellular Internet of Things (CIoT) for data packet transmissions for data packets among a plurality of communication architecture type is when the second communication architecture types that are transmitted through the user plane is used for the wireless terminal, retrieved from said RRC connection setup completion message initials Non-Access Stratum (NAS) message and generating an initial UE message including the downlink tunnel end point identifier to be used by the second communication architecture type, and
(c) the initial UE to send a message to the core network And,
including the.
[0030]
　In an eleventh aspect, the core network node includes a memory, and at least one processor coupled to said memory. Wherein the at least one processor is configured to receive the initial UE messages from the radio station. The initial UE message, and initials Non-Access Stratum (NAS) message from a wireless terminal, is determined by the radio station from among a plurality of communication architecture types for data packet transmissions for Cellular Internet of Things (CIoT) including the information element indicating the communication architecture type was. Furthermore, the at least one processor, based on said information element is configured to decide to reroute the initial NAS message to the core network corresponding to the determined communication architecture type. Furthermore, the at least one processor, the initial NAS message is configured to transmit the reroute NAS message request message indicating that it is rerouted to the core network to which the corresponding to the radio station.
[0031]
　In a twelfth aspect, a method in a core network node,
(a) receiving an initial UE message from the radio station, the initial UE message, and initials Non-Access Stratum (NAS) message from a wireless terminal, Cellular Internet of Things encompasses the information element indicating the communication architecture types that are determined by the radio station from among a plurality of communication architecture types for data packet transmissions for (CIoT);
(b) based on said information elements it decides to reroute the initial NAS message to the core network corresponding to the determined communication architecture type; and
reroute indicating that (c) the initial NAS message is rerouted to the corresponding core network said the NAS message request message radio Transmitting to the station;
including.
[0032]
　In a thirteenth aspect, the core network node includes a memory, and at least one processor coupled to said memory. Wherein the at least one processor is configured to receive the initial UE messages from the radio station. The initial UE message, initials Non-Access and Stratum (NAS) message, the wireless terminal to any use of the plurality of communication architecture types for data packet transmissions for Cellular Internet of Things (CIoT) from the wireless terminal It encompasses but they want, one or supports, or an information element indicating which is set. Wherein the at least one processor is based on said information element is configured to determine a communication architecture types used for data packet transmission of the wireless terminal. Furthermore, the at least one processor is configured to decide to reroute the initial NAS message to the core network corresponding to the determined communication architecture type. Furthermore, the at least one processor, the initial NAS message is configured to transmit the reroute NAS message request message indicating that it is rerouted to the core network to which the corresponding to the radio station.
[0033]
　In a fourteenth aspect, a method in a core network node,
(a) receiving an initial UE message from the radio station, the initial UE message, and initials Non-Access Stratum (NAS) message from a wireless terminal, Cellular Internet the wireless terminal of any use of the plurality of communication architecture type is desired either information element indicating either whether the support, or any are set for data packet transmissions for of Things (CIoT) encompasses;
; (b) on the basis of the information element, the determining the communications architecture types used for data packet transmission of the wireless terminal
corresponding to (c) the determined communication Architecture type child decides to reroute the initial NAS message to the core network ; And
and (d) to the initial NAS message to send reroute NAS message request message indicating that it is rerouted to the corresponding core network to the radio station;
including.
[0034]
　In a fifteenth aspect, the program, when loaded into a computer, the second, fourth above, sixth, eighth, causes a 10, a method according to the twelfth, or fourteenth aspect of the computer including instructions for the (software code).
Effect of the invention
[0035]
　According to the embodiments described above, with respect to specific communication procedures involving the determination of the communication architecture used for the UE as CIoT devices (or selection), the efficiency of communication procedure, reducing the signaling message, or an appropriate CN It can be provided which contributes to the selection device, method, and program.
BRIEF DESCRIPTION OF THE DRAWINGS
[0036]
Is a diagram illustrating an example of FIG. 1] CIoT architecture.
2 is a diagram showing an example of configuration of a wireless communication network in accordance with some embodiments.
3 is a sequence diagram showing an example of a communication procedure according to the first embodiment.
4 is a sequence diagram showing an example of a communication procedure according to the second embodiment.
5 is a sequence diagram showing an example of a communication procedure according to the third embodiment.
6 is a sequence diagram showing an example of a communication procedure according to the fourth embodiment.
7 is a sequence diagram showing an example of a communication procedure according to the fifth embodiment.
8 is a sequence diagram showing an example of a communication procedure according to the sixth embodiment.
9 is a sequence diagram showing an example of a communication procedure according to a seventh embodiment.
[10] is a sequence diagram showing an example of a communication procedure according to the eighth embodiment.
11 is a sequence diagram showing an example of a communication procedure according to a ninth embodiment.
12 is a sequence diagram showing an example of a communication procedure according to a ninth embodiment.
13 is a sequence diagram showing an example of a communication procedure according to a tenth embodiment.
14 is a sequence diagram showing an example of a communication procedure according to a tenth embodiment.
15 is a sequence diagram showing an example of a communication procedure according to the eleventh embodiment.
16 is a sequence diagram showing an example of a communication procedure according to the eleventh embodiment.
17 is a sequence diagram showing an example of a communication procedure according to a twelfth embodiment.
18 is a sequence diagram showing an example of a communication procedure according to the thirteenth embodiment.
19 is a sequence diagram showing an example of a communication procedure according to a fourteenth embodiment.
FIG. 20 is a sequence diagram showing an example of a communication procedure according to the nineteenth embodiment.
21 is a sequence diagram showing an example of a communication procedure according to the nineteenth embodiment.
22 is a sequence diagram showing an example of a communication procedure according to a twentieth embodiment.
FIG. 23 is a sequence diagram showing an example of a communication procedure according to a twentieth embodiment.
FIG. 24 is a sequence diagram illustrating an example of a communication procedure according to a twenty-first embodiment.
[FIG. 25A] is a sequence diagram showing an example of a communication procedure according to a twenty-first embodiment.
[FIG. 25B] is a sequence diagram showing an example of a communication procedure according to a twenty-first embodiment.
FIG. 26 is a block diagram showing a configuration example of a radio terminal according to some embodiments.
FIG. 27 is a block diagram showing an exemplary configuration of a base station in accordance with some embodiments.
[FIG. 28] is a block diagram showing an example of the configuration of a core network node according to some embodiments.
DESCRIPTION OF THE INVENTION
[0037]
　Hereinafter, specific embodiments will be described in detail with reference to the drawings. In the drawings, the same or corresponding components are denoted by the same reference numerals, for clarity of description, repeated explanation is omitted as appropriate.
[0038]
　A plurality of embodiments described below can can either be carried out independently, also be implemented in appropriate combination. These several embodiments have different novel features together. Accordingly, the plurality of embodiments, contribute to solving the different purpose or task to each other, which contributes to achieve different effects from each other.
[0039]
　A plurality of embodiments described below are described the wireless communication network for CIoT including LTE emtc and NB-IoT as the main subject. However, these embodiments may be applied to a wireless communication network for other CIoT.
[0040]

　FIG. 2 shows a configuration example of a wireless communication network according to some embodiments including the present embodiment. In the example of FIG. 2, UE1 as CIoT devices communicate with the application server 4 via the CIoT radio access network (RAN) 2 and a core network (CN) 3. RAN2 supports multiple communication architecture types for data packet transmissions for CIoT. RAN2 broadcasts the cell using explicit or implicitly indicate information, for example, Master Information Block (MIB) or System Information Block (SIB) a plurality of communication architecture type supported by RAN2. UE1 supports at least one of the plurality of communication architecture type. CN3 supports the plurality of communication architecture type. CN3 includes a plurality of individual dedicated directed to a part of the communication architecture type CN (DCN), it may include another DCN directed to some other.
[0041]
　In some implementations, the plurality of communication architecture types, may include first and second communication architecture types that correspond to the solution 2 and 18 shown in Non-Patent Document 1. In the first communication architecture type, is transmitted via the user data packet is the control plane is transmitted or received by the UE1 (eg, NAS messages between the UE and the MME / C-SGN). In the first communication architecture type, the DRB by RAN2 for transmission UE1 data packet setup is not required. With regard SRB used to send the data packet, Access Stratum (AS) security by RAN2 (ie, ciphering and deciphering of control plane data, and integrity protection and integrity verification of control plane data) may be omitted. In other words, the process of the Packet Data Convergence Protocol (PDCP) layer for SRB used to send the data packet may be omitted. In this case, the UE1 data packet, NAS security keys with UE1 and CN3 (eg, MME, C-SGN) is encrypted and decrypted by. On the other hand, in the second communication architecture type, via the user data packet is the user plane (eg, DRB and General Packet Radio Service (GPRS) Tunneling Protocol (GTP) EPS bearers including tunnel) sent or received by the UE1 It sent Te.
[0042]
　UE1 may support one or both of the LTE emtc and NB-IoT. In other words, UE1 may support either or both CIoT RAT (NB-IoT RAT) and LTE RAT (eMTC). RAN2 may include either or both of the eNB to support CIoT CIoT BS and LTE RAT supports the RAT (NB-IoT RAT) (eMTC). CN3 is, C-SGN, or MME and S-GW, or may include both. CN3 further, P-GW, Home Subscriber Server (HSS), and Policy and Charging Rules Function (PCRF) may include other network entities such as.
[0043]
　Figure 3 is a sequence diagram showing an example of a communication procedure according to the present embodiment. The steps in FIG. 3, during the attach procedure to the UE1 of CN3, communication architecture type used for transmission of UE1 data packet is determined. UE1 determines the communication architecture types used for data packet transmission of UE1, explicitly or implicitly established factors shown (establishment cause) RRC connection request including the determined communication architecture type (RRC sending a Connection Request) message to RAN2.
[0044]
　In step 301, UE1 determines the communication architecture types used for data packet transmission of UE1 (selection). In some implementations, UE1, based on the preset default UE capabilities UE1 (capability data), may select the communication architecture type to use. Additionally or alternatively, UE1 measures the estimated propagation loss between the received power of the reference signal from RAN2 (RSRP) or UE1 and RAN2 (CIoT-BS / eNB), measured RSRP or propagation based on the loss, you may select the communication architecture type to use. Additionally or alternatively, UE1 is the coverage improvement is needed the (coverage enhancement (CE)) levels were determined based on RSRP or propagation loss was measured, selects a communication architecture type on the basis of the CE level it may be. Additionally or alternatively, UE1, the data transmission trigger (eg, mo-Data, mo-ExceptionData, mt-Access, mo-Signaling) may select a communication architecture type according to. Additionally or alternatively, UE1 may select a communication architecture type according to the type of application that performs transmission data packet.
[0045]
　In step 302, UE1 initiates a random access procedure. That, UE1 transmits a random access preamble (Random Access Channel (RACH) preamble) to RAN2, receiving a random access response (RAR) message from RAN2.
[0046]
　In step 303, UE1 is the third message (Msg3) of the random access procedure, i.e. transmits RRC connection request (RRC Connection Request) message to RAN2. The RRC Connection Request message is transmitted using the SRB 0 on Common Control Channel (CCCH). The RRC Connection Request message includes an explicit or established factors implicitly shown (establishment cause) information element communications architecture types that are determined (selected) by the UE1.
[0047]
　Here, establishment cause indicating a communication architecture type, for example, in the case of a communication architecture type of the first (or second) is, one of ordinary establish factors (eg, mo-Data, mo-ExceptionData, use mo-Signaling, mt-Access) and, in the case of the communication architecture type of the second (or first) may use a particular establishment cause. Certain established factors, when applied to the first communication architecture types, information indicating that for example a communication architecture type for transmitting user data in NAS message (eg, mo-DataOverNAS, mo-ExceptionDataOverNAS, mo- SignalingDataOverNAS, mt-AccessDataOverNAS) any good. Also, certain established factors, when applied to a second communication architecture types, information indicating that transmitting user data in the user plane (UP) (AS message) for example by setting the DRB (eg, mo- DataUP, mo-ExceptionDataUP, mo-SignalingUP, mt-AccessUP) any good.
[0048]
　In step 304, RAN2, in response to receiving the RRC Connection Request message, transmits an RRC connection setup (RRC Connection Setup) message to the UE1. The RRC Connection Setup message is transmitted using the SRB 0 on CCCH. The RRC Connection Setup message includes the configuration information for SRB 1, makes it possible to use a Dedicated Control Channel (DCCH) in the subsequent (Subsequent) signaling.
[0049]
　The RRC Connection Setup message may indicate the need for a PDCP. More specifically, the RRC Connection Setup message, the need for PDCP (e.g. whether to use conventional the PDCP) may indicate to the UE1. In some implementations, the flag information indicating the need for PDCP may be included in the RRC Connection Setup in ArueidiioResourceConfigDedicated IE message are included or in other IE.
[0050]
　In some implementations, PDCP settings that are included in the RRC Connection Setup message (pdcp-Config) may indicate the need for a PDCP. The PDCP configuration, the need for PDCP (e.g. whether to use conventional the PDCP) may include flag information indicating the UE1. The PDCP configuration may include information indicating whether or not to enable PDCP Config of default settings SRB1 to UE1. The PDCP configuration, specific PDCP Config (e.g., RLC-SAP and PDCP Sequence Number (SN) length is applied to SRB1) may contain. Alternatively, RAN2, depending on the communication architecture types that are determined by the UE1, may determine whether to include a PDCP set in the RRC Connection Setup message (pdcp-Config). Specifically, RAN2, when UE1 selects the second communication architecture type, may include a PDCP configuration for SRB 1 to the RRC Connection Setup message.
[0051]
　In step 305, UE1 transmits RRC connection setup complete (RRC Connection Setup Complete) message to RAN2. The RRC Connection Setup Complete message is transmitted using the SRB 1 on DCCH. The RRC Connection Setup Complete message carries the initial NAS message. Incidentally, FIG. 3 because directed to a attach procedure, the initial NAS message is an attach request (Attach Request) message. The Attach Request message includes the EPS is set to "CIoT Attach" attach type IE (information element).
[0052]
　RAN2 receives RRC Connection Setup Complete message from the UE1, S1AP RRC Connection Setup Complete initial NAS message retrieved from the message (ie, Attach Request message) to CN3 (eg, MME, C-SGN) to: Initial UE ( transmitted using Initial UE) message. Initial NAS message (ie, Attach Request message), S1AP: Initial UE NAS-Protocol Data Unit (PDU) message embedded in IE (information element). RAN2 is an information element indicating communication architecture types that are determined (selected) by the UE1 S1AP: Initial may be included in the UE message. RAN2 selects the DCN corresponding to the communication architecture types that are determined by the UE1 from within CN3, initial NAS message (ie, Attach Request message) carrying the S1AP: Initial be transmitted to DCN to the selected UE Message good.
[0053]
　In step 306, CN3 (eg, MME, C-SGN) executes an authentication (Authentication) and security procedures, setting up the NAS security. Authentication and security procedures downlink NAS messages required (ie, Authentication Request and NAS Security Mode Command) is, RRC: transmitted on SRB 1 using DL Information Transfer messages. Likewise, authentication and security procedures uplink NAS messages required (ie, Authentication Response and NAS Security Mode Complete) is, RRC: transmitted on SRB 1 using UL Information Transfer message.
[0054]
　In step 307, CN3 (eg, MME, C-SGN) is, NAS: transmits Attach approve (Attach Accept) message to the UE1. Incidentally, the session for the UE1 (eg, DRB and S1 bearer) setup may not be performed. Therefore, CN3 (eg, MME, C-SGN) is, S1AP: Initial Context Setup Request message RAN2 (eg, CIoT-BS, eNB) does not need to be sent to. Therefore, the Attach Accept message, S1AP: Downlink may be transmitted from CN3 to RAN2 using NAS transport message. Then, RAN2 is the Attach Accept message, RRC: transmitted to UE1 on SRB 1 using DL Information Transfer messages.
[0055]
　UE1 receives via RAN2 the Attach Accept message from CN3. Attach Accept message, transfers the data type (eg, IP, non-IP, SMS) and UE address (eg, IP address) may indicate. UE1, in response to receiving the Attach Accept message, NAS: sends the Attach Complete (Attach Complete) message to the CN3. The Attach Complete message, RRC: sent to RAN2 on SRB 1 using UL Information Transfer message. RAN2 is, S1AP the Attach Complete message received: forwarding to CN3 using Uplink NAS transport message.
[0056]
　In step 308, RAN2 transmits RRC connection release (RRC Connection Release) message to the UE1 on SRB 1. CN3 is, S1AP: S1 by sending to RAN2 a UE Context Release Command message may request the release of the RRC connection to the UE1 to RAN2. RRC connection release in response to receiving the (RRC Connection Release) message, UE1 transitions from RRC-Connected mode in RRC-Idle mode. In order of UE1 as CIoT device may be defined different other dormant mode or condition existing RRC-idle mode. Therefore, UE1, in response to receiving the RRC connection release (RRC Connection Release) message, may transition to the RRC-Idle mode or other sleep mode. The other dormant mode or state, information about the RRC connection to holds the (eg, Access Stratum Security Context, bearer related information, L2 / 1 parameters), it is used in the second communication Architecture Type good.
[0057]
　Attach Accept message in step 307, RRC Connection Release message of step 308, or downlink NAS message from the other CN3 to the UE1 communication architecture type used for UE1 (eg, Applied Architecture Type, Selected Architecture Type ) may be explicitly or implicitly indicates.
[0058]
　In step 309, UE1 stores a communication architecture types that are set in the Attach procedure (stored).
[0059]
　Procedure shown in FIG. 3, for example may be modified as follows. UE1, in RRC Connection Request message (step 303), together with the usual established factors may indicate a communication architecture type with a different information element. The specific information elements, for example, information element indicating whether you select the first and second communication architecture type (eg, Selected Architecture Type, Applied Architecture Type) may be used. For example the UE1, the value of the information element to indicate a first communication architecture type set DataOverNAS (DONAS) or Type 1, RRC value of the information element to indicate a second communication Architecture Type -Suspend or may be set to Type 2.
[0060]
　For example, the specific information element, SelectedArcType ENUMERATED {type1, type2} (or, {dataOverNAS, rrc-Suspend}) may be defined as. Alternatively, the specific information element, flag information indicating that selects the first communication architecture type (eg, SelectedArcType ENUMERATED {type1}, ArcType1 ENUMERATED {true}) may be used. Moreover, instead of this, the specific information element, flag information indicating that selects the second communication architecture type (eg, SelectedArcType ENUMERATED {type2}, ArcType2 ENUMERATED {true}) may be used.
[0061]
　On the other hand one of the two communication architecture type if the method of transmitting flag information indicating that the (eg, second communication architecture type) is selected is mounted to UE1, UE1 the other communication architecture type ( eg, be used first communication architecture type) may be defined as the default (basic settings). Thus, if the UE1 does not send the flag information, UE1 may be deemed to have selected the default communication architecture type. That, RAN2 that do not receive the flag information, recognizes that UE1 selects the default communication architecture type.
[0062]
　Procedure shown in FIG. 3, for example, may be further modified as follows. RAN2 may use other different communication architecture type for the UE1 communication architecture type shown in RRC Connection Request message (step 303) by UE1. In this case, RAN2, using the RRC Connection Setup message (step 304), the other communication architecture type (eg, Applied Architecture Type, Selected Architecture Type) and may inform the UE1. Alternatively, RAN2 transmits the RRC Connecion Reject message to UE1 instead in step 304, the other communication architecture type in the message may notify the UE1. In response to reception of the other communication architecture type of notification, UE1 terminates the current attach procedure may be restarted from a new RRC connection setup procedure (RRC Connection Setup procedure). Alternatively, UE1 according notifies other communication architecture type from RAN2, may continue the current attach procedure and RRC connection setup procedure.
[0063]
　If the user plane second communication architecture types user data packet via a (eg, DRB and GPRS Tunneling Protocol (GTP) EPS bearers including tunnel) is transmitted is used for UE1, CN3 is in step 307, NAS: the Attach Accept message S1AP: Initial Context Setup Request may be transmitted to RAN2 included in the message. The S1AP: Initial Context Setup Request message, the security key (K used for UE1 eNB including) and UE Security Algorithm. RAN2 the security key received (K eNB according) and UE Security Algorithm, may perform the AS security setup. AS security setup, NAS: Attach may be performed before sending Accept the message to the UE1, it may be performed after sending.
[0064]
　Although Figure 3 shows a Mobile Originated (MO) data transmission, the same procedure as in FIG. 3 may be applied to a Mobile Terminated (MT) data transmission.
[0065]
　According to the example of FIG. 3, UE1 is established factors indicating communication architecture type was determined, the determined communications architecture types used for transmission of UE1 data packet (establishment cause), or other information elements the RRC Connection Request message including sending to RAN2. The use of established factors or other information elements of RRC Connection Request message to indicate the communication architecture types that are determined by the UE1 results for example the following advantages. To a 1, UE1 may transmit a communication architecture types that are determined by the UE1 as AS (RRC) information instead of NAS information. Therefore, RAN2 may UE1 is able to recognize the communication architecture type desired, RAN2 can perform processing UE1 is corresponding to the communication architecture type desired (eg, selection of the CN (DCN)) . To a 2, UE1 may notify the RAN2 communication architecture types that are determined by the UE1 before setting RRC connection. Therefore, RAN2 can reduce the number of signaling messages required to set up the RRC connection depending on the communication architecture determined by UE1.
[0066]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. In the present embodiment, other communication procedures involving the determination of communication architecture used for UE1 (or selection) is described. Figure 4 is a sequence diagram showing an example of a communication procedure according to the present embodiment. The steps in FIG. 4, during the attach procedure to the UE1 of CN3, communication architecture type used for transmission of UE1 data packet is determined. UE1 is, RRC Connection including explicitly or implicitly shown, the information elements regarding the communication architecture type determines the communication architecture type, the determined communication architecture types used for transmission of UE1 data packet to send a Setup Complete message to RAN2.
[0067]
　Step 401-404 are the same as steps 301-304 shown in FIG. However, RRC Connection Request message in step 403 does not indicate a communication architecture types that are determined (selected) by the UE1.
[0068]
　In step 405, UE1 transmits RRC connection setup complete (RRC Connection Setup Complete) message to RAN2. The RRC Connection Setup Complete message is transmitted using the SRB 1 on DCCH. The RRC Connection Setup Complete message includes indicating explicitly or implicitly a communications architecture types that are determined by the UE1, and UE assistance IE (information element) about the communication architecture type, and initial NAS message. UE assistance IE may be a NAS information, may be AS (RRC) information.
[0069]
　If UE assistance IE is AS (RRC) information, RAN2, depending on the communication architecture types that are determined by the UE1, to PDCP configuration for SRB 1 to (pdcp-Config) may be transmitted to UE1 , using the PDCP layer (application) may notify the UE1. Specifically, RAN2, when UE1 selects the second communication architecture types, may transmit the PDCP configuration for SRB 1 to UE1.
[0070]
　RAN2 uses receives RRC Connection Setup Complete message from the UE1, RRC Connection Setup Complete message initial NAS message retrieved from (ie, Attach Request message) to CN3 (eg, MME, C-SGN) of the initial UE message to send Te. If UE assistance IE is AS (RRC) information, RAN2 is, Initial UE selects the DCN corresponding to the communication architecture types that are determined by the UE1 from within CN3, carrying an initial NAS message (ie, Attach Request message) messages may be sent to the selected DCN the. In contrast, UE Assistance IE be a NAS information, UE assistance IE is S1AP with initial NAS message: embedded in Initial UE message of NAS-PDU IE (information element). In this case, RAN2 is explicitly or implicitly indicate notify the communication architecture types that are determined by the UE1, for example, Initial Context Setup Request message (eg, Architecture Type IE), may be received from CN3.
[0071]
　Step 406-409 are the same as steps 306-309 in FIG. 3.
[0072]
　Procedure shown in FIG. 4, for example, may be modified as follows. RAN2 or CN3 may use other different communication architecture types and communication architecture type shown in RRC Connection Setup Complete message or Attach Request message (step 404) by UE1 for UE1.
[0073]
　RAN2 in response to RRC Connection Setup Complete message (step 404), another communication architecture type (eg, Applied Architecture Type, Selected Architecture Type) may send an RRC Connection Reject message to the UE1 showing the. In this case, UE1 may restart a new RRC connection setup procedure.
[0074]
　Alternatively, CN3, using the Attach Accept message (step 407), another communication architecture type (eg, Applied Architecture Type, Selected Architecture Type) and may inform the UE1. In this case, UE1, exit the current attach procedure, may be re-start from a new RRC connection setup procedure. Alternatively, UE1 according notifies other communication architecture type from RAN2, it may continue the current attach procedure.
[0075]
　If the user plane second communication architecture types user data packet via a (eg, DRB and GPRS Tunneling Protocol (GTP) EPS bearers including tunnel) is transmitted is used for UE1, CN3 is in step 407, NAS: the Attach Accept message S1AP: Initial Context Setup Request may be transmitted to RAN2 included in the message. The S1AP: Initial Context Setup Request message, the security key (K used for UE1 eNB including) and UE Security Algorithm. RAN2 the security key received (K eNB according) and UE Security Algorithm, may perform the AS security setup. AS security setup, NAS: Attach may be performed before sending Accept the message to the UE1, it may be performed after sending.
[0076]
　Although Figure 4 shows a Mobile Originated (MO) data transmission, the same procedure as in FIG. 4 may be applied to a Mobile Terminated (MT) data transmission.
[0077]
　According to the example of FIG. 4, UE1 is the RRC Connection Setup Complete message containing the UE assistance IE indicating a communication architecture type was determined, the determined communications architecture types used for transmission of UE1 data packet to send to the RAN2. The use of RRC Connection Setup Complete message to indicate the communication architecture types that are determined by the UE1 may, for example result in the following advantages. In some implementations, UE1 may transmit a communication architecture types that are determined by the UE1 as NAS information. Therefore, UE1 can easily inform the communication architecture types UE1 wishes to CN3.
[0078]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. In the present embodiment, other communication procedures involving the determination of communication architecture used for UE1 (or selection) is described. Figure 5 is a sequence diagram showing an example of a communication procedure according to the present embodiment. In the procedure of FIG. 5, during the attach procedure to the UE1 of CN3, the communication architecture types used for transmission UE1 data packet RAN2 is determined (or selected).
[0079]
　Step 501-504 are the same as steps 402 to 405 shown in FIG. However, RRC Connection Setup Complete message in step 504 indicates explicitly or implicitly one or more communication architecture type supported by UE1, information elements (eg regarding the communication architecture types, UE the Supported Architecture Type )including. The information element is AS (RRC) information. Therefore, RAN2 (eg, CIoT-BS, eNB), based on the information elements, it can detect one or more communication architecture type supported by UE1.
[0080]
　The information element, for example may indicate the communication architecture type supported by UE1 (eg, {type1, type2, ..}, or {DONAS, RRC-Suspend, ..}). The information element, which type of the plurality of communications architecture types may be a bitmap indicating it is supported by the UE1. The information element, except for the default communication architecture type, or may be a flag or bit map indicating whether one or communication architecture type of the plurality of options are supported by the UE1. That is, the information element may indicate that the communication architecture type options are supported (eg, typeX supported), it may indicate whether it is supported (eg, Support of typeX = ENUMERATED {true, ...}, or {Supported, Not Supported}). The above type1, type2 (and TypeX), for example DataOverNAS (DONAS), may be replaced by a name indicating a more specific communication architecture type as RRC-Suspend.
[0081]
　In step 505, RAN2 considers one or more communication architecture type supported by UE1, determining the communications architecture types used for UE1. In some implementations, RAN2, based on preset default UE capabilities UE1 (capability data), may select the communication architecture types used for UE1. Additionally or alternatively, RAN2, based on estimated propagation loss between the received power due to UE1 of the reference signal from RAN2 (RSRP) or UE1 and RAN2 (CIoT-BS / eNB), for UE1 You may select the communication architecture type to use. Measurement results of the RSRP or propagation loss may be sent from UE1 to RAN2. Additionally or alternatively, RAN2, based on CN3 network capability (capability data), may select the communication architecture types used for UE1. Additionally or alternatively, RAN2, based on the load of RAN2 (eg, Cell load, S1 Transport Network Layer (TNL) load, number of Connected UEs, number of UEs whose UE context stored), used for the UE1 the communication architecture types that may be selected.
[0082]
　RAN2, depending on the communication architecture types that are determined by the UE1, to PDCP configuration for SRB 1 to (pdcp-Config) may be sent to the UE1, the UE1 to use PDCP layer (application) it may be notified. Specifically, RAN2, when selecting the second communication architecture type for UE1, may transmit the PDCP configuration for SRB 1 to UE1.
[0083]
　In step 506, RAN2 is, S1AP RRC Connection Setup Complete initial NAS message retrieved from the message (ie, Attach Request message) to the CN3 (eg, MME, C-SGN): transmitted using Initial UE message. Initial NAS message (ie, Attach Request message), S1AP: embedded in Initial UE message of NAS-PDU IE (information element). RAN2 is an information element indicating the communication architecture type determined in step 505 S1AP: Initial may be included in the UE message. RAN2 is a DCN corresponding to the communication architecture type determined in step 505 to select from within CN3, initial NAS message (ie, Attach Request message) carrying the S1AP: Initial be transmitted to DCN to the selected UE Message good.
[0084]
　Step 507-510 are the same as steps 306-309, or steps 406-409 of FIG. 4 in FIG.
[0085]
　If the second communication architecture type is used for UE1, the procedure shown in FIG. 5, as well as other procedures as described above, it may be modified to perform the AS security setup. Although Figure 5 shows a Mobile Originated (MO) data transmission, the same procedure as in FIG. 5 may be applied to a Mobile Terminated (MT) data transmission.
[0086]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. In the present embodiment, other communication procedures involving the determination of communication architecture used for UE1 (or selection) is described. Figure 6 is a sequence diagram showing an example of a communication procedure according to the present embodiment. In the procedure of FIG. 6, during the attach procedure to the UE1 of CN3, RAN2 determines the communication architecture type to be used for transmission of UE1 data packets. The procedure of FIG. 6 shows explicitly or implicitly one or more communication architecture type supported by UE1, information elements related to the communication architecture type (eg, UE Supported Architecture Type) is RRC Connection points to be transmitted using the Request message is different from the procedure shown in FIG.
[0087]
　Step 601 and 602 are similar to steps 302 and 303 shown in FIG. However, RRC Connection Request message of step 602 includes information elements indicating the one or more communication architecture type supported by UE1 to (eg, UE Supported Architecture Type). The information element is AS (RRC) information. Therefore, RAN2 (eg, CIoT-BS, eNB), based on the information elements, it can detect one or more communication architecture type supported by UE1.
[0088]
　In step 603, RAN2 considers one or more communication architecture type supported by UE1, determining the communications architecture types used for UE1.
[0089]
　Step 604 is similar to step 304 of FIG. However, RRC Connection Setup message in step 604, the communication architecture types that are determined by RAN2 in step 603 (eg, Applied Architecture Type, Selected Architecture Type) may indicate.
[0090]
　Step 605 and 606 are similar to steps 305 of FIG. However, RAN2 the communication architecture type determined in step 603 (eg, Applied Architecture Type, Selected Architecture Type) information element indicating S1AP: Initial may be included in the UE message. RAN2 is a DCN corresponding to the communication architecture type determined in step 603 to select from within CN3, carry initial NAS message (ie, Attach Request message) S1AP: Initial transmit the DCN to the selected UE Message it may be.
[0091]
　Step 607-610 are the same as steps 507-510 in steps 306-309 of FIG. 3 or FIG.
[0092]
　If the second communication architecture type is used for UE1, the procedure shown in FIG. 6, as well as other procedures as described above, it may be modified to perform the AS security setup. Although Figure 6 shows a Mobile Originated (MO) data transmission, the same procedure as in FIG. 6 may be applied to a Mobile Terminated (MT) data transmission.
[0093]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. In the present embodiment, other communication procedures involving the determination of communication architecture used for UE1 (or selection) is described. Figure 7 is a sequence diagram showing an example of a communication procedure according to the present embodiment. In the procedure of FIG. 7, during the attach procedure to the UE1 of CN3, RAN2 determines the communication architecture type to be used for transmission of UE1 data packets. The procedure of FIG. 7 shows explicitly or implicitly one or more communication architecture type supported by UE1, information elements (eg, UE Supported Architecture Type) relating to the communications architecture type is initial NAS message (ie, Attach Request message) with a different and procedures that it is transmitted is shown in FIGS. 5 and 6 as NAS information.
[0094]
　Step 701-704 are the same as steps 402 to 405 shown in FIG. However, in step 704, UE1 transmits NAS information element indicating one or more communication architecture type supported by UE1 (eg, UE Supported Architecture Type) together with Attach Request message. The NAS information element, for example may indicate the communication architecture type supported by UE1 (eg, {type1, type2, ..}, or {DONAS, RRC-Suspend, ..}). Alternatively, the NAS information element may indicate that the communication architecture type options are supported (eg, typeX supported), may indicate whether it is supported ( eg, Support of typeX = ENUMERATED {true, ...}, or {Supported, Not Supported}). The above type1, type2 (and TypeX), for example DataOverNAS (DONAS), may be replaced by a name indicating a more specific communication architecture type as RRC-Suspend.
[0095]
　In step 705, CN3 is 1 or more communication architecture type supported by UE1 (eg, UE Supported Architecture Type) S1AP showing the: sending a Initial Context Setup Request message to RAN2. In step 706, RAN2 considers one or more communication architecture type supported by UE1 based on the information received from CN3, determining the communications architecture types used for UE1. RAN2 is determined the communication architecture type to CN3 S1AP: Initial Context Setup Response may be notified using a message (step 707).
[0096]
　Step 708-711 are steps 306-309 of FIG. 3, steps 507-510 in FIG. 5, or the same as steps 607-610 in FIG. 6.
[0097]
　If the second communication architecture type is used for UE1, the procedure shown in FIG. 7, as well as other procedures as described above, it may be modified to perform the AS security setup. Figure 7 but shows a Mobile Originated (MO) data transmission, the same procedure as in FIG. 7 may be applied to a Mobile Terminated (MT) data transmission.
[0098]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. In the present embodiment, other communication procedures involving the determination of communication architecture used for UE1 (or selection) is described. Figure 8 is a sequence diagram showing an example of a communication procedure according to the present embodiment. The steps in FIG. 8, during the attach procedure to the UE1 of CN3, RAN2 determines the communication architecture type to be used for transmission of UE1 data packets. The procedure of FIG. 8 shows explicitly or implicitly one or more communication architecture type supported by UE1, the communication architecture type of Information Elements (eg, UE Supported Architecture Type) from HSS5 CN3 different (eg, MME, C-SGN ) and procedures that are sent to via the RAN2 is shown in FIGS. 5-7.
[0099]
　Step 801-804 are the same as steps 701-704 shown in Figure 7. However, in step 804, UE1 is, NAS information element indicating one or more communication architecture type supported by UE1 (eg, UE Supported Architecture Type) there is no need to transmit.
[0100]
　In step 805, CN3 (eg, MME, C-SGN) executes an authentication (Authentication) and security procedures, setting up the NAS security. In step 806, CN3 (eg, MME, C-SGN), when receiving UE1 authentication information (Authentication Information) from HSS 5, 1 or more communication architecture type supported by UE1 (eg, UE the Supported Architecture Type) received from the HSS5. HSS5 manages UE the Supported Architecture Type as subscriber information of UE1.
[0101]
　Step 807-809 are the same as steps 705-707 in FIG. Step 810-812 are steps 307-309 of FIG. 3, steps 508-510 of FIG. 5 are similar to steps 709-711 in steps 608-611, or 7 of Figure 6.
[0102]
　If the second communication architecture type is used for UE1, the procedure shown in FIG. 8, as well as other procedures as described above, it may be modified to perform the AS security setup. Figure 8 but shows a Mobile Originated (MO) data transmission, the same procedure as in Figure 8, may be applied to Mobile Terminated (MT) data transmission.
[0103]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. In the present embodiment, other communication procedures involving the determination of communication architecture used for UE1 (or selection) is described. Figure 9 is a sequence diagram showing an example of a communication procedure according to the present embodiment. The steps in FIG. 9, during the attach procedure to the UE1 of CN3, CN3 determines the communication architecture type to be used for transmission of UE1 data packets.
[0104]
　Step 901-904 are the same as steps 701-704 in FIG. That is, in step 904, CN3 (eg, MME, C-SGN) shows explicitly or implicitly one or more communication architecture type supported by UE1, NAS information elements regarding the communication architecture type (eg, UE Supported Architecture Type) received from UE1 with the Attach Request message.
[0105]
　In step 905, CN3 may consider one or more communication architecture type supported by the UE1 (UE Supported Architecture Type), determines a communication architecture types used for UE1. In some implementations, CN3, based on preset default UE capabilities UE1 (capability data), may select the communication architecture types used for UE1. Additionally or alternatively, CN3 is, RAN2 (eg, CIoT BS, eNB) based on the network capability of (capability data), you may select the communication architecture types used for UE1. Additionally or alternatively, the communication architecture CN3 is a load of CN3 (eg, S1 Transport Network Layer (TNL) load, number of Connected UEs, number of UEs whose UE context stored) based on, used for UE1 type may be selected. Additionally or alternatively, CN3 is, Quality of Service that apply to UE1 (QoS) (eg, QoS Class Identifier (QCI), Allocation and Retention Priority (ARP), the resource type (Guaranteed Bit Rate (GBR) or non based on -GBR)), may be selected communication architecture types used for UE1.
[0106]
　In step 906, CN3, the communication architecture type determined in step 905 (eg, Applied Architecture Type, Selected Architecture Type) S1AP showing the: sending a Initial Context Setup Request message to RAN2. RAN2 MAY send a response to the notification of step 906 (step 907).
[0107]
　Step 908-911 are steps 306-309 of FIG. 3, steps 406-409 of FIG. 4, steps 507-510 of FIG. 5 are similar to steps 708-711 in steps 607-610, or 7 of Figure 6 .
[0108]
　If the second communication architecture type is used for UE1, the procedure shown in FIG. 9, as well as other procedures as described above, it may be modified to perform the AS security setup. Although Figure 9 shows a Mobile Originated (MO) data transmission, the same procedure as in FIG. 9 may be applied to a Mobile Terminated (MT) data transmission.
[0109]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. In the present embodiment, other communication procedures involving the determination of communication architecture used for UE1 (or selection) is described. Figure 10 is a sequence diagram showing an example of a communication procedure according to the present embodiment. In the procedure of FIG. 10, during the attach procedure to the UE1 of CN3, CN3 determines the communication architecture type to be used for transmission of UE1 data packets. The procedure of FIG. 10 shows explicitly or implicitly one or more communication architecture type supported by UE1, the communication architecture type of Information Elements (eg, UE Supported Architecture Type) from HSS5 CN3 different (eg, MME, C-SGN ) and procedures that are sent to was shown in FIG.
[0110]
　Step 1001-1006 are the same as steps 801-806 in FIG. Step 1007-1009 are the same as steps 905-907 in FIG. Step 1010-1012 are steps 307-309 of FIG. 3, steps 407-409 of FIG. 4, steps 508-510 of FIG. 5, steps 608 to 610 in FIG. 6, steps 709 to 711 in FIG. 7, the steps of FIG. 8 810-812, or the same as steps 909-911 in FIG.
[0111]
　If the second communication architecture type is used for UE1, the procedure shown in FIG. 10, as well as other procedures as described above, it may be modified to perform the AS security setup. Figure 10 is illustrates a Mobile Originated (MO) data transmission, the same procedure as in FIG. 10 may be applied to a Mobile Terminated (MT) data transmission.
[0112]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. In the present embodiment, other communication procedures involving the determination of communication architecture used for UE1 (or selection) is described. 11 and FIG. 12 is a sequence diagram showing an example of a communication procedure according to the present embodiment. In the procedure of FIG. 11 and FIG. 12, during the RRC connection setup procedure for after Attach Complete UE1 is to transition to the transmit data packet from the RRC-Idle mode (or other dormant mode) RRC-Connected mode, UE1 is determined communication architecture types used for data packet transmission of UE1 (or selection) to.
[0113]
　Figure 11 shows a case where the first communication architecture type is used for UE1. As already described, in the first communication architecture type, is transmitted via the user data packet is the control plane is transmitted or received by the UE1 (eg, NAS messages between the UE and the MME / C-SGN) . On the other hand, FIG. 12 shows a case where the second communication architecture type is used for UE1. In the second communication architecture type, is transmitted via the user data packet is the user plane (eg, DRB and GPRS Tunneling Protocol (GTP) EPS bearers including tunnel) sent or received by the UE1.
[0114]
　Figure 11 will be described. In step 1101, UE1 determines the communication architecture types used for data packet transmission of UE1 (selection). Parameters considered to determine the communications architecture types, may be similar to step 301 of FIG. In the example of FIG. 11, UE1 is the communication architecture type for each transmission opportunity of data packets can be determined (selected). Therefore, UE1 is the parameter that dynamically changes every transmission opportunity of data packets may be considered. For example, UE1, the data transmission trigger (eg, mo-Data, mo-ExceptionData, mt-Access, mo-Signaling) may select a communication architecture type according to. Additionally or alternatively, UE1 may select a communication architecture type according to the type of application that performs transmission data packet.
[0115]
　Step 1102 to 1106 are the same as steps 302-305 in FIG. 3. However, the example of FIG. 11 shows a transition from RRC-Idle mode after Attach Complete (or other dormant mode) to RRC-Connected mode. Further, in the example of FIG. 11, in step 1101, UE1 selects the first communication architecture type. Thus, initial NAS message sent by the UE1 at step 1105, a NAS message carrying the small data. That, UE1 may piggyback the small data on initial NAS message.
[0116]
　In step 1106, RAN2 is, RRC Connection Setup Complete initial NAS message retrieved from the message (ie, NAS message carrying the small data) CN3 (eg, MME, C-SGN) on S1AP: Initial with UE message transmission to. Initial NAS message (ie, NAS message carrying the small data), S1AP: embedded in Initial UE message of NAS-PDU IE (information element). RAN2 is explicitly or implicitly indicating the information element of the first communication architecture types that are determined by the UE1 S1AP: Initial may be included in the UE message. RAN2 is a DCN corresponding to the first communication architecture types that are determined by the UE1 selected from within CN3, S1AP: Initial UE message may be sent to the selected DCN the.
[0117]
　In step 1107, CN3 (eg, MME, C-SGN), in order to obtain a small data packet, decodes the uplink NAS message from the UE1 (decrypt). In step 1108, CN3, depending on the data type of small data packets, and forwards the small data packets. If an ACK or response to Mobile Originated small packets are expected, CN3 receives a response downlink data packets arriving (step 1109). In step 1110, CN3 encrypts the downlink data packet to generate a downlink NAS message carrying the Daunrin data packets that are encrypted. In step 1111, S1AP: to send a DL NAS Transport message to RAN2. In step 1112, RAN2 is, RRC: a DL Information Transfer messages transmitted in SRB 1 to UE1. The DL Information Transfer message includes downlink NAS message carrying the Daunrin data packets encrypted UE1 addressed.
[0118]
　Next Figure 12 will be described. Step 1201 of FIG. 12 is the same as step 1101 of FIG. 11. However, in the example of FIG. 12, UE1 selects the second communication architecture types for data packet transmission UE1.
[0119]
　Step 1202-1206 are the same as steps 1102-1106 of Figure 11. However, since in the example of FIG. 12 is used the second communication architecture type, initial NAS message sent by the UE1 at step 1205, a service request (Service Request) message.
[0120]
　In step 1206, RAN2 is, S1AP RRC Connection Setup Complete initial NAS message retrieved from the message (ie, Service Request message) to the CN3 (eg, MME, C-SGN): transmitted using Initial UE message. Initial NAS message (ie, Service Request message), S1AP: embedded in Initial UE message of NAS-PDU IE (information element). RAN2 is explicitly or implicitly indicating the information element and the second communication architecture types that are determined by the UE1 S1AP: Initial may be included in the UE message. RAN2 is a DCN corresponding to the second communication architecture types that are determined by the UE1 selected from within CN3, S1AP: Initial UE message may be sent to the selected DCN the.
[0121]
　Step 1207-1211 is similar to the procedure established EPS bearer in existing service request procedure. In step 1212 and 1213, UE1 sends uplink data on an uplink bearer via S-GW6 and RAN2, receives Dan link data over the S-GW6 and RAN2 on the downlink bearer .
[0122]
　In step 1214, UE1, RAN2, and CN3 performs suspend the RRC connection (suspension). UE1 transitions from RRC-Connected to RRC-Idle mode (or other dormant mode), the information about the RRC connection in RRC-Idle mode (or other dormant mode), eg, Access Stratum Security Context, bearer related information ( incl. to RoHC state information) and L2 / 1 parameters when holding the applicable (retain). Similarly, RAN2 also holds information about the UE1 of the RRC connection, eg, Access Stratum Security Context, the bearer related information (incl. RoHC state information) and L2 / 1 parameters when applicable. Furthermore, RAN2 and CN3 holds S1AP UE Contexts. Furthermore, RAN2 holds S1-U tunnel addresses. Thus, UE1, RAN2, and CN3 may be reused for earlier in the RRC connection setup (previous previous) after the information from the RRC connection (Subsequent).
[0123]
　Although Figures 11 and 12 show a Mobile Originated (MO) data transmission, the same procedure as in FIGS. 11 and 12, may be applied to Mobile Terminated (MT) data transmission.
[0124]
　Procedure of Figure 12 may be modified as follows. In some implementations, S1AP step 1206: Initial UE message may indicate downlink tunnel end point identifier to be used in the second communication architecture type. Downlink tunnel end point identifier identifies a RAN2 side tunnel endpoint bearer between RAN2 and CN3 used for transmission UE1 of data packets in the second communication architecture type. The downlink tunnel end point identifier may be S1 S1 eNB TEID bearer (GTP tunnel) (S1 TEID (DL)). Furthermore, S1AP step 1206: Initial UE message, RAN2 address used for UE1 data packets transmitted in the second communication architecture type (eg, eNB address) may indicate. Accordingly, required in the conventional EPS bearer establishment procedure can omit transmission of the Modify Bearer Response message Modify Bearer Request message from the MME to the S-GW, and the S-GW to the MME. Additionally or alternatively, you can omit transmission from the necessary eNB of Initial Context Setup Response message to the MME in normal EPS bearer establishment procedure. In CIoT, RAN2 and CN3 are capable of enabling communication with multiple CIoT devices are required. By eliminating the transmission of these signaling messages, it can contribute to a reduction in the load of RAN2 and CN3 for CIoT.
[0125]
　According to the example of FIGS. 11 and 12, UE1 includes establishment cause indicating communication architecture type was determined, the determined communications architecture types used for transmission of UE1 data packet (establishment cause) to send the RRC Connection Request message to RAN2. Therefore, the example of FIG. 11 and FIG. 12 can provide the same advantages as the example of FIG. Moreover, the example of FIG. 11 and 12, during the RRC connection setup procedure for after Attach Complete UE1 is to transition to the transmit data packet from the RRC-Idle mode (or other dormant mode) RRC-Connected mode in, it can allow determining the communications architecture types UE1 are used for transmission of UE1 data packets.
[0126]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. In the present embodiment, other communication procedures involving the determination of communication architecture used for UE1 (or selection) is described. 13 and FIG. 14 is a sequence diagram showing an example of a communication procedure according to the present embodiment. In the procedure of FIG. 13 and FIG. 14, during the RRC connection setup procedure for after Attach Complete UE1 is to transition to the transmit data packet from the RRC-Idle mode (or other dormant mode) RRC-Connected mode, UE1 determines the communication architecture types used for data packet transmission UE1. Figure 13 shows a case where the first communication architecture type is used for UE1. On the other hand, FIG. 14 shows a case where the second communication architecture type is used for UE1. The procedure of FIG. 13 and FIG. 14, the point to be sent in RAN2 is different from the procedure of FIG. 11 and FIG. 12 using communication architecture types that are determined by the UE1 is the RRC Connection Setup Complete message.
[0127]
　Figure 13 will be described. Step 1301-1312 are the same as steps 1101-1112 of Figure 11. However, in the procedure of FIG. 13, similarly to the procedure of FIG 4, UE1 is first explicitly or implicitly indicate UE assistance IE (information element) communication architecture type of RRC Connection Setup determined by UE1 transmitted to RAN2 with Complete message (step 1305).
[0128]
　Next Figure 14 will be described. Step 1401 to 1414 are similar to steps 1201-1214 in FIG. 12. However, in the procedure of FIG. 14, similarly to the procedure of FIG 4, UE1 is explicitly or implicitly indicate UE assistance IE (information element) of the RRC Connection Setup a second communication architecture types that are determined by the UE1 transmitted to RAN2 with Complete message (step 1405).
[0129]
　Although Figures 13 and 14 show a Mobile Originated (MO) data transmission, the same procedure as in FIGS. 13 and 14, may be applied to Mobile Terminated (MT) data transmission.
[0130]
　According to the example of FIGS. 13 and 14, UE1 determines the communication architecture types used for data packet transmission of UE1, RRC Connection Setup including the UE assistance IE indicating the determined communication Architecture Type to send a Complete message to RAN2. Thus, Examples 13 and 14 can provide the same advantages as in the example of FIG. Further examples of FIGS. 13 and 14, during the RRC connection setup procedure for after Attach Complete UE1 is to transition to the transmit data packet from the RRC-Idle mode (or other dormant mode) RRC-Connected mode in, it can allow determining the communications architecture types UE1 are used for transmission of UE1 data packets.
[0131]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. In the present embodiment, other communication procedures involving the determination of communication architecture used for UE1 (or selection) is described. 15 and FIG. 16 is a sequence diagram showing an example of a communication procedure according to the present embodiment. In the procedure of FIG. 15 and FIG. 16, during the RRC connection setup procedure for UE1 after attachment completion of transition from the RRC-Idle mode (or other sleep mode) for transmission data packets to the RRC-Connected mode, RAN2 determines the communication architecture types used for data packet transmission UE1. Figure 15 shows a case where the first communication architecture type is used for UE1. On the other hand, FIG. 16 shows a case where the second communication architecture type is used for UE1. The procedure of FIG. 15 and FIG. 16 is different from RAN2 is that the determination of the communication architecture type is shown in FIGS. 11 and 12 procedures.
[0132]
　Figure 15 will be described. Step 1501 to 1505 are the same as steps 601-605 in FIG. 6. However, the example of FIG. 15 shows a transition from RRC-Idle mode after Attach Complete (or other dormant mode) to RRC-Connected mode. Further, in the example of FIG. 15, in step 1503, RAN2 selects the first communication architecture type for UE1. Thus, initial NAS message sent by the UE1 at step 1505, a NAS message carrying the small data. That, UE1 may piggyback the small data on initial NAS message. Incidentally, RRC Connection Setup message in step 1504, the first communications architecture types that are determined by RAN2 in step 1503 (eg, Applied Architecture Type, Selected Architecture Type) may be explicitly or implicitly indicates.
[0133]
　Here, if the RAN2 indicates explicitly communications architecture type, RAN2 is, AS layer (eg, RRC layer) indicating the communication architecture type information element, or the information elements of NAS layer in RRC Connection Setup message it may be transmitted to the UE1 put. If the NAS information element indicating communication architecture type is transmitted, UE1 of NAS layer, to the information indicating the communication architecture type to be used may be transmitted to UE1 in the AS layer, in accordance with the communication architecture type data transmission may start. On the other hand, indicating implicitly communications architecture types RAN2, RAN2, the notification setting information related to the communication architecture type selected by the inclusion of RRC Connection Setup message, the selected communication architecture type to UE1 it may be.
[0134]
　In step 1506, RAN2 is, RRC Connection Setup Complete initial NAS message retrieved from the message (ie, NAS message carrying the small data) CN3 (eg, MME, C-SGN) on S1AP: Initial with UE message transmission to. Initial NAS message (ie, NAS message carrying the small data), S1AP: embedded in Initial UE message of NAS-PDU IE (information element). RAN2 the communication architecture type determined in step 1503 (eg, Applied Architecture Type, Selected Architecture Type) information element indicating S1AP: Initial may be included in the UE message. RAN2 is a DCN corresponding to the communication architecture type determined in step 1503 to select from within CN3, carry initial NAS message (ie, Attach Request message) S1AP: Initial transmit the DCN to the selected UE Message it may be.
[0135]
　Step 1507 to 1512 are similar to steps 1307-1312 in steps 1107 to 1112, or 13 in FIG. 11.
[0136]
　Next, with reference to FIG. 16 will be described. Step 1601 to 1606 are similar to steps 1501-1505 in FIG. 15. However, in step 1603, RAN2 selects the second communication architecture type for UE1. Thus, initial NAS message sent by the UE1 at step 1605, a service request (Service Request) message. Incidentally, RRC Connection Setup message in step 1604, a second communication architecture types that are determined by RAN2 in step 1603 (eg, Applied Architecture Type, Selected Architecture Type) may be explicitly or implicitly indicates.
[0137]
　Step 1606-1614 are the same as steps 1406 to 1414 in steps 1206 to 1214, or 14 in FIG. 12.
[0138]
　While FIGS. 15 and 16 show a Mobile Originated (MO) data transmission, the same procedure as in FIGS. 15 and 16 may be applied to a Mobile Terminated (MT) data transmission.
[0139]
　Example of FIG. 15 and FIG. 16, during the RRC connection setup procedure for after Attach Complete UE1 is to transition to the transmit data packet from the RRC-Idle mode (or other dormant mode) RRC-Connected mode, RAN2 makes available for determining the communications architecture types used for data packet transmission UE1.
[0140]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. However, CN3 includes a plurality of (individual) core network. RAN2 is configured to determine a communication architecture types used for data packet transmission of UE1, corresponding to the determined communication architecture type (individual) of a plurality of core network CN3 of (individual) Core Network It is configured to select from among. Furthermore, RAN2 is the initial Non-Access Stratum (NAS) message, and is configured to transmit to the selected core network.
[0141]
　Figure 17 is a sequence diagram showing an example of a communication procedure according to the present embodiment. In the example of FIG. 17, CN3, the first (individual) Core Network ((D) CN-1 3A), and a second corresponding to the second communication architecture type that corresponds to the first communication Architecture Type including the (individual) core network ((D) CN-2 3B).
[0142]
　Step 1701 is similar to step 504 of FIG. That, UE1 is the RRC connection setup procedure for initial attach, and transmits the RRC Connection Setup Complete message. RRC Connection Setup Complete message in step 1701, includes explicitly or implicitly indicating the information element of one or more communication architecture type supported by UE1 to (eg, UE Supported Architecture Type). The information element is AS (RRC) information.
[0143]
　In step 1702, as in step 505 of FIG. 5, RAN2 considers one or more communication architecture type supported by UE1, determining the communications architecture types used for UE1. Furthermore, RAN2 selects corresponding to the determined communication architecture type (individual) core network from a plurality of (individual) core network in CN3. That, RAN2 selects CN-1 3A when you select the first communication architecture type for UE1, to CN-1 3A S1AP: Initial transmits a UE message (step 1703). RAN2 selects CN-2 3B in case of selecting the second communication architecture type for UE1, and transmits the Initial UE message to the CN-2 3B (step 1704). The Initial UE message, the communication architecture type selected by RAN2 (eg, Applied Architecture Type, Selected Architecture Type) may indicate.
[0144]
　Step from 1705 to 1708 are the same as steps 507-510 in FIG. Attach Accept message in step 1706, the downlink NAS message RRC Connection Release message of step 1707, or from other CN3 (ie, CN-1 3A or CN-2 3B) to the UE1, the communication used for the UE1 the architecture type may explicitly or implicitly shown.
[0145]
　Incidentally, if the UE1 after completing the Attach according to the procedure shown in FIG. 17 performs data transmission, UE1 uses the Registered MME IE of RRC Connection Setup Complete message (information element), UE1 is registered (individual) information CN, i.e. MME or information C-SGN, may indicate. RAN2, for the selection of the communication architecture type of application and (individual) CN choice for UE1, may refer to Registered MME IE of RRC Connection Setup Complete message. That, RAN2, when Registered MME IE indicates the NAS node CN-1 3A (MME / C-SGN), selects the first communication architecture type and CN-1 3A for UE1, Registered MME If the IE indicates the NAS node CN-2 3B (MME / C-SGN), the second communication architecture type and CN-2 3B may be selected for UE1. In addition to the Registered MME IE, or alternatively, Registered C-SGN IE, Registered DCN IE, or UE the Usage Type may be used.
[0146]
　According to the example of FIG. 17, RAN2 is configured to determine a communication architecture types used for UE1, Initial UE message selects (individual) core network to be transmitted. Therefore, RAN2 can according dynamic determination in RAN2 communication architecture types used for UE1, selecting the appropriate (individual) core network.
[0147]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. However, CN3 includes a plurality of (individual) core network. RAN2 is configured to determine a communication architecture type used for transmission of UE1 data packets. CN3, as appropriate (individual) to the core network Initial UE message corresponding to the communication architecture types that are determined by RAN2 is transmitted, and is configured to perform rerouting (redirection) of the Initial UE Message.
[0148]
　Figure 18 is a sequence diagram showing an example of a communication procedure according to the present embodiment. In the example of FIG. 18, CN3, the first (individual) Core Network ((D) CN-1 3A), and a second corresponding to the second communication architecture type that corresponds to the first communication Architecture Type including the (individual) core network ((D) CN-2 3B).
[0149]
　Step 1801 and 1805 are similar to steps 504 and 505 in FIG. RAN2 receives encompassing RRC Connection Setup Complete message from the UE1 initials NAS message. Then, RAN2 considers one or more communication architecture type supported by UE1, determining the communications architecture types used for UE1.
[0150]
　In step 1803, RAN2 is, S1AP the predesignated or arbitrarily selected (individual) core network: sending a Initial UE message. The Initial UE message includes explicitly or implicitly indicating the information element communication architecture types used for UE1 (eg, Applied Architecture Type, Selected Architecture Type) a. In the example of FIG. 18, RAN2 sends the Initial UE message (individual) Core Network CN-2 3B. Incidentally, pre-specified (individual) core network, for example, may be one that supports default communication architecture type.
[0151]
　In step 1804, CN3 (here, CN-2 3B) NAS node in (MME / C-SGN) receives the Initial UE message received from RAN2, the information element indicating the communication architecture type of the message (eg, Applied Architecture Type, Selected Architecture Type) to refer to. If the communication architecture types used for UE1 is associated with CN-2 3B, NAS node in CN-2 3B is attachment processing on the basis of the Attach Request message that is included in the Initial UE Message It is continued. In contrast, (here, CN-1 3A) communications architecture type is other (individual) core network which is used for UE1 when associated with the, NAS node in CN-2 3B is , requests the RAN2 to reroute the Initial UE message to the CN-1 3A. Specifically, as shown in Figure 18, CN-2 3B are, S1AP: it sends a Reroute NAS Message Request message to RAN2. The Reroute NAS Message Request message includes an Initial UE should message is sent (individual) core network identifier (eg, MME Group ID, C-SGN Group ID, DCN Group ID and Additional Global Unique Temporary Identity (GUTI)) .
[0152]
　In step 1804, Initial in determining the reroute UE message, CN3 is, UE1 subscriber data acquired from HSS5 (subscription data), for example UE Capability, or UE Usage Type (eg, C-IoT, general MTC, delay tolerant MTC) may be further consideration of the.
[0153]
　In step 1805, RAN2 is, S1AP: Reroute in response to NAS Message Request message has been received, the Reroute specified in the NAS Message Request message (individual) core network (here, CN-1 3A) toward the to reroute the Initial UE message Te.
[0154]
　Step 1806-1809 are the same as steps 1705-1708 of Figure 17. Step 1807 of Attach Accept message, the downlink NAS message RRC Connection Release message of step 1808, or from other CN3 (ie, CN-1 3A or CN-2 3B) to the UE1, the communication used for the UE1 the architecture type may explicitly or implicitly shown.
[0155]
　If UE1 after completing the Attach according to the procedure shown in FIG. 18 performs data transmission, UE1 uses the Registered MME IE of RRC Connection Setup Complete message (information element), UE1 is registered (individual ) information of CN, i.e. MME or information C-SGN, may indicate. RAN2, for the selection of the communication architecture type of application and (individual) CN choice for UE1, may refer to Registered MME IE of RRC Connection Setup Complete message. That, RAN2, when Registered MME IE indicates the NAS node CN-1 3A (MME / C-SGN), selects the first communication architecture type and CN-1 3A for UE1, Registered MME If the IE indicates the NAS node CN-2 3B (MME / C-SGN), the second communication architecture type and CN-2 3B may be selected for UE1.
[0156]
　According to the example of FIG. 18, CN3 recognizes the communication architecture types that are determined by RAN2, reroute Initial UE message in response to the communications architecture types that are determined by RAN2. Therefore, CN3 may, depending on the dynamic determination in RAN2 communication architecture types used for UE1, processes the Initial UE message in the appropriate (individual) core network.
[0157]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. However, CN3 includes a plurality of (individual) core network. CN3 is configured to determine a communication architecture types used for data packet transmission of UE1, appropriate (individual) core network Initial UE message corresponding to the communication architecture types that are determined by CN3 is transmitted as it is configured to perform rerouting (redirection) of the Initial UE message.
[0158]
　Figure 19 is a sequence diagram showing an example of a communication procedure according to the present embodiment. In the example of FIG. 19, CN3, the first (individual) Core Network ((D) CN-1 3A), and a second corresponding to the second communication architecture type that corresponds to the first communication Architecture Type including the (individual) core network ((D) CN-2 3B). The procedure of FIG. 19 is different from the procedures that CN3 makes decisions communication architecture types used for UE1 is shown in Figure 18.
[0159]
　Step 1901 and 1902 are similar to steps 904 of FIG. That is, in step 1901, UE1 is the initial NAS message (ie, Attach Request message) and individual NAS information including the one or more communication architecture type supported by the UE1 (UE Supported Architecture Type) (Dedicated to send the RRC Connection Setup Complete message carrying the NAS Information) to RAN2. In step 1902, RAN2 retrieves individual NAS information from RRC Connection Setup Complete message. Then, RAN2 is, S1AP carry NAS-PDU includes an individual NAS information retrieved: Initial The UE message to the pre-selected for the specified or any (separate) core network. In the example of FIG. 19, RAN2 sends the Initial UE message (individual) Core Network CN-2 3B.
[0160]
　Step 1903 is similar to step 905 of FIG. That, CN3 (here, CN-2 3B) NAS node in (MME / C-SGN) takes into account one or more communication architecture type supported by the UE1 (UE Supported Architecture Type), UE1 determining the communications architecture types used for. NAS node in CN-2 3B, in the determination of the communication architecture type, UE1 subscriber data acquired from HSS 5 (subscription data), for example UE Capability, or even consider the UE the Usage Type.
[0161]
　Step 1904 to 1909 are similar to steps 1804-1809 in FIG. 18. However, S1AP step 1904: Reroute NAS Message Request message, determined by CN-2 3B (selected) has been explicitly or implicitly indicating the information element communication architecture types used for UE1 (eg, Applied Architecture Type, Selected Architecture Type) may contain. Thus, RAN2 can recognize the communication architecture types used for UE1.
[0162]
　According to the example of FIG. 19, CN3 is configured to determine a communication architecture type for UE1, reroute Initial UE message in response to the communications architecture types that are the determined. Therefore, CN3 may, depending on the dynamic determination at CN3 communication architecture types used for UE1, processes the Initial UE message in the appropriate (individual) core network.
[0163]

　a method for transmitting an explicit or implicitly indicate information element communication architecture type from UE1 to RAN2, the method described in the above embodiments, i.e. RRC message (eg, RRC Connection Request, not limited to the method using the RRC Connection Setup Complete).
[0164]
　For example, UE1 is transmitted, RRC than the lower layer (ie, RLC, MAC) RLC header of using the MAC header or MAC Control Element (MAC CE), the information element indicating the communication architecture type (UE Assistance IE) it may be. Additionally or alternatively, UE1 is, RLC header, using the MAC header or MAC CE, PDCP processing (eg, AS security process) may transmit information indicating the omission of the RAN2. More specifically, if the first communication architecture type involves the omission of PDCP processing, UE1, at least one of the MAC information element indicating omission of information elements and PDCP processing showing a first communication Architecture Type it may be transmitted in the CE.
[0165]
　For example, in step 401 of FIG. 4 when the UE1 is determined first communication architecture type (selection), UE1, when sending a RRC Connection Setup Complete message (step 405), PDCP processing for SRB 1 It might be omitted. Therefore, UE1 uses the MAC CE, and transmits at least one information element indicating omission of information elements and PDCP processing showing a first communication architecture type. By using the MAC CE, RAN2 with respect messages received from UE1 (including RRC Connection Setup Complete), to recognize that the PDCP processing of the message is omitted at the time of the MAC processing prior PDCP processor it can.
[0166]
<16th Embodiment>
　In the above embodiments, the random access procedure due to the time of UE1 transitions from RRC-Idle mode (or other dormant mode) RRC-Connected mode, the transmission of the random access preamble Although an example has been shown to be performed, not limited to this. Other random access procedures may be implemented to UE1 and RAN2. In some implementations, UE 11, instead of the random access preamble (RACH preamble), the smaller (shorter) messages may be sent in RACH. In this case, the message sent on the RACH may indicate a communication architecture types that are to have been or support determined (selected) by the UE1. Thus, UE1 may notify the RAN2 communication architecture types that are also supported determined (selected) by the UE1 before setting RRC connection. For example, RAN2, taking into account the communication architecture type notified from the UE1, can generate an RA response message. For example, RA response message may include a backoff indicator according to a communication architecture type notified from the UE1.
[0167]

　RACH resources used in UE1 transitions from RRC-Idle mode (or other dormant mode) RRC-Connected mode, be assigned individually to a plurality of communication architecture type good. In this case, UE1 includes a preamble or small (short) by either RACH resources for the initial RACH transmission including a message is used, determined by the UE1 (selected) have been or supported communication architecture type it may be implicitly shows. Thus, UE1 may notify the RAN2 communication architecture types that are also supported determined (selected) by the UE1 before setting RRC connection. For example, RAN2, taking into account the communication architecture type notified from the UE1, can generate an RA response message. For example, RA response message may include a backoff indicator according to a communication architecture type notified from the UE1.
[0168]

　The above-described embodiments, the communication of NB-IoT, communications LTE emtc, or may be applied to both. Furthermore, the above-described embodiments, LTE, may be applied to the communication of other UE according to LTE-Advanced and these improvements.
[0169]
　Configuration example of a wireless communication network according to the present embodiment is the same as FIG. Incidentally, UE1 according to the present embodiment, CIoT device (eg, NB-IoT, LTE eMTC) may be a, LTE, LTE-Advanced and may be another UE according to these improvements. In the present embodiment, an example of mobility if any of the plurality of communication architecture type described above is applied to the UE1 is described.
[0170]
　UE1 of mobility, idle mode (eg, RRC-Idle, other dormant mode) cell change in (idle mode mobility) and Connected mode (eg, RRC-Connected) cell change in a (Connected mode mobility) including. Idle mode mobility, including a cell re-selection procedure in the idle mode. Connected mode mobility, including a backward handover procedure and forward handover procedure in the Connected mode (eg, RRC release with redirection (RRC release with redirection).
[0171]
　Wireless communication network according to the present embodiment, for one or more of the plurality of communication architecture type including first and second communication architecture type, UE1 mobility any of these communication architecture type is applied it may or may not support. Here, "it does not support mobility" and, when after a cell change in the idle mode or Connected mode of the applied communication architecture type of determined or selected to UE1, was applied prior cell change to UE1 It means that the communication architecture type and its configuration is not considered.
[0172]
　In some implementations, RAN2 may in the first (or second) Mobility RRC-Connected mode for UE1 to apply communication architecture type (handover, redirection) functions disabled (disabled). In other words, UE1, the functions of the RRC-Connected mode mobility (eg, measurement report, handover, redirection) may be disabled (deactivated-) a. Additionally or alternatively, RAN2, for example, even if the function of the second (or first) mobility of RRC-Idle mode for UE1 to apply communication architecture type (cell reselection) disabled (disabled) good. In other words, UE1, the functions of the RRC-Idle mode mobility (eg, cell reselection, measurement) may be disabled (deactivated-) a.
[0173]
　In some implementations, UE1 applying the communication architecture type of the first (or second) can be RRC-Idle mode functions and RRC-Connected mode enable features of mobility Mobility (activated) good. In this case, UE1 may operate as follows upon cell change in RRC-Idle or RRC-Connected mode.
[0174]
　For example, UE1 in response to the execution of the cell reselection may be set to UE1 in reselection previous cell (The assigned) releases the communication architecture type of information (discarded).
[0175]
　For example, UE1, during the handover procedure in RRC-Connected mode (backward handover), the source RAN node in RAN2 (eg, the source eNB, the source CIoT BS) in response to receiving a handover instruction from may release the information about the set to UE1 (applied are) communication architecture type (discarded). Handover instruction may be, for example, a RRC Connection Reconfiguration message including mobilityControlInfo IE.
[0176]
　For example, UE1, during the RRC release with redirection procedure in RRC-Connected mode, the source RAN node in RAN2 the RRC Connection Release message requesting the redirection (eg, the source eNB, the source CIoT BS) that is received from the in response, it may be set to UE1 release information about (applied are) communication architecture type (discarded). Alternatively, UE1 is released in response to execution of the cell reselection according RRC Connection Release message requesting redirection is set to UE1 in reselection before cell (applied) communication architecture type of information (discarded) may be. Here, Release the Cause is used in RRC Connection Release message, may be the "other", a new cause (eg, redirectionForCIoT, redirectionForCellUpdate, redirectionRequired, cellUpdateRequired) is defined, may also be use.
[0177]
　After UE1 in the cell change, UE1, RAN2, and CN3 is obtained according to the process described in any of the above embodiments may determine a communication architecture types used for UE1 (selection). Alternatively, UE1, after the cell change may be performed data transmission in the existing LTE and LTE-Advanced (fall back to legacy / conventional mechanism).
[0178]
　As described above, in this embodiment, when the UE1 cell changes in the idle mode (sleep mode) or Connected mode, UE1 releases the cell before the change of the communication architecture type setting (discarded). Therefore, it is possible to prevent the communication architecture type setting mismatch with the network after the change UE1 and the cell (mismatch) arises.
[0179]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. UE1 according to the present embodiment, CIoT device (eg, NB-IoT, LTE eMTC) may be a, LTE, LTE-Advanced and may be another UE according to these improvements. In the present embodiment, an example of an idle mode mobility if any of the plurality of communication architecture type described above is applied to the UE1 is described.
[0180]
　UE1 according to the present embodiment, when performing cell reselection, the explicitly or implicitly indicate information elements that have been set (applied) communication architecture type before cell reselection UE1 RAN2 or sent to the CN3. Specifically, UE1, when first becomes RRC-Connected mode after cell reselection may transmit the information element.
[0181]
　20 and FIG. 21 is a sequence diagram showing an example of a communication procedure according to the present embodiment. Figure 20 shows a case where the first communication architecture type is used for UE1. On the other hand, FIG. 21 shows a case where the second communication architecture type is used for UE1. In the example of FIGS. 20 and 21, RAN2 includes a RAN-1 2A and RAN2 2B. RAN-1 2A corresponds to the previous RAN node cell change (cell reselection) (eg, CIoT BS, eNB), RAN-2 2B corresponds to the RAN node after cell change.
[0182]
　It will be described FIG. 20. In step 2001, in accordance with any of the procedures described in Embodiments 1 through 17, UE1 is set according to the communication architecture type is determined, the determined communications architecture types used for UE1 It is. In the example of FIG. 20, UE1 uses the first communication architecture type. In step 2002, RAN-1 2A transmits RRC connection release (RRC Connection Release) message to the UE1 on SRB 1. In step 2003, UE1 may store a communication architecture types that are set to UE1 and (storage), a transition to RRC-Idle mode (or other sleep mode). In the example of FIG. 20, UE1 uses the first communication architecture type.
[0183]
　UE1 measures the serving cell and the peripheral cell in a RRC-Idle mode (or other sleep mode). In step 2004, UE1 performs cell reselection. In step 2005 and 2006, UE1 and RAN-2 2B performs an RRC connection establishment procedure for UE1 first becomes RRC-Connected mode after cell reselection. During the procedure, UE1 is set from the previous cell reselection UE1 the (applied are) explicit communication architecture type or implicitly indicated by the information element (eg, Configured arc-type information) It sends to RAN-2 2B. The information element, for example, may be transmitted using the RRC Connection Request message, it may be transmitted using an RRC Connection Setup Complete message. In the example of FIG. 20, the information element indicates a first communications architecture type. Thus, RAN2 2B is set from the previous cell reselection UE1 (are applied) can know the communication architecture type, RAN2 is in communication architecture types that are set to UE1 depending processing can be performed.
[0184]
　In step 2007, UE1 performs UL data transmission or DL ​​data reception or both using NAS messages. Similar to the embodiment of the ninth to 10, UE1 is, RRC Setup Complete message or RRC: using UL Information Transfer message on SRB 1, it may send a NAS message including the UL data. UE1 is, RRC: on SRB 1 using DL Information Transfer message may receive a NAS message including the DL data.
[0185]
　Procedure of Figure 20 may be modified as follows. For example, RAN-2 2B communicates with CN3, it may be carried out UE1 authentication or authorization.
[0186]
　UE1 can be transmitted is set from the previous cell reselection UE1 (The assigned) information element indicating communication architecture type (eg, Configured arc-type information), and the CN3 using NAS messages good. In this case, CN3 may transmit an information element indicating that have been set (applied) communications architecture type to UE1 in RAN-2 2B.
[0187]
　UE1, instead of the information element indicating the set (applied) are communication architecture type to UE1, and the information element indicating the resumption of communication architecture types that are set (resume), reselection before information element indicating cell or RAN node may send (eg, Physical cell ID (PCI), Carrier frequency (EARFCN), E-UTRAN cell Global ID (ECGI)) to RAN-2 2B. In this case, RAN-2 2B is set to UE1 the (applied) communication architecture type, may contact the RAN node managing reselection previous cell.
[0188]
　UE1 is an information element indicating resume (resume) the communication architecture types that are set may be transmitted to the CN3. In this case, CN3 may transmit an information element indicating that have been set (applied) communications architecture type to UE1 in RAN-2 2B.
[0189]
　Next, description will be made to FIG. 21. In step 2101, in accordance with any of the procedures described in Embodiments 1 through 17, UE1 is set according to the communication architecture type is determined, the determined communications architecture types used for UE1 It is. In the example of FIG. 21, UE1 uses the second communication architecture type. In step 2102, RAN-1 2A transmits suspend the RRC Connection (suspension) RRC message for (RRC Connection Suspend message) to the UE1. In response to reception of the RRC message, UE1 transitions from RRC-Connected to RRC-Idle mode (or other dormant mode), holds information about the RRC connection in RRC-Idle mode (or other dormant mode) (step 2103). Similarly, RAN-1 2A and CN3 holding the context for the UE1 required for temporary cessation of RRC connection (suspension) (step 2103). Furthermore, UE1 and RAN-1 2A, the communication architecture type that is set to UE1 (here, the second communication architecture type) stores (step 2104).
[0190]
　Step 2105 and 2106 are similar to steps 2004 and 2005 in FIG. 20. However, the RRC message transmitted in step 2106 is set to UE1 (applied are) explicit communication architecture type or implicitly indicated by the information element (eg, Configured arc-type information) is first It shows a second communication architecture type. Further, RRC message transmitted in step 2106, includes an information element indicating reselection previous cell or RAN node (eg, PCI, ECGI).
[0191]
　In step 2107, in response to receiving the RRC message in step 2106, RAN-2 2B requests the UE context to the cell reselection previous RAN-1 2A. In step 2098, RAN-1 2A sends a UE context held in RAN-1 2A in RAN-2 2B. In step 2109, RAN-2 2B, in order to resume the RRC connection has been suspended, to communicate with CN3. Specifically, RAN-2 2B is, S1-AP: The UE Context Active message sent to CN3, S1-AP: The UE Context Active Ack messages may be received from CN3. S1-AP: UE Context Active message causes a configuration change of a S1 bearer within CN3 (modification) procedure. The procedure includes, for example, transmitted from the MME (or C-SSN) of Modify Bearer Request message to the S-GW, and the transmission of the Modify Bearer Response message from the S-GW to the MME (or C-SSN).
[0192]
　In step 2110, RAN-2 2B transmits RRC message indicating the completion of the resumption of the RRC connection (resumption) of (RRC Connection Resume Complete message) to the UE1. The RRC message includes an AS security information. In step 2111, UE1 and RAN-2 2B establishes the AS security. In step 2112, UE1 transmits UL data via the RAN-2 2B on UL bearer, to receive the DL data over the RAN-2 2B on the DL bearer.
[0193]
　As described above, in the present embodiment, UE1 is the cell when performing reselection, cell are set reselection before the UE1 (applied are) information element indicating communication architecture type (eg, the Configured arc-type information), and transmits to the RAN-2 2B or CN3. Therefore, it is possible to prevent the communication architecture type setting mismatch with the network after the change UE1 and the cell (mismatch) arises.
[0194]
<20th Embodiment>
　configuration example of a wireless communication network according to the present embodiment is the same as FIG. UE1 according to the present embodiment, CIoT device (eg, NB-IoT, LTE eMTC) may be a, LTE, LTE-Advanced and may be another UE according to these improvements. In the present embodiment, an example of a Connected mode mobility when any of the plurality of communication architecture type described above is applied to the UE1 is described.
[0195]
　In the present embodiment, when the UE1 handover, the source RAN node (eg, CIoT BS, eNB) is (are used for UE1) which is set to UE1 explicitly or implicitly communications architecture type sending a manner handover request including an information element indicating (handover request) target RAN node (eg, CIoT BS, eNB) to.
[0196]
　22 and FIG. 23 is a sequence diagram showing an example of a communication procedure according to the present embodiment. Figure 22 shows a case where the first communication architecture type is used for UE1. On the other hand, FIG. 23 shows a case where the second communication architecture type is used for UE1. In the example of FIGS. 22 and 23, RAN2 includes a RAN-1 2A and RAN2 2B. RAN-1 2A corresponds to the source RAN node (eg, CIoT BS, eNB), RAN-2 2B corresponds to the target RAN node.
[0197]
　It will be described FIG. 22. In step 2201, in accordance with any of the procedures described in Embodiments 1 through 17, UE1 is set according to the communication architecture type is determined, the determined communications architecture types used for UE1 It is. In the example of FIG. 20, UE1 uses the first communication architecture type. In step 2202, UE1 is RRC-Connected mode. Accordingly, in step 2202, UE1 may perform UL data transmission or DL ​​data reception or both using NAS messages.
[0198]
　In step 2203, UE1 transmits a measurement report indicating the measurement result of the serving cell and the peripheral cell to the source RAN-1 2A. In step 2004, the source RAN-1 2A determines the UE1 of handover to the target RAN-2 2B. In step 2005, the source RAN-1 2A transmits a handover request to the target RAN-2 2B. The handover request includes the source RAN-1 communications architecture types that are used for the UE1 in 2A (here the first communication architecture type) information element indicating (eg, arc-type information).
[0199]
　In step 2206, in response to receiving the handover request, the target RAN-2 2B transmits a response to the handover request message (eg, Handover Request Acknowledge message) to the source RAN-1 2A. In some implementations, the response message indicates whether the target RAN-2 2B can correspond to the communications architecture type notified from the source RAN-1 2A. Alternatively, the response message, explicitly or implicitly indicating the (modified) communication architecture types used for UE1 in the target RAN-2 2B.
[0200]
　In step 2207, the source RAN-1 2A show that even after the handover is the current communication architecture type is continued, or applied after the handover to the UE1 (changed) information element indicating communication architecture type ( eg, transmits arc-type information) a handover instruction including the to UE1. Handover instruction may be, for example, a RRC Connection Reconfiguration message including mobilityControlInfo IE. In the example of FIG. 22, the first communication architecture type is also used for the UE1 in the target RAN-2 2B.
[0201]
　In step 2208, UE1 performs a random access procedure for synchronization to the target cell (target RAN-2 2B). In step 2209, UE1 sends confirmation handover the RRC Connection Reconfiguration Complete message containing the (Handover Confirm The) the target RAN-2 2B. In step 2210, UE1 according communication architecture types that are instructed from the source RAN-1 2A in step 2207, performs UL transmission or DL ​​transmission, or both. In the example of FIG. 22, the first communication architecture type is also used for the UE1 in the target RAN-2 2B. Accordingly, in step 2210, UE1 may perform UL data transmission or DL ​​data reception or both using NAS messages.
[0202]
　Procedure of Figure 22 may be modified as follows. In step 2205, the handover request, the use of the first communications architecture type may indicate that it is authorized to UE1 (authorized).
[0203]
　Next, description will be made to FIG. 23. In step 2301, in accordance with any of the procedures described in Embodiments 1 through 17, UE1 is set according to the communication architecture type is determined, the determined communications architecture types used for UE1 It is. In the example of FIG. 23, UE1 uses the second communication architecture type. In step 2302, bearer establishment procedure for the UE1 is executed. In step 2303, UE1 transmits UL data via the RAN-1 2A on UL bearer, to receive the DL data over the RAN-1 2A on the DL bearer.
[0204]
　Step 2304-2310 are the same as steps 2203-2209 of Figure 22. However, in the example of FIG. 23, the target RAN-2 2B uses a second communication architecture type for UE1. In step 2311, the target RAN-2 2B, like the normal handover procedure, to communicate with CN3 to change the path of the S1 bearer for UE1. For example, the target RAN-2 2B is, S1AP: a Path Switch Request message and sends it to the CN3, S1AP: receiving a Path Switch Request Ack message from CN3.
[0205]
　In step 2312, UE1 transmits UL data via the target RAN-2 2B on UL bearer, to receive the DL data over the target RAN-2 2B on the DL bearer.
[0206]
　In step 2313, UE1, the target RAN-2 2B, and CN3 performs suspend the RRC connection (suspension).
[0207]
　Procedure steps and 23 of Figure 22 may be combined as appropriate. That is, as already described, the target RAN-2 2B may be applied to UE1 different communication architectures type as was applied to UE1 in the source RAN-1 2A. Thus, in FIG. 22, the handover response message (step 2206) is to indicate that the second communication architecture type is used for UE1 in the target RAN-2 2B, step 2311 of FIG. 23 in place of steps 2210 ~ 2313 may be performed. In the case of the contrary it is the same.
[0208]
　As described above, in the present embodiment, the source RAN-1 2A is a handover request including an information element indicating the communication architecture type (with and used for UE1) set in the UE1 of (Handover Request) sent to the target RAN-2 2B. Therefore, it is possible to prevent the communication architecture type setting mismatch between the UE1 and the target RAN-2 2B (mismatch) arises.
[0209]
　Further, in the present embodiment, the target RAN-2 2B is an information element indicating whether the source RAN-1 2A from the notified communication architecture type to the target RAN-2 2B can handle or the target RAN-2 2B, Send a handover response message including an information element indicating the (changed) communications architecture types used for UE1 in the source RAN-1 2A in. In addition, the source RAN-1 2A transmits a handover instruction including an information element indicating communication architecture types used for UE1 in the target RAN-2 2B to UE1. Therefore, the communication architecture type different from that of the source RAN-1 2A in the target RAN-2 2B can be used for the UE1.
[0210]

　configuration example of a wireless communication network according to the present embodiment is the same as FIG. UE1 according to the present embodiment, CIoT device (eg, NB-IoT, LTE eMTC) may be a, LTE, LTE-Advanced and may be another UE according to these improvements. In the present embodiment, an example of a Connected mode mobility when any of the plurality of communication architecture type described above is applied to the UE1 is described.
[0211]
　In the present embodiment, when the forward handover procedure in Connected mode, UE1 indicates explicitly or implicitly (the applied are) communication architecture types that are set to UE1 in the source RAN-1 2A It sends the information element to the target RAN-2 2B. Specifically, UE1 may transmit the information element using the RRC connection re-establishment message to the target RAN-2 2B (RRC Connection Re-establishment message). Forward handover procedure, an RRC release message with redirection source RAN-1 2A may be initiated by sending the UE1. Alternatively, forward handover procedure, in response to expiration of Radio Link Failure (RLF) timer may be voluntarily disclosed by UE1.
[0212]
　Figure 24 and Figures 25A and 25B are sequence diagrams showing an example of a communication procedure according to the present embodiment. Figure 24 shows a case where the first communication architecture type is used for UE1. On the other hand, FIGS. 25A and 25B show a case in which the second communication architecture type is used for UE1. In the example of FIG. 24 and FIGS. 25A and 25B, RAN2 includes a RAN-1 2A and RAN2 2B. RAN-1 2A corresponds to the source RAN node (eg, CIoT BS, eNB), RAN-2 2B corresponds to the target RAN node.
[0213]
　Figure 24 will be described. Step 2401-2403 are the same as steps 2201 to 2,203 in Fig. 22. In step 2404, the source RAN-1 2A transmits an RRC release message indicating redirection to the target RAN-2 2B to UE1. In this case, in response to reception of the RRC release message, UE1 performs cell reselection (Step 2405). Incidentally, step 2404 may not be performed. Specifically, UE1 may perform spontaneously cell according to the expiration of the RLF timer (re) selection (step 2405).
[0214]
　In step 2406, UE1 sends the RRC connection reestablishment request message to the target RAN-2 2B. The RRC connection reestablishment request message, the source RAN-1 explicitly or implicitly indicate a have been set (applied) communications architecture type to UE1 in 2A, information elements (eg regarding the communication architecture type , including the Configured arc-type information).
[0215]
　In step 2407, the target RAN-2 2B transmits RRC connection reestablishment message (RRC Connection Re-establishment message) to the UE1. The message indicates that the current communication architecture type is continued, or applied to UE1 in the target RAN-2 2B (changed) shows explicitly or implicitly communications architecture type, the communication information element architectural type (eg, arc-type information) may contain.
[0216]
　In the example of FIG. 24, the target RAN-2 2B uses a first communications architecture types for the UE1. Thus, step 2408 is similar to step 2210 of FIG. 22.
[0217]
　Next, description will be 25A and 25B. Step 2501-2504 are the same as steps 2301 to 2304 in FIG. 23.
[0218]
　Step 2505-2508 are the same as steps 2404-2407 of Figure 24. In the example of FIGS. 25A and 25B, the target RAN-2 2B uses a second communication architecture type for UE1. Accordingly, steps 2509-2514 are the same as steps 2107-2112 of Figure 21.
[0219]
　Step 2515 is similar to step 2313 of FIG. 23.
[0220]
　Procedure of Figure 25A and 25B may be modified as follows. RRC connection release message of step 2505 may indicate a Resume ID. Resume ID is an identifier RAN2 assigns to UE1 for RRC suspension. RAN2 uses Resume ID to associate the UE context and UE1 previously stored. In some implementations, the source RAN-1 2A will determine the Resume ID, which may be sent to the UE1 and the target RAN-2 2B. Alternatively, the target RAN-2 2B is determined the Resume ID, which may be transmitted to UE1 via the source RAN-1 2A.
[0221]
　As described above, in the present embodiment, UE1 is the case of performing cell reselection regarding forward handover is set to UE1 in the source RAN-1 2A (the application is) Communication Architecture Type information element (eg, Configured arc-type information) indicating the, sent to the target RAN-2 2B. Therefore, it is possible to prevent the communication architecture type setting mismatch between the UE1 and the target RAN-2 2B (mismatch) arises.
[0222]

　3GPP is scheduled to begin in 2016 the standardization work of 5G towards the introduction of 2020 migrated as 3GPP Release 14. 5G is assumed to be implemented in an innovative development of the combination according to the introduction of the continuous development of LTE and LTE-Advanced (enhancement / evolution) and new 5G air interface (new Radio Access Technology (RAT)) ing. New RAT (New 5G RAT), for example, LTE / LTE-Advanced frequency band continuous development is the subject of (eg, 6 GHz or less) frequency band, for example 10 GHz or more super high frequency band and higher than to support the millimeter-wave band of more than 30 GHz.
[0223]
　High frequency band, it is possible to provide a high-rate communication. However, the coverage of the higher frequency band, due to its frequency characteristics, it is more localized. Thus, while the high frequency band is used to improve the capacity and data rate in a particular area, a wide coverage is provided by the existing low frequency band. That is, in order to secure the New 5G stability RAT communication in the higher frequency band, the low frequency band and a high frequency band, i.e. LTE / LTE-Advanced and New 5G RAT, close (tight) integration (integration) or close interworking is required. Wireless terminal supporting 5G (5G User Equipment (UE)) using the Carrier Aggregation (CA) or Dual Connectivity (DC) or techniques improve these, the low frequency band and high frequency band (i.e., LTE / LTE connected to both -Advanced cell and New 5G cell).

claims

[Claim 1]A memory,at least one processor coupled to the memory,
provided with,
　at least one processor is the use of any more of the communication architecture types for data packet transmissions for Cellular Internet of Things (CIoT) or desired, and is configured to transmit one or supports, or radio Resource Control (RRC) connection setup complete message either contains a UE assistance information element indicating whether it is set in the wireless station,
wireless terminal.
[Claim 2]
　Wherein the plurality of communication architecture type includes the data packet is a first communications architecture types that are transmitted through the control plane, and data packets to a second communication architecture types that are transmitted through the user plane,
　wherein the at least one processor, when the second communication architecture type is used for the wireless terminals, an additional Packet Data Convergence Protocol (PDCP) configuration required for the second communication Architecture type the RRC message including being configured to receive from the radio station,
the radio terminal according to claim 1.
[Claim 3]
　A method in a wireless terminal,
　Cellular Internet of Things (CIoT) regarding desires to any use of the plurality of communication architecture types for data packet transmission, one or supported, or any is set the radio Resource Control (RRC) connection setup complete message containing the UE assistance information element indicating whether it is comprises transmitting to the radio station,
the method.
[Claim 4]
　The non-transitory computer readable medium storing a program for causing a method in a wireless terminal to a computer,
　the method comprising a plurality of communication architecture types for data packet transmissions for Cellular Internet of Things (CIoT) you want to any use of any or supported, or any to send a radio Resource Control (RRC) connection setup complete message containing the UE assistance information element indicating whether it is set in the wireless station the equipped, non-transitory computer readable media.
[Claim 5]
　A memory,
　at least one processor coupled to the memory,
provided with,
　at least one processor is
　configured to receive a Radio Resource Control (RRC) connection setup complete message from the wireless terminal,
　Cellular Internet of Things whether the wireless terminal among the plurality of communication architecture types for data packet transmissions for (CIoT) wishes to any use, one or supports, or UE assistance information element indicating which is set the is configured to retrieve from the RRC connection setup complete message,
the wireless station.
[Claim 6]
　Wherein the at least one processor is further based on the UE assistance information element, wherein being configured to determine a communication architecture types used for data packet transmission of the wireless terminal,
according to claim 5 radio stations.
[Claim 7]
　Wherein the at least one processor is further
　configured to select a core network corresponding to the determined communication architecture type from among a plurality of core network,
　has been removed from the RRC Connection Setup Complete message initials Non- It is configured to transmit the Access Stratum (NAS) message to the selected core network,
the radio station according to claim 6.
[8.]
　Wherein the at least one processor, it said has an initial NAS message and the initial UE message including an information element indicating the determined communication architecture type is configured to transmit to the selected core network,
to claim 7 radio station according.
[Claim 9]
　Wherein the plurality of communication architecture type includes the data packet is a first communications architecture types that are transmitted through the control plane, and data packets to a second communication architecture types that are transmitted through the user plane,
　wherein the at least one processor is
　transmitted when the first communication architecture type was determined for the wireless terminal, the initial NAS message to the first core network corresponding to the first communication Architecture type It is configured to,
　when the second communication architecture type was determined for the wireless terminal, to transmit the initial NAS message to the second core network corresponding to the second communication Architecture type is configured,
in claim 7 or 8 serial Of the radio station.
[Claim 10]
　Wherein the plurality of communication architecture type includes the data packet is a first communications architecture types that are transmitted through the control plane, and data packets to a second communication architecture types that are transmitted through the user plane,
　wherein the at least one processor, when the second communication architecture type is used for the wireless terminal, in response to receiving the RRC connection setup complete message, the second communication Architecture type additional Packet Data Convergence Protocol (PDCP) is configured to send the RRC message to the radio terminal including setting, necessary for
radio stations according to any one of claims 5-9.
[Claim 11]
　Wherein the plurality of communication architecture type includes the data packet is a first communications architecture types that are transmitted through the control plane, and data packets to a second communication architecture types that are transmitted through the user plane,
　wherein the at least one processor is
　when said second communication architecture type is used for the wireless terminal, the initial Non-Access Stratum (NAS) messages retrieved from the RRC connection setup complete message configured to generate an encompassing initial UE message and downlink tunnel end point identifier to be used in the second communication architecture type,
　core corresponding to the initial UE message to the second communication Architecture type networks It is configured to transmit the over-click,
radio station according to any one of claims 5-10.
[Claim 12]
　A method in a radio station,
　receiving a Radio Resource Control (RRC) connection setup complete message from the wireless terminal, and
　Cellular Internet of Things (CIoT) among a plurality of communication architecture types for data packet transmissions for wherein either wireless terminal desires to any use, one or supported, or any be extracted UE assistance information element indicating whether it is set from the RRC connection setup complete message,
comprising the method.
[Claim 13]
　The non-transitory computer readable medium storing a program for causing a method in a radio station to a computer,
　the method comprising
　receiving a Radio Resource Control (RRC) connection setup complete message from the wireless terminal, and
　Cellular Internet of Things whether the wireless terminal among the plurality of communication architecture types for data packet transmissions for (CIoT) wishes to any use, indicating either whether the support, or any is set retrieving the UE assistance information element from the RRC connection setup complete message,
comprising a non-transitory computer readable media.
[Claim 14]
　A memory,
　at least one processor coupled to the memory,
provided with,
　at least one processor is
　configured to receive a Radio Resource Control (RRC) connection setup complete message from the wireless terminal,
　Cellular Internet of Things when the second communication architecture types that data packets are transmitted over the user plane of the plurality of communication architecture types for data packet transmissions for (CIoT) is used for the wireless terminal, the generating an initial UE message including the downlink tunnel end point identifier to be used in the initial Non-Access Stratum (NAS) message and the second communication architecture type taken from the RRC connection setup complete message It is configured ,
　Wherein and the initial UE message is configured to transmit to the core network,
the radio station.
[Claim 15]
　A method in a radio station,
　Radio Resource Control (RRC) connection setup complete message be received from the wireless terminal,
　data of the plurality of communication architecture types for data packet transmissions for Cellular Internet of Things (CIoT) when the second communication architecture type packets are transmitted over the user plane is used for the wireless terminal, the initial Non-Access Stratum (NAS) messages retrieved from the RRC connection setup complete message and said second communication architecture type by generating an initial UE message including the downlink tunnel end point identifier to be used, and
　it, to transmit the initial UE message to the core network
comprises a method .
[Claim 16]
　The non-transitory computer readable medium storing a program for causing a method in a radio station to a computer,
　the method comprising
　receiving a Radio Resource Control (RRC) connection setup complete message from the wireless terminal,
　Cellular If the second communication architecture types that data packets are transmitted over the user plane of the plurality of communication architecture types for data packet transmissions for Internet of Things (CIoT) is used for the wireless terminal , the initial UE message including the downlink tunnel end point identifier to be used in the initial Non-Access Stratum (NAS) messages retrieved from the RRC connection setup complete message and the second communication Architecture type child generate a And,
　to transmit the initial UE message to the core network
comprises a non-transitory computer readable media.
[Claim 17]
　A memory,
　at least one processor coupled to the memory,
provided with,
　at least one processor is
　configured to receive the initial UE messages from the radio station, the initial UE message, initials Non from the wireless terminal inclusion and -access Stratum (NAS) message, and the information element indicating the communication architecture types that are determined by the radio station from among a plurality of communication architecture types for data packet transmissions for Cellular Internet of Things (CIoT) and,
　on the basis of the information element, configured to decide to reroute the initial NAS message to the core network corresponding to the determined communication architecture type,
　rerouted to the core network to which the initial NAS message is the corresponding Li that shows is that the Over preparative NAS message request message is configured to transmit to the radio station,
the core network node.
[Claim 18]
　A method in a core network node,
　receiving an initial UE message from the radio station, the initial UE message, and initials Non-Access Stratum (NAS) message from a wireless terminal, data about Cellular Internet of Things (CIoT) includes an information element indicating the communication architecture types that are determined by the radio station from among a plurality of communication architecture type for packet transmission;
　based on said information elements, the determined communication Architecture type and; it decides to reroute the initial NAS message to the corresponding core network
　to send a reroute NAS message request message indicating that the initial NAS message is rerouted to the corresponding core network to the radio station;
equipped with a, square .
[Claim 19]
　The non-transitory computer readable medium storing a program for causing a process in the core network node to the computer,
　the method comprising
　receiving an initial UE message from the radio station, the initial UE message, the wireless terminal information indicating the initial Non-Access Stratum (NAS) message, the communication architecture types that are determined by the radio station from among a plurality of communication architecture types for data packet transmissions for Cellular Internet of Things (CIoT) from includes the elements;
　and; on the basis of the information element, it decides to reroute the initial NAS message to the core network corresponding to the determined communication architecture type
　cores said initial NAS message the corresponding reroute the network Transmitting a reroute NAS message request message indicating the fact that the said radio station;
comprises a non-transitory computer readable media.
[Claim 20]
　A memory,
　at least one processor coupled to the memory,
provided with,
　at least one processor is
　configured to receive the initial UE messages from the radio station, the initial UE message, initials Non from the wireless terminal and -access Stratum (NAS) message, Cellular Internet of Things or the wireless terminal of any use of the plurality of communication architecture types for data packet transmissions for (CIoT) desires, one or supported, or any that includes an information element indicating whether it is set,
　based on said information elements, said configured to determine a communication architecture types used for data packet transmission of the wireless terminal,
　is the determined wherein the core network corresponding to the communication architecture type initials Is configured to decide to reroute the NAS message,
　the initial NAS message is configured to transmit the reroute NAS message request message indicating that it is rerouted to the corresponding core network to the radio station,
the core network node.
[Claim 21]
　The reroute NAS message request message includes an information element indicating the communication architecture type the determined,
a core network node according to claim 20.
[Claim 22]
　A method in a core network node,
　receiving an initial UE message from the radio station, the initial UE message, and initials Non-Access Stratum (NAS) message from a wireless terminal, data about Cellular Internet of Things (CIoT) whether the wireless terminal to any use of the plurality of communication architecture type for packet transmission is desired, one or supported, or any that includes an information element indicating whether it is set;
　the information element ; based on, it determines the communication architecture types used for data packet transmission of the wireless terminal
　decides to reroute the initial NAS message to the core network corresponding to the determined communication Architecture type it is; and
　the initial NAS message There transmitting a reroute NAS message request message indicating that it is rerouted to the core network to which the corresponding to the radio station;
comprises a method.
[Claim 23]
　The non-transitory computer readable medium storing a program for causing a process in the core network node to the computer,
　the method comprising
　receiving an initial UE message from the radio station, the initial UE message, the wireless terminal and initials Non-Access Stratum (NAS) message from, Cellular Internet of Things or the wireless terminal of any use of the plurality of communication architecture types for data packet transmissions for (CIoT) wishes, support either to have or one that includes an information element indicating whether it is set;
　; on the basis of the information element, it determines the communication architecture types used for data packet transmission of the wireless terminal
　said determining the core network corresponding to the communication architecture types that are The possible decides to reroute the initial NAS message; and
　that the initial NAS message to send reroute NAS message request message indicating that it is rerouted to the corresponding core network to the radio station;
comprises, non transitory computer-readable media.
[Claim 24]
　A wireless terminal,
　a memory,
　and at least one processor coupled to said memory,
comprising a
　at least one processor, cell reselection, the reception of the handover indication, or reception of radio resource release request with redirection in response to said being configured to release the communication architecture type of information for the data packet transmission related to Cellular is set in the wireless terminal Internet of Things (CIoT),
wireless terminal.
[Claim 25]
　A wireless terminal,
　a memory,
　and at least one processor coupled to said memory,
comprising a
　at least one processor, when performing cell reselection, the wireless terminal before the cell reselection Cellular Internet of Things is configured to transmit the information element indicating the communication architecture type for data packet transmissions for (CIoT) to the radio station or a core network, which is set in
the wireless terminal.
[Claim 26]
　A wireless station,
　a memory,
　and at least one processor coupled to said memory,
comprising a
　at least one processor is
　receiving a Radio Resource Control (RRC) message including a first information element from the wireless terminal is configured to, the first piece of information shows a communication architecture type for data packet transmissions for Cellular Internet of Things from previous cell reselection are set in the wireless terminal (CIoT),
radio station .
[Claim 27]
　The RRC message further includes a second information element indicating an identifier for identifying a cell or radio station the radio terminal was connected before the cell reselection,
　the at least one processor, wherein the based on the second information element, wherein the wireless terminal before the cell reselection is configured to request the setting information of the wireless terminal to the radio station that was connected,
the radio station according to claim 26 .
[Claim 28]
　A memory,
　at least one processor coupled to the memory,
provided with,
　at least one processor is configured to send a message requesting a handover of the wireless terminal to the target wireless station,
　said message, said wireless It shows a communication architecture type for data packet transmissions for Cellular Internet of Things that are set in the terminal (CIoT),
the source wireless station.
[Claim 29]
　Wherein the at least one processor, indicating that the current communication architecture type even after the handover is continued, or handover instruction including an information element indicating the communication architecture type to be applied to the wireless terminal after said handover the is configured to transmit to the radio terminal,
the source wireless station of claim 28.
[Claim 30]
　A target wireless station,
　a memory,
　and at least one processor coupled to said memory,
comprising a
　at least one processor
　for receiving a first message requesting a handover of a wireless terminal from a source radio station is configured, the first message, the show the first communication architecture types for data packet transmissions for Cellular are set in the wireless terminal Internet of Things (CIoT),
　responsive to the first message is configured to to send a second message to the source radio station, said second message, whether it corresponds to the first communication architecture type, or of the wireless terminals in the target wireless station It shows a second communication architecture types used for,
the target wireless station.
[Claim 31]
　A memory,
　at least one processor coupled to the memory,
provided with,
　at least one processor is the use of any more of the communication architecture types for data packet transmissions for Cellular Internet of Things (CIoT) or desired, and is configured to transmit one or supported, or any take radio Resource Control (RRC) connection request message including the establishment cause, or other information elements indicating whether the set to the radio station ,
wireless terminal.
[Claim 32]
　A memory,
　at least one processor coupled to the memory,
provided with,
　at least one processor is
　configured to receive a Radio Resource Control (RRC) connection request message from the wireless terminal,
　Cellular Internet of Things (CIoT wherein either wireless terminal desires to any use, establishment cause, or other information indicating which whether the support, or any is set among a plurality of communication architecture types for) about the data packet transmission the element is configured to retrieve from the RRC connection request message,
the radio station.