Mobile communication system, communication terminal device, base station device, and base station control device

Abstract

To provide a communication system and the like, capable of mitigating congestion of a core network in a situation in which data is simultaneously communicated from many terminals or to many terminals even when many terminal groups exist under a base station.SOLUTION: A communication system includes: a base station that receives, from a terminal, MTC information showing that the terminal is an MTC device; and a base station controller that controls the base station. The base station notifies the base station controller of MTC identification information for identifying the MTC device. The base station controller notifies the base station of a paging message together with the MTC identification information.SELECTED DRAWING: Figure 26

Description

[Technical Field]

[0001] The present invention relates to a communication system and the like. [Background technology]

[0002] Among the third-generation communication systems, the Wideband Code Division Multiple Access (W-CDMA) system has been commercially available in Japan since 2001. Furthermore, the High Speed ​​Downlink Packet Access (HSDPA) service has been launched, which achieves even faster data transmission speeds on the downlink by adding a packet transmission channel (High Speed-Downlink Shared Channel: HS-DSCH) to the downlink (dedicated data channel, dedicated control channel). Furthermore, the High Speed ​​Uplink Packet Access (HSUPA) service has also been launched to further increase the speed of data transmission in the uplink. W-CDMA is a communication system defined by the 3rd Generation Partnership Project (3GPP), a standardization organization for mobile communication systems, and Release 8 of the standard is currently being compiled.

[0003] Additionally, 3GPP is considering a new communication method other than W-CDMA, called Long Term Evolution (LTE) for wireless sections and System Architecture Evolution (SAE) for the overall system configuration, including the core network (also simply called the network). This communication method is also called the 3.9G (3.9 Generation) system.

[0004] LTE's access method, wireless channel configuration, and protocols will be completely different from those of the current W-CDMA (HSDPA / HSUPA). For example, W-CDMA uses Code Division Multiple Access, while LTE uses Orthogonal Frequency Division Multiplexing (OFDM) for the downlink and Single Carrier Frequency Division Multiple Access (SC-FDMA) for the uplink. Furthermore, while W-CDMA's bandwidth is 5 MHz, LTE's bandwidth can be selected from 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, and 20 MHz for each base station. Also, unlike W-CDMA, LTE does not include circuit switching and is packet-only.

[0005] Because the LTE communication system is configured using a new core network different from the W-CDMA core network (General Packet Radio Service: GPRS), it is defined as an independent radio access network separate from the W-CDMA network. Therefore, to distinguish it from the W-CDMA communication system, in the LTE communication system, the base station that communicates with mobile terminals (User Equipment: UE) is called the E-UTRAN NodeB (eNB), and the base station control device (Radio Network Controller) that exchanges control data and user data with multiple base stations is called the EPC (Evolved Packet Core) or the aGW (Access Gateway). This LTE communication system provides unicast services and E-MBMS (Evolved Multimedia Broadcast Multicast Service). The E-MBMS service is a broadcast multimedia service, sometimes simply referred to as MBMS. It transmits large-capacity broadcast content such as news, weather forecasts, and mobile broadcasts to multiple mobile terminals. This is also known as a point-to-multipoint service.

[0006] Current decisions made by 3GPP regarding the overall architecture of the LTE system are described in Non-Patent Document 1 (Chapter 4.6.1). The overall architecture will be explained using FIG. 1, which is an explanatory diagram showing the configuration of an LTE communication system. In FIG. 1, if a control protocol for a mobile terminal 101, such as RRC (Radio Resource Control), and a user plane, such as PDCP (Packet Data Convergence Protocol), RLC (Radio Link Control), MAC (Medium Access Control), and PHY (Physical layer), terminate at a base station 102, an E-UTRAN (Evolved Universal Terrestrial Radio Access) is composed of one or more base stations 102.

[0007] The base stations 102 schedule and transmit paging signals (also referred to as paging messages) notified from a mobility management entity (MME) 103. The base stations 102 are connected to each other via an X2 interface. The base stations 102 are also connected to an evolved packet core (EPC) via an S1 interface. More specifically, the base stations 102 are connected to a mobility management entity (MME) 103 via an S1_MME interface and to a serving gateway (S-GW) 104 via an S1_U interface.

[0008] The MME 103 distributes paging signals to a single or multiple base stations 102. The MME 103 also performs mobility control in the idle state. The MME 103 manages a tracking area list when a mobile terminal is in the idle state or active state.

[0009] The S-GW 104 transmits and receives user data to and from one or more base stations 102. The S-GW 104 serves as a local mobility anchor point during handover between base stations. The EPC also includes a P-GW (PDN Gateway), which performs packet filtering for each user and assigns UE-ID addresses.

[0010] The control protocol RRC between the mobile terminal 101 and the base station 102 performs broadcast, paging, RRC connection management, etc. The states of the base station and mobile terminal in RRC include RRC_IDLE and RRC_CONNECTED. In RRC_IDLE, PLMN (Public Land Mobile Network) selection, system information (SI) broadcast, paging, cell reselection, mobility, etc. are performed. In RRC_CONNECTED, the mobile terminal has an RRC connection, can transmit and receive data to and from the network, and also performs handover (HO), neighbor cell measurements, etc.

[0011] The current decisions regarding the frame structure in the LTE system at 3GPP, as described in Non-Patent Document 1 (Chapter 5), will be explained using Figure 2. Figure 2 is an explanatory diagram showing the structure of a radio frame used in an LTE communication system. In Figure 2, one radio frame is 10 ms. The radio frame is divided into 10 equally sized subframes. The subframe is divided into two equally sized slots. The first and sixth subframes of each radio frame include a downlink synchronization signal (SS). The synchronization signals include a primary synchronization signal (P-SS) and a secondary synchronization signal (S-SS).

[0012] MBSFN (Multimedia Broadcast Multicast Service Single Frequency Network) and non-MBSFN channels are multiplexed on a subframe basis. MBSFN transmission is a simultaneous transmission technique achieved by transmitting the same waveform from multiple cells at the same time. MBSFN transmissions from multiple cells in an MBSFN area appear to mobile terminals as a single transmission. MBSFN is a network that supports such MBSFN transmission. Hereinafter, a subframe for MBSFN transmission is referred to as an MBSFN subframe.

[0013] Non-Patent Document 2 describes an example of signaling when allocating MBSFN subframes. FIG. 3 is an explanatory diagram showing the structure of an MBSFN frame. In FIG. 3, MBSFN subframes are allocated for each MBSFN frame. MBSFN frames are repeated at an allocation period (radio frame allocation period). MBSFN subframes are subframes allocated for MBSFN in radio frames defined by an allocation period and an allocation offset (radio frame allocation offset), and are subframes for transmitting multimedia data. A radio frame that satisfies the following equation (1) is a radio frame that includes an MBSFN subframe.

[0014] SFN mod radioFrameAllocationPeriod=radioFrameAllocationOffset …(1) MBSFN subframe allocation is performed using 6 bits. The leftmost bit defines the MBSFN allocation for subframe 2 (#1). The second bit defines the MBSFN allocation for subframe 3 (#2), the third bit defines the MBSFN allocation for subframe 4 (#3), the fourth bit defines the MBSFN allocation for subframe 7 (#6), the fifth bit defines the MBSFN allocation for subframe 8 (#7), and the sixth bit defines the MBSFN allocation for subframe 9 (#8). If the bit indicates "1", it indicates that the corresponding subframe is allocated for MBSFN.

[0015] Current decisions regarding channel configuration in LTE systems at 3GPP are described in Non-Patent Document 1 (Chapter 5). It is assumed that the same channel configuration as that of non-CSG cells is used in CSG (Closed Subscriber Group) cells. Physical channels are explained using FIG. 4. FIG. 4 is an explanatory diagram illustrating physical channels used in an LTE communication system. In FIG. 4, a Physical Broadcast Channel (PBCH) 401 is a downlink channel transmitted from a base station 102 to a mobile terminal 101. A BCH transport block is mapped to four subframes in a 40 ms interval. There is no explicit signaling of the 40 ms timing. A Physical Control Format Indicator Channel (PCFICH) 402 is transmitted from the base station 102 to the mobile terminal 101. The PCFICH notifies the mobile terminal 101 of the number of OFDM symbols used for PDCCHs. The PCFICH is transmitted for each subframe.

[0016] The Physical Downlink Control Channel (PDCCH) 403 is a downlink channel transmitted from the base station 102 to the mobile terminal 101. The PDCCH reports resource allocation, HARQ (Hybrid Automatic Repeat reQuest) information related to DL-SCH (a downlink shared channel, which is one of the transport channels shown in FIG. 5, which will be described later), and PCH (a paging channel, which is one of the transport channels shown in FIG. 5). The PDCCH carries an uplink scheduling grant. The PDCCH carries Ack (Acknowledgement) / Nack (Negative Acknowledgement), which are response signals to uplink transmission. The PDCCH is also called an L1 / L2 control signal.

[0017] The Physical Downlink Shared Channel (PDSCH) 404 is a downlink channel transmitted from the base station 102 to the mobile terminal 101. The DL-SCH (downlink shared channel), which is a transport channel, and the PCH, which is a transport channel, are mapped to the PDSCH. The Physical Multicast Channel (PMCH) 405 is a downlink channel transmitted from the base station 102 to the mobile terminal 101. The MCH (multicast channel), which is a transport channel, is mapped to the PMCH.

[0018] The Physical Uplink Control Channel (PUCCH) 406 is an uplink channel transmitted from the mobile terminal 101 to the base station 102. The PUCCH carries Ack / Nack, which is a response signal to a downlink transmission. The PUCCH carries a CQI (Channel Quality Indicator) report. The CQI is quality information indicating the quality of received data or the quality of the communication path. The PUCCH also carries a Scheduling Request (SR). The Physical Uplink Shared Channel (PUSCH) 407 is an uplink channel transmitted from the mobile terminal 101 to the base station 102. The UL-SCH (the uplink shared channel, which is one of the transport channels shown in FIG. 5) is mapped to the PUSCH.

[0019] A Physical Hybrid ARQ Indicator Channel (PHICH) 408 is a downlink channel transmitted from the base station 102 to the mobile terminal 101. The PHICH carries Ack / Nack, which is a response to an uplink transmission. A Physical Random Access Channel (PRACH) 409 is an uplink channel transmitted from the mobile terminal 101 to the base station 102. The PRACH carries a random access preamble.

[0020] The downlink reference signal is a symbol known in mobile communication systems. Reference symbol received power (RSRP) is a physical layer measurement of a mobile terminal.

[0021] The transport channels described in Non-Patent Document 1 (Chapter 5) will be explained using Fig. 5. Fig. 5 is an explanatory diagram explaining the transport channels used in an LTE communication system. Fig. 5(A) shows the mapping between downlink transport channels and downlink physical channels. Fig. 5(B) shows the mapping between uplink transport channels and uplink physical channels.

[0022] A broadcast channel (BCH) for downlink transport channels is broadcast to the entire coverage of the base station (cell). The BCH is mapped to a physical broadcast channel (PBCH).

[0023] The Downlink Shared Channel (DL-SCH) is subject to retransmission control using Hybrid ARQ (HARQ). DL-SCH can be broadcast to the entire coverage of a base station (cell). DL-SCH supports dynamic or semi-static resource allocation. Semi-static resource allocation is also known as persistent scheduling. DL-SCH supports DRX (Discontinuous reception) for mobile terminals to reduce power consumption. DL-SCH is mapped to the Physical Downlink Shared Channel (PDSCH).

[0024] The Paging Channel (PCH) supports DRX of mobile terminals to enable low power consumption of the mobile terminals. The PCH is required to broadcast to the entire coverage of the base station (cell). The PCH is mapped to physical resources such as the Physical Downlink Shared Channel (PDSCH) that can be dynamically used for traffic, or to physical resources such as the Physical Downlink Control Channel (PDCCH) of other control channels.

[0025] The Multicast Channel (MCH) is used for broadcasting to the entire coverage of a base station (cell). The MCH supports SFN combining of MBMS services (MTCH and MCCH) in multi-cell transmission. The MCH supports semi-static resource allocation. The MCH is mapped to the PMCH.

[0026] The Uplink Shared Channel (UL-SCH) is subject to retransmission control using Hybrid ARQ (HARQ). The UL-SCH supports dynamic or semi-static resource allocation. The UL-SCH is mapped to the Physical Uplink Shared Channel (PUSCH).

[0027] The Random Access Channel (RACH) shown in Figure 5(B) is limited to control information. The RACH has a risk of collision. The RACH is mapped to the Physical Random Access Channel (PRACH).

[0028] We will explain HARQ. HARQ is a technology that improves the communication quality of a transmission path by combining Automatic Repeat reQuest (ARQ) and Forward Error Correction. It has the advantage that error correction works effectively by retransmission even for transmission paths where communication quality varies. In particular, by combining the reception results of the initial transmission and the retransmission when retransmitting, it is possible to obtain further quality improvements.

[0029] An example of a retransmission method will be explained below. If the receiving side is unable to decode the received data correctly, in other words, if a CRC (Cyclic Redundancy Check) error occurs (CRC=NG), the receiving side will send a "Nack" to the sending side. The sending side, having received the "Nack," will retransmit the data. If the receiving side is able to decode the received data correctly, in other words, if no CRC error occurs (CRC=OK), the receiving side will send an "Ack" to the sending side. The sending side, having received the "Ack," will send the next data.

[0030] One example of an HARQ scheme is Chase Combining. Chase Combining transmits the same data sequence for the initial transmission and retransmission, and improves the gain by combining the initial transmission data sequence with the retransmission data sequence during retransmission. This is based on the idea that even if the initial transmission data contains errors, some of the data may be correct, and by combining the correct parts of the initial transmission data with the retransmission data, data can be transmitted with higher accuracy. Another example of an HARQ scheme is Incremental Redundancy (IR). IR increases redundancy by transmitting parity bits during retransmission, which increases redundancy by combining with the initial transmission, and improves quality through error correction.

[0031] The logical channels described in Non-Patent Document 1 (Chapter 6) will be explained using Fig. 6. Fig. 6 is an explanatory diagram explaining logical channels used in an LTE communication system. Fig. 6(A) shows mapping between downlink logical channels and downlink transport channels. Fig. 6(B) shows mapping between uplink logical channels and uplink transport channels.

[0032] The Broadcast Control Channel (BCCH) is a downlink channel for broadcast system control information. The BCCH, which is a logical channel, is mapped to the Broadcast Channel (BCH), which is a transport channel, or the Downlink Shared Channel (DL-SCH).

[0033] The Paging Control Channel (PCCH) is a downlink channel for transmitting paging signals. The PCCH is used when the network does not know the cell location of the mobile terminal. The PCCH, which is a logical channel, is mapped to the Paging Channel (PCH), which is a transport channel.

[0034] The Common Control Channel (CCCH) is a channel for transmitting control information between a mobile terminal and a base station. The CCCH is used when the mobile terminal does not have an RRC connection with the network. In the downlink direction, the CCCH is mapped to the Downlink Shared Channel (DL-SCH), which is a transport channel. In the uplink direction, the CCCH is mapped to the Uplink Shared Channel (UL-SCH), which is a transport channel.

[0035] The Multicast Control Channel (MCCH) is a downlink channel for point-to-multipoint transmission. It is a channel used to transmit MBMS control information for one or several MTCHs from the network to mobile terminals. The MCCH is a channel used only by mobile terminals receiving MBMS. The MCCH is mapped to the transport channel, the Downlink Shared Channel (DL-SCH) or the Multicast Channel (MCH).

[0036] A Dedicated Control Channel (DCCH) is a channel that transmits dedicated control information between a mobile terminal and a network. The DCCH is mapped to an Uplink Shared Channel (UL-SCH) in the uplink and to a Downlink Shared Channel (DL-SCH) in the downlink.

[0037] A Dedicated Traffic Channel (DTCH) is a point-to-point communication channel for transmitting user information to an individual mobile terminal. DTCH exists in both uplink and downlink. In uplink, DTCH is mapped to an uplink shared channel (UL-SCH) and in downlink, it is mapped to a downlink shared channel (DL-SCH).

[0038] The Multicast Traffic Channel (MTCH) is a downlink channel for transmitting traffic data from the network to mobile terminals. The MTCH is a channel used only by mobile terminals receiving MBMS. The MTCH is mapped to the Downlink Shared Channel (DL-SCH) or the Multicast Channel (MCH).

[0039] GCI stands for Global Cell Identity. In LTE and UMTS (Universal Mobile Telecommunication System), CSG cells (Closed Subscriber Group cells) are introduced. CSG is explained below (see Non-Patent Document 3, Chapter 3.1). A CSG (Closed Subscriber Group) is a cell in which an operator specifies available subscribers (a cell for specific subscribers).

[0040] An identified subscriber is authorized to access one or more E-UTRAN cells of a PLMN (Public Land Mobile Network). The one or more E-UTRAN cells to which an identified subscriber is authorized are called "CSG cell(s)". However, PLMNs have access restrictions. A CSG cell is a part of a PLMN that broadcasts a unique CSG identity (CSG ID; CSG-ID). Members of a pre-registered and authorized subscriber group access CSG cells using the CSG-ID, which is access permission information.

[0041] The CSG-ID is broadcast by a CSG cell or cells, and there are multiple CSG-IDs in a mobile communication system, and the CSG-ID is used by a mobile terminal (UE) to facilitate access to CSG-related members.

[0042] The location of a mobile terminal is tracked in units of an area consisting of one or more cells. This location tracking is done to enable tracking the location of a mobile terminal even when it is in standby mode and calling the mobile terminal (the mobile terminal can receive calls). The area used for tracking the location of a mobile terminal is called a tracking area.

[0043] The CSG White List is a list stored in the Universal Subscriber Identity Module (USIM) that contains all CSG IDs of the CSG cells to which the subscriber belongs. The CSG White List is also sometimes called the Allowed CSG ID List.

[0044] The term "suitable cell" is explained below (see Chapter 4.3 of Non-Patent Document 3). A "suitable cell" is a cell on which a UE can camp to receive normal services. Such a cell must satisfy the following conditions (1) and (2).

[0045] (1) The cell is part of the selected or registered PLMN, or a PLMN in the "Equivalent PLMN List."

[0046] (2) The latest information provided by the NAS (Non-Access Stratum) and the following conditions (a) to (d) must be met: (a) The cell is not a barred cell. (b) The cell is not part of the "prohibited LAs for roaming" list and is part of at least one Tracking Area (TA). In that case, the cell must satisfy (1) above. (c) the cell satisfies the cell selection criteria. (d) For a cell that is identified by System Information (SI) as a CSG cell, the CSG-ID is part of the UE's "CSG WhiteList" (included in the UE's CSG WhiteList).

[0047] An "acceptable cell" is described below (see Chapter 4.3 of Non-Patent Document 3). This is a cell on which a UE can camp to receive limited services (emergency calls). Such a cell shall fulfill all of the following requirements. In other words, the minimum set of requirements for initiating an emergency call in an E-UTRAN network is as follows: (1) The cell is not a barred cell. (2) The cell meets the cell selection evaluation criteria.

[0048] Camping on a cell refers to a state in which the UE has completed the cell selection / reselection process and selected a cell for monitoring system information and paging information.

[0049] 3GPP is studying base stations called Home-NodeB (Home-NB; HNB) and Home-eNodeB (Home-eNB; HeNB). HNB in ​​UTRAN or HeNB in ​​E-UTRAN is a base station for access services for homes, businesses, and businesses, for example. Non-Patent Document 4 discloses three different modes of access to HeNB and HNB. Specifically, these are open access mode, closed access mode, and hybrid access mode.

[0050] Each mode has the following characteristics: In open access mode, a HeNB or HNB is operated as a normal cell of a regular operator. In closed access mode, a HeNB or HNB is operated as a CSG cell, which is a CSG cell that can only be accessed by CSG members. In hybrid access mode, it is a CSG cell that is simultaneously accessible to non-CSG members. In other words, a hybrid access mode cell (also called a hybrid cell) is a cell that supports both open access mode and closed access mode.

[0051] In 3GPP, there is discussion about dividing all PCIs (Physical Cell Identities) into those for CSG cells and those for non-CSG cells (referred to as PCI split) (see Non-Patent Document 5). There is also discussion about PCI split information being broadcast from a base station to mobile terminals under its control in system information. The basic operation of a mobile terminal using PCI split will be disclosed. A mobile terminal that does not have PCI split information needs to perform a cell search using all PCIs (for example, using all 504 codes). In contrast, a mobile terminal that has PCI split information can perform a cell search using the PCI split information.

[0052] Furthermore, 3GPP is currently formulating standards for Long Term Evolution Advanced (LTE-A) as Release 10 (see Non-Patent Documents 6 and 7).

[0053] In the LTE-A system, support for relays (Relay Nodes (RNs)) is being considered to achieve high communication speeds, high throughput at cell edges, new coverage areas, and so on. The relay nodes are wirelessly connected to the radio access network via donor cells (Donor eNBs; DeNBs). Within the range of the donor cell, the link from the network (NW) to the relay shares the same frequency band as the link from the network to the UE. In this case, Release 8 UEs can also connect to the donor cell. The link between the donor cell and the relay node is called the backhaul link, and the link between the relay node and the UE is called the access link.

[0054] In the FDD (Frequency Division Duplex) backhaul link multiplexing method, transmission from DeNB to RN is performed in the downlink (DL) frequency band, and transmission from RN to DeNB is performed in the uplink (UL) frequency band. In the relay resource division method, the link from DeNB to RN and the link from RN to UE are time-division multiplexed in one frequency band, and the link from RN to DeNB and the link from UE to RN are also time-division multiplexed in one frequency band. This prevents the transmission of a relay from interfering with the reception of the relay itself.

[0055] 3GPP is considering not only regular eNBs (macro cells), but also so-called local nodes such as pico eNBs (pico cells), HeNBs / HNBs / CSG cells, nodes for hot zone cells, relay nodes, and remote radio heads (RRHs).

[0056] These local nodes are deployed to complement macrocells in response to various service requirements, such as high-speed and large-capacity communications. For example, HeNBs are required to be installed in large numbers in shopping districts, apartment buildings, schools, and companies. For this reason, HeNBs may be installed within the coverage area of ​​a macrocell. When a HeNB is installed within the coverage area of ​​a macrocell, interference occurs between the macrocell, HeNB, and mobile terminals (UE). This interference prevents the mobile terminals (UE) from communicating with the macrocell or HeNB, resulting in a decrease in communication speed. If the interference power becomes even greater, communication may become impossible. Therefore, a method is needed to avoid interference and optimize communication quality in situations where macrocells and local nodes are deployed together.

[0057] In 3GPP, studies on Machine Type Communication (MTC) technology are underway (see Non-Patent Document 8). The number of MTC devices (MTC Devices: MTCDs) is expected to be enormous. In MTC services, situations arise in which data is communicated simultaneously from or to a large number of MTCDs. This causes a problem of congestion in the core network.

[0058] In order to solve such a problem, Non-Patent Document 9 discloses that an eNB holds back and aggregates signaling messages common to MTCDs in the same MTCD group, thereby making the signaling messages compact. [Prior art documents] [Non-patent literature]

[0059] [Non-Patent Document 1] 3GPP TS36.300 V10.0.0 Chapter 4.6.1, Chapter 4.6.2, Chapter 5, Chapter 6, Chapter 10.1.2, Chapter 10.7 [Non-patent document 2] 3GPP TS36.331 V9.3.0 [Non-patent document 3] 3GPP TS36.304 V9.3.0 Chapter 3.1, Chapter 4.3, Chapter 5.2.4 [Non-patent document 4] 3GPP S1-083461 [Non-Patent Document 5] 3GPP R2-082899 [Non-patent document 6] 3GPP TR 36.814 V9.0.0 [Non-Patent Document 7] 3GPP TR 36.912 V9.0.0 [Non-patent document 8] 3GPP TS 22.368 V2.0.0 [Non-Patent Document 9] 3GPP S2-103186 Summary of the Invention [Problem to be solved by the invention]

[0060] As described above, Non-Patent Document 9 discloses that the eNB holds back and aggregates signaling messages common to MTCDs in the same MTCD group, thereby making the signaling messages compact.

[0061] However, when there are many MTCD groups under the umbrella of an eNB, even if the method disclosed in Non-Patent Document 9 is used, the above-mentioned problem of congestion occurring in the core network recurs.

[0062] An object of the present invention is to provide a communication system etc. that can alleviate congestion in a core network when a situation arises in which data is communicated simultaneously from or to a large number of MTCDs, even when there are many MTCD groups under an eNB. [Means for solving the problem]

[0063] The mobile communication system of the present invention is a mobile communication system including a communication terminal device, a base station device that performs wireless communication with the communication terminal device, and a base station control device that controls the base station device, wherein the communication terminal device is an MTC (Machine Type Communication) device, the base station control device includes an MME (Mobility Management Entity), and data is transmitted from the communication terminal device to the MME via the base station device. [Effects of the Invention]

[0064] According to the present invention, even when there are a large number of terminal groups under the umbrella of a base station, congestion in the core network can be alleviated when a situation arises in which data needs to be communicated between a large number of terminals included in these groups.

[0065] The objects, features, aspects, and advantages of the present invention will become more apparent from the following detailed description and the accompanying drawings. [Brief explanation of the drawings]

