10 Charging Aspects
22.2203GPPRelease 17Service requirements for Home Node B (HNB) and Home eNode B (HeNB)TS
NOTE: Refer to charging requirements in TS 22.115 [8]
Annex A (informative): Use cases
These use cases do not imply any requirement beyond that which is contained in the normative part of this TS.
Usecase-1: H(e)NB Mobility
User A connects to the H(e)NB via mobile device. User A should be able to move around within the H(e)NB coverage in the home or enterprise. User should also be able to invoke additional services based on user policy and operator policy.
Usecase-2: H(e)NB Guest Users
User A and User B are subscribers of Operator 1 and Operator 2 respectively. User A visits User B in his home and User B allows User A to use H(e)NB in User B’s home. User A should be able to access all the services he is subscribed to from Operator 1 based on the policies set by User B and operator 2. Operator 1 and Operator 2 have roaming agreement.
Usecase-3: HNB/HeNB – NB/eNB Handovers
User A subcribes to cellular services of Operator 1 and is authorised to access a HNB/HeNB from same or other operator. User A starts service in the H(e)NB coverage and continues moving into a cellular network. Similarly User A starts service in cellular network and continues moving into H(e)NB coverage. User A does not see any impact on services due to mobility in both cases.
Usecase-4: Access to Home based services
User A connects to the H(e)NB via mobile device. User A should be able to access home based services (e.g. local digital media servers and digital media players) from the mobile device. Other users may access the home based services subject to H(e)NB Hosting Party policies.
Usecase-5: Media Transfer
User A connects to the H(e)NB via mobile device. User A starts viewing video streaming service on the mobile device. User A then wants to continue viewing the video on a different screen for better viewing. User A should be able to transfer the session to a high-definition TV or PC connected via broadband connection. User A should also be able to transfer the session from the TV or PC to a mobile device and continue the session in the H(e)NB coverage and also in the cellular network.
Usecase-6: IMS capable HNB used for coverage purposes
In this scenario, the reason for an operator to introduce IMS capable HNB is to offload voice traffic from his existing CS core network to IMS. However, as in this scenario the usage of ‘legacy’ services (e.g. CS Fax) is still assumed – only the utilization of network resources is to be changed – it is requested that IMS capable HNB provides all the services/ capabilities that are provided through regular Node B from the beginning.
Usecase-7: IMS capable HNB for a new business model
This scenario starts with a view that HNB is located in the user’s residence and the UE is the preferred equipment to interact with home services/ applications. New business can be expected there. In this scenario, some of the CS services/ capabilities that are provided through regular Node B might not be needed or might be provided in a later step if the operator could instead offer attractive new services under IMS capable HNB only.
Usecase-8: IMS capable HNB for Green field operator
This scenario expects new players to get into the mobile market. In this scenario, they would aim to deploy cost efficient and future proof infrastructure, i.e. no CS domain but IMS/PS domain only, regardless of whether or not UEs have IMS client on them.
Usecase-9: Hybrid access mode
In order to improve the coverage in a shopping mall, H(e)NBs are deployed. The shopping mall owner may have been provided a special deal by the network operator where the employees of the shopping mall will get preferential charging rates and priority access when accessing services via these H(e)NBs. In exchange, the shopping mall owner allows the public to use the H(e)NBs to access the normal network operator services. The H(e)NB Hosting Party should not need to manage the public access and the public should not need to do anything special in order to get services on the H(e)NB.
Use case-10: Open access mode
Typically to enhance coverage or capacity of an operator’s public network, for example in railway stations, airports, stadiums, etc, taking benefit of the H(e)NBs additional functionality (e.g. uncoordinated deployment).
Usecase-11: HNB interacts with Home network
User A connects with his UE (possibly a pre-Rel 9 UE) to the HNB with IMS Interworking and Local IP Access to the home network capabilities. The home network accommodates home network devices (Intercom, Door lock, Network radio, Photo server, etc.) and the HNB. User A should be able to communicate with a visitor at Intercom via the mobile device.
Usecase-12: HNB interacts with IP-PABX
User A connects with his UE (possibly a pre-Rel 9 UE) to a HNB with IMS Interworking and Local IP Access to the home network capabilities at an office. The HNB might be deployed and interconnect with an enterprise extension telephone system (e.g. SIP based PABX). User A should be able to make/receive an extension call to/from fixed line UE under SIP based PABX. In addition, User A with the mobile device and User B with computers should be able to access a common groupware server at the office and share the same information such as schedule, emails, etc.
Usecase-13: Electronic customer guide in shopping centre, using Local IP access
A department store or shopping centre provides electronic shopping guide. When user A enters into a shopping centre where a shopping centre H(e)NB is installed, an invitation indication shows up on his mobile device which he accepts. This allows him access to the centre’s H(e)NB. Subsequently, he accesses the centre’s customer service server, which is only accessible through the H(e)NB where he uploads his shopping list. The customer service server responds a list of sale items of similar nature. He accepts or declines the various choices and the final shopping list is downloaded to his UE. While user A is waiting, User A watches free TV show or advertisement provided through the H(e)NB for the shop customer. While in the shopping centre the user has simultaneous access to operator’s and local shopping centre services.
Usecase-14: Local IP Access
The user has the subscription through home operator H. The user is served by the home operator H. The UE obtains IP connectivity in both a local gateway to obtain local connectivity for IMS services (e.g. as in local IP access or for enterprise scenarios with call to other terminals in the PABX area) and to a home gateway (as in normal connectivity for IMS services). For IMS sessions to be routed to e.g. remote terminals, the traffic is sent through the connectivity with the home gateway, whereas for IMS session that can be routed locally (e.g. based on local phone number), the traffic is sent through the connectivity with the local gateway through the local IP access. Whether the UE routes a specific IMS session through the local access or the home gateway can be controlled on a per session basis. Also, the UE may obtain local connectivity by default (e.g. based on static configuration by the operator) or dynamically based on indication by the IMS server.
Usecase-15:
Subscriber A from Network A owns HNB/HeNB A because of no macro network coverage .
Guest user B from Network B visits subscriber A’s house. Subscriber A wants to allow guest user B access to HNB/HeNB A while the guest user B is visiting.
Usecase-16:
Corporation A has sites in country A, B and C.
Corporation A has employees from country A and B.
Employees in country A are from Operator AA and AB.
Employees in country B are from Operator B.
Corporation A has HNB/HeNB in country A from Operator AA and country B from Operator B.
Employees from country A and B are allowed access to HNB/HeNBs in country A and B.
Usecase-17: Content-sharing services in the residential IP network
During a trip to the zoo Alice has taken several pictures and has recorded a video clip on her UE. After returning home her UE connects to the H(e)NB in the home and accesses the residential IP network. The local devices (video, printer, ..) are automatically discovered by the UE. Alice views the videos on her video player, prints photos on her printer, uploads her media onto media server, and downloads media for her next outing.
Annex B (informative): Clarification of H(e)NB Access Modes
Table B.1 illustrates the different H(e)NB Access Modes and what access is allowed for UEs of any release depending on whether the UE is allowed access to the CSG.
In Table B.1 “Access” means “Access to services”.
“Preferential access” means the user will get preferential access to the cell.
Table B.1: H(e)NB access for UEs of any release
|
H(e)NB Access Mode |
|||
|
Open |
Closed |
Hybrid |
|
|
UE allowed access to CSG |
Access |
Access |
Preferential Access |
|
UE not allowed access to CSG |
Access |
No Access |
Access |
NOTE: Pre Release 8 UEs can only access HNBs
Annex C (informative): Overview of identifiers and names.
Table C.1: Overview of identifiers and names
|
item |
used for |
associated with |
permanently stored in |
distribution method |
displayed to user |
comment |
|
H(e)NB equipment identity |
|
H(e)NB (physical entity) |
|
O&M procedures |
NO |
not known to UE, therefore not useable by UE to identify a H(e)NB |
|
CSG identity |
|
|
|
|
YES, if HNB Name is not available |
A CSG identity is unique within a PLMN. In the UE a CSG ID, together with a network identifier, identifies a CSG globally uniquely. |
|
HNB name (optional) |
for supporting (ease of use) manual CSG selection, displaying a “friendly” name to the user |
CSG identity |
|
|
YES during manual selection, OPTIONAL during normal operation. (USIM entry takes precedence over broadcast and ME) |
If a HNB name is stored in the UE it needs to be associated with a CSG identity. Initial configuration in the UE may be done by the operator (e.g. at point of sale). Later, a HNB name is implicitly associated to the current CSG identity by the UE when the user stores the HNB name |
|
CSG Type |
for additional information (on e.g. billing mode) to the user when camping on a CSG cell (i.e. after CSG has been selected) |
CSG identity (relationship: |
|
|
YES, if CSG is in Allowed CSG List. (USIM entry takes precedence over ME) |
UE needs to associate a CSG Type with a CSG identity |
Annex D (informative): Change history
|
TSG SA# |
SA Doc. |
SA1 Doc |
Spec |
CR |
Rev |
Rel |
Cat |
Subject/Comment |
Old |
New |
WI |
|
SP-43 |
SP-090087 |
– |
22.220 |
– |
– |
– |
– |
Approved by SA plenary. |
2.0.0 |
9.0.0 |
EHNB |
|
SP-44 |
SP-090373 |
S1-091273 |
22.220 |
0002 |
1 |
Rel-9 |
F |
Clarification on the displaying of the H(e)NB name during manual CSG selection |
9.0.0 |
9.1.0 |
EHNB |
|
SP-44 |
SP-090373 |
S1-091164 |
22.220 |
0004 |
4 |
Rel-9 |
B |
Optional USIM support in H(e)NB |
9.0.0 |
9.1.0 |
EHNB |
|
SP-44 |
SP-090373 |
S1-091387 |
22.220 |
0011 |
3 |
Rel-9 |
F |
Clarification on Local IP Access Requirements |
9.0.0 |
9.1.0 |
EHNB |
|
SP-44 |
SP-090373 |
S1-091083 |
22.220 |
0015 |
– |
Rel-9 |
F |
Remove VPLMN CSG support for Rel9 |
9.0.0 |
9.1.0 |
EHNB |
|
SP-44 |
SP-090373 |
S1-091382 |
22.220 |
0016 |
2 |
Rel-9 |
F |
Clarification on the requirement of session diversion. |
9.0.0 |
9.1.0 |
EHNB |
|
SP-44 |
SP-090373 |
S1-091279 |
22.220 |
0019 |
2 |
Rel-9 |
F |
Allowed CSG list management for hybrid cells |
9.0.0 |
9.1.0 |
EHNB |
|
SP-44 |
SP-090373 |
S1-091158 |
22.220 |
0023 |
3 |
Rel-9 |
D |
Clarification of H(e)NB Owner / Hosting Party |
9.0.0 |
9.1.0 |
EHNB |
|
SP-44 |
SP-090373 |
S1-091159 |
22.220 |
0024 |
2 |
Rel-9 |
D |
H(e)NB Operator Change |
9.0.0 |
9.1.0 |
EHNB |
|
SP-44 |
SP-090373 |
S1-091383 |
22.220 |
0025 |
2 |
Rel-9 |
F |
Clarification of the terminology about H(e)NB access modes |
9.0.0 |
9.1.0 |
EHNB |
|
SP-44 |
SP-090373 |
S1-091274 |
22.220 |
0026 |
1 |
Rel-9 |
F |
Minor corrections for clarification |
9.0.0 |
9.1.0 |
EHNB |
|
SP-44 |
SP-090374 |
S1-091260 |
22.220 |
0005 |
1 |
Rel-9 |
F |
Rel 8 Rel 9 CSG lists alignment (approved at SA#44 but not implemented in 9.1.0) |
9.1.0 |
9.1.1 |
EHNB |
|
SP-45 |
SP-090477 |
S1-093332 |
22.220 |
0032 |
2 |
Rel-9 |
F |
CSG Lists clarification |
9.1.1 |
9.2.0 |
EHNB |
|
SP-45 |
SP-090477 |
S1-093329 |
22.220 |
0035 |
1 |
Rel-9 |
F |
IP access approach of backhaul network for H(e)NB |
9.1.1 |
9.2.0 |
EHNB |
|
SP-45 |
SP-090477 |
S1-093331 |
22.220 |
0037 |
1 |
Rel-9 |
D |
Editorial corrections of TS 22.220 |
9.1.1 |
9.2.0 |
EHNB |
|
SP-45 |
SP-090477 |
S1-093480 |
22.220 |
0039 |
2 |
Rel-9 |
C |
Loss of IP Backhaul Connection |
9.1.1 |
9.2.0 |
EHNB |
|
SP-45 |
SP-090477 |
S1-093330 |
22.220 |
0041 |
1 |
Rel-9 |
F |
Clarification of definition for H(e)NB Hosting Party |
9.1.1 |
9.2.0 |
EHNB |
|
SP-45 |
SP-090483 |
S1-093477 |
22.220 |
0038 |
4 |
Rel-10 |
F |
CR to 22.220 on Clarification of QoS Requirements |
9.1.1 |
10.0.0 |
TEI 10 |
|
SP-46 |
SP-090839 |
S1-094318 |
22.220 |
0057 |
1 |
Rel-10 |
A |
Simplified CSG list handling |
10.0.0 |
10.1.0 |
EHNB |
|
SP-46 |
SP-090845 |
S1-094323 |
22.220 |
0067 |
2 |
Rel-10 |
B |
H(e)NB mobility related load optimization |
10.0.0 |
10.1.0 |
EHNBF |
|
SP-46 |
SP-090845 |
S1-094380 |
22.220 |
0063 |
3 |
Rel-10 |
B |
Requirements on HNBs in enterprise environments |
10.0.0 |
10.1.0 |
EHNBF |
|
SP-46 |
SP-090849 |
S1-094328 |
22.220 |
0046 |
3 |
Rel-10 |
B |
Local IP Access requirements update |
10.0.0 |
10.1.0 |
LIPA_SIPTO |
|
SP-46 |
SP-090849 |
S1-094321 |
22.220 |
0047 |
2 |
Rel-10 |
B |
Selected IP Traffic Offload Requirements for H(e)NB SubSystem |
10.0.0 |
10.1.0 |
LIPA_SIPTO |
|
SP-46 |
SP-090849 |
S1-094429 |
22.220 |
0062 |
1 |
Rel-10 |
B |
Use case for digital content sharing with LIPA |
10.0.0 |
10.1.0 |
EHNBF |
|
SP-47 |
SP-100186 |
S1-100331 |
22.220 |
0072 |
1 |
Rel-10 |
B |
Termination of data session |
10.1.0 |
10.2.0 |
EHNBF |
|
SP-47 |
SP-100186 |
S1-100328 |
22.220 |
0080 |
1 |
Rel-10 |
F |
IMS HNB interworking alignment with SA2 decision |
10.1.0 |
10.2.0 |
EHNBF |
|
SP-47 |
SP-100186 |
S1-100453 |
22.220 |
0092 |
3 |
Rel-10 |
B |
Add VPLMN CSG support for Rel-10 |
10.1.0 |
10.2.0 |
EHNB |
|
SP-47 |
SP-100230 |
S1-100324r |
22.220 |
0094 |
1 |
Rel-10 |
A |
Clarification of the interaction of the Operator and Allowed CSG lists |
10.1.0 |
10.2.0 |
EHNB |
|
SP-47 |
SP-100187 |
S1-100316 |
22.220 |
0070 |
1 |
Rel-10 |
B |
Mobility for Local IP Access (LIPA) |
10.1.0 |
10.2.0 |
LIPA_SIPTO |
|
SP-47 |
SP-100187 |
S1-100012 |
22.220 |
0071 |
– |
Rel-10 |
F |
Removal of SIPTO common requirements |
10.1.0 |
10.2.0 |
LIPA_SIPTO |
|
SP-47 |
SP-100187 |
S1-100326 |
22.220 |
0082 |
3 |
Rel-10 |
B |
Clarification of requirements for LIPA |
10.1.0 |
10.2.0 |
LIPA_SIPTO |
|
SP-47 |
SP-100188 |
S1-100025 |
22.220 |
0073 |
– |
Rel-10 |
A |
H(e)NB Hosting Party USIM management |
10.1.0 |
10.2.0 |
TEI-10 |
|
SP-48 |
SP-100402 |
S1-101248 |
22.220 |
0100 |
3 |
Rel-10 |
F |
Enable/disable Selected IP Traffic Offload per H(e)NB |
10.2.0 |
10.3.0 |
LIPA_SIPTO |
|
SP-48 |
SP-100399 |
S1-101250 |
22.220 |
0101 |
4 |
Rel-10 |
F |
Clarification of the CSG list in networks, Operator CSG list (OCL) and Allowed CSG list (ACL) |
10.2.0 |
10.3.0 |
EHNBF |
|
SP-49 |
SP-100573 |
S1-102388 |
22.220 |
0110 |
4 |
Rel-10 |
F |
Removal of requirement to inhibit Allowed CSG List and VPLMN Autonomous CSG Roaming clarifications |
10.3.0 |
10.4.0 |
EHNBF |
|
SP-49 |
SP-100576 |
S1-102399 |
22.220 |
0106 |
3 |
Rel-10 |
F |
Correction on HNB Name |
10.3.0 |
10.4.0 |
EHNBF |
|
SP-49 |
SP-100576 |
S1-102404 |
22.220 |
0107 |
4 |
Rel-10 |
F |
Clarification of LIPA requirements |
10.3.0 |
10.4.0 |
EHNBF |
|
SP-49 |
SP-100578 |
S1-102197 |
22.220 |
0105 |
3 |
Rel-10 |
F |
SIPTO for H(e)NB Subsystems Policy and User Interaction |
10.3.0 |
10.4.0 |
LIPA_SIPTO |
|
SP-49 |
SP-100578 |
S1-102400 |
22.220 |
0104 |
3 |
Rel-10 |
F |
Enablement/disablement policies for LIPA |
10.3.0 |
10.4.0 |
LIPA_SIPTO |
|
SP-50 |
SP-100796 |
S1-103277 |
22.220 |
0117 |
1 |
Rel-10 |
F |
Requirement on conditional LIPA |
10.4.0 |
10.5.0 |
LIPA_SIPTO |
|
SP-50 |
SP-100796 |
S1-103348 |
22.220 |
0118 |
3 |
Rel-10 |
F |
Clarification on "enable/disable LIPA" |
10.4.0 |
10.5.0 |
LIPA_SIPTO |
|
SP-51 |
SP-110161 |
S1-110183 |
22.220 |
0123 |
2 |
Rel-11 |
A |
Hosting Party Identity Module |
11.0.0 |
11.1.0 |
TEI9 |
|
SP-51 |
SP-110172 |
S1-110178 |
22.220 |
0119 |
3 |
Rel-11 |
B |
New Requirements for Enterprise Interworking scenario |
11.0.0 |
11.1.0 |
TEI 11 |
|
SP-52 |
SP-110368 |
S1-111403 |
22.220 |
0133 |
1 |
Rel-11 |
A |
Correction to the admission control for the H(e)NB |
11.1.0 |
11.2.0 |
TEI11 |
|
SP-52 |
SP-110369 |
S1-111432 |
22.220 |
0129 |
1 |
Rel-11 |
A |
Removal of PBX integration requirements |
11.1.0 |
11.2.0 |
EHNBF |
|
SP-52 |
SP-110376 |
S1-111126 |
22.220 |
0134 |
– |
Rel-11 |
F |
Clarification for SIPTO policy |
11.1.0 |
11.2.0 |
TEI11 |
|
SP-53 |
SP-110582 |
S1-112387 |
22.220 |
0142 |
1 |
Rel-11 |
F |
Clarification for SIPTO user consent |
11.2.0 |
11.3.0 |
TEI11 |
|
SP-53 |
SP-110582 |
S1-112394 |
22.220 |
0136 |
1 |
Rel-11 |
F |
SIPTO for the Local Residential/Enterprise Networks |
11.2.0 |
11.3.0 |
TEI11 |
|
SP-53 |
SP-110582 |
S1-112395 |
22.220 |
0140 |
2 |
Rel-11 |
F |
H(e)NB behaviour in case of absence of the UICC |
11.2.0 |
11.3.0 |
TEI11 |
|
SP-53 |
SP-110582 |
S1-112396 |
22.220 |
0137 |
3 |
Rel-11 |
B |
Allow the H(e)NB UICC application to acquire location Information |
11.2.0 |
11.3.0 |
TEI11 |
|
SP-54 |
SP-110871 |
S1-113415r |
22.220 |
0147 |
2 |
Rel-11 |
A |
H(e)NB emergency call support |
11.3.0 |
11.4.0 |
EHNB |
|
SP-54 |
SP-110808 |
S1-113458 |
22.220 |
0149 |
1 |
Rel-11 |
A |
MBMS not supported for HeNB |
11.3.0 |
11.4.0 |
EHNB |
|
SP-57 |
SP-120520 |
S1-122477 |
22.220 |
0156 |
3 |
Rel-11 |
A |
Optional UICC authentication |
11.5.0 |
11.6.0 |
TEI9 |
|
2014-10 |
Updated to Rel-12 by MCC |
11.6.0 |
12.0.0 |
||||||||
|
2015-12 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-13 by MCC |
12.0.0 |
13.0.0 |
|
|
2017-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-14 by MCC |
13.0.0 |
14.0.0 |
|
|
2019-07 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-15 version (MCC) |
14.0.0 |
15.0.0 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2020-07 |
SA#88e |
– |
– |
– |
– |
Updated to Rel-16 by MCC |
16.0.0 |
|
2022-03 |
SA#95e |
– |
– |
– |
– |
Updated to Rel-17 by MCC |
17.0.0 |