id
stringlengths 5
12
| title
stringlengths 8
250
| type
stringclasses 2
values | version
stringclasses 222
values | working_group
stringclasses 30
values | url
stringlengths 67
81
| scope
stringlengths 0
65.7k
|
|---|---|---|---|---|---|---|
42.033
|
Lawful Interception; Stage 1
|
TS
|
12.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/42_series/42.033/42033-c00.zip
|
This Technical Specification provides the stage 1 description for a lawful interception function to be implemented in a given GSM PLMN in order for a network operator to be able to fulfil national lawful requirements. It shall be noted that national variation may exist but it is not the intention for this specification to encompass all of them. The purpose of this specification is to cover the options which may be selectable according to national regulations or as required by the GSM PLMN operator in co-operation with their suppliers.
In the preparation of this specification general reference was made to the European Union Council Resolution, January 1995: "International Requirements for the Lawful Interception of Telecommunications".
|
43.033
|
3G security; Lawful Interception; Stage 2
|
TS
|
12.0.0
|
S3
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.033/43033-c00.zip
|
The present document gives the stage 2 description of Lawful Interception within a PLMN for circuit switched systems and GPRS. It does not address the interface between the PLMN and the LEA lawful intercepted product and related information collection functions. This is outside the scope of the GSM standard.
The structure of the present document is as follows:
- clause 4 covers the architecture of the interception system;
- clause 5 describes how interception is activated, deactivated and interrogated within the interception system;
- clause 6 describes how the system is provisioned, defines events at which interception takes place and what kind of information is generated at each event;
- clause 7 provides brief descriptions of various intercept cases;
- clause 8 reviews security requirements for access to the interception system;
- annex A provides information flows to illustrate when intercepted traffic and related data is generated;
- annex B describes an interception system for GPRS. The annex is subdivided into 5 sections that are identical in structure to clauses 4 through 8, but applicable to a GPRS clause rather than a GSM circuit switched system.
|
43.801
|
Solutions for Voice services over Adaptive Multi-user channels on One Slot (VAMOS) enhancements
|
TR
|
12.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.801/43801-c00.zip
|
The present document contains the results from the 3GPP study item on VAMOS Enhancements. This includes study of the following aspects:
- Objectives of the study.
- Common assumptions for the evaluation of candidate techniques.
- Candidate techniques including those that utilize network synchronization, and further those that use inter-cell interference coordination/mitigation and inter-cell channel state sharing in and between BSS. A candidate technique will support frequency hopping.
- Evaluations of candidate techniques based on the objectives.
VAMOS enhancements will also investigate a new logical interface between BSSs in A/Gb mode which applies to control plane only and can be utilised by VAMOS enhancement solutions, since no logical interface between BSSs in A/Gb mode exists in current specifications.
|
43.802
|
GERAN study on mobile data applications
|
TR
|
12.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.802/43802-c00.zip
|
The present document contains the results from the feasibility study on efficient support of mobile data applications for human communications in GERAN.
The following aspects shall be covered in the study:
- Analysis on relevant traffic profiles from GERAN perspective for the mobile data applications of human communications
- Analysis on the impacts on GERAN network based on the identified traffic profiles
- GERAN enhancements to alleviate these impacts with regards to: Radio resource utilization; signalling procedures; RR states and transition between them and Battery lifetime
- Common assumptions on simulations and evaluations for candidate solutions
|
43.868
|
GERAN improvements for Machine-Type Communications (MTC)
|
TR
|
12.1.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/43_series/43.868/43868-c10.zip
|
The present document contains the results from the study of improvements for Machine-type Communications in GERAN.
The following items are in the scope of the study:
- GERAN enhancements for Smart metering
- Enhancements which enable or improve efficient use of RAN resources and/or which lower complexity when a large number of MTC devices are served.
- GERAN enhancements for overload and congestion control on the radio, A and Gb interface
- GERAN enhancements regarding identifiers used for MTC devices in the radio access network
|
51.010-7
|
Mobile Station (MS) conformance specification; Part 7: Location Services (LCS) test scenarios and assistance data
|
TS
|
12.5.0
|
R5
|
https://www.3gpp.org/ftp/Specs/archive/51_series/51.010-7/51010-7-c50.zip
|
The present document contains the orbital model information, the assistance data and the assistance data files that shall be used for all LCS Assisted GPS and Assisted GNSS test cases defined in subclause 70 of TS 51.010-1 [4].
|
22.809
|
Feasibility study on support for 3GPP voice interworking with enterprise IP-PBX (VINE)
|
TR
|
11.2.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.809/22809-b20.zip
|
This study aims to provide use cases and requirements for the following aspects of interworking between 3GPP networks and Enterprise voice services:
- Support for CS and IMS voice services interworking with IP-PBX services while at the same time maintaining full operator visibility and control of the related voice service signalling in the mobile operator’s core network,
- Mobile operator control of security, manageability and operation of IP-PBX interworking function,
- Mobile operator control of availability of IP-PBX services to 3GPP mobile devices,
- Mobility between cellular and Enterprise environments, and
- Continuity when an IMS session is moved between cellular and Enterprise environments and when the IMS session is moved between mobile and fixed devices in the Enterprise environment.
Use cases and requirements from other SDOs will be considered in this study.
The following services aspects will be covered:
- CS and IMS services,
- Enterprise specific value-added services (e.g. "short code dialling", conferencing, transfer of sessions to a soft-phone on a PC), and
- Interaction between services provided by the mobile operator and services provided by the Enterprise.
|
22.871
|
Study on non-voice emergency services
|
TR
|
11.3.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.871/22871-b30.zip
|
Non Voice Emergency Services will be applicable to GPRS (GERAN, UTRAN) and to EPS (GERAN, UTRAN, E‑UTRAN and non-3GPP).
|
22.894
|
Feasibility study on IP Multimedia Subsystem (IMS) network-independent public user identities
|
TR
|
11.0.0
|
S1
|
https://www.3gpp.org/ftp/Specs/archive/22_series/22.894/22894-b00.zip
|
This study aims to examine the use cases and potential requirements that allow different Public User Identities of the form sip:user@domain belonging to the same domain to be:
- assigned by multiple network operators, where an individual Public User Identity is served by only a single network operator for all IMS services;
- provisioned by network operators in the case where other URI schemes have already been, or are going to be, provisioned by different service providers in the internet.
The Public User Identities could be SIP URIs associated with or derived from user identities of services from the Internet domain.
This study also aims to clarify the relationships (e.g., business, interworking) between the Domain Name Owner, the assignee of sip:user@domain where it is not the same as the domain owner, and operators sharing the domain name.
Any potential regulatory aspects will also be considered.
|
23.812
|
Feasibility study on IP Multimedia Subsystem (IMS) evolution
|
TR
|
11.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.812/23812-b00.zip
|
The scope of the technical report is to capture the results of a study into the feasibility of enhancing IMS network architecture. This report intends to study the feasibility of enhancing IMS network architecture as follows,
- Investigating architectural improvements to reduce the complexity of signalling procedures by reducing the signalling hops, or the number of options and combinations (by looking at different groupings of combining existing entities);
- Investigating means to improve system-level load balancing and reliability;
- Investigating possibilities for reducing configuration workload to save OPEX.
- Investigating the introduction of IMS Overload Control mechanisms.
Backward compatibility with current IMS specifications shall be ensured.
NOTE: overlap with SA5 and CT4 work need to be monitored.
This report is intended to explore potential architecture improvements and also provide conclusions on the above aspects with respect to potential future normative specification work.
There are a number of functions involved in call session setup in IMS network. Interfaces and interactions between network elements may be a little complicated and not that efficient. It is deemed beneficial to review the current IMS architecture including aspects such as the possible optimization of interfaces/reference points (by looking at different groupings of combining existing entities), reducing options of solutions for the same issues, relevancy of certain functions etc.
IMS network service availability largely relies on the reliability of network entities. If some network elements implementing critical functions (e.g. S-CSCF, HSS) fail, service availability may be impacted. Moreover network elements may not be fully utilized because network load may not be well distributed, e.g. some nodes may be overloaded due to sudden traffic increase, while others may be under loaded to some extent. Though there are some element level approaches to solve these problems, some system level solutions should be studied, for example, the method to distribute load between network elements in different geographical locations especially when a disaster happens, such as earthquake.
Network expansion may require significant manual configurations, and the network maintenance and upgrade may be time-consuming and also may be costly for operators. Introducing self-organization features may improve the network intelligence and reduce the efforts of manual configuration.
The objectives of the study for investigating the introduction of IMS Overload Control mechanisms are to:
- Determine the parts of IMS architecture for which overload control mechanisms are needed;
- Evaluate the applicability of candidate solutions for Overload Control to the SIP entities of the IP multimedia core network architecture, including:
- mechanisms having already been specified or studied within 3GPP and their possible enhancements,
- mechanisms specified or studied by other bodies (e.g. ETSI TISPAN, IETF) and their possible enhancements,
- other mechanisms, if proposed within this work item;
- Provide recommendations based on analysis.
|
23.813
|
Study on policy solutions and enhancements
|
TR
|
11.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.813/23813-b00.zip
|
The objective is to study an evolved policy solution through enhancement of 3GPP policy framework. One of the aims of the study is to ensure a policy architecture that provides an extensible framework for easy reuse with new IP based services by identifying areas where improvement of specifications are feasible. The study item will look into solutions for the examples in the section above.
Existing components for consideration in the Policy Study are functions and interfaces to/from
- PCRF, PCEF and BBERF;
- SPR, HSS;
- ANDSF;
- IMS policy decision making entities.
The study aims to provide a more comprehensive way (e.g. going beyond existing 3GPP PCC framework) to handle operator policies for all IP / service flows (IMS and non-IMS) in a coordinated manner and under varying network conditions while keeping in view aspects such as:
- user preferences;
- user subscriptions;
- service requirements;
- terminal capabilities (including converged terminals);
- network capabilities (3GPP and those non 3GPP accesses inter- working with 3GPP);
- Session transfer and terminating policies;
- Security policy control, e.g. firewalling and gating.
Roaming scenarios are considered as part of this study. Compatibility with existing system architecture elements are protected and backward compatibility is expected. All types of policies i.e. static/pre-provisioned, dynamic, network based, UE based are considered in the study.
When a key issue is resolved sufficiently to be incorporated into the specification in an independent manner, the study work may move forward for a decision for normative specification work on such issue(s) using a new work item or a TEI.
|
23.842
|
Study on network provided location information to the IP Multimedia Subsystem (IMS)
|
TR
|
11.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.842/23842-b00.zip
|
The present document investigates architecture solutions for making the Network Provided Location Information (NPLI) related to the access network that the UE is camped on available to the IMS nodes whenever the IMS operator needs to record this information either to fulfil legal obligations, for charging or for other purposes.
This study will gather the various existing regulatory and operator requirements that the solution needs to fulfil, in particular:
- whether the provision of the Network Provided Location (NPLI) Information and local time are applicable to all the users served by a network (i.e. "non-roaming" subscribers and inbound roamers) or only to the network operator subscribers;
- whether Network Provided Location (NPLI) and local time need to be made available also if EPS/GPRS and IMS services of a subscriber are provided by different networks;
- what events trigger the need to retrieve the Network Provided Location (NPLI) and local time.
The study is then expected to produce solution candidates which detail the necessary Stage 2 message flows, architecture enhancements and new functionality needed in the EPS and GPRS networks. The solution candidates will also describe what IP Multimedia Subsystem elements are affected in order to obtain the Network Provided Location (NPLI).
The solutions produced will then be assessed against the criteria identified in section 7 where recommendations for normative work will also be made.
|
23.849
|
Study on Stage 2 aspects of Optimised Service Charging and Allocation of Resources (OSCAR) in the IP Multimedia Subsystem (IMS) whilst roaming
|
TR
|
11.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.849/23849-b00.zip
|
The present document provides a study into the new (Rel-11) requirements identified by SA WG1 to allow a home network to control a visited network to perform the following IMS functions for its subscribers:
- conferencing (network hosted);
- transcoding;
- tone insertion; and
- announcement insertion.
|
23.850
|
Study on roaming architecture for voice over IP Multimedia Subsystem (IMS) with local breakout
|
TR
|
11.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.850/23850-b00.zip
|
In the context of support of roaming for voice over IMS, the GSM Association has decided that local breakout in the visited network will be needed (see GSMA PRD IR.65 [6]). This is because local breakout can be regarded as one cornerstone to allow the replication of the charging principles on which CS roaming is based on. However there are several other aspects that need to be considered e.g. the split/bundling of user and control plane, capturing of SDP information needed to generate charging records, to make such principles applicable to voice over IMS roaming.
This study item will therefore investigate solutions for the provision of voice over IMS in roaming scenarios that facilitate the realization of a charging model that replicates the principles of CS model.
It will be studied whether changes to the core 3GPP specifications are needed and if so which ones. The study will focus on IMS layer and not EPC aspects.
As some of the aspects of the roaming are outside the scope of 3GPP (e.g. decision to anchor media or control plane, interaction with carrier networks, roaming agreements) this study will be performed in close cooperation with the GSM Association which may provide additional requirements and guidance during its development.
|
23.854
|
Enhancements for Multimedia Priority Service (MPS)
|
TR
|
11.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.854/23854-b00.zip
|
MPS will enable National Security/Emergency Preparedness (NS/EP) users (herein called Service Users) to make priority calls/sessions using the public networks. This service needs to be ensured also under special conditions such as network congestion. Service Users are the government-authorized personnel, emergency management officials and/or other authorized users. Effective disaster response and management rely on the Service User's ability to communicate during congestion conditions. Service Users are expected to receive priority treatment, in support of mission critical multimedia communications.
The enhancements for MPS evaluated in this document are priority aspects of EPS packet bearer services and priority related interworking between IMS and EPS packet bearer services. These enhancements enable the network to support end-to-end priority treatment for MPS call/session origination/termination, including the Non Access Stratum (NAS) and Access Stratum (AS) signalling establishment procedures at originating/terminating network side as well as resource allocation in the core and radio networks for bearers. Priority treatment will be applicable to IMS based multimedia services, priority EPS bearer services and CS Fallback.
This document clarifies the architectural requirements for MPS, considers the priority service scenarios, and evaluates solution alternatives. Solutions will be proposed and evaluated based on the following three service categories: IMS based multimedia service (voice, video etc), priority EPS bearer services (PS data without IMS interaction) and CS Fallback. Common issues for multiple service categories should be resolved by single solution to limit the amount of overall functionality and to avoid complexity.
The basic eMPS, i.e. priority handling of IMS based multimedia service, EPS bearer services and CS Fallback have completed in Rel‑10. In Rel‑11, Single Radio Voice Call Continuity (SRVCC) from LTE to UTRAN/GERAN/1xCS will be investigated based on Rel‑10 SRVCC specification.
The result of the analysis should be suitable as a basis for normative MPS specification work.
The scope of the MPS part is to further investigate:
- The signalling and procedures for identifying priority and authorizing the usage of priority service.
- The required priority attributes used in enabling end-to-end priority marking and priority treatment during establishment, modification and release of an IMS based priority voice/video/data session.
- The scenarios and capabilities for supporting priority EPS bearer data services.
- The potential impacts on existing and relevant standard procedures in order to provide preferential treatment for MPS requests in the event of congestion.
- Inter-working with other IMS and CS networks to provide an end-to-end priority service.
|
23.855
|
Data Identification in Access Network Discovery and Selection Function (ANDSF) (DIDA)
|
TR
|
11.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.855/23855-b00.zip
|
This Technical Report describes proposed extensions to ANDSF Inter-System Routing Policies (ISRP) to provide to operators a better control of the network resources used for each application or IP flow. Specifically the Technical Report focuses on additional mechanism to identify classes of traffic an ISRP applies to.
Any extension to the ANDSF framework which is not related to identification of traffic is outside the scope of this Technical Report.
|
23.857
|
Study of Evolved Packet Core (EPC) nodes restoration
|
TR
|
11.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.857/23857-b00.zip
|
The present document contains the study on EPC nodes failure and restoration.
This document will consider any necessary operational protocol recovery mechanisms in the EPS in order to restore the subscriber service in the event of EPC node failure or clean up the hanging resource in other EPC nodes if the recovery of the failed node is not possible. The document will address the following aspects:
- list the different network failure scenarios to be analyzed for EPC nodes: MME, S4-SGSN, SGW and PGW;
- identify precisely the problems resulting from the current definition of the standards;
- list various possible solutions;
- identify pros and cons of possible solutions;
- conclude on potential enhancements to the standards (depending on gains vs complexity).
|
23.885
|
Feasibility Study of Single Radio Voice Call Continuity (SRVCC) from UTRAN/GERAN to E-UTRAN/HSPA; Stage 2
|
TR
|
11.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.885/23885-b00.zip
|
The objective of the feasibility study is to investigate a solution for supporting Single Radio Voice Call Continuity (SRVCC) from 3GPP UTRAN/GERAN CS access to 3GPP E-UTRAN/HSPA access, for voice call initiated in LTE/HSPA access and previously handed over to UTRAN/GERAN CS access, as well as for the voice call directly initiated in UTRAN/GERAN CS access.
This Technical Report investigates solutions for SRVCC for voice calls that are anchored in the IMS.
Coordination between the SRVCC for voice call and the handover of non‑voice PS bearers is also covered.
|
23.888
|
System improvements for Machine-Type Communications (MTC)
|
TR
|
11.0.0
|
S2
|
https://www.3gpp.org/ftp/Specs/archive/23_series/23.888/23888-b00.zip
|
This Technical Report studies and evaluates architectural aspects of the System Improvements for Machine Type Communications requirements specified in TS 22.368 [2].
Specifically, the following system improvements are considered:
- Architectural enhancements to support a large number of Machine-Type Communication (MTC) devices in the network;
- Architectural enhancements to fulfil MTC service requirements;
- Support combinations of architectural enhancements for MTC, though not all combinations may by possible.
The end-to-end aspects of communication between MTC devices and MTC servers (which can be located outside or inside the network operator's domain) are out of the scope of this study. However, the transport services for MTC as provided by the 3GPP system and the related optimizations are considered in this study. In addition, the aspects needed to ensure that MTC devices and/or MTC servers and/or MTC applications do not cause peak loads of short duration (e.g. a "busy minute" rather than a "busy hour") are within the scope of this TR.
Even though some provided solutions may be beneficial for communications from a MTC Device towards another MTC Device, this particular type communication has not been explicitly considered in this Technical Report.
This Technical Report analyzes architectural aspects to achieve these objectives and to gather technical content until it can be included in the relevant technical specifications.
NOTE: Some aspects in this feasibility study have led into normative specification in TS 23.682 [20], TS 23.060 [21], TS 23.401 [5], TS 23.221 [22] and TS 23.272 [23]. The text of the present document was not updated to align with normative specifications.
|
24.820
|
3GPP system to fixed broadband access network interworking
|
TR
|
11.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.820/24820-b00.zip
|
The present document studies the additional UE – EPC procedures within the scope of 3GPP TS 24.302 [2] and 3GPP TS 24.229 [3], for the interworking between a 3GPP system and a Fixed Broadband Access network defined by Broadband Forum to provide the IP connectivity to a 3GPP UE using a WLAN and a H(e)NB connected to a Fixed Broadband Access network.
The report covers the discovery and network selection procedures, QoS aspects, Tunnel management procedures, selection of the IP mobility mode, Authentication and Access Authorization using Authentication, Authorization and Accounting (AAA) procedures, and IP CAN session impacts.
The present document is applicable to the UE and the network. In this technical specification the network is the 3GPP EPC.
|
24.826
|
Study on impacts on signalling between User Equipment (UE) and core network from energy saving
|
TR
|
11.0.0
|
C1
|
https://www.3gpp.org/ftp/Specs/archive/24_series/24.826/24826-b00.zip
|
The present document contains the result of the study on the impacts on signalling between the UE and core network when energy saving measures are applied to network entities.
The study aims, within the defined CT1 work areas, at:
- analysing UE idle mode procedures and signalling between the UE and core network resulting from switch on/off of radio equipment in all types of 3GPP accesses, including home cell deployment and I-WLAN, as well as power adaptation of radio equipment (where applicable);
- performing a corresponding analysis for connected mode UEs;
- analysing similar impacts from activation status of non-3GPP access networks;
- documenting limitations, weaknesses and inefficiencies in these procedures, with emphasis on mass effects in the signalling between the UE and core network; and
- studying potential optimizations and enhancements to these procedures.
The study also evaluates potential enhancements to 3GPP specifications under CT1 responsibility.
This study takes into account decisions made by other 3GPP working groups in their related work.
|
25.144
|
User Equipment (UE) and Mobile Station (MS) over the air performance requirements
|
TS
|
11.2.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.144/25144-b20.zip
|
The present document establishes Over the Air antenna minimum requirements for User Equipment (UE) and Mobile Station (MS).
Requirements are defined for roaming bands for the speech position (beside the head) and for the data transfer position (free space). Requirements for free space are applicable to devices used in the data transfer position and consist of laptop mounted equipment (LME) plug-in UEs and laptop embedded equipment (LEE) UEs. All bands are potential roaming bands, and the requirements for roaming bands shall therefore be fulfilled for all bands supported by a UE/MS.
Requirements for operating bands are dependent on how the network has been built and are thus operator specific and can not be specified here. Recommended performance values for operating bands (Annex B) are however included in this specification for information. It should be recognised that the ability to meet the recommended performance values depends on the number of frequency bands supported by the UE/MS.
|
25.863
|
Universal Terrestrial Radio Access (UTRA); Uplink transmit diversity for High Speed Packet Access (HSPA)
|
TR
|
11.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.863/25863-b00.zip
|
The present document is intended to capture RAN1 and RAN4 findings produced in the context of the study item "Uplink Transmit Diversity for HSPA" [2]. The study is focussed on schemes that do not require any newly standardised dynamic feedback signalling between network and UE. The uplink transmit diversity schemes maybe categorized into two types of algorithms:
- transmission from 1 Tx antenna (e.g. switched antenna Tx diversity); or
- simultaneous transmission from 2 Tx antennas (e.g. transmit beamforming).
The scope is understood to be limited to schemes which also do not require any semi-static mode configuration signalling for demodulation. The possibility of semi-static disabling of a transmit diversity scheme is not precluded.
The work under this study item aims at:
- evaluating the potential benefits of the indicated UL Tx diversity techniques;
- investigating the impacts on the UE implementation;
- investigating how to ensure that the UE operating an uplink Tx diversity will not cause any detrimental effects to overall system performance;
- investigating the impacts of Tx diversity on existing BS and UE RF and demodulation performance requirements; and
- analyzing how to derive any additional performance/test requirements that are deemed needed as an outcome of the study, as well as understanding the impacts of any such new requirements.
The performance of closed loop transmit diversity, in which the Node-B controls and dynamically adapts the pre-coding vector that a UE shall apply is described in [124].
|
25.871
|
Uplink Multiple Input Multiple Output (MIMO) for High Speed Packet Access (HSPA)
|
TR
|
11.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.871/25871-b00.zip
|
The present document captures evaluation results and analysis from the study item on “Uplink MIMO for HSPA” described in [2].
The work under this study intends to capture the feasibility and merits of UL MIMO in terms of average user throughput for the following configuration
• Up to 2 streams can be transmitted by the UE
• UL MIMO transmission applies to E-DCH physical channels
• Both 2x2 and 2x4 configurations are considered
Additionally, the following are also investigated:
• Impact on infrastructure implementation
• Impact on UE implementation
• Impact on specifications
|
25.872
|
High Speed Packet Access (HSDPA) multipoint transmission
|
TR
|
11.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.872/25872-b00.zip
|
HSPA based mobile internet offerings are becoming very popular and data usage is increasing rapidly. Consequently, HSPA has begun to be deployed on more than one transmit antenna or more than one carrier. As an example, the single cell downlink MIMO (MIMO-Physical layer) feature was introduced in Release 7. This feature allowed a NodeB to transmit two transport blocks to a single UE from the same cell on a pair of transmit antennas thus improving data rates at high geometries and providing a beamforming advantage to the UE in low geometry conditions. Subsequently, in Release-8 and Release-9, the dual cell HSDPA (DC-HSDPA) and dual band DC-HSDPA features were introduced. Both these features allow the NodeB to serve one or more users by simultaneous operation of HSDPA on two different carrier frequencies in two geographically overlapping cells, thus improving the user experience across the entire cell coverage area. In Release 10 these concepts were extended so that simultaneous transmissions to a single UE could occur from four cells (4C-HSDPA).
When a UE falls into the softer or soft handover coverage region of two cells on the same carrier frequency, it would be beneficial for the non-serving cell to be able to schedule packets to this UE and thereby improving this particular user’s experience, especially when the non-serving cell is partially loaded. MultiPoint HSDPA allows two cells to transmit packets to the same UE, providing improved user experience and system load balancing. MultiPoint HSDPA can operate on one or two frequencies.
|
25.873
|
UE Demodulation Performance Requirements Under Multiple-cell Scenario for 1.28Mcps TDD
|
TR
|
11.0.0
|
R4
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.873/25873-b00.zip
|
The present document is the technical report for the work item on UE demodulation performance requirements under multiple-cell scenario for 1.28Mcps TDD, which was approved at TSG RAN#50. The objective of this WI is to define the performance requirements under multi-cell scenario for 1.28Mcps TDD.
|
25.874
|
High Speed Packet Access (HSPA) feedback and signalling efficiency enhancements for Low Chip Rate (LCR) Time Division Duplex (TDD)
|
TR
|
11.0.0
|
RP
|
https://www.3gpp.org/ftp/Specs/archive/25_series/25.874/25874-b00.zip
|
The present document summarizes the study results of the SI “HSPA Feedback and Signalling Efficiency Enhancements for LCR TDD”. The study results focus on the following three study items.
(1) CQI feedback enhancement
• Evaluate the impact the discontinuous CQI feedback will create
• If needed, find out how to solve the problem the discontinuous CQI feedback will create
• Evaluate how much gain will be obtained with the new methods.
(2) HSPA control channel efficiency optimisation
◦ find out the new methods for increasing the HSPA control channel efficiency.
• Evaluate how much gain will be obtained with the new methods.
(3) HSPA signalling enhancements for more efficient resource usage
◦ find out the new methods for more efficient HSPA resource usage
◦ Evaluate how much gain will be obtained with the new methods.
|
26.851
|
Enhancements to Multimedia (EMM); Download Delivery Enhancements (DDE) and IMS-based PSS and MBMS streaming synchronization Enhancements (IPME) aspects
|
TR
|
11.2.0
|
S4
|
https://www.3gpp.org/ftp/Specs/archive/26_series/26.851/26851-b20.zip
|
The present document contains the results of the work items EMM , EMM-DDE and EMM-IPME. This document does not include the results from the EMM-EFEC work item.
|
29.161
|
Interworking between the Public Land Mobile Network (PLMN) supporting packet based services with Wireless Local Area Network (WLAN) access and Packet data Networks (PDN)
|
TS
|
11.0.0
|
C3
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.161/29161-b00.zip
|
The present document defines the requirements for Packet Domain interworking between a:
a) PLMN with WLAN access and PDN;
b) PLMN with WLAN access and PLMN.
The present document also defines, in clause 12, the usage of Radius at the Pp Reference Point between the Packet Data Gateway and the Presence Network Agent, see 3GPP TS 23.141 [18].
|
29.234
|
3GPP system to Wireless Local Area Network (WLAN) interworking; Stage 3
|
TS
|
11.2.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.234/29234-b20.zip
|
The present document defines the stage-3 protocol description for several reference points in the WLAN-3GPP Interworking System.
The present document is applicable to:
• The Dw reference point between the 3GPP AAA Server and an SLF.
• The Wa reference point between the WLAN AN and the 3GPP AAA Proxy.
• The Wd reference point between the 3GPP AAA Proxy and 3GPP AAA Server.
• The Wx reference point between the 3GPP AAA Server and the HSS.
• The Wm reference point between the 3GPP AAA Server and the PDG.
• The Wg reference point between the 3GPP AAA Server/Proxy and the WAG.
• The Pr reference point between the 3GPP AAA Server and the PNA.
|
29.818
|
Study on the enhancement of protocols for SMS service over SGs
|
TR
|
0.1.1
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.818/29818-011.zip
|
The present document is a study on alternative protocols for the SMS over SGs architecture. Several involved interfaces are using MAP protocols for which alternative protocols will be analysed.
After addressing the requirements to introduce these protocol alternatives, the TR will identify which MAP procedures on the different interfaces for SMS need to have their equivalent with alternative protocols and will give their description with them. Interworking with other networks will be analysed with the possible use of interworking functions.
It will compare solutions with alternative protocols and make recommendations.
|
29.839
|
3GPP system - fixed broadband access network interworking; Home (e)Node B - security gateway interface
|
TR
|
11.0.0
|
C4
|
https://www.3gpp.org/ftp/Specs/archive/29_series/29.839/29839-b00.zip
|
The present document specifies the H(e)NB – SeGW interface. The interface is used for the interworking between a 3GPP system and a Fixed Broadband Access network defined by Broadband Forum. The interworking procedure provides the IP connectivity to a 3GPP UE using a H(e)NB connected to a Fixed Broadband Access network as specified in 3GPP TS 23.139 [3].
The specification covers the QoS aspects, and Tunnel management procedures.
|
30.821
|
Telecommunication management; Project scheduling and open issues for SA5, Release 11
|
TR
|
0.4.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/30_series/30.821/30821-040.zip
|
The present document contains the up-to-date SA5 Work Item Descriptions (WIDs) and captures the status of all SA5 work items in the current Release.
This TR is used as a mean to provide input to the 3GPP work plan handled by MCC.
Status list of Work items can be found in Annex A of the present document.
|
32.171
|
Telecommunication management; Subscription Management (SuM) Network Resource Model (NRM) Integration Reference Point (IRP); Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.171/32171-b00.zip
|
The present document defines, in addition to the requirements defined in [1], [2], [3] and [4], requirements for the present SuM NRM IRP.
|
32.172
|
Telecommunication management; Subscription Management (SuM) 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.172/32172-b00.zip
|
The present document defines the Network Resources Model (NRM) for the SuM IRP.
|
32.176
|
Telecommunication management; Subscription Management (SuM) 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.176/32176-b00.zip
|
The present document is part of an Integration Reference Point (IRP) named Subscription Management (SuM) Network Resource Model (NRM) IRP, through which an IRPAgent can communicate configuration management information to one or several IRPManagers concerning SuM resources. The SuM 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 SuM NRM IRP.
This specification is related to 3GPP TS 32.172 [5] V10.2.X.
|
32.252
|
Telecommunication management; Charging management; Wireless Local Area Network (WLAN) charging
|
TS
|
11.2.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.252/32252-b20.zip
|
The present document is part of a series of documents that specify charging functionality and charging management in GSM/UMTS networks. The GSM/UMTS core network charging architecture and principles are specified in 3GPP TS 32.240 [1], which provides an umbrella for other charging management documents that specify:
- the content of the CDRs per domain and subsystem (offline charging);
- the content of real-time charging messages per domain / subsystem (online charging);
- the functionality of online and offline charging for those domains and subsystems;
- the interfaces that are used in the charging framework to transfer the charging information (i.e. CDRs or charging events).
The complete document structure for these TSs is defined in 3GPP TS 32.240 [1].
The present document specifies the Offline and Online Charging description for the 3GPP interworked Wireless LAN (WLAN), based on the functional stage 2 description of 3GPP WLAN interworking in 3GPP TS 23.234 [201] as well as the Charging support and Charging differentiation for Mobility between 3GPP-Wireless Local Area Network (WLAN) interworking and 3GPP systems, based on the functional stage 2 description of mobility between 3GPP-WLAN and 3GPP systems in 3GPP TS 23.327 [202]. This charging description includes the offline and online charging architecture and scenarios specific to the 3GPP interworked WLAN, as well as the mapping of the common 3GPP charging architecture specified in 3GPP TS 32.240 [1] onto the 3GPP interworked WLAN. It further specifies the structure and content of the CDRs for offline charging, and the charging events for online charging. The present document is related to other 3GPP charging TSs as follows:
- The common 3GPP charging architecture is specified in 3GPP TS 32.240 [1].
- The parameters, abstract syntax and encoding rules for these CDR types are specified in 3GPP TS 32.298 [51].
- A transaction based mechanism for the transfer of CDRs within the network is specified in 3GPP TS 32.295 [54].
- The file based mechanism used to transfer the CDRs from the network to the operator's billing domain (e.g. the billing system or a mediation device) is specified in 3GPP TS 32.297 [52].
- The 3GPP Diameter application that is used for WLAN offline and online charging is specified in 3GPP TS 32.299 [50].
- The Online and Offline Charging description for Trusted WLAN Access Network to the 3GPP EPC, based on the functional stage 2 description in 3GPP TS 23.402 [209], is specified in 3GPP TS 32.251 [11].
All terms, definitions and abbreviations used in the present document, that are common across 3GPP TSs, are defined in the 3GPP Vocabulary, 3GPP TR 21.905 [100]. Those that are common across charging management in GSM/UMTS domains or subsystems are provided in the umbrella document 3GPP TS 32.240 [1] and are copied into clause 3 of the present document for ease of reading. Finally, those items that are specific to the present document are defined exclusively in the present document.
Furthermore, requirements that govern the charging work are specified in 3GPP TS 22.115 [102].
|
32.521
|
Telecommunication management; Self-Organizing Networks (SON) Policy Network Resource Model (NRM) Integration Reference Point (IRP); Requirements
|
TS
|
11.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.521/32521-b10.zip
|
The present document describes concept and requirements of SON Policy management for Self-Optimization and SON coordination.
|
32.522
|
Telecommunication management; Self-Organizing Networks (SON) Policy 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.522/32522-b70.zip
|
The present document is part of an Integration Reference Point (IRP) named Self Organizing Networks (SON) Policy Network Resource Model (NRM) IRP, through which an IRPAgent can communicate management information to one or several IRPManagers concerning SON policies. The SON policy 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 SON policy NRM IRP: Information Service (IS).
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 [11]). However, which Interface IRP is applicable is outside the scope of the present document.
The present document also contains stage 2 descriptions for those functionalities for the Self-Optimization OAM, SON coordination and Energy Saving Management.
|
32.526
|
Telecommunication management; Self-Organizing Networks (SON); Policy Network Resource Model (NRM) Integration Reference Point (IRP); Solution Set (SS) definitions
|
TS
|
11.7.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.526/32526-b70.zip
|
The present document specifies the Solution Set definitions for the IRP whose semantics is specified in 3GPP TS 32.522 [4] SON Policy Network Resource Model IRP: Information Service (IS).
This Solution Set definitions specification is related to 3GPP TS 32.522 V11.7.X [4].
|
32.621
|
Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Requirements
|
TS
|
11.0.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.621/32621-b00.zip
|
The present document defines , in addition to the requirements defined in [1], [2] and [3], the requirements for the present IRP: Generic Network Resources IRP.
|
32.622
|
Telecommunication management; Configuration Management (CM); Generic network resources Integration Reference Point (IRP); Network Resource Model (NRM)
|
TS
|
11.1.0
|
S5
|
https://www.3gpp.org/ftp/Specs/archive/32_series/32.622/32622-b10.zip
|
The present document specifies the Generic network resource information that can be communicated between an IRPAgent and one or several IRPManagers for network management purposes.
This document specifies the semantics 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.
The document specifies the information in a generic manner in that the information specified is a base from which all other NRM IRP ISs such as GERAN NRM IRP IS [20] can inherit or have associations with.
|
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.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.