[0066] [Figure 1] FIG. 1 is an explanatory diagram showing the configuration of an LTE communication system. [Figure 2] FIG. 1 is an explanatory diagram showing the configuration of a radio frame used in an LTE communication system. [Figure 3] FIG. 1 is an explanatory diagram showing the structure of an MBSFN frame. [Figure 4] FIG. 1 is an explanatory diagram illustrating physical channels used in an LTE communication system. [Figure 5] FIG. 1 is an explanatory diagram illustrating transport channels used in an LTE communication system. [Figure 6] FIG. 1 is an explanatory diagram illustrating logical channels used in an LTE communication system. [Figure 7] 1 is a block diagram showing the overall configuration of an LTE mobile communication system currently being discussed in 3GPP. [Figure 8] FIG. 8 is a block diagram showing the configuration of a mobile terminal (mobile terminal 71 in FIG. 7) according to the present invention. [Figure 9] FIG. 8 is a block diagram showing the configuration of a base station (base station 72 in FIG. 7) according to the present invention. [Figure 10] 8 is a block diagram showing the configuration of an MME (MME unit 73 in FIG. 7) according to the present invention. FIG. [Figure 11] FIG. 8 is a block diagram showing the configuration of a HeNBGW 74 shown in FIG. 7 which is a HeNBGW according to the present invention. [Figure 12] 1 is a flowchart showing an outline of operations from cell search to standby operation performed by a mobile terminal (UE) in an LTE communication system. [Figure 13] FIG. 1 is an explanatory diagram showing an example of an MTC architecture being studied by 3GPP. [Figure 14] FIG. 1 is a diagram showing a protocol stack for control data between a UE and an MME in the prior art. [Figure 15] FIG. 2 is a diagram illustrating a protocol stack of control data between an MTCD and an MME according to the first embodiment. [Figure 16] FIG. 4 is a flowchart illustrating a processing procedure of a HeNB regarding line concentration processing according to the first embodiment. [Figure 17] FIG. 2 is a diagram showing a sequence of the mobile communication system in the first embodiment. [Figure 18] 10 is a flowchart showing a processing procedure of a HeNB related to a concentration process according to a first modification of the first embodiment; [Figure 19] FIG. 10 is a diagram showing a sequence of a mobile communication system according to a second modification of the first embodiment. [Figure 20] FIG. 10 is a diagram showing a sequence of a mobile communication system according to a third modification of the first embodiment. [Figure 21] FIG. 11 is a diagram showing a sequence of a mobile communication system according to a fourth modification of the first embodiment. [Figure 22] FIG. 10 is a diagram showing a sequence of a mobile communication system in the second embodiment. [Figure 23] FIG. 10 is a diagram showing a sequence of a mobile communication system in the second embodiment. [Figure 24] FIG. 10 is a diagram showing a sequence of a mobile communication system according to a first modification of the second embodiment. [Figure 25] FIG. 10 is a diagram showing a sequence of a mobile communication system in a third modification of the second embodiment. [Figure 26] FIG. 11 is a diagram showing a sequence of a mobile communication system in the third embodiment. [Figure 27] FIG. 11 is a diagram showing a sequence of a mobile communication system in a fourth embodiment. [Figure 28] FIG. 13 is a diagram showing a sequence of a mobile communication system in a fifth embodiment. [Figure 29] FIG. 13 is a diagram showing a sequence of a mobile communication system in a fifth embodiment. [Figure 30] 1 is a sequence of a mobile communication system in a diagram showing locations for explaining a current paging method. [Figure 31] FIG. 11 is a diagram showing a sequence of a mobile communication system for explaining the waste of radio resources when the third embodiment is executed. [Figure 32] FIG. 11 is a diagram showing a sequence of a mobile communication system for explaining the waste of radio resources when the third embodiment is executed. [Figure 33] FIG. 11 is a diagram showing a sequence of a mobile communication system for explaining the waste of radio resources when the fourth embodiment is executed. [Figure 34] FIG. 11 is a diagram showing a sequence of a mobile communication system for explaining the waste of radio resources when the fourth embodiment is executed. [Figure 35] FIG. 20 is a diagram showing a sequence of a mobile communication system in a seventh embodiment. [Figure 36] FIG. 20 is a diagram showing a sequence of a mobile communication system in a seventh embodiment. [Figure 37] FIG. 13 is a diagram showing another sequence of the mobile communication system in the seventh embodiment. [Figure 38] FIG. 13 is a diagram showing another sequence of the mobile communication system in the seventh embodiment. [Figure 39] FIG. 13 is a diagram showing another sequence of the mobile communication system in the seventh embodiment. [Figure 40] FIG. 13 is a diagram showing another sequence of the mobile communication system in the seventh embodiment. [Figure 41] FIG. 13 is a diagram showing another sequence of the mobile communication system in the seventh embodiment. [Figure 42] FIG. 13 is a diagram showing another sequence of the mobile communication system in the seventh embodiment. [Figure 43] FIG. 20 is a diagram showing a sequence of a mobile communication system in a first modification of the seventh embodiment. [Figure 44] FIG. 20 is a diagram showing a sequence of a mobile communication system in a first modification of the seventh embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0067] Embodiment 1 Fig. 7 is a block diagram showing the overall configuration of an LTE mobile communication system currently being discussed in 3GPP. Currently, 3GPP is considering the overall configuration of a system including CSG (Closed Subscriber Group) cells (Home-eNodeB (Home-eNB; HeNB) of E-UTRAN, Home-NB (HNB) of UTRAN) and non-CSG cells (eNodeB (eNB) of E-UTRAN, NodeB (NB) of UTRAN, BSS of GERAN), and a configuration such as that shown in Fig. 7 has been proposed for E-UTRAN (see Chapter 4.6.1 of Non-Patent Document 1).

[0068] Referring to Figure 7, a mobile terminal device (hereinafter referred to as "mobile terminal" or "User Equipment (UE)") 71 is capable of wireless communication with a base station device (hereinafter referred to as "base station") 72, and transmits and receives signals via wireless communication. The mobile terminal device corresponds to a communication terminal device. Hereinafter, the mobile terminal device may also be referred to as a "communication terminal." The base stations 72 are classified into eNB72-1, which is a macrocell, and Home-eNB72-2, which is a local node. The eNB72-1 corresponds to a large-scale base station device and has a relatively large coverage area, which is the range in which communication with the mobile terminal UE71 is possible. The Home-eNB72-2 corresponds to a small-scale base station device and has a relatively small coverage area.

[0069] The eNB72-1 is connected to an MME, an S-GW, or an MME / S-GW unit (hereinafter sometimes referred to as an "MME unit") 73 including an MME and an S-GW via an S1 interface, and control information is communicated between the eNB72-1 and the MME unit 73. Multiple MME units 73 may be connected to one eNB72-1. The eNBs 72-1 are connected to each other via an X2 interface, and control information is communicated between the eNBs 72-1.

[0070] The Home-eNB72-2 is connected to the MME unit 73 via an S1 interface, and control information is communicated between the Home-eNB72-2 and the MME unit 73. Multiple Home-eNBs 72-2 are connected to one MME unit 73. Alternatively, the Home-eNB72-2 is connected to the MME unit 73 via a HeNBGW (Home-eNB GateWay) 74. The Home-eNB72-2 and the HeNBGW74 are connected via an S1 interface, and the HeNBGW74 and the MME unit 73 are connected via an S1 interface. One or more Home-eNBs 72-2 are connected to one HeNBGW 74, and information is communicated via the S1 interface. The HeNBGW74 is connected to one or more MME units 73, and information is communicated via the S1 interface.

[0071] Furthermore, the following configurations are currently being considered in 3GPP: The X2 interface between the Home-eNB72-2 is not supported. From the MME unit 73, the HeNBGW74 appears as the eNB72-1. From the Home-eNB72-2, the HeNBGW74 appears as the MME unit 73. Regardless of whether the Home-eNB72-2 is connected to the MME unit 73 via the HeNBGW74, the interface between the Home-eNB72-2 and the MME unit 73 is the same, the S1 interface. Mobility to or from the Home-eNB72-2 that spans multiple MME units 73 is not supported. The Home-eNB72-2 supports only one cell.

[0072] FIG. 8 is a block diagram showing the configuration of a mobile terminal (mobile terminal 71 in FIG. 7) according to the present invention. The transmission process of the mobile terminal 71 shown in FIG. 8 will be described. First, control data from a protocol processing unit 801 and user data from an application unit 802 are stored in a transmission data buffer unit 803. The data stored in the transmission data buffer unit 803 is passed to an encoder unit 804, where it is subjected to encoding processes such as error correction. Some data may be output directly from the transmission data buffer unit 803 to a modulator unit 805 without being encoded. The data encoded by the encoder unit 804 is modulated by a modulator unit 805. The modulated data is converted into a baseband signal, and then output to a frequency converter unit 806, where it is converted into a radio transmission frequency. A transmission signal is then transmitted from an antenna 807 to the base station 72.

[0073] Furthermore, the reception process of the mobile terminal 71 is performed as follows. A radio signal from the base station 72 is received by the antenna 807. The received signal is converted from a radio reception frequency to a baseband signal by the frequency conversion unit 806, and demodulated by the demodulation unit 808. The demodulated data is passed to the decoder unit 809, where decoding processes such as error correction are performed. Of the decoded data, control data is passed to the protocol processing unit 801, and user data is passed to the application unit 802. A series of processes of the mobile terminal 71 is controlled by the control unit 810. Therefore, although the control unit 810 is omitted in FIG. 8, it is connected to each of the units 801 to 809.

[0074] FIG. 9 is a block diagram showing the configuration of a base station (base station 72 in FIG. 7) according to the present invention. The transmission processing of the base station 72 shown in FIG. 9 will be described. An EPC communication unit 901 transmits and receives data between the base station 72 and the EPC (MME unit 73, HeNBGW 74, etc.). An other base station communication unit 902 transmits and receives data with other base stations. Since the X2 interface between the Home-eNB 72-2 is not expected to be supported, it is possible that the other base station communication unit 902 does not exist in the Home-eNB 72-2. The EPC communication unit 901 and the other base station communication unit 902 each exchange information with a protocol processing unit 903. Control data from the protocol processing unit 903, and user data and control data from the EPC communication unit 901 and the other base station communication unit 902 are stored in a transmission data buffer unit 904.

[0075] The data stored in the transmission data buffer unit 904 is passed to an encoder unit 905, where it undergoes encoding processes such as error correction. Some data may be output directly from the transmission data buffer unit 904 to a modulator unit 906 without undergoing encoding processes. The encoded data is modulated by the modulator unit 906. The modulated data is converted into a baseband signal, and then output to a frequency converter unit 907, where it is converted into a radio transmission frequency. The transmission signal is then transmitted from an antenna 908 to one or more mobile terminals 71.

[0076] Furthermore, the reception process of the base station 72 is performed as follows. A radio signal from one or more mobile terminals 71 is received by an antenna 908. The received signal is converted from a radio reception frequency to a baseband signal by a frequency conversion unit 907, and demodulated by a demodulation unit 909. The demodulated data is passed to a decoder unit 910, where decoding processes such as error correction are performed. Of the decoded data, control data is passed to a protocol processing unit 903 or an EPC communication unit 901 or an other base station communication unit 902, and user data is passed to the EPC communication unit 901 and the other base station communication unit 902. A series of processes of the base station 72 is controlled by a control unit 911. Therefore, although the control unit 911 is omitted in FIG. 9, it is connected to each of the units 901 to 910.

[0077] The functions of the Home-eNB72-2 currently being discussed in 3GPP are shown below (see Chapter 4.6.2 of Non-Patent Document 1). The Home-eNB72-2 has the same functions as the eNB72-1. In addition, when connecting to a HeNBGW74, the Home-eNB72-2 has a function to discover an appropriate serving HeNBGW74. The Home-eNB72-2 connects to only one HeNBGW74. In other words, when connecting to a HeNBGW74, the Home-eNB72-2 does not use the Flex function in the S1 interface. When the Home-eNB72-2 is connected to one HeNBGW74, it does not connect to another HeNBGW74 or another MME unit 73 at the same time.

[0078] The TAC and PLMN ID of the Home-eNB72-2 are supported by the HeNBGW74. When the Home-eNB72-2 is connected to the HeNBGW74, the selection of the MME unit 73 in "UE attachment" is performed by the HeNBGW74 instead of the Home-eNB72-2. The Home-eNB72-2 may be deployed without network planning. In this case, the Home-eNB72-2 is moved from one geographical area to another. Therefore, the Home-eNB72-2 in this case needs to be connected to different HeNBGW74 depending on its location.

[0079] Figure 10 is a block diagram showing the configuration of an MME according to the present invention. Figure 10 shows the configuration of an MME 73a included in the MME unit 73 shown in Figure 7 above. A PDN GW communication unit 1001 transmits and receives data between the MME 73a and a PDN GW. A base station communication unit 1002 transmits and receives data via the S1 interface between the MME 73a and a base station 72. If the data received from the PDN GW is user data, the user data is passed from the PDN GW communication unit 1001 to the base station communication unit 1002 via a user plane communication unit 1003, and transmitted to one or more base stations 72. If the data received from the base station 72 is user data, the user data is passed from the base station communication unit 1002 to the PDN GW communication unit 1001 via the user plane communication unit 1003, and transmitted to the PDN GW.

[0080] If the data received from the PDN GW is control data, the control data is passed from the PDN GW communication unit 1001 to the control plane control unit 1005. If the data received from the base station 72 is control data, the control data is passed from the base station communication unit 1002 to the control plane control unit 1005.

[0081] The HeNBGW communication unit 1004 is provided when a HeNBGW 74 is present, and transmits and receives data via an interface (IF) between the MME 73a and the HeNBGW 74 depending on the information type. Control data received from the HeNBGW communication unit 1004 is passed from the HeNBGW communication unit 1004 to the control plane control unit 1005. The result of processing in the control plane control unit 1005 is transmitted to the PDN GW via the PDN GW communication unit 1001. In addition, the result of processing in the control plane control unit 1005 is transmitted to one or more base stations 72 via the base station communication unit 1002 by the S1 interface, and is also transmitted to one or more HeNBGWs 74 via the HeNBGW communication unit 1004.

[0082] The control plane control unit 1005 includes a NAS security unit 1005-1, an SAE bearer control unit 1005-2, an idle state mobility management unit 1005-3, and the like, and performs overall processing for the control plane. The NAS security unit 1005-1 performs security for NAS (Non-Access Stratum) messages, etc. The SAE bearer control unit 1005-2 performs management of SAE (System Architecture Evolution) bearers, etc. The idle state mobility management unit 1005-3 performs mobility management in the standby state (LTE-IDLE state, also simply referred to as idle), generation and control of paging signals in the standby state, addition, deletion, update, and search of tracking areas (TAs) for one or more mobile terminals 71 under its control, and management of the tracking area list (TA List).

[0083] The MME 73a initiates a paging protocol by transmitting a paging message to a cell belonging to a tracking area (TA) in which the UE is registered. The idle state mobility management unit 1005-3 may manage the CSG, CSG-ID, and whitelist of the Home-eNB 72-2 connected to the MME 73a.

[0084] In the management of CSG-IDs, the relationship between a mobile terminal corresponding to a CSG-ID and a CSG cell is managed (added, deleted, updated, searched). For example, the relationship may be the relationship between one or more mobile terminals registered for user access to a certain CSG-ID and the CSG cell belonging to that CSG-ID. In the management of whitelists, the relationship between mobile terminals and CSG-IDs is managed (added, deleted, updated, searched). For example, a whitelist may store one or more CSG-IDs registered by a user of a certain mobile terminal. The management of these CSG-related information may be performed by other parts of the MME 73a. A series of processes of the MME 73a is controlled by the control unit 1006. Therefore, although not shown in FIG. 10, the control unit 1006 is connected to each of the units 1001 to 1005.

[0085] The functions of the MME 73a currently being discussed in 3GPP are as follows (see Chapter 4.6.2 of Non-Patent Document 1). The MME 73a performs access control for one or more mobile terminals that are members of CSGs (Closed Subscriber Groups). The MME 73a optionally allows the execution of paging optimization.

[0086] Fig. 11 is a block diagram showing the configuration of the HeNBGW 74 shown in Fig. 7 which is a HeNBGW according to the present invention. An EPC communication unit 1101 transmits and receives data between the HeNBGW 74 and the MME 73a via the S1 interface. A base station communication unit 1102 transmits and receives data between the HeNBGW 74 and the Home-eNB 72-2 via the S1 interface. A location processing unit 1103 performs processing to transmit registration information and the like out of the data from the MME 73a passed via the EPC communication unit 1101 to multiple Home-eNBs 72-2. The data processed by the location processing unit 1103 is passed to the base station communication unit 1102 and transmitted to one or multiple Home-eNBs 72-2 via the S1 interface.

[0087] Data that does not require processing by location processing unit 1103 and is merely passed through (transmitted) is passed from EPC communication unit 1101 to base station communication unit 1102, and transmitted to one or more Home-eNBs 72-2 via the S1 interface. A series of processes by HeNBGW 74 is controlled by control unit 1104. Therefore, although omitted in Fig. 11, control unit 1104 is connected to each of units 1101 to 1103.

[0088] The functions of HeNBGW 74 currently being discussed in 3GPP are as follows (see Chapter 4.6.2 of Non-Patent Document 1). HeNBGW 74 relays S1 applications. Although it is part of the procedure of the MME 73a to the Home-eNB 72-2, HeNBGW 74 terminates S1 applications that are not related to the mobile terminal 71. When HeNBGW 74 is deployed, procedures unrelated to the mobile terminal 71 are communicated between the Home-eNB 72-2 and HeNBGW 74, and between HeNBGW 74 and MME 73a. No X2 interface is set up between HeNBGW 74 and other nodes. HeNBGW 74 allows execution of paging optimization as an option.

[0089] Next, an example of a general cell search method in a mobile communication system is shown. Fig. 12 is a flowchart showing an outline of the process from cell search to standby operation performed by a mobile terminal (UE) in an LTE communication system. When the mobile terminal starts a cell search, in step ST1201, it synchronizes slot timing and frame timing using a primary synchronization signal (P-SS) and a secondary synchronization signal (S-SS) transmitted from a surrounding base station. The synchronization signal (SS) combining the P-SS and S-SS is assigned a synchronization code that corresponds one-to-one to a PCI (Physical Cell Identity) assigned to each cell. Currently, 504 different PCIs are being considered, and synchronization is achieved using these 504 PCIs, and the PCI of the synchronized cell is detected (identified).

[0090] Next, in step ST1202, for the synchronized cell, a reference signal RS (cell-specific Reference Signal: CRS) transmitted from the base station for each cell is detected and the received power (also referred to as RSRP) is measured. The reference signal RS uses a code that has a one-to-one correspondence with the PCI, and by correlating with this code, it is possible to separate the cell from other cells. By deriving the code for the RS of the cell from the PCI identified in step ST1201, it is possible to detect the RS and measure the RS received power.

[0091] Next, in step ST1203, the cell with the best RS reception quality (for example, the cell with the highest RS reception power, ie, the best cell) is selected from one or more cells detected up to step ST1202.

[0092] Next, in step ST1204, the PBCH of the best cell is received to obtain the BCCH, which is broadcast information. The BCCH on the PBCH carries a MIB (Master Information Block), which includes cell configuration information. Therefore, the MIB can be obtained by receiving the PBCH and obtaining the BCCH. Examples of MIB information include the DL (downlink) system bandwidth (also called transmission bandwidth configuration: dl-bandwidth), the number of transmitting antennas, and the SFN (System Frame Number).

[0093] Next, in step ST1205, the DL-SCH of the cell is received based on the cell configuration information in the MIB, and SIB (System Information Block) 1 is obtained from the broadcast information BCCH. SIB 1 includes information on access to the cell, information on cell selection, and scheduling information for other SIBs (SIBk; k is an integer greater than or equal to 2). SIB 1 also includes a TAC (Tracking Area Code).

[0094] Next, in step ST1206, the mobile terminal compares the TAC of the SIB1 received in step ST1205 with the TAC in the TA (Tracking Area) list that the mobile terminal already holds. If the comparison shows that the TAC received in step ST1205 is the same as the TAC included in the TA list, the mobile terminal enters standby mode in that cell. If the comparison shows that the TAC received in step ST1205 is not included in the TA list, the mobile terminal requests a change of TA to perform a Tracking Area Update (TAU) to the core network (EPC) (including MME, etc.) through that cell. The core network updates the TA list based on the identification number (UE-ID, etc.) of the mobile terminal that is sent from the mobile terminal together with the TAU request signal. The core network transmits the updated TA list to the mobile terminal. The mobile terminal rewrites (updates) the TAC list that the mobile terminal holds with the received TA list. Thereafter, the mobile terminal enters standby mode in that cell.

[0095] The introduction of Closed Subscriber Group (CSG) cells is being considered for LTE and Universal Mobile Telecommunication System (UMTS). As mentioned above, only one or more mobile terminals registered with a CSG cell are allowed to access it. A CSG cell and one or more registered mobile terminals constitute one CSG. A CSG configured in this way is assigned a unique identification number called a CSG-ID. Note that one CSG may have multiple CSG cells. Once a mobile terminal registers with one CSG cell, it can access other CSG cells in the CSG to which that CSG cell belongs.

[0096] Furthermore, a Home-eNB in ​​LTE or a Home-NB in ​​UMTS may be used as a CSG cell. A mobile terminal registered in a CSG cell has a whitelist. Specifically, the whitelist is stored in a SIM (Subscriber Identity Module) / USIM. The whitelist stores CSG information of the CSG cell in which the mobile terminal has registered. Specific examples of CSG information include a CSG-ID, a Tracking Area Identity (TAI), and a TAC. As long as the CSG-ID and the TAC are associated with each other, either one of them may be used. Furthermore, as long as the CSG-ID and the TAC are associated with a Global Cell Identity (GCI), the GCI may also be used.

[0097] From the above, a mobile terminal that does not have a whitelist (in the present invention, this also includes the case where the whitelist is empty) cannot access a CSG cell and can only access non-CSG cells. On the other hand, a mobile terminal that has a whitelist can access both a CSG cell with a registered CSG-ID and a non-CSG cell.

[0098] In 3GPP, there is discussion about dividing all PCIs (Physical Cell Identities) into those for CSG cells and those for non-CSG cells (referred to as PCI split) (see Non-Patent Document 5). There is also discussion about PCI split information being broadcast from a base station to mobile terminals under its control in system information. Non-Patent Document 5 discloses the basic operation of a mobile terminal using PCI split. A mobile terminal that does not have PCI split information needs to perform a cell search using all PCIs (for example, using all 504 codes). In contrast, a mobile terminal that has PCI split information can perform a cell search using the PCI split information.

[0099] Also, 3GPP has decided that the PCI for hybrid cells is not included in the PCI range for CSG cells (see Chapter 10.7 of Non-Patent Document 1).

[0100] 3GPP specifies two modes for a mobile terminal to select or reselect a CSG cell. The first is automatic mode. The automatic mode has the following features: Selection or reselection is performed using an allowed CSG ID list in the mobile terminal. After selecting a PLMN, the mobile terminal camps on a cell in the selected PLMN only if it is a non-CSG cell or a CSG cell with a CSG ID that is included in the allowed CSG list. If the allowed CSG list of the mobile terminal is empty, the mobile terminal stops its autonomous search function for CSG cells (see Chapter 5.2.4.8.1 of non-patent document 3).

[0101] The second mode is manual mode. The features of manual mode are as follows: The mobile terminal presents the user with a list of CSGs available in the currently selected PLMN. The list of CSGs that the mobile terminal provides to the user is not limited to the CSGs included in the allowed CSG list stored in the mobile terminal. After the user selects a CSG based on the CSG list, the mobile terminal camps on a cell with the selected CSG ID and attempts to register (see Chapter 5.2.4.8.1 of Non-Patent Document 3).

[0102] HeNBs and HNBs are required to support a variety of services. For example, operators allow mobile terminals to register with certain HeNBs and HNBs and permit only registered mobile terminals to access HeNB and HNB cells, thereby increasing the radio resources available to the mobile terminals and enabling high-speed communication. To compensate for this, operators charge higher fees than usual.

[0103] To realize such services, CSG cells (Closed Subscriber Group cells) have been introduced, which can only be accessed by registered (subscribed, member) mobile terminals. It is required that many CSG cells (Closed Subscriber Group cells) be installed in shopping malls, apartment buildings, schools, companies, etc. For example, a CSG cell is installed for each store in a shopping mall, for each room in an apartment building, for each classroom in a school, and for each section in a company, and a usage method is required in which only users registered in each CSG cell can use the CSG cell. HeNBs / HNBs are required not only to complement communications outside the coverage of a macrocell, but also to support the various services mentioned above. For this reason, there are cases in which HeNBs / HNBs are installed within the coverage of a macrocell.

[0104] MTC technology is being studied in 3GPP (see Non-Patent Document 8). Unlike conventional human-to-human (H2H) communication, MTC is machine-to-machine (M2M) communication. In other words, it does not require human interaction, i.e., human-to-human interaction. Application examples of services using MTC technology (hereinafter referred to as "MTC services") include metering for gas, electricity, water, etc., as well as transportation management and order management (Tracking & Tracing). One characteristic of MTC services is the enormous number of MTC devices (MTC Devices: MTCDs). As an example, it is expected that more than 30,000 MTCDs will be present under one cell.

[0105] The 3GPP is studying the architecture of MTC (see 3GPP R3-100315 (hereinafter referred to as "Non-Patent Document 10")). FIG. 13 is a diagram showing an example of the architecture of MTC studied by the 3GPP. Support for MTC services is being studied not only for LTE communication systems but also for WCDMA (registered trademark) communication systems.

[0106] In Fig. 13, MTCDs 1301 to 1304 and an NB / eNB 1305 are connected via interfaces Uu 1311 to 1314. An SGSN / MME (Serving GPRS Support Node / Mobility Management Entity) 1306 is connected to the NB / eNB 1305 via an IuPS / S1 interface 1315. Although not shown, a radio network controller (RNC) exists between the NB and the SGSN. The NB and RNC are connected via an Iub interface, and the RNC is connected to the SGSN via an IuPS interface.

[0107] The HLR / HSS (Home Location Register / Home Subscriber Server) 1307 is connected to the SGSN / MME 1306 via a Gr / S6a interface 1316. The communication operator domain 1317 includes the NB / eNB 1305, the SGSN / MME 1306, and the HLR / HSS 1307.

[0108] The MTC server 1308 is included in a communication operator domain 1317. An MTC user 1309 that provides MTC services is connected to the MTC server 1308 via an application program interface (API) 1310. The node to which the MTC server 1308 should be connected in the communication operator domain 1317 is currently under consideration in 3GPP.

[0109] Information for the MTC service is notified to the MTCDs 1301 to 1304 by the MTC user 1309 from the MTC server 1308 using the NB / eNB 1305, SGSN / MME 1306, and HLR / HSS 1307, which are nodes in the communication operator area 1317. Conversely, information from the MTCDs 1301 to 1304 is notified to the MTC server 1308 using the NB / eNB 1305, SGSN / MME 1306, and HLR / HSS 1307, which are nodes in the communication operator area 1317, and the information is used by the MTC user 1309.

[0110] In the MTC service, situations arise where data is transmitted simultaneously from or to multiple MTCDs. For example, such situations arise when an MTCD transmits meter reading data to an MTC server once a day at 1:00 AM, or when an MTC server requests an MTCD to transmit meter reading data. Another example is when software upgrade data is transmitted simultaneously to all MTCDs.

[0111] Conventional communication methods are optimized for H2H communication, so they do not address situations where multiple MTCDs communicate data simultaneously. When multiple MTCDs communicate data simultaneously, or to multiple MTCDs, congestion occurs in the radio network and core network. In other words, these networks become overloaded.

[0112] For example, when the MTC server requests that meter reading data be transmitted to a large number of MTCDs simultaneously, a large amount of data is transmitted from the MTCDs 1301 to 1304 to the MTC server 1308 using the NB / eNB 1305, SGSN / MME 1306, and HLR / HSS 1307, which are nodes in the communication operator area 1317. In such a situation, an overload state occurs in the communication between the NB / eNB 1305 and the SGSN / MME 1306. This causes problems such as a shortage of communication resources or an overload state in the processing of the NB / eNB 1305 and SGSN / MME 1306.

[0113] To address the issue of congestion in the core network, the aforementioned Non-Patent Document 9 discloses the following solution. It describes that an eNB holds back and aggregates signaling messages common to MTCDs in the same group, thereby compacting the signaling messages. Specifically, it describes a method in which an eNB holds back non-access stratum (NAS) signaling messages from an MTCD for a predetermined time or until many NAS signaling messages arrive. However, Non-Patent Document 9 does not suggest or disclose a solution to the issue when many MTCD groups exist under an eNB. It also does not disclose a method in which an eNB holds back and aggregates signaling messages from MTCDs and then transmits them to the core network.

[0114] To address the issue of congestion occurring in the core network, 3GPP S2-101008 (hereinafter referred to as "Non-Patent Document 11") discloses the following solution. It describes that MTCDs in the same MTCD group share one network resource for UEs that are not MTCDs. However, Non-Patent Document 11 does not suggest the issue when many MTCD groups exist under an eNB, nor does it disclose a solution. Non-Patent Document 11 also discloses mapping an International Mobile Subscriber Identity (IMSI) as a source address, an MTCD number, and a cell number in a message from an MTCD to an MTC server. However, it does not disclose a method for MTCDs in the same MTCD group to share one network resource.

[0115] 3GPP R2-103269 (hereinafter referred to as "Non-Patent Document 12") describes a problem that when an MTCD is installed underground, for example, the channel quality between each MTCD and the eNB is poor and direct communication is inappropriate. To address this problem, Non-Patent Document 12 discloses installing a concentrator between the eNB and the MTCD, separate from the eNB. However, Non-Patent Document 12 does not disclose a method of transmitting from the concentrator to the eNB.

[0116] The problem to be solved in the first embodiment will be described below. When many MTCD groups exist under the umbrella of an eNB, the method disclosed in the above-mentioned Non-Patent Document 9, that is, the method in which the eNB holds back and collects signaling messages common to MTCDs in the same MTCD group, cannot reduce the number of signaling messages. The first embodiment discloses a communication system that can alleviate congestion in the core network when a situation arises in which data is communicated from a large number of MTCDs, even when many MTCD groups exist under the umbrella of an eNB. The communication system of this embodiment is a mobile communication system. An MTCD group corresponds to a group of terminal devices.

