Co-BCCH Introduction

What is Co-BCCH?
Co-BCCH: Common BCCH Cell, also called GSM900&DCS1800, Multi-band cell;
Based on Enhanced Concentric Cell Algorithm;
Two layers in a cell: UL (900M) and  OL (1800M);
The UL covers the whole cell area, The OL may not match the UL coverage area;
UL manages BCCH, SDCCH,PDCH and TCH channels, while OL only manages the TCH channels

Why Co-BCCH?
Improve capability:
    UL and OL share the BCCH, SDCCH, PDCH, and the TCH     channels will be increased accordingly
Frequency restrict:
    The frequency resource doesn’t support high     configuration, as in VNP totally we have 42 P-GSM     frequency, maximum support S4/4/4
Simplify network structure:
    Reduce number of cells in the network
    Reduce number of Location Area Codes
    Reduce number of neighboring cells
    Simplify multi-layer network into one layer network

Carrier Aggregation Band Combinations – 3GPP Releases 10 and 11

CA enables the sharing of spectrum across multiple spectrum channels (component carriers) and multiple bands. CA can be implemented with both FDD and TDD spectrum. It can be intra-band using spectrum in the same band that is either contiguous or non-contiguous. Or, CA can involve the combined use of inter-band of spectrum in different bands. While CA makes possible the combination of 5x20MHz carriers across 5 spectrum bands, current activity – both in standards bodies and from service providers – centers on CA with single band or dual band scenarios.

According to Third Generation Partnership Project (3GPP) Releases 10 and 11, there is an array of band combinations now specified for LTE-A CA as shown in Table I, below.

Table 1: Carrier Aggregation Band Combinations – 3GPP Releases 10 and 11

Source: 3GPP, 2013

There is a significant omission in the spectrum band combinations detailed in Table 1, namely, options for CA with the Asia Pacific (APT700) MHz band plan, which is now widely adopted across the Asia Pacific region and by a growing pool of service providers in Latin America. However, this issue, along with the addition of multiple CA band configurations are being addressed as part of the current 3GPP Release 12 agenda, as detailed in Table 2, below.

Table 2: Carrier Aggregation Band Combinations – 3GPP Release 12

Source: 3GPP, 2013

Candidate spectrum bands for CA vary by region, with service providers in the US primarily focusing on combining 700MHz spectrum in either Band 12, 13 or 17 with AWS spectrum. Canadian operators are expected to follow the same path once 700MHz (based on the US band plan) is awarded next year. Although not reflected in Table 2, 3GPP Release 12 also includes work items for CA 3-band implementations across the North American bands – 2, 4, 5, 13, 17 and 30. In the United States, Sprint will initially focus on CA within the 2600MHz TDD. In Canada, Rogers is also looking to CA with its AWS and 2600MHz spectrum holdings.

European CA activities are focused on different combinations of spectrum across the 800MHz, 1800MHz and 2600MHz FDD bands. 1800MHz combined with 2600MHz FDD spectrum is also of interest to operators in the Asia Pacific. Service providers in the region will also examine sharing with 700MHz as it is progressively released across the region. This is also the case for service providers in Latin America. 3GPP Release 12 includes a work item for CA in the 1800MHz band with the APT700MMhz band. As shown in Tables 1 and 2, 3GPP releases also account for country specific band allocations such as in Japan, China and South Korea.

The 3GPP CA work item lists are also devoid of options for TDD-CA, other than in single band mode. While CA combining both FDD and TDD spectrum will eventuate in the longer term, CA TDD deployments will initially focus on intra-band deployments. This is made possible as, unlike FDD spectrum licenses, service provider TDD holdings are generally based on larger bandwidth (MHz) allocations (i.e. 2x20MHz) capable of supporting LTE-A delivery.

SIB12: CMAS notification

• contains a CMAS notification
• CMAS notifications carry high emerygency situations and is defined for three catagories:

  -Presiential Alerts (President of a geographical location can send alerts)

  -Threat Alerts (Tornado/Hurricane alerts)

  -AMBER Alerts (Child abduction, endangered situation)

• introduced in Release9

Signalling radio bearer: N/A
RLC-Mode: TMLogical channel: BCCH
Direction: E‑UTRAN to UE

Important contents of SystemInformationBlockType12
messageIdentifier
serialNumber
warningMessageSegmentType
warningMessageSegmentNumber
warningMessageSegment
dataCodingScheme

Field Descriptions:

messageIdentifier	Identifies the source and type of CMAS notification
serialNumber	Identifies variations of a CMAS notification
warningMessageSegmentType	Indicates whether the included CMAS warning message segment is the last segment or not
warningMessageSegmentNumber	Segment number of the CMAS warning message segment contained in the SIB. A segment number of zero corresponds to the first segment, one corresponds to the second segment, and so on
warningMessageSegment	Carries a segment of the Warning Message
dataCodingScheme	Identifies the alphabet/coding and the language applied variations of a CMAS notification

SIB11: ETWS secondary notification

•  contains an ETWS secondary notification

Signalling radio bearer: N/A
RLC-Mode: TM
Logical channel: BCCH
Direction: E‑UTRAN to UE

Important contents of SystemInformationBlockType11
messageIdentifier
serialNumber
warningMessageSegmentType
warningMessageSegmentNumber
warningMessageSegment
dataCodingScheme

Field Descriptions:

messageIdentifier	Identifies the source and type of ETWS notification (earthquake, tsunami warning, any emergency or test message)
serialNumber	Identifies variations of an ETWS notification. -uses various mechanisms to alert the user (display message, play a tone or vibrate, location where the message is applicable, also contains an update number which specifies whether a change is in the message content or not)
warningMessageSegmentType [last/not last]	Indicates whether the included ETWS warning message segment is the last segment of the complete segment or not
warningMessageSegmentNumber	# allows oedering of the message segments # Segment number of the ETWS warning message segment contained in the SIB. A segment number of zero corresponds to the first segment, one corresponds to the second segment, and so on
warningMessageSegment	carries actual segment of the message
dataCodingScheme	Identifies the alphabet/coding and the language applied variations of an ETWS notification

SIB10: ETWS primary notification

• contains an ETWS primary notification

Signalling radio bearer: N/A
RLC-Mode: TM
Logical channel: BCCH
Direction: E‑UTRAN to UE

Important contents of SystemInformationBlockType10

messageIdentifier
serialNumber
warningType
warningSecurityInfo


Field Descriptions:

messageIdentifier	Identifies the source and type of ETWS notification (earthquake, tsunami warning, any emergency or test message)
serialNumber	Identifies variations of an ETWS notification. -uses various mechanisms to alert the user (display message, play a tone or vibrate, location where the message is applicable, also contains an update number which specifies whether a change is in the message content or not)
warningType	# Identifies the warning type of the ETWS primary notification (earthquake, tsunami, etc.) and # provides information on emergency user alert and UE popup
warningSecurityInfo	# is optional, only applied when security is applied # Provides security information for the ETWS notification