COMMUNICATION SYSTEM, COMMUNICATION TERMINAL DEVICE, AND PRIMARY CELL
By determining and notifying mobile terminals of secondary cell connections using RRC Control messages, the LTE-A system ensures stable and efficient carrier aggregation, addressing the challenge of wider bandwidth support.
Patent Information
- Application Number
- JP2023005546
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2011-02-10
- Filing Date
- 2023-01-18
- Publication Date
- 2024-11-11
- Estimated Expiration
- 2032-02-07
AI Technical Summary
The LTE-A system aims to support wider frequency bandwidths up to 100MHz, but existing methods for carrier aggregation do not provide a clear method for notifying mobile terminals of CSG indication and CSG-ID for secondary cells, leading to unstable operation and inappropriate service provision.
A communication system where a primary cell determines whether a candidate cell can be connected as a secondary cell and notifies the mobile terminal using RRC Control messages, ensuring appropriate service provision and stable operation.
This approach improves communication speed and stabilizes the operation of the communication system by providing appropriate services through carrier aggregation.
Smart Images

Figure 0007580503000001 
Figure 0007580503000002 
Figure 0007580503000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a communication system, a communication terminal device, and a primary cell. [Background technology]
[0002] Among the communication methods called the third generation, the W-CDMA (registered trademark) (Wideband Code division Multiple Access) method has been commercially available in Japan since 2001. In addition, the HSDPA (High Speed Downlink Packet Access) method has been launched, which realizes even faster data transmission using the downlink by adding a packet transmission channel (High Speed-Downlink Shared Channel: HS-DSCH) to the downlink (individual data channel, individual control channel). Furthermore, the HSUPA (High Speed Uplink Packet Access) method has also been launched to further increase the speed of data transmission in the uplink. W-CDMA is a communication method defined by 3GPP (3rd Generation Partnership Project), a standardization organization for mobile communication systems, and the Release 10 version of the specification has been compiled.
[0003] In addition, 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] In LTE, the access method, radio channel configuration and protocols will be completely different from the current W-CDMA (HSDPA / HSUPA). For example, W-CDMA uses Code Division Multiple Access, whereas LTE uses OFDM (Orthogonal Frequency Division Multiplexing) for downlink and SC-FDMA (Single Carrier Frequency Division Multiple Access) for uplink. In addition, while W-CDMA uses 5MHz bandwidth, LTE allows users to select from 1.4MHz, 3MHz, 5MHz, 10MHz, 15MHz and 20MHz for each base station. Also, LTE does not include circuit switching like W-CDMA, and is only a packet communication method.
[0005] LTE is defined as an independent radio access network separate from the W-CDMA network, since the communication system is configured using a new core network different from the W-CDMA core network (General Packet Radio Service: GPRS). Therefore, to distinguish it from the W-CDMA communication system, in the LTE communication system, the base station that communicates with the mobile terminal (User Equipment: UE) is called eNB (E-UTRAN NodeB), and the base station control device (Radio Network Controller) that exchanges control data and user data with multiple base stations is called EPC (Evolved Packet Core) or aGW (Access Gateway).
[0006] This LTE communication system provides unicast service and E-MBMS (Evolved Multimedia Broadcast Multicast Service). The E-MBMS service is a broadcast type multimedia service, and is sometimes simply called MBMS. It transmits large volume broadcast content such as news, weather forecasts, and mobile broadcasts to multiple mobile terminals. This is also called point to multipoint service.
[0007] Current decisions on the overall architecture of the LTE system in 3GPP are described in Non-Patent Document 1 (Chapter 4). The overall architecture will be explained with reference to FIG. 1. FIG. 1 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), are terminated in a base station 102, an E-UTRAN (Evolved Universal Terrestrial Radio Access) is composed of one or more base stations 102.
[0008] The base stations 102 schedule and transmit paging signals (also called 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.
[0009] The MME 103 distributes paging signals to a single or multiple base stations 102. The MME 103 also performs mobility control in an idle state. The MME 103 manages a tracking area list when a mobile terminal is in an idle state and when it is in an active state.
[0010] 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.
[0011] 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 the 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 re-selection, 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), measurement of neighbor cells, etc.
[0012] The current decisions on the frame configuration in the LTE system in 3GPP, which are described in Non-Patent Document 1 (Chapter 5), will be explained with reference to FIG. 2. FIG. 2 is an explanatory diagram showing the configuration of a radio frame used in a communication system of the LTE type. In FIG. 2, one radio frame is 10 ms. The radio frame is divided into 10 subframes of equal size. The subframe is divided into two slots of equal size. The first and sixth subframes of each radio frame include a downlink synchronization signal (SS). The synchronization signal includes a primary synchronization signal (P-SS) and a secondary synchronization signal (S-SS).
[0013] Channels for MBSFN (Multimedia Broadcast multicast service Single Frequency Network) and non-MBSFN are multiplexed on a subframe basis. MBSFN Transmission is a simulcast transmission technique that is 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 transmissions. Hereinafter, a subframe for MBSFN transmission is referred to as an MBSFN subframe.
[0014] Non-patent document 2 describes an example of signaling when allocating MBSFN subframes. Fig. 3 is an explanatory diagram showing the configuration of an MBSFN frame. In Fig. 3, a radio frame including an MBSFN subframe is allocated for each allocation period (radio frame allocation period). An MBSFN subframe is a subframe allocated for MBSFN in a radio frame defined by an allocation period and an allocation offset (radio frame allocation offset), and is a subframe for transmitting multimedia data. A radio frame that satisfies the following formula (1) is a radio frame including an MBSFN subframe. SFN mod radioFrameAllocationPeriod=radioFrameAllocationOffset …(1)
[0015] MBSFN subframe allocation is done by 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.
[0016] Current decisions on channel configuration in the LTE system in 3GPP are described in Non-Patent Document 1 (Chapter 5). It is assumed that the same channel configuration as that of a non-CSG cell is used in a CSG cell (Closed Subscriber Group cell). The physical channel will be explained using FIG. 4. FIG. 4 is an explanatory diagram explaining the physical channel used in the LTE communication system.
[0017] In FIG. 4, the Physical Broadcast channel (PBCH) 401 is a downlink channel transmitted from the base station 102 to the mobile terminal 101. The BCH transport block is mapped to four subframes in a 40 ms interval. There is no explicit signaling of the 40 ms timing. The Physical Control Format Indicator Channel (PCFICH) 402 is transmitted from the base station 102 to the mobile terminal 101. The PCFICH informs the base station 102 to the mobile terminal 101 about the number of OFDM symbols to use for the PDCCHs. The PCFICH is transmitted every subframe.
[0018] 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 of DL-SCH (a downlink shared channel, which is one of the transport channels shown in FIG. 5 described later) and PCH (a paging channel, which is one of the transport channels shown in FIG. 5), and HARQ information related to DL-SCH. 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.
[0019] The Physical Downlink Shared Channel (PDSCH) 404 is a downlink channel transmitted from the base station 102 to the mobile terminal 101. A DL-SCH (downlink shared channel) which is a transport channel and a 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. A MCH (multicast channel) which is a transport channel is mapped to the PMCH.
[0020] 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 Channel Quality Indicator (CQI) report. The CQI is quality information indicating the quality of received data or the quality of a 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.
[0021] 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 signal 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.
[0022] A downlink reference signal is a symbol known in a mobile communication system. Reference signal received power (RSRP) measurement is one of the physical layer measurements of a mobile terminal.
[0023] The transport channel described in Non-Patent Document 1 (Chapter 5) will be explained with reference to Fig. 5. Fig. 5 is an explanatory diagram explaining the transport channel used in the LTE communication system. Fig. 5(A) shows the mapping between the downlink transport channel and the downlink physical channel. Fig. 5(B) shows the mapping between the uplink transport channel and the uplink physical channel.
[0024] The downlink transport channel will now be described. A broadcast channel (BCH) is broadcast to the entire coverage of the base station (cell). The BCH is mapped to a physical broadcast channel (PBCH).
[0025] Retransmission control using HARQ (Hybrid ARQ) is applied to the Downlink Shared Channel (DL-SCH). 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 called persistent scheduling. DL-SCH supports discontinuous reception (DRX) of mobile terminals to reduce power consumption of mobile terminals. DL-SCH is mapped to the physical downlink shared channel (PDSCH).
[0026] The Paging Channel (PCH) supports DRX of mobile terminals to enable low power consumption of the mobile terminals. The PCH is required to be 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.
[0027] 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.
[0028] 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).
[0029] The Random Access Channel (RACH) shown in FIG. 5B is limited to control information. The RACH has a risk of collision. The RACH is mapped to the Physical Random Access Channel (PRACH).
[0030] We will explain HARQ. HARQ is a technology that improves the communication quality of a transmission line by combining Automatic Repeat reQuest and Forward Error Correction. It has the advantage that error correction works effectively by retransmission even for transmission lines whose communication quality changes. In particular, it is possible to obtain further quality improvement by combining the reception result of the initial transmission and the reception result of the retransmission when retransmitting.
[0031] An example of a retransmission method will be described below. If the received data cannot be decoded correctly on the receiving side, in other words, if a CRC (Cyclic Redundancy Check) error occurs (CRC=NG), the receiving side will send a "Nack" to the transmitting side. The transmitting side that receives the "Nack" will retransmit the data. If the received data can be decoded correctly on the receiving side, in other words, if no CRC error occurs (CRC=OK), the receiving side will send an "Ack" to the transmitting side. The transmitting side that receives the "Ack" will send the next data.
[0032] One example of the HARQ method is Chase Combining. Chase Combining is a method in which the same data is transmitted in the initial transmission and retransmission, and the gain is improved by combining the initial transmission data and the retransmission data in the retransmission. This is based on the idea that even if the initial transmission data contains an error, some of it is correct, and by combining the correct parts of the initial transmission data and the retransmission data, data can be transmitted with higher accuracy. Another example of the HARQ method is IR (Incremental Redundancy). IR increases redundancy, and by transmitting a parity bit in the retransmission, the redundancy is increased by combining it with the initial transmission, and the quality is improved by the error correction function.
[0033] The logical channels (hereinafter sometimes referred to as "logical channels") described in Non-Patent Document 1 (Chapter 6) will be explained with reference to 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.
[0034] 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).
[0035] The Paging Control Channel (PCCH) is a downlink channel for transmitting paging information and changes to system information. The PCCH is used when the cell location of the mobile terminal is unknown to the network. The PCCH, which is a logical channel, is mapped to the Paging Channel (PCH), which is a transport channel.
[0036] 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.
[0037] The Multicast Control Channel (MCCH) is a downlink channel for point-to-multipoint transmission. The MCCH is used for transmission of MBMS control information for one or several MTCHs from the network to the mobile terminals. The MCCH is used only by mobile terminals receiving MBMS. The MCCH is mapped to the Multicast Channel (MCH), which is a transport channel.
[0038] A Dedicated Control Channel (DCCH) is a channel that transmits dedicated control information between a mobile terminal and a network on a one-to-one basis. DCCH is used when a mobile terminal is in an RRC connection. DCCH is mapped to an uplink shared channel (UL-SCH) in the uplink and to a downlink shared channel (DL-SCH) in the downlink.
[0039] A Dedicated Traffic Channel (DTCH) is a one-to-one 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, DTCH is mapped to a downlink shared channel (DL-SCH).
[0040] Multicast Traffic Channel (MTCH) is a downlink channel for transmitting traffic data from the network to the mobile terminal. MTCH is a channel used only by mobile terminals receiving MBMS. MTCH is mapped to the Multicast Channel (MCH).
[0041] GCI stands for Global Cell Identity. In LTE, LTE-A (Long Term Evolution Advanced) and UMTS (Universal Mobile Telecommunication System), CSG cells (Closed Subscriber Group cells) are introduced. CSG is explained below (see Chapter 3.1 of Non-Patent Document 3). A CSG cell (Closed Subscriber Group cell) is a cell in which an operator specifies available subscribers (hereinafter, sometimes referred to as a "specific subscriber cell").
[0042] An identified subscriber is permitted to access one or more cells in a PLMN (Public Land Mobile Network). The one or more cells to which an identified subscriber is permitted to access are called "CSG cell(s)". However, there are access restrictions in PLMNs. A CSG cell is a part of a PLMN that broadcasts a unique CSG identity (CSG ID; CSG-ID) and broadcasts "TRUE" in the CSG Indication. Members of a pre-registered and permitted subscriber group access a CSG cell using a CSG-ID, which is access permission information.
[0043] The CSG-ID is broadcast by a CSG cell or cells. There are multiple CSG-IDs in a mobile communication system. And the CSG-ID is used by a mobile terminal (UE) to facilitate the access of CSG-related members.
[0044] The location of a mobile terminal is tracked in units of an area consisting of one or more cells. The purpose of location tracking is to enable tracking the location of a mobile terminal and calling it (the mobile terminal can receive calls) even when it is in standby mode. The area for tracking the location of a mobile terminal is called a tracking area.
[0045] The CSG White List is a list that may be stored in a Universal Subscriber Identity Module (USIM) in which all CSG IDs of CSG cells to which a subscriber belongs are recorded. The CSG White List may also be simply called a white list or an allowed CSG list. The MME performs access control for access of a mobile terminal through a CSG cell (see Chapter 4.3.1.2 of Non-Patent Document 9). Specific examples of access of a mobile terminal include attach, combined attach, detach, service request, and Tracking Area Update procedure (see Chapter 4.3.1.2 of Non-Patent Document 9).
[0046] The service types of a mobile terminal in standby mode are described below (see Chapter 4.3 of Non-Patent Document 3). The service types of a mobile terminal in standby mode include limited service (also called limited service), normal service, and operator service. Limited services are emergency calls, ETWS (Earthquake and Tsunami Warning System), and CMAS (Commercial Mobile Alert System) on acceptable cells, which will be described later. Standard service (also called normal service) is a public service on an appropriate cell, which will be described later. Operator service is a service only for operators on a reserved cell, which will be described later.
[0047] The term "suitable cell" is explained below. A "suitable cell" is a cell on which a UE may camp to receive normal services. Such a cell must satisfy the following conditions (1) and (2).
[0048] (1) The cell is part of the selected PLMN or the registered PLMN, or a PLMN in the "Equivalent PLMN List".
[0049] (2) The following conditions (a) through (d) must be met in accordance with the latest information provided by the Non-Access Stratum (NAS): (a) the cell is not a barred cell; (b) The cell is part of a Tracking Area (TA) that is not part of the "Prohibited LAs for Roaming" list. In that case, the cell must satisfy (1) above. (c) the cell meets the cell selection evaluation 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).
[0050] An "acceptable cell" is explained below. This is a cell on which a UE may camp to receive limited services. Such a cell shall satisfy all of the following requirements (1) and (2).
[0051] (1) The cell is not a barred cell (also called a barred cell), and (2) the cell meets the cell selection evaluation criteria.
[0052] A "barred cell" is indicated in the system information. A "reserved cell" is indicated in the system information.
[0053] "Camping on a cell" means that the UE has completed a cell selection or cell reselection process and has selected a cell for monitoring system information and paging information. The cell on which the UE camps is sometimes called a "serving cell."
[0054] In 3GPP, base stations called Home-NodeB (Home-NB; HNB) and Home-eNodeB (Home-eNB; HeNB) are under consideration. HNB in UTRAN or HeNB in E-UTRAN is a base station for home, corporate, and commercial access services, for example. Non-Patent Document 4 discloses three different modes of access to HeNB and HNB. Specifically, they are an open access mode, a closed access mode, and a hybrid access mode.
[0055] 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, a HeNB or HNB is operated as a CSG cell to which non-CSG members are also allowed to access at the same time. A hybrid access mode cell (also called a hybrid cell) is, in other words, a cell that supports both open access mode and closed access mode.
[0056] In 3GPP, among all PCIs (Physical Cell Identities), there is a PCI range reserved by the network for use by CSG cells (see Chapter 10.5.1.1 of Non-Patent Document 1). Dividing the PCI range is sometimes called PCI split. PCI split information is notified by the 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, all 504 codes. On the other hand, a mobile terminal that has PCI split information can perform a cell search using the PCI split information.
[0057] Furthermore, 3GPP is currently formulating standards for Long Term Evolution Advanced (LTE-A) as Release 10 (see Non-Patent Documents 6 and 7).
[0058] In the LTE-A system, support for relays and relay nodes (RNs) is being considered in order to obtain high communication speeds, high throughput at cell edges, new coverage areas, and the like. The relay nodes are wirelessly connected to a radio access network via a donor cell (Donor eNB; DeNB). Within the range of the donor cell, the link from the network (Network: NW) to the relay node shares the same frequency band (hereinafter sometimes referred to as "frequency band") as the link from the network to the UE. In this case, a Release 8 UE can also connect to the donor cell. The link between the donor cell and the relay node is called a backhaul link, and the link between the relay node and the UE is called an access link.
[0059] 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. In this way, the relay can prevent the transmission of the relay from interfering with the reception of the own relay.
[0060] In 3GPP, in addition to normal eNBs (macro cells), pico eNBs (pico cells), HeNB / HNB / CSG cells, nodes for hot zone cells, relay nodes, remote radio heads (RRHs), and other so-called local nodes are being considered.
[0061] In LTE, a frequency band (hereinafter sometimes referred to as "operating band") that can be used for communication is predetermined. Non-patent document 8 describes the frequency band. In communication by FDD (Frequency Division Duplex), a downlink frequency band (hereinafter sometimes referred to as "downlink frequency band") and a paired uplink frequency band (hereinafter sometimes referred to as "uplink frequency band") are predetermined, and the uplink frequency band is different from the downlink frequency band. This is because a downlink and an uplink are always required in conventional communication such as voice, and FDD allows transmission and reception to be performed simultaneously by dividing the frequency between the downlink and the uplink.
[0062] In FDD, a default value of the interval (TX-RX frequency separation: TX-RX frequency interval) between the carrier frequency of the resource used for the downlink (hereinafter sometimes referred to as the "downlink carrier frequency") and the carrier frequency of the resource used for the uplink (hereinafter sometimes referred to as the "uplink carrier frequency") is determined for each frequency band. Non-Patent Document 8 describes the default value of the TX-RX frequency interval.
[0063] In LTE, a cell broadcasts information on the frequency band and uplink carrier frequency used by the cell to UEs served by the cell as broadcast information. Specifically, the frequency band information is included in SIB1. The uplink carrier frequency is included in SIB2. If the uplink carrier frequency is not included in SIB2, the uplink carrier frequency is derived from the downlink carrier frequency using a default value for the TX-RX frequency interval. The UE recognizes the downlink carrier frequency by selecting or reselecting a cell, and can obtain the frequency band and uplink carrier frequency used by the cell by receiving broadcast information from the cell.
[0064] As disclosed in Non-Patent Document 1, 3GPP is currently formulating the "Long Term Evolution Advanced (LTE-A)" standard as Release 10.
[0065] In the LTE-A system, in order to support wider frequency bandwidths (transmission bandwidths) of up to 100 MHz, carrier aggregation (CA) is being considered, which aggregates two or more component carriers (CCs).
[0066] While an LTE-compatible Release 8 or 9 UE can only transmit and receive on a CC corresponding to one serving cell, a Release 10 UE is expected to have the capability to simultaneously transmit and receive on CCs corresponding to multiple serving cells, or to only receive, or to only transmit.
[0067] Each CC uses a Release 8 or 9 configuration, and CA supports contiguous CCs, non-contiguous CCs, and CCs with different frequency bandwidths. It is not possible for a UE to configure more uplink CCs (UL CCs) than the number of downlink CCs (DL CCs). CCs configured by the same eNB do not need to provide the same coverage. CCs are compatible with Release 8 or 9.
[0068] In CA, there is one independent HARQ entity per serving cell in both uplink and downlink. A transport block is generated per TTI per serving cell. Each transport block and HARQ retransmission is mapped to a single serving cell.
[0069] When CA is configured, the UE has only one RRC connection with the network. In the RRC connection, one serving cell provides NAS mobility information and security input. This cell is called a Primary Cell (PCell). In the downlink, the carrier corresponding to the PCell is the Downlink Primary Component Carrier (DL PCC). In the uplink, the carrier corresponding to the PCell is the Uplink Primary Component Carrier (UL PCC).
[0070] According to UE capabilities, a secondary cell (SCell) is configured to form a pair of a PCell and a serving cell. In the downlink, the carrier corresponding to the SCell is a downlink secondary component carrier (DL SCC). In the uplink, the carrier corresponding to the SCell is an uplink secondary component carrier (UL SCC).
[0071] For one UE, a set of one PCell and a serving cell consisting of one or more SCells is configured.
[0072] In each SCell, in addition to downlink (DL) resources, uplink (UL) resources can be used by the UE. The number of DL SCCs is equal to or greater than the number of UL SCCs. There is no SCell that is used only for UL resources. For one UE, each UL resource belongs to only one serving cell. The number of serving cells depends on the UE capabilities.
[0073] The PCell is changed only in the HO procedure. The PCell is used to transmit the PUCCH. Note that the PUCCH for HARQ of the DL-SCH without the UL-SCH is transmitted only on the UL PCC. Unlike the SCells, the PCell is not de-activated.
[0074] Re-establishment is triggered when the PCell experiences RLF (Radio link failure). It is not triggered in SCells. NAS information is obtained from the PCell.
[0075] Reconfiguration, addition, and removal of SCells are performed by the RRC. In a handover within LTE, the RRC also adds, removes, and reconfigures SCells used with the target PCell.
[0076] When adding a SCell, dedicated RRC signaling is used to transmit all necessary system information (SI) for the SCell, i.e., this is performed in connected mode, and the UE does not need to receive SI broadcast from the SCell.
[0077] It is considered that the addition and modification of the SCell will be notified to the mobile terminal by the PCell using an "RRC Connection Reconfiguration message" of dedicated RRC signaling (see Non-Patent Document 2). It is considered that the release of the SCell will be notified to the mobile terminal by the PCell using an "RRC Connection Reconfiguration message" of dedicated RRC signaling, or will be triggered by "RRC Connection re-establishment" (see Non-Patent Document 2). The "RRC Connection Reconfiguration message" of dedicated RRC signaling includes "SCell To AddModList" and "SCell To ReleaseList".
[0078] In addition, in each cell, SIB2 indicates the carrier frequency of the uplink resource.
[0079] Non-Patent Document 10 discloses that a CSG indication and a CSG-ID can be set for each cell (CC). However, Non-Patent Document 10 does not disclose a method for notifying a mobile terminal of the setting contents. Furthermore, Non-Patent Document 10 does not raise any problem or disclose any solution regarding the relationship between the CSG to which the SCell belongs and the CSG to which the mobile terminal belongs.
[0080] Non-Patent Document 2 discloses that the PCell notifies the mobile terminal of the addition and modification of the SCell using an "RRC Connection Reconfiguration message" of dedicated RRC signaling. The "RRC Connection Reconfiguration message" of dedicated RRC signaling for the addition and modification of the SCell does not include a CSG indication and a CSG-ID. Non-Patent Document 2 does not disclose a method for setting the CSG indication and CSG-ID for each SCell, or a method for notifying the mobile terminal of the setting contents. Furthermore, Non-Patent Document 2 does not disclose any problem or solution regarding the relationship between the CSG to which the SCell belongs and the CSG to which the mobile terminal belongs. [Prior art documents] [Non-patent literature]
[0081] [Non-Patent Document 1] 3GPP TS36.300 V10.2.0 [Non-Patent Document 2] 3GPP TS36.331 V10.0.0 [Non-Patent Document 3] 3GPP TS36.304 V10.0.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.3.0 [Non-Patent Document 8] 3GPP TS 36.101 V10.0.0 [Non-Patent Document 9] 3GPP TR 23.830 V9.0.0 [Non-Patent Document 10] 3GPP R2-104041 Summary of the Invention [Problem to be solved by the invention]
[0082] In the LTE-A system, in order to improve communication speed, it is considered to support a frequency bandwidth larger than that of the LTE system, specifically, a frequency bandwidth of up to 100 MHz. As one method of supporting this, carrier aggregation (CA) is being studied. In carrier aggregation, a pair of serving cells is formed for a mobile terminal by a PCell and an SCell.
[0083] As described above, Non-Patent Document 2 and Non-Patent Document 10 do not describe a method of notifying a mobile terminal of a CSG indication for each SCell and a CSG-ID. In addition, Non-Patent Document 2 and Non-Patent Document 10 do not describe the relationship between a CSG to which an SCell belongs and a CSG to which a mobile terminal belongs. Therefore, a problem occurs in that the operation of a communication system cannot be uniquely determined and appropriate services cannot be provided.
[0084] An object of the present disclosure is to provide a communication system etc. capable of providing appropriate services while improving communication speeds using carrier aggregation. [Means for solving the problem]
[0085] The communication system disclosed herein is a communication system having a communication terminal device and a plurality of cells capable of wireless communication between the communication terminal device, and when a connection is established between the communication terminal device and a primary cell, which is one of the plurality of cells, the communication terminal device determines whether it is possible to connect to a candidate cell that is a candidate for a secondary cell, which is a cell capable of wireless communication in parallel with the primary cell, and notifies the primary cell of the determination result using an RRC (Radio Resource Control) message, and when the primary cell is notified by the communication terminal device of the determination result that it is possible to connect to the candidate cell, the primary cell sets the candidate cell as the secondary cell.
[0086] The communication terminal device disclosed herein is a communication terminal device in a communication system that includes a plurality of cells capable of wireless communication between the communication terminal device and the communication terminal device, and in which a connection has been established between the communication terminal device and a primary cell, which is one of the plurality of cells, the communication terminal device, and is characterized in that it determines whether it is possible to connect to a candidate cell that is a candidate for a secondary cell, which is a cell capable of wireless communication in parallel with the primary cell, and notifies the primary cell of the result of the determination using an RRC (Radio Resource Control) message.
[0087] The primary cell of the present disclosure is a primary cell in a communication system that includes a communication terminal device and a plurality of cells capable of wireless communication between the communication terminal device, and when a connection is established between a primary cell, which is one of the plurality of cells, and the communication terminal device, the communication terminal device determines whether it is possible to connect to a candidate cell that is a candidate for a secondary cell, which is a cell capable of wireless communication in parallel with the primary cell, and notifies the primary cell of the determination result using an RRC (Radio Resource Control) message, and is characterized in that when the communication terminal device notifies the determination result that it is possible to connect to the candidate cell, the candidate cell is set as the secondary cell. Effect of the Invention
[0088] According to the present disclosure, it is possible to improve communication speeds using carrier aggregation while stabilizing the operation of the communication system, thereby making it possible to provide appropriate services.
[0089] The objects, features, aspects, and advantages of the present disclosure will become more apparent from the following detailed description and the accompanying drawings. [Brief description of the drawings]
[0090] [Figure 1] FIG. 1 is an explanatory diagram showing the configuration of an LTE communication system. [Diagram 2] FIG. 1 is an explanatory diagram showing the configuration of a radio frame used in an LTE communication system. [Diagram 3] FIG. 2 is an explanatory diagram showing the structure of an MBSFN frame. [Figure 4] FIG. 2 is an explanatory diagram illustrating physical channels used in an LTE communication system. [Diagram 5] FIG. 1 is an explanatory diagram illustrating transport channels used in an LTE communication system. [Figure 6] FIG. 2 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. 2 is a block diagram showing a configuration of a mobile terminal. [Figure 9] FIG. 2 is a block diagram showing the configuration of a base station. [Figure 10] FIG. 2 is a block diagram showing the configuration of an MME. [Figure 11] FIG. 2 is a block diagram showing the configuration of a HeNBGW. [Figure 12] 1 is a flowchart showing an outline of operations from cell search to standby performed by a mobile terminal (UE) in an LTE communication system. [Figure 13]FIG. 1 is a diagram illustrating the concept of CA. [Figure 14] FIG. 11 is a diagram showing an example of a sequence of a communication system in the second embodiment. [Figure 15] FIG. 11 is a diagram showing an example of a sequence of a communication system in a first modification of the second embodiment. [Figure 16] FIG. 11 is a diagram showing an example of a sequence of a communication system in the third embodiment. [Figure 17] FIG. 11 is a diagram showing another example of the sequence of the communication system in the third embodiment. [Figure 18] FIG. 13 is a diagram showing an example of a sequence of a communication system in the fourth embodiment. [Figure 19] FIG. 13 is a diagram showing another example of the sequence of the communication system in the fourth embodiment. [Figure 20] FIG. 13 is a diagram showing an example of a sequence of a communication system in the fifth embodiment. [Figure 21] FIG. 23 is a diagram showing an example of a sequence of a communication system in a first modification of the fifth embodiment. [Figure 22] FIG. 23 is a diagram showing an example of a sequence of a communication system in the sixth embodiment. [Diagram 23] FIG. 1 is a diagram showing a sequence of a communication system relating to a handover method from an eNB or a HeNB to a CSG cell or a hybrid cell, as disclosed in Non-Patent Document 1. [Figure 24] FIG. 23 is a diagram showing an example of a sequence of a communication system in the eighth embodiment. [Diagram 25] FIG. 23 is a diagram showing an example of a sequence of a communication system in a first modification of the eighth embodiment. [Figure 26] FIG. 23 is a diagram showing an example of a sequence of a communication system in a second modification of the eighth embodiment. [Figure 27] FIG. 23 is a diagram showing an example of a sequence of a communication system in a third modification of the eighth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0091] Embodiment 1 Fig. 7 is a block diagram showing the overall configuration of an LTE-based 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 as shown in Fig. 7 has been proposed for E-UTRAN (see Chapter 4.6.1 of Non-Patent Document 1).
[0092] Explained below is Fig. 7. A mobile terminal device (hereinafter referred to as "mobile terminal" or "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. The base station 72 is classified into an eNB72-1 which is a macrocell, and a Home-eNB72-2 which is a local node. The eNB72-1 corresponds to a large-scale base station device, and has a relatively large-scale coverage as the coverage range in which communication with the mobile terminal (UE) 71 is possible. The Home-eNB72-2 corresponds to a small-scale base station device, and has a relatively small-scale coverage as its coverage.
[0093] 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. A plurality of 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.
[0094] 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. A plurality of Home-eNB72-2 are connected to one MME unit 73. Alternatively, the Home-eNB72-2 is connected to the MME unit 73 via a Home-eNB GateWay (HeNBGW) 74. The Home-eNB72-2 and the HeNBGW74 are connected by an S1 interface, and the HeNBGW74 and the MME unit 73 are connected via an S1 interface. One or a plurality of Home-eNB72-2 are connected to one HeNBGW74, and information is communicated via the S1 interface. The HeNBGW74 is connected to one or a plurality of MME units 73, and information is communicated via the S1 interface. The MME unit 73 and the HeNBGW 74 correspond to upper node devices, and control connections between the mobile terminal (UE) 71 and the base stations eNB 72-1 and Home-eNB 72-2.
[0095] Furthermore, the following configuration is currently being considered in 3GPP. The X2 interface between the Home-eNBs 72-2 is supported. That is, the Home-eNBs 72-2 are connected to each other via the X2 interface, and control information is communicated between the Home-eNBs 72-2. From the MME unit 73, the HeNBGW 74 appears as the Home-eNB 72-2. From the Home-eNB 72-2, the HeNBGW 74 appears as the MME unit 73. In either case where the Home-eNB 72-2 is connected to the MME unit 73 via the HeNBGW 74 or where the Home-eNB 72-2 is directly connected to the MME unit 73, the interface between the Home-eNB 72-2 and the MME unit 73 is the same as the S1 interface. The HeNBGW 74 does not support mobility to or from the Home-eNB 72-2 across multiple MME units 73. The Home-eNB 72-2 supports only one cell.
[0096] FIG. 8 is a block diagram showing the configuration of a mobile terminal (mobile terminal 71 in FIG. 7). 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 encoding such as error correction is performed. There may be data that is directly output from the transmission data buffer unit 803 to a modulation unit 805 without being encoded. The data that has been encoded by the encoder unit 804 is modulated by the modulation unit 805. The modulated data is converted into a baseband signal, and then output to a frequency conversion unit 806, where it is converted into a radio transmission frequency. Thereafter, a transmission signal is transmitted from an antenna 807 to the base station 72.
[0097] Moreover, the receiving process of the mobile terminal 71 is executed as follows. A radio signal from the base station 72 is received by the antenna 807. The received signal is converted from a radio receiving 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 such as error correction is performed. Of the decoded data, the control data is passed to the protocol processing unit 801, and the 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.
[0098] FIG. 9 is a block diagram showing the configuration of a base station (base station 72 in FIG. 7). The transmission process of the base station 72 shown in FIG. 9 will be described. The EPC communication unit 901 transmits and receives data between the base station 72 and the EPC (the MME unit 73, the HeNBGW 74, etc.). The other base station communication unit 902 transmits and receives data with other base stations. The EPC communication unit 901 and the other base station communication unit 902 each exchange information with a protocol processing unit 903. The control data from the protocol processing unit 903, and the 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.
[0099] The data stored in the transmission data buffer unit 904 is passed to an encoder unit 905, where it undergoes encoding processing 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 processing. The encoded data is modulated in 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.
[0100] Moreover, the reception process of the base station 72 is executed 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 such as error correction is 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 unit 901 to 910.
[0101] 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 of discovering 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.
[0102] 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 geographical area. Therefore, the Home-eNB72-2 in this case needs to be connected to a different HeNBGW74 depending on the location.
[0103] FIG. 10 is a block diagram showing the configuration of an MME. FIG. 10 shows the configuration of an MME 73a included in the MME unit 73 shown in FIG. 7 described 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 between the MME 73a and a base station 72 via an S1 interface. 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.
[0104] When 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. When 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.
[0105] 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 a control plane control unit 1005. A result of processing in the control plane control unit 1005 is transmitted to the PDN GW via a PDN GW communication unit 1001. In addition, a result of processing in the control plane control unit 1005 is transmitted to one or more base stations 72 by the S1 interface via a base station communication unit 1002, and is also transmitted to one or more HeNBGW 74 via the HeNBGW communication unit 1004.
[0106] 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, etc., and performs general 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 called idle), generation and control of paging signals in the standby state, addition, deletion, update, search, and tracking area (TA) list management for one or more mobile terminals 71 under its control.
[0107] The MME 73a starts 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.
[0108] In the management of CSG-ID, the relationship between the mobile terminal corresponding to the CSG-ID and the CSG cell is managed (added, deleted, updated, searched). For example, the relationship may be between one or more mobile terminals registered for user access to a certain CSG-ID and the CSG cell belonging to the CSG-ID. In the management of whitelist, the relationship between the mobile terminal and the CSG-ID is managed (added, deleted, updated, searched). For example, the whitelist may store one or more CSG-IDs registered by a user of a certain mobile terminal. The management of these CSGs 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 the control unit 1006 is omitted in FIG. 10, it is connected to each unit 1001 to 1005.
[0109] 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 allows the execution of paging optimization as an option.
[0110] Fig. 11 is a block diagram showing a configuration of the HeNBGW 74 shown in Fig. 7 which is a HeNBGW. 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 a process of transmitting registration information and the like out of the data from the MME 73a passed via the EPC communication unit 1101 to a plurality of 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 a plurality of Home-eNBs 72-2 via the S1 interface.
[0111] Data that does not require processing in the location processing unit 1103 and is merely passed through (transmitted) is passed from the EPC communication unit 1101 to the base station communication unit 1102, and transmitted to one or more Home-eNBs 72-2 via the S1 interface. A series of processes in the HeNBGW 74 is controlled by a control unit 1104. Thus, although omitted in FIG. 11, the control unit 1104 is connected to each of the units 1101 to 1103.
[0112] The functions of the HeNBGW 74 currently being discussed in 3GPP are shown below (see Chapter 4.6.2 of Non-Patent Document 1). The HeNBGW 74 relays S1 applications. Although it is a part of the procedure of the MME 73a to the Home-eNB 72-2, the HeNBGW 74 terminates S1 applications not related to the mobile terminal 71. When the HeNBGW 74 is deployed, procedures not related to the mobile terminal 71 are communicated between the Home-eNB 72-2 and the HeNBGW 74, and between the HeNBGW 74 and the MME 73a. An X2 interface is not set between the HeNBGW 74 and other nodes. The HeNBGW 74 allows the execution of paging optimization as an option.
[0113] Next, an example of a general cell search method in a mobile communication system is shown. FIG. 12 is a flow chart showing an outline of a 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, the mobile terminal synchronizes slot timing and frame timing using a first synchronization signal (P-SS) and a second synchronization signal (S-SS) transmitted from a surrounding base station. A synchronization code that corresponds one-to-one to a PCI (Physical Cell Identity) assigned to each cell is assigned to the synchronization signal (SS) including the P-SS and S-SS. Currently, 504 types of PCI are considered as the number of PCIs, and the 504 types of PCIs are used to synchronize and detect (identify) the PCI of the synchronized cell.
[0114] 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 called RSRP) is measured. A code that has a one-to-one correspondence with the PCI is used for the reference signal RS, and the cell can be separated from other cells by correlating with the code. By deriving the code for the RS of the cell from the PCI identified in step ST1201, it becomes possible to detect the RS and measure the RS received power.
[0115] Next, in step ST1203, the cell with the best RS reception quality (for example, the cell with the highest RS reception power, that is, the best cell) is selected from one or more cells detected up to step ST1202.
[0116] 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 the 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 the transmission bandwidth configuration: dl-bandwidth), the number of transmitting antennas, and the SFN (System Frame Number).
[0117] Next, in step ST1205, the DL-SCH of the cell is received based on the cell configuration information of the MIB, and SIB (System Information Block) 1 in the broadcast information BCCH is obtained. SIB 1 includes information on access to the cell, information on cell selection, and scheduling information of other SIBs (SIBk; k is an integer ≧2). SIB 1 also includes a TAC (Tracking Area Code).
[0118] Next, in step ST1206, the mobile terminal compares the TAC of the SIB1 received in step ST1205 with the TAC in the tracking area (TA) 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 the 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 a core network (EPC) (including MME, etc.) through the cell. The core network updates the TA list based on the identification number (UE-ID, etc.) of the mobile terminal transmitted from the mobile terminal together with a 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. After that, the mobile terminal enters standby mode in the cell.
[0119] In LTE, LTE-A and Universal Mobile Telecommunication System (UMTS), the introduction of Closed Subscriber Group (CSG) cells is being considered. As mentioned above, only one or more mobile terminals registered in a CSG cell are allowed to access it. A CSG cell and one or more registered mobile terminals constitute one CSG. A CSG thus constituted is assigned a unique identification number called a CSG-ID. Note that one CSG may have multiple CSG cells. Once a mobile terminal registers in one CSG cell, it can access other CSG cells in the CSG to which that CSG cell belongs.
[0120] Also, Home-eNBs in LTE and LTE-A and Home-NBs in UMTS may be used as CSG cells. 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 CSG-ID, TAI (Tracking Area Identity), and TAC. As long as CSG-ID and TAC are associated with each other, either one of them may be used. Also, as long as CSG-ID and TAC are associated with GCI (Global Cell Identity), GCI may be used.
[0121] From the above, a mobile terminal that does not have a whitelist (in this disclosure, 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 the CSG cell with the registered CSG-ID and non-CSG cells.
[0122] In 3GPP, there is a discussion on dividing all PCIs (Physical Cell Identities) into those for CSG cells and those for non-CSG cells (see Non-Patent Document 1). Of all PCIs, there is a PCI range reserved by the network for use by CSG cells (see Chapter 10.5.1.1 of Non-Patent Document 1). Dividing a PCI range is sometimes called PCI split. PCI split information is notified by 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). On the other hand, a mobile terminal that has PCI split information can perform a cell search using the PCI split information.
[0123] Also, in 3GPP, it has been decided that the PCI for hybrid cells is not included in the range of the PCI for CSG cells (see Chapter 10.7 of Non-Patent Document 1).
[0124] In 3GPP, there are two modes for the mobile terminal to select or reselect a CSG cell. The first mode 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 the selection of a PLMN is completed, 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 in the allowed CSG list. If the allowed CSG list of the mobile terminal is empty, the mobile terminal stops the autonomous search function for CSG cells (see Chapter 5.2.4.8.1 of non-patent document 3).
[0125] The second mode is a manual mode. The features of the manual mode are as follows: The mobile terminal shows the user 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 list of CSGs, the mobile terminal camps on a cell with the selected CSG ID and attempts to register (see non-patent document 3).
[0126] HeNBs and HNBs are required to support various services. For example, operators register mobile terminals with certain HeNBs and HNBs and allow only registered mobile terminals to access HeNB and HNB cells, thereby increasing the wireless resources that the mobile terminals can use and enabling high-speed communication. To compensate for this, operators set a higher fee than usual.
[0127] In order to realize such services, CSG cells (Closed Subscriber Group cells) that can be accessed only by registered (subscribed, member) mobile terminals are introduced. It is required that many CSG cells (Closed Subscriber Group cells) are installed in shopping streets, apartment buildings, schools, companies, etc. For example, a CSG cell is installed for each store in a shopping street, 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. HeNB / HNB is required not only to complement communication outside the coverage of a macro cell (area complementation type HeNB / HNB), but also to support various services as described above (service provision type HeNB / HNB). For this reason, there are also cases where HeNB / HNB is installed within the coverage of a macro cell.
[0128] As mentioned above, in the LTE-A system, CA, which aggregates, i.e., consolidates, two or more CCs, is being considered in order to support a frequency bandwidth of up to 100 MHz, which is wider than the frequency bandwidth of the LTE system.
[0129] Fig. 13 is a diagram showing the concept of CA. The eNB shown in Fig. 13 configures a cell n consisting of DL CCn and UL CCn associated with DL-CCn by DL / UL links according to SIB2. The carrier frequency of DL CCn is indicated as Fn(DL), and the carrier frequency of UL CCn is indicated as Fn(UL). Here, n is an integer from 1 to 5.
[0130] The UE camps on cell 1 and performs an RRC connection as indicated by arrow 1301. This makes cell 1 the PCell.
[0131] Thereafter, the eNB notifies the UE of information on the CCs to be aggregated by dedicated RRC signaling indicated by arrow 1302. As the information on the CCs, information on cell m consisting of DL CCm and UL CCm, for example, system information, is notified. Here, m is an integer from 2 to 5. In this way, the eNB notifies the UE of the information on the CCs, so that cells 2 to 5 become SCells.
[0132] In this manner, the eNB performs CA for the UE using cells 1 to 5. Then, the UE performs communication with cells 1 to 5 based on CA, as indicated by arrow 1303.
[0133] The following shows an example of the configuration of a UE that supports CA. In the configuration shown in FIG. 8 above, some or all of the modulation unit 805, frequency conversion unit 806, antenna 807, and demodulation unit 808 may be made broadband. On the transmitting side, some or all of the modulation unit 805, frequency conversion unit 806, and antenna 807 may be made to operate in a band including a predetermined number of consecutive UL CCs. On the receiving side, some or all of the antenna 807, frequency conversion unit 806, and demodulation unit 808 may be made to operate in a band including a predetermined number of consecutive DL CCs. In this way, it becomes possible to support CA using a predetermined number of consecutive UL CCs or DL CCs.
[0134] As another method, some or all of the modulation unit 805, the frequency conversion unit 806, the antenna 807, and the demodulation unit 808 may be provided in parallel in a plurality of configurations to operate in a band including a predetermined number of non-contiguous UL CCs or DL CCs. On the transmitting side, some or all of the modulation unit 805, the frequency conversion unit 806, and the antenna 807 may be provided in parallel in a plurality of configurations to operate in a band including a predetermined number of non-contiguous UL CCs. On the receiving side, some or all of the antenna 807, the frequency conversion unit 806, and the demodulation unit 808 may be provided in parallel in a plurality of configurations to operate in a band including a predetermined number of non-contiguous DL CCs. In this way, it is possible to support CA using a predetermined number of non-contiguous UL CCs or DL CCs. The above two configurations may be appropriately combined.
[0135] The following shows an example of the configuration of an eNB that supports CA. In the configuration shown in Fig. 9 above, a protocol processing unit 903 processes UEs that perform CA for each cell configured by the eNB, and a transmission data buffer unit 904, an encoder unit 905, a modulator unit 906, a frequency converter unit 907, an antenna 908, a demodulator unit 909, and a decoder unit 910 are configured for each cell. In this way, it becomes possible to perform CA for UEs by the cells configured by the eNB.
[0136] The problem to be solved by the first embodiment will be described below. Non-Patent Document 10 discloses that a CSG indication and a CSG-ID can be set for each cell (CC). However, Non-Patent Document 10 does not disclose a method for notifying a mobile terminal of the setting contents. Therefore, the operation of the communication system cannot be uniquely determined, and a problem occurs in that appropriate services cannot be provided.
[0137] The solution in the first embodiment is as follows. Each cell (CC) notifies a mobile terminal being served of a CSG indication and a CSG-ID set for each cell (CC) by using broadcast information. In addition, during a call, that is, notification of a CSG indication and a CSG-ID of the SCell to a mobile terminal in an RRC_CONNECTED state, is performed by an "RRC Connection Reconfiguration message" of dedicated RRC signaling from the PCell.
[0138] The above-described first embodiment can provide the following effects. A method of notifying a mobile terminal of a CSG indication and a CSG-ID set for each cell (CC) is uniquely determined, enabling stable service provision. The first embodiment can achieve an improvement in communication speed using stable carrier aggregation.
[0139] Embodiment 2 The problem to be solved in the second embodiment will be described below. When the first embodiment is used, the following problem occurs. As described above, when a mobile terminal accesses through a CSG cell, the MME executes access control, that is, restricts access from the UE to the CSG cell. In other words, the base station does not restrict access to the CSG. Therefore, for a UE that is not registered in the CSG to which the cell belongs, the cell (CC) may be set as an SCell and made active.
[0140] Therefore, in a communication system, if the MME executes access control in access of a mobile terminal through a CSG cell, the following problem occurs. Consider a case where a base station sets a cell as an SCell for a mobile terminal that is not registered in a CSG to which the cell belongs. In this case, after the cell is set as an SCell, access of the mobile terminal through the cell is not permitted due to access control in the MME. In such a case, carrier aggregation cannot be executed. Thus, when a base station has a cell that belongs to a CSG, a problem occurs in that it may not be possible to realize an improvement in communication speed using carrier aggregation.
[0141] Furthermore, when a base station sets a mobile terminal that is not registered in a CSG to which a cell belongs as an SCell, the following problem occurs in the mobile terminal. The mobile terminal is uncertain as to whether to communicate through the cell (CC) in accordance with the addition or update of the SCell notified from the PCell, or to determine that the cell (CC) is inaccessible using a CSG access restriction based on a whitelist stored in the USIM in the mobile terminal. This causes a problem that the operation of the mobile terminal becomes unstable. Therefore, a problem occurs in that the operation of the communication system is not uniquely determined, and appropriate services cannot be provided.
[0142] The solution in the second embodiment is as follows. When a cell is configured as an SCell, the communication system is capable of providing a normal service to a mobile terminal through the cell. When a SCell is configured, the mobile terminal determines that it is possible to receive a normal service through the cell.
[0143] Furthermore, when the cell is configured as an SCell, the communication system may be capable of providing a normal service to the mobile terminal through the cell even when the cell belongs to a CSG and the mobile terminal is a mobile terminal that is not registered in the CSG. When the mobile terminal is configured as an SCell, the mobile terminal may determine that it is capable of receiving a normal service through the cell even when the mobile terminal is not registered in the CSG to which the cell belongs.
[0144] As specific examples of a case where a cell is configured as an SCell, the following two cases (1) and (2) are disclosed.
[0145] (1) Notification of configuration contents as an SCell to a mobile terminal. Specific examples of the configuration contents include a CSG-ID and a CSG indication for each CC.
[0146] (2) The configuration contents as the SCell are not notified to the mobile terminal. Specific examples of the configuration contents include a CSG-ID and a CSG indication for each CC. The following two cases (a1) and (a2) are disclosed as specific examples of not notifying the configuration contents to the mobile terminal. (a1) A case where notification of the configuration contents is omitted. Specific examples of the configuration contents include a CSG-ID and a CSG indication for each CC. (a2) A case where the SCell does not belong to a CSG. In other words, a case where the SCell is not a CSG cell.
[0147] As specific examples of a case where a cell is configured as an SCell, the following two cases (1) and (2) are disclosed.
[0148] (1) Receive configuration contents as an SCell. Specific examples of the configuration contents include a CSG-ID and a CSG indication for each CC.
[0149] (2) The setting contents are not received as SCell.
[0150] By implementing the solution in the second embodiment, even if a base station has a cell belonging to a CSG, it is possible to improve the communication speed using carrier aggregation. In addition, it is possible to make the operation of a mobile terminal unique, and it is possible to provide an appropriate service.
[0151] Specific examples of the operation of the MME are disclosed below. The MME does not perform access control of a mobile terminal through a cell configured in an SCell by a base station. The MME may not perform access control of a mobile terminal through a CSG cell configured in an SCell by a base station. The MME may only perform access control of a mobile terminal through a PCell. The MME may only perform access control of a mobile terminal through a PCell belonging to a CSG. The MME may only perform access control of a mobile terminal through a PCell that is a CSG cell.
[0152] As specific examples of the operation of a base station, the following two (1) and (2) are disclosed.
[0153] (1) When performing carrier aggregation, the base station can configure any cell in the base station as a SCell. Also, when performing carrier aggregation, the base station may be able to configure any cell as a SCell even if the base station includes a cell belonging to a CSG.
[0154] (2) When performing carrier aggregation, the base station can activate any cell in the base station as a SCell. Also, when performing carrier aggregation, the base station may be able to activate any cell as a SCell even if the base station includes a cell belonging to a CSG.
[0155] Specific examples of the operation of the mobile terminal are disclosed below. The mobile terminal does not impose a CSG access restriction on a cell (hereinafter, may be simply referred to as an "SCell") whose configuration content has been notified as an SCell. The following three (1) to (3) are disclosed as specific examples of a method in which the mobile terminal does not impose a CSG access restriction.
[0156] (1) Even if the CSG-indication and CSG-ID of the SCell are included in the configuration content as an SCell, the mobile terminal shall not restrict access using the CSG-indication and CSG-ID. For example, the CSG-ID of the SCell included in the configuration content as an SCell shall not be compared with the CSG-ID in the USIM of the mobile terminal. Alternatively, even if the CSG-ID of the SCell included in the configuration content as an SCell does not match the CSG-ID included in the USIM of the mobile terminal, it may not be determined that access is impossible. In addition, the CSG-indication and CSG-ID of the SCell may not be notified by the configuration as an SCell.
[0157] (2) It is assumed that no access restriction is performed using the CSG-indication and CSG-ID broadcast from the cell configured as the SCell using broadcast information. For example, the CSG-ID broadcast from the cell configured as the SCell using broadcast information is not compared with the CSG-ID in the USIM of the mobile terminal. Alternatively, even if the CSG-ID broadcast from the cell configured as the SCell using broadcast information does not match the CSG-ID included in the USIM of the mobile terminal, it may not be determined that access is impossible. Also, the CSG-ID broadcast using broadcast information from the cell configured as the SCell may not be received or may be ignored. Also, the SIB1 broadcast from the cell configured as the SCell may not be received or may be ignored. Also, the SIB broadcast from the cell configured as the SCell may not be received or may be ignored. Also, the broadcast information broadcast from the cell configured as the SCell may not be received or may be ignored.
[0158] (3) A combination of (1) and (2) above.
[0159] As mentioned above, in CSG cells, preferential treatment of services for CSG members belonging to the same CSG is being considered. Specific examples of preferential treatment include preferential allocation of resources to CSG members, or discounts on communication fees for CSG members. Accordingly, it is conceivable that billing settings may differ between CSG members and non-CSG members.
[0160] A specific example of charging settings when the second embodiment is used is shown below. A specific example of a decision body is the core network side. As specific examples of entities on the core network side, the following two entities (1) and (2) are disclosed. (1) MME. (2) HSS (Home Subscriber Server).
[0161] As specific examples of charging settings, the following three (1) to (3) are disclosed. (1) The use of SCells not registered in a CSG shall be charged in the same way as that of CSG-registered members. (2) The use of SCells not registered in a CSG shall be charged in the same way as that of CSG-registered members. (3) The use of SCells not registered in a CSG shall be charged in the same way as that of PCells.
[0162] As specific examples of service handling, the following three items (1) to (3) are disclosed. (1) The use of SCells not registered with the CSG shall be handled in the same way as services for CSG-registered members. (2) The use of SCells not registered with the CSG shall be handled in the same way as services for CSG-registered members. (3) The use of SCells not registered with the CSG shall be handled in the same way as services for PCells.
[0163] Next, a specific example of a sequence of the communication system in the second embodiment will be described with reference to Fig. 14. Fig. 14 is a diagram showing an example of a sequence of the communication system in the second embodiment. In this operation example, a case will be described in which a base station A having a plurality of cells (CC) including a cell 1 and a cell 2 exists, a UE selects cell 1 in the base station A as the best cell and camps on it, and after starting communication, cell 2 is set as an SCell. The plurality of cells of the base station A are configured with component carriers of different frequencies. The base station A aggregates two or more cells out of the plurality of cells, i.e., performs carrier aggregation (CA), and is capable of wireless communication with the UE by transmitting and receiving the component carriers of the aggregated cells in parallel.
[0164] In step ST1401, the UE selects a best cell, which is a cell with the best reception quality of the RS, for example, a cell with the highest reception power of the RS. In this operation example, in step ST1401, the UE selects cell 1 in base station A as the best cell. When the best cell is selected in step ST1401, the UE proceeds to step ST1402.
[0165] In step ST1402, the UE receives the MIB of the best cell selected in step ST1401. Specifically, the UE receives the PBCH of the best cell selected in step ST1401 to obtain the BCCH, which is broadcast information. The BCCH on the PBCH carries the MIB, which includes cell configuration information. Therefore, the MIB can be obtained by receiving the PBCH and obtaining the BCCH. Examples of MIB information include DL (downlink) system bandwidth (also called transmission bandwidth configuration: dl-bandwidth), the number of transmitting antennas, SFN (System Frame Number), and the like.
[0166] In Step ST1403, base station A notifies the UE of the SIB. SIB1 of the SIB includes information on access to the cell, such as a CSG identity (CSG-ID), a CSG indication, information on cell selection, and scheduling information of other SIBs (SIBk; an integer k≧2).
[0167] Specifically, when a cell operates in an open access mode or a hybrid access mode, the CSG indication is set to "FALSE" and is broadcast from the cell. Also, when a cell operates in a closed access mode, the CSG indication is set to "TRUE" and is broadcast from the cell. When the CSG indication is set to "TRUE", the mobile terminal can access the cell only if the CSG identity (CSG-ID) matches a CSG identity (CSG-ID) in a whitelist stored in the mobile terminal, for example, in the USIM (see Non-Patent Document 2).
[0168] In this operation example, cell 1 broadcasts "CSG-indication_cell 1" to the UE as the CSG indication, and broadcasts "CSG-ID_cell 1" to the UE as the CSG identity.
[0169] In step ST1404, the UE receives the SIB. Specifically, the UE receives the DL-SCH of the cell based on the cell configuration information of the MIB, and obtains the SIB1 in the broadcast information BCCH. The UE receives the other SIB based on the scheduling information of the other SIB in the SIB1. After receiving the SIB in this way in step ST1404, the UE proceeds to step ST1405.
[0170] In Step ST1405, the UE judges whether or not the CSG indication (CSG-indication) in the SIB received in Step ST1404 is "TRUE". In other words, the UE judges whether or not the access mode of the SCell is a closed access mode. If the UE judges in Step ST1405 that the CSG indication is "TRUE", it moves to Step ST1406. If the UE judges in Step ST1405 that the CSG indication is not "TRUE", that is, is "FALSE", it moves to Step ST1407.
[0171] In Step ST1406, the UE determines whether or not the UE is registered in the CSG indicated by the CSG identity in the SIB received in Step ST1404. The UE may determine whether or not the CSG identity in the SIB received in Step ST1404 matches a CSG identity in a whitelist stored in, for example, the USIM of the UE.
[0172] If the UE determines in Step ST1406 that the UE is registered, the UE proceeds to Step ST1407. Alternatively, if the UE determines in Step ST1406 that the CSG identity in the received SIB matches the CSG identity in the whitelist stored in, for example, the USIM of the UE, the UE may proceed to Step ST1407.
[0173] When the UE determines in Step ST1406 that the UE is unregistered, the UE returns to Step ST1401 to select another cell as the best cell. Alternatively, when the UE determines in Step ST1406 that the CSG identity in the received SIB does not match the CSG identity in the whitelist stored in, for example, the USIM of the UE, the UE may return to Step ST1401 to select another cell as the best cell.
[0174] In Step ST1407, the UE camps on the cell selected in Step ST1401. In this operation example, the UE camps on cell 1 in the base station A.
[0175] In Step ST1408, the UE establishes an RRC connection with the cell on which it camped in Step ST1407. In a base station capable of carrier aggregation, the cell to which the UE has established an RRC connection is called a PCell. The PCell corresponds to a connected cell. In this operation example, the UE establishes an RRC connection with cell 1 in base station A.
[0176] In Step ST1409, the UE notifies the MME of the first NAS message via the cell in which the UE has established an RRC connection. In this operation example, the UE notifies the MME of the first NAS message via cell 1 in base station A.
[0177] In step ST1410, the cell 1 notifies the MME of the NAS message received from the UE in step ST1409. As a specific example of a method for notifying the NAS message, the cell 1 maps the NAS message received from the UE to an "INITIAL UE MESSAGE" and notifies the MME of the NAS message. The notification includes the CSG identity and cell access mode of the base station (cell) in addition to the NAS message received from the UE in step ST1409 (see 3GPP TS 36.413 V9.5.0 (hereinafter referred to as "Non-Patent Document 11"). In this operation example, the cell 1 notifies the MME of CSG-ID_cell 1 as the CSG identity and Cell Access Mode_cell 1 as the cell access mode.
[0178] In step ST1411, the MME judges whether or not the cell access mode received in step ST1410 is the "closed access mode". If the MME judges in step ST1411 that the cell access mode is the "closed access mode", it proceeds to step ST1412. If the MME judges in step ST1411 that the cell access mode is not the "closed access mode", that is, the "open access mode" or the "hybrid access mode", it proceeds to step ST1413.
[0179] In Step ST1412, the MME judges whether or not the UE is registered to the CSG identity received in Step ST1410. If the MME judges in Step ST1412 that the UE is registered, it moves to Step ST1413. If the MME judges in Step ST1412 that the UE is not registered, that is, is unregistered, it moves to Step ST1414. In Step ST1412, when the MME judges whether or not the UE is registered, it may inquire of the HSS or may use information stored in the HSS.
[0180] In Step ST1413, the MME determines that it is possible to communicate with the UE via the cell that has notified the UE of the NAS message in Step ST1410. In this operation example, the MME determines that it is possible to communicate with the UE via cell 1 in base station A.
[0181] In Step ST1414, the MME determines that it is not possible to communicate with the UE via the cell that has notified the UE of the NAS message in Step ST1410.
[0182] In Step ST1415, the MME notifies the UE that has notified the NAS message via the cell in Step ST1409 of the determination result as to whether or not communication with the UE is possible via the cell. In this operation example, the MME notifies the UE of the determination result that communication with the UE is possible via the cell 1.
[0183] In step ST1416, the UE judges whether or not communication is possible via the cell based on the judgment result received in step ST1415. If the UE judges in step ST1416 that communication is possible, it proceeds to step ST1417. If the UE judges in step ST1416 that communication is not possible, it ends the process and proceeds to other processes. The other processes are not characteristic of the present disclosure, so their explanation will be omitted. In this operation example, the UE judges that communication is possible via the cell.
[0184] In Step ST1417, the cell starts communication with the UE. In this operation example, cell 1, as a PCell, starts communication with the UE.
[0185] In step ST1418, the cell decides to set another cell as an SCell. The SCell corresponds to an aggregation-enabled cell, and can be aggregated together with the PCell. In this operation example, cell 1, which has become the PCell, decides to set cell 2 as an SCell. In the present embodiment, no CSG access restriction is performed when determining the SCell. Specifically, when determining the SCell in step ST1418, the processes corresponding to steps ST1410 to ST1415 are not performed.
[0186] In step ST1419, the cell notifies the UE of the SCell to be added or updated and the configuration contents of the cell by using dedicated RRC signaling. In this operation example, the cell notifies the UE of cell 2 as the SCell to be added and the configuration contents of cell 2 by using the "RRC Connection Reconfiguration message" of the dedicated RRC signaling. At that time, the system information of cell 2 is also notified.
[0187] In the present embodiment, when an SCell is added or updated, the UE does not perform CSG access restriction on the SCell. Specifically, the UE does not perform the processes equivalent to steps ST1405 to ST1406 by using the configuration contents of cell 2 received in step ST1419 or the system information of cell 2 received in step ST1419.
[0188] In step ST1420, cell 2 broadcasts the SIB to UEs being served by it. Specifically, information regarding access to cell 2, for example, "CSG-ID_cell 2" is broadcast as a CSG identity, and "CSG-indication_cell 2" is broadcast as a CSG indication. In the present embodiment, when an SCell is added or updated, the UE does not perform CSG access restriction on the SCell. Specifically, the UE does not perform processes equivalent to steps ST1405 to ST1406 by using the system information of cell 2 broadcast from cell 2 in step ST1420. Alternatively, the UE may not receive the system information of cell 2 broadcast from cell 2 in step ST1420.
[0189] In Step ST1421, the UE notifies the cell, which is the PCell, that the configuration of the SCell to be added or the SCell to be updated, which was received in Step ST1419, has been completed. The notification is made by using, for example, "RRC Connection Reconfiguration Complete." In this operation example, the UE notifies cell 1, which is the PCell, that the configuration of the SCell has been completed.
[0190] In Step ST1422, the cell that is an SCell starts communication with the UE. In this operation example, cell 2, as an SCell, starts communication with the UE.
[0191] The above-described second embodiment can provide the following advantages: It is possible to improve communication speed using carrier aggregation, while stabilizing the operation of the communication system, and to provide appropriate services.
[0192] This embodiment can be used in combination with the above-described first embodiment.
[0193] Second embodiment, modified example 1 In this modification, further improvements to the above-mentioned embodiment 2 are described below. In this modification, the differences from the solution of the above-mentioned embodiment 2 are mainly described, and the parts not described are the same as embodiment 2.
[0194] In each cell (CC), it is possible to configure whether or not it can be used as a SCell. This configuration is sometimes referred to as a "SCell usage configuration." The PCell decides to configure the cell as an SCell according to the "SCell usage configuration" of each cell. The PCell decides to configure a cell that is indicated as usable in the "SCell usage configuration" as an SCell. The PCell does not configure a cell that is indicated as unusable in the "SCell usage configuration" as an SCell.
[0195] As specific examples of SCell usage settings, the following three (1) to (3) are disclosed. (1) Whether or not it is available. (2) That it is available. Compared to specific example (1), it is possible to obtain an effect of reducing the amount of information. (3) That it is not available. Compared to specific example (1), it is possible to obtain an effect of reducing the amount of information.
[0196] The following three methods (1) to (3) are disclosed as specific examples of a method in which a PCell knows the "SCell usage configuration" of another cell.
[0197] (1) Before deciding to configure the PCell as an SCell, a SCell candidate cell is selected. The PCell queries the SCell candidate cell about the "SCell usage configuration" of the SCell candidate cell. The base station or a control unit of the base station may also determine the "SCell usage configuration" of each cell.
[0198] (2) Each cell notifies the base station control unit of the "SCell usage setting" of its own cell. Before deciding to set the PCell as an SCell, an SCell candidate cell is selected. The PCell queries the base station control unit about the "SCell usage setting" of the SCell candidate cell. Before the query from the PCell, the base station control unit may notify each cell (PCell) of its "SCell usage setting". Also, the base station or the base station control unit may decide the "SCell usage setting" of each cell.
[0199] (3) Each cell notifies other cells of its own cell's "SCell usage configuration." Alternatively, the base station or a control unit of the base station may determine the "SCell usage configuration" of each cell.
[0200] Before deciding to configure the PCell as an SCell, the PCell may select an SCell candidate cell set including one or more cells. The SCell candidate cell set may be configured based on, for example, UE capabilities. As a specific example of a configuration method based on UE capabilities, an SCell candidate cell or an SCell candidate cell included in the SCell candidate cell set is selected from cells belonging to a frequency band in which the UE can transmit and receive. This provides an effect of preventing a delay in control when determining the SCell. The SCell candidate cell may be selected from the SCell candidate cell set.
[0201] The "SCell usage setting" may be changed. By making the "SCell usage setting" changeable, it is possible to obtain an effect of enabling flexible cell operation.
[0202] The "SCell usage setting" may be changed based on the conditions of the "SCell usage setting". As specific examples of the conditions of the "SCell usage setting", the following six (1) to (6) are disclosed. (1) Load status of the cell. For example, in the case of a high load or a large number of mobile terminals being served, the "SCell usage setting" can be set to "unusable" to ensure radio resources for the mobile terminals being served. (2) Access mode of the cell. Specific examples of the access mode include an open access mode, a closed access mode, and a hybrid access mode. (3) Transmission power of the cell. (4) Coverage of the cell. (5) Power-on status or low power consumption operation status of the cell. (6) A combination of the above (1) to (5).
[0203] As specific examples of the notification timing of the "SCell usage setting", the following five items (1) to (5) are disclosed.
[0204] (1) Periodically. This makes it possible to respond to changes in the "SCell usage settings."
[0205] (2) When a change is made. This makes it possible to handle changes to the "SCell usage setting" in the same way as in specific example (1). Also, compared to specific example (1), it is possible to obtain the effect of reducing the number of notifications.
[0206] (3) When the base station is installed. This makes it possible to obtain the effect of making control easier than in the specific example (1).
[0207] (4) When each cell starts operating. This provides an advantage that control is easier than in the specific example (1). Also, it provides an advantage that flexible operation is possible for each cell, compared to the specific example (3).
[0208] (5) When each cell is powered on. This provides the advantage of easier control compared to the specific example (1). Also, compared to the specific example (3), it provides the advantage of allowing flexible operation for each cell.
[0209] Next, a specific example of the sequence of the communication system in the first modification of the second embodiment will be described with reference to Fig. 15. Fig. 15 is a diagram showing an example of the sequence of the communication system in the first modification of the second embodiment. In the first modification of the second embodiment, the processes of steps ST1401 to ST1416 in Fig. 14 are the same as those in the second embodiment, so illustrations and explanations are omitted, and illustrations and explanations are given starting from the process of step ST1417 in Fig. 14. In addition, since the sequence shown in Fig. 15 is similar to the sequence shown in Fig. 14, the same steps are assigned the same step numbers, and common explanations are omitted.
[0210] In this operation example, a case will be described in which there is a base station A having multiple cells (CC) including cell 1 and cell 2, a UE selects cell 1 in base station A as the best cell, camps on it, starts communication, and then cell 2 is configured as the SCell. As a specific example of a method in which a PCell knows the "SCell use setting" of other cells, a case will be disclosed in which each cell notifies the control unit of the base station of its own cell's "SCell use setting". As a specific example of the notification timing of the "SCell use setting", a case will be disclosed at the time of base station installation.
[0211] In Step ST1501, a base station is installed. In this operation example, base station A having a plurality of cells (CC) including cell 1 and cell 2 is installed.
[0212] In Step ST1502 and Step ST1503, each cell in the base station notifies the control unit in the base station of the configuration of its own cell. The configuration of its own cell includes a "SCell usage configuration." In this operation example, in Step ST1502, cell 1 notifies the control unit of the "SCell usage configuration" of its own cell, cell 1. In Step ST1503, cell 2 notifies the control unit of the "SCell usage configuration" of its own cell, cell 2.
[0213] Next, the processes of steps ST1401 to ST1407 shown in the above-mentioned Fig. 14 are performed, and the UE selects cell 1 in base station A as the best cell and camps on it. Next, the processes of steps ST1408 to ST1416 shown in the above-mentioned Fig. 14 are performed, and then the UE proceeds to step ST1417.
[0214] In Step ST1417, the cell that is a PCell starts communication with the UE. In this operation example, cell 1, as a PCell, starts communication with the UE.
[0215] In Step ST1504, the cell that is the PCell selects another cell as a SCell candidate. In this operation example, cell 1 that has become the PCell selects cell 2 as a SCell candidate.
[0216] In Step ST1505, the cell that is a PCell inquires of the control unit about the configuration of the cell that is the SCell candidate selected in Step ST1504. The cell that is a PCell may inquire of the control unit about the "SCell usage configuration" of the SCell candidate. In this operation example, cell 1 that is a PCell inquires of the control unit about the "SCell usage configuration" of cell 2 that has been selected as a SCell candidate.
[0217] In Step ST1506, the control unit responds to the inquiry in Step ST1505 to the cell that is a PCell. The control unit may notify the cell that is a PCell of the "SCell usage setting" of the queried cell. In this operation example, the control unit notifies cell 1 that is a PCell of "available", which is the "SCell usage setting" of cell 2 that is the queried cell.
[0218] In Step ST1507, the cell that is a PCell judges whether or not the cell that is a SCell candidate selected in Step ST1504 can be used as a SCell. For this judgment, the response result to the inquiry received from the control unit in Step ST1506 is used.
[0219] If the cell that is a PCell determines in Step ST1507 that the cell that is a SCell candidate selected in Step ST1504 can be used as a SCell, it proceeds to Step ST1508. If the cell that is a PCell determines in Step ST1507 that the cell that is a SCell candidate selected in Step ST1504 cannot be used as a SCell, it returns to Step ST1504 to select another cell as a SCell candidate.
[0220] In this operation example, cell 1, which is a PCell, determines that cell 2, which is a SCell candidate, can be used as a SCell, and proceeds to step ST1508.
[0221] In step ST1508, the cell that is a PCell decides to configure a cell that is a SCell candidate as an SCell. In this operation example, cell 1 that is a PCell decides to configure cell 2 that is a SCell candidate as an SCell. In this modification, similar to the second embodiment, no CSG access restriction is performed when determining an SCell. Specifically, when determining an SCell in step ST1508, processes equivalent to steps ST1410 to ST1415 shown in FIG. 14 described above are not performed.
[0222] In addition to the effects of the second embodiment, the above-described first modification of the second embodiment provides the following effects. It becomes possible to configure, for each cell in a base station, whether or not a cell can be used as an SCell. This makes it possible to configure, for each cell, whether or not radio resources are to be occupied for a mobile terminal using the cell as a PCell. Therefore, it is possible to realize more detailed cell management.
[0223] This modification can be used in combination with the above-described first embodiment.
[0224] Embodiment 3 The problems to be solved in the third embodiment are described below. When the second embodiment described above is used, the following problems arise. A CSG is a cell for specific subscribers, which is a cell for which an operator specifies available subscribers. Therefore, in the second embodiment, in which a mobile terminal that is not registered in a CSG to which a cell belongs uses resources of the cell, a problem arises that goes against the purpose of the CSG.
[0225] In addition, in a CSG cell, a system is being considered that gives preferential treatment to CSG members who belong to the same CSG. Examples of preferential treatment include preferential allocation of resources to CSG members, or discounts on communication fees for CSG members. Accordingly, it is conceivable that billing settings may differ between CSG members and non-CSG members.
[0226] However, when the second embodiment is used, even if a user has a desire to belong to a CSG and to receive a desired service or to apply a desired billing setting, a CC not registered in a CSG will be used due to the settings from the PCell regardless of the user's desire. Therefore, a problem occurs in that a user-friendly communication system cannot be constructed.
[0227] The solution in the third embodiment is described below. In this embodiment, the differences from the solution in the second embodiment will be mainly described, and the parts that are not described are the same as those in the second embodiment.
[0228] The base station can configure a cell (CC) belonging to the same CSG as the PCell as an SCell. The base station may activate a cell (CC) belonging to the same CSG as the PCell as an SCell. Alternatively, when the PCell belongs to a CSG, the base station can configure a cell (CC) belonging to the same CSG as the PCell as an SCell. When the PCell belongs to a CSG, the base station may activate a cell (CC) belonging to the same CSG as the PCell as an SCell. Alternatively, when the PCell does not belong to a CSG, the base station can configure a cell (CC) not belonging to a CSG as an SCell. When the PCell does not belong to a CSG, the base station may activate a cell (CC) not belonging to a CSG as an SCell.
[0229] In the third embodiment, CSG access restriction is also performed in the mobile terminal and the MME for the PCell, as in the second embodiment. Therefore, by using the solution of the present embodiment, it is possible to prevent a mobile terminal that is not registered in the CSG to which a cell belongs from using the resources of the cell as an SCell.
[0230] A specific example of the operation of the MME is disclosed below. The MME omits the access control of the mobile terminal through the cell configured in the SCell in the base station, treating the access control of the mobile terminal through the PCell as the same as the access control of the mobile terminal through the PCell. The MME may be configured to only perform the access control of the mobile terminal through the PCell belonging to the CSG. The MME may be configured to only perform the access control of the mobile terminal through the PCell that is a CSG cell.
[0231] The following three methods (1) to (3) are disclosed as specific examples of a method in which a PCell knows whether or not another cell belongs to a CSG and the CSG-ID to which the other cell belongs.
[0232] (1) Before deciding to configure a PCell as an SCell, a SCell candidate cell is selected. The PCell queries the SCell candidate cell as to whether or not the SCell candidate cell belongs to a CSG and the CSG-ID to which the SCell candidate cell belongs.
[0233] Instead of inquiring about "whether the SCell belongs to a CSG" and "CSG-ID", it is also possible to inquire about "CSG indication" and "CSG-ID". In this case, if the response from the SCell does not include CSG-ID and the CSG indication is "FALSE", it may be determined that the SCell does not belong to a CSG. If the response from the SCell includes CSG-ID and the CSG indication is "TRUE", it may be determined that the SCell belongs to a CSG. If the response from the SCell includes CSG-ID and the CSG indication is "FALSE", it may be determined that the SCell belongs to a CSG.
[0234] Also, instead of inquiring about "whether or not the SCell belongs to a CSG" and "CSG-ID", "CSG-ID" may be inquired. In that case, if the response from the SCell does not include CSG-ID, it may be determined that the SCell does not belong to a CSG. Also, if the response from the SCell includes CSG-ID, it may be determined that the SCell belongs to a CSG.
[0235] (2) Each cell notifies the control unit of the base station whether or not the cell "belongs to a CSG", and if it does, notifies the "CSG-ID". Before deciding to set the PCell as an SCell, an SCell candidate cell is selected. The PCell queries the control unit whether or not the SCell candidate cell belongs to a CSG, and the CSG-ID to which the SCell candidate cell belongs. Instead of querying "whether or not the cell belongs to a CSG" and "CSG-ID", a "CSG indication" and "CSG-ID" may be queried. The information indicated by the combination of "CSG indication" and "CSG-ID" is the same as in the specific example (1) described above. Also, instead of querying "whether or not the cell belongs to a CSG" and "CSG-ID", a "CSG-ID" may be queried. The information indicated by "CSG-ID" is the same as in the specific example (1) described above.
[0236] (3) Each cell notifies other cells whether or not it "belongs to a CSG", and if it does, notifies "CSG-ID". Instead of notifying "belongs to a CSG" and "CSG-ID", it may notify "CSG indication" and "CSG-ID". The information indicated by the combination of "CSG indication" and "CSG-ID" is the same as in the above specific example (1). Also, instead of notifying "belongs to a CSG" and "CSG-ID", it may notify "CSG-ID". The information indicated by "CSG-ID" is the same as in the above specific example (1).
[0237] In the specific examples (1) to (3), "whether or not it belongs to the CSG" may be "that it belongs to the CSG" or "that it does not belong to the CSG".
[0238] A specific example of the notification timing of "whether or not the UE belongs to a CSG" and the "CSG-ID" is similar to the specific example of the notification timing of the "SCell use setting" in the first modification of the second embodiment described above, and therefore description thereof will be omitted.
[0239] Before deciding to configure the PCell as an SCell, the PCell may select a SCell candidate cell set. A specific example of the SCell candidate cell set is the same as that in the first modification of the second embodiment described above, and therefore a description thereof will be omitted.
[0240] Specific examples of the operation of the mobile terminal are disclosed below. The mobile terminal omits CSG access restriction for a cell for which configuration contents have been notified as an SCell, in the same manner as for access control of a PCell. The following three (1) to (3) are disclosed as specific examples of a method in which the mobile terminal omits CSG access restriction.
[0241] (1) Even if the CSG-indication and CSG-ID of the SCell are included in the configuration content as an SCell, the mobile terminal shall not restrict access using the CSG-indication and CSG-ID. For example, the CSG-ID of the SCell included in the configuration content as an SCell shall not be compared with the CSG-ID in the USIM of the mobile terminal. In addition, the CSG-indication and CSG-ID of the SCell may not be notified by the configuration as an SCell.
[0242] (2) It is assumed that no access restriction is performed using the CSG-indication and CSG-ID broadcasted from the cell configured as the SCell using broadcast information. For example, the CSG-ID broadcasted from the cell configured as the SCell using broadcast information is not compared with the CSG-ID in the USIM of the mobile terminal. Also, the CSG-ID broadcasted using broadcast information from the cell configured as the SCell may not be received or may be ignored. Also, the SIB1 broadcasted from the cell configured as the SCell may not be received or may be ignored. Also, the SIB broadcasted from the cell configured as the SCell may not be received or may be ignored. Also, the broadcast information broadcasted from the cell configured as the SCell may not be received or may be ignored.
[0243] (3) A combination of (1) and (2) above.
[0244] Next, a specific example of a sequence of the communication system in the third embodiment will be described with reference to Fig. 16. Fig. 16 is a diagram showing an example of a sequence of the communication system in the third embodiment. In the third embodiment, the processes of steps ST1401 to ST1416 in Fig. 14 are the same as those in the second embodiment, so illustrations and explanations are omitted, and illustrations and explanations are given starting from the process of step ST1417 in Fig. 14. In addition, the sequence shown in Fig. 16 is similar to the sequences shown in Figs. 14 and 15, so the same steps are given the same step numbers and common explanations are omitted.
[0245] In this operation example, a case will be described in which a base station A having multiple cells (CC) including cell 1 and cell 2 exists, a UE selects cell 1 in base station A as the best cell, camps on it, starts communication, and then cell 2 is set as an SCell. As a specific example of a method in which a PCell knows whether or not other cells belong to a CSG and the CSG-ID to which other cells belong, a case will be disclosed in which each cell notifies a control unit of a base station of "whether or not the cell belongs to a CSG" and, if it belongs to a CSG, notifies the "CSG-ID". As a specific example of the notification timing of "whether or not the cell belongs to a CSG" and "CSG-ID", a case will be disclosed at the time of base station installation.
[0246] In Step ST1501, a base station is installed. In this operation example, base station A having a plurality of cells (CC) including cell 1 and cell 2 is installed.
[0247] In steps ST1601 and ST1602, each cell in the base station notifies the control unit in the base station of the setting of its own cell. The setting of its own cell includes "whether or not it belongs to a CSG", and further includes "CSG-ID" if its own cell belongs to a CSG. In this operation example, in step ST1601, cell 1 notifies the control unit of "whether or not it belongs to a CSG" of its own cell, cell 1, and notifies the control unit of the "CSG-ID" of cell 1 if cell 1 belongs to a CSG. In step ST1602, cell 2 notifies the control unit of "whether or not it belongs to a CSG" of its own cell, cell 2, and notifies the control unit of the "CSG-ID" of cell 2 if cell 2 belongs to a CSG.
[0248] Next, the processes of steps ST1401 to ST1407 shown in the above-mentioned Fig. 14 are performed, and the UE selects cell 1 in base station A as the best cell and camps on it. Next, the processes of steps ST1408 to ST1416 shown in the above-mentioned Fig. 14 are performed, and then the UE proceeds to step ST1417.
[0249] In Step ST1417, the cell that is a PCell starts communication with the UE. In this operation example, cell 1, as a PCell, starts communication with the UE.
[0250] In Step ST1504, the cell that is the PCell selects another cell as a SCell candidate. In this operation example, cell 1 that has become the PCell selects cell 2 as a SCell candidate.
[0251] In step ST1603, the cell that is a PCell inquires of the control unit about the configuration of the cell that is the SCell candidate selected in step ST1504. The cell that is a PCell may inquire of the control unit about "whether or not the SCell candidate belongs to a CSG" and, if it belongs to a CSG, its "CSG-ID." In this operation example, cell 1 that is a PCell inquires of the control unit about "whether or not the cell 2 selected as the SCell candidate belongs to a CSG" and, if it belongs to a CSG, its "CSG-ID."
[0252] In step ST1604, the control unit responds to the inquiry in step ST1603 to the cell that is a PCell. The control unit may notify the cell that is a PCell of "whether or not the queried cell belongs to a CSG" and, if the queried cell belongs to a CSG, of its "CSG-ID." In this operation example, the control unit notifies cell 1 that is a PCell of "whether or not the queried cell belongs to a CSG" and, if the queried cell belongs to a CSG, of its "CSG-ID."
[0253] In Step ST1605, the cell that is a PCell judges whether or not the cell that is the SCell candidate selected in Step ST1504 belongs to a CSG. For this judgment, a response result to the inquiry received from the control unit in Step ST1604 is used. If the cell that is a PCell judges in Step ST1605 that the cell that is the SCell candidate selected in Step ST1504 belongs to a CSG, it moves to Step ST1606. If the cell that is a PCell judges in Step ST1504 that the cell that is the SCell candidate does not belong to a CSG, it moves to, for example, Step ST1508, although this is not a characteristic feature of the present embodiment.
[0254] In Step ST1606, the cell that is a PCell judges whether or not the CSG to which the cell that is the SCell candidate selected in Step ST1504 belongs is the same as the CSG to which the cell itself belongs. For this judgment, the response result to the inquiry received from the control unit in Step ST1604 is used.
[0255] If the cell that is a PCell determines in Step ST1606 that the CSG to which the SCell candidate cell selected in Step ST1504 belongs (CSG-ID_SCell candidate) is the same as the CSG to which its own cell belongs (CSG-ID_cell1), it proceeds to Step ST1508. If the cell that is a PCell determines in Step ST1504 that the CSG to which the SCell candidate cell selected in Step ST1504 belongs is different from the CSG to which its own cell belongs, it returns to Step ST1504 to select another cell as the SCell candidate.
[0256] The processes of Steps ST1605 and ST1606 realize the feature of this embodiment, that is, only a cell (CC) that belongs to the same CSG as the PCell can be configured as an SCell.
[0257] In Step ST1508, the cell that is a PCell decides to configure a cell that is a SCell candidate as an SCell. In this operation example, cell 1 that is a PCell decides to configure cell 2 that is a SCell candidate as an SCell. In this embodiment, when determining an SCell, CSG access restriction is omitted since it is the same as access control of a mobile terminal through a PCell. Specifically, when determining an SCell in Step ST1508, processing equivalent to steps ST1410 to ST1415 shown in the above-mentioned FIG. 14 is not performed.
[0258] Next, another specific example of the sequence of the communication system in the third embodiment will be described with reference to Fig. 17. Fig. 17 is a diagram showing another example of the sequence of the communication system in the third embodiment. In the third embodiment, the processes of steps ST1401 to ST1416 in Fig. 14 are the same as those in the second embodiment, so illustrations and explanations are omitted, and illustrations and explanations are given starting from the process of step ST1417 in Fig. 14. In addition, since the sequence shown in Fig. 17 is similar to the sequences shown in Figs. 14 to 16, the same steps are given the same step numbers, and common explanations are omitted.
[0259] In this operation example, a case will be described in which a base station A having multiple cells (CC) including cell 1 and cell 2 exists, a UE selects cell 1 in base station A as the best cell, camps on it, starts communication, and then cell 2 is set as an SCell. As a specific example of a method in which a PCell knows whether other cells belong to a CSG or not and the CSG-ID to which other cells belong, a case will be disclosed in which each cell notifies the control unit of the base station of its own cell's "CSG-ID". As a specific example of the timing of notifying the "CSG-ID", a case will be disclosed when the base station is installed.
[0260] In steps ST1701 and ST1702, each cell in the base station notifies the control unit in the base station of the setting of its own cell. If the cell belongs to a CSG, the setting of the own cell includes a "CSG-ID." In this operation example, in step ST1701, cell 1 notifies the control unit of the "CSG-ID" of cell 1 if it belongs to a CSG. In step ST1702, cell 2 notifies the control unit of the "CSG-ID" of cell 2 if it belongs to a CSG.
[0261] In Step ST1703, the cell that is a PCell inquires of the control unit about the configuration of the cell that is the SCell candidate selected in Step ST1504. The cell that is a PCell may inquire of the control unit about the "CSG-ID" when the cell belongs to the CSG of the SCell candidate. In this operation example, cell 1 that is a PCell inquires of the control unit about the "CSG-ID" when the cell belongs to the CSG of cell 2 selected as the SCell candidate.
[0262] In step ST1704, the control unit responds to the inquiry in step ST1703 to the cell that is a PCell. The control unit may notify the cell that is a PCell of the "CSG-ID" when the cell belongs to the CSG of the queried cell. In this operation example, the control unit notifies cell 1 that is a PCell of the "CSG-ID" when the cell belongs to the CSG of cell 2 that is the queried cell.
[0263] In Step ST1705, the cell that is a PCell judges whether or not the cell that is a SCell candidate selected in Step ST1504 has a CSG-ID. In other words, the cell that is a PCell judges whether or not the SCell belongs to a CSG. For this judgment, the response result to the inquiry received from the control unit in Step ST1704 is used.
[0264] If the cell that is a PCell determines in Step ST1705 that the SCell candidate cell selected in Step ST1504 has a CSG-ID, it moves to Step ST1606. In other words, if the cell that is a PCell determines in Step ST1705 that the SCell candidate cell selected in Step ST1504 has a CSG-ID, it determines that the SCell candidate cell belongs to the CSG, and moves to Step ST1606.
[0265] If the cell that is a PCell determines in Step ST1705 that the cell that is a SCell candidate selected in Step ST1504 does not have a CSG-ID, the cell proceeds to, for example, Step ST1508, although this is not a characteristic feature of the present embodiment. In other words, if the cell that is a PCell determines in Step ST1705 that the cell that is a SCell candidate selected in Step ST1504 does not have a CSG-ID, the cell proceeds to, for example, Step ST1508, although this is not a characteristic feature of the present embodiment.
[0266] The processes of Steps ST1705 and ST1606 realize the feature of this embodiment, that is, only a cell (CC) that belongs to the same CSG as the PCell can be configured as an SCell.
[0267] According to the above-described third embodiment, in addition to the effects of the second embodiment, the following effects can be obtained. For the SCell as well, it is possible for an operator to specify available subscribers. Also, by belonging to a CSG, it is possible to build a user-friendly communication system that respects the user's wishes, such as the services that the user wants to receive or the billing settings that the user wants to apply.
[0268] This embodiment can be used in combination with the above-described first embodiment, second embodiment, and first modification of second embodiment.
[0269] Embodiment 4 In the fourth embodiment, a different solution to the same problem as in the third embodiment is disclosed. The solution in the fourth embodiment is described below. In this embodiment, the differences from the solution in the second embodiment are mainly described, and the parts not described are the same as in the second embodiment.
[0270] The base station cannot configure a cell (CC) belonging to a CSG as a SCell. The base station may not activate a cell (CC) belonging to a CSG as a SCell. The base station can configure a cell (CC) not belonging to a CSG as a SCell. The base station may activate a cell (CC) not belonging to a CSG as a SCell.
[0271] By using the solution of this embodiment, it is possible to prevent a mobile terminal that is not registered in the CSG to which the cell belongs from using the resources of the cell as an SCell.
[0272] Furthermore, the following may be done. The base station may not configure a cell that operates in a closed access mode among the cells (CC) that belong to the CSG as a SCell. The base station may not activate a cell that operates in a closed access mode among the cells (CC) that belong to the CSG as a SCell.
[0273] The base station can configure a cell (CC) that does not belong to a CSG, or a cell (CC) that belongs to a CSG and operates in an open access mode, or a cell (CC) that belongs to a CSG and operates in a hybrid access mode, as an SCell. The base station may activate a cell (CC) that does not belong to a CSG, or a cell (CC) that belongs to a CSG and operates in an open access mode, or a cell (CC) that belongs to a CSG and operates in a hybrid access mode, as an SCell.
[0274] In this way, taking into account the access mode of the cell belonging to the CSG increases the number of cells that can be configured as an SCell, compared to the above method that does not consider the access mode. This makes it easier to improve communication speed using carrier aggregation, compared to the above method that does not consider the access mode, and makes it possible to prevent a mobile terminal that is not registered in the CSG to which the cell belongs from using the resource of the cell as an SCell.
[0275] The following is disclosed as a specific example of the operation of the MME. The MME does not execute access control of a mobile terminal through a cell configured as an SCell in the base station, since the access of the mobile terminal is not through a CSG cell. The MME may not execute access control of a mobile terminal through a CSG cell configured as an SCell in the base station, since the access of the mobile terminal is not through a CSG cell operating in a closed access mode. The MME may execute only access control of a mobile terminal through a PCell. The MME may execute only access control of a mobile terminal through a PCell belonging to the CSG. The MME may execute only access control of a mobile terminal through a PCell that is a CSG cell.
[0276] The following three methods (1) to (3) are disclosed as specific examples of a method for a PCell to know whether or not another cell belongs to a CSG and the access mode when another cell belongs to a CSG. Hereinafter, the access mode may also be referred to as an "operation mode."
[0277] (1) Before deciding to configure a PCell as an SCell, a SCell candidate cell is selected. The PCell inquires of the SCell candidate cell about whether the SCell candidate cell belongs to a CSG and the operation mode when the SCell candidate cell belongs to a CSG.
[0278] Instead of inquiring about "whether or not the SCell belongs to a CSG" and "operation mode", it is also possible to inquire about "CSG indication" and "CSG-ID". In that case, if the response from the SCell does not include a CSG-ID and the CSG indication is "FALSE", it may be determined that the SCell does not belong to a CSG, or that the SCell belongs to a CSG and operates in open access mode.
[0279] Also, if the response from the SCell includes a CSG-ID and the CSG indication is "TRUE", it may be determined that the SCell belongs to the CSG and is operating in the closed access mode. Also, if the response from the SCell includes a CSG-ID and the CSG indication is "FALSE", it may be determined that the SCell belongs to the CSG and is operating in the hybrid access mode.
[0280] (2) Each cell notifies the control unit of the base station whether or not its own cell "belongs to a CSG", and if its own cell belongs to a CSG, notifies the "CSG-ID". Before deciding to set the PCell as an SCell, an SCell candidate cell is selected. The PCell queries the control unit whether or not the SCell candidate cell belongs to a CSG, and the operation mode when the SCell candidate cell belongs to a CSG. Instead of querying "whether or not the SCell belongs to a CSG" and the "operation mode", the query may query "CSG indication" and "CSG-ID". The information indicated by the combination of "CSG indication" and "CSG-ID" is the same as in the above specific example (1).
[0281] (3) Each cell notifies other cells of "whether or not the cell belongs to a CSG" and the "operation mode" when the cell belongs to a CSG. Instead of notifying "whether or not the cell belongs to a CSG" and the "operation mode", the cell may notify "CSG indication" and "CSG-ID". The information indicated by the combination of "CSG indication" and "CSG-ID" is the same as in the above specific example (1).
[0282] In the specific examples (1) to (3), "whether or not it belongs to the CSG" may be "that it belongs to the CSG" or "that it does not belong to the CSG".
[0283] A specific example of the notification timing of "whether or not the UE belongs to a CSG" and the "operation mode" is similar to the specific example of the notification timing of the "SCell use setting" in the first modification of the second embodiment described above, and therefore a description thereof will be omitted.
[0284] Before deciding to configure the PCell as an SCell, the PCell may select a SCell candidate cell set. A specific example of the SCell candidate cell set is the same as that in the first modification of the second embodiment described above, and therefore a description thereof will be omitted.
[0285] A specific example of the operation of the mobile terminal is disclosed below. The mobile terminal omits the execution of CSG access control in the mobile terminal, i.e., CSG access restriction, for a cell whose configuration has been notified as an SCell, since the cell does not belong to the CSG. The mobile terminal may omit the execution of CSG access control in the mobile terminal, i.e., CSG access restriction, for a cell whose configuration has been notified as an SCell, since the cell does not belong to the CSG operating in a closed access mode. A specific example of the method in which the mobile terminal omits CSG access restriction is the same as that of the above-mentioned third embodiment, and therefore a description thereof will be omitted.
[0286] Next, a specific example of a sequence of the communication system in the fourth embodiment will be described with reference to Fig. 18. Fig. 18 is a diagram showing an example of a sequence of the communication system in the fourth embodiment. In the fourth embodiment, the processes of steps ST1401 to ST1416 in Fig. 14 are the same as those in the second embodiment, so illustrations and explanations are omitted, and illustrations and explanations are given starting from the process of step ST1417 in Fig. 14. In addition, the sequence shown in Fig. 18 is similar to the sequences shown in Figs. 14 and 15, so the same steps are given the same step numbers and common explanations are omitted.
[0287] In this operation example, a case will be described in which a base station A having multiple cells (CC) including cell 1 and cell 2 exists, a UE selects cell 1 in base station A as the best cell, camps on it, starts communication, and then cell 2 is set as an SCell. As a specific example of a method in which a PCell knows whether or not other cells belong to a CSG, and the operation mode when other cells belong to a CSG, a case will be disclosed in which each cell notifies a control unit of a base station of "whether or not the cell belongs to a CSG" and the "operation mode" when the cell belongs to a CSG. As a specific example of the notification timing of "whether or not the cell belongs to a CSG" and the "operation mode", a case will be disclosed at the time of base station installation.
[0288] In Step ST1501, a base station is installed. In this operation example, base station A having a plurality of cells (CC) including cell 1 and cell 2 is installed.
[0289] In steps ST1801 and ST1802, each cell in the base station notifies the control unit in the base station of the setting of its own cell. The setting of its own cell includes "whether or not it belongs to a CSG" and "operation mode" when it belongs to a CSG. In this operation example, in step ST1801, cell 1 notifies the control unit of "whether or not it belongs to a CSG" of cell 1 and "operation mode" when it belongs to a CSG. In step ST1802, cell 2 notifies the control unit of "whether or not it belongs to a CSG" of cell 2 and "operation mode" when it belongs to a CSG.
[0290] Next, the processes of steps ST1401 to ST1407 shown in the above-mentioned Fig. 14 are performed, and the UE selects cell 1 in base station A as the best cell and camps on it. Next, the processes of steps ST1408 to ST1416 shown in the above-mentioned Fig. 14 are performed, and then the UE proceeds to step ST1417.
[0291] In Step ST1417, the cell that is a PCell starts communication with the UE. In this operation example, cell 1, as a PCell, starts communication with the UE.
[0292] In Step ST1504, the cell that is the PCell selects another cell as a SCell candidate. In this operation example, cell 1 that has become the PCell selects cell 2 as a SCell candidate.
[0293] In Step ST1803, the cell that is a PCell inquires of the control unit about the configuration of the cell that is the SCell candidate selected in Step ST1504. The cell that is a PCell may inquire of the control unit about "whether or not the SCell candidate belongs to a CSG" and about the "operation mode" if it belongs to a CSG. In this operation example, cell 1 that is a PCell inquires of the control unit about "whether or not the cell 2 selected as the SCell candidate belongs to a CSG" and about the "operation mode" if it belongs to a CSG.
[0294] In step ST1804, the control unit responds to the inquiry in step ST1803 to the cell that is a PCell. The control unit may notify the cell that is a PCell of "whether or not the queried cell belongs to a CSG" and the "operation mode" when the queried cell belongs to a CSG. In this operation example, the control unit notifies cell 1 that is a PCell of "whether or not cell 2 that is a queried cell belongs to a CSG" and the "operation mode" when the queried cell belongs to a CSG.
[0295] In Step ST1805, the cell that is a PCell judges whether or not the cell that is the SCell candidate selected in Step ST1504 belongs to the CSG. For this judgment, the response result to the inquiry received from the control unit in Step ST1804 is used.
[0296] If the cell that is a PCell determines in Step ST1805 that the cell that is a SCell candidate selected in Step ST1504 belongs to the CSG, it moves to Step ST1806. If the cell that is a PCell determines in Step ST1805 that the cell that is a SCell candidate selected in Step ST1504 does not belong to the CSG, it moves to Step ST1508.
[0297] In Step ST1806, the cell that is a PCell judges whether or not the operation mode of the cell that is a SCell candidate selected in Step ST1504 is the closed access mode. For this judgment, the response result to the inquiry received from the control unit in Step ST1804 is used.
[0298] If the cell that is a PCell determines in Step ST1806 that the operation mode of the cell that is a SCell candidate selected in Step ST1504 is not the closed access mode, it proceeds to Step ST1508. In other words, if the cell that is a PCell determines in Step ST1806 that the operation mode of the cell that is a SCell candidate selected in Step ST1504 is the open access mode or the hybrid access mode, it proceeds to Step ST1508.
[0299] Also, if the cell that is a PCell determines in Step ST1806 that the operation mode of the cell that is the SCell candidate selected in Step ST1504 is the closed access mode, the cell that is a PCell returns to Step ST1504 to select another cell as the SCell candidate.
[0300] The process of Step ST1805 and Step ST1806 realizes the feature of this embodiment, that is, that a cell (CC) not belonging to a CSG can be configured as a SCell. Alternatively, it realizes that a cell (CC) not belonging to a CSG, or a cell (CC) belonging to a CSG that operates in an open access mode, or a cell (CC) belonging to a CSG that operates in a hybrid access mode can be configured as a SCell.
[0301] In step ST1508, the cell that is a PCell decides to configure a cell that is a SCell candidate as an SCell. In this operation example, cell 1 that is a PCell decides to configure cell 2 that is a SCell candidate as an SCell. In this embodiment, when determining an SCell, CSG access restriction is omitted since it is assumed that the mobile terminal does not access through a CSG cell, or even if the mobile terminal accesses through a CSG cell, it is assumed that the terminal accesses through a CSG cell but not through a CSG cell operating in a closed access mode. Specifically, when determining an SCell in step ST1508, processing equivalent to steps ST1410 to ST1415 is not performed.
[0302] Next, another specific example of the sequence of the communication system in the fourth embodiment will be described with reference to Fig. 19. Fig. 19 is a diagram showing another example of the sequence of the communication system in the fourth embodiment. In the fourth embodiment, the processes of steps ST1401 to ST1416 in Fig. 14 are the same as those in the second embodiment, so illustrations and explanations are omitted, and illustrations and explanations are given starting from the process of step ST1417 in Fig. 14. In addition, the sequence shown in Fig. 19 is similar to the sequences shown in Figs. 14, 15, and 18, so the same steps are given the same step numbers and common explanations are omitted.
[0303] In this operation example, a case will be described in which a base station A having multiple cells (CC) including cell 1 and cell 2 exists, a UE selects cell 1 in base station A as the best cell and camps on it, starts communication, and then cell 2 is set as an SCell. As a specific example of a method in which a PCell knows whether or not other cells belong to a CSG, and the operation mode in that case, a case in which each cell notifies a control unit of the base station of its own cell's "CSG indication" and "CSG-ID" will be disclosed. As a specific example of the notification timing of the "CSG indication" and "CSG-ID", a case at the time of base station installation will be disclosed.
[0304] In steps ST1901 and ST1902, each cell in the base station notifies the control unit in the base station of the setting of its own cell. The setting of its own cell includes a "CSG indication" and a "CSG-ID." In this operation example, in step ST1901, cell 1 notifies the control unit of its "CSG indication" and "CSG-ID." In step ST1902, cell 2 notifies the control unit of its "CSG indication" and "CSG-ID."
[0305] In Step ST1903, the cell that is a PCell inquires of the control unit about the configuration of the cell that is the SCell candidate selected in Step ST1504. The cell that is a PCell may inquire of the control unit about the "CSG indication" and "CSG-ID" of the SCell candidate. In this operation example, cell 1 that is a PCell inquires of the control unit about the "CSG indication" and "CSG-ID" of cell 2 that has been selected as the SCell candidate.
[0306] In Step ST1904, the control unit responds to the inquiry in Step ST1903 to the cell that is a PCell. The control unit may notify the cell that is a PCell of the "CSG indication" and "CSG-ID" of the queried cell. In this operation example, the control unit notifies cell 1 that is a PCell of the "CSG indication" and "CSG-ID" of cell 2 that is the queried cell.
[0307] In Step ST1905, the cell that is a PCell judges whether or not the cell that is a SCell candidate selected in Step ST1504 has a CSG-ID. In other words, the cell that is a PCell judges whether or not the SCell belongs to a CSG. For this judgment, the response result to the inquiry received from the control unit in Step ST1904 is used.
[0308] If the cell that is a PCell determines in Step ST1905 that the SCell candidate cell selected in Step ST1504 has a CSG-ID, it moves to Step ST1906. In other words, if the cell that is a PCell determines in Step ST1905 that the SCell candidate cell selected in Step ST1504 has a CSG-ID, it determines that the SCell candidate cell belongs to the CSG, and moves to Step ST1906.
[0309] If the cell that is a PCell determines in Step ST1905 that the SCell candidate cell selected in Step ST1504 does not have a CSG-ID, it moves to Step ST1508. In other words, if the cell that is a PCell determines in Step ST1905 that the SCell candidate cell selected in Step ST1504 does not have a CSG-ID, it determines that the SCell candidate cell does not belong to a CSG, and moves to Step ST1508.
[0310] In Step ST1906, the cell that is a PCell judges whether or not the CSG indication of the cell that is a SCell candidate selected in Step ST1504 is "TRUE". In other words, the cell judges whether or not the access mode of the SCell is a closed access mode. For this judgment, the response result to the inquiry received from the control unit in Step ST1904 is used.
[0311] If the cell that is a PCell determines in Step ST1906 that the CSG indication of the cell that is a SCell candidate selected in Step ST1504 is not "TRUE", that is, is "FALSE", it proceeds to Step ST1508. In other words, if the cell that is a PCell determines in Step ST1906 that the operation mode of the cell that is a SCell candidate selected in Step ST1504 is the open access mode or the hybrid access mode, it proceeds to Step ST1508.
[0312] Furthermore, if the cell that is a PCell determines in Step ST1906 that the CSG indication of the SCell candidate selected in Step ST1504 is "TRUE", the cell returns to Step ST1504 to select another cell as the SCell candidate. In other words, if the cell that is a PCell determines in Step ST1906 that the operation mode of the cell that is the SCell candidate selected in Step ST1504 is the closed access mode, the cell returns to Step ST1504 to select another cell as the SCell candidate.
[0313] The process of Step ST1905 and Step ST1906 realizes the feature of this embodiment that a cell (CC) not belonging to a CSG can be configured as a SCell. Alternatively, a cell (CC) not belonging to a CSG, or a cell (CC) belonging to a CSG that operates in an open access mode, or a cell (CC) belonging to a CSG that operates in a hybrid access mode can be configured as a SCell.
[0314] According to the above-described fourth embodiment, in addition to the effects of the second embodiment, the following effects can be obtained. For the SCell as well, it is possible for an operator to specify available subscribers. Also, by belonging to a CSG, it is possible to build a user-friendly communication system that respects the user's wishes, such as the services that the user wants to receive or the billing settings that the user wants to apply.
[0315] This embodiment can be used in combination with the above-described first embodiment, second embodiment, first modification of second embodiment, and third embodiment.
[0316] Embodiment 5. In the fifth embodiment, a different solution is disclosed for the same problem as in the third embodiment, that is, the problem that occurs when the second embodiment is used. The solution in the fifth embodiment is shown below. In this embodiment, the problem in the second embodiment is solved by using a method different from that of the second embodiment.
[0317] Before deciding to configure the PCell as an SCell, a SCell candidate cell is selected. The cell that is the PCell notifies the mobile terminal of the configuration contents of the SCell candidate cell. The mobile terminal that receives the configuration contents of the SCell candidate cell performs CSG access restriction on the cell that has been notified of the configuration contents as an SCell candidate cell. The mobile terminal notifies the PCell of the determination result of the CSG access restriction. The PCell that receives the determination result determines the SCell based on the determination result.
[0318] The PCell may select an SCell candidate cell set before deciding to configure the PCell as an SCell. The configuration content of the SCell candidate cell notified to the mobile terminal by the PCell may be the configuration content of the SCell candidate cell set. In addition, the CSG access restriction performed by the mobile terminal may be for the SCell candidate cell set. A specific example of the SCell candidate cell set is the same as that of the first modification of the second embodiment described above, and therefore a description thereof will be omitted.
[0319] By using the solution of the present embodiment, a CSG access restriction for an SCell is executed in a mobile terminal. This makes it possible to prevent a cell belonging to a CSG in which a mobile terminal is not registered from being set as an SCell for the mobile terminal while improving communication speed by using carrier aggregation. Therefore, it becomes possible to prevent a mobile terminal that is not registered in a CSG to which a cell belongs from using resources of the cell as an SCell.
[0320] Specific examples of the operation of the mobile terminal are disclosed below. The mobile terminal performs CSG access restriction on a cell whose configuration has been notified as a SCell candidate cell. The mobile terminal may perform CSG access restriction when the SCell candidate cell is a CSG cell. The following three (1) to (3) are disclosed as specific examples of a method in which the mobile terminal performs CSG access restriction.
[0321] (1) Access restriction is performed using the CSG-indication and CSG-ID of the SCell candidate cell in the configuration content as the SCell candidate cell. For example, the CSG-ID of the SCell candidate cell included in the configuration content as the SCell candidate cell is compared with the CSG-ID in the USIM of the mobile terminal. If the comparison result shows that the CSG-ID of the SCell candidate cell included in the configuration content as the SCell candidate cell is included in a whitelist in, for example, the USIM of the mobile terminal, it is determined that the cell is accessible. Also, if the comparison result shows that the CSG-ID of the SCell candidate cell included in the configuration content as the SCell candidate cell is not included in the whitelist in the USIM of the mobile terminal, it is determined that the cell is not accessible.
[0322] (2) An access restriction is performed using a CSG-indication and a CSG-ID broadcast from a cell set as an SCell candidate cell using broadcast information. For example, the CSG-ID broadcast from a cell set as an SCell candidate cell using broadcast information is compared with the CSG-ID in the USIM of the mobile terminal. If the comparison result shows that the CSG-ID broadcast from the cell set as an SCell candidate cell using broadcast information is included in a whitelist in, for example, the USIM of the mobile terminal, it is determined that the access is possible. If the comparison result shows that the CSG-ID broadcast from the cell set as an SCell candidate cell using broadcast information is not included in a whitelist in, for example, the USIM of the mobile terminal, it is determined that the access is not possible.
[0323] (3) A combination of (1) and (2) above.
[0324] The following three conditions (1) to (3) are disclosed as specific examples of conditions when the mobile terminal notifies the PCell of the CSG access restriction determination result.
[0325] (1) The mobile terminal notifies when CSG access restriction is performed. In this specific example, the judgment result is always notified. This makes it easier to detect communication errors that occur in the wireless section. Therefore, compared to specific examples (2) and (3), it is possible to obtain the effect of being able to build a system that is more resistant to communication errors.
[0326] (2) The mobile terminal notifies the mobile terminal when the CSG access restriction determination result is "access not possible". If the PCell does not receive the CSG access restriction determination result from the mobile terminal for a certain period of time, the PCell may determine that the CSG access restriction determination result is "accessible". In this specific example, compared to specific example (1), it is possible to obtain an effect of enabling radio resources to be utilized more effectively.
[0327] (3) The mobile terminal notifies the mobile terminal when the CSG access restriction determination result is "accessible". If the PCell does not receive the CSG access restriction determination result from the mobile terminal for a certain period of time, the PCell may determine that the CSG access restriction determination result is "inaccessible". In this specific example, compared to specific example (1), it is possible to obtain an effect of enabling radio resources to be utilized more effectively.
[0328] A specific example of a method in which the mobile terminal notifies the PCell of the determination result of the CSG access restriction will be described below. The mobile terminal notifies the PCell of the determination result of the CSG access restriction by using RRC signaling or an RRC message.
[0329] The following two methods (1) and (2) are disclosed as specific examples of a method in which a mobile terminal notifies a PCell of a result of a CSG access restriction determination by using an RRC message.
[0330] (1) New RRC signaling or RRC message is provided. The parameter to be mapped to the newly provided RRC signaling is the result of the CSG access restriction determination. The result of the CSG access restriction determination may be notified together with a mobile terminal identifier. The identifier of the mobile terminal may be a UE-ID or an IMSI.
[0331] (2) Existing RRC signaling or RRC messages are used. The parameter that needs to be added to the existing RRC signaling is the result of the CSG access restriction determination. The specific example (2) is more effective than the specific example (1) in that it does not require new signaling, and it is possible to avoid the communication system becoming complicated.
[0332] Next, a specific example of a method in which a mobile terminal notifies a result of a CSG access restriction determination using existing RRC signaling is disclosed below. The method disclosed in Non-Patent Document 2 is used. Specifically, a response method to an "RRC Connection Reconfiguration message" of RRC signaling, which is being considered for use when adding or updating an SCell, is used.
[0333] The existing method of responding to the "RRC Connection Reconfiguration message" will be described. In the mobile terminal, if the reconfiguration instructed by the "RRC Connection Reconfiguration message" is successfully completed, the mobile terminal notifies the base station of "RRC Connection Reconfiguration complete". In the mobile terminal, if the reconfiguration instructed by the "RRC Connection Reconfiguration message" is not successfully completed, the mobile terminal notifies the base station of "RRC Connection reestablishment REQUEST" to request RRC connection re-establishment to the base station.
[0334] A specific example of a case where an existing response method is used is disclosed below. If the CSG access restriction determination result is "accessible", the mobile terminal notifies the PCell of "RRC Connection Reconfiguration complete" assuming that the reconfiguration instructed by the "RRC Connection Reconfiguration message" has been successfully completed. If "RRC Connection Reconfiguration complete" is notified, and the CSG access restriction determination result indicates "accessible", it becomes unnecessary to provide new RRC signaling and additional parameters are also unnecessary, making it possible to build a communication system with excellent backward compatibility.
[0335] Alternatively, a parameter of the CSG access restriction determination result may be added to the "RRC Connection Reconfiguration message." This makes it possible to clearly notify the CSG access restriction determination result. Therefore, it is possible to clearly distinguish this from "RRC Connection Reconfiguration complete," which is a case in which the CSG access restriction determination result is not notified, and it is possible to obtain an effect of building a stable communication system.
[0336] On the other hand, when the CSG access restriction determination result is "access not possible", the existing response method to the "RRC Connection Reconfiguration message" has the following problem: In the existing response method, if the reconfiguration instructed by the "RRC Connection Reconfiguration message" has not been completed successfully, an "RRC Connection reestablishment REQUEST" is notified as described above.
[0337] However, even if the determination result of the CSG access restriction is "inaccessible", there is no problem with the RRC connection with the PCell, and there is no need to re-establish the RRC connection. Therefore, when the determination result of the CSG access restriction is "inaccessible", the reconfiguration instructed by the "RRC Connection Reconfiguration message" is not completed successfully in the mobile terminal, but the mobile terminal does not notify the PCell of "RRC Connection reestablishment REQUEST". This makes it possible to prevent unnecessary RRC connection re-establishment, and has the effect of preventing delays in control of the communication system.
[0338] As specific examples of notification methods when the CSG access restriction determination result is “access not permitted,” the following two (a1) and (a2) are disclosed.
[0339] (a1) New RRC signaling or an RRC message is provided. The parameters to be mapped to the newly provided RRC signaling are “inaccessible”.
[0340] (a2) Uses existing RRC signaling or an RRC message. The parameter that needs to be added to the existing RRC signaling is "inaccessible." The specific example (a2) is more effective than the specific example (a1) in that it does not require new signaling, and it is possible to avoid complicating the communication system. An example of the existing RRC signaling is "RRC Connection Reconfiguration complete."
[0341] A specific example of the operation of the base station is disclosed below. Before deciding to configure the PCell as an SCell, the base station selects a SCell candidate cell. The PCell notifies the mobile terminal of the configuration contents of the SCell candidate cell. The PCell receives, from the mobile terminal, the result of the determination of the CSG access restriction made by the mobile terminal. The PCell that has received the result of the determination makes a SCell decision based on the result of the determination.
[0342] A specific example of the SCell determination performed by the base station based on the result of the CSG access restriction determination performed by the mobile terminal will be disclosed below. A case where "access possible" is received from the mobile terminal as the result of the CSG access restriction determination performed by the mobile terminal will be disclosed. The PCell decides to set the SCell candidate cell as the SCell. Alternatively, the PCell may determine that the SCell candidate cell can be activated.
[0343] Disclosed is a case where "access not possible" is received from a mobile terminal as a result of the CSG access restriction determination made by the mobile terminal. The PCell decides not to set the SCell candidate cell as an SCell. Alternatively, the PCell decides to remove the SCell candidate cell from the SCell candidate cells. Alternatively, the PCell may determine that the SCell candidate cell cannot be activated.
[0344] Specific examples of the operation of the MME are disclosed below. The MME does not execute access control of a mobile terminal through a cell configured as an SCell in the base station. The MME may omit execution of CSG access control in the MME, assuming that access control of a cell configured as an SCell in the base station is completed on the mobile terminal side. The MME may execute only access control of a mobile terminal through a PCell. The MME may execute only access control of a mobile terminal through a PCell belonging to the CSG. The MME may execute only access control of a mobile terminal through a PCell that is a CSG cell.
[0345] Next, a specific example of the sequence of the communication system in the fifth embodiment will be described with reference to Fig. 20. Fig. 20 is a diagram showing an example of the sequence of the communication system in the fifth embodiment. In the fifth embodiment, the processes of steps ST1401 to ST1416 in Fig. 14 described above are the same as those in the second embodiment, so illustrations and explanations are omitted, and illustrations and explanations are given starting from the process of step ST1417 in Fig. 14. In addition, the sequence shown in Fig. 20 is similar to the sequences shown in Figs. 14 and 15, so the same steps are given the same step numbers and common explanations are omitted.
[0346] In this operation example, a case will be described in which there is a base station A having multiple cells (CC) including cell 1 and cell 2, a mobile terminal (UE) selects cell 1 in base station A as the best cell, camps on it, starts communication, and then cell 2 is set as the SCell.
[0347] As a specific example of a method in which a mobile terminal performs CSG access restriction, a case in which access restriction is performed using a CSG-indication and a CSG-ID of an SCell candidate cell in the configuration contents as an SCell candidate cell is disclosed. As a specific example of a condition in which a mobile terminal notifies a PCell of a CSG access restriction determination result, a case in which CSG access restriction is performed is disclosed. As a specific example of a method in which a mobile terminal notifies a PCell of a CSG access restriction determination result, a case in which "RRC Connection Reconfiguration complete", which is an existing RRC signaling, is used for both "accessible" and "inaccessible", is disclosed.
[0348] After the processes of steps ST1401 to ST1416 shown in FIG. 14 described above are performed, in step ST1417, the cell that is the PCell, cell 1 in this operation example, starts communication with the mobile terminal (UE). Next, in step ST1504, the cell that is the PCell selects another cell as a SCell candidate. In this operation example, cell 1 that has become the PCell selects cell 2 as a SCell candidate.
[0349] In step ST2001, the cell that is the PCell notifies the mobile terminal (UE) of the configuration contents of the SCell candidate cell by using dedicated RRC signaling. In this operation example, the cell 2 is notified as the SCell candidate cell and the configuration contents of cell 2 by using an "RRC Connection Reconfiguration message" of the dedicated RRC signaling. At that time, the system information of cell 2 is also notified. Specifically, information regarding access to cell 2, for example, CSG-ID_cell 2, etc. is notified as the CSG identity, and CSG-indication_cell 2, etc. is notified as the CSG indication.
[0350] In step ST2002, cell 2 broadcasts the SIB to mobile terminals being served by cell 2. Specifically, information regarding access to cell 2, for example, CSG-ID_cell 2, etc. is broadcast as a CSG identity, and CSG-indication_cell 2, etc. is broadcast as a CSG indication. In this operation example, a case is disclosed in which access restriction is performed using the CSG-indication and CSG-ID of an SCell candidate cell in the configuration content as an SCell candidate cell. Therefore, the mobile terminal may or may not receive broadcast information from cell 2.
[0351] In Step ST2003, the mobile terminal (UE) judges whether or not the CSG indication in the configuration content of the SCell candidate cell received in Step ST2001 is "TRUE". In this operation example, the mobile terminal judges whether or not the CSG-indication_cell2 is "TRUE". If the mobile terminal judges in Step ST2003 that the CSG indication is "TRUE", it moves to Step ST2004. If the mobile terminal judges in Step ST2003 that the CSG indication is not "TRUE", that is, that it is "FALSE", it moves to Step ST2005.
[0352] In Step ST2004, a mobile terminal (UE) judges whether or not the mobile terminal is registered in the CSG indicated by the CSG identity in the configuration content of the SCell candidate cell received in Step ST2001. If the mobile terminal judges in Step ST2004 that the mobile terminal is registered, the mobile terminal moves to Step ST2005. If the mobile terminal judges in Step ST2004 that the mobile terminal is unregistered, the mobile terminal moves to Step ST2006.
[0353] The process of Steps ST2003 and ST2004 realizes the feature of this embodiment, that is, a mobile terminal performs CSG access restriction on a cell whose configuration content has been notified as a SCell candidate cell.
[0354] In Step ST2005, the mobile terminal (UE) sets “access possible” or “access OK” as the determination result of the CSG access restriction. In this operation example, the mobile terminal sets “access OK” as the determination result of the CSG access restriction during “RRC Connection Reconfiguration complete”.
[0355] In Step ST2006, the user equipment (UE) sets "access not possible" or "access NG" as the result of the CSG access restriction determination.
[0356] In Step ST2007, the mobile terminal notifies the cell that is the PCell of "RRC Connection Reconfiguration Complete" in response to the "RRC Connection Reconfiguration" received in Step ST2007. The mobile terminal may notify the cell that is the PCell of "RRC Connection Reconfiguration Complete." The "RRC Connection Reconfiguration Complete" includes the access judgment result set in Step ST2005 or Step ST2006.
[0357] In Step ST2008, the cell that is a PCell judges whether the judgment result of the CSG access restriction in the mobile terminal for the cell that is a SCell candidate selected in Step ST1504 is whether the cell is accessible or not, or whether the judgment result of the CSG access restriction in the mobile terminal for the cell that is a SCell candidate is whether the cell is not accessible or not. For this judgment, the access judgment result received from the mobile terminal in Step ST2007 is used.
[0358] When the cell that is a PCell determines in step ST2008 that the judgment result of the CSG access restriction in the mobile terminal of the cell that is a SCell candidate selected in step ST1504 is accessible, the cell that is a PCell moves to step ST1508. When the cell that is a PCell determines in step ST1504 that the judgment result of the CSG access restriction in the mobile terminal of the cell that is a SCell candidate selected in step ST1504 is inaccessible, the cell that is a PCell returns to step ST1504 to select another cell as a SCell candidate. In this operation example, cell 1 that is a PCell determines that cell 2 that is a SCell candidate is accessible as a SCell, and moves to step ST1508.
[0359] The process of step ST2008 realizes the feature of this embodiment, that is, the cell that is the PCell determines the SCell based on the determination result of the CSG access restriction of the mobile terminal.
[0360] The above-described fifth embodiment can provide the following effects. As in the above-described third embodiment, it is possible for an operator to specify available subscribers for the SCell. It is also possible to configure a cell corresponding to one or more CSG-IDs in a whitelist held in a UE as an SCell. Also, by belonging to a CSG, it is possible to build a user-friendly communication system that respects the user's wishes, such as the services to be received or the billing settings to be applied. At the same time, as in the above-described second embodiment, it is possible to stabilize the operation of the communication system while improving the communication speed using carrier aggregation, and to provide appropriate services.
[0361] This embodiment can be used in combination with the above-described first embodiment.
[0362] Fifth embodiment, variant 1 In this modification, further improvements to the above-mentioned embodiment 5 are described below. In this modification, the differences from the solution of the above-mentioned embodiment 5 are mainly described, and the parts not described are the same as embodiment 5.
[0363] Before deciding to configure the PCell as an SCell, an SCell candidate cell is selected. In each cell (CC), it is possible to configure whether a CSG-unregistered mobile terminal (UE) can use the cell as an SCell. This configuration is also referred to as "SCell use configuration for CSG-unregistered UE". The PCell notifies the mobile terminal of the configuration contents of the SCell candidate cell and the "SCell use configuration for CSG-unregistered UE" of the cell. The mobile terminal that receives the configuration contents of the SCell candidate cell of the cell and the "SCell use configuration for CSG-unregistered UE" performs CSG access restriction on the SCell candidate cell, taking into consideration the "SCell use configuration for CSG-unregistered UE".
[0364] Alternatively, a SCell candidate cell is selected before deciding to configure the PCell as an SCell. In each cell (CC), it is possible to configure whether a CSG-unregistered mobile terminal (UE) can use the cell as an SCell. This configuration is sometimes referred to as "SCell use configuration for CSG-unregistered UE." When the "SCell use configuration for CSG-unregistered UE" of the SCell candidate cell is "unusable," the PCell notifies the mobile terminal of the configuration content of the SCell candidate cell.
[0365] The mobile terminal that has received the configuration content of the SCell candidate cell performs CSG access restriction on the cell that has been notified of the configuration content as the SCell candidate cell. The mobile terminal notifies the PCell of the determination result of the CSG access restriction. The PCell that has received the determination result may determine an SCell based on the determination result. In other words, when the "SCell usage configuration for CSG unregistered UE" of the SCell candidate cell is "usable", the PCell may not determine an SCell based on the mobile terminal's determination result of the CSG access restriction.
[0366] As specific examples of the SCell usage configuration for a UE not registered in a CSG, the following three (1) to (3) are disclosed. (1) Whether or not a UE not registered in a CSG can be used as a SCell. (2) That a UE not registered in a CSG can be used as a SCell. Compared to specific example (1), this has the effect of reducing the amount of information. (3) That a UE not registered in a CSG cannot be used as a SCell. Compared to specific example (1), this has the effect of reducing the amount of information.
[0367] A specific example of the method in which the PCell knows the "SCell usage configuration of a UE not registered in a CSG" of another cell is similar to the specific example of the method in which the PCell knows the "SCell usage configuration" of another cell in the above-mentioned first variant of the second embodiment, so the explanation is omitted.
[0368] A specific example of the notification timing of the "SCell usage configuration of a CSG unregistered UE" is similar to the specific example of the notification timing of the "SCell usage configuration" in the first modification of the second embodiment described above, and therefore a description thereof will be omitted.
[0369] The PCell may select an SCell candidate cell set before deciding to configure the PCell as an SCell. The configuration content of the SCell candidate cell notified to the mobile terminal by the PCell may be the configuration content of the SCell candidate cell set. In addition, the CSG access restriction performed by the mobile terminal may be for the SCell candidate cell set. A specific example of the SCell candidate cell set is the same as that of the first modification of the second embodiment described above, and therefore a description thereof will be omitted.
[0370] A specific example of a method in which the mobile terminal performs CSG access restriction on the SCell candidate cell, taking into consideration the "SCell usage configuration of CSG unregistered UE", is disclosed below. If the "SCell usage configuration of CSG unregistered UE" indicates that it is usable, the mobile terminal determines that the SCell candidate cell is usable as a SCell even if it is CSG unregistered, and does not perform CSG access restriction. If the "SCell usage configuration of CSG unregistered UE" indicates that it is not usable, the mobile terminal performs CSG access restriction.
[0371] Next, a specific example of the sequence of the communication system in the first modification of the fifth embodiment will be described with reference to Fig. 21. Fig. 21 is a diagram showing an example of the sequence of the communication system in the first modification of the fifth embodiment. In the first modification of the fifth embodiment, the processes of steps ST1401 to ST1416 in Fig. 14 described above are the same as those in the second embodiment, so illustrations and explanations are omitted, and illustrations and explanations are given starting from the process of step ST1417 in Fig. 14. In addition, the sequence shown in Fig. 21 is similar to the sequences shown in Figs. 14, 15, and 20, so the same steps are given the same step numbers and common explanations are omitted.
[0372] In this operation example, a case will be described in which there is a base station A having multiple cells (CC) including cell 1 and cell 2, a mobile terminal (UE) selects cell 1 in base station A as the best cell, camps on it, starts communication, and then cell 2 is set as the SCell.
[0373] As a specific example of a method in which a mobile terminal performs CSG access restriction, a case in which access restriction is performed using a CSG-indication and a CSG-ID of an SCell candidate cell in the configuration contents as an SCell candidate cell is disclosed. As a specific example of a condition in which a mobile terminal notifies a PCell of a CSG access restriction determination result, a case in which CSG access restriction is performed is disclosed. As a specific example of a method in which a mobile terminal notifies a PCell of a CSG access restriction determination result, a case in which "RRC Connection Reconfiguration complete", which is an existing RRC signaling, is used for both "accessible" and "inaccessible", is disclosed.
[0374] As a specific example of a method in which a PCell knows the "SCell usage configuration of a CSG unregistered UE" of another cell, a case in which each cell notifies a control unit of a base station of its own cell's "SCell usage configuration of a CSG unregistered UE" is disclosed. As a specific example of the notification timing of the "SCell usage configuration of a CSG unregistered UE", a case at the time of base station installation is disclosed.
[0375] In Step ST1501, a base station is installed. In this operation example, base station A having a plurality of cells (CC) including cell 1 and cell 2 is installed.
[0376] In steps ST2101 and ST2102, each cell in the base station notifies a control unit in the base station of the configuration of its own cell. The configuration of its own cell includes a "SCell use configuration of a UE not registered with CSG." In this operation example, in step ST2101, cell 1 notifies the control unit of its "SCell use configuration of a UE not registered with CSG." In step ST2102, cell 2 notifies the control unit of its "SCell use configuration of a UE not registered with CSG."
[0377] Next, the processes of steps ST1401 to ST1407 shown in the above-mentioned Fig. 14 are performed, and the mobile terminal (UE) selects cell 1 in base station A as the best cell and camps on it. Next, the processes of steps ST1408 to ST1416 shown in the above-mentioned Fig. 14 are performed, and then the mobile terminal (UE) proceeds to step ST1417.
[0378] In Step ST1417, the cell that is a PCell starts communication with the mobile terminal. In this operation example, cell 1, as a PCell, starts communication with the mobile terminal.
[0379] In Step ST1504, the cell that is the PCell selects another cell as a SCell candidate. In this operation example, cell 1 that has become the PCell selects cell 2 as a SCell candidate.
[0380] In Step ST2103, the cell that is a PCell inquires of the control unit about the configuration of the cell that is the SCell candidate selected in Step ST1504. The cell that is a PCell may inquire of the control unit about the "SCell usage configuration of a CSG unregistered UE" of the SCell candidate. In this operation example, cell 1 that is a PCell inquires of the control unit about the "SCell usage configuration of a CSG unregistered UE" of cell 2 selected as the SCell candidate.
[0381] In Step ST2104, the control unit responds to the inquiry in Step ST2103 to the cell that is a PCell. The control unit may notify the cell that is a PCell of the "SCell use configuration of a CSG unregistered UE" of the queried cell. In this operation example, the control unit notifies cell 1 that is a PCell of the "SCell use configuration of a CSG unregistered UE" of cell 2 that is the queried cell.
[0382] In step ST2105, the cell that is the PCell notifies the mobile terminal of the SCell candidate cell and the configuration contents of the SCell candidate cell by using dedicated RRC signaling. In this operation example, the mobile terminal notifies the mobile terminal of cell 2 as the SCell candidate cell and the configuration contents of cell 2 by using an "RRC Connection Reconfiguration message" of the dedicated RRC signaling. At that time, the system information of cell 2 and "SCell use configuration of CSG unregistered UE" are also notified. Specifically, information regarding access to cell 2, for example, CSG-ID_cell 2, etc. is notified as the CSG identity, and CSG-indication_cell 2, etc. is notified as the CSG indication.
[0383] In step ST2106, cell 2 broadcasts the SIB to mobile terminals served by the cell 2. At that time, the "SCell use configuration of CSG unregistered UE" of cell 2 may also be broadcast. Specifically, information regarding access to cell 2, for example, CSG-ID_cell 2, etc. is broadcast as a CSG identity, and CSG-indication_cell 2, etc. is broadcast as a CSG indication. In this operation example, a case is disclosed in which access restriction is performed using the CSG-indication and CSG-ID of an SCell candidate cell in the configuration content as an SCell candidate cell. Therefore, the mobile terminal may or may not receive broadcast information from cell 2.
[0384] In Step ST2107, the user equipment (UE) judges whether or not the SCell candidate cell received in Step ST2105 can be used as a SCell in a CSG unregistered UE. For this judgment, the user equipment (UE) uses the "SCell use configuration of CSG unregistered UE" received from the cell in Step ST2105.
[0385] If the user equipment (UE) determines in Step ST2107 that the SCell candidate cell received in Step ST2105 is usable as a SCell in a CSG unregistered UE, the user equipment moves to Step ST2005. If the user equipment determines in Step ST2107 that the SCell candidate cell received in Step ST2105 is not usable as a SCell in a CSG unregistered UE, the user equipment moves to Step ST2003.
[0386] In addition to the effects of the above-described fifth embodiment, the first modification of the fifth embodiment provides the following effects. It is possible to set, for each cell in a base station, whether or not a UE that is not CSG registered can be used as an SCell. This makes it possible to realize more detailed cell management.
[0387] This modification can be used in combination with the above-described first embodiment.
[0388] Embodiment 6 In the sixth embodiment, a different solution is disclosed for the same problem as in the third embodiment, that is, the problem that occurs when the second embodiment is used. The solution in the sixth embodiment is shown below. In this embodiment, the problem in the second embodiment is solved by using a method different from that of the second embodiment.
[0389] A base station (cell) configures an SCell in consideration of the CSG registration status of a mobile terminal. This can prevent the mobile terminal from configuring a cell belonging to an unregistered CSG as an SCell for the mobile terminal. Therefore, it is possible to prevent a mobile terminal that is unregistered in a CSG to which a cell belongs from using resources of the cell as an SCell while improving communication speed using carrier aggregation. The CSG registration status of a mobile terminal corresponds to the permission status of access to SCell candidate cells for the mobile terminal (UE).
[0390] A specific example of a method in which a base station (cell) configures an SCell in consideration of the CSG registration status of a mobile terminal is disclosed below. The cell is capable of configuring a cell (CC) that does not belong to a CSG as an SCell. The cell is capable of configuring, among the cells (CC) that belong to a CSG, a cell (CC) that operates in an open access mode or a cell (CC) that operates in a hybrid access mode as an SCell. The cell is capable of configuring, among the cells (CC) that belong to a CSG, a cell (CC) that belongs to the same CSG as the CSG to which the mobile terminal is registered as an SCell. The cell is unable to configure, among the cells (CC) that belong to a CSG, a cell (CC) that operates in a closed access mode and that belongs to a CSG to which the mobile terminal is not registered as an SCell.
[0391] When configuring a cell (CC) that operates in a hybrid access mode among cells (CC) belonging to a CSG as an SCell, the base station (cell) may do the following: Allow a mobile terminal registered in the CSG to which the cell belongs to to be able to configure the cell (CC) as an SCell with priority over unregistered mobile terminals.
[0392] The following three (1) to (3) are disclosed as specific examples of methods for a PCell to know whether or not other cells belong to a CSG, the operating mode when other cells belong to a CSG, and the CSG-ID when other cells belong to a CSG.
[0393] (1) Before deciding to configure a PCell as an SCell, a SCell candidate cell is selected. The PCell queries the SCell candidate cell about whether the SCell candidate cell belongs to a CSG, the CSG-ID to which the SCell candidate cell belongs, and the operation mode of the SCell candidate cell.
[0394] The "CSG indication" and "CSG-ID" may be queried. In this case, if the response from the SCell does not include the CSG-ID and the CSG indication is "FALSE", it may be determined that the SCell does not belong to the CSG, or that the SCell belongs to the CSG and operates in the open access mode. If the response from the SCell includes the CSG-ID and the CSG indication is "TRUE", it may be determined that the SCell belongs to the CSG and operates in the closed access mode. If the response from the SCell includes the CSG-ID and the CSG indication is "FALSE", it may be determined that the SCell belongs to the CSG and operates in the hybrid access mode.
[0395] The PCell may select a set of SCell candidate cells before deciding to configure the PCell as an SCell. In this case, the inquiry may be made to the set of SCell candidate cells.
[0396] (2) Each cell notifies the control unit of the base station of "whether or not the own cell belongs to a CSG", the "CSG-ID" when the own cell belongs to a CSG, and the "operation mode" when the own cell belongs to a CSG. Before deciding to configure the PCell as an SCell, an SCell candidate cell is selected. The PCell inquires of the control unit whether or not the SCell candidate cell belongs to a CSG, the CSG-ID to which the SCell candidate cell belongs, and the operation mode. The "CSG indication" and "CSG-ID" may be inquired. The information indicated by the combination of the "CSG indication" and "CSG-ID" is the same as in the above specific example (1). Before deciding to configure the PCell as an SCell, the PCell may select a SCell candidate cell set. In this case, the inquiry may be made to the SCell candidate cell set.
[0397] (3) Each cell notifies other cells of "whether or not the cell belongs to a CSG", its "CSG-ID" if it belongs to a CSG, and its "operation mode" if it belongs to a CSG. It may also notify "CSG indication" and "CSG-ID". The information indicated by the combination of "CSG indication" and "CSG-ID" is the same as in the above specific example (1).
[0398] In the specific examples (1) to (3), "whether or not it belongs to the CSG" may be "that it belongs to the CSG" or "that it does not belong to the CSG".
[0399] Specific examples of the notification timing of "whether or not the device belongs to a CSG," "CSG-ID," and "operation mode" are similar to the specific examples of the notification timing of the "SCell usage setting" in the first variant of the second embodiment described above, and therefore will not be described.
[0400] The following two methods (1) and (2) are disclosed as specific examples of a method in which a base station (cell) knows the CSG registration status of a mobile terminal.
[0401] (1) A base station (cell) knows the CSG registration status of a mobile terminal via an MME. The MME may notify a cell of the CSG registration status of a mobile terminal that is in a call, communication, or CONNECTED state via the cell. The notification may be the registration status of the mobile terminal with respect to one or more CSGs to which a base station including the cell belongs. This prevents notification of information that is not used in selecting an SCell in the cell, and provides the effect of enabling effective use of communication resources. As specific examples of triggers for the notification, the following two (a1) and (a2) are disclosed.
[0402] (a1) The MME notifies spontaneously. (a2) The MME notifies when a request made by the cell to the MME is triggered. The cell may make the request when determining an SCell candidate cell. The cell may also request notification of the registration status of the mobile terminal with respect to the CSG to which the SCell candidate cell belongs. In this case, the MME may notify the registration status of the mobile terminal with respect to the CSG to which the SCell candidate cell belongs.
[0403] (2) A base station (cell) knows the CSG registration status of a mobile terminal via a UE. A mobile terminal that is in a call, in communication, or in a CONNECTED state may notify the cell of the CSG registration status of the mobile terminal. As specific examples of triggers for such notification, the following two (b1) and (b2) are disclosed.
[0404] (b1) The mobile terminal spontaneously notifies. (b2) The mobile terminal notifies, triggered by a request made by the cell to the mobile terminal. The cell may request notification of the registration status of the mobile terminal for one or more CSGs to which the base station including the cell belongs. In that case, the mobile terminal may notify the registration status of the mobile terminal for one or more CSGs to which the base station including the cell belongs. This prevents the cell from notifying information that is not used for selecting an SCell, and an effect of enabling efficient use of radio resources can be obtained. The cell may also make the request when determining an SCell candidate cell. The cell may also request notification of the registration status of the mobile terminal for the CSG to which the SCell candidate cell belongs. In that case, the mobile terminal may notify the registration status of the mobile terminal for the CSG to which the SCell candidate cell belongs.
[0405] A specific example of a notification method in which a base station (cell) learns the CSG registration status of a mobile terminal via an MME is disclosed below. "UE Context" is used. "INITIAL CONTEXT SETUP REQUEST", which is a setup request for "UE Context" notified from an MME to a base station as disclosed in Non-Patent Document 11, or "UE context modification" may also be used. This method is effective in that it does not require new signaling, and makes it possible to avoid complicating the communication system.
[0406] Also, in order to notify the registration status of the mobile terminal, it is advisable to use "CSG membership Status" included in "INITIAL CONTEXT SETUP REQUEST". This makes additional parameters unnecessary, and makes it possible to build a communication system with excellent backward compatibility. Also, it is advisable to newly create "CSG membership Status" during "UE context modification". This allows the base station (cell) to know the CSG registration status of the mobile terminal via the MME even when the "UE Context" is changed other than when the mobile terminal first starts communication with the base station (cell). Therefore, it is possible to obtain the effect of enabling the construction of a flexible communication system.
[0407] As specific examples of points that require modification to existing parameters, the following three items (1) to (3) will be disclosed. For convenience, the "INITIAL CONTEXT SETUP REQUEST" will be described, but the same applies to "UE context modification."
[0408] (1) In the conventional technology, when a mobile terminal is accessed via a cell operating in a hybrid access mode, the existing parameter "CSG membership Status" is included in the "INITIAL CONTEXT SETUP REQUEST". Therefore, in the conventional technology, when a mobile terminal is accessed via a cell not belonging to a CSG, or via a cell belonging to a CSG operating in an open access mode, or via a cell belonging to a CSG operating in a closed access mode, the MME cannot notify the cell of the registration status of the mobile terminal.
[0409] Therefore, "CSG membership Status" is included in "INITIAL CONTEXT SETUP REQUEST" in all cases, regardless of the cell through which the mobile terminal accesses. This enables the MME to notify the cell of the registration status of the mobile terminal even when the mobile terminal accesses the cell through a cell that does not belong to the CSG, through a cell that belongs to the CSG and operates in an open access mode, or through a cell that belongs to the CSG and operates in a closed access mode.
[0410] A new parameter other than "CSG membership Status" may be provided. Alternatively, when a mobile terminal is accessed via a cell capable of carrier aggregation, "CSG membership Status" may be included in "INITIAL CONTEXT SETUP REQUEST". This prevents notification of information that is not used in selecting an SCell in the cell, and provides the effect of enabling effective use of communication resources.
[0411] (2) In the conventional technology, the "CSG membership status" of the cell through which the mobile terminal passes when accessing is notified. Therefore, in the conventional technology, the MME cannot notify a cell of the CSG registration status of a mobile terminal other than the CSG to which the cell belongs.
[0412] Therefore, the "CSG membership Status" of the "INITIAL CONTEXT SETUP REQUEST" may include the registration status of all CSG-IDs registered by the UE, regardless of the cell through which the mobile terminal accesses. This makes it possible to notify the registration status of the mobile terminal for CSGs other than the CSG to which the cell through which the mobile terminal accesses belongs. A new parameter other than the "CSG membership Status" may be created.
[0413] Alternatively, the registration status of the mobile terminal with respect to the CSG to which other cells in the base station including the cell through which the mobile terminal accesses may belong may be notified. This prevents notification of information that is not used in the selection of an SCell in the cell, and provides an effect of enabling effective use of communication resources.
[0414] (3) A combination of (1) and (2) above.
[0415] A specific example of the operation of the MME is disclosed below. The MME omits the execution of CSG access control in the MME, regarding the access control of the mobile terminal through the cell configured in the SCell in the base station as being executed by the PCell. The MME may be configured to execute only the access control of the mobile terminal through the PCell. The MME may be configured to execute only the access control of the mobile terminal through the PCell belonging to the CSG. The MME may be configured to execute only the access control of the mobile terminal through the PCell that is a CSG cell.
[0416] A specific example of the operation of the mobile terminal is disclosed below. The mobile terminal omits the execution of CSG access control in the mobile terminal for a cell for which the configuration contents have been notified as an SCell, assuming that the mobile terminal itself can access the cell. A specific example of the method in which the mobile terminal omits CSG access restriction is the same as that in the above-mentioned third embodiment, and therefore a description thereof will be omitted.
[0417] Next, a specific example of a sequence of the communication system in the sixth embodiment will be described with reference to Fig. 22. Fig. 22 is a diagram showing an example of a sequence of the communication system in the sixth embodiment. In the sixth embodiment, the processes of steps ST1401 to ST1416 in Fig. 14 described above are the same as those in the second embodiment, so illustrations and explanations are omitted, and illustrations and explanations are given starting from the process of step ST1417 in Fig. 14. In addition, the sequence shown in Fig. 22 is similar to the sequences shown in Figs. 14, 15, and 19, so the same steps are given the same step numbers, and common explanations are omitted.
[0418] In this operation example, a case will be described in which a base station A having multiple cells (CC) including cell 1 and cell 2 exists, a UE selects cell 1 in base station A as the best cell, camps on it, starts communication, and then cell 2 is set as an SCell. As a specific example of a method in which a PCell knows whether other cells belong to a CSG, the CSG-ID when other cells belong to a CSG, and the operation mode when other cells belong to a CSG, a case in which each cell notifies a control unit of the base station of its own cell's "CSG indication" and "CSG-ID" will be disclosed. As a specific example of the notification timing of the "CSG indication" and "CSG-ID", a case at the time of base station installation will be disclosed. As a specific example of a method in which a base station (cell) knows the CSG registration status of a mobile terminal, a case in which the base station (cell) knows the CSG registration status of a mobile terminal via an MME will be disclosed. In addition, as a specific example of a notification method in which a base station (cell) knows the CSG registration status of a mobile terminal via an MME, a case in which "INITIAL CONTEXT SETUP REQUEST" is used will be disclosed.
[0419] After the processing of step ST1501 shown in FIG. 15 and steps ST1901 and ST1902 shown in FIG. 19 is performed, the processing of steps ST1401 to ST1407 shown in FIG. 14 is performed, and the mobile terminal (UE) selects cell 1 in base station A as the best cell and camps on it.
[0420] In Step ST2201, the MME requests the base station (cell) to set up a "UE Context" of the mobile terminal. The MME may request the PCell to set up a "UE Context" of the mobile terminal. Furthermore, the MME may notify the base station (cell) of the CSG registration status of the mobile terminal. This request may use an "INITIAL CONTEXT SETUP REQUEST". Furthermore, the "INITIAL CONTEXT SETUP REQUEST" may include a "CSG Membership Status".
[0421] Next, after the processes of Steps ST1408 to ST1416 shown in Fig. 14 described above are performed, in Step ST1417, the cell that is a PCell starts communication with the mobile terminal (UE). In this operation example, cell 1, as a PCell, starts communication with the mobile terminal.
[0422] Next, after the processes of Step ST1504 and Steps ST1903 to ST1905 are performed, in Step ST1906, the cell that is a PCell judges whether or not the CSG indication of the cell that is a SCell candidate selected in Step ST1504 is "TRUE". In other words, the cell that is a PCell judges whether or not the access mode of the SCell is a closed access mode. For this judgment, the response result to the inquiry received from the control unit in Step ST1904 is used.
[0423] If the cell that is a PCell determines in Step ST1906 that the CSG indication of the cell that is a SCell candidate selected in Step ST1504 is not "TRUE", that is, is "FALSE", it proceeds to Step ST1508. In other words, if the cell that is a PCell determines in Step ST1906 that the operation mode of the cell that is a SCell candidate selected in Step ST1504 is the open access mode or the hybrid access mode, it proceeds to Step ST1508.
[0424] Furthermore, if the cell that is a PCell determines in Step ST1906 that the CSG indication of the SCell candidate selected in Step ST1504 is "TRUE", it moves to Step ST2202. In other words, if the cell that is a PCell determines in Step ST1906 that the operation mode of the cell that is the SCell candidate selected in Step ST1504 is the closed access mode, it moves to Step ST2202.
[0425] In Step ST2202, the cell that is a PCell judges whether or not the mobile terminal is registered in the CSG to which the SCell candidate cell selected in Step ST1504 belongs. For the CSG to which the SCell candidate cell belongs in this judgment, the response result to the inquiry received from the control unit in Step ST1904 is used. For the CSG registration status of the mobile terminal in this judgment, the notification received from the MME in Step ST2201 is used.
[0426] When the cell that is a PCell determines in Step ST2202 that the mobile terminal is registered in the CSG to which the SCell candidate cell belongs, the cell moves to Step ST1508. When the cell that is a PCell determines in Step ST2202 that the mobile terminal is not registered in the CSG to which the SCell candidate cell belongs, the cell returns to Step ST1504 to select another cell as the SCell candidate cell.
[0427] The processing of steps ST1905, ST1906, and ST2202 realizes a feature of the present embodiment that a cell (CC) not belonging to a CSG, or a cell (CC) belonging to a CSG that operates in an open access mode, or a cell (CC) belonging to a CSG that operates in a hybrid access mode, or a cell (CC) belonging to the same CSG as the CSG to which the mobile terminal is registered, can be configured as an SCell. Alternatively, a cell (CC) belonging to a CSG that operates in a closed access mode and that belongs to a CSG to which the mobile terminal is not registered can be configured as an SCell.
[0428] The above-described sixth embodiment can provide the following effects. As in the above-described third embodiment, it is possible for an operator to specify available subscribers for SCells as well. Furthermore, by belonging to a CSG, it is possible to build a user-friendly communication system that respects the user's wishes, such as the services that the user wants to receive or the billing settings that the user wants to apply. At the same time, as in the above-described second embodiment, it is possible to stabilize the operation of the communication system while improving the communication speed using carrier aggregation, and to provide appropriate services.
[0429] This embodiment can be used in combination with the above-described first embodiment.
[0430] Embodiment 7 In the seventh embodiment, a different solution to the same problem as in the second embodiment described above is disclosed. The solution in the seventh embodiment is as follows. Each cell (CC) is not allowed to set a CSG-ID for each cell (CC). One or more cells (CC) included in the same base station belong to one CSG. In a base station capable of carrier aggregation, each cell (CC) may not be allowed to set a CSG-ID for each cell (CC). One or more cells (CC) included in a base station capable of carrier aggregation may belong to one CSG.
[0431] A specific example of the operation of the MME is disclosed below. The MME omits the access control of the mobile terminal through the cell configured in the SCell in the base station, treating the access control of the mobile terminal through the PCell as the same as the access control of the mobile terminal through the PCell. The MME may be configured to only perform the access control of the mobile terminal through the PCell belonging to the CSG. The MME may be configured to only perform the access control of the mobile terminal through the PCell that is a CSG cell.
[0432] As specific examples of the operation of a base station, the following two (1) and (2) are disclosed.
[0433] (1) When performing carrier aggregation, the base station can configure any cell in the base station as a SCell. In addition, when performing carrier aggregation, the base station can configure any cell as a SCell even if the base station includes a cell that belongs to a CSG.
[0434] (2) When performing carrier aggregation, the base station can activate any cell in the base station as a SCell. Also, when performing carrier aggregation, the base station can activate any cell as a SCell even if the base station includes a cell belonging to a CSG.
[0435] In the configuration of a cell (PCell) as an SCell for a mobile terminal, the CSG-indication and CSG-ID of the SCell may not be notified.
[0436] A specific example of the operation of the mobile terminal is disclosed below. The mobile terminal omits the execution of CSG access control in the mobile terminal, that is, CSG access restriction, for a cell notified of the configuration contents as an SCell, in the same manner as the access control of a PCell. A specific example of the method in which the mobile terminal omits CSG access restriction is the same as in the above-mentioned third embodiment, and therefore a description thereof will be omitted.
[0437] A specific example of the sequence of the communication system in the seventh embodiment is similar to the sequence shown in FIG. 14, and therefore a description thereof will be omitted.
[0438] The above-described seventh embodiment can provide the following effects. As in the above-described third embodiment, it is possible for an operator to specify available subscribers for SCells as well. Furthermore, by belonging to a CSG, it is possible to build a user-friendly communication system that respects the user's wishes, such as the services that the user wants to receive or the billing settings that the user wants to apply. At the same time, as in the above-described second embodiment, it is possible to stabilize the operation of the communication system while improving the communication speed using carrier aggregation, and to provide appropriate services.
[0439] Furthermore, in the seventh embodiment, the control of the communication system in the mobile terminal or base station is easier than in the third, fourth, fifth, and sixth embodiments. Therefore, compared to the third, fourth, fifth, and sixth embodiments, the seventh embodiment can provide an effect of preventing control delays.
[0440] Embodiment 8 The aforementioned Non-Patent Document 1 discloses that handovers in an LTE system include handovers via an X2 interface (also called X2 handovers) and handovers via an S1 interface (also called S1 handovers). It also discloses that movement from an eNB or HeNB to a CSG cell or hybrid cell uses S1 handover.
[0441] FIG. 23 is a diagram showing a sequence of a communication system relating to a handover method from an eNB or a HeNB to a CSG cell or a hybrid cell, which is disclosed in Non-Patent Document 1.
[0442] In Step ST2300, a source eNB starts communication with a mobile terminal (UE). In Step ST2301, the source eNB notifies the mobile terminal of a measurement configuration.
[0443] In Step ST2313, the UE performs a measurement report in accordance with the measurement configuration notified in Step ST2301. The measurement report includes the PCI of the measurement target cell and the like.
[0444] In Step ST2314, the source eNB performs reconfiguration of the measurement setting to request receiving and reporting system information of the measurement target cell, as necessary. The source eNB sets a measurement gap, as necessary. A measurement gap is a period during which the mobile terminal stops transmitting and receiving data in the frequency currently being served in order to measure other systems or other frequencies.
[0445] In Step ST2302, the mobile terminal performs a measurement report in accordance with the measurement reconfiguration notified in Step ST2314. The measurement report includes the CSG-ID of the measurement target cell and a member indication for the measurement target cell. The member indication is a membership status determined based on the CSG-ID that the mobile terminal receives from the target cell and a whitelist in the mobile terminal. The CSG-ID of the measurement target cell and the like can be obtained by the mobile terminal receiving system information of the measurement target cell.
[0446] In Step ST2303, the source eNB makes a handover (HO) decision in consideration of the measurement report received from the UE in Step ST2302.
[0447] In Step ST2304, the source eNB notifies the MME of a handover request. The handover request is also referred to as a handover required. The handover request includes the CSG-ID of the target cell determined in Step ST2303. If the target cell is a hybrid cell, the handover request includes the access mode of the target cell.
[0448] In Step ST2305, the MME executes access control. Specifically, the MME determines whether the mobile terminal is registered in the CSG-ID of the target cell received in Step ST2304, thereby determining whether the mobile terminal can access the target cell. The CSG subscription data of the mobile terminal stored in the MME is used to determine whether the mobile terminal is registered in the CSG-ID of the target cell.
[0449] In Step ST2306, the MME determines whether or not handover is possible, taking into consideration the result of the access control in Step ST2305, that is, the result of determining whether or not the UE can access the target cell.
[0450] Specifically, when the MME determines in Step ST2305 that the UE cannot access the target cell, the MME determines in Step ST2306 that handover is not possible. When the MME determines in Step ST2306 that handover is not possible, the MME ends the process and moves to another process. The other processes are not characteristic of the present disclosure, and therefore description thereof will be omitted.
[0451] When the MME determines in Step ST2305 that the UE can access the target cell, the MME determines in Step ST2306 that handover is possible, and proceeds to Step ST2307.
[0452] In Step ST2307, the MME notifies the target eNB, which is the target cell, of a handover request. The handover request includes the CSG-ID of the target eNB received from the source eNB. If the target eNB is a hybrid cell, the handover request includes the membership status.
[0453] In Step ST2308, the target eNB judges whether or not the CSG-ID included in the handover request received in Step ST2307 is the same as the CSG-ID broadcast by the target eNB. Hereinafter, this judgment may be referred to as a "CSG-ID check."
[0454] In step ST2309, the target eNB uses the result of the judgment in step ST2308 to judge whether the check result of the CSG-ID is OK or not, that is, whether it is good or not. If the target eNB judges in step ST2308 that the CSG-IDs are the same, it judges in step ST2309 that the check result of the CSG-ID is good and proceeds to step ST2310. If the target eNB judges in step ST2308 that the CSG-IDs are not the same, that is, different, it judges in step ST2309 that the check result of the CSG-ID is not good, ends the process, and proceeds to other processes. The other processes are not characteristic of the present disclosure, so a description thereof will be omitted.
[0455] In Step ST2310, the target eNB notifies the MME of a handover request acknowledgment. In Step ST2310, the MME, which has received the handover request acknowledgment from the target eNB, notifies the source eNB of a handover command in Step ST2311. In Step ST2312, the source eNB, which has received the handover command from the MME, notifies the mobile terminal of the handover command.
[0456] Non-Patent Document 1 describes that the PCell can be changed only by handover. However, Non-Patent Document 1 does not raise any problem about the relationship between the CSG to which the handover destination CC (cell) belongs and the CSG to which the mobile terminal belongs, nor discloses any solution to the problem.
[0457] Also, 3GPP R2-104788 (hereinafter referred to as "Non-Patent Document 12") discloses that the PCell should be changeable in reconfiguration. However, Non-Patent Document 12 does not raise any problem or disclose any solution regarding the relationship between the CSG to which the handover destination CC (cell) belongs and the CSG to which the mobile terminal belongs.
[0458] The problem to be solved in the eighth embodiment will be described below. In the conventional technology, an appropriate method of access control in changing a PCell to a CSG cell or a hybrid cell in the same base station (eNB) is not disclosed. Also, as described above, in access of a mobile terminal through a CSG cell, an MME executes access control. That is, a base station does not restrict access to a CSG. Therefore, for a UE that is not registered in a CSG to which a cell belongs, the cell (CC) may be set as a CC to which the PCell is changed. Therefore, a problem occurs that appropriate services cannot be provided.
[0459] The solution in the eighth embodiment is as follows. The MME performs access control of a CC to which the PCell is changed (hereinafter, also referred to as a "target CC"). The PCell (hereinafter, also referred to as a "source CC") notifies the MME of the CSG-ID of the target CC.
[0460] The source cell (PCell) may change the method of obtaining the CSG-ID of the target CC depending on whether the target cell is in the same base station or not. Alternatively, the source cell (PCell) may change the method of obtaining the CSG-ID of the target CC depending on whether the target cell is controlled by the same controller or not.
[0461] A specific example of a method for a source cell to determine whether a target cell exists within the same base station is disclosed below. The determination is made based on cell identification information of the measurement target cell (target cell) included in a measurement report from a mobile terminal. Specific examples of cell identification information include PCI and GCI. If a cell having cell identification information of the measurement target cell exists within the same base station as the source cell, the target cell is determined to exist within the same base station. If a cell having cell identification information of the measurement target cell does not exist within the same base station as the source cell, the target cell is determined to not exist within the same base station. The entity making the determination within the source cell may be the source cell (PCell) or a control unit.
[0462] A specific example of a method in which the PCell knows the CSG-ID of the target CC when the target cell is not in the same base station as the PCell (source CC) is disclosed below. The CSG-ID is obtained from a measurement report of the mobile terminal. This specific example can also be used as a specific example of a method in which the PCell knows the CSG-ID of the target CC when the target cell is not controlled by the same control unit as the PCell (source CC).
[0463] The following four specific examples (1) to (4) are disclosed as specific examples of a method in which a PCell knows the CSG-ID of a target CC when the target cell is in the same base station as the PCell (source CC). The following four specific examples (1) to (4) can also be cited as specific examples of a method in which a PCell knows the CSG-ID of a target CC when the target cell is controlled by the same control unit as the PCell (source CC).
[0464] (1) Obtained from a measurement report of a mobile terminal. This specific example is similar to the handover method from an eNB or HeNB to a CSG cell or a hybrid cell disclosed in Non-Patent Document 1. Therefore, according to this specific example, it is possible to obtain an effect of preventing the communication system from becoming complicated, compared with the specific examples (2) to (4) described later.
[0465] (2) The PCell queries the target CC for the "CSG-ID". This eliminates the need for the PCell to obtain the CSG-ID of the measurement target cell (target CC) from the measurement report of the mobile terminal. Also, in this specific example, unlike specific example (1), the mobile terminal does not need to receive system information of the measurement target cell. Therefore, it is not necessary to provide a measurement gap in the mobile terminal, and it is possible to obtain the effect of preventing a decrease in the communication speed of the mobile terminal.
[0466] (3) Each cell notifies the control unit of the base station of the "CSG-ID" of its own cell. The PCell inquires of the control unit about the "CSG-ID" of the target CC. This eliminates the need for the PCell to obtain the CSG-ID of the measurement target cell (target CC) from the measurement report of the mobile terminal. Also, in this specific example, unlike specific example (1), the mobile terminal does not need to receive system information of the measurement target cell. Therefore, it is not necessary to provide a measurement gap in the mobile terminal, and it is possible to obtain an effect that it is possible to prevent a decrease in the communication speed of the mobile terminal. Also, the control unit may notify each cell (PCell) of the "CSG-ID" of each cell before the inquiry from the PCell.
[0467] (4) Each cell notifies other cells of its own cell's "CSG-ID". This eliminates the need for the PCell to obtain the CSG-ID of the measurement target cell (target CC) from the measurement report of the mobile terminal. Also, in this specific example, unlike specific example (1), the mobile terminal does not need to receive system information of the measurement target cell. Therefore, it is not necessary to provide a measurement gap in the mobile terminal, and it is possible to obtain the effect of preventing a decrease in the communication speed of the mobile terminal.
[0468] The specific examples (2) to (4) can be easily realized because the PCell (source CC) and the target CC are present in the same base station, or because the PCell (source CC) and the target CC are controlled by the same controller.
[0469] The following two methods (1) and (2) are disclosed as specific examples of a method in which a source CC notifies an MME of a CSG-ID of a target CC.
[0470] (1) A new S1 signaling is provided. The parameter to be mapped to the newly provided S1 signaling is the CSG-ID of the target CC. This may be notified together with the identifier of the mobile terminal. The identifier of the mobile terminal may be the UE-ID or the IMSI.
[0471] (2) Existing S1 signaling is used. A specific example of existing signaling is a handover request. The handover request is also called a handover required. This specific example is similar to the handover method from an eNB or HeNB to a CSG cell or a hybrid cell disclosed in Non-Patent Document 1. Therefore, according to this specific example, it is possible to obtain an effect of preventing the communication system from becoming complicated.
[0472] The MME performs access control using the CSG-ID of the target CC received from the source CC.
[0473] Next, a specific example of a sequence of the communication system in the eighth embodiment will be described with reference to Fig. 24. Fig. 24 is a diagram showing an example of a sequence of the communication system in the eighth embodiment. In this embodiment, the processes of steps ST1401 to ST1416 in Fig. 14 described above are the same as those in the second embodiment, and therefore illustration and description are omitted. Also, the sequence shown in Fig. 24 is similar to the sequence shown in Fig. 23, so the same steps are given the same step numbers and common descriptions are omitted.
[0474] In this operation example, a case will be described in which a base station A having multiple cells (CC) including cell 1 and cell 2 exists, a UE selects cell 1 in base station A as the best cell to camp on, and after starting communication, cell 2 becomes the CC to which the PCell is changed. As a specific example of a method in which the PCell knows the CSG-ID of the target CC, a case will be disclosed in which each cell notifies the control unit of the base station of the "CSG-ID" of its own cell.
[0475] In step ST2400, a base station is installed. In this operation example, base station A having multiple cells (CC) including cell 1 and cell 2 is installed. In steps ST2401 and ST2402, each cell in the base station notifies the control unit in the base station of the setting of its own cell. The setting of its own cell includes a "CSG-ID." In this operation example, in step ST2401, cell 1 notifies the control unit of its "CSG-ID." In step ST2402, cell 2 notifies the control unit of its "CSG-ID."
[0476] Next, after the processes of steps ST1401 to ST1416 shown in FIG. 14 described above are performed, in step ST2300, the source CC, which is the source eNB, starts communication with the mobile terminal (UE). In this operation example, cell 1, which is the source CC, which is the source cell (PCell), starts communication with the mobile terminal (UE).
[0477] In Step ST2403, the source CC (cell 1) notifies the user equipment (UE) of a measurement configuration. In Step ST2404, the user equipment (UE) performs a measurement report to the source CC (cell 1) according to the measurement configuration notified in Step ST2403. The measurement report includes the PCI of the measurement target cell, which is the measurement target cell, and the like.
[0478] In step ST2303, the source CC (cell 1) which is the source eNB makes a handover decision in consideration of the measurement report received from the mobile terminal (UE) in step ST2404. Also, the source CC (cell 1) which is the source cell (PCell) may determine whether or not the target cell exists within the same base station, and may determine a method of obtaining the CSG-ID of the target CC. In this operation example, the source CC (cell 1) determines that the target CC (cell 2) exists within the same base station.
[0479] Also, in this operation example, as a method of obtaining the CSG-ID of the target CC, a method in which each cell notifies the control unit of the base station of the "CSG-ID" of its own cell is selected. In this case, the source CC does not execute reconfiguration of the measurement configuration requesting the mobile terminal (UE) to receive and report the system information of the measurement target cell in step ST2314 of FIG. 23. This eliminates the need for the mobile terminal to receive the system information of the measurement target cell. Therefore, it is possible to obtain an effect that it is possible to prevent a decrease in the communication speed of the mobile terminal by eliminating the need to provide a measurement gap in the mobile terminal. This is because the PCell obtains the CSG-ID of the target CC from a control unit or the like. Also, the method of obtaining the CSG-ID may be determined separately from the handover determination.
[0480] In Step ST2405, the cell inquires of the control unit about the configuration of the target CC determined in Step ST2303. The cell may inquire of the control unit about the "CSG-ID" and "access mode" of the target CC. In this operation example, cell 1, which is a PCell, inquires of the control unit about the "CSG-ID" and "access mode" of cell 2 selected as the target CC. Instead of inquiring about the "CSG-ID" and "access mode", the cell may inquire about the "CSG-ID" and "CSG indication".
[0481] In Step ST2406, the control unit responds to the inquiry in Step ST2405 to the cell. The control unit may notify the cell of the "CSG-ID" and "access mode" of the queried cell. In this operation example, the control unit notifies cell 1, which is a PCell, of the "CSG-ID" and "access mode" of cell 2, which is the queried cell. Instead of notifying the "CSG-ID" and "access mode", the control unit may notify the "CSG-ID" and "CSG indication".
[0482] In Step ST2407, the PCell notifies the MME of a handover request. The handover request is also referred to as a handover required. The handover request includes the CSG-ID of the target CC determined in Step ST2303. The handover request may include the access mode (Cell Access Mode) of the target CC.
[0483] In Step ST2305, the MME executes access control. Specifically, the MME determines whether the mobile terminal is registered in the CSG-ID of the target CC received in Step ST2407, thereby determining whether the mobile terminal is allowed to access the target CC. The CSG subscription data of the mobile terminal stored in the MME is used to determine whether the mobile terminal is registered in the CSG-ID of the target CC. The CGS registration data of the mobile terminal may be obtained by inquiring the HSS, or information stored in the HSS may be used as the CGS registration data of the mobile terminal. The access control may be, for example, the processing of Steps ST1411 to ST1414 shown in FIG. 14 described above.
[0484] In Step ST2306, the MME determines whether or not handover is possible, as described above, in consideration of the result of the access control in Step ST2305. If the MME determines that handover is possible, it proceeds to Step ST2408, and if it determines that handover is not possible, it ends the process and proceeds to another process.
[0485] In step ST2408, the MME notifies cell 2, which is the target CC, of a handover request. The handover request includes the CSG-ID of the target CC, which is the target eNB, received from the source CC, which is the source eNB. The handover request may include a membership status. By using the handover request, the method becomes similar to the handover method from an eNB or HeNB to a CSG cell or hybrid cell disclosed in the above-mentioned Non-Patent Document 1, and an effect can be obtained that the communication system can be prevented from becoming complicated.
[0486] In step ST2409, cell 2, which is the target CC, checks the CSG-ID. Specifically, cell 2, which is the target CC, judges whether the CSG-ID included in the handover request received in step ST2408 is the same as the CSG-ID broadcast by its own eNB. Alternatively, cell 2 may judge whether handover is acceptable (hereinafter, also referred to as "judging whether handover is acceptable" or "checking handover acceptance"). Also, cell 2 may check the CSG-ID and judge whether handover is acceptable.
[0487] In step ST2410, cell 2, which is the target CC, uses the result of the judgment in step ST2409 to judge whether the check result of the CSG-ID is OK or not, that is, whether it is good or not. If cell 2, which is the target CC, judges in step ST2409 that the CSG-IDs are the same, it judges in step ST2410 that the check result of the CSG-ID is good and moves to step ST2310. If cell 2, which is the target CC, judges in step ST2409 that the CSG-IDs are different, it judges in step ST2410 that the check result of the CGS-ID is not good, ends the process, and moves to another process. The other processes are not characteristic of this disclosure, so their explanation will be omitted.
[0488] When the cell 2 that is the target CC judges in step ST2409 whether or not it can accept the handover, it judges in step ST2410 whether the judgment result of whether or not it can accept the handover is OK or not, that is, whether or not it can accept the handover. When the cell 2 checks the CSG-ID and judges whether or not it can accept the handover in step ST2409, the cell 2 that is the target CC judges in step ST2410 whether or not the check result of the CSG-ID and the judgment result of whether or not it can accept the handover are OK or not, that is, whether or not it is good or not. When the cell 2 judges in step ST2410 that it is good, it moves to step ST2310, and when it judges that it is not good, it ends the process and moves to another process.
[0489] In Step ST2310, cell 2, which is the target CC, notifies the MME of a handover request acknowledgment. In Step ST2310, the MME, which has received the handover request acknowledgment from cell 2, notifies cell 1, which is the source CC, of a handover command in Step ST2311. In Step ST2312, cell 1, which has received the handover command from the MME, notifies the mobile terminal (UE) of the handover command.
[0490] The above-described eighth embodiment can provide the following effects. It is possible to improve the communication speed using carrier aggregation while stabilizing the operation of the communication system, and to provide appropriate services. It is also possible to eliminate the need to provide a measurement gap in the mobile terminal, and to prevent a decrease in the communication speed of the mobile terminal.
[0491] Although the present embodiment has been described mainly in terms of a case where handover is used to change the PCell, the present embodiment can also be applied to a case where reconfiguration is used to change the PCell.
[0492] This embodiment can be used in combination with the above-mentioned embodiment 1, embodiment 2, variant 1 of embodiment 2, embodiment 3, embodiment 4, embodiment 5, variant 1 of embodiment 5, embodiment 6, and embodiment 7.
[0493] Eighth embodiment, variant 1 In a first modification of the eighth embodiment, a different solution is disclosed for the same problem as in the eighth embodiment. In this modification, the differences from the solution in the eighth embodiment are mainly described, and the parts not described are the same as in the eighth embodiment.
[0494] When the target cell is present within the same base station, the source cell (PCell) can omit the "determination of whether or not to accept handover" or the "check of CSG-ID" in the target cell (CC). For example, in step ST2409 in FIG. 24, the "determination of whether or not to accept handover" or the "check of CSG-ID" can be omitted. In addition, the signaling required for the "determination of whether or not to accept handover" or the "check of CSG-ID" can be omitted.
[0495] Alternatively, both the "determination of whether or not to accept handover" and the "check of CSG-ID" may be omitted. Alternatively, the "determination of whether or not to accept handover" or the "check of CSG-ID" in the target cell may be performed by the source cell (CC). As a specific example when the source cell (PCell) is present in the same base station as the target cell, the PCell may be changed.
[0496] By doing so, the following effects can be obtained: It is possible to prevent delays in control of the communication system. It is also possible to reduce the processing load on the base station. It is also possible to realize low power consumption in the base station.
[0497] The omission can be easily realized when the PCell (source CC) and the target CC are present in the same base station, or when the PCell (source CC) and the target CC are controlled by the same controller.
[0498] A specific example of the method in which the source cell judges whether the target cell exists in the same base station or not is the same as that in the eighth embodiment, and therefore the explanation is omitted.
[0499] The following four (1) to (4) are disclosed as specific examples of optional processes such as judgments (hereinafter sometimes referred to as "control steps") and signaling.
[0500] (1) Notification of a handover request acknowledgment from the target CC to the MME. For example, the process of step ST2310 in FIG. 24. When the PCell notifies the MME of the CSG-ID of the target CC, the target CC may notify the MME that the response to the MME is to be omitted. For example, in step ST2407 in FIG. 24, the target CC may notify the MME that the response to the MME is to be omitted. The notification may be an information element of a message in which the source CC, which is the PCell, notifies the MME of the CSG-ID of the target CC. The notification may be substituted by a notification that the PCell is changed. With this specific example, after the MME notifies the handover request, it becomes possible to clearly determine whether or not there is a response to the handover request. This has the effect of enabling the construction of a stable communication system.
[0501] (2) Notification of a handover command from the MME to the PCell, which is the source CC. For example, the process of step ST2311 in FIG. 24. A message capable of recognizing that the source CC has been determined by the MME to be handover-enabled may be provided. A specific example of the new message is a notification from the target CC that has received a handover request from the MME. A specific example of the notification is a handover request acknowledgment.
[0502] (3) Judgment as to whether or not the CSG-ID included in the handover request in the target CC is the same as the CSG-ID broadcast by its own eNB, that is, "checking the CSG-ID". Or, "judging whether or not to accept the handover". Or, both "judging whether or not to accept the handover" and "checking the CSG-ID". For example, either one or both of the processes of step ST2409 and step ST2410 in FIG. 24.
[0503] This specific example (3) is particularly effective when the specific examples (2) to (4) of the method for the PCell to know the CSG-ID of the target CC are used, because there is no need to obtain the CSG-ID from the mobile terminal, and problems such as communication errors are less likely to occur.
[0504] When the determination is omitted, the notification of the handover request from the MME to the target CC may be omitted. For example, the process of step ST2408 in FIG. 24 may be omitted. A handover command or a handover request may be notified from the MME to the source CC. The handover command or the handover request may include the membership status. When the PCell notifies the MME of the CSG-ID of the target CC, the target CC may notify the MME that the determination is omitted. Alternatively, the source CC may notify the MME that the determination is to be performed. The notification may be an information element of a message in which the PCell notifies the MME of the CSG-ID of the target CC. The notification may be substituted by a notification that the PCell is changed.
[0505] This specific example (3) enables the MME to clearly determine the other party to notify of the handover request, which has the effect of enabling the construction of a stable communication system.
[0506] In this specific example (3), when the source cell (CC) executes the "determination of whether or not to accept handover" in the target cell, the processing load status and resource usage status of the target CC may be taken into consideration. The following is disclosed as a specific example of a method in which the PCell, which is the source cell, knows the processing load status and resource usage status of other cells. The processing load status and resource usage status may be included as the settings of the own cell.
[0507] (4) A combination of (1) to (3) above.
[0508] The specific examples (2) to (4) can be easily realized when the source CC and the target CC, which are PCells, are present in the same base station, or when the source CC and the target CC, which are PCells, are controlled by the same controller.
[0509] Next, a specific example of a sequence of a communication system in Modification 1 of the eighth embodiment will be described with reference to Fig. 25. Fig. 25 is a diagram showing an example of a sequence of a communication system in Modification 1 of the eighth embodiment. In this modification, the processes of steps ST1401 to ST1416 in Fig. 14 described above are the same as those in the second embodiment, and therefore illustration and description are omitted. In addition, the sequence shown in Fig. 25 is similar to the sequences shown in Figs. 23 and 24, so the same steps are given the same step numbers and common descriptions are omitted.
[0510] In this operation example, a base station A having multiple cells (CCs) including cell 1 and cell 2 is present, and after a UE selects cell 1 in base station A as the best cell and camps on it, and starts communication, cell 2 is set as the CC to which the PCell is changed. As a specific example of a method in which the PCell knows the CSG-ID of the target CC, a case in which each cell notifies the control unit of the base station of the "CSG-ID" of its own cell is disclosed. As specific examples of optional control steps, a notification of a handover request acknowledgement from the target CC to the MME in the above specific example (1), a notification of a handover command from the MME to the PCell, which is the source CC, in the above specific example (2), and a check of the CSG-ID in the target CC in the above specific example (3), i.e., a determination of whether the CSG-ID included in the handover request is the same as the CSG-ID broadcast by the eNB itself, and a determination of whether to accept the handover are disclosed.
[0511] As described above, after the processing of steps ST2400 to ST2402 is performed, the processing of steps ST1401 to ST1416 shown in FIG. 14 is performed, and then the processing of steps ST2300, ST2403, ST2404, ST2303, ST2405, and ST2406 is performed in sequence.
[0512] Next, in Step ST2501, cell 1, which is the PCell, notifies the MME of a handover request. The handover request is also called a handover required. The handover request includes the CSG-ID of the target CC determined in Step ST2303. The handover request may include the access mode (Cell Access Mode) of the target CC. In addition, the handover request may include an indication that the PCell is changed.
[0513] In this operation example, the notification is made to the effect that the PCell is changed, and that the notification of the handover request acknowledgment from the target CC to the MME is omitted, and that the determination of whether or not the CSG-ID included in the handover request in the target CC is the same as the CSG-ID broadcast by the own eNB, that is, the CSG-ID check is omitted. When the source CC, which is the PCell, executes the "determination of whether or not to accept handover" in the target cell or the "check of CSG-ID", it may be performed before this step ST2501, for example. For the "determination of whether or not to accept handover" or the "check of CSG-ID", the configuration information of the target CC received in step ST2406 may be used.
[0514] Next, the processes of Step ST2305 and Step ST2306 are performed. Next, in Step ST2502, the MME notifies the source CC, cell 1, of a handover request or a handover command. Having received the notice of a change in the PCell in Step ST2501, the MME may change the counterpart to which the handover request is notified from the target CC to the source CC.
[0515] In addition to the effects of the eighth embodiment, the first modification of the eighth embodiment described above provides the following effects. In this modification, a control step is omitted, so that delays in control of the communication system can be prevented. Furthermore, the processing load of the base station can be reduced. Furthermore, low power consumption of the base station can be achieved.
[0516] Although the present modification has been described mainly in terms of a case where handover is used to change the PCell, the present modification can also be applied to a case where reconfiguration is used to change the PCell.
[0517] This variant can be used in combination with the above-mentioned embodiment 1, embodiment 2, variant 1 of embodiment 2, embodiment 3, embodiment 4, embodiment 5, variant 1 of embodiment 5, embodiment 6, embodiment 7, and embodiment 8.
[0518] Eighth embodiment, modified example 2 In the second modification of the eighth embodiment, another solution to the same problem as in the eighth embodiment is disclosed. The solution in the second modification of the eighth embodiment is described below. In this modification, differences from the solution in the eighth embodiment are mainly described, and the parts not described are the same as in the eighth embodiment. In this modification, the base station performs access control of the target CC. Alternatively, the PCell may perform the access control.
[0519] The PCell, which is a source cell, may change the method of access control of the target CC depending on whether the target cell exists in the same base station. Alternatively, the PCell, which is a source cell, may change the method of access control of the target CC depending on whether the target cell is controlled by the same controller.
[0520] A specific example of the method in which the source cell judges whether the target cell exists in the same base station or not is the same as that in the eighth embodiment, and therefore the explanation is omitted.
[0521] A specific example of a method for access control of a target CC when the target cell does not exist in the same base station as the source CC that is a PCell is disclosed below. For example, as shown in the above-mentioned FIG. 23, an MME executes access control of the target CC. This specific example can also be cited as a specific example of a method for access control of a target CC when the target cell is not controlled by the same control unit as the source CC that is a PCell.
[0522] A specific example of a method for access control of a target CC when the target cell is present in the same base station as the source CC that is a PCell is disclosed below. The specific example disclosed below can also be cited as a specific example of a method for access control of a target CC when the target cell is controlled by the same controller as the source CC that is a PCell.
[0523] The cell is able to set or select a cell (CC) that does not belong to a CSG as a target CC. The cell is able to set or select a cell (CC) that operates in an open access mode or a cell (CC) that operates in a hybrid access mode among the cells (CC) that belong to a CSG. The cell is able to set or select a cell (CC) that belongs to the same CSG as the CSG to which the mobile terminal is registered among the cells (CC) that belong to a CSG as a target CC. The cell is unable to set or select a cell (CC) that operates in a closed access mode among the cells (CC) that belong to a CSG to which the mobile terminal is not registered as a target CC.
[0524] When setting or selecting a cell (CC) that operates in a hybrid access mode among the cells (CC) belonging to a CSG as a target CC, the base station (cell) may do the following: Allow a mobile terminal that is registered in the CSG to which the cell belongs to set or select the cell (CC) as a target CC in preference to unregistered mobile terminals.
[0525] A specific example of the method in which the PCell knows whether or not another cell belongs to the CSG, and the operation mode and CSG-ID when the other cell belongs to the CSG, is similar to that in the sixth embodiment, and therefore a description thereof will be omitted.
[0526] A specific example of the method in which the base station (cell) knows the CSG registration status of the mobile terminal is the same as in the sixth embodiment, and therefore the explanation will be omitted.
[0527] Next, a specific example of a sequence of a communication system in Modification 2 of the eighth embodiment will be described with reference to Fig. 26. Fig. 26 is a diagram showing an example of a sequence of a communication system in Modification 2 of the eighth embodiment. In this modification, the processes of steps ST1401 to ST1416 in Fig. 14 described above are the same as those in the second embodiment, and therefore illustration and description are omitted. In addition, the sequence shown in Fig. 26 is similar to the sequences shown in Figs. 23 and 24, and therefore the same steps are given the same step numbers and common descriptions are omitted.
[0528] In this operation example, a case will be described in which a base station A having multiple cells (CCs) including cell 1 and cell 2 exists, a UE selects cell 1 in base station A as the best cell and camps on it, and after starting communication, cell 2 becomes the CC to which the PCell is changed. As a specific example of a method in which the PCell knows the CSG-ID of the target CC, a case in which each cell notifies the control unit of the base station of the "CSG-ID" of its own cell is disclosed. As a specific example of a method in which the base station (cell) knows the CSG registration status of the mobile terminal, a case in which the base station (cell) knows the CSG registration status of the mobile terminal via MME is disclosed. In addition, as a specific example of a notification method in which the base station (cell) knows the CSG registration status of the mobile terminal via MME, a case in which "INITIAL CONTEXT SETUP REQUEST" is used is disclosed.
[0529] After the processes of steps ST2400 to ST2402 are performed, the processes of steps ST1401 to ST1407 shown in FIG. 14 are performed, and the mobile terminal (UE) selects cell 1 in base station A as the best cell and camps on it.
[0530] In Step ST2601, the MME requests the base station (cell) to set up a "UE Context" of the mobile terminal. The MME may request the PCell to set up a "UE Context" of the mobile terminal. Furthermore, the MME may notify the base station (cell) of the CSG registration status of the mobile terminal. This request may use an "INITIAL CONTEXT SETUP REQUEST". Furthermore, the "INITIAL CONTEXT SETUP REQUEST" may include a "CSG Membership Status".
[0531] Next, after the processes of steps ST1408 to ST1416 shown in FIG. 14 described above are performed, the processes of steps ST2300, ST2403, and ST2404 are performed. Next, in step ST2602, the cell inquires of the control unit of the base station about the configuration of the target CC determined in step ST2303. The cell may inquire of the control unit of the base station about the "CSG indication" and "CSG-ID" of the determined target CC. In this operation example, cell 1, which is a PCell, inquires of the control unit of base station A about the "CSG indication" and "CSG-ID" of cell 2 determined as the target CC.
[0532] In step ST2603, the control unit of the base station responds to the inquiry in step ST2602 to the cell. The control unit of the base station may notify the cell of the "CSG indication" and "CSG-ID" of the queried cell. In this operation example, the control unit of base station A notifies cell 1, which is the PCell, of the "CSG indication" and "CSG-ID" of cell 2, which is the queried cell.
[0533] In Step ST2604, the cell judges whether or not the target CC determined in Step ST2303 has a CSG-ID. In other words, the cell judges whether or not the target CC belongs to a CSG. For this judgment, the cell uses the response result to the inquiry received from the control unit of the base station in Step ST2603.
[0534] If the cell determines in Step ST2604 that the target CC determined in Step ST2303 has a CSG-ID, the cell proceeds to Step ST2605. In other words, if the cell determines in Step ST2604 that the target CC determined in Step ST2303 has a CSG-ID, the cell determines that the target CC belongs to a CSG, and proceeds to Step ST2605.
[0535] If the cell determines in Step ST2604 that the target CC determined in Step ST2303 does not have a CSG-ID, the cell proceeds to Step ST2312. In other words, if the cell determines in Step ST2604 that the target CC determined in Step ST2303 does not have a CSG-ID, the cell determines that the target CC does not belong to a CSG, and proceeds to Step ST2312.
[0536] In Step ST2605, the cell judges whether or not the CSG indication of the target CC determined in Step ST2303 indicates "TRUE". In other words, the cell judges whether or not the access mode of the target CC is a closed access mode. For this judgment, the cell uses the response result to the inquiry received from the control unit of the base station in Step ST2603.
[0537] If the cell determines in step ST2605 that the CSG indication of the target CC determined in step ST2303 is not "TRUE", that is, is "FALSE", it proceeds to step ST2312. In other words, if the cell determines in step ST2605 that the operation mode of the target CC determined in step ST2303 is the open access mode or the hybrid access mode, it proceeds to step ST2312.
[0538] Also, if the cell determines in step ST2605 that the CSG indication of the target CC determined in step ST2303 is "TRUE", it proceeds to step ST2606. In other words, if the cell determines in step ST2605 that the operation mode of the target CC determined in step ST2303 is the closed access mode, it proceeds to step ST2606.
[0539] In Step ST2606, the cell judges whether or not the mobile terminal is registered in the CSG to which the cell of the target CC determined in Step ST2303 belongs. For the CSG to which the target CC belongs in this judgment, the cell uses the response result to the inquiry received from the control unit of the base station in Step ST2603. For the CSG registration status of the mobile terminal in this judgment, the cell uses the notification received from the MME in Step ST2601.
[0540] When the cell determines in step ST2606 that the mobile terminal is registered in the CSG to which the target CC belongs, the cell proceeds to step ST2312. When the cell determines in step ST2606 that the mobile terminal is not registered in the CSG to which the target CC belongs, the cell ends the process and proceeds to other processes. The other processes are not characteristic of the present disclosure, and therefore will not be described here.
[0541] The processing of steps ST2604, ST2605, and ST2606 realizes the feature of this modification that a cell (CC) not belonging to a CSG, a cell (CC) belonging to a CSG that operates in an open access mode, a cell (CC) belonging to a CSG that operates in a hybrid access mode, or a cell (CC) belonging to the same CSG as the CSG to which the mobile terminal is registered, as a target CC, which is a cell (CC) belonging to a CSG that operates in a closed access mode, as well as a cell (CC) belonging to a CSG to which the mobile terminal is not registered, as a target CC.
[0542] Although different from the sequence shown in FIG. 26, before the PCell determines the target CC, a target CC candidate cell may be selected, and the processing of steps ST2602 to ST2606 may be performed for the candidate cell, and then the processing of step ST2303 may be performed.
[0543] In Step ST2607, the cell judges whether or not the target CC can accept handover. If the cell judges in Step ST2607 that the target CC determined in Step ST2303 can accept handover, the cell proceeds to Step ST2312. If the cell judges in Step ST2607 that the target CC determined in Step ST2303 cannot accept handover, the cell ends the process and proceeds to other processes. The other processes are not characteristic of the present disclosure, and therefore will not be described here.
[0544] The determination in Step ST2607 may take into consideration the processing load status, resource usage status, etc. of the target CC. The following is disclosed as a specific example of a method in which the PCell knows the processing load status and resource usage status of other cells. The processing load status, resource usage status, etc. may be included as the configuration of the own cell.
[0545] The above-described second modification of the eighth embodiment can provide the following effects similar to those of the eighth embodiment. While improving communication speed using carrier aggregation, the operation of the communication system can be stabilized, and appropriate services can be provided.
[0546] Although the present modification has been described mainly in terms of a case where handover is used to change the PCell, the present modification can also be applied to a case where reconfiguration is used to change the PCell.
[0547] This variant can be used in combination with the above-mentioned embodiment 1, embodiment 2, variant 1 of embodiment 2, embodiment 3, embodiment 4, embodiment 5, variant 1 of embodiment 5, embodiment 6, embodiment 7, embodiment 8, and variant 1 of embodiment 8.
[0548] Eighth embodiment, modified example 3 In the third modification of the eighth embodiment, a different solution is disclosed for the same problem as in the eighth embodiment. In this modification, the differences from the solutions in the eighth embodiment and the second modification of the eighth embodiment are mainly described, and the parts not described are the same as in the eighth embodiment and the second modification of the eighth embodiment.
[0549] In this modification, the source cell PCell changes the method of access control of the target CC depending on whether the target cell exists in the same base station. Alternatively, the source cell PCell may change the method of access control of the target CC depending on whether the target cell is controlled by the same control unit.
[0550] A specific example of the method in which the source cell judges whether the target cell exists in the same base station or not is the same as that in the eighth embodiment, and therefore the explanation is omitted.
[0551] A specific example of a method for access control of a target CC when the target cell does not exist in the same base station as the source CC that is a PCell is disclosed below. For example, as shown in the above-mentioned FIG. 23, an MME executes access control of the target CC. This specific example can also be cited as a specific example of a method for access control of a target CC when the target cell is not controlled by the same control unit as the source CC that is a PCell.
[0552] A specific example of a method of access control of a target CC when the target cell is present in the same base station as the source CC that is a PCell is disclosed below. If the target CC satisfies a predetermined condition, access control in changing the PCell is omitted. This specific example can also be cited as a specific example of a method of access control of a target CC when the target cell is controlled by the same control unit as the source CC that is a PCell.
[0553] As specific examples of the predetermined conditions, the following three conditions (1) to (3) are disclosed.
[0554] (1) When the target CC is already under access control: A specific example when the access is already under control is shown below. The target CC is selected from an SCell. The target CC may be selected from an SCell under access control. A specific example of an SCell under access control is an SCell set using the above-mentioned third, fourth, fifth, sixth or seventh embodiment.
[0555] (2) When the target CC is a cell (CC) that does not require access control. Specific examples of cells that do not require access control are as follows: a cell (CC) that does not belong to a CSG, a cell (CC) that belongs to a CSG and operates in an open access mode, and a cell (CC) that belongs to a CSG and operates in a hybrid access mode. As a specific example of a method for a PCell to know whether or not another cell belongs to a CSG and the operation mode when another cell belongs to a CSG, a method similar to that of the above-mentioned fourth embodiment can be used, and therefore a description thereof will be omitted.
[0556] (3) A combination of (1) and (2) above.
[0557] Furthermore, if the target CC satisfies other predetermined conditions, access control in changing the PCell may be performed.
[0558] As specific examples of the other conditions, the following three conditions (1) to (3) are disclosed.
[0559] (1) When access control has not been executed for the target CC. Specific examples when access control has not been executed are shown below. The target CC is selected from among other than an SCell. The target CC may be selected from among other than an SCell that is access-controlled. The target CC may be selected from among SCells that are not access-controlled. A specific example of an SCell for which access control has not been executed is an SCell configured using the above-mentioned second embodiment.
[0560] (2) When the target CC is a cell (CC) that requires access control. A specific example of a cell that requires access control is a cell (CC) that belongs to a CSG. Also, among the cells (CC) that belong to a CSG, a cell (CC) that operates in a closed access mode may be used. As a specific example of a method for a PCell to know whether or not another cell belongs to a CSG and an operation mode when another cell belongs to a CSG, a method similar to that of the above-mentioned fourth embodiment can be used, and therefore a description thereof will be omitted.
[0561] (3) A combination of (1) and (2) above.
[0562] Next, a specific example of a sequence of a communication system in Modification 3 of the eighth embodiment will be described with reference to Fig. 27. Fig. 27 is a diagram showing an example of a sequence of a communication system in Modification 3 of the eighth embodiment. In this modification, the processes of steps ST1401 to ST1416 in Fig. 14 described above are the same as those in the second embodiment, and therefore illustration and description are omitted. In addition, the sequence shown in Fig. 27 is similar to the sequences shown in Figs. 23 and 24, so the same steps are given the same step numbers and common descriptions are omitted.
[0563] In this operation example, a case will be described in which a base station A having multiple cells (CC) including cell 1 and cell 2 exists, a UE selects cell 1 in base station A as the best cell to camp on, and after starting communication, cell 2 is set as the CC to which the PCell is changed. As a specific example of a condition for omitting access control in changing the PCell, a case in which the target CC is already under access control will be disclosed. As a specific example of a case in which access control is already under control, a case in which the target CC is selected from an SCell will be disclosed.
[0564] After the processes of steps ST2400 to ST2402 are performed, the processes of steps ST1401 to ST1416 shown in FIG. 14 described above are performed, and further the processes of steps ST2300, ST2403, and ST2404 are performed. Next, in step ST2701, the cell judges whether or not the target CC determined in step ST2303 is included in the SCell. If the cell judges in step ST2701 that the target CC determined in step ST2303 is included in the SCell, it moves to step ST2312. If the cell judges in step ST2701 that the target CC determined in step ST2303 is not included in the SCell, it moves to step ST2702.
[0565] In Step ST2702, the cell executes access control when changing the PCell. As specific examples of the access control, the following four (1) to (4) are disclosed.
[0566] (1) Executes access control when changing the PCell disclosed in embodiment 8. As a specific example, the processes of steps ST2405 to ST2311 shown in the above-mentioned FIG.
[0567] (2) Executes access control in changing the PCell disclosed in the first modification of the eighth embodiment. As a specific example, the processes of Step ST2405 to Step ST2502 shown in the above-mentioned FIG.
[0568] (3) Executes access control in changing the PCell disclosed in Modification 2 of Embodiment 8. As a specific example, the processes of Step ST2602 to Step ST2607 shown in the above-mentioned FIG.
[0569] (4) A combination of (1) to (3) above.
[0570] In addition to the effects of the eighth embodiment and the second modification of the eighth embodiment, the third modification of the eighth embodiment provides the following effects. In this modification, a control step is omitted, so that delays in control of the communication system can be prevented. Furthermore, the processing load of the base station can be reduced. Furthermore, low power consumption of the base station can be achieved.
[0571] Although the present modification has been described mainly in terms of a case where handover is used to change the PCell, the present modification can also be applied to a case where reconfiguration is used to change the PCell.
[0572] This variant can be used in combination with the above-mentioned embodiment 1, embodiment 2, variant 1 of embodiment 2, embodiment 3, embodiment 4, embodiment 5, variant 1 of embodiment 5, embodiment 6, embodiment 7, embodiment 8, and variant 1 of embodiment 8.
[0573] In LTE-A, carrier aggregation between eNB and RRH or between eNB and repeater is under consideration (see Non-Patent Document 1). Non-Patent Document 1 does not describe the relationship between eNB and RRH, or the relationship between CSG to which eNB and repeater belong and CSG to which mobile terminal belongs. Therefore, the operation of the communication system is not uniquely determined, and a problem occurs in which appropriate services cannot be provided.
[0574] To address the above problem, all of the embodiments including the modified examples can be applied to the cell (CC) of the present disclosure as a CC included in an eNB, a CC included in an RRH, or a CC included in a repeater. This makes it possible to improve communication speeds using carrier aggregation between an eNB and an RRH, or between an eNB and a repeater, while stabilizing the operation of the communication system and providing appropriate services.
[0575] Coordinated Multiple Point transmission and reception (CoMP) technology is being considered for LTE-A (see non-patent documents 6 and 7). CoMP is a technology that aims to expand the coverage of high data rates, improve throughput at cell edges, and increase system throughput by performing coordinated transmission or reception between multiple geographically separated points. CoMP is divided into downlink CoMP (DL CoMP) and uplink CoMP (UL CoMP).
[0576] Specific examples of multipoints, transmission points, or reception points under consideration include base stations (NB, eNB, HNB, HeNB), RRUs (Remote Radio Units), RREs (Remote Radio Equipment), RRHs (Remote Radio Heads), and relays. A unit (cell) that performs multipoint coordinated transmission is called a multipoint unit (multipoint cell), a multipoint coordinated transmission and reception technology cooperation set (CoMP cooperation set), or a multipoint coordinated transmission and reception technology transmission point (CoMP transmission point(s)).
[0577] Non-Patent Documents 6 and 7 do not describe the relationship between the CSG to which the multipoints belong and the CSG to which the mobile terminal belongs in the multipoint coordinated transmission and reception technology cooperation set. Therefore, the operation of the communication system is not uniquely determined, and a problem occurs in which appropriate services cannot be provided.
[0578] To address the above-mentioned problem, all of the embodiments including the modified examples can be applied to the cell (CC) of the present disclosure as a transmission point or a reception point in CoMP. This makes it possible to provide appropriate services while expanding the coverage of high data rates, improving throughput at cell edges, and increasing system throughput using coordinated multipoint transmission and reception technology.
[0579] Although the above embodiments have been described mainly with reference to the LTE-Advanced system, the communication system of the present disclosure can also be applied to other communication systems.
[0580] Although the present disclosure has been described in detail, the above description is illustrative in all respects and does not limit the present disclosure. It is understood that countless variations not illustrated can be assumed without departing from the scope of the present disclosure. [Explanation of symbols]
[0581] 71 mobile terminal device (UE), 72 base station device, 72-1 eNB, 72-2 Home-eNB, 73 MME / S-GW unit (MME unit), 74 HeNBGW, CC component carrier, DL downlink, UL uplink.
Claims
1. A communication system including a communication terminal device and a plurality of cells capable of wireless communication between the communication terminal device, In a situation where a connection is established between a primary cell, which is one of the plurality of cells, and the communication terminal device, The communication terminal device determines whether a connection to a candidate cell that is a candidate for a secondary cell that is a cell capable of wireless communication in parallel with the primary cell is possible, and notifies the primary cell of the determination result using an RRC (Radio Resource Control) message; A communication system characterized in that the primary cell sets the candidate cell as the secondary cell when the communication terminal device notifies the primary cell of a determination that connection to the candidate cell is possible.
2. The candidate cell is a specific subscriber cell to which the connectable communication terminal device is identified, In a state where a connection is established between the primary cell and the communication terminal device, the candidate cell notifies the communication terminal device of specific subscriber information, which is information about a specific subscriber of the candidate cell; 2. The communication system according to claim 1, wherein the communication terminal device determines whether or not connection to the candidate cell is possible based on the specific subscriber information notified from the candidate cell.
3. The specific subscriber information is identification information for identifying a specific subscriber group that can use the candidate cell, The communication system according to claim 2, characterized in that the communication terminal device determines whether it is possible to connect to the candidate cell by determining whether it belongs to the specific subscriber group identified from the specific subscriber information.
4. A communication terminal device and a plurality of cells capable of wireless communication between the communication terminal device and the communication terminal device, A communication terminal device in a communication system in which a connection is established between a primary cell that is one of the plurality of cells and the communication terminal device, A communication terminal device characterized in that it determines whether a connection to a candidate cell that is a candidate for a secondary cell that is a cell capable of wireless communication in parallel with the primary cell is possible, and notifies the primary cell of the determination result using an RRC (Radio Resource Control) message.
5. A communication terminal device and a plurality of cells capable of wireless communication between the communication terminal device and the communication terminal device, In a situation where a connection is established between a primary cell that is one of the plurality of cells and the communication terminal device, the communication terminal device determines whether a connection to a candidate cell that is a candidate for a secondary cell that is a cell capable of wireless communication in parallel with the primary cell is possible, and notifies the primary cell of the determination result using an RRC (Radio Resource Control) message, A primary cell characterized in that, when the communication terminal device notifies the communication terminal device of a judgment result that connection to the candidate cell is possible, the primary cell sets the candidate cell as the secondary cell.
Citation Information
Patent Citations
Multi-carrier operational modes in wireless communications protocol, method of initializing a mobile station in order to prepare for multi-carrier operation in same, and carrier management method in same
WO2010129223A2