[0117] The solution in the first embodiment is as follows. The HeNB performs a concentration process to concentrate data from an MTCD under its control to an MME, an SGSN, an MTC server, or the like, which is a core network. The HeNB concentrates data from an MTCD under its control to an MME, an SGSN, an MTC server, or the like, which is a core network, without directly transmitting the data, relaying the data, or passing through the data. This makes it possible to perform concentration process even when there are many MTCDs belonging to different MTCD groups under the control of the HeNB. Therefore, it is possible to alleviate congestion in the core network even in a situation where there are many MTCDs belonging to different MTCD groups under the control of the HeNB.

[0118] Furthermore, when a HeNB operates in a closed access mode or a hybrid access mode, it may be configured to concentrate data from MTCDs belonging to the same CSG to the core network. This allows the HeNB to process only data from MTCDs that are registered in the same CSG as the HeNB among the MTCDs under its control, and the processing is in line with the purpose of the closed access mode, which is to operate as a cell that can only be accessed by CSG members.

[0119] Furthermore, when a HeNB operates in the hybrid access mode, the open access mode may be used by mobile terminals other than the MTCD, and the closed access mode may be used by the MTCD. The MTCD may be permitted to access only HeNBs in the same CSG. In this case, the HeNB may concentrate data from communication terminals accessing in the closed access mode to the core network.

[0120] The processing performed by the HeNB can be performed by the eNB to obtain the same effect. For convenience, the following description will be centered on the HeNB.

[0121] As specific examples of a communication method between a HeNB and an MTCD, the following two (1) and (2) are disclosed. (1) A communication method for a mobile communication system standardized by 3GPP. (2) A communication method other than a mobile communication system standardized by 3GPP.

[0122] As specific examples of communication methods other than the mobile communication system standardized by 3GPP, the following five (1) to (5) are disclosed: (1) infrared communication; (2) coaxial cable communication; (3) optical fiber communication; (4) Bluetooth (registered trademark) communication; and (5) ZigBee (registered trademark) communication.

[0123] Specific examples of data from an MTCD to a core network that is the subject of concentration processing in a HeNB are disclosed below. First, the following two (1) and (2) are disclosed as specific examples of the content of data that is the subject of concentration processing. (1) Control data. (2) User data. Next, the following two (1) and (2) are disclosed as specific examples of signaling that is the subject of concentration processing. (1) NAS signaling or NAS messages. (2) RRC signaling or RRC messages.

[0124] The following three methods (1) to (3) are disclosed as specific examples of a method in which a HeNB distinguishes whether a user equipment (UE) being served by the HeNB is an MTCD or other than an MTCD. In the following description, a user equipment (UE) other than an MTCD may also be referred to as a "normal UE."

[0125] (1) Separate systems are used for identifiers used by MTCD and normal UE. For example, a new MTCD-ID is created in addition to the current UE-ID. The current UE-ID may be used as an identifier for normal UE, and the MTCD-ID may be used as an identifier for MTCD.

[0126] (2) A new indicator for distinguishing whether a UE is MTCD or not (hereinafter also referred to as "MTCD indicator") is established. As specific examples of the MTCD indicator, the following seven indicators (a) to (g) are disclosed. (a) An indicator indicating whether a UE is an MTCD or a normal UE. (b) An indicator indicating whether a UE is an MTCD. If an indicator indicating that a UE is not an MTCD is included, HeNB determines that the UE is a normal UE. (c) An indicator indicating whether a UE is a normal UE. If an indicator indicating that a UE is not a normal UE is included, HeNB determines that the UE is an MTCD. (d) An indicator indicating that a UE is an MTCD. If an indicator indicating that a UE is not an MTCD is not included, HeNB determines that the UE is a normal UE. (e) An indicator indicating that a UE is not MTCD. If an indicator indicating that a UE is not an MTCD is not included, HeNB determines that the UE is an MTCD. (f) An indicator indicating that a UE is a normal UE. If an indicator indicating that a UE is a normal UE is not included, HeNB determines that the UE is an MTCD. (g) An indicator indicating that a UE is not a normal UE. If the UE does not include an indicator indicating that the UE is not a normal UE, the HeNB determines that the UE is a normal UE.

[0127] (3) Determine whether the access is made by a communication method other than the mobile communication system standardized by 3GPP. A mobile terminal that has accessed by a communication method other than the mobile communication system standardized by 3GPP is determined to be an MTCD.

[0128] Among the specific examples of the method by which a HeNB distinguishes whether a mobile terminal (UE) served by the HeNB is an MTCD or not an MTCD, specific example (1), specific example (2)-(d), specific example (2)-(g), and specific example (3) do not require newly added parameters or processes if the current UE is a normal UE. Therefore, by using specific example (1), specific example (2)-(d), specific example (2)-(g), or specific example (3), the problem can be solved without changing the specifications of the current UE.

[0129] The following two (1) and (2) are disclosed as specific examples of a method for notifying a HeNB of whether a UE is an MTCD or a non-MTCD. (1) An RRC message or RRC signaling is used to notify a HeNB of whether the UE is an MTCD or a non-MTCD. The above-mentioned separate identifier system is used in the RRC message or RRC signaling. In addition, an MTCD indicator is mapped to the RRC message or RRC signaling. A specific example of RRC signaling is an "RRC Connection Request" (see Non-Patent Document 2). Compared to specific example (2) described later, this specific example (1) enables a HeNB to determine whether the UE is an MTCD before receiving data to a core network that is the target of concentration processing. Therefore, it is possible to prevent control delays in concentration processing at the HeNB.

[0130] (2) Using data to the core network that performs line concentration processing, the HeNB is notified of whether the UE is an MTCD or other than an MTCD. The separate identifier is used for the data to the core network. An MTCD indicator is also mapped to the data to the core network. Here, the separate identifier may be used in the header / footer of the core network data. The MTCD indicator may also be mapped to the header / footer of the core network data. If it becomes possible to distinguish whether the UE is an MTCD or other than an MTCD using the header / footer of the core network data, the HeNB does not need to constantly interpret the contents of messages from the MTCD to the core network. This reduces the processing load on the HeNB.

[0131] As specific examples of line concentration processing, the following four (1) to (4) are disclosed. (1) NAS signaling or NAS messages are terminated and separately notified to the MME. At this time, unnecessary data may be reduced and notified to the MME. This reduces the amount of communication from the HeNB to the core network and alleviates congestion in the core network. (2) NAS signaling or NAS messages are interpreted and separately notified to the MME. At this time, unnecessary data may be reduced and notified to the MME. This reduces the amount of communication from the HeNB to the core network and alleviates congestion in the core network. (3) Data to the core network from one or multiple MTCDs is collectively notified to the MME. This reduces the number of communications from the HeNB to the core network and alleviates congestion in the core network. (4) A combination of the above (1) to (3).

[0132] The concept of a HeNB terminating NAS signaling will be described with reference to Fig. 14 and Fig. 15. First, a protocol stack for control data between a UE and an MME in the conventional technology will be described with reference to Fig. 14. Fig. 14 is a diagram showing a protocol stack for control data between a UE and an MME in the conventional technology. The interface between a UE and an HeNB is defined as LTE-Uu 1401 (see Non-Patent Document 1, 3GPP TS23.401 V10.0.0 (hereinafter referred to as "Non-Patent Document 13")). The interface between a HeNB and an MME is defined as S1-MME 1402 (see Non-Patent Document 13).

[0133] The UE, HeNB, and MME have Layer 1 (L1) protocols 1403-1, 1403-2, 1403-3, and 1403-4. The UE and HeNB have Medium Access Control (MAC) protocols 1404-1 and 1404-2. The HeNB and MME have Layer 2 (L2) protocols 1405-1 and 1405-2. The UE and HeNB have Radio Link Control (RLC) protocols 1406-1 and 1406-2. The HeNB and MME have Internet Protocol (IP) protocols 1407-1 and 1407-2. The UE and HeNB have Packet Data Convergence Protocol (PDCP) protocols 1408-1 and 1408-2. The HeNB and MME have Stream Control Transport Protocol for the control plane (SCTP) protocols 1409-1 and 1409-2. The UE and HeNB have RRC (Radio Resource Control) protocols 1410-1 and 1410-2. The HeNB and MME have S1-AP (S1 Application Protocol) 1411-1 and 1411-2.

[0134] Relay 1412 is performed in each protocol layer within the HeNB. NAS (Non-Access Stratum) protocols 1413-1 and 1413-2 exist in the UE and MME. The NAS protocols support mobility management functions and the activation, modification, and deactivation of user plane bearers.

[0135] Next, a protocol stack of control data between the MTCD and MME in the first embodiment will be described with reference to Fig. 15. Fig. 15 is a diagram showing a protocol stack of control data between the MTCD and MME in the first embodiment. In Fig. 15, parts corresponding to the protocol layers shown in Fig. 14 are given the same reference numerals, and common descriptions will be omitted.

[0136] The interface between the MTCD and the HeNB is defined as LTE-Uu 1401. The MTCD has a layer 1 (L1) protocol 1403-1, a MAC protocol 1404-1, an RLC protocol 1406-1, a PDCP 1408-1, an RRC protocol 1410-1, and an MTC NAS protocol 1501-1. Here, although the MTC NAS protocol does not reach the MME, the term "NAS" is used for convenience.

[0137] The HeNB contains a layer 1 (L1) protocol 1403-2, a MAC protocol 1404-2, an RLC protocol 1406-2, a PDCP 1408-2, an RRC protocol 1410-2, and an MTC NAS protocol 1501-2. The presence of the MTC NAS protocol 1501-2 in the HeNB enables the HeNB to perform the above-mentioned line concentration 1504. Relay 1412 is performed in each protocol layer in the HeNB. S1-APs 1502-1, 1502-2, and 1502-3 exist in the HeNB and MME. In FIG. 15, the S1-AP in the HeNB is depicted as being separated into S1-AP 1502-1 and S1-AP 1502-3, but there may be only one S1-AP in the HeNB. The MME contains a normal UE NAS protocol 1503.

[0138] The protocol stack for control data between normal UE and MME in the first embodiment is the same as that in the conventional technology, and therefore description thereof will be omitted (see FIG. 14). However, the MME has a NAS protocol 1503 for normal UE (see FIG. 15).

[0139] Next, a specific example of operation using the first embodiment will be described with reference to Fig. 16 and Fig. 17. In this example of operation, a case of NAS signaling will be disclosed as a specific example of data from an MTCD to a core network, which is a target of concentration processing in a HeNB. Also, as a specific example of a method in which a HeNB distinguishes whether a mobile terminal (UE) being served by the HeNB is an MTCD or a non-MTCD, a case in which an MTCD indicator is mapped to an RRC message "RRC Connection Request" will be disclosed. Also, as a specific example of concentration processing, a case in which data from one or more MTCDs to the core network is collectively notified to an MME will be disclosed.

[0140] First, a specific example of concentration processing by the HeNB according to the first embodiment will be described with reference to Fig. 16. Fig. 16 is a flowchart showing a processing procedure of the HeNB regarding concentration processing according to the first embodiment.

[0141] In Step ST1601, the HeNB determines whether or not it has received an RRC message "RRC Connection Request" from the UE. If the HeNB determines that it has received an RRC message from the UE, it proceeds to Step ST1602. If the HeNB determines that it has not received an RRC message from the UE, it repeats the determination processing of Step ST1601.

[0142] In Step ST1602, the HeNB checks the MTCD indicator mapped to the RRC message received in Step ST1601, and then proceeds to Step ST1603.

[0143] In Step ST1603, the HeNB determines whether or not it has received an RRC message from the MTCD, that is, whether or not the UE that transmitted the RRC message received in Step ST1601 is an MTCD, based on the MTCD indicator confirmed in Step ST1602. If the HeNB has received an RRC message from the MTCD, that is, if it has determined that the UE that transmitted the RRC message is an MTCD, it moves to Step ST1604. If the HeNB has not received an RRC message from the MTCD, that is, if it has determined that the UE that transmitted the RRC message is not an MTCD, it moves to Step ST1605.

[0144] In Step ST1604, the HeNB concentrates data from the MTCD to the core network. After completing the process of Step ST1604, the HeNB terminates all processing procedures. In Step ST1605, the HeNB does not concentrate data from the UE to the core network. That is, data is transmitted from the UE to the core network via the HeNB. After completing the process of Step ST1605, the HeNB terminates all processing procedures.

[0145] Next, a specific example of a sequence of the mobile communication system according to the first embodiment will be described with reference to Fig. 17. Fig. 17 is a diagram showing the sequence of the mobile communication system according to the first embodiment. Assume that m normal UEs and n MTCDs are present under an HeNB. Here, m and n are natural numbers. The m normal UEs are represented as normal UE_1 to normal UE_m, and the n MTCDs are represented as MTCD_1 to MTCD_n.

[0146] In Step ST1701, normal UE_1 transmits "RRC Connection Request", which is an RRC message including an MTCD indicator, to HeNB. In Step ST1702, normal UE_m transmits "RRC Connection Request", which is an RRC message including an MTCD indicator, to HeNB. In this manner, in the present embodiment, it is assumed that, of normal UE_1 to normal UE_m, normal UE_1 and normal UE_m transmit "RRC Connection Request", which is an RRC message including an MTCD indicator, to HeNB, assuming that data to be transmitted to the core network has occurred.

[0147] In Step ST1703, MTCD_1 transmits "RRC Connection Request", which is an RRC message including an MTCD indicator, to HeNB. In Step ST1704, MTCD_n transmits "RRC Connection Request", which is an RRC message including an MTCD indicator, to HeNB. In this manner, in the present embodiment, it is assumed that, of MTCD_1 to MTCD_n, MTCD_1 and MTCD_n transmit "RRC Connection Request", which is an RRC message including an MTCD indicator, to HeNB, assuming that data to be transmitted to the core network has occurred.

[0148] In Step ST1705, the HeNB checks the MTCD indicator included in the received "RRC Connection Request" and determines whether or not the RRC message is data from the MTCD. If the HeNB determines that the data is from the MTCD, it moves to Step ST1707. If the HeNB determines that the data is not from the MTCD, it moves to Step ST1706.

[0149] In this operation example, step ST1701 is a process of transmitting an RRC message from normal UE_1, so in step ST1705 it is determined that the data is not from an MTCD, and the process proceeds to step ST1706. Also, step ST1702 is a process of transmitting an RRC message from normal UE_m, so in step ST1705 it is determined that the data is not from an MTCD, and the process proceeds to step ST1706. Also, step ST1703 is a process of transmitting an RRC message from MTCD_1, so in step ST1705 it is determined that the data is from an MTCD, and the process proceeds to step ST1707. Also, step ST1704 is a process of transmitting an RRC message from MTCD_n, so in step ST1705 it is determined that the data is from an MTCD, and the process proceeds to step ST1707.

[0150] In Step ST1706, the HeNB is configured not to concentrate data from normal UEs, which are mobile terminals (UEs) other than the MTCDs being served by the HeNB, to the core network. In this operation example, the HeNB is configured not to concentrate NAS signaling from UEs other than the MTCDs being served by the HeNB, specifically, not to concentrate NAS signaling from normal UEs to the core network.

[0151] In Step ST1707, the HeNB is configured to concentrate data from an MTCD being served by the HeNB to the core network. In this operation example, the HeNB is configured to concentrate NAS signaling from an MTCD among UEs being served by the HeNB, specifically, to concentrate NAS signaling from the MTCD to the core network.

[0152] In Step ST1708, normal UE_1 transmits NAS signaling, which is data to the core network, to MME via HeNB. Since HeNB is set not to perform concentration processing of NAS signaling from normal UE_1 in Step ST1706, the NAS signaling transmitted from normal UE_1 is notified to MME via HeNB as is.

[0153] In Step ST1709, normal UE_m transmits NAS signaling, which is data to the core network, to MME via HeNB. In Step ST1706, HeNB is configured not to perform concentration processing of NAS signaling from normal UE_m, and therefore, the NAS signaling transmitted from normal UE_m is notified to MME via HeNB as is. Similarly, when NAS signaling is transmitted from another normal UE to MME via HeNB, the NAS signaling transmitted from the other normal UE is notified to MME as is via HeNB.

[0154] In Step ST1710, the MTCD_1 transmits, to the MME, NAS signaling, which is data to be transmitted to the core network. Since the HeNB is configured to perform concentrating processing of the NAS signaling from the MTCD_1 in Step ST1707, the HeNB performs concentrating processing of the NAS signaling transmitted from the MTCD_1 in Step ST1712. Furthermore, in Step ST1712 or Step ST1707, the HeNB may omit the processing (see Non-Patent Document 2) that is performed when the HeNB receives a normal "RRC Connection Request". Furthermore, in Step ST1712, the HeNB may notify the MTCD that transmitted the "RRC Connection Request" of "RRC Connection reject". Furthermore, the HeNB may map information indicating that data from the MTCD to the core network has been received into the "RRC Connection reject". Furthermore, the HeNB may map information requesting retransmission of data from the MTCD to the core network into the "RRC Connection reject".

[0155] In Step ST1711, the MTCD_n transmits NAS signaling, which is data to the core network, to the MME. Since the HeNB is configured to perform concentrating processing of the NAS signaling from the MTCD_n in Step ST1707, the NAS signaling transmitted from the MTCD_n is subjected to concentrating processing in Step ST1712. Similarly, when NAS signaling is transmitted from another MTCD to the MME, the NAS signaling transmitted from the other MTCD is subjected to concentrating processing in Step ST1712.

[0156] In Step ST1712, the HeNB performs a process of concentrating NAS signaling, which is data from the MTCDs under its control to the core network. In Step ST1713, the HeNB consolidates the data to the MME, which is data from MTCD_1 and MTCD_n to the core network, and notifies the MME of the collected data.

[0157] The first embodiment can provide the following effects. According to the first embodiment, the HeNB performs concentration processing to concentrate data from MTCDs under its control to the core network. At this time, the concentration processing is performed across MTCD groups. In other words, since the concentration processing is performed regardless of the MTCD group, even if there are many MTCD groups under the HeNB, it is possible to reduce the number of communications from the HeNB to the core network or the amount of data. This makes it possible to obtain a mobile communications system that can alleviate congestion in the core network even if there are many MTCD groups under the HeNB and a situation arises in which data is communicated from a large number of MTCDs.

[0158] Furthermore, even when an MTCD is set in a location with a poor radio environment as a mobile communication system standardized by 3GPP, there is no need to provide a separate entity like the centralized device shown in Non-Patent Document 12, and it becomes possible to communicate with an MTC user and an MTC server using a 3GPP network with the HeNB as the origin. The fact that there is no need to provide a separate entity has the advantage of being able to avoid the mobile communication system becoming complicated.

[0159] First embodiment, variant 1 When the above-described first embodiment is used, the following problem occurs. Performing concentration processing causes a delay in data transmission from the MTCD to the core network compared to when concentration processing is not performed. A specific example of the occurrence of the delay will be described with reference to FIG. 17 above.

[0160] NAS signaling from normal UE_1, which does not perform concentration processing, to the core network is notified to MME directly via HeNB in ​​Step ST1708. On the other hand, NAS signaling from MTCD_1, which performs concentration processing, to the core network is subjected to concentration processing within HeNB in ​​Step ST1712, and then notified to MME separately from HeNB in ​​Step ST1713. In this way, when concentration processing is performed, a control delay occurs within the HeNB.

[0161] Generally, most MTCDs are considered to be tolerant of delays, but some MTCDs are sensitive to delays. A specific example is an MTCD equipped with a function to detect the occurrence of an earthquake. If delays occur when applying the above-described first embodiment to such a delay-sensitive MTCD, this will cause problems in terms of MTCD service.

[0162] The solution in Modification 1 of Embodiment 1 is shown below. The explanation will focus on the parts that differ from the solution in Embodiment 1. Parts that are not explained are the same as in Embodiment 1.

[0163] A HeNB concentrates data from MTCDs under its control that are tolerant of delay to a core network such as an MME, an SGSN, or an MTC server. A HeNB does not concentrate data from MTCDs under its control that are not tolerant of delay to a core network such as an MME, an SGSN, or an MTC server.

[0164] A HeNB concentrates data from an MTCD with a low priority among the MTCDs under its control to a core network such as an MME, an SGSN, or an MTC server. A HeNB does not concentrate data from an MTCD with a high priority among the MTCDs under its control to a core network such as an MME, an SGSN, or an MTC server.

[0165] A specific example of a method in which a HeNB distinguishes whether a mobile terminal (UE) being served by the HeNB is an MTCD with low priority is disclosed below: An indicator representing priority (hereinafter also referred to as a "priority indicator") is newly created.

[0166] As specific examples of priority indicators, the following seven indicators (a) to (g) are disclosed.

[0167] (a) An indicator of high or low priority.

[0168] (b) Indicator indicating whether the priority is low or not If an indicator indicating that the priority is not low is included, the HeNB determines that the MTCD has high priority.

[0169] (c) Indicator indicating whether the priority is high or not. If an indicator indicating that the priority is not high is included, the HeNB determines that the MTCD has low priority.

[0170] (d) Indicator indicating that the MTCD is a low-priority MTCD. If an indicator indicating that the MTCD is a low-priority MTCD is not included, the HeNB determines that the MTCD is a high-priority MTCD.

[0171] (e) Indicator indicating that the MTCD is not a low-priority MTCD. If the indicator indicating that the MTCD is not a low-priority MTCD is not included, the HeNB determines that the MTCD is a low-priority MTCD.

[0172] (f) Indicator indicating that the MTCD is a high-priority MTCD. If the indicator indicating that the MTCD is a high-priority MTCD is not included, the HeNB determines that the MTCD is a low-priority MTCD.

[0173] (g) Indicator indicating that the MTCD is not a high-priority MTCD. If an indicator indicating that the MTCD is not a high-priority MTCD is not included, the HeNB determines that the MTCD is a high-priority MTCD.

[0174] Here, the priority is described as "low" or "high," but the priority indicator does not need to be binary. There may be multiple priorities. The priority indicator may be represented by, for example, an integer. As a specific example, assume that the priority indicator is represented as "0," "1," "2," or "3," with larger numbers indicating higher priorities. In this specific example, an MTCD with a priority indicator of "0" or "1" is considered to be tolerant of control delays due to concentration processing, and the HeNB concentrates data from the MTCD to the core network. In contrast, an MTCD with a priority indicator of "2" or "3" is considered to be sensitive to control delays due to concentration processing, and the HeNB does not concentrate data from the MTCD to the core network.

[0175] The following two methods (1) and (2) are disclosed as specific examples of a method for notifying a HeNB of whether an MTCD is a low-priority MTCD.

[0176] (1) Using an RRC message or RRC signaling, an MTCD is notified to the HeNB of whether it is a low-priority MTCD or a high-priority MTCD. Furthermore, a priority indicator is mapped to the RRC message or RRC signaling. A specific example of RRC signaling is an "RRC Connection Request" (see Non-Patent Document 2). Compared to specific example (2) described later, this specific example (1) enables the HeNB to determine whether it is an MTCD before receiving data to the core network that is the target of the line concentration process. Therefore, it is possible to prevent control delays in the line concentration process at the HeNB.

[0177] (2) Using data to the core network that performs line concentration processing, the HeNB is notified of whether the MTCD is a low-priority MTCD or a high-priority MTCD. Furthermore, a priority indicator is mapped to data to the core network (hereinafter sometimes referred to as "core network data"). Furthermore, the priority indicator may be mapped to the header or footer of the core network data. If it becomes possible to distinguish whether the UE is an MTCD or a non-MTCD using the header or footer of the core network data, the HeNB does not need to constantly interpret the contents of messages from the MTCD to the core network. This can reduce the processing load on the HeNB.

[0178] Next, a specific example of operation using the first modification of the first embodiment will be described with reference to Fig. 18. Fig. 18 is a flowchart showing a processing procedure of a HeNB related to line concentration processing in the first modification of the first embodiment. In Fig. 18, steps corresponding to those shown in Fig. 16 are given the same reference numerals, and common descriptions will be omitted.

[0179] In this operation example, a case of NAS signaling is disclosed as a specific example of data from an MTCD to a core network, which is a target of concentration processing in a HeNB. Also, as a specific example of a method in which a HeNB distinguishes whether a mobile terminal (UE) being served by the HeNB is an MTCD or a non-MTCD, a case in which an MTCD indicator is mapped to an RRC message "RRC Connection Request" is disclosed. Also, as a specific example of a method in which a HeNB distinguishes whether an MTCD being served by the HeNB is an MTCD with a low priority or an MTCD with a high priority, a case in which a priority indicator is mapped to an RRC message "RRC Connection Request" is disclosed.

[0180] The HeNB sequentially performs the processes of Steps ST1601 to ST1603 described above. In this modification, if the HeNB determines in Step ST1603 that the UE is an MTCD, it moves to Step ST1801, and if it determines that the UE is not an MTCD, it moves to Step ST1605.

[0181] In Step ST1801, the HeNB checks the priority indicator mapped to the RRC message, and then proceeds to Step ST1802.

[0182] In Step ST1802, the HeNB determines whether or not it has received an RRC message from an MTCD with a low priority, that is, whether or not the MTCD that transmitted the RRC message received in Step ST1601 is an MTCD with a low priority, based on the priority indicator confirmed in Step ST1801. If the HeNB has received an RRC message from an MTCD with a low priority, that is, if it has determined that the MTCD is an MTCD with a low priority, it moves to Step ST1604 and performs the above-mentioned processing. If the HeNB has not received an RRC message from an MTCD with a low priority, that is, if it has determined that the MTCD is not an MTCD with a low priority, it moves to Step ST1605 and performs the above-mentioned processing.

[0183] A specific example of the sequence of the mobile communication system in variant example 1 of embodiment 1 is the same as the sequence of the mobile communication system in embodiment 1 shown in Figure 17, except that steps ST1801 and ST1802 shown in Figure 18 are provided between steps ST1705 and ST1706 shown in Figure 17, so illustration and explanation will be omitted.

[0184] In addition to the effects of Embodiment 1, Modification 1 of Embodiment 1 can provide the following effects. For an MTCD that is tolerant of delay, by executing the same process as in Embodiment 1, it is possible to alleviate congestion in the core network, similarly to Embodiment 1. Furthermore, for an MTCD that is sensitive to delay occurrence, it is possible to prevent the HeNB from performing concentration processing, and therefore it is possible to prevent the MTCD from being affected by control delays due to concentration processing.

[0185] Embodiment 1 Variation 2 In the second modification of the first embodiment, the start and end times of the first embodiment will be disclosed.

[0186] The solution in the second modification of the first embodiment is shown below. The explanation will focus on the parts that differ from the solution in the first embodiment. The parts that are not explained are the same as those in the first embodiment.

[0187] The execution of the process of the first embodiment is started in response to an instruction from the core network, such as the MME or SGSN, and the execution of the process of the first embodiment is stopped in response to an instruction from the core network, such as the MME or SGSN.

[0188] The following three (1) to (3) are disclosed as specific examples of triggers that cause the MME, SGSN, etc., which are core networks, to instruct the HeNB to start (hereinafter also referred to as "concentration ON") the process of embodiment 1 (hereinafter also referred to as "concentration process"): (1) When an entity, i.e., a component, such as the MME or SGSN, which are core networks, becomes overloaded. (2) When the processing load of the MME, SGSN, etc., which are core networks, exceeds a threshold. This may also be when the MTCD-related processing load of the MME, SGSN, etc., which are core networks, exceeds a threshold. (3) When the communication volume exceeds a threshold. This may also be when the MTCD-related communication volume exceeds a threshold. The communication volume may be the communication volume between the MME and the HeNB. It may also be the communication volume between the SGSN and the HeNB.

[0189] The following three (1) to (3) are disclosed as specific examples of triggers for the core network to instruct the stopping of concentration processing (hereinafter also referred to as "concentration OFF"). (1) When an entity such as an MME or SGSN, which is a core network, is no longer overloaded. (2) When the processing load of an MME, SGSN, etc., which is a core network, falls below a threshold. This may also be when the MTCD-related processing load of an MME, SGSN, etc., which is a core network, falls below a threshold. (3) When the communication volume falls below a threshold. This may also be when the MTCD-related communication volume falls below a threshold. The communication volume may be the communication volume between an MME and a HeNB. It may also be the communication volume between an SGSN and a HeNB.

