hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.44.2 Attributes | Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
localAddress
M
M
M
-
M
remoteAddress
M
M
M
-
M |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.44.3 Attribute constraints | Name
Definition
localAddress CM Support Qualifier
The condition is “MAP over SIGTRAN is supported”.
remoteAddress CM Support Qualifier
The condition is “MAP over SIGTRAN is supported”. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.45 EP_NLS | |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.45.1 Definition | This IOC represents the NLs interface between AMF and LMF, which is defined in 3GPP TS 23.501[3]. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.45.2 Attributes | Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
localAddress
M
M
M
-
M
remoteAddress
M
M
M
-
M |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.46 EP_NLG | |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.46.1 Definition | This IOC represents the NLg interface between AMF and GMLC, which is defined in 3GPP TS 23.501[3]. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.46.2 Attributes | Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
localAddress
M
M
M
-
M
remoteAddress
M
M
M
-
M |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.47 AMFSet | |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.47.1 Definition | This IOC represents the AMF Set which consists of some AMFs that serve a given area and Network Slice. For more information about the AMF Set, see 3GPP TS 23.501 [3]. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.47.2 Attributes | Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
pLMNIdList
M
M
M
-
M
tAClist
M
M
M
-
M
aMFSetId
M
M
M
-
M
nSSAI
CM
M
M
-
M
Attribute related to role
AMFRegion
M
M
M
-
M
AMFSetMemberList
M
M
M
-
M |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.47.3 Attribute constraints | Name
Definition
nSSAI CM Support Qualifier
The condition is “network slicing feature is supported”. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.48 AMFRegion | |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.48.1 Definition | This IOC represents the AMF Region which consists one or multiple AMF Sets. For more information about the AMF Region, see 3GPP TS 23.501 [3]. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.48.2 Attributes | Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
pLMNIdList
M
M
M
-
M
tAClist
M
M
M
-
M
aMFRegionId
M
M
M
-
M
nSSAI
CM
M
M
-
M
Attribute related to role
AMFSet
M
M
M
-
M |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.48.3 Attribute constraints | Name
Definition
nSSAI CM Support Qualifier
The condition is “network slicing feature is supported”. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.49 ExternalAMFFunction | |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.49.1 Definition | This IOC represents an external AMF functionality used in EN-DC. For more information about the AMF, see 3GPP TS 23.501 [3]. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.49.2 Attributes | Attribute name
Support Qualifier
isReadable
isWritable
isInvariant
isNotifyable
Id
M
M
-
-
M
pLMNIdList
M
M
M
-
M
aMFIdentifier
M
M
M
-
M |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.49.3 Attribute constraints | None. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.3.49.4 Notifications | The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions. |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.4 Attribute definitions | |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.4.1 Attribute properties | The following table defines the attributes that are present in several Information Object Classes (IOCs) of the present document.
Attribute Name
Documentation and Allowed Values
Properties
aMFIdentifier
The AMFI is constructed from an AMF Region ID, an AMF Set ID and an AMF Pointer. The AMF Region ID identifies the region, the AMF Set ID uniquely identifies the AMF Set within the AMF Region, and the AMF Pointer uniquely identifies the AMF within the AMF Set. (Ref. 3GPP TS 23.003 [4])
type: Integer
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
allowedValues: N/A
isNullable: False
aMFSetId
It represents the AMF Set ID, which is uniquely identifies the AMF Set within the AMF Region.
allowedValues: defined in subclause 2.10.1 of 3GPP TS 23.003 [4].
type: Integer
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
allowedValues: N/A
isNullable: False
aMFSetMemberList
It is the list of DNs of AMFFunction instances of the AMFSet.
allowedValues: N/A
type: DN
multiplicity: 1
isOrdered: N/A
isUnique: True
defaultValue: None
isNullable: False
aMFRegionId
It represents the AMF Region ID, which identifies the region.
allowedValues: defined in subclause 2.10.1 of 3GPP TS 23.003 [4].
type: Integer
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
allowedValues: N/A
isNullable: False
localAddress
Local address including IP address used for initialization of the underlying transport.
IP address can be an IPv4 or an IPv6 address.
type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False
remoteAddress
Remote address including IP address used for initialization of the underlying transport.
IP address can be an IPv4 or an IPv6 address.
type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
isNullable: False
nfProfileList
It is a set of NFProfile(s) to be registered in the NRF instance. NFProfile is defined in 3GPP TS 29.510 [10].
type: <<dataType>>
multiplicity: *
isOrdered: N/A
isUnique: N/A
defaultValue: None
allowedValues: N/A
isNullable: False
nSIIdList
It is a set of NSI Id. The NSI ID is defined in subclause 6.1.6.2.8 of 3GPP TS 29.531 [11].
type: String
multiplicity: *
isOrdered: N/A
isUnique: N/A
defaultValue: None
allowedValues: N/A
isNullable: False
nSSAI
It represents the types of NSSAI the managed object is capable of supporting, NSSAI is a set of S-NSSAI(s), an S-NSSAI is comprised of a SST (Slice/Service type) and an optional SD (Slice Differentiator) field, (Ref. 3GPP TS 23.003 [4]).
type: <<dataType>>
multiplicity: *
isOrdered: N/A
isUnique: N/A
defaultValue: None
allowedValues: N/A
isNullable: False
pLMNIdList
It is a list of PLMN-Id, PLMN-Id= Mobile Country Codes (MCC)|| Mobile Network Codes(MNC) (Ref. 3GPP TS 23.003 [4])
allowedValues:
A list of at most six entries of PLMN Identifiers. The PLMN Identifier is composed of a Mobile Country Code (MCC) and a Mobile Network Code (MNC).
type: Integer
multiplicity: 1..*
isOrdered: N/A
isUnique: N/A
defaultValue: None
allowedValues: N/A
isNullable: False
sBIFQDN
It is used to indicate the FQDN of the registered NF instance in service-based interface, for example, NF instance FQDN structure is:
nftype<nfnum>.slicetype<sliceid>.mnc<MNC>.mcc<MCC>.3gppnetwork.org
type: String
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
allowedValues: N/A
isNullable: False
sBIServiceList
It is used to indicate the all supported NF services registered on service-based interface.
type: String
multiplicity: *
isOrdered: N/A
isUnique: N/A
defaultValue: None
allowedValues: N/A
isNullable: False
tACList
It is the list of Tracking Area Code (either legacy TAC or extended TAC) where the represented management function serving.
allowedValues:
Legacy TAC and Extended TAC are defined in clause 9.3.3.10 of TS 38.413 [12].
type: Integer
multiplicity: 1..*
isOrdered: N/A
isUnique: N/A
defaultValue: None
allowedValues: N/A
isNullable: False
weightFactor
The weight factor is typically set according to the capacity of local node (AMF) relative to other nodes in the same type. And it is used to achieve load balancing among a set of same type of network functions. (Ref. 3GPP TS 23.501 [3])
type: Integer
multiplicity: 1
isOrdered: N/A
isUnique: N/A
defaultValue: None
allowedValues: N/A
isNullable: False |
d3ac8d6aa3347ad7b01f9ee2550c87ae | 28.543 | 4.5 Common notifications | 5 Solution Set
This specification defines the following 3GPP 5GC NRM Solution Set definitions:
- JSON based 3GPP 5GC NRM Solution Set (Annex A).
Annex A (normative):
JSON definitions
A.1 General
This annex contains the JSON definitions for the 5GC NRM, in accordance with 5GC NRM information model definitions specified in clause 4.
A.2 Architectural features
A.3 Mapping
A.4 Solution Set definitions
A.4.1 JSON definition structure
A.4.2 Graphical representation
A.4.3 JSON schema "ngcNrm.json"
{
{
"info": {
"title": "3GPP 5GC NRM JSON Solution Set",
"description": "JSON based solution set definitions for 5GC NRM",
"version": "1.0.0"
},
"definitions": {
"description": "attribute definitions",
"aMFIdentifier": {
"type": "object",
"description": "AMFIdentifier comprise of amfRegionId, amfSetId and amfPointer",
"properties": {
"amfRegionId": {
"$ref": "#/definitions/AmfRegionId"
},
"amfSetId": {
"$ref": "#/definitions/AmfSetId"
},
"amfPointer": {
"$ref": "#/definitions/AmfPointer"
}
}
},
"AmfRegionId": {
"type": "string",
"description": "AmfRegionId is defined in TS 23.003"
},
"AmfSetId": {
"type": "string",
"description": "AmfSetId is defined in TS 23.003"
},
"AmfPointer": {
"type": "string",
"description": "AmfPointer is defined in TS 23.003"
},
"amfSetMemberList": {
"type": "array",
"description": "List of DNs of AMF",
"items": {
"type": "string",
"description": "Identification of managed function."
}
},
"nFProfileList": {
"type": "array",
"description": "List of NF profile",
"items": {
"$ref": "#/definitions/NFProfile"
}
}
"NFProfile": {
"type": "object",
"description": "NF profile stored in NRF, defined in TS 29.510",
"properties": {
"nFInstanceId": {
"type": "string",
"description": "uuid of NF instance"
}
"nFType": {
"$ref": "#/definitions/NFType"
},
"nFStatus": {
"$ref": "#/definitions/NFStatus"
},
"plmn": {
"$ref": "#/definitions/PlmnId"
},
"sNssais": {
"type": “array”,
"item": {
"$ref": "#/definitions/Snssai"
}
}
"fqdn": {
"$ref": "#/definitions/Fqdn"
},
"interPlmnFqdn": {
"$ref": "#/definitions/Fqdn"
},
"ipv4Addresses": {
"type": “array”,
"item": {
"$ref": "#/definitions/Ipv4Addr"
}
},
"ipv6Addresses": {
"type": “array”,
"item": {
"$ref": "#/definitions/Ipv6Addr"
}
},
"ipv6Prefixes": {
"type": “array”,
"item": {
"$ref": "#/definitions/Ipv6Prefix"
}
},
"capacity": {
"$ref": "#/definitions/Capacity"
},
"udrInfo": {
"$ref": "#/definitions/UdrInfo"
},
"amfInfo": {
"$ref": "#/definitions/amfInfo"
},
"smfInfo": {
"$ref": "#/definitions/SmfInfo"
},
"upfInfo": {
"$ref": "#/definitions/UpfInfo"
},
"nfServices": {
"type": “array”,
"item": {
"$ref": "#/definitions/NFService"
}
}
}
},
"NFService": {
"type": "object",
"description": "NF Service is defined in TS 29.510",
"properties": {
"serviceInstanceId": {
"type": "string",
},
"serviceName": {
"type": "string",
},
"version": {
"type": "string",
},
"schema": {
"type": "string",
},
"fqdn": {
"$ref": "#/definitions/Fqdn"
},
"interPlmnFqdn": {
"$ref": "#/definitions/Fqdn"
},
"ipEndPoints": {
"type": "array",
"item": {
"$ref": "#/definitions/IpEndPoint"
}
},
"apiPrfix": {
"type": "string",
},
"defaultNotificationSubscriptions": {
"type": “array”,
"item": {
"$ref": "#/definitions/DefaultNotificationSubscriptions"
}
},
"allowedPlmns": {
"type": "array",
"item": {
"$ref": "#/definitions/PlmnId"
}
},
"allowedNfTypes": {
"type": "array",
"item": {
"$ref": "#/definitions/NFType"
}
},
"allowedNssais": {
"type": "array",
"item": {
"$ref": "#/definitions/Snssai"
}
},
"capacity": {
"$ref": "#/definitions/Capacity"
},
"supportedFeatures": {
"$ref": "#/definitions/SupportedFeatures"
}
}
},
"NFType": {
"type": "string",
"description": " NF name defined in TS 23.501",
"enum": [
"NRF",
"UDM",
"AMF",
"SMF",
"AUSF",
"NEF",
"PCF",
"SMSF",
"NSSF",
"UDR",
"LMF",
"GMLC",
"5G_EIR",
"SEPP",
"UPF”,
"N3IWF",
"AF",
"UDSF”,
"DN"
]
},
"Fqdn": {
"type": "string"
},
"IpEndPoint": {
"type": "object",
"properties": {
"ipv4Address": {
"$ref": "#/definitions/Ipv4Addr"
},
"ipv6Address": {
"$ref": "#/definitions/Ipv6Addr"
},
"ipv6Prefix": {
"$ref": "#/definitions/Ipv6Prefix"
},
"transport": {
"$ref": "#/definitions/TransportProtocol"
},
"port": {
"type": "integer"
}
}
},
"UdrInfo": {
"type": "object",
"properties": {
"supiRanges": {
"type": "array",
"items": {
"$ref": "#/definitions/SupiRange"
}
}
}
},
"SupiRange": {
"type": "object",
"properties": {
"start": {
"type": "string"
},
"end": {
"type": "string"
},
"pattern": {
"type": "string"
}
}
},
"AmfInfo": {
"type": "object",
"properties": {
"amfSetId": {
"$ref": "#/definitions/AmfSetId"
}
}
},
"SmfInfo": {
"type": "object",
"properties": {
"dnnList": {
"type": "array",
"items": {
"$ref": "#/definitions/Dnn"
}
}
}
},
"UpfInfo": {
"type": "object",
"properties": {
"sNssaiUpfInfoList": {
"type": "array",
"items": {
"$ref": "#/definitions/SnssaiUpfInfoItem"
}
}
}
},
"SnssaiUpfInfoItem": {
"type": "object",
"properties": {
"sNssai": {
"$ref": "#/definitions/Snssai"
}
"dnnUpfInfoList": {
"type": "array",
"items": {
"$ref": "#/definitions/DnnUpfInfoListInfo"
}
}
}
},
"DnnUpfInfoItem": {
"type": "object",
"properties": {
"dnn": {
"$ref": "#/definitions/Dnn"
}
}
},
"DefaultNotificationSubscription": {
"type": "object",
"properties": {
"notificationType": {
"$ref": "#/definitions/NotificationType"
},
"callbackUri": {
"$ref": "#/definitions/Uri"
},
"n1MessageClass": {
"$ref": "#/definitions/N1MessageClass"
}
"n2InformationClass": {
"$ref": "#/definitions/n2InformationClass"
}
}
},
"NotificationType": {
"type": "string",
"description": "any of enumrated value",
"enum": [
"N1_MESSAGES",
"N2_INFORMATION",
"LOCATION_NOTIFICATION"
]
},
"TranportProtocol": {
"type": "string",
"description": "any of enumrated value",
"enum": [
"TCP"
]
},
"NFStatus": {
"type": "string",
"description": "any of enumrated value",
"enum": [
"REGISTERED",
"SUSPENDED"
]
},
"NFRegistrationData": {
"type": "object",
"properties": {
"heartBeatTimer": {
"type": "integer"
},
"nfProfile": {
"$ref": "#/definitions/NFProfile"
}
}
},
"nSIIdList": {
"type": "array",
"items": {
"nSIId": {
"$ref": "#/definitions/NSIId"
}
}
},
"NSIId": {
"type": "string",
"description": "NSI Id is defined in TS 29.531"
},
"plmnIdList": {
"type": "array",
"items": {
"plmnId": {
"$ref": "#/definitions/PlmnId"
}
}
},
"PlmnId": {
"type": "object",
"properties": {
"mcc": {
"$ref": "#/definitions/Mcc"
},
"mnc": {
"$ref": "#/definitions/Mnc"
}
}
},
"Mcc": {
"type": "string",
},
"Mnc": {
"type": "string",
},
"Tac": {
"type": "string",
},
"NrCellId": {
"type": "string",
},
"nssai": {
"type": "array",
"item": {
"$ref": "#/definitions/Snssai"
}
},
"Snssai": {
"type": "object",
"properties": {
"sst": {
"$ref": "#/definitions/Sst"
},
"sd": {
"type": "string"
}
}
},
"Sst": {
"type": "integer",
},
"sbiFqdn": {
"$ref": "#/definitions/Fqdn"
},
"sBIServiceList": {
"type": "array",
"item": {
"$ref": "#/definitions/NFService"
}
},
"tacList": {
"type": "array",
"item": {
"$ref": "#/definitions/Tac"
}
},
"weightFactor": {
"type": "integer"
}
}
}
Annex B (informative):
Change history
Change history
Date
Meeting
TDoc
CR
Rev
Cat
Subject/Comment
New version
2017-12
SA5#116
S5-176539
Skeleton of TS
0.0.0
2018-02
SA5#117
S5-181244
S5-181440
S5-181441
Add content of scope.
Add class diagrams for 5GC.
Add class definitions for 5G
Some editorial fixes.
0.1.0
2018-04
SA5#118
S5-182398
S5-182492
S5-182493
S5-182494
S5-182495
S5-182496
S5-182497
S5-182498
S5-182499
S5-182500
Modify 5GC NF NRM diagrams.
Add IM definitions for NSSF and NRF,
Add IM definitions for AMF Set.
Add IM definitions for SMF and UPF.
Add IM definitions for AUSF, UDM, UDR and 5G-EIR.
Add IM definitions for PCF and NWDAF.
Add IM definitions for UDSF.
Add IM definitions for N3IWF.
Add IM definitions for SEPP.
Add IM definitions for SMSF and LMF.
0.2.0
2018-05
SA5#119
S5-183539
S5-183540
S5-183541
Editor's note cleanup and editorial changes
Add IM definitions for N6 interface
Add JSON definitions for 5GC modelling
Some editorial fixes.
0.3.0
2018-06
SA#80
SP-180412
Presented for information
1.0.0
3GPP TSG-SA Meeting #80 Tdoc SP-180412
La Jolla, US, 11-15 Jun. 2018
Title: Presentation of Specification/Report to TSG:
TS 28.543, Management and orchestration of networks and network slicing; 5G Core Network (5GC) Network Resource Model (NRM); Stage 2 and stage 3, Version 1.0.0
Source: SA5
Document for: Information
Abstract of document:
The document specifies the Information Model definitions and Solution Set definitions for 5G Core Network (5GC) network resource model, to fulfil the requirements identified in 3GPP TS 28.542. The Information Model definitions define the semantics and behaviour of information object class attributes and relations visible on the management interfaces in a protocol and technology neutral way. And Solution Set definitions define one or more solution set(s) with specific protocol(s) according to the Information Model definitions.
Changes since last presentation to SA Meeting:
None (first presentation to SA).
Outstanding Issues:
The stage 3 work has just been started and need further improvements.
Contentious Issues:
None.
Change history of this document:
1999-11-17: original issue
2007-09-06: removal of references to Working Groups; bring names of TSGs up to date; correction of typo
2015-01-06: adds tdoc header & removes redundant information below |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 1 Scope | The present document constitutes the output of the initial evaluation phase for the work item “LTE RAN Enhancements for Diverse Data Applications” (LTE_eDDA). The document captures agreements and descriptions related to the evaluation methodology used, descriptions of enhancement proposals and their evaluation results, and conclusions and recommendations for further work within the scope of the LTE_eDDA work item. |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[x] <doctype> <#>[ ([up to and including]{yyyy[-mm]|V<a[.b[.c]]>}[onwards])]: "<Title>". |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 3 Definitions, symbols and abbreviations | |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 21.905 [x] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [x].
<example>: <text used to clarify abstract rules by applying them literally>. |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
<symbol> <Explanation> |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [x] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [x].
<ACRONYM> <Explanation> |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 4 Evaluation Methodology | Enhancement proposals considered as part of the LTE_eDDA work item are likely to exhibit some diversity in their focus on different application/traffic situations, and to tackle different areas of the system and its optimisation.
In order to provide the necessary degree of commonality and comparability between company results when evaluating these proposals, an evaluation framework has been established encompassing:
• Evaluation guidelines(detailed in sub-clause 4.1)
• The types of traffic to be evaluated (detailed in sub-clause 4.2) |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 4.1 Evaluation Guidelines | |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 4.1.1 Traffic Sources | The following alternatives have been identified to generate source traffic for the purposes of evaluation:
Traffic Trace:
Data traffic or packets captured from live systems or apparatus running one or more applications of interest
Synthetic Models:
Abstract modelling of application-level and/or user behaviours in order to faithfully represent or emulate data traffic that would typically be observed from a live running application
Statistical Models:
Generation of data traffic or packets according to random processes governed by parameters that are themselves derived from statistics observed from one or more live running applications
• Companies may use either trace-based or synthetic/statistical model-based approaches to generate source traffic
• For trace based approaches:
◦ Reasonable disclosure of the trace capture environment is required (sufficient to enable reproduction of a similar traffic scenario by another company). This should include for example, information relating to the access technologies used during the capture, any pertinent configuration details therein, the data rates of involved links, the nature of running or open applications, the degree of user interactivity with the device and the captured protocol layer
◦ Key statistics of the trace shall be provided— to include at least the distributions of inter-arrival times, and packet sizes, and information regarding data rates
◦ Provision of the actual trace is optional
• For model-based approaches:
◦ Disclosure of the model and its parameters is required
◦ Some validation of the model (i.e. verifying its alignment with real-world traces, statistics or behaviours) shall be provided
• To help improve alignment between company evaluations, the guideline traffic scenarios of sub-clause 4.2 have been created. Companies are encouraged to use traces or models whose statistical properties conform to (or are closely consistent with) those listed for the guideline traffic scenarios, although the use of other traffic scenarios for evaluation purposes is not precluded. |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 4.1.2 Simulation Environment | • For the purposes of simulation, a suitable abstraction of the physical layer is permitted (it need not be explicitly modelled). Where appropriate, basic HARQ functionality at the sub-frame level should be included.
• Depending on the nature of the proposal, some evaluations may require that TCP is modelled. Evaluations shall state whether or not this has been performed and provide reasons. TCP modelling may apply to either traffic models or to trace-based traffic. A simplified TCP model may be used, sufficient to capture slow-start and congestion avoidance effects.
• When submitting proposals, companies should consider whether there are any potential impacts to mobility. If significant mobility aspects are identified, evaluations regarding those impacts should also be provided.
• Where appropriate, assumptions on how the network’s RRC state control mechanisms operate shall be stated |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 4.1.3 Output Metrics | Metrics of interest are dependent on the nature of a particular proposal. However, the following guidelines regarding output metrics are recommended. It is expected that wherever there is perceived to be a significant impact to one of the areas covered by these metrics, the associated metric(s) will be provided and the guidelines followed.
• UE power consumption (for the radio communications part)
◦ This may further comprise (or be related to) associated metrics such as active time and active time utilisation
◦ The power consumption effects of RRC state transitions and mobility should be taken into account
◦ Power consumption may be expressed in absolute terms or relative to a baseline power consumption value. Depending on the particular proposal, the baseline power consumption value may be for example that of RRC_IDLE or that of the system with/without implementation of a particular enhancement
◦ Parameters that affect power consumption and which are configured by the network shall be stated, along with any associated assumptions
◦ To help improve alignment and to help derive baseline values, the following relative power consumption values shall be used for one sub-frame unit of transmit or receive operation. For FDD both transmit and receive functions may take place at the same time (and their power contributions are hence summed), whereas for TDD these occur at separate times
Table 4.1.3-1: Reference values for UE power consumption
Function
Relative UE Power Consumption
Tx sub-frame
[TBD]
Editors Note: possibly a function of Tx power, or two simplified mean values could be used, one for Tx of control (e.g. PUCCH) and one for Tx of data (PUSCH)
Rx sub-frame (PDCCH only)
[TBD]
Rx sub-frame (PDCCH+PDSCH)
[TBD]
DRX sub-frame
[TBD]
• Overheads and Signalling
◦ Signalling costs should be evaluated
◦ System resource overheads (e.g. in terms of number or fraction of assigned/used/reserved control channel resources and RBs) should be considered
◦ Effects on RRC state transition frequency, on handover frequency and on the average time spent in connected mode (vs. idle) should be reported where appropriate
• User Visible Metrics / QoS
◦ Latency: Impacts or benefits to latency shall be provided, in the form of latency distributions, percentiles or bounds.
◦ Throughput: Impacts or benefits to throughput shall be provided, in the form of throughput distributions, percentiles or bounds.
◦ The data unit size (e.g. web-page, IP datagram, MAC PDU etc..) used to represent the latency and throughput metrics and distributions shall be stated
◦ If the proposal relates to differing levels of QoS, metrics associated with each of the different QoS levels shall be provided |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 4.2 Traffic Scenarios and Characterisation | The following traffic scenarios provide the primary focus for the evaluations. The emphasis is on smartphone and tablet device types (rather than PCs).
Table 4.2-1: Traffic scenarios
Label
Traffic Scenario
Description
Top priority
A
Background Traffic
Traffic from an unattended phone with applications not in “active phase” (i.e. not including email retrieval, no IM sending etc…)
B
IM
Instant Messaging. Includes IM background traffic.
Non-top-priority
C
Gaming
Use of on-line interactive games
D
Interactive Content Pull
User-interactive web browsing, online maps, social network browsing, application store / music store browsing and other similar content pull by the user
E
HTTP Video Streaming
Segment-oriented transfer of video media
A statistical characterisation of each of these traffic scenarios is provided in sub-clauses 4.2.1 through 4.2.5 respectively. |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 4.2.1 A) Background Traffic | Editor’s note: pending outcome of RAN2 email discussion on packet inter-arrival and packet size CDFs |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 4.2.2 B) Instant Messaging | Editor’s note: pending outcome of RAN2 email discussion on packet inter-arrival and packet size CDFs |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 4.2.3 C) Gaming | Editor’s note: pending outcome of RAN2 email discussion on packet inter-arrival and packet size CDFs |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 4.2.4 D) Interactive Content Pull | Editor’s note: pending outcome of RAN2 email discussion on packet inter-arrival and packet size CDFs |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 4.2.5 E) HTTP Video Streaming | Editor’s note: pending outcome of RAN2 email discussion on packet inter-arrival and packet size CDFs |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 5 Evaluation of existing EUTRAN functionality | Editor’s note: Intention is to include evaluations for existing functionality in Rel-8/9/10 |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 6 Proposals and Evaluations (new functionality) | Editor’s note: Intention is to describe proposals along with their evaluations within separate sub-clauses 6.1, 6.2, … etc… It may at a later stage be possible to re-structure this section such that similar proposals are logically grouped |
f5fd9ff51348f38f64d5c2b5cf01e495 | 36.832 | 7 Recommendations and Conclusions | Annex <A>:
<Annex title>
A.1 <Annex Heading>
Annex <X>:
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
2011-09
Initial draft version capturing the outcome of RAN2#75
---
0.0.0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 1 Scope | The present document is a technical report for Inter-band Carrier Aggregation under Rel-12 time frame. The purpose is to gather the relevant background information and studies in order to address Inter-band Carrier Aggregation requirements.
This TR covers relevant background information and studies in order to address Inter-band Carrier Aggregation requirements for the Rel-12 band combinations in table 1-1.
Table 1-1: Release 12 inter-band carrier aggregation combinations
WI code
WI title
Class
LTE_CA_B1_B7
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 7
A3
LTE_CA_B2_B4
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 4
A4
LTE_CA_B23_B29
LTE Advanced inter-band Carrier Aggregation of Band 23 and Band 29
A1
LTE_CA_B3_B26
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 26
A1
LTE_CA_B3_B19
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 19
A1
LTE_CA_B1_B8
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 8
A1
LTE_CA_B3_B28
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 28
A1
LTE_CA_B1_B26
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 26
A1
LTE_CA_B39_B41
LTE Advanced inter-band Carrier Aggregation of Band 39 and Band 41
A3
LTE_CA_B2_B12
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 12
A1
LTE_CA_B2_B13
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 13
A1
LTE_CA_B19_B21
LTE Advanced inter-band Carrier Aggregation of Band 19 and Band 21
A5
LTE_CA_B12_B25
LTE Advanced inter-band Carrier Aggregation of Band 12 and Band 25
A1
LTE_CA_B2_B5
LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 5
A1
LTE_CA_B1_B18
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 18
A1
LTE_CA_B7_B28
LTE Advanced inter-band Carrier Aggregation of Band 7 and Band 28
A1
LTE_CA_B5_B25
LTE Advanced inter-band Carrier Aggregation of Band 5 and Band 25
A1
LTE_CA_B1_B11
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 11
A5
LTE_CA_B8_B11
LTE Advanced inter-band Carrier Aggregation of Band 8 and Band 11
A5
LTE_CA_B5_B7
LTE Advanced inter-band Carrier Aggregation of Band 5 and Band 7
A1
LTE_CA_B1_B3
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 3
A3
LTE_CA_B1_B28
LTE Advanced inter-band Carrier Aggregation of Band 1 and Band 28
A2
LTE_CA_B4_B27
LTE Advanced inter-band Carrier Aggregation of Band 4 and Band 27
A1
LTE_CA_B3_B27
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 27
A1
LTE_CA_B8_B27
LTE Advanced inter-band Carrier Aggregation of Band 8 and Band 27
A3
LTE_CA_B3_B20_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 20
A1
LTE_CA_B7_B20_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 7 and Band 20
A1
LTE_CA_B41_B42
LTE Advanced inter-band Carrier Aggregation of Band 41 and Band 42
A5
LTE_CA_B5_B13
LTE Advanced inter-band Carrier Aggregation of Band 5 and Band 13
A3
LTE_CA_B7_B22
LTE Advanced inter-band Carrier Aggregation of Band 7 and Band 22
A5
LTE_CA_B2_B5_BWset
Additional bandwidth combination set for LTE Advanced inter-band Carrier Aggregation of Band 2 and Band 5
A1
The scope of the report has been further extended [6] to cover the 2 DL fallback modes for the 3 DL Carrier Aggregation combinations with single UL configuration. These 3 DL/1UL combinations are listed in table 1-2. In addition, the report also covers the LTE TDD-FDD joint operation including Carrier Aggregation combinations [7], captured in Table 1-3.
Table 1-2: Release 12 inter-band carrier aggregation combinations (3 DL/1UL)
WI code
WI title
LTE_CA_B2_B5_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 5 and Band 30
LTE_CA_B2_B29_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 2, Band 29 and Band 30
LTE_CA_B1_B5_B7
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 5 and Band 7
LTE_CA_B2_B12_B30
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 2, Band 12 and Band 30
LTE_CA_B1_B3_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 3 and Band 20
LTE_CA_B1_B7_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 7 and Band 20
LTE_CA_B7_B8_B20
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 7, Band 8 and Band 20
LTE_CA_B1_B18_B28
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 1, Band 18 and Band 28
LTE_CA_3DL_FB_BW
Additional bandwidth combinations for LTE Advanced inter-band Carrier Aggregation to support 3DL fallback
LTE_CA_B4_B7_B12
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) for Band 4, Band 7 and Band 12
Table 1-3: Release 12 inter-band carrier aggregation combinations (LTE TDD-FDD joint operation)
WI code
WI title
Class
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 1 and Band 41)
A3
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 1 and Band 42)
A3
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 3 and Band 40)
A3
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 8 and Band 40)
A1
LTE_CA_TDD_FDD
LTE TDD-FDD joint operation including Carrier Aggregation (Band 3 and Band 42)
A2
LTE_CA_B26_B41_B41
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 26, Band 41 and Band 41
-
LTE_CA_B3_B38
LTE Advanced inter-band Carrier Aggregation of Band 3 and Band 38
A3
LTE_CA_B19_B42_B42
LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) of Band 19, Band 42 and Band 42
A1
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications. |
389f9b67c003a620147a83200e3331ae | 36.851 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TR 30.007: “Guideline on WI/SI for new Operating Bands”
[3] 3GPP TR 36.850: “Inter-band Carrier Aggregation Technical Report (Release 11)”
[4] 3GPP TS 36.101: "E-UTRA UE radio transmission and reception"
[5] 3GPP TS 36.331: "E-UTRA UE RRC Protocol specification (Release 11)"
[6] RP-131633, “Way forward on 3DL/1UL WIs and TRs”, RAN4 Chairman (NSN), Busan, Korea, 3-6 Dec, 2013
[7] R4-142018, “TP for TR 36.851: Skeleton for TDD-FDD CA”, Nokia Corporation, San Jose del Cabo, Mexico, Mar 31st – 4th Apr, 2014
[8] 3GPP TR 36.853: “LTE Advanced 3 Band Carrier Aggregation (3DL/1UL) (Release 12)” |
389f9b67c003a620147a83200e3331ae | 36.851 | 3 Definitions, symbols and abbreviations | |
389f9b67c003a620147a83200e3331ae | 36.851 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
Carrier aggregation: Aggregation of two or more component carriers in order to support wider transmission bandwidths.
Channel bandwidth: The RF bandwidth supporting a single E-UTRA RF carrier with the transmission bandwidth configured in the uplink or downlink of a cell. The channel bandwidth is measured in MHz and is used as a reference for transmitter and receiver RF requirements.
Inter-band carrier aggregation: Carrier aggregation of component carriers in different operating bands.
NOTE: Carriers aggregated in each band can be contiguous or non-contiguous. |
389f9b67c003a620147a83200e3331ae | 36.851 | 3.2 Symbols | For the purposes of the present document, the following symbols apply:
FDL_low The lowest frequency of the downlink operating band
FDL_high The highest frequency of the downlink operating band
FUL_low The lowest frequency of the uplink operating band
FUL_high The highest frequency of the uplink operating band
ΔRIB Allowed reference sensitivity relaxation due to support for inter-band CA operation.
ΔTIB,c Allowed maximum configured output power relaxation due to support for inter-band CA operation, for serving cell c. |
389f9b67c003a620147a83200e3331ae | 36.851 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
A-MPR Additional Maximum Power Reduction
BS Base Station
CA Carrier Aggregation
CA_X-Y CA for band X and band Y where X and Y are the applicable E-UTRA operating band
CC Component Carriers
DL Downlink
ETC Extreme Temperature Conditions
E-UTRA Evolved UMTS Terrestrial Radio Access
FDD Frequency Division Duplex
IL Insertion Loss
IMD Intermodulation Distortion
PA Power Amplifier
REFSENS Reference Sensitivity power level
TDD Time Division Duplex
UE User Equipment
UL Uplink |
389f9b67c003a620147a83200e3331ae | 36.851 | 4 Background | The present document is a technical report for Inter-band Carrier Aggregation under Rel-12 time frame. It covers both the UE and BS side. The document is divided in two different parts:
- Common part: this part covers BS and UE specific which is band combination independent.
- Specific band combination part: this part covers each band combination and its specific issues independently from each other (i.e. one subclause is defined per band combination)
The specific band combination parts are independent and therefore, the working speed also differs. Annex A contains a list of all CA combinations covered in the present document as well as the status of each WI. The content of each specific combination part can be considered as finalized when the current status of the WI under Annex A is indicated as “Closed”.
4.1 TR Maintenance
A single company is responsible for introducing all approved TPs in the current TR, TR editor. However, it is the responsibility of the rapporteur of each WI to ensure that the TPs related to the WI have been implemented. |
389f9b67c003a620147a83200e3331ae | 36.851 | 5 Inter-band Carrier Aggregation: general part | 5.1 BS specific
<Text will be added.>
5.2 UE specific
<Text will be added.>
5.2.1 Class A1. Low-high band combination without harmonic relation between bands or intermodulation problem
<Text will be added.> |
389f9b67c003a620147a83200e3331ae | 36.851 | 5.2.2 Class A2. Low-high band combination with harmonic relation between bands | <Text will be added.>
5.2.3 Class A3. Low-low or high-high band combination without intermodulation problem (low order IM)
<Text will be added.> |
389f9b67c003a620147a83200e3331ae | 36.851 | 5.2.4 Class A4. Low-low, low-high or high-high band combination with intermodulation problem (low order IM) | <Text will be added.> |
389f9b67c003a620147a83200e3331ae | 36.851 | 5.2.5 Class A5. Combination except for A1 – A4 | <Text will be added.>
5.3 RRM specific
<Text will be added.>
5.3.1 Class A1. Low-high band combination without harmonic relation between bands or intermodulation problem
<Text will be added.> |
389f9b67c003a620147a83200e3331ae | 36.851 | 6 Inter-band Carrier Aggregation: band combination specific part | |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1 Class A1. Low-high band combination without harmonic relation between bands or intermodulation problem | |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.1 LTE Advanced Carrier Aggregation of Band 23 and Band 29 (1 UL) | Table 6.1.1-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_23-29
23
2000 MHz
–
2020 MHz
5, 10, 15, 20
2180 MHz
–
2200 MHz
5, 10, 15, 20
FDD
29
N/A
717 MHz
–
728 MHz
5, 10
6.1.1.1 List of specific combination issues
6.1.1.1.1 Channel bandwidths per operating band for CA
Table 6.1.1.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
Maximum aggregated bandwidth
[MHz]
Bandwidth Combination Set
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_23A-29A
23
Yes
Yes
Yes
Yes
30
0
29
Yes
Yes
Yes
23
Yes
Yes
20
1
29
Yes
Yes
Yes
NOTE: For the UE that signals support of any bandwidth combination set for carrier aggregation, the UE shall support all single carrier bandwidths for the constituent bands as defined in table 5.6.1-1 of TS 36.101 [4] when operating in single carrier mode.
6.1.1.1.2 Co-existence studies for CA_23-29
The 2nd and 3rd order harmonics and IMD products caused in the BS by transmitting of Band 23 and Band 29 DL carriers can be calculated as shown in table 6.1.1.1.2-1 below:
Table 6.1.1.1.2-1: Band 23 and Band 29 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
717
728
2180
2200
2nd order harmonics frequency range (MHz)
1434
1456
4360
4400
3rd order harmonics frequency range (MHz)
2151
2184
6540
6600
2nd order IMD products
(f2_low – f1_high)
(f2_high – f1_low)
(f2_low + f1_low)
(f2_high + f1_high)
IMD frequency limits (MHz)
1452
1483
2897
2928
3rd order IMD products
(f2_low – 2*f1_high)
(f2_high – 2*f1_low)
(2*f2_low – f1_high)
(2*f2_high – f1_low)
IMD frequency limits (MHz)
724
766
3632
3683
3rd order IMD products
(2*f1_low + f2_low)
(2*f1_high + f2_high)
(2*f2_low + f1_low)
(2*f2_high + f1_high)
IMD frequency limits (MHz)
3614
3656
5077
5128
3rd order IMD products
(f1_low – f2_high + f2_low)
(f1_high + f2_high – f2_low)
(f2_low – f1_high + f1_low)
(f2_high + f1_high – f1_low)
IMD frequency limits (MHz)
697
748
2169
2211
3rd order IMD products (with maximum channel bandwidth)
(f1_low – f2_BWmax)
(f1_high + f2_BWmax)
(f2_low – f1_BWmax)
(f2_high + f1_BWmax)
IMD frequency limits (MHz)
697
748
2170
2210
It can be seen from table 6.1.1.1.2-1 that the 2nd harmonics of Band 29 carriers may fall into the BS receive band of Bands 11 and 21, while the 2nd IMD products caused by BS supporting carrier aggregation of Band 23 and Band 29 may fall into the BS receive band of Band 21, and the 3rd IMD products may fall into the BS receive band of Bands 12, 17, 28, 43 and 44. Note that the calculation in table 6.1.1.1.2-1 (except the last row) assumes the BS is transmitting with the whole 20 MHz DL frequency of Band 23 and the whole 11 MHz DL frequency of Band 29. But even if the BS is only transmitting an up to 10 MHz DL in Band 29 as stated in the WIDS, the 3rd IMD products may still fall into the BS receive band of the Bands 12, 17, 28, 43 and 44 as shown in the last row in table 6.1.1.1.2-1.
It should be noted that Bands 11, 21, 28 and 44 are not intended for use in the same geographical area as Bands 23 and 29. Therefore, the focus here will be on the harmonics and IMD falling into Bands 12, 17 and 43.
With the performances of the current BS antenna system, transmit and receive path components, amplifiers, pre-distortion algorithms and filters, it is expected that the IMD interference generated within the Band 43 receiver would be well below the receiver noise floor eliminating the possibility of receiver desensitization, provided that Bands 23 and 29 BS transmitters do not share the same antenna with Band 43 BS receiver. However, the 3rd IMD products may still fall into the BS receive band of Bands 12 and 17, which is only 1 MHz away from Band 29 transmit band, and desensitize the receiver.
Therefore, it is recommended that Bands 23 and 29 BS transmitters should not share the same antenna with Band 12 or 17 BS receiver to prevent Band 12 or 17 BS receiver desensitization, or with Band 43 BS receiver unless the antenna path meets very stringent 3rd order PIM specification so that the PIM will not cause Band 43 BS receiver desensitization.
6.1.1.1.3 ∆TIB and ∆RIB values
For two simultaneous DL and one UL the TIB,c and RIB values are shown in table 6.1.1.1.3-1, and in table 6.1.1.1.3-2:
Table 6.1.1.1.3-1: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_23A-29A
23
0.3
29
N/A
Table 6.1.1.1.3-2: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_23A-29A
23
0
29
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.2 LTE Advanced Carrier Aggregation of Band 3 and Band 26 | Table 6.1.2-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_3-26
3
1710 MHz
–
1785 MHz
10, 15, 20
1805 MHz
–
1880 MHz
10, 15, 20
FDD
26
814 MHz
–
849 MHz
5, 10,15
859 MHz
–
894 MHz
5, 10, 15 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.2.1 List of specific combination issues | |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.2.1.1 Channel bandwidths per operating band for CA | Table 6.1.2.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
Bandwidth Combination Sets
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_3A-26A
3
Yes
Yes
Yes
Yes
0
26
Yes
Yes
Yes
3
Yes
Yes
1
26
Yes
Yes
NOTE: For the UE that signals support of any bandwidth combination set for carrier aggregation, the UE shall support all single carrier bandwidths for the constituent bands as defined in table 5.6.1-1 of TS 36.101 [4] when operating in single carrier mode. |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.2.1.2 Co-existence studies for CA_3-26 (1 UL/2 DL) | Table 6.1.2.1.2-1 summarizes frequency ranges where harmonics occur due to Band 3 or Band 26 for both UL and DL. It can be seen that UL harmonic frequencies of Band 3 and Band 26 does not locate within the receive bands of interest in the DL.
Table 6.1.2.1.2-1: Impact of UL/DL Harmonic Interference
2nd Harmonic
3rd Harmonic
2nd Harmonic
3rd Harmonic
Band
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
UL Low Band Edge
UL High Band Edge
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
DL Low Band Edge
DL High Band Edge
3
1710
1785
1805
1880
3420
3570
5130
5355
3610
3760
5415
5640
26
814
849
859
894
1628
1698
2442
2547
1718
1788
2577
2682
6.1.2.1.2.1 Co-existence studies for 1 UL/2 DL
The 2nd and 3rd order harmonics and IMD products caused in the BS by transmitting of Band 3 and Band 26 DL carriers can be calculated as shown in table 6.1.2.1.2.1-1 below:
Table 6.1.2.1.2-1: Co-existence studies for 1 UL/2 DL
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
859
894
1805
1880
2nd order harmonics frequency range (MHz)
1718
1788
3610
3760
3rd order harmonics frequency range (MHz)
2577
2682
5415
5640
2nd order IMD products
(f2_low – f1_high)
(f2_high – f1_low)
(f2_low + f1_low)
(f2_high + f1_high)
IMD frequency limits (MHz)
911
1021
2664
2774
3rd order IMD products
(f2_low – 2*f1_high)
(f2_high – 2*f1_low)
(2*f2_low – f1_high)
(2*f2_high – f1_low)
IMD frequency limits (MHz)
17
162
2716
2901
3rd order IMD products
(2*f1_low + f2_low)
(2*f1_high + f2_high)
(2*f2_low + f1_low)
(2*f2_high + f1_high)
IMD frequency limits (MHz)
3523
3668
4469
4654
3rd order IMD products
(f1_low – f2_high + f2_low)
(f1_high + f2_high – f2_low)
(f2_low – f1_high + f1_low)
(f2_high + f1_high – f1_low)
IMD frequency limits (MHz)
784
969
1770
1915
3rd order IMD products (with maximum channel bandwidth)
(f1_low – f2_BWmax)
(f1_high + f2_BWmax)
(f2_low – f1_BWmax)
(f2_high + f1_BWmax)
IMD frequency limits (MHz)
839
914
1790
1895
It can be seen from table 6.1.2.1.2.1-1 that the 2nd harmonics of BS transmitting in Bands 3 and 26 may fall into the BS receive band of Bands 3, 4, 9, 10 and 43, and the 3rd harmonics may fall into the BS receive band of Bands 38 and 41, while the 2nd IMD products may fall into the BS receive band of Bands 8 and 41, and the 3rd IMD products may fall into the BS receive band of Bands 2, 3, 5, 6, 8, 9, 13, 14, 18, 19, 20, 25, 26, 27, 33, 35, 37, 39, 42, 43 and 44. Note that the calculation in table 6.1.2.1.2.1-1 (except the last row) assumes the BS is transmitting with the whole 75 MHz DL frequency of Band 3 and the whole 35 MHz DL frequency of Band 26. If the BS is only transmitting up to 20 MHz DL in Band 3 and up to 15 MHz DL in Band 26 as stated in the WIDS, then the 3rd IMD products will not fall into the BS receive band of Band 3, 9, 13, 14,18, 27, 33, 37 or 44 as shown in the last row in table 6.1.2.1.2.1-1, and may only fall into the BS receive band of certain frequency range within Bands 5 and 26 under the transmit configurations shown in table 6.1.2.1.2.1-2 below.
Table 6.1.2.1.2.1-2: Band (3 + 26) BS transmit configurations with 3rd IMD within Bands 3 and 26 BS receive band
Band 26 DL channel bandwidth (MHz)
Lower edge of Band 26 DL frequency block (MHz)
Band 3 DL channel bandwidth (MHz)
Lower edge of IMD frequency limits (MHz)
5, 10 or 15
859 – 863.9
15
844 – 848.9
5, 10 or 15
859 – 868.9
20
839 – 848.9
On the other hand, if the BS is only transmitting up to 10 MHz DL in Band 3, i.e. 15 MHz and 20 MHz are not used, then there could not be 3rd IMD products within the BS receive band of Band 5 or 26. Moreover, only the highest 10 MHz frequency spectrum in Band 8 (905 – 915 MHz for UL and 950 – 960 MHz for DL) is allocated for mobile services in South Korea, thus the 2nd IMD products may only fall into the BS receive band of Band 8 frequency spectrum used in South Korea (905 – 915 MHz) under the transmit configurations shown in table 6.1.2.1.2.1-3 below.
Table 6.1.2.1.2.1-3: Band (3 + 26) BS transmit configurations with 2nd IMD within 905 – 915 MHz
Band 3 DL channel bandwidth (MHz)
Band 26 DL channel bandwidth (MHz)
Lower edge of Band 3 DL frequency block minus higher edge of Band 26 DL frequency block (MHz)
IMD frequency limits (MHz)
5, 10, 15 or 20
5, 10 or 15
≤ 915
911 – 915
And the 3rd IMD products may only fall into the BS receive band of Band 8 frequency spectrum used in South Korea (905 – 915 MHz) under the transmit configurations (with a 15 or 20 MHz DL in Band 3) shown in table 6.1.2.1.2.1-4 below.
Table 6.1.2.1.2.1-4: Band (3 + 26) BS transmit configurations with 3rd IMD within 905 – 915 MHz
Band 26 DL channel bandwidth (MHz)
Band 26 DL frequency block (MHz)
Band 3 DL channel bandwidth (MHz)
IMD frequency limits (MHz)
5
889 – 894
15
874 – 909
5
889 – 894
20
869 – 914
10
884 – 894
15
869 – 909
10
884 – 894
20
864 – 914
5
884 – 889
20
864 – 909
10
879 – 889
20
859 – 909
It should be noted that Bands 2, 4, 6, 9, 10, 19, 20, 25, 35, 38, 39, 41, 42 and 43 are not intended for use in the same geographical area as Bands 3 and 26. Consequently, the focus here will be on the harmonics and IMD products falling into Bands 3, 5, 8 and 26.
As shown above, the 2nd harmonics of BS transmitting in Band 26 may fall into the BS receive band of Band 3, while the 3rd order IMD products caused by mixing of Bands 3 and 26 DL carriers may fall within Bands 5, 8 and 26 UL used in South Korea if certain BS transmit configurations are used, and hence BS receiver desensitization may be an issue
Therefore, it is recommended that Bands 3 and 26 BS transmitters should not share the same antenna with Band 5, 8 or 26 BS receiver for the affected frequency ranges if the aforementioned BS transmit configurations are used, unless the antenna path meets very stringent 2nd and 3rd order PIM specification so that the PIM will not cause Band 5, 8 or 26 BS receiver desensitization.
6.1.2.1.3 ∆TIB and ∆RIB values
For two simultaneous DL and one UL the TIB,c and RIB values are shown in table 6.1.2.1.3-1, and in table 6.1.2.1.3-2:
Table 6.1.2.1.3-1: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_3-26
3
0.3
26
0.3
Table 6.1.2.1.3-2: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_3-26
3
0
26
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.3 LTE Advanced Carrier Aggregation of Band 3 and Band 19 (1 UL) | Table 6.1.3-1: Inter-band CA
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_3-19
3
1710 MHz
–
1785 MHz
5,10, 15, 20
(note 1)
1805 MHz
–
1880 MHz
5, 10, 15, 20
FDD
19
830 MHz
–
845 MHz
5, 10, 15
(note 1)
875 MHz
–
890 MHz
5, 10, 15
NOTE 1: The WI considers only one uplink component carrier to be used in any of the two frequency bands at any time.
6.1.3.1 List of specific combination issues |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.3.1.1 Channel bandwidths per operating band for CA | Table 6.1.3.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_3A-19A
3
Yes
Yes
Yes
Yes
19
Yes
Yes
Yes |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.3.1.2 Co-existence studies for CA_3-19 | As band 3 and band 19 are a low-high band combination the harmonic frequencies are far away from the receive and transmit bands of interest in the DL and UL (see table 6.1.3.1.2-1) and therefore we can conclude that there is no issue on harmonic interference.
Table 6.1.3.1.2-1: Impact of UL/DL Harmonic Interference
2nd Harmonic
3rd Harmonic
2nd Harmonic
3rd Harmonic
Band
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
UL Low Band Edge
UL High Band Edge
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
DL Low Band Edge
DL High Band Edge
3
1710
1785
1805
1880
3420
3570
5130
5355
3610
3760
5415
5640
19
830
845
875
890
1660
1690
2490
2535
1750
1780
2625
2670
6.1.3.1.3 ∆TIB and ∆RIB values
For two simultaneous DL and one UL the TIB,c and RIB values are shown in table 6.1.3.1.3-1 and in table 6.1.3.1.3-2:
Table 6.1.3.1.3-1: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_3-19
3
0.3
19
0.3
Table 6.1.3.1.3-2: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_3-19
3
0
19
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.4 LTE Advanced Carrier Aggregation of Band 1 and Band 8 (1 UL) | Table 6.1.4-1: Inter-band CA
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_1-8
1
1920 MHz
–
1980 MHz
5,10, 15, 20
(note 1)
2110 MHz
–
2170 MHz
5, 10, 15, 20
FDD
8
880 MHz
–
915 MHz
5, 10
(note 1)
925 MHz
–
960 MHz
5, 10
NOTE 1: Only one uplink component carrier is to be supported in any of the two frequency bands at any time.
6.1.4.1 List of specific combination issues |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.4.1.1 Channel bandwidths per operating band for CA | Table 6.1.4.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
Bandwidth Combination Set
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_1A-8A
1
Yes
Yes
Yes
Yes
0
8
Yes
Yes
1
Yes
Yes
1
8
Yes
Yes |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.4.1.2 Co-existence studies for CA_1-8 | As shown in table 6.1.4.1.2-1, the harmonic frequencies of band 1 and band 8 in UL are away from the receive bands of interest in the DL and we can conclude that there is no issue on UL harmonic interference.
Table 6.1.4.1.2-1: Impact of UL Harmonic Interference
2nd Harmonic
3rd Harmonic
Band
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
UL Low Band Edge
UL High Band Edge
UL Low Band Edge
UL High Band Edge
1
1920
1980
2110
2170
3840
3960
5760
5940
8
880
915
925
960
1760
1830
2640
2745
Table 6.1.4.1.2-2: Band 1 and Band 8 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
925
960
2110
2170
2nd order harmonics frequency range (MHz)
1850
1920
4220
4340
3rd order harmonics frequency range (MHz)
2775
2880
6330
6510
2nd order IMD products
(f2_low – f1_high)
(f2_high – f1_low)
(f2_low + f1_low)
(f2_high + f1_high)
IMD frequency limits (MHz)
925
960
2110
2170
3rd order IMD products
(f2_low – 2*f1_high)
(f2_high – 2*f1_low)
(2*f2_low – f1_high)
(2*f2_high – f1_low)
IMD frequency limits (MHz)
190
320
3260
3415
3rd order IMD products
(2*f1_low + f2_low)
(2*f1_high + f2_high)
(2*f2_low + f1_low)
(2*f2_high + f1_high)
IMD frequency limits (MHz)
3960
4090
5145
5300
3rd order IMD products
(f1_low – max BW f2)
(f1_high + max BW f2)
(f2_low – max BW f1)
(f2_high + max BW f1)
IMD frequency limits (MHz)
905
980
2100
2180
It can be seen from table 6.1.4.1.2-2 that the upper edge of the 2nd harmonics of BS transmit band of f1 (band 8) is on the lower edge of BS receive band of f2 (band 1). It can also be seen that the 3rd IMD falls into BS receive band of band 8. However, as noted in subclause 5.1, these issues can be regarded as covered in co-located BS scenarios and there is no need to address in Inter-band carrier aggregation context.
6.1.4.1.3 ΔTIB,c and ΔRIB values
For two simultaneous DL and only one UL, the tentative TIB,c and RIB values are given in the tables below.
Table 6.1.4.1.3-1: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_1A-8A
1
0.3
8
0.3
NOTE: The values in the table reflect what can be achieved with the present state of the art technology. They shall be reconsidered when the state of the art technology progresses
Table 6.1.4.1.3-2: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_1A-8A
1
0
8
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.5 LTE Advanced Carrier Aggregation of Band 3 and Band 28 (1 UL) | Table 6.1.5-1: Inter-band CA
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_3-28
3
1710 MHz
–
1785 MHz
5,10, 15, 20
(note 1)
1805 MHz
–
1880 MHz
5, 10, 15, 20
FDD
28
703 MHz
–
748 MHz
5, 10, 15, 20
(note 1)
758 MHz
–
803 MHz
5, 10, 15, 20
NOTE 1: The WI considers only one uplink component carrier to be used in any of the two frequency bands at any time.
6.1.5.1 List of specific combination issues |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.5.1.1 Channel bandwidths per operating band for CA | Table 6.1.5.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_3A-28A
3
Yes
Yes
Yes
Yes
28
Yes
Yes
Yes
Yes |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.5.1.2 Co-existence studies for CA_3-28 | As band 3 and band 28 are a low-high band combination the harmonic frequencies are far away from the receive bands of interest in the DL (see table 6.1.5.1.2-1) and we can conclude that there is no issue on harmonic interference.
Table 6.1.5.1.2-1: Band 3 and Band 28 UL harmonics
2nd Harmonic
3rd Harmonic
Band
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
UL Low Band Edge
UL High Band Edge
UL Low Band Edge
UL High Band Edge
3
1710
1785
1805
1880
3420
3570
5130
5355
28
703
748
758
803
1406
1496
2109
2244
The 2nd and 3rd order harmonics and IMD products caused in the BS by transmitting of band 3 and band 28 DL carriers can be calculated as shown in table 6.1.5.1.2-1 below:
Table 6.1.5.1.2-2: Band 3 and Band 28 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
758
803
1805
1880
2nd order harmonics frequency range (MHz)
1516
1606
3610
3760
3rd order harmonics frequency range (MHz)
2274
2409
5415
5640
2nd order IMD products
(f2_low – f1_high)
(f2_high – f1_low)
(f2_low + f1_low)
(f2_high + f1_high)
IMD frequency limits (MHz)
1002
1122
2563
2683
3rd order IMD products
(f2_low – 2*f1_high)
(f2_high – 2*f1_low)
(2*f2_low – f1_high)
(2*f2_high – f1_low)
IMD frequency limits (MHz)
199
364
2807
3002
3rd order IMD products
(2*f1_low + f2_low)
(2*f1_high + f2_high)
(2*f2_low + f1_low)
(2*f2_high + f1_high)
IMD frequency limits (MHz)
3321
3486
4368
4563
3rd order IMD products
(f1_low – max BW f2)
(f1_high + max BW f2)
(f2_low – max BW f1)
(f2_high + max BW f1)
IMD frequency limits (MHz)
683
878
1760
1925
It can be seen that the 3rd IMD falls into BS receive band of band 3 and 28. However, these products will not fall into the BS own receive block if the frequency range as defined with the channel bandwidths given in table 6.1.5.1.1-1 are used for the more detailed IMD calculation.
6.1.5.1.3 ΔTIB,c and ΔRIB values
For two simultaneous DL and only one UL, the tentative TIB,c and RIB values are given in the tables below.
Table 6.1.5.1.3-1: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_3A-28A
3
0.3
8
0.3
NOTE: The values in the table reflect what can be achieved with the present state of the art technology. They shall be reconsidered when the state of the art technology progresses
Table 6.1.5.1.3-2: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_3A-28A
3
0
8
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.6 LTE Advanced Carrier Aggregation of Band 1 and Band 26 | CA_1A-26A is designed to operate in the operating bands defined in table 6.1.6-1.
Table 6.1.6-1: Inter band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_1-26
1
1920 MHz
–
1980 MHz
5, 10, 15, 20
2110 MHz
–
2170 MHz
5, 10, 15, 20
FDD
26
814 MHz
–
849 MHz
5, 10, 15
859 MHz
–
894 MHz
5, 10, 15
6.1.6.1 List of specific combination issues |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.6.1.1 Channel bandwidths per operating band for CA | Table 6.1.6.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
Maximum aggregate bandwidth [MHz]
Bandwidth Combination Set
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_1A-26A
1
Yes
Yes
Yes
Yes
35
0
26
Yes
Yes
Yes
1
Yes
Yes
20
1
26
Yes
Yes |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.6.1.2 Co-existence studies for CA_1-26 | Although Band 1 and Band 26 are a High-Low band combination, the harmonic frequencies do not fall into the frequency ranges of both bands as observed in table 6.1.6.1.2-1. Therefore we can conclude that there is no issue on harmonic interference.
Table 6.1.6.1.2-1: Impact of UL/DL Harmonic Interference
2nd Harmonic
3rd Harmonic
2nd Harmonic
3rd Harmonic
Band
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
UL Low Band Edge
UL High Band Edge
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
DL Low Band Edge
DL High Band Edge
1
1920
1980
2110
2170
3840
3960
5760
5940
4220
4340
6330
6510
26
814
849
859
894
1628
1698
2442
2547
1718
1788
2577
2682
Table 6.1.6.1.2-2 gives the frequency range of the third and fifth order intermodulation products when two simultaneous DLs are active in Band 1 and band 26. It can be seen that the intermodulation products are not falling within the two inter-bands and therefore no further relaxation is needed.
Table 6.1.6.1.2-2: Third order and fifth order intermodulation products (DL)
Band
DL low band edge
DL high band edge
DL 3rd order products
DL 5th order products
1
2110 MHz
2170 MHz
N/A
3326 – 3481 MHz
N/A
4542 – 4792 MHz
26
859 MHz
894 MHz
6.1.6.1.3 ∆TIB and ∆RIB values
Following relaxations are allowed for the UE which supports inter-band carrier aggregation of Band 1 and Band 26.
Table 6.1.6.1.3-1: IB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_1A-26A
1
0.3
26
0.3
Table 6.1.6.1.3-2: RIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB,c [dB]
CA_1A-26A
1
0
26
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.7 LTE Advanced Carrier Aggregation of Band 2 and Band 12 (1 UL) | Table 6.1.7-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_2-12
2
1850 MHz
–
1910 MHz
5, 10, 15, 20
1930 MHz
–
1990 MHz
5, 10, 15, 20
FDD
12
699 MHz
–
716 MHz
3, 5, 10
729 MHz
–
746 MHz
3, 5, 10
6.1.7.1 List of specific combination issues |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.7.1.1 Channel bandwidths per operating band for CA | Table 6.1.7.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_2A-12A
2
Yes
Yes
Yes
Yes
12
Yes
Yes
Yes
NOTE: For the UE that signals support of any bandwidth combination set for carrier aggregation, the UE shall support all single carrier bandwidths for the constituent bands as defined in table 5.6.1-1 of TS 36.101 [4] when operating in single carrier mode. |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.7.1.2 Co-existence studies for CA_2-12 | The 2nd and 3rd order harmonics and IMD products caused in the BS by transmitting of Band 2 and Band 12 DL carriers can be calculated as shown in table 6.1.7.1.2-1 below:
Table 6.1.7.1.2-1: Band 2 and Band 12 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
729
746
1930
1990
2nd order harmonics frequency range (MHz)
1458
1492
3860
3980
3rd order harmonics frequency range (MHz)
2187
2238
5790
5970
2nd order IMD products
(f2_low – f1_high)
(f2_high – f1_low)
(f2_low + f1_low)
(f2_high + f1_high)
IMD frequency limits (MHz)
1184
1261
2659
2736
3rd order IMD products
(f2_low – 2*f1_high)
(f2_high – 2*f1_low)
(2*f2_low – f1_high)
(2*f2_high – f1_low)
IMD frequency limits (MHz)
438
532
3114
3251
3rd order IMD products
(2*f1_low + f2_low)
(2*f1_high + f2_high)
(2*f2_low + f1_low)
(2*f2_high + f1_high)
IMD frequency limits (MHz)
3388
3482
4589
4726
3rd order IMD products
(f1_low – f2_high + f2_low)
(f1_high + f2_high – f2_low)
(f2_low – f1_high + f1_low)
(f2_high + f1_high – f1_low)
IMD frequency limits (MHz)
669
806
1913
2007
It can be seen from table 6.1.7.1.2-1 that the 2nd harmonics of Band 12 carriers may fall into the BS receive band of Band 21, while the 2nd IMD products caused by BS supporting carrier aggregation of Band 2 and Band 12 may fall into the BS receive band of Band 41, and the 3rd IMD products may fall into the BS receive band of Bands 1, 12, 13, 14, 17, 22, 23, 25, 28, 31, 33, 36, 37, 39, 42 and 44. Note that the calculation in table 6.1.7.1.2-1 (except the last row) assumes the BS is transmitting with the whole 60 MHz DL frequency of Band 2 and the whole 17 MHz DL frequency of Band 12. If the BS is only transmitting an up to 10 MHz DL in Band 2 and Band 12 as stated in the WIDS, then the 3rd IMD products will not fall into the BS receive band of Band 12, 13, 14, 17, 23, 25, 33 or 39 as shown in the last row in table 6.1.7.1.2-1.
It should be noted that Bands 1, 21, 28, 31, 39 and 44 are not intended for use in the same geographical area as Bands 2 and 12. Moreover, co-location of Band (2 + 12) transmitter and Band 33, 36 or 37 transceiver implies FDD/TDD co-location on adjacent frequencies which requires the use of certain site-engineering solutions to avoid mutual interference. Therefore, the focus here will be on the harmonics and IMD falling into Bands 22, 41 and 42.
With the performances of the current BS antenna system, transmit and receive path components, amplifiers, pre-distortion algorithms and filters, it is expected that the IMD interference generated within the Band 22, 41 or 42 receiver would be well below the receiver noise floor eliminating the possibility of receiver desensitization, provided that Bands 2 and 12 BS transmitters do not share the same antenna with Band 22, 41 or 42 BS receiver.
Therefore, it is recommended that Bands 2 and 12 BS transmitters should not share the same antenna with Band 22, 41 or 42 BS receiver, unless the antenna path meets very stringent 2nd and 3rd order PIM specification so that the PIM will not cause Band 22, 41 or 42 BS receiver desensitization. Note that antenna sharing may be allowed as the state-of-the-art continues to evolve in the future.
6.1.7.1.3 ΔTIB,c and ΔRIB
The following relaxations are allowed for the inter-band carrier aggregation of Band 2 and Band 12
Table 6.1.7.1.3-1: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_2A-12A
2
0.3
12
0.3
Table 6.1.7.1.3-2: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_2A-12A
2
0
12
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.8 LTE Advanced Carrier Aggregation of Band 2 and Band 13 | CA_2-13 is designed to operate in the operating bands in table 6.1.8-1.
Table 6.1.8-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_2-13
2
1850 MHz
–
1910 MHz
5,10,15, 20
(note 1)
1930 MHz
–
1990 MHz
5, 10, 15, 20
FDD
13
777 MHz
–
787 MHz
10
(note 1)
746 MHz
–
756 MHz
10
NOTE 1: The WI considers only one uplink component carrier to be used in any of the two frequency bands at any time
6.1.8.1 List of specific combination issues |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.8.1.1 Channel bandwidths per operating band for CA | Table 6.1.8.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
Bandwidth Combination Set
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_2A-13A
2
Yes
Yes
Yes
Yes
0
13
Yes
2
Yes
Yes
1
13
Yes |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.8.1.2 Co-existence studies for CA_2-13 | As shown in table 6.1.8.1.2-1, the harmonic frequencies of Band 2 and Band 13 in UL are away from the receive bands of interest in the DL and therefore we can conclude that there is no issue on harmonic interference.
Table 6.1.8.1.2-1: Impact of UL/DL Harmonic Interference
2nd Harmonic
3rd Harmonic
2nd Harmonic
3rd Harmonic
Band
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
UL Low Band Edge
UL High Band Edge
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
DL Low Band Edge
DL High Band Edge
2
1850
1910
1930
1990
3700
3820
5550
5730
3860
3980
5790
5970
13
777
787
746
756
1554
1574
2331
2361
1492
1512
2238
2268 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.8.1.2.1 Co-existence studies for 1 UL/2 DL | The 2nd and 3rd order harmonics and IMD products caused in the BS by transmitting of Band 2 and Band 13 DL carriers can be calculated as shown in table 6.1.8.1.2.1-1 below:
Table 6.1.8.1.2.1-1: Band 2 and Band 13 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
746
756
1930
1990
2nd order harmonics frequency range (MHz)
1492
1512
3860
3980
3rd order harmonics frequency range (MHz)
2238
2268
5790
5970
2nd order IMD products
(f2_low – f1_high)
(f2_high – f1_low)
(f2_low + f1_low)
(f2_high + f1_high)
IMD frequency limits (MHz)
1174
1244
2676
2746
3rd order IMD products
(f2_low – 2*f1_high)
(f2_high – 2*f1_low)
(2*f2_low – f1_high)
(2*f2_high – f1_low)
IMD frequency limits (MHz)
418
498
3104
3234
3rd order IMD products
(2*f1_low + f2_low)
(2*f1_high + f2_high)
(2*f2_low + f1_low)
(2*f2_high + f1_high)
IMD frequency limits (MHz)
3422
3502
4606
4736
3rd order IMD products
(f1_low – f2_high + f2_low)
(f1_high + f2_high – f2_low)
(f2_low – f1_high + f1_low)
(f2_high + f1_high – f1_low)
IMD frequency limits (MHz)
686
816
1920
2000
3rd order IMD products (with maximum channel bandwidth)
(f1_low – f2_BWmax)
(f1_high + f2_BWmax)
(f2_low – f1_BWmax)
(f2_high + f1_BWmax)
IMD frequency limits (MHz)
726
776
1920
2000
It can be seen from table 6.1.8.1.2.1-1 that the 2nd and 3rd harmonics of Band 2 and Band 13 carriers will not fall into the BS receive band of any frequency band currently defined in 3GPP, but the 2nd IMD products caused by BS supporting carrier aggregation of Band 2 and Band 13 may fall into the BS receive band of Band 41, and the 3rd IMD products may fall into the BS receive band of Bands 1, 12, 13, 14, 17, 18, 22, 26, 27, 28, 31, 36, 37, 42 and 44. Note that the calculation in table 6.1.8.1.2.1-1 (except the last row) assumes the BS is transmitting with the whole 60 MHz DL frequency of Band 2 and the whole 10 MHz DL frequency of Band 13. If the BS is only transmitting an up to 20 MHz DL in Band 2 and an up to 10 MHz DL in Band 13 as stated in the WIDS, then the 3rd IMD products may only fall into the BS receive band of the Bands 1, 22, 28, 31, 36, 37, 42 and 44 as shown in the last row in table 6.1.8.1.2.1-1.
It should be noted that that Bands 1, 18, 28, 31 and 44 are not intended for use in the same geographical area as Bands 2 and 13. Moreover, co-location of Band (2 +13) transmitter and Band 36 or 37 transceiver implies FDD/TDD co-location on adjacent frequencies which requires the use of certain site-engineering solutions to avoid mutual interference. Therefore, the focus here will be on the harmonics and IMD falling into Bands 12, 14, 17, 22, 26, 27, 41 and 42.
With the performances of the current BS antenna system, transmit and receive path components, amplifiers, pre-distortion algorithms and filters, it is expected that the IMD interference generated within the Band 22, 41 or 42 receiver would be well below the receiver noise floor eliminating the possibility of receiver desensitization, provided that Bands 2 and 13 BS transmitters do not share the same antenna with Band 12, 14, 17, 22, 26, 27, 41 or 42 BS receiver.
Therefore, it is recommended that Bands 2 and 13 BS transmitters should not share the same antenna with 12, 14, 17, 22, 26, 27, 41 or 42 BS receiver to prevent Band 12, 14, 17, 22, 26, 27, 41 or 42 BS receiver desensitization, unless the antenna path meets very stringent 2nd and 3rd order PIM specification so that the PIM will not cause Band 12, 14, 17, 22, 26, 27, 41 or 42 BS receiver desensitization.
6.1.8.1.3 ΔTIB,c and ΔRIB (1 UL)
For the UE which supports CA_2A-13A the ΔTIB,c is defined for applicable bands in table 6.1.8.1.3-1.
Table 6.1.8.1.3-1: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_2A-13A
2
0.3
13
0.3
For the UE which supports CA_2A-13A the ΔRIB is defined for applicable bands in table 6.1.8.1.3-2.
Table 6.1.8.1.3-2: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_2A-13A
2
0
13
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.9 LTE Advanced Carrier Aggregation of Band 12 and Band 25 (1 UL) | Table 6.1.9-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_12-25
12
699 MHz
–
716 MHz
5, 10
729 MHz
–
746 MHz
5, 10
FDD
25
1850 MHz
–
1915 MHz
5, 10
1930 MHz
–
1995 MHz
5, 10
6.1.9.1 List of specific combination issues |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.9.1.1 Channel bandwidths per operating band for CA | Table 6.1.9.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_12A-25A
12
Yes
Yes
25
Yes
Yes
NOTE: For the UE that signals support of any bandwidth combination set for carrier aggregation, the UE shall support all single carrier bandwidths for the constituent bands as defined in table 5.6.1-1 of TS 36.101 [4] when operating in single carrier mode. |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.9.1.2 Co-existence studies for CA _12_25 | The 2nd and 3rd order harmonics and IMD products caused in the BS by transmitting of Band 12 and Band 25 DL carriers can be calculated as shown in Table 6.1.9.1.2-1 below:
Table 6.1.9.1.2-1: Band 12 and Band 25 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
729
746
1930
1995
2nd order harmonics frequency range (MHz)
1458
1492
3860
3990
3rd order harmonics frequency range (MHz)
2187
2238
5790
5985
2nd order IMD products
(f2_low – f1_high)
(f2_high – f1_low)
(f2_low + f1_low)
(f2_high + f1_high)
IMD frequency limits (MHz)
1184
1266
2659
2741
3rd order IMD products
(f2_low – 2*f1_high)
(f2_high – 2*f1_low)
(2*f2_low – f1_high)
(2*f2_high – f1_low)
IMD frequency limits (MHz)
438
537
3114
3261
3rd order IMD products
(2*f1_low + f2_low)
(2*f1_high + f2_high)
(2*f2_low + f1_low)
(2*f2_high + f1_high)
IMD frequency limits (MHz)
3388
3487
4589
4736
3rd order IMD products
(f1_low – f2_high + f2_low)
(f1_high + f2_high – f2_low)
(f2_low – f1_high + f1_low)
(f2_high + f1_high – f1_low)
IMD frequency limits (MHz)
664
811
1913
2012
3rd order IMD products (with maximum channel bandwidth)
(f1_low – f2_BWmax)
(f1_high + f2_BWmax)
(f2_low – f1_BWmax)
(f2_high + f1_BWmax)
IMD frequency limits (MHz)
719
756
1920
2005
It can be seen from Table 6.1.9.1.2-1 that the 2nd harmonics of Band 12 carriers may fall into the BS receive band of Band 21, while the 2nd IMD products caused by BS supporting carrier aggregation of Band 12 and Band 25 may fall into the BS receive band of Band 41, and the 3rd IMD products may fall into the BS receive band of Bands 1, 12, 13, 14, 17, 22, 23, 25, 27, 28, 31, 33, 34, 36, 37, 39, 42 and 44. Note that the calculation in Table 6.1.9.1.2-1 (except the last row) assumes the BS is transmitting with the whole 60 MHz DL frequency of Band 25 and the whole 17 MHz DL frequency of Band 12. If the BS is only transmitting an up to 10 MHz DL in Band 25 and Band 12 as stated in the WIDS, then the 3rd IMD products will not fall into the BS receive band of Band 12, 13, 14, 17, 23, 25, 27, 33, 34 or 39 as shown in the last row in Table 6.1.9.1.2-1.
It should be noted that Bands 1, 21, 28, 31, and 44 are not intended for use in the same geographical area as Bands 25 and 12. Moreover, a co-location of Band (12 + 25) transmitter and Band 36 or 37 transceivers implies FDD/TDD co-location on adjacent frequencies which requires the use of certain site-engineering solutions to avoid mutual interference. Therefore, the focus here will be on the harmonics and IMD falling into Bands 22, 41 and 42.
With the performances of the current BS antenna system, transmit and receive path components, amplifiers, pre-distortion algorithms and filters, it is expected that the IMD interference generated within the Band 22, 41 or 42 receiver would be well below the receiver noise floor eliminating the possibility of receiver desensitization, provided that Bands 2 and 12 BS transmitters do not share the same antenna with Band 22, 41 or 42 BS receiver.
Therefore, it is recommended that Bands 12 and 25 BS transmitters should not share the same antenna with Band 22, 41 or 42 BS receivers; unless the antenna path meets very stringent 2nd and 3rd order PIM specification so that the PIM will not cause Band 22, 41 or 42 BS receiver de-sensitization. Note that antenna sharing may be allowed as the state-of-the-art continues to evolve in the future.
6. 1.9.1.3 ΔTIB,c and ΔRIB
The following relaxations are allowed for the inter-band carrier aggregation of Band 2 and Band 12
Table 6.1.9.1.3-1: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_12A-25A
12
0.3
25
0.3
Table 6.1.9.1.3-2: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_12A-25A
12
0
25
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.10 LTE Advanced Carrier Aggregation of Band 2 and Band 5 | CA_2-5 is designed to operate in the operating bands in table 6.1.10-1.
Table 6.1.10-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_2-5
2
1850 MHz
–
1910 MHz
5, 10, 15, 20
(note 1)
1930 MHz
–
1990 MHz
5, 10, 15, 20
FDD
5
824 MHz
–
849 MHz
5, 10
(note 1)
869 MHz
–
894 MHz
5, 10
NOTE 1: The WI considers only one uplink component carrier to be used in any of the two frequency bands at any time
6.1.10.1 List of specific combination issues |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.10.1.1 Channel bandwidths per operating band for CA | Table 6.1.10.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
Bandwidth Combination Set
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_2A-5A
Yes
Yes
Yes
Yes
0
Yes
Yes
Yes
Yes
1
Yes
Yes |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.10.1.2 Co-existence studies for CA_2-5 | As shown in table 6.1.10.1.2-1, the harmonic frequencies of Band 2 and Band 5 in UL are away from the receive bands of interest in the DL and therefore we can conclude that there is no issue on harmonic interference.
Table 6.1.10.1.2-1: Impact of UL/DL Harmonic Interference
2nd Harmonic
3rd Harmonic
2nd Harmonic
3rd Harmonic
Band
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
UL Low Band Edge
UL High Band Edge
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
DL Low Band Edge
DL High Band Edge
2
1850
1910
1930
1990
3700
3820
5550
5730
3860
3980
5790
5970
5
824
849
869
894
1648
1698
2472
2547
1738
1788
2607
2682 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.10.1.2.1 Co-existence studies for 1 UL/2 DL | The 2nd and 3rd order harmonics and IMD products caused in the BS by transmitting of Band 2 and Band 5 DL carriers can be calculated as shown in Table 6.1.10.1.2.1-1 below:
Table 6.1.10.1.2.1-1: Band 2 and Band 5 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
869
894
1930
1990
2nd order harmonics frequency range (MHz)
1738
1788
3860
3980
3rd order harmonics frequency range (MHz)
2607
2682
5790
5970
2nd order IMD products
(f2_low – f1_high)
(f2_high – f1_low)
(f2_low + f1_low)
(f2_high + f1_high)
IMD frequency limits (MHz)
1036
1121
2799
2884
3rd order IMD products
(f2_low – 2*f1_high)
(f2_high – 2*f1_low)
(2*f2_low – f1_high)
(2*f2_high – f1_low)
IMD frequency limits (MHz)
142
252
2966
3111
3rd order IMD products
(2*f1_low + f2_low)
(2*f1_high + f2_high)
(2*f2_low + f1_low)
(2*f2_high + f1_high)
IMD frequency limits (MHz)
3668
3778
4729
4874
3rd order IMD products
(f1_low – f2_high + f2_low)
(f1_high + f2_high – f2_low)
(f2_low – f1_high + f1_low)
(f2_high + f1_high – f1_low)
IMD frequency limits (MHz)
809
954
1905
2015
3rd order IMD products (with maximum channel bandwidth)
(f1_low – f2_BWmax)
(f1_high + f2_BWmax)
(f2_low – f1_BWmax)
(f2_high + f1_BWmax)
IMD frequency limits (MHz)
849
914
1920
2000
the 2nd harmonics of BS transmitting in Band 5 may fall into the BS receive band of Bands 3, 4, 9 and 10, and the 3rd harmonics may fall into the BS receive band of Bands 38 and 41, while the 3rd IMD products caused by BS supporting carrier aggregation of Band 2 and Band 5 may fall into the BS receive band of Bands 1, 2, 5, 6, 8, 18, 19, 20, 23, 25, 26, 27, 33, 34, 35, 36, 37, 39 and 43. Note that the calculation in Table 6.1.10.1.2.1-1 (except the last row) assumes the BS is transmitting with the whole 60 MHz DL frequency of Band 2 and the whole 25 MHz DL frequency of Band 5. If the BS is only transmitting an up to 20 MHz DL in Band 2 and an up to 10 MHz DL in Band 5 as stated in the WIDS, then the 3rd IMD products may only fall into the BS receive band of the Bands 1, 8, 20, 36, 37 and 43 as shown in the last row in Table 6.1.10.1.2.1-1.
It should be noted that that Bands 1, 3, 8, 9, 20 and 38 are not intended for use in the same geographical area as Bands 2 and 5. Moreover, co-location of Band (2 + 5) transmitter and Band 36 or 37 transceiver implies FDD/TDD co-location on adjacent frequencies which requires the use of certain site-engineering solutions to avoid mutual interference. Therefore, the focus here will be on the harmonics and IMD falling into Bands 4, 10, 41 and 43.
With the performances of the current BS antenna system, transmit and receive path components, amplifiers, pre-distortion algorithms and filters, it is expected that the IMD interference generated within the Band 4, 10, 41 or 43 receiver would be well below the receiver noise floor eliminating the possibility of receiver desensitization, provided that Bands 2 and 5 BS transmitters do not share the same antenna with Band 4, 10, 41 or 43 BS receiver.
Therefore, it is recommended that Bands 2 and 5 BS transmitters should not share the same antenna with Band 4, 10, 41 or 43 BS receiver to prevent BS receiver desensitization, unless the antenna path meets very stringent 2nd and 3rd order PIM specification so that the PIM will not cause Band 4, 10, 41 or 43 BS receiver desensitization.
6.1.10.1.3 ΔTIB,c and ΔRIB (1 UL)
For the UE which supports CA_2A-5A the ΔTIB,c is defined for applicable bands in table 6.1.10.1.3-1.
Table 6.1.10.1.3-1: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_2A-5A
2
0.3
5
0.3
For the UE which supports CA_2A-5A the ΔRIB is defined for applicable bands in table 6.1.10.1.3-2.
Table 6.1.10.1.3-2: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_2A-5A
2
0
5
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.11 LTE Advanced Carrier Aggregation of Band 1 and Band 18 | CA_1A-18A is designed to operate in the operating bands defined in Table 6.1.11-1.
Table 6.1.11-1: Inter band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_1-18
1
1920 MHz
–
1980 MHz
5, 10, 15, 20
2110 MHz
–
2170 MHz
5, 10, 15, 20
FDD
18
815 MHz
–
830 MHz
5, 10
860 MHz
–
875 MHz
5, 10
6.1.11.1 List of specific combination issues |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.11.1.1 Channel bandwidths per operating band for CA | Table 6.1.11.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
Maximum aggregate bandwidth [MHz]
Bandwidth Combination Set
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_1A-18A
1
Yes
Yes
Yes
Yes
35
0
18
Yes
Yes
Yes
1
Yes
Yes
20
1
18
Yes
Yes |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.11.1.2 Co-existence studies for CA_1-18 | Studies have been already made in Rel-11. See [3]. |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.11.1.2.1 Co-existence studies for 1 UL/2 DL | The 2nd and 3rd order harmonics and IMD products caused in the BS by transmitting of Band 1 and Band 18 DL carriers can be calculated as shown in Table 6.1.11.1.2.1-1 below:
Table 6.1.11.1.2.1-1: Band 1 and Band 18 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
860
875
2110
2170
2nd order harmonics frequency range (MHz)
1720
1750
4220
4340
3rd order harmonics frequency range (MHz)
2580
2625
6330
6510
2nd order IMD products
(f2-low – f1-high)
(f2-high – f1-low)
(f2-low + f1-low)
(f2-high + f1-high)
IMD frequency limits (MHz)
1235
1310
2970
3045
3rd order IMD products
(f2-low – 2*f1-high)
(f2-high – 2*f1-low)
(2*f2-low – f1-high)
(2* f2-high – f1-low)
IMD frequency limits (MHz)
360
450
3345
3480
3rd order IMD products
(2*f1-low + f2-low)
(2*f1-high + f2-high)
(2*f2-low + f1-low)
(2*f2-high + f1-high)
IMD frequency limits (MHz)
3830
3920
5080
5215
3rd order IMD products
(f1-low – f2-high + f2-low)
(f1-high + f2-high – f2-low)
(f2-low – f1-high + f1-low)
(f2-high + f1-high – f1-low)
IMD frequency limits (MHz)
800
935
2095
2185
3rd Order IMD products (with maximum channel bandwidth)
(f1_low – f2_BWmax)
(f1_high + f2_BWmax)
(f2_low – f1_BWmax)
(f2_high + f1_BWmax)
IMD frequency limits (MHz)
840
895
2095
2185
It can be seen from Table 6.1.11.1.2.1-1 that the 2nd harmonics of BS transmitting in Band 18 may fall into the BS receive band of Bands 3, 4, 9 and 10, and the 3rd harmonics of BS transmitting in Band 18 may fall into the BS receive band of Bands 38 and 41, while the 3rd IMD products caused by BS supporting CA of Band 1 and Band 18 may fall into the BS receive band of Bands 5, 6, 8, 18, 19, 20, 22, 26, 27, 42 and 44. Note that the calculation in Table 6.1.11.1.2.1-1 (except the last row) assumes the BS is transmitting with the whole 60 MHz DL frequency of Band 1 and the whole 15 MHz DL frequency of Band 18. If the BS is only transmitting an up to 20 MHz DL in Band 1 and an up to 15 MHz DL in Band 18 as stated in the WIDS, then the 3rd IMD products may only fall into the BS receive band of the Bands 5, 8, 19, 20, 22, 26 and 42 as shown in the last row in Table 6.1.11.1.2.1-1, and the 3rd IMD products will not fall into the BS receive frequency range within Band 8 (900 – 915 MHz) that is allocated in Japan. Also the 3rd IMD products may only fall into the BS receive band of certain frequency range within Band 19 under the transmit configurations shown in Table 6.1.11.1.2.1-2 below.
Table 6.1.11.1.2.1-2: Band (1 + 18) BS transmit configurations with 3rd IMD within Band 19 BS receive band
Band 1 DL channel bandwidth (MHz)
Band 18 DL channel bandwidth (MHz)
Lower edge of Band 18 DL frequency block (MHz)
Lower edge of IMD frequency limits (MHz)
20
5, 10 or 15
860 – 874.9
840 – 844.9
It should be noted that Bands 4, 5, 10, 20, 26 and 38 are not intended for use in the same geographical area as Bands 1 and 18, and the 3rd IMD products caused by BS supporting CA of Band 1 and Band 18 will not fall into the BS receive frequency range within Band 8 that is allocated in Japan. Therefore, the focus here will be on the harmonics and IMD falling into Bands 3, 9, 19, 22, 41 and 42.
With the performances of the current BS antenna system, transmit and receive path components, amplifiers, pre-distortion algorithms and filters, it is expected that the harmonics and IMD interference generated within the Band 3, 9, 22, 41 or 42 receiver would be well below the receiver noise floor eliminating the possibility of receiver desensitization, provided that Bands 1 and 18 BS transmitters do not share the same antenna with Band 3, 9, 22, 41 or 42 BS receiver.
On the other hand, it is recommended that Bands 1 and 18 BS transmitters should not share the same antenna with Band 3, 9, 22, 41 or 42 BS receiver, or Band 19 BS receiver for the affected frequency ranges if the aforementioned BS transmit configurations are used, in order to prevent BS receiver desensitization, unless the antenna path meets very stringent harmonics and 3rd order PIM specification so that the harmonics and PIM will not cause Band 3, 9, 19, 22, 41 or 42 BS receiver desensitization. |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.12 LTE Advanced Carrier Aggregation of Band 7 and Band 28 | CA_7-28 is designed to operate in the operating bands in table 6.1.12-1.
Table 6.1.12-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_7-28
7
2500 MHz
–
2570 MHz
5,10,15, 20
(Note 1)
2620 MHz
–
2690 MHz
5, 10, 15, 20
FDD
28
703 MHz
–
748 MHz
5, 10, 15
(Note 1)
758 MHz
–
803 MHz
5, 10, 15
NOTE 1: The WI considers only one uplink component carrier to be used in any of the two frequency bands at any time
6.1.12.1 List of specific combination issues |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.12.1.1 Channel bandwidths per operating band for CA | Table 6.1.12.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_7A-28A
7
Yes
Yes
Yes
Yes
28
Yes
Yes
Yes |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.12.1.2 Co-existence studies for CA_7-28 | As shown in table 6.1.12.1.2-1, the harmonic frequencies of Band 7 and Band 28 in UL are away from the receive bands of interest in the DL and therefore we can conclude that there is no issue on harmonic interference.
Table 6.1.12.1.2-1: Impact of UL/DL Harmonic Interference
2nd Harmonic
3rd Harmonic
Band
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
UL Low Band Edge
UL High Band Edge
UL Low Band Edge
UL High Band Edge
7
2500
2570
2620
2690
5000
5140
7500
7710
28
703
748
758
803
1406
1496
2109
2244
The 2nd and 3rd order harmonics and IMD products caused in the BS by transmitting of band 7 and band 28 DL carriers can be calculated as shown in table 6.1.12.1.2-2 below:
Table 6.1.12.1.2-2: Band 7 and Band 28 DL harmonics and IMD products
BS DL carriers
f1_low
f1_high
f2_low
f2_high
DL frequency (MHz)
758
803
2620
2690
2nd order harmonics frequency range (MHz)
1516
1606
5240
5380
3rd order harmonics frequency range (MHz)
2274
2409
7860
8070
2nd order IMD products
(f2-low – f1-high)
(f2-high – f1-low)
(f2-low + f1-low)
(f2-high + f1-high)
IMD frequency limits (MHz)
1817
1932
3378
3493
3rd order IMD products
(f2-low – 2*f1-high)
(f2-high – 2*f1-low)
(2*f2-low – f1-high)
(2* f2-high – f1-low)
IMD frequency limits (MHz)
1014
1174
4437
4622
3rd order IMD products
(2*f1-low + f2-low)
(2*f1-high + f2-high)
(2*f2-low + f1-low)
(2*f2-high + f1-high)
IMD frequency limits (MHz)
4136
4296
5998
6183
3rd order IMD products
(f1-low – f2-high + f2-low)
(f1-high + f2-high – f2-low)
(f2-low – f1-high + f1-low)
(f2-high + f1-high – f1-low)
IMD frequency limits (MHz)
688
873
2575
2735
It can be seen that the 3rd IMD products may fall into BS receive band of band 28. However, as described in subclause 5.1 of TR 36.850, due to the low-high band combinations use separate antennas, this issue can be regarded as covered in co-located BS scenarios and there is no need to address in inter-band carrier aggregation context.
6.1.12.1.3 ΔTIB,c and ΔRIB (1 UL)
For the UE which supports CA_7A-28A the ΔTIB,c is defined for applicable bands in table 6.1.12.1.3-1.
Table 6.1.12.1.3-1: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_7A-28A
7
0.3
28
0.3
For the UE which supports CA_7A-28A the ΔRIB is defined for applicable bands in table 6.1.12.1.3-2.
Table 6.1.12.1.3-2: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_7A-28A
7
0
28
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.13 LTE Advanced Carrier Aggregation of Band 5 and Band 25 | CA_5-25 is designed to operate in the operating bands in table 6.1.13-1.
Table 6.1.13-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_5-25
5
824 MHz
–
849 MHz
5,10
(Note 1)
869 MHz
–
894 MHz
5, 10
FDD
25
1850 MHz
–
1915 MHz
5 ,10, 15, 20
(Note 1)
1930 MHz
–
1995 MHz
5, 10, 15, 20
NOTE 1: The WI considers only one uplink component carrier to be used in any of the two frequency bands at any time
6.1.13.1 List of specific combination issues |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.13.1.1 Channel bandwidths per operating band for CA | Table 6.1.13.1.1-1: Supported E-UTRA bandwidths per CA configuration for inter-band CA
CA operating / channel bandwidth
Bandwidth Combination Set
E-UTRA CA Configuration
E-UTRA Bands
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
CA_5A-25A
5
Yes
Yes
0
25
Yes
Yes
Yes
Yes |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.13.1.2 Co-existence studies for CA_5-25 | As shown in table 6.1.13.1.2-1, the harmonic frequencies of Band 5 and Band 25 in UL are away from the receive bands of interest in the DL and therefore we can conclude that there is no issue on harmonic interference.
Table 6.1.13.1.2-1: Impact of UL/DL Harmonic Interference
2nd Harmonic
3rd Harmonic
2nd Harmonic
3rd Harmonic
Band
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
UL Low Band Edge
UL High Band Edge
UL Low Band Edge
UL High Band Edge
DL Low Band Edge
DL High Band Edge
DL Low Band Edge
DL High Band Edge
5
824
849
869
894
1648
1698
2472
2547
1738
1788
2607
2682
25
1850
1915
1930
1995
3700
3830
5550
5745
3860
3990
5790
5985 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.13.1.2.1 Co-existence studies for 1 UL/2 DL | The 2nd and 3rd order harmonics and IMD products caused in the BS by transmitting of Band 5 and Band 25 DL carriers can be calculated as shown in Table 6.1.13.1.2.1-1 below:
Table 6.1.13.1.2.1-1: Band 5 and Band 25 DL harmonics and IMD products
BS DL carriers
f1-low
f1-high
f2-low
f2-high
DL frequency (MHz)
869
894
1930
1995
2nd harmonics frequency limits (MHz)
1738
1788
3860
3990
3rd harmonics frequency limits (MHz)
2607
2682
5790
5985
2nd order IMD products
(f2-low – f1-high)
(f2-high – f1-low)
(f2-low + f1-low)
(f2-high + f1-high)
IMD frequency limits (MHz)
1036
1126
2799
2889
3rd order IMD products
(f2-low – 2*f1-high)
(f2-high – 2*f1-low)
(2*f2-low – f1-high)
(2*f2-high – f1-low)
IMD frequency limits (MHz)
142
257
2966
3121
3rd order IMD products
(2*f1-low + f2-low)
(2*f1-high + f2-high)
(2*f2-low + f1-low)
(2*f2-high + f1-high)
IMD frequency limits (MHz)
3668
3783
4729
4884
3rd order IMD products
(f1-low – f2-high + f2-low)
(f1-high + f2-high – f2-low)
(f2-low – f1-high + f1-low)
(f2-high + f1-high – f1-low)
IMD frequency limits (MHz)
804
959
1905
2020
3rd order IMD products (with maximum channel bandwidth)
(f1-low – f2-BWmax)
(f1-high + f2- BWmax)
(f2-low – f1- BWmax)
(f2-high + f1- BWmax)
IMD frequency limits (MHz)
849
914
1920
2005
It can be seen from Table 6.1.13.1.2.1-1 that the 2nd harmonics of BS transmitting in Band 5 may fall into the BS receive band of Bands 3, 4, 9 and 10, and the 3rd harmonics may fall into the BS receive band of Bands 38 and 41, while the 3rd IMD products caused by BS supporting carrier aggregation of Band 5 and Band 25 may fall into the BS receive band of Bands 1, 2, 5, 6, 8, 18, 19, 20, 23, 25, 26, 27, 33, 34, 35, 36, 37. 39 and 43. Note that the calculation in Table 6.1.13.1.2.1-1 (except the last row) assumes the BS is transmitting with the whole 25 MHz DL frequency of Band 5 and the whole 65 MHz DL frequency of Band 25. If the BS is only transmitting an up to 10 MHz DL in Band 5 and an up to 20 MHz DL in Band 25 as stated in the WIDS, then the 3rd IMD products may only fall into the BS receive band of Bands 1, 8, 20, 23, 36, 37 and 43 as shown in the last row in Table 6.1.13.1.2.1-1.
It should be noted that Bands 1, 3, 8, 9, 20 and 38 are not intended for use in the same geographical area as Bands 5 and 25. Moreover, co-location of Band (5 + 25) transmitter and Band 36 or 37 transceiver implies FDD/TDD co-location on adjacent frequencies which requires the use of certain site-engineering solutions to avoid mutual interference. Therefore, the focus here will be on the harmonics and IMD falling into Bands 4, 10, 23, 41 and 43.
With the performances of the current BS antenna system, transmit and receive path components, amplifiers, pre-distortion algorithms and filters, it is expected that the IMD interference generated within the Band 4, 10, 41 or 43 receiver would be well below the receiver noise floor eliminating the possibility of receiver desensitization, provided that Bands 5 and 25 BS transmitters do not share the same antenna with Band 4, 10, 41 or 43 BS receiver. But there is not a large frequency gap between Band 25 DL and Band 23 UL, and hence Band 23 BS receiver desensitization may still be an issue.
Therefore, it is recommended that Bands 5 and 25 BS transmitters should not share the same antenna with Band 4, 10, 23, 41 or 43 BS receiver to prevent BS receiver desensitization, unless the antenna path meets very stringent 2nd and 3rd order PIM specification so that the PIM will not cause Band 4, 10, 23, 41 or 43 BS receiver desensitization. Note that antenna sharing may be allowed as the state-of-the-art continues to evolve in the future.
6.1.13.1.3 ΔTIB,c and ΔRIB (1 UL)
For the UE which supports CA_5A-25A the ΔTIB,c is defined for applicable bands in table 6.1.13.1.3-1.
Table 6.1.13.1.3-1: ΔTIB,c
Inter-band CA Configuration
E-UTRA Band
ΔTIB,c [dB]
CA_5A-25A
5
0.3
25
0.3
For the UE which supports CA_5A-25A the ΔRIB is defined for applicable bands in table 6.1.13.1.3-2.
Table 6.1.13.1.3-2: ΔRIB
Inter-band CA Configuration
E-UTRA Band
ΔRIB [dB]
CA_5A-25A
5
0
25
0 |
389f9b67c003a620147a83200e3331ae | 36.851 | 6.1.14 LTE Advanced Carrier Aggregation of Band 5 and Band 7 | CA_5-7 is designed to operate in the operating bands in table 6.1.14-1.
Table 6.1.14-1: Inter-band CA operating bands
E-UTRA CA Band
E-UTRA Band
Uplink (UL) band
Downlink (DL) band
Duplex
mode
BS receive / UE transmit
Channel BW (MHz)
BS transmit / UE receive
Channel BW (MHz)
FUL_low – FUL_high
FDL_low – FDL_high
CA_5-7
5
824 MHz
–
849 MHz
1.4, 3, 5, 10
(Note 1)
869 MHz
–
894 MHz
1.4, 3, 5, 10
FDD
7
2500 MHz
–
2570 MHz
10,15, 20
(Note 1)
2620 MHz
–
2690 MHz
10, 15, 20
NOTE 1: The WI considers only one uplink component carrier to be used in any of the two frequency bands at any time
6.1.14.1 List of specific combination issues |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.