tech-invite   World Map     

3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search

Top          in Index          Prev          Next

TR 23.832 (SA2)
IMS aspects of architecture for
Home Node B (HNB)

|   ToC   |   3GPP‑Page   |   Help   |

(W-zip) V10.0.0    2010/03    84 p.


Rapporteur:  Mr. Drevon, Nicolas
See also:  H(e)NB-related TS/TR    


This TR describes an IMS capable HNB SubSystem (the HNB and the HNB Gateway) as an optional capability of HNB that allows e.g. an operator to offload CS traffic to the IMS. The HNB and HNB Gateway are described in TR 23.830, and the capabilities of these network elements are assumed by this TR.

To achieve this and to satisfy the related requirements and use cases captured in TS 22.220, the objective is to investigate the following:
  • an architecture to enable IMS capable HNB Subsystem to use the IMS for CS terminals using a corresponding equivalent IMS services (voice service in IMS Multimedia Telephony);
  • the impacts of the IMS capable HNB Subsystem to idle mode mobility for all supported UE types (e.g. IMS registration/de-registration);
  • service continuity at least in the direction from IMS capable HNB Subsystem to macro network;
  • support for pre-Rel-9 CS and IMS UEs when using IMS capable HNB Subsystem.
The TR will analyze solutions for the related architectural issues and capture the conclusions.


 

Here          Top

 

 

1   Scope   Word-p. 7
2   References
3   Definitions and abbreviations   Word-p. 8
4   Service Scenarios
5   Architectural Requirements   Word-p. 9
6   Architecture Alternatives   Word-p. 10
6.1   Alternative 1
6.2   Alternative 2: IMS capable HNB Subsystem using IMS centralised services IWF   Word-p. 27
6.3   Void
6.4   Alternative 4 - IMS HNB GW as SIP UA and HO anchor   Word-p. 28
6.4.1   Introduction      Up
6.4.2   Reference architecture
6.4.3   Functional Entities   Word-p. 29
6.4.4   Interfaces and Reference points
6.4.5   Registration
6.4.6   Origination
6.4.7   Termination   Word-p. 38
6.4.8   Control and user plane paths before and after handover      Up
6.4.9   Handover to macro   Word-p. 43
6.4.10   Handover to HNB   Word-p. 46
6.4.11   Supplementary services   Word-p. 49
6.5   Void
6.6   Alternative 6: Consolidated Architecture with SIP UA in HNB
6.7   Alternative 7: Architecture for IMS-capable HNB subsystem with the SIP UA in the HNB GW   Word-p. 65
6.8   Alternative 8: Interworking of IMS at HNB and HNB-CAS   Word-p. 69
7   Assessment   Word-p. 82
8   Conclusion
A   Change history   Word-p. 83

Up          Top