[0190] A specific example of a protocol used by core networks such as MME and SGSN to instruct HeNBs to turn line concentration on or off is S1-AP.

[0191] The following four (1) to (4) are disclosed as specific examples of signaling used by a core network such as an MME or SGSN to instruct a HeNB to turn on concentration: (1) Create new signaling indicating concentration on, or initiation, or start. (2) Create new signaling indicating termination on, or initiation, or start of a NAS message. (3) Create new signaling indicating interpretation on, or initiation, or start of a NAS message. (4) Use existing S1-AP signaling, "Overload Start" (see 3GPP TS36.413 V9.3.0 (hereinafter referred to as "Non-Patent Document 14")).

[0192] In the current standard, an eNB that receives "Overload Start" from an MME performs processing such as rejecting an RRC connection from a mobile terminal under its control. In contrast, in Modification 2 of the first embodiment, an eNB that receives "Overload Start" from an MME performs line concentration processing for an MTCD under its control.

[0193] Compared with concrete examples (1) to (3), concrete example (4) has the advantage of being able to avoid complicating the mobile communication system in that it does not require the provision of new signaling. Furthermore, the current "Overload Start" standard denies access itself from mobile terminals served by eNBs. In contrast, concrete example (4) concentrates data from MTCDs, which are UEs other than normal UEs, thereby reducing the number of communications or the amount of communication, thereby alleviating the overload state on the core network side. Data from normal UEs may be transmitted to the core network side as usual. This prevents access itself from being denied from mobile terminals served by eNBs. Therefore, a user-friendly mobile communication system can be constructed.

[0194] The following four (1) to (4) are disclosed as specific examples of signaling that a core network such as an MME or SGSN can use to instruct a HeNB to turn off concentration: (1) Create new signaling to indicate concentration OFF, or stop, or stop. (2) Create new signaling to indicate NAS message termination OFF, or stop, or stop. (3) Create new signaling to indicate NAS message interpretation OFF, or stop, or stop. (4) Use existing S1-AP signaling, "Overload stop" (see Non-Patent Document 14).

[0195] In the current standard, an eNB that receives "Overload stop" from an MME starts normal operation on the MME. In contrast, in Modification 2 of the first embodiment, an eNB that receives "Overload stop" from the MME stops concentration processing for MTCDs served by the eNB.

[0196] Compared with the specific examples (1) to (3), the specific example (4) has the advantage that it is possible to avoid the mobile communication system from becoming complicated in that it is not necessary to provide new signaling. Furthermore, when the overload state of the MME is resolved, it is possible to stop the concentration process that may cause delays for data from MTCDs, which are UEs other than normal UEs. Therefore, it is possible to build a user-friendly mobile communication system.

[0197] Next, a specific operation example using the second modification of the first embodiment will be described with reference to Fig. 19. Fig. 19 is a diagram showing a sequence of a mobile communication system in the second modification of the first embodiment. It is assumed that MTCD_1 to MTCD_n exist under the control of a HeNB.

[0198] In this operation example, a case where communication volume exceeds a threshold is disclosed as a specific example of a trigger when a core network such as an MME or SGSN instructs a HeNB to start concentration processing. Also, a case where communication volume falls below a threshold is disclosed as a specific example of a trigger when a core network such as an MME or SGSN instructs a HeNB to stop concentration processing. Also, a case where a core network such as an MME or SGSN newly establishes signaling indicating concentration ON as a specific example of signaling when a core network such as an MME or SGSN instructs a HeNB to turn concentration ON. Also, a case where a core network such as an MME or SGSN newly establishes signaling indicating concentration OFF as a specific example of signaling when a core network such as an MME or SGSN instructs a HeNB to turn concentration OFF is disclosed.

[0199] In Step ST1901, the MME determines whether or not the amount of communication between the MME and the HeNB is equal to or greater than a threshold. If the MME determines that the amount of communication is equal to or greater than the threshold, it proceeds to Step ST1902. If the MME determines that the amount of communication is not equal to or greater than the threshold, that is, that the amount of communication is less than the threshold, it proceeds to Step ST1904.

[0200] In Step ST1902, the MME notifies the HeNB of signaling indicating that concentration is ON.

[0201] In Step ST1904, the MME notifies the HeNB of signaling indicating concentration OFF.

[0202] In Step ST1906, the HeNB judges whether or not it has received signaling indicating concentration ON. If it judges that it has received signaling indicating concentration ON, it proceeds to Step ST1903. If it judges that it has not received signaling indicating concentration ON, it proceeds to Step ST1905. Although not shown in the figure, after determining in Step ST1906 that it has not received signaling indicating concentration ON, the HeNB may judge whether or not it has received signaling indicating concentration OFF. If it judges that it has received signaling indicating concentration OFF, it may proceed to Step ST1905. If it judges that it has not received signaling indicating concentration OFF, it may perform normal processing.

[0203] In Step ST1903, the HeNB executes a concentration process for data from an MTCD under its control to the core network. Also, in Step ST1903, the HeNB may omit the process (see Non-Patent Document 2) that is performed when the HeNB receives a normal "RRC Connection Request." Also, in Step ST1903, the HeNB may notify the MTCD that has transmitted the "RRC Connection Request" of "RRC Connection reject." Also, the HeNB may map information indicating that data has been received from the MTCD to the core network into the "RRC Connection reject." Also, the HeNB may map information requesting retransmission of data from the MTCD to the core network into the "RRC Connection reject."

[0204] In Step ST1905, the HeNB does not perform concentration processing on data from the MTCDs being served by the HeNB to the core network.

[0205] Although the present modification has been described mainly as an example in which it is combined with the first embodiment, it can also be used in combination with the first modification of the first embodiment.

[0206] In addition to the effects of Embodiment 1, Modification 2 of Embodiment 1 can provide the following effects. By using Modification 2 of Embodiment 1, when congestion occurs in the core network or an entity of the core network is overloaded, the core network can start concentration processing of HeNBs at its discretion. By starting concentration processing, it is possible to alleviate congestion in the core network while continuing services to mobile terminals.

[0207] Furthermore, when congestion in the core network is alleviated or the overload of an entity in the core network is resolved, the core network can stop the concentration process of the HeNB at its discretion. Compared to the method of always concentrating data from the MTCDs under its control to the core network in the first embodiment, stopping the concentration process eliminates the control delay to the MTCD service that occurs in the concentration process, making it possible to build a user-friendly mobile communication system.

[0208] Embodiment 1, Variation 3 When the above-described second modification of the first embodiment is used, the following problem occurs. Consider a case where there are HeNBs that have the ability to perform line concentration processing and HeNBs that do not have the ability to perform line concentration processing. It is pointless for the MME, SGSN, etc., which are core networks, to execute the processing of the second modification of the first embodiment to notify HeNBs that do not have the ability to perform line concentration processing of an instruction to start or stop line concentration processing. Specifically, this results in a waste of communication resources from the core network to the HeNBs, and a waste of processing in the core network.

[0209] The solution in Modification 3 of Embodiment 1 is shown below. The explanation will focus on the parts that differ from the solutions in Embodiment 1 and Modification 2 of Embodiment 1. Parts that are not explained are the same as those in Embodiment 1 and Modification 2 of Embodiment 1.

[0210] The HeNB notifies the MME, SGSN, etc., which are the core network, of capability information related to the concentration of data from the MTCD. The core network performs the process of Variation 2 of the first embodiment described above for the HeNBs that are capable of concentrating data from the MTCD.

[0211] The following three (1) to (3) are disclosed as specific examples of capability information related to concentration processing that the HeNB notifies to the core network. (1) Information on whether data from an MTCD can be concentrated. Or, information that data from an MTCD can be concentrated. Or, information that data from an MTCD cannot be concentrated. (2) Information on whether NAS signaling can be interpreted. Or, information that NAS signaling can be interpreted. Or, information that NAS signaling cannot be interpreted. (3) Information on whether NAS signaling can be terminated. Or, information that NAS signaling can be terminated. Or, information that NAS signaling cannot be terminated.

[0212] Among specific examples of the capability information related to the line concentration process, using (1) information that data from an MTCD can be concentrated, (2) information that NAS signaling can be interpreted, and (3) information that NAS signaling can be terminated is effective in that a HeNB that does not have the capability to perform line concentration process does not need to notify the core network of the capability information related to the line concentration process.

[0213] The following three (1) to (3) are disclosed as specific examples of timing when a HeNB notifies a core network of capability information related to line concentration processing. (1) When a HeNB is installed. If there is no change in the HeNB's capability to perform line concentration processing, it is possible to obtain the effect of preventing communication resources from being wasted. (2) Periodically. This is effective when there is a change in the HeNB's capability to perform line concentration processing. In addition, since the capability information is notified periodically, it is possible to obtain the effect of being resistant to communication errors. (3) When the capability of a HeNB is changed. This is effective when there is a change in the HeNB's capability to perform line concentration processing. Compared to specific example (2), since notification is only made when there is a change in capability, it is possible to obtain the effect of preventing communication resources from being wasted.

[0214] The following three examples (1) to (3) are disclosed as specific examples of signaling when a HeNB notifies a core network of capability information related to line concentration processing.

[0215] (1) New S1 signaling or S1 message is provided. S1 signaling for control purposes may be provided. Also, S1 signaling that does not require a response message from the receiving side, such as an MME or SGSN, may be provided. S1 signaling that does not require a response message is also called "Class 2" (see Non-Patent Document 14). Also, S1 signaling that is unrelated to mobile terminals may be provided. S1 signaling that is unrelated to mobile terminals is also called "non UE associated Signaling" (see Non-Patent Document 14). The parameter to be mapped to the newly provided S1 signaling is the above-mentioned "capability information related to line concentration processing that the HeNB notifies the core network."

[0216] (2) New S1 signaling or S1 message is provided. S1 signaling for control purposes may be provided. Also, S1 signaling that requires a response message from the receiving side, such as MME or SGSN, may be provided. S1 signaling that requires a response message is also called "Class 1" (see Non-Patent Document 14). Also, S1 signaling that is unrelated to mobile terminals may be provided. The parameter to be mapped to the newly provided S1 signaling is the above-mentioned "capability information related to line concentration processing that the HeNB notifies the core network."

[0217] (3) Use of existing S1 signaling. Existing S1 signaling for control may be used. Also, S1 signaling unrelated to existing mobile terminals may be used. A parameter that needs to be added to the existing S1 signaling is the above-mentioned "capability information related to line concentration processing that the HeNB notifies the core network." Compared to specific examples (1) and (2), there is an advantage in that there is no need to provide new signaling, which can avoid the mobile communication system from becoming complicated.

[0218] Next, the following two examples (a) and (b) will be disclosed as specific examples of existing S1 signaling.

[0219] (a) "S1 SETUP REQUEST" (see Non-Patent Document 14). The purpose of "S1 SETUP REQUEST" is for the eNB and MME to exchange application-level data required for correct interoperability of the S1 interface. The parameters already included are eNB-specific information, such as the eNB's CSG-ID, global cell identifier, and TAC. The HeNB's capability information related to line concentration processing is also HeNB-specific information. Therefore, when the HeNB uses "S1 SETUP REQUEST" to notify the core network of its capability information related to line concentration processing, the receiving MME can obtain the HeNB-specific information all at once. This reduces the processing load on the MME and prevents control delays in the mobile communication system.

[0220] (b) "eNB Configuration Update" (see Non-Patent Document 14). The purpose of "eNB Configuration Update" is to update application-level data required for the eNB and MME to correctly share the S1 interface. The parameters already included are information specific to the eNB, such as the CSG-ID and TAC of the eNB. The capability information related to the line concentration process of the HeNB is also information specific to the HeNB. Therefore, by using "eNB Configuration Update" to notify the core network of the capability information related to the line concentration process, the receiving MME can obtain the HeNB-specific information all at once. This has the effect of reducing the processing load on the MME and preventing control delays in the mobile communication system.

[0221] Next, a specific example of operation using the third modification of the first embodiment will be described with reference to Fig. 20. Fig. 20 is a diagram showing the sequence of a mobile communication system in the third modification of the first embodiment. In Fig. 20, steps corresponding to those shown in Fig. 19 are given the same reference numerals, and common descriptions will be omitted.

[0222] In this operation example, the time when a HeNB is installed will be disclosed as a specific example of the timing when a HeNB notifies a core network of capability information related to line concentration processing.

[0223] In Step ST2001, a HeNB is installed. In Step ST2002, the HeNB notifies the MME of capability information related to line concentration processing of the HeNB. The MME that has received the capability information related to line concentration processing stores and manages the information.

[0224] In Step ST2003, the MME determines whether or not the HeNB is capable of performing line concentration, based on the capability information related to line concentration received in Step ST2002. If the MME determines that the HeNB is capable of performing line concentration, it proceeds to Step ST1901. If the MME determines that the HeNB is not capable of performing line concentration, the MME ends the process and description thereof will be omitted, as this is not an essential part of the present embodiment.

[0225] After it is determined in step ST2003 that the HeNB is capable of performing line concentration processing, the MME and the HeNB perform the processes of steps ST1901 to ST1906, as in the above-mentioned Fig. 19. In this modification, as shown in Fig. 20, the process of step ST1901 is performed after the process of step ST2003, but the process of step ST2003 and the process of step ST1901 may be performed in any order, or the process of step ST2003 may be performed after the process of step ST1901.

[0226] Although this modification has been described mainly as an example in which it is combined with the first embodiment and the second modification of the first embodiment, it can also be used in combination with the first modification of the first embodiment.

[0227] In addition to the effects of Embodiment 1 and Embodiment 2, Modification 3 of Embodiment 1 can provide the following effect. It is possible to prevent the core network from notifying a HeNB that does not have the ability to perform concentration processing of an instruction to start or stop concentration processing. This makes it possible to effectively utilize communication resources from the core network to the HeNB, and also to reduce the processing load on the core network.

[0228] First embodiment, variant 4 In Variation 4 of the First Embodiment, a different solution to the same problem as in Variation 3 of the First Embodiment is disclosed. The solution in Variation 4 of the First Embodiment is shown below. The explanation will focus on the parts that differ from the solutions in the First Embodiment and Variation 2 of the First Embodiment. Parts that are not explained are the same as those in the First Embodiment and Variation 2 of the First Embodiment.

[0229] In the fourth modification of the first embodiment, the MME, SGSN, etc., which are the core network, execute the processing of the second modification of the first embodiment for both HeNBs that have the ability to perform line concentration processing and HeNBs that do not have the ability to perform line concentration processing. When a HeNB receives an instruction to start or stop line concentration processing, the HeNB performs different operations depending on whether it has the ability to perform line concentration processing.

[0230] Specific examples of the operation of a HeNB capable of performing line concentration processing include the first embodiment, the first modification of the first embodiment, and the second modification of the first embodiment.

[0231] Specific examples of the operation of a HeNB that does not have the ability to perform line concentration processing are disclosed below. First, the following four examples (1) to (4) are disclosed as specific examples of the operation of a HeNB that receives an instruction to start line concentration processing from a core network such as an MME or SGSN.

[0232] (1) Stop or reject the transmission and reception of data from a mobile terminal under its control to the core network, such as MME or SGSN. Specific examples of data to the MME include NAS messages and NAS signaling.

[0233] (2) Rejecting RRC connection-related signaling from a mobile terminal being served by the mobile terminal. Specific examples of RRC connection-related signaling include "RRC CONNECTION REQUEST" and "RRC CONNECTION Reestablishment Request" (see Non-Patent Document 2).

[0234] (3) Perform the operation when "Overload Start" is received from the current MME (see Non-Patent Document 14). Specifically, reject the establishment of an RRC connection other than an emergency call.

[0235] (4) A combination of (1) to (3) above.

[0236] A specific example of the operation of a HeNB that receives an instruction to stop concentration processing from a core network such as an MME or SGSN is to perform normal operation.

[0237] Next, a specific example of operation using the fourth modification of the first embodiment will be described with reference to Fig. 21. Fig. 21 is a diagram showing the sequence of a mobile communication system in the fourth modification of the first embodiment. In Fig. 21, steps corresponding to those shown in Fig. 19 are given the same reference numerals, and common descriptions will be omitted.

[0238] In this operation example, a case where "Overload Start", which is an existing S1-AP signaling, is used is disclosed as a specific example of signaling from a core network to instruct a HeNB to turn concentration ON. Also, a case where "Overload stop", which is an existing S1-AP signaling, is used is disclosed as a specific example of signaling from a core network to instruct a HeNB to turn concentration OFF. Also, as an operation example when a HeNB that does not have the ability to perform concentration processing receives an instruction to start concentration processing from the core network, a case where the HeNB performs operation when the current "Overload Start" is received is disclosed.

[0239] In Step ST1901, the MME determines whether or not the amount of communication between the MME and the HeNB is equal to or greater than a threshold. If the MME determines that the amount of communication is equal to or greater than the threshold, it proceeds to Step ST2101. If the MME determines that the amount of communication is not equal to or greater than the threshold, that is, that the amount of communication is less than the threshold, it proceeds to Step ST2104.

[0240] In Step ST2101, the MME notifies the HeNB of "Overload Start." In Step ST2104, the MME notifies the HeNB of "Overload Stop."

[0241] In Step ST2107, the HeNB judges whether or not it has received "Overload Start." If it determines that it has received "Overload Start," it moves to Step ST2102. If it determines that it has not received "Overload Start," it moves to Step ST2105. Although not shown in the figure, after determining that it has not received "Overload Start" in Step ST2107, the HeNB may determine whether or not it has received "Overload Stop." Then, if it determines that it has received "Overload Stop," it may move to Step ST2105, and if it determines that it has not received "Overload Stop," it may move to Step ST2106.

[0242] In Step ST2102, the HeNB determines whether or not its own cell has the capability to perform line concentration. If the HeNB determines that it has the capability to perform line concentration, it moves to Step ST1903. If the HeNB determines that it does not have the capability to perform line concentration, it moves to Step ST2103.

[0243] In Step ST1903, the HeNB performs a concentration process for data from the MTCDs being served to the core network, and ends the process. In Step ST2103, the HeNB rejects the establishment of an RRC connection other than an emergency call from a mobile terminal being served by the HeNB, and ends the process.

[0244] In Step ST2105, the HeNB determines whether or not its own cell has the capability to perform line concentration. If the HeNB determines that it has the capability to perform line concentration, it moves to Step ST1905. If the HeNB determines that it does not have the capability to perform line concentration, it moves to Step ST2106.

[0245] In Step ST1905, the HeNB does not perform concentration processing on data from the MTCDs being served by the HeNB to the core network. In Step ST2106, the HeNB performs normal operation.

[0246] The determination process of Step ST2105 may be omitted, and the HeNB that has received the “Overload Stop” from the MME in Step ST2104 may proceed to Step ST2106 and perform normal operation, regardless of whether or not it has the capability to perform line concentration.

[0247] Although this modification has been described mainly as an example in which it is combined with the first embodiment and the second modification of the first embodiment, it can also be used in combination with the first modification of the first embodiment.

[0248] In addition to the effects of Embodiment 1 and Modification 2 of Embodiment 1, Modification 4 of Embodiment 1 can provide the following effects: Compared to Modification 3 of Embodiment 1, it is no longer necessary for the HeNB to notify the core network of capability information related to line concentration processing of its own cell, and it is possible to effectively utilize communication resources between the HeNB and the core network.

[0249] In addition, the core network does not need to store whether or not the HeNBs under its control have the capability to perform concentration processing, and it is no longer necessary to distinguish between operations depending on whether or not the HeNBs have the capability to perform concentration processing (see step ST2003 in FIG. 20), thereby reducing the processing load on the core network.

[0250] Furthermore, when congestion occurs in the core network and the core network notifies the HeNB of signaling instructing it to turn on line concentration, an operation that leads to communication between the HeNB and the core network or a reduction in the processing load on the core network is started, regardless of whether the HeNB has the ability to perform line concentration (see step ST2103 and step ST1903 in FIG. 21). Therefore, it is possible to avoid congestion in the core network, regardless of whether the HeNB has the ability to perform line concentration.

[0251] Embodiment 2 In the second embodiment, a specific method for transmitting data from the HeNB to an MME, an SGSN, or the like that constitutes a core network after the HeNB performs concentration processing using the first embodiment will be disclosed.

[0252] The solution in the second embodiment is as follows: The HeNB acts as a trigger or a starting point to transmit data from the MTCD under its control to the MME, SGSN, MTC server, etc., which are the core network.

[0253] The following two (1) and (2) are disclosed as specific examples of conditions that trigger data transmission from an MTCD under the control of a HeNB to an MME, SGSN, MTC server, etc., which are core networks.

[0254] (1) A HeNB transmits data from an MTCD under its control to a core network, regardless of whether it receives uplink data from an MTCD under its control. The transmission may be performed using resources for the MTCD. Specific examples of resources for the MTCD include a time during which communication for the MTCD is permitted, a permitted period, or permitted resources. The time or period during which communication for the MTCD is permitted corresponds to the permitted period. The resources permitted for communication for the MTCD correspond to permitted resources. The configuration of resources for the MTCD may be configured or updated in the HeNB by an MME, SGSN, MTC server, or the like, which is a core network, or may be statically determined, i.e., determined in advance.

[0255] In the above-mentioned Non-Patent Document 9, the eNB holds the message for a predetermined time from the time when it receives the message from the MTCD. In contrast, in this specific example, the HeNB transmits to the core network at a time when communication for the MTCD is permitted, regardless of the time when it receives the message from the MTCD. Therefore, in this specific example, the core network side can grasp the time when transmission for the MTCD from the HeNB is likely to occur. In Non-Patent Document 9, it is impossible for the core network side to grasp the time when the eNB receives the message from the MTCD, and therefore it is impossible to grasp the time when transmission for the MTCD from the eNB is likely to occur based on the time when the message is received from the MTCD. Therefore, compared to Non-Patent Document 9, in this specific example, the core network can easily adjust the load by the MTCD.

[0256] Also, 3GPP TR23.888 V0.5.1 (hereinafter referred to as "Non-Patent Document 15") discloses that a network operator permits an MTCD to access the network only for a predefined period. In contrast, in this specific example, it is not necessary to set the period during which the MTCD is permitted to access the network. Therefore, it is not necessary for the core network to notify or set the permitted period to a large number of MTCDs, and therefore radio resources can be used effectively. Furthermore, in this specific example, it is not necessary to manage the time of each MTCD in the core network or to establish synchronization between the core network and the MTCD, and therefore it is possible to avoid the communication system from becoming complicated.

[0257] (2) When the HeNB receives uplink data from an MTCD under its control, it transmits the data from the MTCD under its control to the core network, such as the MME, SGSN, or MTC server.

[0258] As specific examples of uplink data from an MTCD, the following two examples (a) and (b) are disclosed.

[0259] (a) Reception of RRC message and RRC signaling. Non-Patent Document 9 discloses that the eNB transmits data from the MTCD to the core network upon receiving NAS signaling. In this specific example, the eNB transmits data from the MTCD to the core network upon receiving RRC signaling. This enables preparation for concentration processing at an earlier stage than in Non-Patent Document 9. Data from the served MTCD may be transmitted to the core network after a predetermined time has elapsed since the RRC message was received, or after a time set by the core network has elapsed. Alternatively, data from the served MTCD may be transmitted to the core network when an RRC message from the served MTCD has been received a predetermined number of times.

[0260] (b) Reception of uplink data transmitted by a communication method other than a mobile communication system standardized by 3GPP. With this specific example, even if an MTCD is set in a location with a poor radio environment for a mobile communication system standardized by 3GPP, as in the above specific example (2), the HeNB can transmit data from an MTCD under its control to the core network in response to reception of uplink data from the MTCD under its control.

[0261] Data from an MTCD under its control may be transmitted to the core network after a predetermined time has elapsed from the time point when uplink data transmitted in a communication method other than the mobile communication system standardized by 3GPP has been received, or after a time set by the core network has elapsed. Alternatively, data from an MTCD under its control may be transmitted to the core network when uplink data transmitted in a communication method other than the mobile communication system standardized by 3GPP has been received from the MTCD under its control a predetermined number of times.

[0262] A specific example of signaling when a HeNB transmits data from an MTCD under its control to an MME, SGSN, MTC server, or the like, which is a core network, via an S-GW is disclosed below. The data is transmitted using the User Datagram Protocol (UDP) (see Non-Patent Document 13). The data may be user data.

[0263] A specific example of signaling when a HeNB transmits data from an MTCD under its control to an MME, SGSN, MTC server, or the like, which is a core network, via an MME, is disclosed below. The S1 interface (also referred to as "S1-MME" or "S1-U") is used. The data may be control data.

[0264] Further specific examples of transmitting data from a served MTCD to a core network using the S1 interface are disclosed below. New S1 signaling or S1 messages are provided. S1 signaling for control may be provided. Also, S1 signaling that does not require a response message from the receiving side, such as an MME or SGSN, may be provided. S1 signaling that does not require a response message is also referred to as "Class 2" (see Non-Patent Document 14). Also, S1 signaling that is unrelated to a mobile terminal may be provided. S1 signaling that is unrelated to a mobile terminal is also referred to as "non-UE associated Signaling" (see Non-Patent Document 14).

[0265] The following eight parameters (1) to (8) are disclosed as specific examples of parameters to be mapped to the newly established S1 signaling. (1) HeNB identifier. This allows the receiving side to identify which HeNB the data passed through, so it may be PCI (Physical Cell Identity), CGI (Cell Global Identity), etc. (2) MTCD identifier. This allows the receiving side to identify which MTCD the data came from, so it may be IMSI, MTCD serial number, etc. The number of these parameters may be the same as the number of MTCDs performing the concentrating process. (3) PDU (Protocol Data Unit) for MTC. A PDU is a block of data that has meaning between peer layers. This makes it possible to map data from the MTCD to the core network to the newly established S1 signaling. The number of these parameters may be the same as the number of MTCDs performing the concentrating process. (4) SDU (Service Data Unit) for MTC. An SDU is a block of data requested for transfer from a higher layer. This makes it possible to map data from an MTCD to a core network in a newly established S1 signaling. This parameter may be as many as the number of MTCDs performing concentrating processing, i.e., the number of MTCDs performing concentrating processing. (5) Service type or service identifier. This allows for cases where the data destination differs for each service. Even when one MTCD supports multiple services, it can also accommodate cases where the data destination differs for each service. (6) Information indicating which MTC server or MTC user the data is intended for. A specific example is an MTC server identifier or an MTC user identifier. This allows for the destination to be changed appropriately. (7) An identifier or index indicating a combination of (5) and (6). (8) A combination of (1) to (7).

[0266] Next, a specific example of operation using the second embodiment will be described with reference to Fig. 22. Fig. 22 is a diagram showing the sequence of the mobile communication system in the second embodiment. In Fig. 22, steps corresponding to those shown in Fig. 17 and Fig. 19 are given the same reference numerals, and common descriptions will be omitted.

[0267] In this operation example, as a specific example of a condition that triggers a HeNB to transmit data from an MTCD under its control to a core network, a case will be disclosed in which the HeNB transmits data from an MTCD under its control to a core network regardless of whether the HeNB has received uplink data from the MTCD under its control. The case will also be disclosed in which the transmission to the core network is performed during a period in which communication for the MTCD is permitted.

[0268] In Step ST2201, the MME notifies the HeNB of period information indicating a period during which the HeNB is permitted to transmit data from an MTCD being served by the HeNB to a core network. In other words, the MME notifies the HeNB of period information indicating a period during which communication for the MTCD is permitted.

[0269] Next, MTCD_1 performs the process of Step ST1703 described above, and MTCD_n performs the process of Step ST1704 described above. The HeNB that has received the "RRC Connection Request" transmitted from MTCD_1 and MTCD_n performs the processes of Step ST1705 and Step ST1903 described above. After completing the process of Step ST1903, the HeNB proceeds to Step ST2202.

