id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 214
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
32.626
|
Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
11.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.626/32626-b20.zip
|
The TS 32.62x-series (Generic Network Resources IRP) define an Integration Reference Point (IRP) through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Network Management related information to one or several "IRPManagers" (typically Network Managers).
This TS-family specifies a generic Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Information Object Classes (IOCs) and Managed Object Classes (MOCs).
The present document specifies the Solution Sets for the Generic NRM IRP.
These Solution Set specifications are related to 3GPP TS 32.622 V11. 1.X [4].
|
32.631
|
Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.631/32631-b00.zip
|
The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Core Network Resources IRP.
|
32.632
|
Telecommunication management; Configuration Management (CM); Core Network Resources Integration Reference Point (IRP); Network Resource Model (NRM)
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.632/32632-b00.zip
|
The present document is part of an Integration Reference Point (IRP) named "Core Network Resources IRP", through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several 'IRPManagers' (typically Network Managers) concerning CN resources.
The present document specifies the protocol neutral Core Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in 3GPP TS 32.622 [16], either by direct reuse or sub-classing, and in addition to that defines CN specific Information Object Classes.
Finally, in order to access the information defined by this NRM, an Interface IRP is needed, such as the Basic CM IRP 3GPP TS 32.60x [17]. However, which Interface IRP that is applicable is outside the scope of the present document.
|
32.636
|
Telecommunication management; Configuration Management (CM); Core network resources Integration Reference Point (IRP); Solution Set (SS) Definitions
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.636/32636-b00.zip
|
The purpose of the present document is to define the mapping of the IRP information model (see TS 32.632 [3]) to the protocol specific details necessary for implementation of this IRP in a specific solution set environment.
This Solution Set specification is related to 3GPP TS 32.632 V11.0.X.
|
32.641
|
Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.641/32641-b00.zip
|
The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: UTRAN Network Resources IRP.
|
32.642
|
Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Network Resource Model (NRM)
|
TS
|
11.5.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.642/32642-b50.zip
|
The present document specifies the UTRAN network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
The present document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding.
|
32.646
|
Telecommunication management; Configuration Management (CM); UTRAN network resources Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
11.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.646/32646-b20.zip
|
The present document specifies the Solution Sets for the UTRAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.642 V11.4.X [4].
|
32.651
|
Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.651/32651-b00.zip
|
The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: GERAN Network Resources IRP.
|
32.652
|
Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Network Resource Model (NRM)
|
TS
|
11.2.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.652/32652-b21.zip
|
The present document specifies the GERAN network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
This document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding.
|
32.656
|
Telecommunication management; Configuration Management (CM); GERAN network resources Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
11.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.656/32656-b20.zip
|
The present document specifies the Solution Sets for the GERAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.652 V11.2.X [4].
|
32.671
|
Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.671/32671-b00.zip
|
The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2] and 3GPP TS 32.600 [3], the requirements for the present IRP: State Management.
|
32.672
|
Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Information Service (IS)
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.672/32672-b00.zip
|
The present document defines the Information Service (IS) part of the State Management IRP. It specifies the semantics of the network resource state and status information visible across the Itf-N. It also specifies the interaction required for the management of the state and status information.
The state and status attributes specified in this document shall be used, where applicable, as attributes in Information Object Class (IOC) definitions of other 3GPP IRPs. When used by the IOC definition, the semantics of the state and status attributes can be qualified and enhanced if deemed necessary.
|
32.676
|
Telecommunication management; Configuration Management (CM); State Management Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.676/32676-b00.zip
|
The present document specifies the Solution Set (SS) definitions for the IRP whose semantics is specified in State Management IRP: Information Service (IS) (3GPP TS 32.672 [1]).
This Solution Set definitions specification is related to 3GPP TS 32.672 V11.0.X.
|
32.691
|
Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP): Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.691/32691-b00.zip
|
The present document defines , in addition to the requirements defined in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2] and 3GPP TS 32.600 [3], the requirements for the present IRP: Inventory Management network resources IRP.
|
32.692
|
Telecommunication management; Inventory Management (IM) network resources Integration Reference Point (IRP); Network Resource Model (NRM)
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.692/32692-b00.zip
|
The present document defines an Integration Reference Point (IRP) through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Network Management related information to one or several 'IRPManagers' (typically Network Managers).
The present document specifies an Inventory Management Network Resource Model, NRM (also referred to as a Management Information Model - MIM) with definitions of Information Object Classes.
|
32.696
|
Telecommunication management; Inventory Management (IM) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
11.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.696/32696-b10.zip
|
The present document provides the NRM-specific part related to the Inventory Management NRM IRP IS in 3GPP TS 32.692 [1] of solution set definitions.
This Solution Set definitions specification is related to 3GPP TS 32.692 V110..X.
|
32.711
|
Telecommunication management; Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.711/32711-b00.zip
|
The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point.
|
32.712
|
Telecommunication management; Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)
|
TS
|
11.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.712/32712-b10.zip
|
The present document is part of an Integration Reference Point (IRP) named "Transport Network (TN) Interface Network Resource Model (NRM) IRP ", through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several "IRPManagers" (typically Network Managers) concerning Transport resources. The "Transport Network (TN) Interface Network Resource Model (NRM) IRP" comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document:
1. specifies the protocol neutral Transport Network Interface Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in TS 32.622 [6], either by direct reuse or sub-classing, and in addition to that defines Transport specific Managed Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs - as described in the Introduction clause above. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service.
In order to access the information defined by this NRM, an IRP Information Service (IS) is needed, such as the Basic CM IRP: IS (TS 32.602 [7]) or the Bulk CM IRP: IS (TS 32.612 [8]). However, which Information Service that is applicable is outside the scope of this document.
Finally, regarding the support of the State Management IRP: IS (TS 32.672 [3]), all NRM's of one release shall support the same State Management IRP version.
This specification is related to 3GPP TS 32.672.
|
32.716
|
Telecommunication management; Configuration Management (CM); Transport Network (TN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.716/32716-b00.zip
|
The present document is part of an Integration Reference Point (IRP) named Transport Network (TN) interface Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning TN resources. The TN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the TN NRM IRP.
This specification is related to 3GPP TS 32.712 [4] V11.0.X.
|
32.721
|
Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.721/32721-b00.zip
|
The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [1], 3GPP TS 32.102 [2] and 3GPP TS 32.600 [3], the requirements for the present Repeater network resources IRP.
|
32.722
|
Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); information Service (IS)
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.722/32722-b00.zip
|
The present document is part of an Integration Reference Point (IRP) named "Repeater Network Resources IRP", through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several "IRPManagers" (typically Network Managers) concerning Repeater resources. The "Repeater Network Resources IRP" comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document specifies the protocol neutral Repeater Network Resources IRP: Network Resource Model.
It reuses relevant parts of the generic NRM in TS 32.622 [10] and 32.642 [5], either by direct reuse or sub-classing, and in addition to that defines Repeater specific Information Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs – as described in the Introduction clause above. An important aspect of such a split is that the Network Resource Models (NRMs) defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service (IS).
To summarize, the present document has the following main purpose: to define the applied Repeater specific NRM, based on the generic NRM in 3GPP TS 32.622 [10].
In order to access the information defined by this NRM, an IRP IS is needed, such as the Basic CM IRP IS (3GPP TS 32.602[11]) or the Bulk CM IRP IS (3GPP TS 32.612 [12]). However, which IS that is applicable is outside the scope of the present document.
|
32.726
|
Telecommunication management; Configuration Management (CM); Repeater network resources Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.726/32726-b00.zip
|
The present specifies the Solution Set definitions for the IRP whose semantics are specified in the Repeater Network Resources IRP NRM Information Service (3GPP TS 32.722 [1]).
This Solution Set specification is related to TS 32.722 v11.0.X.
|
32.731
|
Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.731/32731-b00.zip
|
The present document defines, in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: IMS Network Resource Model (NRM) IRP.
|
32.732
|
Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.732/32732-b00.zip
|
The present document is part of an Integration Reference Point (IRP) named IMS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning IMS resources. The IMS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the protocol neutral IMS NRM IRP: Information Service (IS). It reuses relevant parts of the Generic NRM IRP: IS in 3GPP TS 32.622 [9], either by direct reuse or sub-classing, and in addition to that defines IMS specific Information Object Classes.
Finally, in order to access the information defined by this NRM, an Interface IRP is needed, such as the Basic CM IRP in 3GPP TS 32.602 [10]. However, which Interface IRP that is applicable is outside the scope of the present document.
|
32.736
|
Telecommunication management; IP Multimedia Subsystem (IMS) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.736/32736-b00.zip
|
The present document specifies the Solution Set definitions for the IRP whose semantics is specified in IMS (IP Multimedia Subsystem) NRM (Network Resource Model) IRP: Information Service 3GPP TS 32.732 [3].
This Solution Set definitions specification is related to 3GPP TS 32.732 V10.1.X.
|
32.741
|
Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.741/32741-b00.zip
|
The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the Signalling Transport Network (STN) interface NRM IRP.
|
32.742
|
Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.742/32742-b00.zip
|
The present document is part of an Integration Reference Point (IRP) named "Signalling Transport Network (STN) network resources IRP", through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several "IRPManagers" (typically Network Managers) concerning Signalling Transport resources. This IRP comprises a set of specifications defining Requirements, a protocol neutral Network Resource Model (NRM) and corresponding Solution Set(s).
The present document specifies the protocol neutral STN resources IRP NRM. It reuses relevant parts of the generic NRM in TS 32.622 [6], either by direct reuse or sub-classing, and in addition to that defines Signalling Transport specific Managed Object Classes.
The Configuration Management (CM) area is very large. The intention is to split the specification of the related interfaces in several IRPs - as described in the Introduction clause above. An important aspect of such a split is that the NRMs defined in different IRPs containing NRMs are consistent, and that NRMs supported by an IRPAgent implementation can be accessed as one coherent model through one IRP Information Service (IS).
To summarize, the present document has the following main purpose: to define the applied Signalling Transport Network specific NRM, based on the generic NRM in 3GPP TS 32.622 [6].
In order to access the information defined by this NRM, an IRP IS is needed, such as the Basic CM IRP: IS (TS 32.602 [7]) or the Bulk CM IRP: IS (TS 32.612 [8]). However, which IS is applicable is outside the scope of this document.
Finally, regarding the support of the State Management IRP: IS (TS 32.672 [3]), all NRMs of one release shall support the same State Management IRP version.
|
32.746
|
Telecommunication management; Configuration Management (CM); Signalling Transport Network (STN) interface Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.746/32746-b00.zip
|
The present document is part of an Integration Reference Point (IRP) named Signalling Transport Network (STN) interface Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning STN resources. The STN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the STN NRM IRP.
This specification is related to 3GPP TS 32.742 [9] V11.0.X.
|
32.751
|
Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.751/32751-b00.zip
|
The present document defines, in addition to the requirements defined in [1], [2] and [3], the Requirements for the EPC Network Resource Model (NRM) IRP.
|
32.752
|
Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)
|
TS
|
11.0.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.752/32752-b01.zip
|
The present document specifies the protocol neutral EPC Network Resource Model IRP Information Service, through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate information to one or several 'IRPManagers' (typically Network Managers) concerning EPC resources. It reuses relevant parts of the Generic NRM in 3GPP TS 32.622 [6], either by direct reuse or sub-classing, and in addition to that defines EPC specific Information Object Classes.
In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (3GPP TS 32.602 [7]). However, which Interface IRP is applicable is outside the scope of the present document.
|
32.756
|
Telecommunication management; Evolved Packet Core (EPC) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) Definitions
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.756/32756-b00.zip
|
The TS 32.75x-series (EPC NRM IRP) define an Integration Reference Point (IRP) named EPC Network Resource Model (NRM) IRP, through which an "IRPAgent" (typically an Element Manager or Network Element) can communicate Network Management related information to one or several "IRPManagers" (typically Network Managers).
The present document provides solution set definitions for EPC Network Resources IRP, which define the mapping of the IRP information model (see TS 32.752 [2]) to the protocol specific details necessary for implementation of this IRP.
This Solution Set definitions specification is related to 3GPP TS 32.752 [2] v11.0.X.
|
32.761
|
Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements
|
TS
|
11.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.761/32761-b10.zip
|
The present document defines, in addition to the requirements defined in [1], [2] and [3], the Requirements for the E‑UTRAN Network Resource Model (NRM) IRP.
|
32.762
|
Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)
|
TS
|
11.7.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.762/32762-b70.zip
|
The present document is part of an Integration Reference Point (IRP) named E-UTRAN Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning E-UTRAN resources. The E-UTRAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the protocol neutral E-UTRAN NRM IRP: Information Service (IS). It reuses relevant parts of the Generic NRM IRP: IS in 3GPP TS 32.622 [6], either by direct reuse or sub-classing, and in addition to that defines E-UTRAN specific Information Object Classes.
In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (3GPP TS 32.602 [7]). However, which Interface IRP is applicable is outside the scope of the present document.
|
32.766
|
Telecommunication management; Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
11.9.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.766/32766-b90.zip
|
The present document is part of an Integration Reference Point (IRP) named E-UTRAN Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning E-UTRAN resources. The E-UTRAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the E-UTRAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.762 V11. 7.X [4].
|
32.771
|
Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.771/32771-b00.zip
|
The document describes the requirements for Home NodeB Subsystem (HNS), which includes Home NodeB (HNB) and Home NodeB gateway (HNB GW). The HNS NRM IRP requirements are targeted on both HNB and HNB GW NRM.
|
32.772
|
Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Information Service (IS)
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.772/32772-b00.zip
|
The present document is an Integration Reference Point (IRP) named "Home Node B Subsystem (HNS) network resources IRP ", through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several 'IRPManagers' (typically Network Managers) concerning HNS resources.
The present document specifies the protocol neutral HNS Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in 3GPP TS 32.622 [6], either by direct reuse or sub-classing, and in addition to that defines HNS specific Information Object Classes.
In order to access the information defined by this NRM, an IRP IS is needed, such as the Basic CM IRP IS (3GPP TS 32.602 [7]) or the Bulk CM IRP IS (3GPP TS 32.612 [8]). However, which IS that is applicable is outside the scope of the present document.
The present document (NRM specification) is related to the IS in 3GPP TS 32.672 [9]
|
32.776
|
Telecommunication management; Home Node B (HNB) Subsystem (HNS); Network Resource Model (NRM); Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.776/32776-b00.zip
|
The present document is part of an Integration Reference Point (IRP) named HNS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning HNS resources. The HNS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the HNS NRM IRP.
This specification is related to 3GPP TS 32.772 V11.0.X.
|
32.781
|
Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.781/32781-b00.zip
|
The document describes the requirements for Home eNodeB Subsystem (HeNS), which include Home eNodeB (HeNB) and Home eNodeB gateway (HeNB GW). The HeNS NRM IRP requirements are targeted on both HeNB and HeNB GW NRM.
|
32.782
|
Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP): Information Service (IS)
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.782/32782-b00.zip
|
The present document is an Integration Reference Point (IRP) named " Home enhanced Node B Subsystem (HeNS) Network Resources IRP", through which an 'IRPAgent' (typically an Element Manager or Network Element) can communicate Configuration Management information to one or several 'IRPManagers' (typically Network Managers) concerning HeNB-GW resources.
The present document specifies the protocol neutral HeNS Network Resources IRP: Network Resource Model. It reuses relevant parts of the generic NRM in 3GPP TS 32.622 [5], either by direct reuse or sub-classing, and in addition to that defines HeNB-GW specific Information Object Classes.
In order to access the information defined by this NRM, an IRP IS is needed, such as the Basic CM IRP IS (3GPP TS 32.602 [6]) or the Bulk CM IRP IS (3GPP TS 32.612 [7]). However, which IS that is applicable is outside the scope of the present document.
The present document (NRM specification) is related to the IS in 3GPP TS 32.672 [8]
|
32.786
|
Telecommunication management; Home enhanced Node B (HeNB) Subsystem (HeNS); Network Resource Model (NRM); Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.786/32786-b00.zip
|
The present document is part of an Integration Reference Point (IRP) named HeNS Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning HeNS resources. The HeNS NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the HeNS NRM IRP.
This Solution Set specification is related to 3GPP TS 32.782 V11.0.X.
|
32.791
|
Telecommunication management; Common Radio Access Technology (RAT) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.791/32791-b00.zip
|
The present document defines, in addition to the requirements defined in 3GPP TS 32.101 [2], 3GPP TS 32.102 [3] and 3GPP TS 32.600 [4], the Requirements for the Common RAT NRM IRP for equipment that may be shared between BSS in GSM, UTRAN and E‑UTRAN.
The present document can be used also for managing the equipment that can be shared by several RATs, even in the cases when it is not being shared.
|
32.792
|
Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Information Service (IS)
|
TS
|
11.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.792/32792-b10.zip
|
The present document specifies the Generic Radio Access Network (RAN) network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
This document specifies the semantics and behaviour of information object class attributes and relations visible across the reference point in a protocol and technology neutral way. It does not define their syntax and encoding.
This document specifies equipment that may be shared between BSS in GSM, UTRAN and E‑UTRAN.
In order to access the information defined by this NRM, an Interface IRP such as the "Basic CM IRP" is needed (3GPP TS 32.602 [5]). However, which Interface IRP is applicable is outside the scope of the present document.
|
32.796
|
Telecommunication management; Generic Radio Access Network (RAN) Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.796/32796-b00.zip
|
The present document is part of an Integration Reference Point (IRP) named Generic Radio Access Network (RAN) Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning Generic RAN resources. The Generic RAN NRM IRP comprises a set of specifications defining Requirements, a protocol neutral Information Service and one or more Solution Set(s).
The present document specifies the Solution Sets for the Generic RAN NRM IRP.
This Solution Set specification is related to 3GPP TS 32.792 V11.0.X [4].
|
32.833
|
Telecommunication management; Study on management of converged networks
|
TR
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.833/32833-b00.zip
|
The present document investigates which new functionalities regarding a true end to end management are enabled by a converged OSS. The fragments looked at are Fault Management, Performance Management and Configuration Management.
|
32.834
|
Study on Operations, Administration and Maintenance (OAM) aspects of inter-Radio-Access-Technology (RAT) energy saving
|
TR
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.834/32834-b00.zip
|
General material - [2], [3] - and detailed material - [4], [5], [6] - on Energy Saving and/or its Management aspects have been created by 3GPP. The present document focuses on Inter-RAT aspects of Energy Saving, i.e. reducing the capabilities of one RAT to reduce its energy consumption while providing a back-up by another RAT. Concepts and scenarios described in [2], [3] and methods defined in [4], [5], [6] as well as additions to them are analysed to identify the most favourable management solutions in this context and their possible limitations.
The following RATs are considered in this study: GSM, UMTS; LTE, CDMA.
|
32.853
|
Telecommunication management; Final report from the 3GPP - TM Forum Joint Work Group (JWG) on fault management harmonization
|
TR
|
11.1.1
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.853/32853-b11.zip
| |
32.854
|
Telecommunication management; Fixed Mobile Convergence (FMC) 3GPP / TM Forum concrete model relationships and use cases
|
TR
|
11.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.854/32854-b10.zip
|
This document sets out a number of independent operator activity contexts where each context has been chosen to exercise one or more of the operator requirements and to lead to points of intersection of the network model work of 3GPP and TM Forum where some degree of harmonisation would consequently seem valuable.
Each context description focuses on one or more use cases that suitably describe the relevant details of that operator activity with respect to an expected area of intersection. The use cases are first explained and then depicted via one or more stylized network and model diagrams. The model diagram is then developed to a formal model structure.
Finally the set of changes proposed cumulated from all context analyses are provided as a coherent recommendation. Respective concrete models must use this model to support the FMC use cases to claim FMC network management compliance.
It should be noted that the UIM cannot be used directly for implementation. Implementation classes must be derived from those in the UIM by Inheritance or some other appropriate mechanism. Classes derived from those in the UIM (e.g. for the fixed environment) must use different names from those used in the UIM.
This content of this document has been jointly developed by 3GPP and TM Forum as part of the Joint Working Group on Resource Model Alignment [11].
|
33.816
|
Feasibility study on LTE relay node security
|
TR
|
10.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.816/33816-a00.zip
|
The present document provides an analysis of the security issues by including Relay Nodes (RN) into the LTE network. Furthermore it contains several solutions to provide security for the relay architecture chosen by the RAN groups. It also provides a comparison between those solution and the reasoning why a particular solution was chosen.
|
33.828
|
IP Multimedia Subsystem (IMS) media plane security
|
TR
|
11.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.828/33828-b10.zip
| |
33.830
|
Feasibility study on IMS firewall traversal
|
TR
|
0.5.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.830/33830-050.zip
|
The present document:
a) studies requirements and scenarios for traversal of IMS services over IMS-unaware firewalls
(Non-IMS Aware Firewall - NIMSFW); and
b) studies mechanisms (based on both secure and non-secure tunnels), which can be used for traversal of IMS services over IMS-unaware firewalls.
'
|
33.838
|
Study on Protection against Unsolicited Communication for IMS (PUCI)
|
TR
|
11.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.838/33838-b00.zip
|
The present document studies more focussed the high-level solutions possibilities for PUCI described in the technical report (TR 33.937) on PUCI.
The scope of the study includes:
- Study of the PUCI related information:
- What information to be stored in the HSS.
- Type of PUCI information to be exchanged (e.g. scoring information, contextual information) and how this information should be structured, or even between which nodes the information should be sent.
- If and how PUCI information should be sent inside SIP.
- Study on Invoking of 3rd party PUCI AS or Supplementary Services (SS) depending on configuration.
- Interworking
- with non-IMS networks.
- with other IMS services like SRVCC, ICS, and service continuity.
- Types of communication that should/can be covered by PUCI, and how the different types of communication affect the PUCI solution.
- How much of PUCI that can be achieved via prevention and how much needs to be done via treatment.
- PUCIF to PUCIF communication.
- Use of existing methods of user notification for PUCI communication.
- Mitigation of source identity spoofing, especially from non-IMS networks, on the effectiveness of the PUCI mechanism.
- Illustrative use of standardized PUCI features in typical deployment scenarios.
|
33.844
|
Security Study on IP Multimedia Subsystem (IMS) based peer-to-peer content distribution services; Stage 2
|
TR
|
11.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.844/33844-b00.zip
|
The present document provides an analysis of security aspects of the enhancements of IMS to support Peer-to-Peer Content Distribution Services based on the requirements studied in TR 22.906 [2] and architecture studied in TR 23.844 [3]. This analysis focuses on both the network and terminal and includes security threats, requirements and solutions.
|
33.859
|
Study on the Introduction of Key Hierarchy in Universal Terrestrial Radio Access Network (UTRAN)
|
TR
|
11.1.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/33_series/33.859/33859-b10.zip
|
The objective of this work item is to study potential solutions for introducing an "E-UTRAN-like" key hierarchy in UTRAN, to improve the security level in UTRAN in the presence of the new deployment scenarios and to ensure that a security breach in UTRAN will not propagate into E-UTRAN. The study covers the technical feasibility and consequences. The impacts of such potential solution on UTRAN of earlier releases are identified. Interworking with earlier releases of UTRAN, GERAN and E-UTRAN is also studied.
The UTRAN key hierarchy is assumed to be built on top of (R99+) UMTS AKA, without requiring any changes to the authentication protocol or USIM. Therefore, it could in principle be used also in GERAN as long as USIMs are used and the SGSN, MSC/VLR, and ME are updated. However, the benefit of introducing the key hierarchy in GPRS is smaller than for the circuit switched part, as the traffic protection already terminates in the core network. Solution details for GERAN are not discussed further.
The study covers both PS and CS part of UTRAN.
|
34.122
|
Terminal conformance specification; Radio transmission and reception (TDD)
|
TS
|
11.13.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.122/34122-bd0.zip
|
This present document specifies the measurement procedure for the conformance test of the mobile station that contain transmitting characteristics, receiving characteristics and performance requirements in addition to requirements for support of RRM (Radio Resource Management) in both UTRATDD modes. The two options are the 3,84 Mcps TDD Option and 1,28 Mcps TDD Option, respectively.
The requirements are listed in different clauses only if the corresponding parameters deviate. More generally, tests are only applicable to those mobiles that are intended to support the appropriate functionality. To indicate the circumstances in which tests apply, this is noted in the “definition and applicability” part of the test.
For example only release 5 and later UE declared to support HSDPA shall be tested for this functionality. In the event that for some tests different conditions apply for different releases, this is indicated within the text of the test itself.
|
34.229-4
|
Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); User Equipment (UE) conformance specification; Part 4: Enabler for IP multimedia applications testing
|
TS
|
11.0.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.229-4/34229-4-b00.zip
|
The present document specifies the protocol conformance testing in TTCN-3 for the 3GPP User Equipment (UE) at the Gm interface for the basic IMS test cases using the so-called IP-CAN test model. It also forms the basis for further conformance testing for IM applications.
The present document is the 4th part of a multi-part test specification, 3GPP TS 34.229. The following TTCN test specification and design considerations can be found in the present document:
- the overall test suite structure;
- the testing architecture;
- the test methods and PCO definitions;
- the test configurations;
- the design principles, assumptions, and used interfaces to the TTCN tester (System Simulator);
- TTCN styles and conventions;
- the partial PIXIT proforma;
- the TTCN-3 files for the mentioned protocols tests.
The present document is valid for UEs implemented according 3GPP Releases starting from Release 5 up to the Release indicated on the cover page of the present document.
|
34.902
|
Derivation of test tolerances for multi-cell Radio Resource Management (RRM) conformance tests
|
TR
|
11.3.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/34_series/34.902/34902-b30.zip
|
The present document specifies a method used to derive Test Tolerances for multi-cell Radio Resource Management tests, and establishes a system for relating the Test Tolerances to the measurement uncertainties of the Test System.
The present document is applicable to Release 99 up to the release indicated on the front page of the present Terminal conformance specifications.
|
36.816
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Study on signalling and procedure for interference avoidance for in-device coexistence
|
TR
|
11.2.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.816/36816-b20.zip
|
The present document is intended to capture the output of the study item on Signalling and procedure for interference avoidance for in-device coexistence, which was approved at TSG RAN#48.
The objective of the SI is to investigate suitable mechanisms for interference avoidance from signalling and procedure point of view to facilitate the coexistence scenario that LTE and GPS/ ISM radio within the same device working in adjacent frequencies or sub-harmonic frequencies. The work under this study should take the following steps:
（1） Evaluate whether existing RRM mechanisms could be utilized to effectively solve the coexistence problems that arise in supporting the scenarios abovementioned and guarantee the required QoS in LTE with proper GPS/ISM operation.
（2） If legacy signaling and procedure are not sufficient to ensure required performance in the interested coexistence scenario, study enhanced mechanisms to better avoid interference and mitigate the impact caused by ISM radio.
Impact on legacy LTE UEs should be minimized.
NOTE: The candidate solutions should be firstly considered in the non-CA (carrier aggregation) cases.
|
36.819
|
Coordinated multi-point operation for LTE physical layer aspects
|
TR
|
11.2.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.819/36819-b20.zip
|
This document is related to the technical report for physical layer aspect of the study item “Coordinated Multi-Point Operation for LTE” [1]. The purpose of this TR is to help TSG RAN WG1 to define the physical layer features and enhancements under consideration to operate multi-point coordination and assess the performance benefits of those features and the required specification support for both the downlink and the uplink.
This activity involves the Radio Access work area of the 3GPP studies and has impacts both on the Mobile Equipment and Access Network of the 3GPP systems.
This document is intended to gather all information and draw a conclusion on way forward.
This document is a ‘living’ document, i.e. it is permanently updated and presented to TSG-RAN meetings.
|
36.820
|
LTE for 700 MHz digital dividend
|
TR
|
11.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.820/36820-b20.zip
|
The present document a technical report for the LTE for 700 MHz digital dividend work item. It is intended to define both FDD and TDD arrangements on the 698-806 MHz frequency band in Region 3.
|
36.822
|
LTE Radio Access Network (RAN) enhancements for diverse data applications
|
TR
|
11.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.822/36822-b00.zip
|
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.
|
36.823
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Carrier aggregation enhancements; User Equipment (UE) and Base Station (BS) radio transmission and reception
|
TR
|
11.0.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.823/36823-b01.zip
|
The purpose of this report is to summarize studies of radio requirements for the Base Station (BS) and User Equipment (UE) radio transmission and reception as part of the Rel-11 work on LTE Carrier Aggregation Enhancements.
|
36.824
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE coverage enhancements
|
TR
|
11.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.824/36824-b00.zip
|
The scope of this study item is given in [2].
|
36.826
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Relay radio transmission and reception
|
TR
|
11.3.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.826/36826-b30.zip
|
The present document is the technical report on the "Relays for LTE” work item [2]. The overall objective of the WI is to specify Relays for LTE in Rel-10 timeframe.
This document is intended to gather the relevant background information in order to address Relay Node (RN) requirements as well as propose suitable updates to the specifications under the responsibility of RAN4. RAN4 have agreed to focus on fixed RN.
|
36.828
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Further enhancements to LTE Time Division Duplex (TDD) for Downlink-Uplink (DL-UL) interference management and traffic adaptation
|
TR
|
11.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.828/36828-b00.zip
|
The scope of this study item is given in [2]
|
36.829
|
Enhanced performance requirement for LTE User Equipment (UE)
|
TR
|
11.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.829/36829-b10.zip
|
The objective of this study is to evaluate the feasibility and potential performance improvements of interference cancellation/mitigation techniques for LTE/ LTE-Advanced FDD and TDD UE receivers, based on realistic network scenarios. Scope of the work includes:
▪ Identify realistic deployment scenarios, traffic models, interference models, and performance metrics to evaluate the performance of advanced receiver to mitigate inter-cell interference.
- Evaluation should be based on realistic modelling of inter-cell interference, including both synchronous and asynchronous operations among macro eNBs, different precoders, ranks and powers applied over consecutive subframes, and effect of CRS and control channels to which different precoder is applied compared with data channels.
▪ Study and evaluate feasibility and potential gain by advanced receiver at link and system levels:
- Identify the scenarios and conditions where inter-cell interference mitigation is effective
- Identify the receiver structures that could be a baseline to specify performance requirement.
▪ Receiver structures targeting spatial domain interference mitigation such as IRC are to be considered as a starting point.
▪ Receiver structures targeted to TDM-eICIC are only to be studied under the eICIC enhancements WI.
▪ Details of interference modelling for performance requirements and conformance testing shall be specified in the WI phase. Some complexity considerations should be taken into account during the SI phase to avoid over simplified model later on that doesn’t reflect the performance benefits found.
|
36.833-1-07
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 7
|
TR
|
11.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-1-07/36833-1-07-b00.zip
|
The present document is a technical report of the work item for LTE Advanced Carrier Aggregation in Band 7 which was approved at TSG RAN #53 [2]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
36.833-1-38
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 38
|
TR
|
11.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-1-38/36833-1-38-b10.zip
|
The present document is a technical report of the work item for LTE Advanced Carrier Aggregation in Band 38 which was approved at TSG RAN #52 [2]. The report provides background, analysis of the requirements, and a list of recommended changes to the specifications.
|
36.833-1-41
|
Evolved Universal Terrestrial Radio Access (E-UTRA); LTE-Advanced intra-band contiguous Carrier Aggregation (CA) in Band 41
|
TR
|
11.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.833-1-41/36833-1-41-b00.zip
|
The present document is a technical report of the LTE Advanced Carrier Aggregation in Band 41 work item which was approved at TSG RAN #52 [2]. The objective of this work item is to provide specification support for intra-band contiguous carrier aggregation in LTE TDD Band 41.
The report provides motivation, requirements and a list of recommended changes to the specifications.
|
36.837
|
Public safety broadband high power User Equipment (UE) for band 14
|
TR
|
11.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.837/36837-b00.zip
|
The present document is the Technical Report on Public safety broadband high power User Equipment (UE) for Band 14 for Region 2.
The purpose of this TR is to study the radio requirements for Public safety broadband high power User Equipment (UE) as part of the Rel-11 work item for a new Power Class for Band 14 for Region 2. The normative requirements resulting from this TR will be addressed in the applicable release 11 Technical Specifications (TS)
|
36.839
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Mobility enhancements in heterogeneous networks
|
TR
|
11.1.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.839/36839-b10.zip
|
The present document is intended the capture the output of the Study Item on HetNet mobility improvements for LTE.
The study aims to look at various mobility improvements such as possible improvements to support seamless and robust mobility of users between LTE macro to pico cells in Heterogeneous networks, better strategies to identify and evaluate small cells, handover performance with and without eICIC features, improvements to re-establishment procedures etc. It is also expected to consider these in the context of Carrier aggregation in Home eNodeBs.
|
36.850
|
Inter-band carrier aggregation
|
TR
|
11.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.850/36850-b20.zip
|
The present document is a technical report for Inter-band Carrier Aggregation under Rel-11 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-11 band combinations in table 1-1.
Table 1-1: Release 11 inter-band carrier aggregation combinations
WI code
WI title
Class
LTE_CA_B3_B7
LTE Advanced Carrier Aggregation of Band 3 and Band 7
A3
LTE_CA_B4_B17
LTE Advanced Carrier Aggregation of Band 4 and Band 17
A2
LTE_CA_B4_B13
LTE Advanced Carrier Aggregation of Band 4 and Band 13
A1
LTE_CA_B4_B12
LTE Advanced Carrier Aggregation of Band 4 and Band 12
A2
LTE_CA_B5_B12
LTE Advanced Carrier Aggregation of Band 5 and Band 12
A3
LTE_CA_B7_B20
LTE Advanced Carrier Aggregation of Band 7 and Band 20
A1
LTE_CA_B2_B17
LTE Advanced Carrier Aggregation of Band 2 and Band 17
A1
LTE_CA_B4_B5
LTE Advanced Carrier Aggregation of Band 4 and Band 5
A1
LTE_CA_B5_B17
LTE Advanced Carrier Aggregation of Band 5 and Band 17
A3
LTE_CA_B3_B20
LTE Advanced Carrier Aggregation of Band 3 and Band 20
A1
LTE_CA_B8_B20
LTE Advanced Carrier Aggregation of Band 8 and Band 20
A3
LTE_CA_B3_B5
LTE Advanced Carrier Aggregation of Band 3 and Band 5
A1
LTE_CA_B4_B7
LTE Advanced Carrier Aggregation of Band 4 and Band 7
A3
LTE_CA_B11_B18
LTE Advanced Carrier Aggregation of Band 11 and Band 18
A5
LTE_CA_B1_B18
LTE Advanced Carrier Aggregation of Band 1 and Band 18
A1
LTE_CA_B1_B19
LTE Advanced Carrier Aggregation of Band 1 and Band 19
A1
LTE_CA_B1_B21
LTE Advanced Carrier Aggregation of Band 1 and Band 21
A5
LTE_CA_B3_B8
LTE Advanced Carrier Aggregation of Band 3 and Band 8
A2
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
The contents of this TR is moved to/provided in TR 36.852-11 Release 11 [24].
|
36.852-11
|
LTE Advanced inter-band Carrier Aggregation (CA) (2DL/1UL)
|
TR
|
11.1.1
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.852-11/36852-11-b11.zip
|
The present document is a technical report for Inter-band Carrier Aggregation under Rel-11 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-11 band combinations in table 1-1.
Table 1-1: Release 11 inter-band carrier aggregation combinations
WI code
WI title
Class
LTE_CA_B3_B7
LTE Advanced Carrier Aggregation of Band 3 and Band 7
A3
LTE_CA_B4_B17
LTE Advanced Carrier Aggregation of Band 4 and Band 17
A2
LTE_CA_B4_B13
LTE Advanced Carrier Aggregation of Band 4 and Band 13
A1
LTE_CA_B4_B12
LTE Advanced Carrier Aggregation of Band 4 and Band 12
A2
LTE_CA_B5_B12
LTE Advanced Carrier Aggregation of Band 5 and Band 12
A3
LTE_CA_B7_B20
LTE Advanced Carrier Aggregation of Band 7 and Band 20
A1
LTE_CA_B2_B17
LTE Advanced Carrier Aggregation of Band 2 and Band 17
A1
LTE_CA_B4_B5
LTE Advanced Carrier Aggregation of Band 4 and Band 5
A1
LTE_CA_B5_B17
LTE Advanced Carrier Aggregation of Band 5 and Band 17
A3
LTE_CA_B3_B20
LTE Advanced Carrier Aggregation of Band 3 and Band 20
A1
LTE_CA_B8_B20
LTE Advanced Carrier Aggregation of Band 8 and Band 20
A3
LTE_CA_B3_B5
LTE Advanced Carrier Aggregation of Band 3 and Band 5
A1
LTE_CA_B4_B7
LTE Advanced Carrier Aggregation of Band 4 and Band 7
A3
LTE_CA_B11_B18
LTE Advanced Carrier Aggregation of Band 11 and Band 18
A5
LTE_CA_B1_B18
LTE Advanced Carrier Aggregation of Band 1 and Band 18
A1
LTE_CA_B1_B19
LTE Advanced Carrier Aggregation of Band 1 and Band 19
A1
LTE_CA_B1_B21
LTE Advanced Carrier Aggregation of Band 1 and Band 21
A5
LTE_CA_B3_B8
LTE Advanced Carrier Aggregation of Band 3 and Band 8
A2
This TR contains a general part and band specific combination part. The actual requirements are added to the corresponding technical specifications.
|
36.871
|
Evolved Universal Terrestrial Radio Access (E-UTRA); Downlink Multiple Input Multiple Output (MIMO) enhancement for LTE-Advanced
|
TR
|
11.0.0
|
R1
|
https://www.3gpp.org/ftp/Specs/archive/36_series/36.871/36871-b00.zip
|
This TR collects the work done under the Study Item “Downlink MIMO Enhancement for LTE-Advanced” [2].
|
37.803
|
Universal Mobile Telecommunications System (UMTS) and LTE; Mobility enhancements for Home Node B (HNB) and Home enhanced Node B (HeNB)
|
TR
|
11.2.0
|
R3
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.803/37803-b20.zip
|
This document captures the results of the study item on H(e)NB enhanced mobility in RP-110456[2]. It identifies the existing mobility functions for UMTS and LTE, the use cases and requirements for enhancements, and reviews and compares scenarios and techniques for enhancement of the mobility functionality. Aspects of RAN sharing related to H(e)NB mobility are also included.
|
37.804
|
Study on UMTS/LTE in 900 MHz band and coexistence with 850 MHz band
|
TR
|
11.1.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.804/37804-b10.zip
|
The present document is a technical report of the UMTS/LTE in 900 MHz band study item, which was established at TSG RAN#52. The objective of the study item is to study how we can provide UTRA and E-UTRA specification support for FDD in the 900 MHz band in Japan, and also to study the possible harmonized specification support between the 900 MHz band in Japan and 900 MHz band in Korea.
|
37.806
|
Extending 850 MHz study Technical Report
|
TR
|
11.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.806/37806-b00.zip
|
The present document contains the findings of the Study Item [28] of a more harmonised frequency variant approach within the frequency range of 806-849/851-894 MHz.
|
37.809
|
Evolved Universal Terrestrial Radio Access (E-UTRA) medium range and Multi-Standard Radio (MSR) medium range / local area Base Station (BS) class requirements
|
TR
|
11.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.809/37809-b00.zip
|
The present document is the Technical Report for the Work Item on E-UTRA medium range and MSR medium range/local area BS class requirements.
|
37.812
|
Radio Frequency (RF) requirements for Multi-band and Multi-standard radio (MB-MSR) Base Station (BS)
|
TR
|
11.3.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.812/37812-b30.zip
|
The present document is the Technical Report for the Work Item on Multi-band and Multi-standard radio BS requirements.
|
37.868
|
RAN Improvements for Machine-type Communications
|
TR
|
11.0.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/37_series/37.868/37868-b00.zip
|
The present document is intended to capture the output of the Study Item on RAN Improvements for Machine-type Communications.
The study aims to study the traffic characteristics of different M2M applications with machine-type communications and define new traffic models based on these findings. RAN enhancements for UTRA and EUTRA to improve the support of machine-type communications based on the SA1 requirements should be studied.
The RAN improvements should enable or improve the usage of RAN resources efficiently, and/or reduce the complexity when a large number of machine-type communications devices possibly need to be served based on the existing features as much as possible. Meanwhile, minimize the changes of existing specifications and the impaction of Human-to-Human terminals in order to keep the complexity related to M2M optimizations at a minimum level.
|
44.160
|
General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol Iu mode
|
TS
|
11.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/44_series/44.160/44160-b00.zip
| |
45.860
|
Signal Precoding Enhancements for EGPRS2 DL
|
TR
|
11.5.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/45_series/45.860/45860-b50.zip
|
The present document contains the results from the 3GPP study item on Signal Precoding Enhancements for EGPRS2 DL, SPEED.
The following is covered by the study:
• Objectives for the study
• Common assumptions to be used in the evaluation
• Technical work and performance evaluations based on the objectives
|
21.902
|
Evolution of 3GPP system
|
TR
|
10.0.0
|
SP
|
https://www.3gpp.org/ftp/Specs/archive/21_series/21.902/21902-a00.zip
|
The present document describes a long term, high level roadmap, intended to guide the future work of 3GPP. It is focussed on items pertinent to the evolution of 3GPP specifications, and identifies concepts and trends to be considered by 3GPP when defining future work items. It does not contain details of proposed technologies, rather it contains pointers to direct the activities of the appropriate TSGs in elaborating future releases of the 3GPP standard. As a result, not all of the topics covered herein are within the remit of 3GPP to discuss, and description of such items will not be extensively developed. E.g. Spectrum is an ITU-R/WRC issue and therefore outside the scope of 3GPP. The document is designed to be a "living document" and will be updated accordingly over its lifetime in order to reflect future developments and innovations.
|
22.813
|
Study of use cases and requirements for enhanced voice codecs for the Evolved Packet System (EPS)
|
TR
|
10.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.813/22813-a00.zip
|
This study defines and analyses the new use cases in the environment of EPS and its future services. It evaluates how much the newly defined requirements are met by the already available codecs in 3GPP releases prior to Rel-10. Potential new requirements for voice codecs are elaborated in due course.
Specifically, the objective of this study item is to:
• Identify service and system requirements,
• Identify high level requirements,
• Assess the existing codecs in respect to identified requirements,
• Define a strategy for EPS voice codec(s) standardization,
• Identify some use cases for enhanced voice and mixed content conversational multimedia service for EPS (see Annex A).
Starting from Rel-8 timeframe, MTSI as a conversational multimedia service is provided over EPS. MTSI is the main service for which the enhancements are targeted. This does not however exclude the enhanced service requirements from being later adopted to other services where such enhancements are needed and are found suitable.
|
22.814
|
Location Services (LCS) support in Evolved Packet Core (EPC) for non-3GPP accesses
|
TR
|
10.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.814/22814-a00.zip
|
This Technical Report (TR) presents the results of the Study on LCS support for non-3GPP accesses.
One main concept of EPC is to support a variety of different access systems (existing and future) ensuring mobility and service continuity between these access systems. In that perspective, the LCS support for non 3GPP accesses should be also taken into account. However, historically, TS 22.071 has been applicable only to 3GPP accesses and any new requirements for non 3GPP accesses have not been discussed yet.
Therefore we need to consider how to support LCS in EPC for non 3GPP accesses, e.g. 3GPP2 and WiMAX. Supporting LCS in EPC for non 3GPP access does not necessarily mean that all positioning methods available in various kinds of non 3GPP accesses should be supported in EPC or inventing new positioning methods for other accesses. However, how to realize the presentation of location information in EPC when users are connected in non 3GPP accesses should be at least taken into account. In addition, the service scenarios should be discussed whether new service requirements are needed for the users camping on non 3GPP accesses through EPC.
This work will examine whether requirements in TS 22.071 would be applicable for non 3GPP accesses and specify new service requirements for the users connected to non 3GPP accesses through EPC.
Consideration will be given, but not limited, to the following:
• High level requirements of LCS support for non 3GPP accesses;
• Location information provided to the LCS client for non 3GPP accesses;
• QoS requirements of LCS support for non 3GPP accesses.
• Priority between different LCS services for non 3GPP accesses.
• Privacy requirements of LCS support for non 3GPP accesses.
• Periodic location report of LCS services for non 3GPP accesses.
• Impact on the LCS client and the LCS server to support LCS services for non 3GPP accesses
|
22.893
|
Advanced requirements for IP interconnect
|
TR
|
10.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.893/22893-a00.zip
|
This document studies the technical requirements for carrier grade inter-operator IP Interconnection of Services for the support of Multimedia services provided by IMS and for legacy voice and video PSTN/PLMN services transported over IP infrastructure (e.g. VoIP). These requirements should take into account the new and developing, convergent interconnect models currently being developed outside 3GPP.
Requirements should fulfil:
• Identification of the technical requirements for IP Service Interconnection (service control and user plane aspects) between Service Providers.
• Identification of requirements for the Stage 2 & 3 work to identify relevant existing specifications, initiate enhancements and the development of the new specifications as necessary.
• Supporting of IP Service Interconnection models as defined by other bodies (e.g. GSMA, ETSI, ITU-T).
|
23.824
|
IP-Short-Message-Gateway (IP-SM-GW) enhancements for interworking with Open Mobile Alliance (OMA) Converged IP Messaging (CPM)
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.824/23824-a00.zip
|
The present document specifies the new capabilities and enhancements needed to support SMS over a generic IP Connectivity Access Network (IP-CAN) using IMS capabilities (TS 23.228 [9]). These include (but are not limited) to:
1 Enhancements to the HSS;
2 Communication between the SMS-GMSC/SMS-IWMSC and the HSS;
3 Authentication of service usage and registration;
4 Transfer of UE Terminated SMS, UE Originated SMS, and Delivery reports;
5 Mechanisms to handle SMS when there is more than one IP connection active with the UE, etc.
The document also specifies the capabilities and enhancements needed to support the service level interworking for the Short Message service as defined in the TS 23.040 [2] and in this specification and the Instant Messaging service as defined in OMA-TS-SIMPLE_IM-V1_0-20070816-C [12]. The features supported from the IM specification are limited to the exchange of short or large immediate messages in pager mode.
NOTE: The page-mode immediate message as defined in TS 24.247[14] is considered as a subset of OMA-TS-SIMPLE-IM-V1_0-20070816-C [12].
The service requirements are described in TS 22.340 [18].
|
23.829
|
Local IP Access and Selected IP Traffic Offload (LIPA-SIPTO)
|
TR
|
10.0.1
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.829/23829-a01.zip
|
Support of Local IP access for the Home (e)NodeB Subsystem and of Selected IP traffic offload for the Home (e)NodeB Subsystem and for the macro layer network is required in TS 22.220 [3] and TS 22.101 [2].
This Technical Report describes the following functionalities:
- Local IP access – LIPA – to residential/corporate local network for Home (e)NodeB Subsystem;
- Selected IP traffic offload – SIPTO – (e.g. Internet traffic) for Home (e)NodeB Subsystem;
- Selected IP traffic offload (e.g. Internet traffic, corporate traffic) for the macro network (3G and LTE only).
The report is intended to analyse the architectural aspects to achieve these objectives and to gather the technical content until it can be included in the relevant technical specifications.
|
23.831
|
IP Multimedia Subsystem (IMS) service continuity; Inter-UE transfer enhancements; Stage 2
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.831/23831-a00.zip
|
This technical report intends to develop enhancements to Rel-9 IMS Service Continuity in TS 23.237 [2], specifically in the functional area of Inter-UE Transfer. The main objective is to provide enhancements to mobility of media flows of a session between different UEs (Inter-UE Transfer) with respect to the following aspects:
- Extension of Inter-UE Transfer and Collaborative Session capabilities specified in Rel-09 to multiple UEs belonging to different IMS subscriptions under the same operator.
- Establishment of a Collaborative Session at session setup.
- Support for control of media components of a Collaborative Session by more than one UE simultaneously.
- Transfer of control of a Collaborative Session.
- Controller initiated media modification on a Controllee UE (e.g. video resolution).
- Discovery of ongoing IMS multimedia sessions on different UEs.
- Inter-UE Transfer initiated by the target UE when:
- the target UE belongs to the Collaborative Session but it is not a Controller UE;
- the target UE does not belong to the Collaborative Session and wants to join;
- Inter-UE Transfer is performed without establishing a Collaborative Session.
- Replication of an ongoing multimedia session from one UE on another UE.
- Inter-UE Transfer between UEs connected to the IMS via an IP-CAN and ICS entities that provide interworking with UEs in the CS Domain.
- Execution of MMTEL services for Collaborative Sessions.
This document contains the results of an assessment of alternative architectures to support Inter-UE Transfer enhancements.
|
23.832
|
IP Multimedia Subsystem (IMS) aspects of architecture for Home Node B (HNB); Stage 2
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.832/23832-a00.zip
|
This Technical Report describes an IMS capable HNB SubSystem (the HNB and the HNB Gateway) as an optional capability of HNB that allows e.g. an operator to offload CS traffic to the IMS. The HNB and HNB Gateway are described in TR 23.830 [5], and the capabilities of these network elements are assumed by this TR.
To achieve this and to satisfy the related requirements and use cases captured in TS 22.220 [2], the objective is to investigate the following:
• an architecture to enable IMS capable HNB Subsystem to use the IMS for CS terminals using a corresponding equivalent IMS services (voice service in IMS Multimedia Telephony);
• the impacts of the IMS capable HNB Subsystem to idle mode mobility for all supported UE types (e.g. IMS registration/de-registration);
• service continuity at least in the direction from IMS capable HNB Subsystem to macro network;
• support for pre-Rel‑9 CS and IMS UEs when using IMS capable HNB Subsystem.
The TR will analyze solutions for the related architectural issues and capture the conclusions.
|
23.834
|
Study on General Packet Radio Service (GPRS) Tunelling Protocol (GTP) based S2b; Stage 2
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.834/23834-a00.zip
|
The objective of this feasibility study is to investigate solutions and benefits for supporting a new GTP option for S2b network based mobility.
The study will develop the stage 2 message flows necessary to support S2b based on GTP and mobility between S5/S8 based on GTP and S2b based on GTP.
|
23.845
|
Study on User Data Convergence (UDC) evolution
|
TR
|
10.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.845/23845-a00.zip
|
The present document is addressing a number of topics regarding User Data Convergence evolution. Some of these topics were identified in the Rel9 work but have been delayed, others are new.
These topics are largely independent of each other and are studied separately in this document.
They will be normally addressed through the following steps:
- a description of the topic to be addressed with its interest, the associated requirements to cover or issues to be solved
- a description of the alternative solutions including their impact on 3GPP specifications
- a comparison of the solutions
- a conclusion with recommendations.
|
23.856
|
Single Radio Voice Call Continuity (SRVCC) enhancements; Stage 2
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.856/23856-a00.zip
|
SR-VCC has been standardized in Release 8 TS 23.216 [3] to provide seamless continuity when UE handovers from E-UTRAN to UTRAN/GERAN.
This document contains the results of feasibility study of the requirements and the alternative solutions to improve the handover performance of SRVCC.
The objective of this study is as follows:
- Evaluating the performance of current Rel‑8 SRVCC solution;
- Enhancing the performance of the SR-VCC Flow Break with regard to the roaming and non-roaming case;
- Enhancing SR-VCC handover performance while minimizing the impacts on the network architecture for the directions
- from EUTRAN to UTRAN/GERAN; and
- from UTRAN to UTRAN/GERAN.
|
23.860
|
Enabling coder selection and rate adaptation for UTRAN and E-UTRAN for load adaptive applications; Stage 2
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.860/23860-a00.zip
|
The system enhancements to enable codec rate adaptation at voice call setup over E-UTRA was standardized in Rel-9 in TS 23.401 [2].
The scope of this document is to study and specify enhancements to existing codec selection and codec rate adaptation based on network loading conditions and operator policies over UTRA and E-UTRA. Potential enhancements are definition of the signalling and interfaces enabling:
- To perform codec selection based on network loading conditions and operator policies during call establishment phase over both UTRA and E-UTRA;
- To perform codec data rate adaptation (if possible for the selected codec and needed by the service) based on network loading conditions during call establishment phase over UTRA;
- To perform codec data rate adaptation (if possible for the selected codec and needed by the service) for non-voice RTP-based services based on network loading conditions at call setup over E-UTRA;
- To perform codec data rate adaptation (if possible for the selected codec and needed by the service) based on network loading indications during an on-going call over both UTRA and E-UTRA;
- Support of codec rate adaptation by IMS Core Network entities (e.g., MGCF/MGW, IBCF/TrGW, etc.);
- Setting of Maximum Bit Rate (MBR) to be greater than the Guaranteed Bit Rate (GBR) over E-UTRA.
The solutions can be moved to normative specifications independently of each other once the study on the particular solution has been concluded.
|
23.886
|
Feasibility Study of Single Radio Video Call Continuity (vSRVCC); Stage 2
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.886/23886-a00.zip
|
The objective of the feasibility study is to investigate a solution for supporting single radio the video call continuity from E-UTRAN/HSPA to UTRAN-CS based on the Rel-8/9 Single Radio Voice Call Continuity (SRVCC) architecture as specified in TS 23.216 [2] and TS 23.237 [3], and study the mechanisms to resolve the key issues. It is not expected that the SRVCC architecture will be modified unless any of the key issues cannot be resolved with the current architecture.
The study will be performed to the scenarios where IMS session using bidirectional voice and synchronised video such as defined in TS 22.173 [4], originated in E-UTRAN/HSPA and the UE moves to UTRAN and continues the service over UTRAN in the CS domain.
The video call continuity from E-UTRAN/HSPA to GERAN is not supported.
|
23.889
|
Local Call Local Switch (LCLS) system impacts; Feasibility study
|
TR
|
10.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.889/23889-a00.zip
|
The present document provides a study into the Core Network impacts for providing a solution for Local Call Local Switching. The document analyses and evaluates different solutions to determine the benefits provided compared to the identified impacts.
Specific considerations are given to the following areas:-
- Sending of correlation information between the two legs of the call to the BSS
- Triggering to enable/release Local Call Local Switch (e.g. based on activation of Supplementary Services, etc.)
- Support of existing Supplementary Services
- Support of existing Lawful Intercept functionality
- Impacts to the user plane handling on the A-interface
- Impacts to the MSC-S – MGW Interface (Mc Interface)
- Impacts to the MSC-S – MSC-S Interface (Nc Interface)
The solution(s) considered for local call local switch should keep the core network impacts to a minimum, e.g. the impacts on the nodal functions, existing call flows, call establishment and call release.
The contents of this report when stable shall determine the modifications to existing core network specifications.
|
23.894
|
System enhancements for the use of IP Multimedia Subsystem (IMS) services in local breakout and optimal routeing of media
|
TR
|
10.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.894/23894-a00.zip
|
This study intends to investigate the general problem of system enhancements for the use of IMS services in local breakout and optimal routeing of media.
In particular the above issues will be addressed identifying
- solutions for the home operator to control
- whether the IMS user may connect to a PDN in the visited network, and
- whether connections to PDNs provided from the home and visited network may exist in parallel;
- solutions to enable the IMS network to be aware of whether local breakout can be invoked or not;
- solutions to allow the home operator to determine which of the IMS sessions (for a given UE) can be handled in local breakout and which in home routed mode, and what information (e.g. operator's policies, customer's subscription profile, UE connectivity, and location of the remote end terminal/service) is needed for the decision;
- solutions to allow the UE to concurrently use IMS services through local breakout and other IMS services through home routeing;
- the feasibility of having the local breakout option in IMS service nodes:
- is there a need for a P-CSCF at both PDN accesses?
- if one P-CSCF is enough, what requirements are there for connectivity between the PDNs?
- if methods are necessary to discover an additional P-CSCF in the visited network after the UE has moved to the visited network, even if the network-layer mobility mechanisms can sustain IP connectivity to the previously discovered P-CSCF in the home network;
- the exact location of the decision point in the home network whether to use local breakout (application or delegated to IP-CAN);
- solutions for SIP/SDP signalling related to the use of IMS services through local breakout.
- interactions with network entities such as NAT (as specified in TS 23.228 [8]) when providing IMS services through local breakout;
- interactions with and support of PCC to provide IMS services through local breakout;
- security implications if there is need for multiple P-CSCFs per UE.
Moreover:
- describing a set of scenarios where the selection of an alternative media path (i.e., different to the signalling path) provides benefits to IMS operators by reducing the number of network entities in the media path;
- providing requirements for suitable mechanisms to achieve optimal media routeing;
- analysing the potential solution(s) to solve those scenarios in line with IMS procedures, while taking into account any impact of extensions required to existing functions/procedures (e.g., NAT, transcoding, Security, PCC, BCF, LI, etc.);
- reducing the number of options for solving the same requirement and agree on a preferred solution.
In the end this study will provide conclusions with respects to what further specification work is required in order to fulfil the requirements for the use of IMS services through local breakout and achieve optimal routeing of media.
|
24.837
|
IP Multimedia (IM) Core Network (CN) subsystem inter-UE transfer enhancements; Stage 3
|
TR
|
10.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.837/24837-a00.zip
|
This technical report intends to develop enhancements to Rel-9 IMS service continuity stage 3 within the scope of 3GPP TS 24.237 [6], specifically in the area of inter-UE transfer. This technical report serves as a collection and a base for decision on alternative solution proposals for the different enhancement to Rel-9 IMS service continuity stage 3.
This technical report will be used to move the agreed solutions into the main specifications, once the content has stabilized.
Editor's Note: This TR reflects those inter-UE transfer issues, which are currently reflected in 3GPP TR 23.837. As currently SA2 did not move any of the Rel-10 inter-UE transfer topics to 3GPP TS 24.237, it is not sure which of these features will be finally part of Rel-10. The content of this TR will be scoped to those features, which SA2 decides to make part of the Rel-10 version of 3GPP TS 24.237.
|
25.317
|
High Speed Packet Access (HSPA); Requirements on User Equipments (UEs) supporting a release-independent frequency band combination
|
TS
|
10.1.0
|
R2
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.317/25317-a10.zip
|
The present document specifies requirements on UEs supporting a frequency band combination that is independent of release. TSG-RAN has agreed that the standardisation of new frequency band combinations of DB-DC-HSDPA may be independent of a release. However, in order to implement a UE that conforms to a particular release but supports a band combination of operation that is specified in a later release, it is necessary to specify some extra requirements.
For example, Band I-XI combination for DB-DC-HSDPA (referred to as DB-DC-HSDPA configuration 4 in [2]) is contained in the Release 10 specifications. In order to implement a UE conforming to Release 9 but supporting this configuration, it is necessary for the UE to additionally conform to some parts of the Release 10 specifications, such as the radio frequency and radio resource management requirements for the configuration.
All DB-DC-HSDPA configurations are fully specified in this release of the specifications. The present document does not contain any requirements for UEs supporting DB-DC-HSDPA configurations independent of release.
|
25.864
|
Downlink configurations for Four-carrier High Speed Download Packet Access (4C-HSDPA)
|
TR
|
10.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.864/25864-a00.zip
|
The present document is intended to maintain the list of 4C-HSDPA downlink configurations in the context of the work item “For carrier HSDPA” [2]. Each downlink configuration is composed of the frequency band(s) and the number of downlink adjacent carriers in each band.
In addition, the present document also captured the framework to specify the Rx core requirements for 4C-HSDPA.
|
25.865
|
Improvements of distributed antenna for 1.28 Mcps TDD
|
TR
|
10.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.865/25865-a00.zip
|
The present document is intended to capture the output of the study item on improvements of distributed antenna for 1.28Mcps TDD, which was approved at TSG RAN#47. The objective of this study item is to study the potential enhancement techniques for the distributed antenna.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.