Tech-invite3GPPspaceIETF RFCsSIP

Content for  TR 23.812  Word version:  11.0.0

Top   Top   None   None   Next
1…   4…


1  Scopep. 7

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.
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.

2  Referencesp. 8

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
TR 21.905: "Vocabulary for 3GPP Specifications".
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interfaces; Signalling flows and message contents".
ETSI ES 283 034-2 V3.1.1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Congestion and Overload Control; Part 2: Core GOCAP and NOCA Entity Behaviours".
draft-ietf-soc-overload-control-01:  "Session Initiation Protocol (SIP) Overload Control".
draft-ietf-soc-load-control-event-package:  "A Session Initiation Protocol (SIP) Load Control Event Package".
RFC 2136:  "Dynamic Updates in the Domain Name System (DNS UPDATE)".
RFC 1034:  "Domain Names - Concepts and Facilities".
RFC 1995:  "Incremental Zone Transfer in DNS".

3  Definitions and abbreviationsp. 8

3.1  Definitionsp. 8

For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
Load Balancing:
technique to distribute workload evenly across two or more network nodes implementing the same functions, in order to get optimal resource utilization.
Overload Control:
technique to detect and react to the near-congestion state of a network /node.
Congestion Control:
a set of actions taken to relieve congestion by limiting the spread and duration of it. (ITU-T Recommendation I.113, definition 703).

3.2  Abbreviationsp. 9

For the purposes of the present document, the abbreviations given in TR 21.905 apply.

Up   Top   ToC