[0270] In Step ST2202, the HeNB determines whether or not the period is one in which MTCD communication is permitted, based on the period information received in Step ST2201. If the HeNB determines that the period is one in which MTCD communication is permitted, it proceeds to Step ST2203. If the HeNB determines that the period is not one in which MTCD communication is permitted, it repeats the determination processing of Step ST2202.

[0271] In Step ST2203, the HeNB transmits data from the MTCD under its control to the core network to the MME using the S1 interface. In this operation example, after the process of Step ST1703, processes corresponding to Step ST1705, Step ST1903, and Step ST2202 are actually performed, but illustration and description thereof are omitted for ease of understanding.

[0272] Moreover, if it is determined in step ST1705 that the data is not from the MTCD, this is not an essential part of the present embodiment, and therefore description thereof will be omitted, and the processing ends. Alternatively, if it is determined in step ST1705 that the data is not from the MTCD, the same processing as in step ST2202 may be performed to indicate that there is no data from the MTCD during the period in which communication for the MTCD is permitted. For example, "empty" may be notified. This allows the MME to receive some data during the period in which communication for the MTCD is permitted, and it is possible to reduce communication errors between the HeNB and the MME.

[0273] Furthermore, while repeating the determination process of step ST2202, it is also conceivable that the HeNB separately receives an RRC message from an MTCD being served by the HeNB, and performs processes corresponding to step ST1705, step ST1903, and step ST2202; however, for ease of understanding, the description thereof is omitted.

[0274] Next, a specific example of operation using the second embodiment will be described with reference to Fig. 23. Fig. 23 is a diagram showing the sequence of the mobile communication system in the second embodiment. In Fig. 23, steps corresponding to those shown in Fig. 17 and Fig. 22 are given the same reference numerals, and common explanations will be omitted.

[0275] In this operation example, as a specific example of a condition that triggers a HeNB to transmit data from an MTCD under its control to a core network, a case will be disclosed in which the HeNB transmits data from an MTCD under its control to a core network upon receiving uplink data from the MTCD under its control. Also, as a specific example of uplink data, a case in which RRC signaling is used will be disclosed.

[0276] In Step ST2301, the MME sets, to the HeNB, a time from when the MME receives the RRC message until when the MME transmits data from the MTCD to the core network. In other words, the MME sets, to the HeNB, a concentration processing time, which is the time from when the MME receives the RRC message until when the MME performs concentration processing.

[0277] Next, in Step ST1703, MTCD_1 performs a process of transmitting an "RRC Connection Request" to HeNB, and in Step ST1704, MTCD_n performs a process of transmitting an "RRC Connection Request" to HeNB. Having received the "RRC Connection Request" transmitted from MTCD_1 and MTCD_n, the HeNB performs the processes of Step ST1705 and Step ST1903 described above. After completing the process of Step ST1903, the HeNB proceeds to Step ST2302.

[0278] In Step ST2302, the HeNB determines whether or not the concentration processing time set in Step ST2301 has elapsed since the reception of the RRC message. If the HeNB determines that the concentration processing time has elapsed, it proceeds to Step ST2203. If the HeNB determines that the concentration processing time has not elapsed, it repeats the determination processing of Step ST2302. In this operation example, the HeNB performs processing to determine whether or not the concentration processing time has elapsed in Step ST2302, but may also be configured to perform processing to determine whether or not the concentration processing time has elapsed since the reception of the first RRC message received after the previous transmission of data from an MTCD being served to the core network.

[0279] In this operation example, after the process of step ST1703, processes corresponding to steps ST1705, ST1903 and ST2302 are actually performed, but for ease of understanding, the description thereof is omitted.

[0280] Moreover, if it is determined in step ST1705 that the data is not from the MTCD, this is not an essential part of the present embodiment, and therefore description thereof will be omitted, and the processing ends. Alternatively, if it is determined in step ST1705 that the data is not from the MTCD, the same processing as in step ST2202 may be performed to indicate that there is no data from the MTCD during the period in which communication for the MTCD is permitted. For example, "empty" may be notified. This allows the MME to receive some data during the period in which communication for the MTCD is permitted, and it is possible to reduce communication errors between the HeNB and the MME.

[0281] Furthermore, while repeating the determination process of step ST2302, it is also conceivable that the HeNB separately receives an RRC message from an MTCD being served by the HeNB, and performs processes corresponding to step ST1705, step ST1903, and step ST2302; however, for ease of understanding, the description thereof is omitted.

[0282] In this embodiment, we have mainly described an example in combination with embodiment 1, but this embodiment can also be used in combination with variant 1 of embodiment 1, variant 2 of embodiment 1, variant 3 of embodiment 1, and variant 4 of embodiment 1.

[0283] Furthermore, this embodiment can also be used when an eNB holds back and aggregates signaling messages common to an MTCD group, as disclosed in Non-Patent Document 9.

[0284] The second embodiment can provide the following effects: A method can be established in which the HeNB concentrates data from the MTCDs under its control to the core network, and then transmits the data from the HeNB to the core network.

[0285] Second embodiment, variant 1 In the first modification of the second embodiment, another specific example will be disclosed in which the HeNB in ​​the second embodiment transmits data from an MTCD under its control to an MME, an SGSN, an MTC server, or the like, which is a core network, via the MME using the S1 interface.

[0286] New S1 signaling or S1 messages are provided. S1 signaling for control purposes may also be provided. Also, S1 signaling that requires a response message from the receiving side, such as an MME or SGSN, may also be provided. S1 signaling that requires a response message is also called "Class 1" (see Non-Patent Document 14).

[0287] When the HeNB receives a message indicating success, such as a "Successful message" or an "Ack message", in the response message from the MME, the HeNB may be configured to transmit the next data. When the HeNB receives a message indicating failure, such as an "Unsuccessful message", "failure message" or "Nack message", in the response message from the MME, the HeNB may be configured to perform retransmission. In addition, S1 signaling unrelated to mobile terminals may be provided. S1 signaling unrelated to mobile terminals is also referred to as "non-UE associated Signaling" (see Non-Patent Document 14).

[0288] Specific examples of parameters to be mapped to the newly provided S1 signaling are the same as those in the second embodiment, and therefore will not be described here.

[0289] Next, a specific example of operation using the first modification of the second embodiment will be described with reference to Fig. 24. Fig. 24 is a diagram showing the sequence of the mobile communication system in the first modification of the second embodiment. In Fig. 24, steps corresponding to those shown in Fig. 17 and Fig. 22 are given the same reference numerals, and common explanations will be omitted.

[0290] In this operation example, as a specific example of a condition that triggers transmission from an MTCD under its control to a core network, a case will be disclosed in which the HeNB transmits data from an MTCD under its control to a core network regardless of reception of uplink data from the MTCD under its control. Also, a case will be disclosed in which transmission to the core network is performed during a period in which communication for the MTCD is permitted.

[0291] The MME performs the process of Step ST2201 described above. Next, in Step ST1703, MTCD_1 performs a process of transmitting an "RRC Connection Request" to the HeNB, and in Step ST1704, MTCD_n performs a process of transmitting an "RRC Connection Request" to the HeNB. Having received the "RRC Connection Request" transmitted from MTCD_1 and MTCD_n, the HeNB performs the processes of Step ST1705 and Step ST1903 described above. After completing the process of Step ST1903, the HeNB performs the processes of Step ST2202 and Step ST2203 described above.

[0292] Next, in Step ST2401, the MME that has received data from the MTCD being served by it to the core network by signaling using the class 1 S1 interface from the HeNB in ​​Step ST2203 transmits a response message to the message of the received data to the HeNB.

[0293] Next, in Step ST2402, the HeNB determines whether or not it has received a message indicating success, for example, an Ack message. Specifically, the HeNB determines whether or not the response message received in Step ST2401 is a message indicating success, for example, an Ack message. If the HeNB determines that the response message is a message indicating success, for example, an Ack message, it moves to Step ST2404. If the HeNB determines that the response message is not a message indicating success, that is, if the HeNB determines that the response message is a message indicating failure, for example, a Nack message, it moves to Step ST2403.

[0294] In Step ST2403, the HeNB retransmits the data transmitted in Step ST2203 from the MTCD being served by the HeNB to the core network to the MME, and then returns to Step ST2402 to repeat the determination process.

[0295] In Step ST2404, the HeNB transmits the following data from the MTCD being served by the HeNB to the core network to the MME using the S1 interface.

[0296] In this variant, we have mainly described an example in combination with embodiment 1, but this variant can also be used in combination with variant 1 of embodiment 1, variant 2 of embodiment 1, variant 3 of embodiment 1, and variant 4 of embodiment 1.

[0297] Furthermore, this modification can also be used when an eNB, as disclosed in Non-Patent Document 9, holds back and aggregates signaling messages common to an MTCD group.

[0298] The first modification of the second embodiment can provide the following effects: A method can be established in which the HeNB concentrates data from the MTCDs under its control to the core network, and then transmits the data from the HeNB to the core network.

[0299] Second embodiment, modified example 2 In the second modification of the second embodiment, another specific example will be disclosed in which the HeNB in ​​the second embodiment transmits data from an MTCD under its control to an MME, an SGSN, an MTC server, or the like, which is a core network, via the MME, using the S1 interface. Existing S1 signaling or S1 messages are used. Existing S1 signaling for control may be used. Furthermore, existing S1 signaling unrelated to mobile terminals may be used.

[0300] The following five items (1) to (5) are disclosed as specific examples of parameters required for existing S1 signaling when a HeNB transmits data from an MTCD under its control to a core network such as an MME, SGSN, or MTC server via the MME using the S1 interface. (1) HeNB identifier. (2) MTCD identifier. There may be as many as the number of MTCDs performing concentrating processing, i.e., the same number as the number of MTCDs performing concentrating processing. (3) MTC PDU or SDU. There may be as many as the number of MTCDs performing concentrating processing, i.e., the same number as the number of MTCDs performing concentrating processing. (4) Service type or service identifier. (5) Information indicating which MTC server or MTC user the data is intended for.

[0301] Next, the following two examples (a) and (b) will be disclosed as specific examples of existing S1 signaling.

[0302] (a) "S1 SETUP REQUEST" (see Non-Patent Document 14). The parameters mapped to "S1 SETUP REQUEST" already include "Global eNB ID," which is the HeNB identifier of specific example (1) of the parameters required for the existing S1 signaling described above. Therefore, the parameters that need to be newly added to "S1 SETUP REQUEST" are the MTCD identifier of specific example (2) described above, the MTC PDU or SDU of specific example (3) described above, the service type or service identifier of specific example (4) described above, and information indicating which MTC server or MTC user the data is intended for described above in specific example (5). The number of MTCD identifiers may be the same as the number of MTCDs performing line concentration processing, i.e., the same number as the number of MTCDs performing line concentration processing. The number of MTC PDUs or SDUs may be the same as the number of MTCDs performing line concentration processing, i.e., the same number as the number of MTCDs performing line concentration processing.

[0303] A parameter indicating that data from the MTCD was normally received may be added to "S1 SETUP RESPONSE", which is a response message from the MME indicating success in response to "S1 SETUP REQUEST". A HeNB that receives "S1 SETUP RESPONSE" including a parameter indicating normal reception may transmit data from the next MTCD. Alternatively, a HeNB that receives "S1 SETUP RESPONSE" without newly creating a parameter indicating normal reception may transmit data from the next MTCD. A parameter indicating that data from the MTCD was not normally received may be added to "S1 SETUP FAILURE", which is a response message from the MME indicating failure in response to "S1 SETUP REQUEST". A HeNB that receives "S1 SETUP FAILURE" including a parameter indicating normal reception may retransmit data from the same MTCD. Alternatively, a HeNB that receives "S1 SETUP FAILURE" without newly creating a parameter indicating normal reception may retransmit data from the same MTCD.

[0304] (b) "eNB Configuration Update" (see Non-Patent Document 14). The parameters mapped to "eNB Configuration Update" already include "eNB Name," which is the HeNB identifier of the specific example (1) of the parameters required for the existing S1 signaling described above. Therefore, the parameters that need to be newly added to "S1 SETUP REQUEST" are the MTCD identifier of the specific example (2) described above, the MTC PDU or SDU of the specific example (3) described above, the service type or service identifier of the specific example (4) described above, and information indicating which MTC server or MTC user the data is intended for, described in the specific example (5) described above. The number of MTCD identifiers may be the same as the number of MTCDs performing line concentration processing, i.e., the same number as the number of MTCDs performing line concentration processing. The number of MTC PDUs or SDUs may be the same as the number of MTCDs performing line concentration processing, i.e., the same number as the number of MTCDs performing line concentration processing.

[0305] A parameter indicating that data from the MTCD has been normally received may be added to "eNB Configuration Update Acknowledge", which is a response message from the MME indicating success in response to "eNB Configuration Update". A HeNB that has received "eNB Configuration Update Acknowledge" including a parameter indicating normal reception may transmit data from the next MTCD. Alternatively, a HeNB that has received "eNB Configuration Update Acknowledge" may transmit data from the next MTCD without creating a new parameter indicating normal reception. A parameter indicating that data from the MTCD has not been normally received may be added to "eNB Configuration Update FAILURE", which is a response message from the MME indicating failure in response to "eNB Configuration Update". A HeNB that has received "eNB Configuration Update FAILURE" including a parameter indicating normal reception may retransmit data from the same MTCD. Alternatively, a HeNB that has received "eNB Configuration Update FAILURE" without creating a new parameter indicating normal reception may retransmit data from the same MTCD.

[0306] In this variant, we have mainly described an example in combination with embodiment 1, but this variant can also be used in combination with variant 1 of embodiment 1, variant 2 of embodiment 1, variant 3 of embodiment 1, and variant 4 of embodiment 1.

[0307] Furthermore, this modification can also be used when an eNB, as disclosed in Non-Patent Document 9, holds back and aggregates signaling messages common to an MTCD group.

[0308] In addition to the effects of Embodiment 2, Modification 2 of Embodiment 2 can provide the following effects: Compared with Embodiment 2 and Modification 1 of Embodiment 2, there is an advantage that it is not necessary to provide new signaling, and therefore it is possible to avoid the mobile communication system from becoming complicated.

[0309] Second embodiment, variant 3 Variation 3 of Embodiment 2 discloses another specific example in which the HeNB in ​​Embodiment 2 transmits data from an MTCD under its control to an MME, SGSN, MTC server, or the like, which is a core network, using the S1 interface via the MME. Existing S1 signaling or S1 messages are used. Existing S1 signaling for control may be used. Also, existing S1 signaling related to mobile terminals may be used. Existing S1 signaling related to mobile terminals is also called "UE associated signaling" (see Non-Patent Document 14).

[0310] The following nine items (1) to (9) are disclosed as specific examples of parameters required for existing S1 signaling when a HeNB transmits data from an MTCD under its control to a core network such as an MME, SGSN, or MTC server via the MME using the S1 interface.

[0311] (1) Identifier of HeNB. Since the receiving side can identify which HeNB the data has passed through, it may be PCI (Physical Cell Identity), CGI (Cell Global Identity), or the like.

[0312] (2) MTCD identifier. This allows the receiving side to identify which MTCD the data came from, so it may be the IMSI, the MTCD serial number, etc. This parameter may be the same number as the number of MTCDs performing line concentration processing, i.e., the number of MTCDs performing line concentration processing.

[0313] (3) PDU for MTC. A PDU is a block of data that has meaning between peer layers. By using PDU, it becomes possible to map data from the MTCD to the core network to the newly established S1 signaling. This parameter may be set in the same number as the number of MTCDs that perform line concentration processing, i.e., the same number as the number of MTCDs that perform line concentration processing.

[0314] (4) SDU for MTC. An SDU is a block of data requested for transfer from a higher layer. By using SDU, it becomes possible to map data from the MTCD to the core network to the newly established S1 signaling. This parameter may be set in the same number as the number of MTCDs that perform line concentration processing, i.e., the same number as the number of MTCDs that perform line concentration processing.

[0315] (5) An indicator indicating that the S1 signaling is for MTC. Alternatively, an indicator indicating that the S1 signaling is unrelated to normal UE. The existence of this parameter enables a HeNB to determine whether or not it is using S1 signaling for data transmission from an MTCD under its control to a core network. This enables operations such as not including parameters related to normal UE in S1 signaling when transmitting data from an MTCD to a core network, or indicating that parameters related to normal UE are meaningless information.

[0316] (6) Service type or service identifier. This allows for cases where the data transmission destination differs depending on the service. Also, even if one MTCD supports multiple services, it can accommodate cases where the data transmission destination differs depending on the service.

[0317] (7) Information indicating which MTC server or MTC user the data is intended for. For example, an MTC server identifier or an MTC user identifier. This allows the destination to be changed appropriately.

[0318] (8) An identifier or index indicating a combination of (6) and (7).

[0319] (9) A combination of (1) to (8) above.

[0320] Next, the following two examples (a) and (b) will be disclosed as specific examples of existing S1 signaling.

[0321] (a) "Initial UE Message" (see Non-Patent Document 14). In the current standard, when an eNB receives an uplink NAS message, the eNB transmits the message to an MME using an "Initial UE Message" including an NAS PDU. Therefore, when an HeNB transmits data from an MTCD under its control to a core network to an MME using an "Initial UE Message," it is possible to use the same S1 signaling as in the current standard for the same purpose. This makes it possible to avoid the mobile communication system from becoming complicated. However, this modification can also be used when an HeNB does not receive an uplink NAS message.

[0322] Next, parameters that need to be added or changed to the "Initial UE Message" will be described. The parameters mapped to the "Initial UE Message" already include (1) "CGI," which is the HeNB identifier. Therefore, specific examples of parameters that need to be newly added to the "Initial UE Message" include the following (2) to (8): (2) MTCD identifier. (3) PDU for MTC. (4) SDU for MTC. The "Initial UE Message" already includes a NAS-PDU. For example, if the S1 signaling is for MTC, the NAS-PDU may be the PDU for MTC. (5) Indicator indicating that the S1 signaling is for MTC. (6) Information indicating which MTC server or MTC user the data is intended for. (7) Information indicating which MTC server or MTC user the data is intended for. (8) An identifier or index indicating a combination of the above (6) and (7).

[0323] Among the parameters included in the "Initial UE Message," the parameter that needs to be changed is the "eNB UE S1AP ID." Under the current standard, the eNB assigns a unique "eNB UE S1AP ID" to be used by the mobile terminal and maps it in the "Initial UE Message." The "eNB UE S1AP ID" is a unique identifier associated with the mobile terminal on the S1 interface. When transmitting data from the HeNB to the core network after concentration processing at the HeNB, the transmitted data may include data from multiple MTCDs. In other words, the S1 interface is not used specifically for the mobile terminal. Therefore, a situation may arise in which the HeNB is unable to assign the "eNB UE S1AP ID." Furthermore, under the current standard, the "eNB UE S1AP ID" must always be mapped to the "Initial UE Message." In other words, when data from multiple MTCDs is transmitted in a single "initial UE Message" due to concentration processing, the handling of the "eNB UE S1AP ID" will not be consistent across the mobile communication system. If the mobile communication system is not unified, problems such as the inability to provide a stable communication network will occur. Therefore, for example, if the S1 signaling is for MTC, even if the "eNB UE S1AP ID" is mapped, it will be an invalid parameter on the receiving side, or mapping on the transmitting side will be made optional rather than mandatory. This will clarify the HeNB processing, enable the construction of a unified mobile communication network, and enable the provision of a stable communication network.

[0324] (b) "Uplink NAS Transport" (see Non-Patent Document 14). In the current standard, when an eNB receives an NAS message to be sent to an MME to which a connection via an S1 interface related to a mobile terminal exists, the eNB transmits the message to the MME using "Uplink NAS Transport" including an NAS PDU. Therefore, when a HeNB transmits data from an MTCD under its control to an MME to a core network using "Uplink NAS Transport," it can use the same S1 signaling as in the current standard for the same purpose. This makes it possible to avoid the mobile communication system from becoming complicated. However, this modification can also be used when a HeNB does not receive an uplink NAS message. Furthermore, this modification can also be used when there is no connection via an S1 interface.

[0325] Next, the parameters that need to be added or changed to "Uplink NAS Transport" will be described. The parameters mapped to "Uplink NAS Transport" already include (1) "CGI," which is an identifier of the HeNB. Therefore, specific examples of parameters that need to be newly added to "Initial UE Message" include the following (2) to (8): (2) MTCD identifier. (3) PDU for MTC. (4) SDU for MTC. "Uplink NAS Transport" already includes NAS-PDU. For example, if S1 signaling is for MTC, the NAS-PDU may be the PDU for MTC. (5) Indicator indicating that the S1 signaling is for MTC. (6) Information indicating which MTC server or MTC user the data is intended for. (7) Information indicating which MTC server or MTC user the data is intended for. (8) Identifier or index indicating a combination of (6) and (7).

[0326] The following two parameters (b1) and (b2) are disclosed as parameters that need to be changed among the parameters included in "Uplink NAS Transport".

[0327] (b1) "eNB UE S1AP ID". In the current standard, an eNB assigns a unique "eNB UE S1AP ID" to be used for a mobile terminal and maps it in "Uplink NAS Transport". The "eNB UE S1AP ID" is a unique identifier associated with the mobile terminal on the S1 interface. When data is transmitted from the HeNB to the core network after concentration processing at the HeNB, the transmitted data may include data from multiple MTCDs. In other words, the S1 interface is not used specifically for the mobile terminal. This may result in a situation where the HeNB is unable to assign an "eNB UE S1AP ID".

[0328] Furthermore, the current standard requires that the "eNB UE S1AP ID" be mapped to the "Uplink NAS Transport." In other words, when data from multiple MTCDs is transmitted via a single "Uplink NAS Transport" through line concentration processing, the handling of the "eNB UE S1AP ID" will lack uniformity across the mobile communication system. Without uniformity across the mobile communication system, problems such as the inability to provide a stable communication network will arise. Therefore, for example, if the S1 signaling is for MTC, even if the "eNB UE S1AP ID" is mapped, it can be treated as an invalid parameter on the receiving side, or mapping on the transmitting side can be made optional rather than mandatory. This clarifies HeNB processing, enabling the construction of a unified mobile communication network and the provision of a stable communication network.

[0329] (b2) "MME UE S1AP ID". "MME UE S1AP ID" is a unique identifier associated with a mobile terminal on the S1 interface. When data is transmitted from the HeNB to the core network after concentration processing at the HeNB, the transmitted data may include data from multiple MTCDs. In other words, the S1 interface is not used specifically for the mobile terminal. This may result in a situation where the HeNB cannot assign an "MME UE S1AP ID".

[0330] Furthermore, the current standard requires that "MME UE S1AP ID" be mapped to "Uplink NAS Transport." In other words, when data from multiple MTCDs is transmitted via a single "Uplink NAS Transport" due to line concentration, the handling of "MME UE S1AP ID" will lack uniformity across the mobile communication system. Without uniformity across the mobile communication system, problems such as the inability to provide a stable communication network will arise. Therefore, for example, if the S1 signaling is for MTC, even if "MME UE S1AP ID" is mapped, it can be treated as an invalid parameter on the receiving side, or mapping on the transmitting side can be made optional rather than mandatory. This clarifies HeNB processing, enables the construction of a unified mobile communication network, and ensures the provision of a stable communication network.

[0331] In this variant, we have mainly described an example in combination with embodiment 1, but this variant can also be used in combination with variant 1 of embodiment 1, variant 2 of embodiment 1, variant 3 of embodiment 1, and variant 4 of embodiment 1.

[0332] Furthermore, this modification can also be used when an eNB, as disclosed in Non-Patent Document 9, holds back and aggregates signaling messages common to an MTCD group.

[0333] In addition to the effects of Embodiment 2, Modification 3 of Embodiment 2 can provide the following effects: Compared with Embodiment 2 and Modification 1 of Embodiment 2, there is an advantage that it is not necessary to provide new signaling, and therefore it is possible to avoid the mobile communication system from becoming complicated.

[0334] Second embodiment, variant 4 When the above-described second embodiment is used, the following problem occurs. Consider a case where there are HeNBs that have the ability to perform line concentration processing and HeNBs that do not have the ability to perform line concentration processing. It is pointless for the MME, SGSN, etc., which are core networks, to execute the processing of the second embodiment to HeNBs that do not have the ability to perform line concentration processing and notify them of the time, period, or resources permitted for communication for MTCD via the S1 interface. Specifically, communication resources from the core network to the HeNBs are wasted, and processing in the core network is wasted.

[0335] The solution in Modification 4 of Embodiment 2 is shown below. The explanation will focus on the parts that differ from the solutions in Embodiments 1 and 2. Parts that are not explained are the same as in Embodiments 1 and 2.

[0336] The HeNB notifies the MME, SGSN, etc., which are the core network, of capability information related to the concentration of data from the MTCD. The core network executes the second embodiment for the HeNB that is capable of concentrating data from the MTCD, and notifies the HeNB of resources for the MTCD.

[0337] Furthermore, the core network may execute the second embodiment only for the HeNB that performs line concentration processing, and may perform notification of the MTCD resource.

[0338] Furthermore, when Variation 2 of the first embodiment is executed, notification of MTCD resources may be performed when the core network instructs the HeNB to start concentration processing. In this case, the MTCD resources may be notified together with the instruction to turn concentration ON. As a specific example of signaling in which the core network instructs the HeNB to turn concentration ON, disclosed in Variation 2 of the first embodiment, the MTCD resources may be added to parameters.

[0339] A specific example of capability information related to line concentration processing notified by the HeNB to the core network is the same as that in Modification 3 of Embodiment 1, and therefore description thereof will be omitted.

[0340] The following five examples (1) to (5) are disclosed as specific examples of timing at which the HeNB notifies the core network of capability information related to line concentration processing.

[0341] (1) When installing a HeNB: If there is no change in the HeNB's ability to perform line concentration processing, it is possible to obtain the effect of preventing communication resources from being wasted.

[0342] (2) Periodic. This is effective when there is a change in the HeNB's ability to perform line concentration processing. In addition, since the capability information is notified periodically, it has the effect of being resistant to communication errors.

[0343] (3) When the capabilities of a HeNB are changed. This is effective when there is a change in the capabilities of a HeNB to perform line concentration processing. Compared to specific example (2), specific example (3) only notifies when the capabilities are changed, and therefore has the advantage of not wasting communication resources.

[0344] (4) When a HeNB starts line concentration processing. Or before the start of line concentration processing. The HeNB may notify that line concentration processing will start as capability information related to line concentration processing. Even if a HeNB has the capability to perform line concentration processing, if there is no MTCD under its umbrella, notification of MTCD resources from the core network is useless. Compared to specific examples (1) to (3), specific example (4) makes it possible for the core network to notify MTCD resources only to HeNBs that actually require MTCD resources. Therefore, this specific example (4) can more effectively utilize communication resources from the core network to the HeNB and can reduce the processing load on the core network.

[0345] (5) When terminating the concentration process, the fact that the concentration process will be terminated may be notified as capability information related to the concentration process. The specific examples (4) and (5) can be used in combination.

[0346] A specific example of signaling when the HeNB notifies the core network of capability information related to line concentration processing is the same as that in Modification 3 of Embodiment 1, and therefore description thereof will be omitted. In this case, when S1 signaling requiring a response message is provided using specific example (2), resources for MTCD may be mapped to the response message. This makes it possible to omit communication procedures, reduce the processing load on the HeNB and the core network, and make effective use of communication resources.

[0347] Furthermore, when using specific example (3) and providing existing S1 signaling that requires an existing response message, resources for MTCD may be mapped to the response message. This makes it possible to omit communication procedures, reduce the processing load on the HeNB and the core network, and effectively utilize communication resources. Specific examples of response messages include "S1 SETUP RESPONSE," "S1 SETUP FAILURE," "ENB CONFIGURATION UPDATE ACKNOWLEDGE," and "eNB Configuration Update FAILURE."

[0348] The following three (1) to (3) are disclosed as specific examples of a method for releasing MTCD resources. (1) A validity period for the MTCD resources is determined in advance. When the validity period has elapsed, the core network releases the MTCD resources. (2) When the core network notifies HeNB of the MTCD resources, it also notifies the validity period of the resources. When the validity period has elapsed, the core network releases the MTCD resources. (3) When the above-mentioned specific example (5) of the timing when the HeNB notifies the core network of capability information related to line concentration processing is used, the core network that receives the notification releases the MTCD resources.

