Tech-invite 3GPPspecs RELs Glossaries SIP

Info 21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 4‑5x

TR 23.830 SA2 ★
Architecture aspects of
Home Node B (HNB) / Home enhanced Node B (HeNB)

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced

V9.0.0 (Wzip) 2009/10 55 p.

Rapporteur: Dr. Speicher, Sebastian

This TR describes the architectural aspects of specific UTRAN and E-UTRAN base stations, known as Home NodeBs and Home eNodeBs, which provide services in e.g. residential or enterprise deployments.

full Table of Contents for TR 23.830 Word version: 9.0.0

1 Scope Word-p. 7

3 Definitions and abbreviations Word-p. 8

3.1 Definitions

3.2 Abbreviations Word-p. 9

4 Architectural baseline and assumptions from Rel-8

4.1 Impacting specifications/reports from other 3GPP WGs

4.2 Home NodeB architectural baseline and assumptions Word-p. 10

4.2.1 Architectural assumptions

4.2.2 Architectural requirements

4.2.2.1 Support for CSGs and Allowed CSG List handling

4.2.2.2 Access control Word-p. 11

4.2.2.3 Mobility management

4.2.3 Architecture model for Home NodeB access network

4.2.3.1 Logical architecture

4.2.3.2 Functional entities Word-p. 12

4.2.3.3 Reference points

4.2.3.4 Functional split Word-p. 13

4.3 Home eNodeB architectural baseline and assumptions Word-p. 15

4.3.1 Architectural requirements

4.3.1.1 Support for CSGs and Allowed CSG List handling

4.3.1.2 Access control Word-p. 16

4.3.1.3 Mobility management

4.3.2 Architecture model for Home eNodeB access network

4.3.2.1 Logical architecture

4.3.2.1.1 Variant 1: With dedicated HeNB GW Word-p. 17

4.3.2.1.2 Variant 2: Without HeNB GW

4.3.2.1.3 Variant 3: With HeNB GW for C-Plane Word-p. 18

4.3.2.2 Functional entities

4.3.2.3 Reference points

4.3.2.4 High level functional split Word-p. 19

5 Architectural requirements Word-p. 21

5.1 General requirements

5.1.1 Installation, identification and location requirements

5.1.2 CSG Membership Management

5.1.3 Mobility management

5.1.3.1 Connected Mode

5.1.3.2 Idle Mode

5.1.4 Charging Requirements

5.1.5 Emergency Services Requirements Word-p. 22

5.1.6 QoS and Admission Control Requirements

5.1.7 Local IP Access in Home-based Network Requirements

5.1.8 Local IP Access to Internet Requirements Word-p. 23

5.1.9 Managed Remote Access to home based network

5.2 Home NodeB specific requirements

5.2.1 Access control

5.3 Home eNodeB specific requirements

5.3.1 General requirements

5.3.2 Access control

5.3.3 Mobility management Word-p. 24

6 Architectural issues and solutions

6.1.2 Architectural issue - Needs for a master list of CSG IDs in VPLMN

6.1.2.1 Description

6.1.2.2 Solutions

6.1.2.2.1 Solution 1

6.1.2.3 Evaluation Word-p. 25

6.1.3 Architectural issue - Identity used for CSG members (Rel-8?)

6.1.3.1 Description

6.1.3.2 Solutions Word-p. 27

6.1.3.2.1 Solution 1

6.1.3.3 Evaluation

6.1.4 Architectural issue - Managing changes to CSG membership and handling of CSG ID expiration time Word-p. 28

6.1.4.1 Description

6.1.4.2 Solutions

6.1.4.2.1 Solution 1

6.1.4.3 Evaluation Word-p. 30

6.2 Release 8 and Release 9 Word-p. 32

6.3.1 Architectural issue - Time period control

6.3.1.1 Description

6.3.1.2 Solutions Word-p. 36

6.3.1.2.1 Solution 1

6.3.1.2.2 Solution 2

6.3.1.3 Evaluation

6.3.2 Architectural issue - Diversion of established communications

6.3.2.1 Description

6.3.2.2 Solutions Word-p. 37

6.3.2.2.1 Solution 1

6.3.2.2.2 Solution 2

6.3.2.3 Evaluation

6.3.2.3.1 Diversion of established communications at the expiry of the time period for temporary CSG members

6.3.2.3.2 Diversion of established communications from a hybrid CSG cell when services cannot be provided to a CSG member due to a shortage of HNB/HeNB resources

6.3.3 Architectural issue - Number limit Word-p. 38

6.3.3.1 Description

6.3.3.2 Solutions

6.3.3.2.1 Solution 1

6.3.3.3 Evaluation

6.3.5 Architectural issue - Shared network aspects

6.3.5.1 Description

6.3.5.2 Solutions Word-p. 39

6.3.5.3 Evaluation

6.3.6 Architectural issue - In-bound H(e)NB handover support

6.3.6.1 Description

6.3.6.2 Solutions

6.3.6.2.1 Solution 1: Including the Allowed CSG list in the Handover Restriction List IE

6.3.6.2.2 Solution 2: CSG Access control in the Core Network with support from the source RAN node Word-p. 40

6.3.6.2.3 Solution 3: CSG Access control in the Core Network with support from the target RAN node

6.3.6.3 Evaluation

6.3.7 Architectural issue - Open and hybrid access mode H(e)NB support Word-p. 41

6.3.7.1 Description

6.3.7.2 Sub-issues

6.3.7.2.1 Sub-Issue 1 - Management of the UE's Allowed CSG list

6.3.7.2.2 Sub-Issue 2 - Admission control and rate control for hybrid access mode Word-p. 42

6.3.7.2.3 Sub-Issue 3 - Indicating the access mode to other network entities Word-p. 43

6.3.7.2.4 Sub-Issue 4 - Diversion of established communication for a non-CSG member

6.3.7.3 Evaluation

6.3.8 Architectural issue - CSG membership management (Rel-9?)

6.3.8.1 Description

6.3.8.2 Solutions Word-p. 44

6.3.8.3 Evaluation

6.3.9 Support for Local IP Access

6.3.9.1 Description

6.3.9.2 Solutions

6.3.9.2.1 Solutions covering both LIPA to the Internet and to the home-based network

6.3.9.3 Evaluation Word-p. 46

6.3.11 Architectural issue - Support of Emergency Services

6.3.11.1 Description

6.3.11.2 Solutions

6.3.11.2.1 Solution 1

6.3.11.3 Evaluation

6.4.1 Architectural issue - Storage of CSG ID for temporary & roaming CSG members

6.4.1.1 Description

6.4.1.2 Solutions Word-p. 47

6.4.1.2.1 Solution 1: Storage of CSG ID for temporary CSG members

6.4.1.2.2 Solution 2 Word-p. 48

6.4.1.2.3 Solution 3: Storage of CSG ID for Roaming CSG Members on the network Word-p. 49

6.4.1.2.4 Solution 4: Storage of CSG ID for Temporary CSG Members and Roaming CSG Members on the network

6.4.1.3 Evaluation Word-p. 50

A Functional split for HNB access as per TS 25.467 [3] Word-p. 51

B Functional split for HeNB access as per TS 36.300 [4] Word-p. 53

C Actions of MME/SGSN/MSC/VLR upon Allowed CSG List update Word-p. 54

D Change history Word-p. 55