Content for TR 23.839 Word version: 12.0.0
0 Introduction
1 Scope
2 References
3 Definitions and abbreviations
3.1 Definitions
3.2 Abbreviations
4 Building Blocks
...
...
0 Introduction p. 8
The collaborative work between 3GPP and BBF resulted in a Workshop in February 2010 focusing on Fixed-Mobile Convergence. As a result of this work, it has been identified that several working groups in 3GPP will need to work on: requirements, architecture, security and OA&M. This TR focuses on the architecture aspects of this study. The work includes three building blocks containing specific aspects of the study which are to be conducted within this technical report.
1 Scope p. 9
Based on requirements documented in the stage 1 specifications, this technical report addresses system architecture impacts to support BBF Access Interworking. The study includes multiple phases and covers aspects such as basic connectivity, mobility, authentication and authorisation, policy and QoS aspects, IP Flow mobility, traffic offload, convergence etc.
In each Building Block, the TR describes what changes are expected to normative TSs, e.g. TS 23.402 and TS 23.203.
The work is divided into three separate Building Blocks. See clause 4 for an outline of the content of each building block.
2 References p. 9
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.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.401: "GPRS Enhancements for E-UTRAN Access".
[3]
TS 23.402: "Architecture enhancements for Non-3GPP Accesses ".
[4]
TS 23.203: "Policy and charging control architecture".
[5]
TS 22.278: "Service requirements for the Evolved Packet System (EPS)".
[6]
Broadband Forum WT-203 "Interworking between Next Generation Fixed and 3GPP Wireless Access" (work in progress).
[7]
Broadband Forum TR-058 "Multi-service Architecture and Framework Requirements" September 2003.
[8]
Broadband Forum TR-101 "Migration to Ethernet-based DSL Aggregation" April 2006.
[9]
TS 23.261: "IP Flow Mobility and seamless WLAN offload".
[10]
Broadband Forum WT-145 "Multi-service Broadband Network Functional Modules and Architecture" work in progress.
[11]
Broadband Forum WT-134 "Policy Control Framework " work in progress.
[12]
TS 25.467: "UTRAN architecture for 3G Home Node B (HNB); Stage 2".
[13]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[14]
TS 22.220: "Service requirements for Home Node B (HNB) and Home eNode B (HeNB)".
[15]
TS 33.320: "Security of Home Node B (HNB) / Home evolved Node B (HeNB)".
[16]
TS 33.210: "Network Domain Security; IP network layer security".
[17]
TS 33.310: "Network Domain Security (NDS); Authentication Framework (AF)".
[18]
RFC 4555: "IKEv2 Mobility and Multihoming Protocol (MOBIKE)".
[19]
TS 29.274: "General Packet Radio Service (GPRS); Evolved GPRS Tunnelling Protocol (eGTP) for EPS".
[20]
BBF TR-092: "Broadband Remote Access Server (BRAS) Requirements".
[21]
BBF TR-124: Issues 2 "Functional Requirements for Broadband RG Devices".
[22]
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[23]
TS 23.234: "3GPP system to Wireless Local Area Network (WLAN) interworking".
[24]
TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".
[25]
TS 32.296: "Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces".
[26]
draft-ietf-netext-pmip6-qos-01: "Quality of Service Option for Proxy Mobile IPv6", work in progress.
3 Definitions and abbreviations p. 10
3.1 Definitions p. 10
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.
3GPP Femto:
Refers to the HNB and HeNB NEs as defined by 3GPP. The HNB GW is always required for the HNB architecture while the HeNB GW is option for the HeNB.
UE local IP address is defined as:
either the public IP address assigned to the UE by the BBF domain in the no-NAT case, or the public IP address assigned by the BBF domain to the NATed RG that is used for this UE.
H(e)NB local IP address is defined as:
either the public IP address assigned to the H(e)NB by the BBF domain in the no-NAT case, or the public IP address assigned by the BBF domain to the NATed RG that is used for this H(e)NB.
Non-seamless WLAN offload (NS WLAN-offload):
is a capability of a UE supporting routing specific IP flows over the WLAN access without traversing the EPC as defined in clause 4.1.5 of TS 23.402.
EPC-routed:
User plane traffic that is routed via a PDN GW in EPC as part of a PDN Connection. EPC-routed applies to non-roaming, roaming with traffic home-routed and roaming with traffic local break-out cases.
Fixed Access session:
is an abstraction for the connectivity service in BBF network which is related to one fixed network subscriber, irrespective of access type (e.g. IPoE Subscriber Line session, PPPoE session, IP session) or access technology (e.g. copper or fiber). The session can be created and removed dynamically as example, but not limited to, at power on of RG, when a BBF device starts a PPPoE session, A BBF device may have multiple sessions in series or in parallel if the BBF network supports that.
Default QoS for fixed access session:
is defined as QoS rules which apply to the entire traffic of a fixed access session. Default QoS is installed during session setup and may be modified during the lifetime of fixed access session.
Access Line Identifier is defined as:
the identifier of the Line composed by couple Logical Access ID and Physical Access ID.
Logical Access ID:
contains a Circuit ID (as defined in RFC 3046). The Logical Access ID may explicitly contain the identity of the Virtual Path and Virtual Channel carrying the traffic.
Physical Access ID:
Identifies the physical access to which the user equipment is connected. Includes a port identifier and the identity of the access node where the port resides.
3.2 Abbreviations p. 11
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
ANDSF
Access Network Discovery and Selection Function
BBF
Broadband Forum
BRAS
Broadband Remote Access Server
BNG
Broadband Network Gateway
BPCF
Broadband Policy Control Function
DSMIPv6
Dual-Stack MIPv6
EPC
Evolved Packet Core
ePDG
Evolved Packet Data Gateway
EPS
Evolved Packet System
H ANDSF
Home-ANDSF
MME
Mobility Management Entity
P-GW
PDN Gateway
PMIP/PMIPv6
Proxy Mobile IP version 6
RG
Residential Gateway
S-GW
Serving GW
V-ANDSF
Visited-ANDSF
4 Building Blocks p. 11
The architecture study is planned to be performed within three Building Blocks, with the following scope for each BB.
The following aspects will be covered in Building Block I:
- Aspects on basic connectivity, host-based mobility (S2c), and network-based mobility for untrusted accesses (S2b) on top of Release 10 baseline architecture including network discovery/selection functions and IP address allocation;
- Interworking between 3GPP and BBF architectures for authentication, including identities, on top of Release 10 baseline architecture;
- Policy and QoS interworking between 3GPP and BBF architectures considering the following scenarios:
- When H(e)NB is being used and traffic is routed back to the EPC;
- When WLAN is being used and traffic is routed back to the EPC;
- Multi-access PDN Connectivity;
- IP Flow Mobility and seamless WLAN offloading;
- Policy and QoS interworking between 3GPP and BBF architectures considering the following scenarios:
- When WLAN is being used and traffic is offloaded in the local wireline network (i.e. non-seamless WLAN offloading).
- Converged policy management and charging for the scenarios with traffic routed to EPC and offloaded at the BBF access network for operators providing both 3GPP and BBF accesses.