[0349] By using the specific examples (1) to (3) above, the resources for MTCD are released, so that there is no need to secure unnecessary resources. Furthermore, the released communication resources can be used for other communications, for example, communications for normal UEs. This allows for effective use of communication resources.

[0350] In the specific examples (1) and (2), even when the HeNB is performing line concentration processing, the validity period may elapse and the MTCD resources may be released in the core network. Therefore, the HeNB may be configured to be able to request the MTCD resources. As a specific example of signaling when notifying the core network of request information for the MTCD resources, the specific example of signaling when the HeNB disclosed in Modification 3 of the first embodiment notifies the core network of capability information related to line concentration processing can be used, and therefore a description thereof will be omitted.

[0351] A specific example of operation using the third modification of the second embodiment will be described with reference to Fig. 25. Fig. 25 is a diagram showing the sequence of a mobile communication system in the third modification of the second embodiment. In Fig. 25, steps corresponding to those shown in Figs. 17, 20, and 22 are given the same reference numerals, and common descriptions will be omitted.

[0352] In this operation example, the time when a HeNB is installed is disclosed as a specific example of timing when a HeNB notifies a core network of capability information related to line concentration processing. In addition, it is assumed that the HeNB has line concentration processing capability. As a specific example of signaling when a HeNB notifies a core network of capability information related to line concentration processing, a case where an existing S1 signaling, "S1 SETUP REQUEST", is used is disclosed. In addition, it is disclosed that the "S1 SETUP" procedure is successful, and MTCD resources are notified using "S1 SETUP RESPONSE", which is a response message to "S1 SETUP REQUEST".

[0353] In Step ST2001, a HeNB is installed. In Step ST2501, the HeNB notifies the MME of capability information related to the line concentration process of the HeNB. For this notification, an "S1 SETUP REQUEST" is used. The capability information related to the line concentration process is mapped as a parameter of the "S1 SETUP REQUEST".

[0354] In Step ST2003, the MME determines whether or not the HeNB is capable of performing line concentration processing, based on the capability information related to line concentration processing received in Step ST2501. If the MME determines that the HeNB is capable of performing line concentration processing, it moves to Step ST2502. If the MME determines that the HeNB is not capable of performing line concentration processing, it moves to Step ST2503. In this operation example, since the HeNB has line concentration processing capability, it is determined that the HeNB is capable of performing line concentration processing, and moves to Step ST2502.

[0355] In Step ST2502, the MME notifies the HeNB of the resources for MTCD. For this notification, the MME uses "S1 SETUP RESPONSE." The resources for MTCD are mapped as parameters of the "S1 SETUP RESPONSE."

[0356] In Step ST2503, the MME notifies the HeNB of an "S1 SETUP RESPONSE." The MME does not map the MTCD resources as parameters of the "S1 SETUP RESPONSE." That is, the "S1 SETUP RESPONSE" notified to the HeNB in ​​Step ST2503 does not include the MTCD resources.

[0357] Next, in Step ST1703, MTCD_1 performs a process of transmitting an "RRC Connection Request" to HeNB, and in Step ST1704, MTCD_n performs a process of transmitting an "RRC Connection Request" to HeNB. Having received the "RRC Connection Request" transmitted from MTCD_1 and MTCD_n, the HeNB performs the processes of Step ST1705 and Step ST1903 described above. After completing the process of Step ST1903, the HeNB proceeds to Step ST2504.

[0358] In Step ST2504, the HeNB determines whether or not the resources received in Step ST2502 are for the MTCD. If the HeNB determines that the resources are for the MTCD, it moves to Step ST2203, and the HeNB transmits data from the MTCD being served by the HeNB to the core network to the MME using the S1 interface. If the HeNB determines that the resources are not for the MTCD, it repeats the determination process of Step ST2504.

[0359] Although this modified example has been mainly described as an example of combining it with embodiment 1 and embodiment 2, this modified example can also be used in combination with modified example 1 of embodiment 1, modified example 2 of embodiment 1, modified example 3 of embodiment 1, modified example 4 of embodiment 1, modified example 1 of embodiment 2, modified example 2 of embodiment 2, and modified example 3 of embodiment 2.

[0360] This modification can also be used when an eNB holds back and aggregates signaling messages common to an MTCD group, as disclosed in Non-Patent Document 10.

[0361] In addition to the effects of Embodiment 2, Modification 4 of Embodiment 2 can provide the following effects. It is possible to prevent the core network from notifying a HeNB that does not have the ability to perform line concentration processing of MTCD resources. This makes it possible to effectively utilize communication resources from the core network to the HeNB, and also to reduce the processing load on the core network.

[0362] Embodiment 3 In the present embodiment 3, a paging method when executing the embodiment 1 will be disclosed. In the present embodiment 3, a case where a mobile communication system standardized by 3GPP is used as a communication method between a HeNB and an MTCD will be disclosed.

[0363] A specific example of operation using the third embodiment will be described with reference to Fig. 26. Fig. 26 is a diagram showing the sequence of the mobile communication system in the third embodiment. In Fig. 26, steps corresponding to those shown in Fig. 17 are given the same reference numerals, and common descriptions will be omitted.

[0364] In this operation example, a case of NAS signaling will be disclosed as a specific example of data from an MTCD to a core network that performs line concentration processing at a HeNB. Also, a case where an MTCD indicator is mapped to an RRC message "RRC Connection Request" will be disclosed as a specific example of a method in which a HeNB distinguishes whether a mobile terminal (UE) being served by the HeNB is an MTCD or not an MTCD.

[0365] First, in Step ST1703, MTCD_1 performs a process of transmitting an "RRC Connection Request" to HeNB, and in Step ST1704, MTCD_n performs a process of transmitting an "RRC Connection Request" to HeNB. Having received the "RRC Connection Request" transmitted from MTCD_1 and MTCD_n, HeNB performs the processes of Step ST1705 and Step ST1707 described above. After completing the process of Step ST1707, it proceeds to Step ST2601.

[0366] In this operation example, after the process of step ST1703, processes corresponding to steps ST1705, ST1707 and ST2202 are performed, but for ease of understanding, the description thereof is omitted.

[0367] Also, if it is determined in step ST1705 that the data is not from the MTCD, this is not an essential part of the present embodiment, and therefore the description will be omitted and the process will end.

[0368] In Step ST2601, MTCD_1 transmits an attach message including the identifier of MTCD_1 to HeNB. Details of the attach method are disclosed in Non-Patent Document 13. In Step ST2602, MTCD_n transmits an attach message including the identifier of MTCD_n to HeNB.

[0369] In Step ST2603, the HeNB performs concentration processing on the attach message from MTCD_1 received in Step ST2601 and the attach message from MTCD_n received in Step ST2602. In this operation example, as concentration processing, attach messages, which are data from multiple MTCDs to the core network, are notified to the MME collectively.

[0370] In Step ST2604, the HeNB notifies the MME of the attach message concentrated by performing the concentration process in Step ST2603. The attach message includes the identifier of MTCD_1 and the identifier of MTCD_n, which are identifiers of the MTCDs that are targets of the concentration process, the identifier of the HeNB, and the TAI. As a method of notifying the attach message, the second embodiment, the first modification of the second embodiment, the second modification of the second embodiment, and the third modification of the second embodiment can be used.

[0371] In Step ST2605, the MME notifies the HSS (Home Subscriber Server) of the identifier of MTCD_1 and the identifier of MTCD_n, which are the identifiers of the MTCDs received as the attach message. The HSS is a subscriber information database in a 3GPP mobile communication network, and is an entity that manages authentication information and location information.

[0372] In Step ST2606, the HSS registers and manages the identifiers of the MTCDs that have undergone the attach process, ie, the identifier of MTCD_1 and the identifier of MTCD_n.

[0373] It is assumed that, in Step ST2607, the MME receives an incoming call addressed to MTCD_1. Detailed methods for receiving an incoming call are disclosed in Non-Patent Document 13 and Non-Patent Document 14. The incoming call includes the identifier of MTCD_1. This allows the call to be received by MTCD_1 alone.

[0374] In Step ST2608, the MME searches the tracking area list (also referred to as a TAI list) of MTCD_1.

[0375] In Step ST2609, the MME notifies the HeNB of a paging addressed to MTCD_1. The paging includes a tracking area list of MTCD_1 and an identifier of MTCD_1. By including the identifier of MTCD_1, the paging can be received by MTCD_1 alone.

[0376] In Step ST2610, the HeNB determines whether or not the tracking area included in the tracking area list (TAI List) of MTCD_1 included in the paging received in Step ST2609 is included in the tracking area of ​​the HeNB. If the HeNB determines that the tracking area of ​​the HeNB is included, the HeNB proceeds to Step ST2611. If the HeNB determines that the tracking area of ​​the HeNB is not included, the HeNB does not perform the process of Step ST2611.

[0377] In Step ST2611, the HeNB notifies MTCD_1 of a paging message addressed to MTCD_1. Paging is notified in a mobile communication system standardized by 3GPP. Specifically, the paging message is mapped to the PCCH, which is a logical channel, the PCCH is mapped to the PCH, which is a transport channel, and the PCH is mapped to the PDSCH, which is a physical channel. A paging indicator common to all mobile terminals is transmitted on the PDCCH. Resources for the PDSCH, to which the paging message is mapped, are allocated by the PDCCH, to which the paging indicator is transmitted. Detailed methods for notifying paging are disclosed in Non-Patent Document 1, Non-Patent Document 2, and Non-Patent Document 16.

[0378] In this embodiment, examples of combinations with embodiment 1, embodiment 2, variant 1 of embodiment 2, variant 2 of embodiment 2, and variant 3 of embodiment 2 have mainly been described, but it can also be used in combination with variant 1 of embodiment 1, variant 2 of embodiment 1, variant 3 of embodiment 1, and variant 4 of embodiment 2.

[0379] In the above-described third embodiment, the first embodiment is executed, and a paging method when a mobile communication system standardized by 3GPP is used as a communication method between a HeNB and an MTCD is disclosed. By executing the third embodiment, paging can be realized when a mobile communication system standardized by 3GPP is used.

[0380] Embodiment 4 In the present embodiment 4, a paging method when executing the embodiment 1 will be disclosed. In the present embodiment 4, a case will be disclosed in which a communication system other than the mobile communication system standardized by 3GPP is used as a communication method between a HeNB and an MTCD.

[0381] The solution in the fourth embodiment is shown below. The explanation will focus on the parts that are different from the solution in the first embodiment. The parts that are not explained are the same as those in the first embodiment.

[0382] The HeNB concentrates data from MTCDs that have accessed using a communication system other than the mobile communication system standardized by 3GPP, and notifies the MME, which is a core network, or the SGSN, or the MTC server, etc., using the protocol of the mobile communication system standardized by 3GPP. The HeNB stores the identifier of the MTCD that has performed the concentration process, and when it receives a paging message from the MME that includes the identifier of the MTCD that has performed the concentration process, it notifies the MTCD under its control of the incoming call.

[0383] The following three (1) to (3) are disclosed as specific examples of line concentration processing. (1) Access from a communication system other than the mobile communication system standardized by 3GPP is converted into a protocol for the mobile communication system standardized by 3GPP. When there is access from a communication system other than the mobile communication system standardized by 3GPP, the access content is interpreted, a protocol for the mobile communication system standardized by 3GPP that is appropriate for the access content is selected, and parameters required for the protocol are notified to the core network, such as the MME, SGSN, or MTC server. (2) Data to the core network from one or multiple MTCDs is notified to the MME collectively. This reduces the number of communications from the HeNB to the core network, thereby alleviating congestion in the core network. (3) A combination of (1) and (2).

[0384] Regarding specific examples of line concentration processing, when the above specific example (1) is selected, the following eight examples (a) to (h) are disclosed as specific examples of combinations of access contents by a communication system other than a mobile communication system standardized by 3GPP and protocols of a mobile communication system standardized by 3GPP that are suited to the access contents. In the following explanation, a communication system other than a mobile communication system standardized by 3GPP will be referred to as "non-3GPP," and a mobile communication system standardized by 3GPP will also be referred to as "within 3GPP."

[0385] (a) If MTCD power ON is notified by a method other than 3GPP, the "Attach procedure" is selected within 3GPP. Details of the "Attach procedure" are disclosed in Non-Patent Document 13. (b) If MTCD installation is notified by a method other than 3GPP, the "Attach procedure" is selected within 3GPP. (c) If MTCD location registration is notified by a method other than 3GPP, the "Attach procedure" is selected within 3GPP. (d) If MTCD movement is notified by a method other than 3GPP, the "Tracking Area Update procedure" is selected within 3GPP. Details of the "Tracking Area Update procedure" are disclosed in Non-Patent Document 13. (e) If an MTCD communication request, call request, or call response is notified by a method other than 3GPP, the "Service Request procedure" is selected within 3GPP. Details of the "Service Request procedure" are disclosed in Non-Patent Document 13. (f) If MTCD power OFF is notified by a method other than 3GPP, the "Detach procedure" is selected within 3GPP. Details of the "Detach procedure" are disclosed in Non-Patent Document 13. (g) If the MTCD removal is notified outside of 3GPP, select the "Detach procedure" within 3GPP. (h) If the MTCD failure is notified outside of 3GPP, select the "Detach procedure" within 3GPP.

[0386] As a specific example of the line concentration process, when the above-mentioned specific example (1) is selected, the following four examples (a) to (d) are disclosed as specific examples of parameters required for the protocol.

[0387] (a) When "Attach procedure" is selected in 3GPP, the following (a1) to (a4) are used: (a1) MTCD identifier (a2) HeNB identifier (a3) ​​HeNB tracking area (a4) A combination of the above (a1) to (a3).

[0388] (b) When the "Tracking Area Update procedure" is selected in 3GPP, the following (b1) to (b4) are used: (b1) MTCD identifier (b2) HeNB identifier (b3) Tracking area of ​​HeNB (b4) A combination of the above (b1) to (b3).

[0389] (c) If "Service Request procedures" is selected, the following (c1) to (c4) will be provided: (c1) MTCD identifier. (c2) HeNB identifier. (c3) HeNB tracking area. (c4) A combination of the above (c1) to (c3).

[0390] (d) If "Detach procedure" is selected, (d1) the MTCD identifier.

[0391] A specific example of operation using the fourth embodiment will be described with reference to Fig. 27. Fig. 27 is a diagram showing the sequence of the mobile communication system in the fourth embodiment. In Fig. 27, steps corresponding to those shown in Fig. 17 and Fig. 26 are given the same reference numerals, and common descriptions will be omitted.

[0392] In this operation example, as a specific example of line concentration processing, a case where a combination of specific example (1) and specific example (2) is used, which is the above-mentioned specific example (3), is disclosed. In addition, as a specific example of a combination of access content other than by 3GPP and a protocol within 3GPP that suits the access content, a case where MTCD installation is notified by a protocol other than 3GPP and a case where "Attach procedure" is selected within 3GPP are disclosed. In addition, as a specific example of parameters required for the "Attach procedure" when switching access other than by 3GPP to a protocol within 3GPP, a case where (a1) the MTCD identifier, (a2) the HeNB identifier, and (a3) ​​the tracking area of ​​the HeNB in ​​the above-mentioned specific example (a) are disclosed.

[0393] In Step ST2701, MTCD_1 transmits an MTCD installation notification including the identifier of MTCD_1 to HeNB.

[0394] In Step ST2702, the MTCD_n transmits an MTCD installation notification including the identifier of the MTCD_n to the HeNB.

[0395] In Step ST2703, the HeNB checks whether or not the MTCD installation notification including the identifier of the MTCD_n in Step ST2702 has been received by a method other than 3GPP, and determines whether or not the MTCD installation notification is data from the MTCD. When determining that the MTCD installation notification including the MTCD identifier has been received by a method other than 3GPP, the HeNB determines that the data is from the MTCD, and proceeds to Step ST2704. When determining that the MTCD installation notification including the MTCD identifier has not been received by a method other than 3GPP, the HeNB determines that the data is not from the MTCD, and as this is not an essential part of the present embodiment, description thereof will be omitted and the processing ends.

[0396] Furthermore, when the data is received outside 3GPP without checking whether the MTCD identifier is included, it may be determined that the data is from an MTCD and proceed to step ST2704. When the data is received within 3GPP, it may be determined that the data is from a normal UE, and since this is not an essential part of the present embodiment, the description may be omitted and the processing may be terminated.

[0397] In Step ST2704, the HeNB stores the identifiers of the MTCDs that perform the concentration process. In this operation example, the HeNB stores the identifiers of MTCD_1 and MTCD_n.

[0398] In Step ST2705, the HeNB performs line concentration processing. In this operation example, the HeNB collectively notifies the MME of data to be transmitted to the core network from MTCD_1 and MTCD_n. The HeNB also interprets the contents of Steps ST2701 and ST2702, which are accesses other than those of 3GPP, and understands that the access is related to "installation." Next, the HeNB selects "Attach procedure" as a protocol within 3GPP that is appropriate for accesses related to "installation." The HeNB also maps, as parameters to the "Attach procedure," the identifier of MTCD_1 received in Step ST2701, the identifier of MTCD_n received in Step ST2702, the identifier of its own HeNB, and the tracking area of ​​the HeNB.

[0399] In this operation example, after the process of step ST2701, processes corresponding to steps ST2703, ST2704 and ST2705 are performed, but for ease of understanding, the description thereof is omitted.

[0400] In Step ST2706, the HeNB notifies the MME of the attach message concentrated by performing the concentration process in Step ST2705. The attach message includes the identifier of MTCD_1 and the identifier of MTCD_n, which are identifiers of the MTCDs that are targets of the concentration process, the identifier of the HeNB, and the TAI. For this notification, the second embodiment, the first modification of the second embodiment, the second modification of the second embodiment, and the third modification of the second embodiment can be used.

[0401] After the process of Step ST2706, the MME performs the process of Step ST2605, and the HSS performs the process of Step ST2606. Next, the MME receives the incoming call addressed to MTCD_1 in Step ST2607, and the MME performs the processes of Step ST2608 and Step ST2609.

[0402] Next, in Step ST2707, the HeNB judges whether or not it has performed concentration processing for MTCD_1 included in the paging received in Step ST2609. The HeNB may use the information stored in Step ST2704 to judge whether or not to perform the processing in Step ST2707. If it is determined that concentration processing has been performed, the HeNB proceeds to Step ST2708. If it is determined that concentration processing has not been performed, the HeNB proceeds to Step ST2709. In this operation example, the HeNB has performed concentration processing for MTCD_1, and therefore proceeds to Step ST2708.

[0403] In Step ST2708, the HeNB notifies MTCD_1 of an incoming call addressed to MTCD_1. The notification of the incoming call in Step ST2708 is performed using a communication system other than the 3GPP used in Step ST2701. In Step ST2709, the HeNB determines whether or not the HeNB is included in the tracking area included in the tracking area list of MTCD_1 included in the paging received in Step ST2609. If it is determined that the HeNB is included, it proceeds to Step ST2710. If it is determined that the HeNB is not included, it does not perform the process of Step ST2710. In Step ST2710, the HeNB performs notification of the incoming call using a communication system within 3GPP.

[0404] In this embodiment, examples of combinations with embodiment 1, embodiment 2, variant 1 of embodiment 2, variant 2 of embodiment 2, and variant 3 of embodiment 2 have mainly been described, but it can also be used in combination with variant 1 of embodiment 1, variant 2 of embodiment 1, variant 3 of embodiment 1, and variant 4 of embodiment 2.

[0405] Furthermore, in the present embodiment, a case has been described in which the communication method between the HeNB and the MTCD is other than 3GPP, but the present embodiment can also be used in cases in which the communication method between the HeNB and the MTCD is within 3GPP.

[0406] In the above-described fourth embodiment, the first embodiment is executed, and a paging method when a communication system other than a mobile communication system standardized by 3GPP is used as a communication method between a HeNB and an MTCD is disclosed. By executing the fourth embodiment, paging can be executed when a communication system other than a mobile communication system standardized by 3GPP is used.

[0407] Fourth embodiment, variant 1 When the above-described fourth embodiment is used, the following problem occurs. Even when the MTCD moves and communication with the MTC server via the HeNB becomes impossible, the identifier of the MTCD continues to be stored as the MTCD that performed line concentration processing within the HeNB. This causes a problem that the storage area of ​​the HeNB is used for unnecessary data.

[0408] As solutions in Modification 1 of Embodiment 4, the following two (1) and (2) are disclosed. (1) When an MTCD moves and communication with the MTC server via a HeNB becomes impossible, the MTCD notifies the HeNB of that effect. When the MTCD moves, it notifies the source HeNB of that effect. The HeNB that receives the notification deletes the MTCD from the memory of the MTCD that performed the line concentration process.

[0409] (2) When the MTCD moves and communication with the MTC server via the HeNB becomes impossible, the MTCD notifies the core network to that effect via the HeNB. When the MTCD moves, it notifies the core network to that effect via the source HeNB. The core network that receives the notification determines whether to change the source cell of the MTCD. If the core network decides to change the source cell, it notifies the HeNB that the source cell will be changed. The HeNB that receives the notification deletes the MTCD from the memory of the MTCD that performed line concentration processing. The notification of the change of source cell from the core network to the HeNB includes the identifier of the MTCD.

[0410] The following three items (1) to (3) are disclosed as specific examples of the content notified from an MTCD to a HeNB: (1) To move. (2) To change the serving cell. (3) To perform handover.

[0411] In addition to the effects of Embodiment 4, Modification 1 of Embodiment 4 can provide the following effects. When an MTCD moves and communication with the MTC server via a HeNB becomes impossible, that is, when the HeNB is no longer able to perform line concentration processing for the MTCD, it becomes possible to delete the data of the MTCD from the storage area of ​​the HeNB. This makes it possible to prevent the storage area of ​​the HeNB from being used for useless data.

[0412] Embodiment 5. In the fifth embodiment, a paging method when the first embodiment is executed will be disclosed. In the fifth embodiment, a paging method for each HeNB will be disclosed, instead of paging for each MTCD. It may be paging for each HeNB that has performed line concentration processing.

[0413] The solution in the fifth embodiment is shown below. The explanation will focus on the parts that are different from the solution in the first embodiment. The parts that are not explained are the same as those in the first embodiment.

[0414] Registration with an operator or MTC user is not performed for each MTCD individually, but for each HeNB that performs line concentration processing. Here is an example of the service format. A contract is made for each HeNB installed in a home as an MTCD. Even if there are multiple MTCDs under a HeNB, there will be one contract for the HeNB. Registration is made to the core network on a HeNB basis that performs line concentration processing, and paging is sent to the HeNB. When a HeNB receives a paging, it notifies all MTCDs under its control of the call.

[0415] A specific example of the concentration process is disclosed below. In addition to the specific examples (1) to (4) disclosed in the first embodiment, the operation of the following specific example (5) is performed. (5) The identifier of the MTCD included in the data from the served MTCD to the core network is deleted, and the identifier of the own HeNB is mapped instead. In the case of a message that has already had the identifier of the HeNB added and notified to the core network, it is sufficient to simply delete the identifier of the MTCD.

[0416] A specific example of a method for registration to a core network is disclosed below. The MME notifies the HSS of the identifier of the HeNB that has concentrated data from the MTCD to the core network, rather than the identifier of the MTCD. The HSS registers the identifier of the HeNB that has concentrated data, rather than the identifier of the MTCD.

[0417] The following two methods (1) and (2) are disclosed as specific examples of a HeNB notifying all MTCDs under its control of an incoming call. (1) Using broadcast information. (2) Using group calling.

[0418] A specific example of operation using the fifth embodiment will be described with reference to Fig. 28. Fig. 28 is a diagram showing the sequence of the mobile communication system in the fifth embodiment. In Fig. 28, steps corresponding to those shown in Fig. 17 and Fig. 26 are given the same reference numerals, and common explanations will be omitted.

[0419] In this operation example, a case of NAS signaling is disclosed as a specific example of data from an MTCD that performs line concentration processing at a HeNB to a core network. Also, as a specific example of a method in which a HeNB distinguishes whether a mobile terminal (UE) served by the HeNB is an MTCD or not, a case in which an MTCD indicator is mapped to an RRC message "RRC Connection Request" is disclosed. Also, as a specific example in which a HeNB notifies all MTCDs served by the HeNB of an incoming call, a case in which broadcast information is used is disclosed.

[0420] First, MTCD_1 performs the process of step ST1703, and MTCD_n performs the process of step ST1704. Next, the HeNB that receives the "RRC Connection Request" transmitted from MTCD_1 and MTCD_n performs the process of step ST1705 and step ST1707. Next, MTCD_1 performs the process of step ST2601, and MTCD_n performs the process of step ST2602.

[0421] Next, in Step ST2801, the HeNB performs concentration processing on the attach message from MTCD_1 received in Step ST2601 and the attach message from MTCD_n received in Step ST2602. In this operation example, as concentration processing, attach messages, which are data from a plurality of MTCDs to the core network, are collectively notified to the MME. At that time, the identifiers of MTCD_1 and MTCD_n, which are MTCD identifiers included in the data from the served MTCDs to the core network, are not notified to the MME. Instead of notifying the MTCD identifiers, the HeNB notifies the MME of its own identifier. However, the identifier of the HeNB itself is a parameter notified in the "Attach procedure" from an eNB to an MME in the current standard (see Non-Patent Document 13). In Step ST2801 of this operation example, it is also possible to simply delete the MTCD identifier from the attach message received from the served MTCD.

[0422] In Step ST2802, the HeNB notifies the MME of the attach message concentrated by performing the concentration process in Step ST2801. The attach message does not include the identifier of MTCD_1 and the identifier of MTCD_n, which are identifiers of the MTCDs that are targets of the concentration process, but includes the identifier of the HeNB and the TAI. Notification of the TAI is optional. For the notification in Step ST2802, the second embodiment, the first modification of the second embodiment, the second modification of the second embodiment, or the third modification of the second embodiment can be used.

[0423] In Step ST2803, the MME notifies the HSS of the identifier of the HeNB received in the attach message. In Step ST2804, the HSS registers and manages the HeNB that has been attached.

[0424] It is assumed that, in Step ST2805, the MME receives an incoming call addressed to a HeNB. Detailed methods for receiving an incoming call are disclosed in Non-Patent Document 13 and Non-Patent Document 14. The incoming call includes an identifier of the HeNB. This enables the MME to receive an incoming call on a HeNB basis.

[0425] In Step ST2806, the MME determines whether or not a HeNB is served by the MME. If it determines that a HeNB is served by the MME, it proceeds to Step ST2807, and if it determines that a HeNB is not served by the MME, it terminates the process. In this operation example, since a HeNB is served by the MME, the MME proceeds to Step ST2807. In Step ST2807, the MME may notify the base stations served by the MME, such as eNBs and HeNBs, of paging without performing the process of Step ST2806.

[0426] In Step ST2807, the MME notifies the HeNB of a paging addressed to the HeNB. The paging does not include the tracking area list of MTCD_1, the identifier of MTCD_1, and the "UE identity index value." The "UE identity index value" will be described in embodiment 6, which will be described later. Instead of including the tracking area list of MTCD_1 and the identifier of MTCD_1, the identifier of the HeNB is included. Including the identifier of the HeNB allows the message to be received on a HeNB-by-HeNB basis.

[0427] In Step ST2808, the HeNB judges whether or not the identifier included in the paging received in Step ST2807 is an identifier of the HeNB. If the HeNB judges that it is an identifier of the HeNB, it moves to Step ST2809. If the HeNB judges that it is not an identifier of the HeNB, it judges that it is an identifier of the UE, and moves to Step ST2610. In this operation example, the identifier included in the paging received in Step ST2807 is an identifier of the HeNB, and therefore moves to Step ST2809.

[0428] In Step ST2809, the HeNB judges whether or not the identifier of the HeNB included in the paging received in Step ST2807 is the identifier of its own HeNB. If it is judged to be the identifier of its own HeNB, it proceeds to Step ST2810. If it is judged not to be the identifier of its own HeNB, it terminates the processing. In this operation example, the identifier of the HeNB included in the paging received in Step ST2807 is the identifier of its own HeNB, and therefore it proceeds to Step ST2810.

[0429] In Step ST2810, the HeNB notifies all MTCDs being served by the HeNB of the incoming call by using broadcast information.

[0430] In Step ST2811, the HeNB notifies the mobile terminal of a paging message including a mobile terminal identifier as usual. The paging message is notified in a mobile communication system standardized by 3GPP. Specifically, the paging message is mapped to the PCCH, which is a logical channel, the PCCH is mapped to the PCH, which is a transport channel, and the PCH is mapped to the PDSCH, which is a physical channel. A paging indicator common to all mobile terminals is transmitted on the PDCCH. Resources for the PDSCH, to which the paging message is mapped, are allocated by the PDCCH, to which the paging indicator is transmitted. Detailed methods for notifying the paging message are disclosed in Non-Patent Document 1, Non-Patent Document 2, and Non-Patent Document 16.

[0431] In this embodiment, examples of combinations with embodiment 1, embodiment 2, variant 1 of embodiment 2, variant 2 of embodiment 2, and variant 3 of embodiment 2 have mainly been described, but it can also be used in combination with variant 1 of embodiment 1, variant 2 of embodiment 1, variant 3 of embodiment 1, and variant 4 of embodiment 2.

[0432] Furthermore, in the embodiment, a case has been described in which the communication method between the HeNB and the MTCD is within 3GPP, but the embodiment can also be used in cases in which the communication method between the HeNB and the MTCD is other than 3GPP.

[0433] In the above-described fifth embodiment, the first embodiment is executed, and a paging method for each HeNB is disclosed, instead of paging for each MTCD. By executing the fifth embodiment, paging for each HeNB can be realized.

[0434] Fifth embodiment, variant 1 In a first variant of the fifth embodiment, a method of paging each MTCD will be disclosed, even when the fifth embodiment is executed and registration with an operator or an MTC user is not performed for each MTCD individually but is performed for each HeNB that performs line concentration processing.

[0435] The solution in Modification 1 of Embodiment 5 is shown below. The explanation will focus on the parts that differ from the solutions in Embodiments 1 and 5. Parts that are not explained are the same as in Embodiments 1 and 5.

[0436] The HeNB stores the identifier of the MTCD that performed the line concentration process, and when it receives a paging message including the identifier of the MTCD separately from the identifier of the HeNB from the MME, it notifies the MTCD under its control of the incoming call.

[0437] A specific example of operation using the first modification of the fifth embodiment will be described with reference to Fig. 29. Fig. 29 is a diagram showing the sequence of a mobile communication system in the first modification of the fifth embodiment. In Fig. 29, steps corresponding to those shown in Figs. 17, 26, and 28 are given the same reference numerals, and common descriptions will be omitted.

[0438] In this operation example, a case of NAS signaling will be disclosed as a specific example of data from an MTCD to a core network that performs line concentration processing at a HeNB. Also, a case where an MTCD indicator is mapped to an RRC message "RRC Connection Request" will be disclosed as a specific example of a method in which a HeNB distinguishes whether a mobile terminal (UE) being served by the HeNB is an MTCD or not an MTCD.

[0439] First, MTCD_1 performs the process of step ST1703, and MTCD_n performs the process of step ST1704. Next, the HeNB that receives the "RRC Connection Request" transmitted from MTCD_1 and MTCD_n performs the process of step ST1705 and step ST1707. Next, MTCD_1 performs the process of step ST2601, and MTCD_n performs the process of step ST2602. Next, the HeNB that receives the attach message transmitted from MTCD_1 and MTCD_n performs the processes of step ST2704, step ST2801, and step ST2802. Next, the MME performs the process of step ST2803, and the HSS performs the process of step ST2804.

[0440] It is assumed that, in Step ST2901, the MME receives an incoming call addressed to a HeNB. Detailed methods for receiving an incoming call are disclosed in Non-Patent Document 13 and Non-Patent Document 14. The incoming call includes the identifier of the MTCD_1 to be individually called, in addition to the identifier of the HeNB. This makes it possible to perform paging for each MTCD, even if registration with an operator or the like is not performed for each MTCD, but is performed for each HeNB that performs line concentration processing. The MME performs the process of Step ST2901, and then the process of Step ST2806. If, in Step ST2806, the MME determines that a HeNB exists under its own MME, it proceeds to Step ST2902.

[0441] In Step ST2902, the MME notifies the HeNB of a paging addressed to the HeNB. The paging includes the identifier of MTCD_1 but does not include the tracking area list of MTCD_1. The HeNB performs the processes of Steps ST2808 and ST2809. In Step ST2809, if the HeNB determines that the identifier of the HeNB included in the paging received in Step ST2902 is its own identifier, it moves to Step ST2903.

[0442] In Step ST2903, the HeNB judges whether or not it has performed concentration processing for MTCD_1 whose identifier is included in the paging received in Step ST2902. For the judgment in Step ST2903, the HeNB may use the information stored in Step ST2704. If it is determined that concentration processing has been performed, the HeNB proceeds to Step ST2611. If it is determined that concentration processing has not been performed, the HeNB terminates the processing.

[0443] In this variant, examples of combinations with embodiment 1, embodiment 2, variant 1 of embodiment 2, variant 2 of embodiment 2, and variant 3 of embodiment 2 have mainly been described, but it can also be used in combination with variant 1 of embodiment 1, variant 2 of embodiment 1, variant 3 of embodiment 1, and variant 4 of embodiment 2.

[0444] Furthermore, in this modification, a case has been described in which the communication method between the HeNB and the MTCD is within 3GPP, but this modification can also be used when the communication method between the HeNB and the MTCD is other than 3GPP.

[0445] The above-described first modification of the fifth embodiment discloses a method of executing the fifth embodiment in addition to the first embodiment, and performing paging for each MTCD even when registration with an operator or an MTC user is not performed for each MTCD but is performed for each HeNB that performs line concentration. By executing the first modification of the fifth embodiment, paging for each MTCD can be realized when registration with an operator or an MTC user is performed for each HeNB that performs line concentration.

[0446] Embodiment 6 The problem to be solved in the sixth embodiment will be described below. In the fifth embodiment, when the HeNB uses broadcast information to notify all MTCDs under its control of an incoming call, the radio section, that is, the section between the HeNB and the MTCD, is different from normal paging transmission. During paging from the MME to the HeNB, parameters used to set the radio section are present. Therefore, there are unnecessary parameters, which results in wasted resources.

[0447] The solution in the sixth embodiment is shown below. The explanation will focus on the parts that are different from the solutions in the first and fifth embodiments. The parts that are not explained are the same as those in the first and fifth embodiments.

[0448] When paging is performed for each HeNB instead of for each MTCD, the paging message from the MME to the HeNB is made to differ from the current standard (see Non-Patent Document 14). When the received incoming call includes a HeNB identifier instead of an MTCD identifier, the MME makes the paging message from the MME to the HeNB differ from the current standard.

[0449] As specific examples of paging messages that differ from the current standard, the following two examples (1) and (2) are disclosed.

[0450] (1) A new paging message for each HeNB is provided. Alternatively, a paging message is provided when a new line concentration process is performed. A specific example of a parameter included in the new message is a HeNB identifier.

[0451] (2) The existing S1 signaling "Paging" is used for paging on a HeNB basis. The existing S1 signaling "Paging" is used for paging when line concentration processing is performed.

[0452] Next, we will explain the parameters that need to be added or changed to "Paging." A specific example of a parameter that needs to be added is the HeNB identifier. The following three (a) to (c) are disclosed as specific examples of parameters that need to be changed.

[0453] (a) "UE Identity Index value". In the current standard, the "UE Identity Index value" is used to calculate the "Paging Frame (PF)", which is the radio frame with which the eNB transmits paging. When a HeNB notifies an MTCD under its control of an incoming call using broadcast information, the HeNB does not need to calculate the radio frame with which the paging is transmitted. Therefore, a situation occurs in which it is impossible to specify the "UE Identity Index value" in the mobile communication system. Furthermore, in the current standard, the "UE Identity Index value" must be mapped to "Paging". In other words, if paging per HeNB is transmitted using the current "Paging" rather than paging per MTCD, a problem occurs in which the handling of the "UE Identity Index value" is not standardized in the mobile communication system. If standardization is not achieved in the mobile communication system, problems such as the inability to provide a stable communication network occur. Therefore, for example, if the HeNB identifier is mapped to "Paging", it is determined that paging is per HeNB, and even if the "UE Identity Index value" is mapped, it is treated as an invalid parameter on the receiving side, or mapping on the transmitting side is not required but is made optional. This clarifies the processing of MME and HeNB, making it possible to build a unified mobile communications network and provide a stable communications network.

[0454] (b) "UE Paging Identity". In the current standard, "UE Paging Identity" is the identifier of the mobile terminal being called. When a HeNB notifies all MTCDs under its control of an incoming call using broadcast information, the HeNB does not need an individual identifier of the MTCD, which is a type of mobile terminal. It is also assumed that an individual identifier of the MTCD will not be notified from the calling side. Therefore, a situation arises in which it is impossible to specify "UE Paging Identity" in the mobile communication system. Furthermore, in the current standard, "UE Paging Identity" must always be mapped to "Paging". In other words, if paging is sent per HeNB using the current "Paging" rather than per MTCD, a problem occurs in that the handling of "UE Paging Identity" will not be standardized as a mobile communication system. If there is no standardization as a mobile communication system, problems such as the inability to provide a stable communication network will arise. Therefore, for example, if a HeNB identifier is mapped to "Paging," it is determined that the paging is for each HeNB, and even if "UE Paging Identity" is mapped, it is treated as an invalid parameter on the receiving side, or mapping on the transmitting side is made optional rather than mandatory. This clarifies the processing of MME and HeNB, enables the construction of a unified mobile communication network, and enables the provision of a stable communication network.

[0455] (c) "TA information". In the current standard, an eNB belonging to the TA information transmits paging for "TA information". When a HeNB notifies an MTCD under its control of an incoming call using broadcast information, the paging includes an identifier of the HeNB. As a result, a HeNB whose identifier matches the HeNB identifier included in the paging may notify an MTCD under its control of the incoming call. Therefore, "TA information" is not a particularly necessary parameter. On the other hand, in the current standard, "TA information" must be mapped to "Paging". In other words, when paging per HeNB, rather than paging per MTCD, is transmitted using the current "Paging", the unnecessary parameter "TA information" is notified. Therefore, for example, if a HeNB identifier is mapped to "Paging", it is determined that the paging is per HeNB, and mapping of "TA information" on the transmitting side is made optional rather than mandatory. This makes it possible to prevent the transmission of unnecessary parameters.

[0456] According to the sixth embodiment, in addition to the effects of the fifth embodiment, the following effects can be obtained: It is possible to reduce unnecessary parameters during paging from an MME to a HeNB, and it is possible to use resources effectively.

[0457] Embodiment 7 The problem to be solved in the seventh embodiment will be described below. First, the current paging method will be described. Non-Patent Document 14 discloses the following: In each cell belonging to a tracking area indicated in the TAI List included in the paging message notified from the MME to the eNB, paging is generated on the radio interface.

[0458] The current paging method will be described again using Figure 30. Figure 30 is a diagram showing locations for explaining the current paging method. First, the locations in Figure 30 will be described. eNB3001, HeNB3003, HeNB3005, and HeNB3007 are installed. eNB3001 has coverage 3002. HeNB3003 has coverage 3004. HeNB3005 has coverage 3006. HeNB3007 has coverage 3008. Mobile terminal 3009 exists within coverage 3008 of HeNB3007. eNB3001, HeNB3003, HeNB3005, and HeNB3007 exist within coverage 3002 of eNB3001. Tracking area #1 (TA#1) 3016 includes eNB3001, HeNB3003, HeNB3005, and HeNB3007.

[0459] Also, eNB3010, HeNB3012, and HeNB3014 are installed. eNB3010 has coverage 3011. HeNB3012 has coverage 3013. HeNB3014 has coverage 3015. eNB3010, HeNB3012, and HeNB3014 exist within coverage 3011 of eNB3010. Tracking area #2 (TA#2) 3017 includes eNB3010, HeNB3012, and HeNB3014.

[0460] Consider a case where tracking area #1 (TA#1) 3016 and tracking area #2 (TA#2) 3017 are registered in the tracking area list of mobile terminal 3009. The current paging method when an incoming call occurs to mobile terminal 3009 at the location will be described.

[0461] In the current standard, paging is generated over the radio interface in each cell belonging to a tracking area indicated in the TAI List included in a paging message notified from the MME to the eNB. Therefore, paging is generated over the radio interface from eNB3001, HeNB3003, HeNB3005, and HeNB3007 belonging to tracking area #1 (TA#1) 3016, and eNB3010, HeNB3012, and HeNB3014 belonging to tracking area #2 (TA#2) 3017. Meaningless paging transmissions have the conventional problem of not being able to effectively utilize radio resources and causing interference.

[0462] Next, a problem to be solved in the seventh embodiment will be described below. Consider a case where there are HeNBs that have the ability to perform line concentration processing and HeNBs that do not have the ability to perform line concentration processing. When the third and fourth embodiments described above are executed, a paging notification or an incoming call notification from a HeNB that does not have the ability to perform line concentration processing to an MTCD becomes useless. This causes a problem that radio resources cannot be used effectively.

[0463] Waste of radio resources when the above-described third embodiment is executed will be described with reference to Figures 31 and 32. Figures 31 and 32 are diagrams showing sequences of a mobile communication system for explaining waste of radio resources when the third embodiment is executed. Figures 31 and 32 are connected at the position of boundary line L1. In Figures 31 and 32, steps corresponding to those shown in Figures 17 and 26 are given the same reference numerals, and common descriptions will be omitted.

[0464] This operation example will be described using the location diagram shown in Fig. 30. It is assumed that HeNB3003 and HeNB3007 are HeNBs capable of performing line concentration processing, and HeNB3005 is a HeNB that does not have the ability to perform line concentration processing. The mobile terminal 3009 is an MTCD, and the identifier of the MTCD is MTCD_1.

[0465] First, MTCD_1 performs the process of step ST1703, and MTCD_n performs the process of step ST1704. Next, HeNB3007, which has received the "RRC Connection Request" transmitted from MTCD_1 and MTCD_n, performs the processes of step ST1705 and step ST1707. Next, MTCD_1 performs the process of step ST2601, and MTCD_n performs the process of step ST2602. Next, HeNB3007, which has received the attach message transmitted from MTCD_1 and MTCD_n, performs the processes of step ST2603 and step ST2604. Next, the MME performs the process of step ST2605. Next, the HSS performs the process of step ST2606.

[0466] In Step ST2607, after the MME receives an incoming call addressed to MTCD_1, in Step ST2608, the MME searches the tracking area list (also referred to as a TAI list) of MTCD_1. In this operation example, the MME finds that the tracking area list of MTCD_1 includes tracking area #1 (TA#1) 3016 and tracking area #2 (TA#2) 3017.

[0467] In Step ST3101, the MME notifies the HeNB 3007 of a paging addressed to the MTCD_1. The paging includes a tracking area list of the MTCD_1 and an identifier of the MTCD_1.

[0468] In Step ST3102, the MME notifies the HeNB 3005 of a paging message addressed to the MTCD_1. The paging message includes a tracking area list of the MTCD_1 and an identifier of the MTCD_1.

[0469] In Step ST3103, the MME notifies HeNB 3003 of a paging addressed to MTCD_1. The paging includes a tracking area list of MTCD_1 and an identifier of MTCD_1.

[0470] In Step ST3104, HeNB 3007 judges whether or not its own HeNB is included in the tracking area included in the tracking area list of MTCD_1 included in the paging received in Step ST3101. If it is determined that its own HeNB is included, it proceeds to Step ST3105. If it is determined that its own HeNB is not included, it does not perform the processing of Step ST3105. In this operation example, as shown in FIG. 30, its own HeNB 3007 is included in tracking area #1 (TA #1) 3016 included in the tracking area list. Therefore, after the processing of Step ST3104, it proceeds to Step ST3105.

[0471] In Step ST3105, the HeNB 3007 notifies the MTCD_1 of a paging addressed to the MTCD_1. The paging is notified in a mobile communication system standardized by 3GPP. Detailed methods for notifying the paging are disclosed in Non-Patent Document 1, Non-Patent Document 2, and Non-Patent Document 16.

[0472] In Step ST3106, HeNB 3005 determines whether or not its own HeNB is included in the tracking area included in the tracking area list of MTCD_1 included in the paging received in Step ST3102. If it determines that its own HeNB is included, it proceeds to Step ST3107. If it determines that its own HeNB is not included, it does not perform the processing of Step ST3107. In this operation example, as shown in FIG. 30, its own HeNB 3005 is included in tracking area #1 (TA#1) 3016 included in the tracking area list. Therefore, after the processing of Step ST3106, it proceeds to Step ST3107.

[0473] In Step ST3107, HeNB 3005 notifies MTCD_1 of a paging message addressed to MTCD_1. The paging message is notified in a mobile communication system standardized by 3GPP. Detailed methods for notifying the paging message are disclosed in Non-Patent Document 1, Non-Patent Document 2, and Non-Patent Document 16.

[0474] In Step ST3108, HeNB 3003 judges whether or not its own HeNB is included in the tracking area included in the tracking area list of MTCD_1 included in the paging received in Step ST3103. If it is determined that its own HeNB is included, it proceeds to Step ST3109. If it is determined that its own HeNB is not included, it does not perform the processing of Step ST3109. In this operation example, as shown in FIG. 30, its own HeNB 3003 is included in tracking area #1 (TA #1) 3016 included in the tracking area list. Therefore, after the processing of Step ST3108, it proceeds to Step ST3109.

[0475] In Step ST3109, HeNB 3003 notifies MTCD_1 of a paging message addressed to MTCD_1. The paging message is notified in a mobile communication system standardized by 3GPP. Detailed methods for notifying the paging message are disclosed in Non-Patent Document 1, Non-Patent Document 2, and Non-Patent Document 16.

[0476] As described above, UE 3009, whose MTCD identifier is MTCD_1, is located within coverage 3008 of HeNB 3007, and therefore receives paging from HeNB 3007 in Step ST3105. Therefore, the paging from HeNB 3005 in Step ST3107 and the paging from HeNB 3003 in Step ST3109 are wasted.

[0477] Next, waste of radio resources when the fourth embodiment is implemented will be described with reference to Figures 33 and 34. Figures 33 and 34 are diagrams showing sequences of a mobile communication system for explaining waste of radio resources when the fourth embodiment is implemented. Figures 33 and 34 are connected at the position of boundary line L2. In Figures 33 and 34, steps corresponding to those shown in Figures 26, 27, 31, and 32 are given the same reference numerals, and common descriptions will be omitted.

[0478] This operation example will be described using the location diagram shown in Fig. 30. It is assumed that HeNB3003 and HeNB3007 are HeNBs capable of performing line concentration processing, and HeNB3005 is a HeNB that does not have the ability to perform line concentration processing. The mobile terminal 3009 is an MTCD, and the identifier of the MTCD is MTCD_1. It is assumed that HeNB3007 has performed line concentration processing on data from the mobile terminal 3009.

[0479] First, MTCD_1 performs the process of Step ST2701, and MTCD_n performs the process of Step ST2702. Next, HeNB 3007 performs the process of Step ST2703 to Step ST2706. Next, MME performs the process of Step ST2605, and HSS performs the process of Step ST2606.

[0480] In Step ST2607, after the MME receives an incoming call addressed to MTCD_1, in Step ST2608, the MME searches the tracking area list (also referred to as a TAI list) of MTCD_1. In this operation example, the MME finds that the tracking area list of MTCD_1 includes tracking area #1 (TA#1) 3016 and tracking area #2 (TA#2) 3017.

[0481] In Step ST3101, the MME notifies the HeNB 3007 of a paging message addressed to the MTCD_1. The paging message includes a tracking area list of the MTCD_1 and an identifier of the MTCD_1.

[0482] In Step ST3102, the MME notifies the HeNB 3005 of a paging addressed to the MTCD_1. The paging includes a tracking area list of the MTCD_1 and an identifier of the MTCD_1.

[0483] In Step ST3103, the MME notifies the HeNB 3003 of a paging message addressed to the MTCD_1. The paging message includes a tracking area list of the MTCD_1 and an identifier of the MTCD_1.

[0484] The HeNB 3007 has the capability to perform line concentration processing. Therefore, in Step ST2707, the HeNB judges whether or not it has performed line concentration processing for MTCD_1 included in the paging received in Step ST3101. The HeNB may use the information stored in Step ST2704 to judge whether or not to perform the processing in Step ST2707. If it is determined that it has performed line concentration processing, it moves to Step ST2708. If it is determined that it has not performed line concentration processing, it moves to Step ST2709. In this operation example, the HeNB 3007 has performed line concentration processing for MTCD_1, and therefore it is determined that it has performed line concentration processing, and it moves to Step ST2708.

[0485] Furthermore, HeNB 3005 does not have the capability to perform line concentration processing. Therefore, as in the current paging method, in Step ST3106, HeNB 3005 determines whether or not its own HeNB is included in the tracking area included in the tracking area list of MTCD_1 included in the paging received in Step ST3102. If it determines that its own HeNB is included, it proceeds to Step ST3107. If it determines that its own HeNB is not included, it does not perform the processing of Step ST3107. In this operation example, as shown in FIG. 30 , its own HeNB 3005 is included in tracking area #1 (TA #1) 3016 included in the tracking area list. Therefore, after the processing of Step ST3106, it proceeds to Step ST3107.

[0486] Furthermore, HeNB 3003 has the capability to perform line concentration processing. Therefore, in Step ST3201, HeNB determines whether or not it has performed line concentration processing for MTCD_1 included in the paging received in Step ST3103. If it determines that it has performed line concentration processing, it moves to Step ST3109. If it determines that it has not performed line concentration processing, it moves to Step ST3202. In this operation example, HeNB 3003 has not performed line concentration processing for MTCD_1, so it is determined that it has not performed line concentration processing, and it moves to Step ST3202.

[0487] In Step ST3202, the HeNB determines whether or not the HeNB itself is included in the tracking area included in the tracking area list of MTCD_1 included in the paging received in Step ST3103. If it is determined that the HeNB itself is included, the HeNB proceeds to Step ST3203. If it is determined that the HeNB itself is not included, the HeNB does not perform the process of Step ST3203. In Step ST3203, the HeNB performs notification of an incoming call using a communication system within 3GPP. In this operation example, the HeNB 3003 is included in the tracking area of ​​MTCD_1, and therefore performs the process of Step ST3203.

[0488] As described above, UE 3009, whose MTCD identifier is MTCD_1, is located within coverage 3008 of HeNB 3007, and therefore receives paging from HeNB 3007 in Step ST3105. Therefore, the paging from HeNB 3005 in Step ST3107 and the paging from HeNB 3003 in Step ST3203 are wasted.

[0489] The solution in the seventh embodiment is as follows. The fact that the HeNB will perform line concentration processing is registered with the MME, HSS, etc. on the core network side together with the identifier of the MTCD. Information on whether or not to perform line concentration processing is hereinafter also referred to as "line concentration processing status." When paging addressed to the MTCD occurs, the line concentration processing status is included in the paging message. When the HeNB receives a paging message including information indicating that line concentration processing will be performed, the HeNB transmits a paging message if it has the capability to perform line concentration processing.

[0490] The following four examples (1) to (4) are disclosed as specific examples of timing for registering with the core network that a HeNB will perform concentration processing. (1) Every time a HeNB collects data from an MTCD under its control to the core network. (2) When collecting an MTCD attach message or when selecting an "Attach procedure" during concentration processing. Compared to specific example (1), this specific example (2) reduces the number of times that a HeNB registers with the core network that it will perform concentration processing. Therefore, communication resources can be used more effectively and the processing load on the HeNB can be reduced. (3) When collecting an MTCD TAU message or when selecting a "Tracking Area Update procedure" during concentration processing. Compared to specific example (1), this specific example (3) reduces the number of times that a HeNB registers with the core network that it will perform concentration processing. Therefore, communication resources can be used more effectively and the processing load on the HeNB can be reduced. (4) A combination of the above (2) and (3).

[0491] A specific example of when the core network deletes the registration of the line concentration process is when it receives a "Detach procedure" from the MTCD. A specific example of the registration method is disclosed below. The line concentration process status is stored in association with the MTCD identifier.

[0492] The following two (1) and (2) are disclosed as specific examples of entities to be registered. (1) MME. This eliminates the need to query other entities when processing incoming calls. This is effective in preventing control delays and reducing the processing load on the communication system. (2) HSS. This is effective in enabling centralized management of data because it can be stored together with other registration information. Compared to specific example (1), this is effective in that it can effectively utilize registration information even when the MME is changed due to movement of the mobile terminal. In other words, it can reduce the number of registrations to perform line concentration processing from the HeNB to the HSS. This allows for effective use of communication resources and reduces the processing load on the HeNB.

[0493] The following two methods (1) and (2) are disclosed as specific examples of a method for including information indicating that line concentration has been performed in a paging message when paging occurs. (1) If the registered location is an HSS, the MME of the calling or called party inquires about the line concentration status of the HSS. The MME maps the inquiry result into the paging message. (2) If the registered location is an MEE, the MME of the called party searches for the line concentration status of the MTCD that received the call. The MME maps the search result into the paging message.

[0494] A specific example of operation using the seventh embodiment will be described with reference to Figures 35 and 36. Figures 35 and 36 are diagrams showing sequences of a mobile communication system according to the seventh embodiment. Figures 35 and 36 are connected at the position of boundary line L3. In Figures 35 and 36, steps corresponding to those shown in Figures 17, 26, 31, and 32 are given the same reference numerals, and common descriptions will be omitted.

[0495] This operation example will be described using the location diagram shown in Fig. 30. It is assumed that HeNB3003 and HeNB3007 are HeNBs capable of performing line concentration processing, and HeNB3005 is a HeNB that does not have the ability to perform line concentration processing. The mobile terminal 3009 is an MTCD, and the identifier of the MTCD is MTCD_1. In addition, as a specific example of the timing at which a HeNB registers with the core network that it will perform line concentration processing, a case where an attach message of the MTCD is concentrated will be disclosed. In addition, a case where a specific example of the entity to be registered is an HSS will be disclosed. In addition, a case where the third embodiment is executed will be disclosed.

[0496] First, MTCD_1 performs the process of step ST1703, and MTCD_n performs the process of step ST1704. Next, upon receiving the "RRC Connection Request" transmitted from MTCD_1 and MTCD_n, HeNB 3007 performs the process of step ST1705 and step ST1707. Next, MTCD_1 performs the process of step ST2601, and MTCD_n performs the process of step ST2602. Next, upon receiving the attach messages transmitted from MTCD_1 and MTCD_n, HeNB 3007 performs, in step ST2603, a concentration process on the attach messages from MTCD_1 received in step ST2601 and the attach messages from MTCD_n received in step ST2602. That is, the concentration process on the attach messages is performed. As a result, in this operation example, the intention to perform concentration process is registered with the core network.

[0497] Next, in Step ST3301, HeNB 3007 notifies the MME of the attach message concentrated by performing the concentration process in Step ST2603 and of an intention to perform the concentration process. The attach message includes the identifier of MTCD_1 and the identifier of MTCD_n, which are identifiers of the MTCDs that are targets of the concentration process, the identifier of the HeNB, and the TAI. The intention to perform the concentration process may be included in the attach message. For this notification, the second embodiment, the first modification of the second embodiment, the second modification of the second embodiment, and the third modification of the second embodiment may be used.

[0498] In Step ST3302, the MME notifies the HSS (Home Subscriber Server) of the identifiers of the MTCDs, ie, the identifiers of MTCD_1 and MTCD_n, received as the attach message, and a notice that line concentration processing will be performed.

[0499] In Step ST3303, the HSS registers and manages the identifiers of the attached MTCD_1 and MTCD_n, and the fact that line concentration processing will be performed. During the registration and management, the line concentration processing status is associated with the MTCD identifier. In Step ST2607, after the MME receives an incoming call addressed to MTCD_1, the MME performs the processing of Step ST2608.

[0500] Next, in Step ST3304, the MME inquires of the HSS about the concentration status of MTCD_1. In Step ST3305, the HSS reports the concentration status of MTCD_1 to the MME. In this operation example, since MTCD_1 is being subjected to concentration processing, it is reported that concentration processing will be performed.

[0501] In Step ST3306, the MME determines whether or not MTCD_1 has been subjected to concentration, based on the concentration status report received in Step ST3305. If it is determined that MTCD_1 has been subjected to concentration, the MME proceeds to Step ST3307. If it is determined that MTCD_1 has not been subjected to concentration, the MME proceeds to Step ST3101. In this operation example, MTCD_1 has been subjected to concentration, and it has been reported in Step ST3305 that concentration will be performed. Therefore, it is determined that MTCD_1 has been subjected to concentration, and the MME proceeds to Step ST3307.

[0502] In Step ST3307, the MME adds an indication that line concentration has been performed to the paging message addressed to MTCD_1. Therefore, in this operation example in which the process of Step ST3307 is performed, in Step ST3101, the paging message addressed to MTCD_1 notified to HeNB3007 from the MME includes an indication that line concentration has been performed, in addition to the tracking area list of MTCD_1 and the identifier of MTCD_1. Similarly, in Step ST3102, the paging message addressed to MTCD_1 notified to HeNB3005 from the MME includes an indication that line concentration has been performed, in addition to the tracking area list of MTCD_1 and the identifier of MTCD_1. Similarly, in Step ST3103, the paging message addressed to MTCD_1 notified to HeNB3003 from the MME includes an indication that line concentration has been performed, in addition to the tracking area list of MTCD_1 and the identifier of MTCD_1.

[0503] In Step ST3308, the HeNB 3007 judges whether or not the paging received in Step ST3101 includes information indicating that line concentration has been performed. If it determines that the information indicates that line concentration has been performed, it moves to Step ST3309. If it determines that the information indicates that line concentration has not been performed, it moves to Step ST3104. In this operation example, the paging received in Step ST3101 includes information indicating that line concentration has been performed. Therefore, after the processing of Step ST3308, it moves to Step ST3309.

[0504] In Step ST3309, the HeNB 3007 judges whether or not its own HeNB has concentration processing capability. If it is judged that its own HeNB has concentration processing capability, it proceeds to Step ST3104. If it is judged that its own HeNB does not have concentration processing capability, it does not perform the processes of Step ST3104 and Step ST3105. In this operation example, the HeNB 3007 has concentration processing capability, so it proceeds to Step ST3104. Next, the HeNB 3007 performs the processes of Step ST3104 and Step ST3105.

[0505] In Step ST3310, the HeNB 3005 judges whether or not the paging received in Step ST3102 includes information indicating that line concentration has been performed. If it determines that the information indicates that line concentration has been performed, it proceeds to Step ST3311. If it determines that the information indicates that line concentration has not been performed, it proceeds to Step ST3106. In this operation example, the paging received in Step ST3102 includes information indicating that line concentration has been performed. Therefore, after the processing of Step ST3310, it proceeds to Step ST3311.

[0506] In Step ST3311, the HeNB 3005 determines whether or not its own HeNB has line concentration processing capability. If it determines that its own HeNB has line concentration processing capability, it proceeds to Step ST3106. If it determines that its own HeNB does not have line concentration processing capability, it does not perform the processes of Step ST3106 and Step ST3107. In this operation example, the HeNB 3005 does not have line concentration processing capability, and therefore does not perform the processes of Step ST3106 and Step ST3107. In FIGS. 31 and 32 which explain waste of radio resources when the third embodiment is executed, the HeNB 3005 notifies the MTCD_1 of useless paging addressed to the MTCD_1, which is not received by the MTCD_1, as shown in Step ST3107 of FIG. 32. In this embodiment, it is possible to reduce useless paging as shown in Step ST3107 of FIG. 32.

[0507] In Step ST3312, the HeNB 3003 judges whether or not the paging received in Step ST3103 includes information indicating that line concentration has been performed. If it determines that the information indicates that line concentration has been performed, it proceeds to Step ST3313. If it determines that the information indicates that line concentration has not been performed, it proceeds to Step ST3108. In this operation example, the paging received in Step ST3103 includes information indicating that line concentration has been performed. Therefore, after the processing of Step ST3312, it proceeds to Step ST3313.

[0508] In Step ST3313, the HeNB 3003 determines whether or not its own HeNB has the concentration processing capability. If it determines that its own HeNB has the concentration processing capability, it proceeds to Step ST3108. If it determines that its own HeNB does not have the concentration processing capability, it does not perform the processes of Step ST3108 and Step ST3109. In this operation example, the HeNB 3003 has the concentration processing capability, so it proceeds to Step ST3108. Next, the HeNB 3003 performs the processes of Step ST3108 and Step ST3109.

[0509] A specific example of operation using the seventh embodiment will be described with reference to Figures 37 and 38. Figures 37 and 38 are diagrams showing other sequences of the mobile communication system according to the seventh embodiment. Figures 37 and 38 are connected at the boundary line L4. In Figures 37 and 38, steps corresponding to those shown in Figures 17, 26, and 31 to 36 are given the same reference numerals, and common descriptions will be omitted.

[0510] This operation example will be described using the location diagram shown in Fig. 30. It is assumed that HeNB3003 and HeNB3007 are HeNBs capable of performing line concentration processing, and HeNB3005 is a HeNB that does not have the ability to perform line concentration processing. The mobile terminal 3009 is an MTCD, and the MTCD identifier is MTCD_1. In addition, as a specific example of the timing at which an HeNB registers with the core network that it will perform line concentration processing, a case where an attach message of the MTCD is concentrated will be disclosed. In addition, a case where an MME is a specific example of the entity to be registered will be disclosed. In addition, a case where the third embodiment is executed will be disclosed.

[0511] First, MTCD_1 performs the process of step ST1703, and MTCD_n performs the process of step ST1704. Next, HeNB3007, which has received the "RRC Connection Request" transmitted from MTCD_1 and MTCD_n, performs the processes of step ST1705 and step ST1707. Next, MTCD_1 performs the process of step ST2601, and MTCD_n performs the process of step ST2602. Next, HeNB3007, which has received the attach messages transmitted from MTCD_1 and MTCD_n, performs the processes of step ST2603 and step ST3301.

[0512] Next, in Step ST3401, the MME registers and manages the identifiers of MTCD_1 and MTCD_n, which are the identifiers of the MTCDs received in the attach message of Step ST3301, and the fact that line concentration processing will be performed. When registering and managing, the line concentration processing status is associated with the MTCD identifiers. Next, the MME performs the processing of Step ST2605, and the HSS performs the processing of Step ST2606. In Step ST2607, after the MME receives an incoming call addressed to MTCD_1, the MME performs the processing of Step ST2608.

[0513] Next, in Step ST3402, the MME searches for the concentration status of MTCD_1. After the process of Step ST3402, the MME performs the processes of Step ST3306, Step ST3307, and Step ST3101 to Step ST3103, as in FIG. 36. In addition, HeNB3007 performs the processes of Step ST3308, Step ST3309, Step ST3104, and Step ST3105. In addition, HeNB3005 performs the processes of Step ST3310, Step ST3311, Step ST3106, and Step ST3107. In addition, HeNB3003 performs the processes of Step ST3312, Step ST3313, Step ST3108, and Step ST3109.

[0514] In this operation example, as in the sequence shown in FIG. 36 , in step ST3311, the HeNB 3005 determines whether or not its own HeNB has line concentration processing capability. If it determines that its own HeNB has line concentration processing capability, it proceeds to step ST3106. If it determines that its own HeNB does not have line concentration processing capability, it does not perform the processes of step ST3106 and step ST3107. In this operation example, the HeNB 3005 does not have line concentration processing capability, so it does not perform the processes of step ST3106 and step ST3107. In FIGS. 31 and 32 which explain waste of radio resources when embodiment 3 is performed, the HeNB 3005 notifies MTCD_1 of useless paging addressed to MTCD_1, which is not received by MTCD_1, as shown in step ST3107 of FIG. 32. In this embodiment, it is possible to reduce useless paging such as that shown in step ST3107 of FIG. 32.

[0515] A specific example of operation using the seventh embodiment will be described with reference to Figures 39 and 40. Figures 39 and 40 are diagrams showing other sequences of the mobile communication system according to the seventh embodiment. Figures 39 and 40 are connected at the boundary line L5. In Figures 39 and 40, steps corresponding to those shown in Figures 26, 27, and 31 to 36 are given the same reference numerals, and common descriptions will be omitted.

[0516] This operation example will be described using the location diagram shown in Fig. 30. It is assumed that HeNB3003 and HeNB3007 are HeNBs capable of performing line concentration processing, and HeNB3005 is a HeNB that does not have the ability to perform line concentration processing. The mobile terminal 3009 is an MTCD, and the MTCD identifier is MTCD_1. In addition, as a specific example of the timing at which a HeNB registers with the core network that it will perform line concentration processing, a case where "Attach procedure" is selected during line concentration processing will be disclosed. In addition, a case where a specific example of the entity to be registered is an HSS will be disclosed. In addition, a case where the fourth embodiment is executed will be disclosed.

[0517] First, MTCD_1 performs the process of Step ST2701, and MTCD_n performs the process of Step ST2702. Next, HeNB 3007 performs the processes of Step ST2703 and Step ST2704.

[0518] Next, in Step ST2705, HeNB 3007 performs line concentration processing. In this operation example, the data to the core network from MTCD_1 and MTCD_n are collectively notified to MME. In addition, the HeNB interprets the contents of Step ST2701 and Step ST2702, which are accesses other than those of 3GPP, and understands that this is access related to "installation." Next, it selects "Attach procedure" as a protocol within 3GPP that is appropriate for access related to "installation." It selects "Attach procedure" when performing line concentration processing. Therefore, in this operation example, it registers with the core network that it will perform line concentration processing.

[0519] In Step ST3501, HeNB 3007 notifies the MME of the attach message concentrated by performing the concentration process in Step ST2705 and of an intention to perform the concentration process. The attach message includes the identifier of MTCD_1 and the identifier of MTCD_n, which are identifiers of the MTCDs that are targets of the concentration process, the identifier of the HeNB, and the TAI. The intention to perform the concentration process may be included in the attach message. For this notification, the second embodiment, the first modification of the second embodiment, the second modification of the second embodiment, and the third modification of the second embodiment may be used.

[0520] After the process of Step ST3501, the MME performs the processes of Step ST3302, Step ST2608, Step ST3304, Step ST3306, Step ST3307, and Step ST3101 to Step ST3103. In addition, the HSS performs the processes of Step ST3303, Step ST2607, and Step ST3305. In addition, HeNB3007 performs the processes of Step ST3308, Step ST3309, Step ST2707, Step ST2708, Step ST2709, and Step ST2710. In addition, HeNB3005 performs the processes of Step ST3310, Step ST3311, Step ST3106, and Step ST3107. In addition, HeNB3003 performs the processes of Step ST3312, Step ST3313, Step ST3201, Step ST3109, Step ST3202, and Step ST3203.

[0521] In Step ST3310, the HeNB 3005 judges whether or not the paging received in Step ST3102 includes information indicating that line concentration has been performed. If it determines that the information indicates that line concentration has been performed, it proceeds to Step ST3311. If it determines that the information indicates that line concentration has not been performed, it proceeds to Step ST3106. In this operation example, the paging received in Step ST3102 includes information indicating that line concentration has been performed. Therefore, after the processing of Step ST3310, it proceeds to Step ST3311.

[0522] In Step ST3311, the HeNB 3005 determines whether or not the HeNB has line concentration processing capability. If the HeNB has determined that the HeNB has line concentration processing capability, the HeNB proceeds to Step ST3106. If the HeNB has determined that the HeNB does not have line concentration processing capability, the HeNB does not perform the processes of Step ST3106 and Step ST3107. In this operation example, the HeNB 3005 does not have line concentration processing capability, and therefore does not perform the processes of Step ST3106 and Step ST3107. In FIGS. 33 and 34 which explain waste of radio resources when the fourth embodiment is executed, the HeNB 3005 notifies the MTCD_1 of useless paging addressed to the MTCD_1, which is not received by the MTCD_1, as shown in Step ST3107 of FIG. 34. In this embodiment, useless paging as shown in Step ST3107 of FIG. 34 can be reduced.

[0523] A specific example of operation using the seventh embodiment will be described with reference to Figures 41 and 42. Figures 41 and 42 are diagrams showing other sequences of the mobile communication system in the seventh embodiment. Figures 41 and 42 are connected at the position of boundary line L6. In Figures 41 and 42, steps corresponding to those shown in Figures 26, 27, 31 to 36, 39, and 40 are given the same reference numerals, and common descriptions will be omitted.

[0524] This operation example will be described using the location diagram shown in Fig. 30 mentioned above. It is assumed that HeNB3003 and HeNB3007 are HeNBs capable of performing line concentration processing, and HeNB3005 is a HeNB that does not have the ability to perform line concentration processing. The mobile terminal 3009 is an MTCD, and the MTCD identifier is MTCD_1. In addition, as a specific example of the timing at which a HeNB registers with the core network that it will perform line concentration processing, a case where an attach message of the MTCD is concentrated will be disclosed. In addition, a case where a specific example of the entity to be registered is an MME will be disclosed. In addition, a case where the fourth embodiment is executed will be disclosed.

[0525] In this operation example, similarly to the sequences shown in FIGS. 39 and 40 , in step ST3311, the HeNB 3005 determines whether or not its own HeNB has line concentration processing capability. If it determines that its own HeNB has line concentration processing capability, it proceeds to step ST3106. If it determines that its own HeNB does not have line concentration processing capability, it does not perform the processes of steps ST3106 and ST3107. In this operation example, the HeNB 3005 does not have line concentration processing capability, so it does not perform the processes of steps ST3106 and ST3107. In FIGS. 33 and 34 which explain waste of radio resources when embodiment 4 is executed, the HeNB 3005 notifies MTCD_1 of useless paging addressed to MTCD_1, which is not received by MTCD_1, as shown in step ST3107 of FIG. 34 . In this embodiment, it is possible to reduce useless paging as shown in step ST3107 of FIG. 34 .

[0526] According to the seventh embodiment, in addition to the effects of the third and fourth embodiments, the following effects can be obtained. When a HeNB receives a paging message including information indicating that it will perform line concentration, it transmits a paging message if its own HeNB has the ability to perform line concentration. This makes it possible to reduce notifications of paging addressed to an MTCD performing line concentration from HeNBs that do not have the ability to perform line concentration. An MTCD performing line concentration will not be under the umbrella of a HeNB that does not have the ability to perform line concentration. Therefore, it is possible to reduce only unnecessary paging transmissions from a HeNB, prevent missed calls, and effectively utilize radio resources, thereby reducing interference.

[0527] Seventh embodiment, variant 1 The problem to be solved by the first modification of the seventh embodiment will be described below. When the seventh embodiment is used, the following problem occurs. The problem will be described with reference to FIG. 36. By using the seventh embodiment, it is possible to reduce notifications from HeNBs that do not have the ability to perform line concentration for paging addressed to an MTCD that performs line concentration. On the other hand, in step ST3102 of FIG. 36 and the like, a paging message that is not notified to a HeNB that does not have the ability to perform line concentration is notified. Therefore, communication resources are wasted, and there is a problem that a load of useless processing is generated on the MME or the HeNB that does not have the ability to perform line concentration in step ST3310 and step ST3311 of FIG. 36 and the like.

[0528] The solution in the first modification of the seventh embodiment is shown below. The explanation will focus on the differences from the solution in the seventh embodiment. The parts that are not explained are the same as those in the seventh embodiment.

[0529] The intention to perform line concentration at the HeNB is registered with the MME, HSS, etc. on the core network side together with the MTCD identifier. Information on whether to perform line concentration is hereinafter also referred to as "line concentration status." When paging occurs for an MTCD that performs line concentration, the MME transmits a paging message to a HeNB that has the ability to perform line concentration. When paging occurs for an MTCD that performs line concentration, the MME does not transmit a paging message to a HeNB that does not have the ability to perform line concentration.

[0530] A specific example in which an MME grasps the capability of a HeNB under its control to perform line concentration processing will be disclosed below. Using the third modification of the first embodiment described above, the HeNB notifies the MME, SGSN, etc., which are core networks, of capability information related to the line concentration processing of data from an MTCD.

[0531] A specific example of operation using the first modification of the seventh embodiment will be described with reference to Figures 43 and 44. Figures 43 and 44 are diagrams showing the sequence of a mobile communication system in the first modification of the seventh embodiment. Figures 43 and 44 are connected at the position of boundary line L7. In Figures 43 and 44, steps corresponding to those shown in Figures 17, 26, 31, 32, 35, and 36 are given the same reference numerals, and common descriptions will be omitted.

[0532] This operation example will be described using the location diagram shown in FIG. 30 mentioned above. It is assumed that HeNB 3003 and HeNB 3007 are HeNBs capable of performing line concentration processing, and HeNB 3005 is a HeNB that does not have the ability to perform line concentration processing. The mobile terminal 3009 is an MTCD, and the identifier of the MTCD is MTCD_1. In addition, as a specific example of the timing at which a HeNB notifies the core network of capability information related to line concentration processing, the time at which a HeNB is installed will be disclosed. In addition, as a specific example of the timing at which a HeNB registers with the core network that it will perform line concentration processing, the time at which an attach message of the MTCD is concentrated will be disclosed. In addition, a case where a specific example of the entity to be registered is an HSS will be disclosed. In addition, a case where the third embodiment is executed will be disclosed.

[0533] In Step ST3701, HeNB 3007 is installed. In Step ST3702, HeNB 3007 notifies the MME of capability information related to line concentration processing of HeNB 3007.

[0534] In Step ST3703, HeNB 3005 is installed. In Step ST3704, HeNB 3005 notifies the MME of capability information related to line concentration processing of HeNB 3005.

[0535] In Step ST3705, HeNB 3003 is installed. In Step ST3706, HeNB 3003 notifies the MME of capability information related to line concentration processing of HeNB 3003.

[0536] In Step ST3707, the MME registers and manages the capability information of the HeNBs under its control. When registering and managing the capability information, the MME associates the capability information with the identifier of the HeNB.

[0537] In Step ST3306, the MME determines whether or not MTCD_1 has been subjected to concentration, based on the concentration status report received in Step ST3305. If it is determined that MTCD_1 has been subjected to concentration, the MME proceeds to Step ST3708. If it is determined that MTCD_1 has not been subjected to concentration, the MME proceeds to Step ST3101. In this operation example, MTCD_1 has been subjected to concentration, and it has been reported in Step ST3305 that concentration will be performed. Therefore, it is determined that MTCD_1 has been subjected to concentration, and the MME proceeds to Step ST3708.

[0538] In Step ST3708, the MME selects a HeNB capable of performing line concentration processing from among the HeNBs under its control. For the selection, it is preferable to use the information registered in Step ST3707. In this operation example, HeNB3003 and HeNB3007 are selected as HeNBs capable of performing line concentration processing. On the other hand, HeNB3005 is not selected as a HeNB capable of performing line concentration processing. The MME transmits a paging message to a HeNB capable of performing line concentration processing, and does not transmit a paging message to a HeNB not capable of performing line concentration processing.

[0539] Therefore, in Step ST3101, the MME notifies HeNB 3007 of a paging addressed to MTCD_1. The paging includes the tracking area list of MTCD_1 and the identifier of MTCD_1. In Step ST3103, the MME notifies HeNB 3003 of a paging addressed to MTCD_1. The paging includes the tracking area list of MTCD_1 and the identifier of MTCD_1. The MME does not notify HeNB 3005 of a paging addressed to MTCD_1. In FIG. 36, as shown in Step ST3102, a paging message that is not notified is notified from the MME to HeNB 3005. In this embodiment, it is possible to reduce unnecessary communication as shown in Step ST3102 of FIG. 36.

[0540] On the other hand, if the MME determines in Step ST3306 that the UE that has received the call has not been subjected to concentration processing, in Step ST3101, the MME notifies HeNB 3007 of a paging addressed to MTCD_1. The paging includes the tracking area list of MTCD_1 and the identifier of MTCD_1. In Step ST3102, the MME notifies HeNB 3005 of a paging addressed to MTCD_1. The paging includes the tracking area list of MTCD_1 and the identifier of MTCD_1. In Step ST3103, the MME notifies HeNB 3003 of a paging addressed to MTCD_1. The paging includes the tracking area list of MTCD_1 and the identifier of MTCD_1.

[0541] Although the present modification has been described mainly as an example in which it is combined with the third embodiment, it can also be used in combination with the fourth embodiment.

[0542] According to the first modification of the seventh embodiment, the following effects can be obtained in addition to the effects of the seventh embodiment. When an MME receives a paging message addressed to an MTCD that performs line concentration, it transmits the paging message to a HeNB that has the ability to perform line concentration. This makes it possible to reduce notifications of paging addressed to an MTCD that performs line concentration to a HeNB that does not have the ability to perform line concentration. An MTCD that performs line concentration will not be under the umbrella of a HeNB that does not have the ability to perform line concentration. Therefore, it is possible to reduce only unnecessary paging notifications to HeNBs, prevent missed calls, and effectively utilize communication resources, thereby reducing the processing load on the MME or the HeNB that does not have the ability to perform line concentration.

[0543] Seventh embodiment, variant 2 The problem to be solved by the second modification of the seventh embodiment will be described below. When the seventh embodiment is used, the following problem occurs. The problem will be described with reference to FIG. 35 and FIG. 36. By using the seventh embodiment, it is possible to reduce notifications from HeNBs that do not have the ability to perform concentration processing for paging addressed to an MTCD that performs concentration processing. On the other hand, paging addressed to an MTCD from a HeNB that does not perform concentration processing for the MTCD is notified in advance, as shown in steps ST3103 and ST3109 of FIG. 36. There is a problem that meaningless paging transmission makes it impossible to effectively utilize radio resources and causes interference.

[0544] The solution in the second modification of the seventh embodiment is as follows: The HeNB registers the identifier of the HeNB that has performed the concentration process at the HeNB, together with the identifier of the MTCD, in the MME, HSS, etc. on the core network side.

[0545] As in the seventh embodiment, when paging addressed to an MTCD occurs, the identifier of the HeNB that performed line concentration processing is included in the paging message. When a HeNB receives a paging message including the identifier of the HeNB that performed line concentration processing, if the identifier of the HeNB is that of the HeNB itself, the HeNB transmits the paging message.

[0546] A specific example of the timing at which a HeNB registers the identifier of a HeNB that has performed line concentration processing in the core network is the same as the specific example of “timing at which a HeNB registers the intention to perform line concentration processing in the core network” in embodiment 7, and therefore description thereof will be omitted.

[0547] A specific example of the timing at which the core network deletes the registration of the identifier of the HeNB that performed the concentration process is when the core network receives a "Detach procedure" from the MTCD.

[0548] A specific example of the registration method is disclosed below: The identifier of the HeNB that performed the line concentration process is stored in association with the identifier of the MTCD.

[0549] A specific example of an entity to be registered is the same as that in Embodiment 7, and therefore description thereof will be omitted. A specific example of a method of including an identifier of a HeNB that has performed line concentration processing in a paging message when paging has occurred is the same as the specific example of a method of including information indicating that line concentration processing has been performed in a paging message when paging has occurred in Embodiment 7, and therefore description thereof will be omitted.

[0550] Alternatively, similar to the first modification of the seventh embodiment, when paging addressed to an MTCD that performs line concentration occurs, the MME transmits a paging message to the HeNB that performed the line concentration. When paging addressed to an MTCD that performs line concentration occurs, the MME does not transmit a paging message to HeNBs other than the HeNB that performed the line concentration.

[0551] In addition to the effects of the seventh embodiment and the first modification of the seventh embodiment, the second modification of the seventh embodiment can provide the following effects.

[0552] It is possible to reduce paging addressed to an MTCD from HeNBs other than the HeNB that performed line concentration processing. Alternatively, it is possible to reduce paging notifications to HeNBs other than the HeNB that performed line concentration processing. An MTCD that performs line concentration processing will not be under the umbrella of any HeNB other than the HeNB that performed line concentration processing. Therefore, it is possible to reduce only unnecessary paging from HeNBs or unnecessary paging notifications to HeNBs, prevent missed calls, and effectively utilize radio resources, thereby enabling effective use of communication resources. In addition, it is possible to reduce the processing load on the MME or HeNBs that do not have the ability to perform line concentration processing.

[0553] The method disclosed in the present invention is not limited to eNB / NB, but can also be applied to so-called local nodes such as HeNB, HNB, pico eNB (LTE pico cell (EUTRAN pico cell)), pico NB (WCDMA pico cell (UTRAN pico cell)), hot zone cell nodes, etc. By applying the method disclosed in the present invention to local nodes that support MTC services, it becomes possible to avoid congestion in the core network.

[0554] In the above embodiments, the LTE system (E-UTRAN) has been mainly described, but the communication system of the present invention can also be applied to a W-CDMA system (UTRAN, UMTS) and an LTE-Advanced system.

[0555] Although the present invention has been described in detail, the above description is illustrative in all respects and does not limit the present invention, and it is understood that countless variations not illustrated can be envisaged without departing from the scope of the present invention. [Explanation of symbols]

[0556] 1301 to 1304 MTCD, 1305 NB / eNB, 1306 SGSN / MME, 1307 HLR / HSS, 1308 MTC server, 1309 MTC user, 1310 API, 1311 to 1314 Uu interface, 1315 IuPS / S1 interface, 1316 Gr / S6a interface, 1317 communication operator area, 3001, 3010 eNB, 3003, 3005, 3007, 3012, 3014 HeNB, 3002, 3004, 3006, 3008, 3011, 3013, 3015 coverage, 3009 mobile terminal, 3016 tracking area #1 (TA#1), 3017 tracking area #2 (TA#2).

Claims

1. A mobile communication system including a communication terminal device, a base station device that performs wireless communication with the communication terminal device, and a base station control device that controls the base station device, the communication terminal device is an MTC (Machine Type Communication) device, the base station control device includes an MME (Mobility Management Entity), A mobile communication system, characterized in that data is transmitted from the communication terminal device to the MME via the base station device.

2. 2. The mobile communication system according to claim 1, wherein the data is transmitted from the communication terminal device to the MME via the base station device using NAS (Non-Access Stratum) signaling.

3. 2. The mobile communication system according to claim 1, wherein the data is transmitted from the communication terminal device to the base station device using RRC (Radio Resource Control) signaling.

4. 2. The mobile communication system according to claim 1, wherein the data is transmitted from the base station device to the MME using S1 signaling.

5. A communication terminal device in a mobile communication system including a base station device that performs wireless communication with the communication terminal device, and a base station control device that controls the base station device, the communication terminal device is an MTC (Machine Type Communication) device, the base station control device includes an MME (Mobility Management Entity), A communication terminal device that transmits data to the MME via the base station device.

6. A base station device in a mobile communication system including a communication terminal device, a base station device that performs wireless communication with the communication terminal device, and a base station control device that controls the base station device, the communication terminal device is an MTC (Machine Type Communication) device, the base station control device includes an MME (Mobility Management Entity), A base station device that receives data transmitted from the communication terminal device and transmits the data to the MME.

7. A base station control device in a mobile communication system including a communication terminal device, a base station device that performs wireless communication with the communication terminal device, and a base station control device that controls the base station device, the communication terminal device is an MTC (Machine Type Communication) device, the base station control device includes an MME (Mobility Management Entity), The base station control device is characterized in that the MME receives data transmitted from the communication terminal device via the base station device.

Images