07.02
|
-----
|
------
|
System Enhancements for Fixed Broadband Access to IMS [FBI] – Handled at Adhoc, any documents will have lower priority than other agenda items
|
----------
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
|
|
07.02
|
S2-052462
|
LS In
|
Reply LS (from TSG CT) on handling ETSI specific ISUP features and TISPAN supplementary services in TS 29.163
|
TSG CT (CP-050430, Ericsson)
|
-
|
-
|
-
|
-
|
-
|
-
|
FBI
|
TSG CT plenary thanks CT WG3 for the LS CP-050392 seeking plenary guidance whether ETSI specifications should be referenced by CT WG3 in 29.163. TSG CT plenary had a discussion on the question posed to the plenary and concluded that CT WG3 should goahead and accommodate the interworking between the IMS and Circuit Switched networks by expanding the scope of TS 29.163. To promote a unified IMS in the industry, CT WG3 is encouraged to provide the interworking capabilities requested by TISPAN by way of referencing to the required ETSI specifications for ETSI specific ISUP features including ACR and TISPAN simulation services. This was copied to SA WG2 for information.
|
Noted
|
07.02
|
S2-052536
|
[CR]
|
23.002 CR0164: Introduction of IBCF in 23.002 (Rel-7)
|
Siemens
|
23.002
|
0164
|
-
|
C
|
6.9.0
|
Rel-7
|
FBI
|
Summary of change: Remove IMS ALG in 23.002 and introduce IBCF instead.
|
Not handled and should be re-submitted by the authors to the next meeting
|
07.02
|
S2-052685
|
CR
|
23.228 CR0520R1: Use of IMS as a transit network (Rel-7)
|
Lucent
|
23.228
|
0520
|
1
|
F
|
7.1.0
|
Rel-7
|
FBI
|
Release 7 of IMS needs to be able to support more general routing for sessions using the IMS elements in transit between other networks. Scenarios using the BGCF for IMS as a transit network are added to the session flow procedures sections.
|
Noted
|
07.02
|
S2-052707
|
LS In
|
Reply to SA WG2 on Adding Mobility to "fixed network IMS"
|
ETSI TISPAN (08TD406r3)
|
-
|
-
|
-
|
-
|
-
|
-
|
-
|
TISPAN appreciates the good cooperation it has with 3GPP and SA WG2 to help defining a common IMS for both fixed and mobile networks. TISPAN confirms that the in the first release of the NGN IMS, does not address mobility to its full scope, and thatthe SA WG2 understanding that Release 1 includes terminal mobility and nomadism is correct. To further explain the mobility concept used in Release 1, a number of excerpts from different draft specification are attached below. TISPAN expects that theservices provided over the NGN IMS will be accessed via a wide range of terminals from Desktop PCs via Laptops to hand held devices like SIP phones and PDAs. Although the demands on mobility from user of e.g. Desktop PCs is expected to be limited, TISPAN assumes that NGN users with e.g. laptops and handheld devices will have wishes and demands for more advanced mobility services, such as e.g. support for handoff including service continuity between wireless and wireline technologies. To this end, TISPAN will start interacting with the FMCA (Fixed Mobile Convergence Association) to further understand the expectations and needs for mobility related functions and services. The input from FMCA will among other thing be used in defining the requirements on mobility to be included for NGN release 2, and it is expected that mobility with service continuity will be included. TISPAN appreciates and welcomes the kind offer from SA WG2 and its experts to closely work with TISPAN on the migrationtowards support for full mobility. TISPAN would also appreciate receiving information relating to ongoing work in 3GPP such as the System Architecture Evolution and the Voice Call Continuity, in which we believe aspects are being addressed which also may pertain to mobility in fixed networks, and would be of value to us when extending the mobility concepts supported for NGN release 2.
|
Postponed to meeting #50
|
07.02
|
S2-052747
|
CR
|
23.228 CR0520R2: Use of IMS as a transit network (Rel-7)
|
Nokia
|
23.228
|
0520
|
2
|
B
|
7.1.0
|
Rel-7
|
FBI
|
Scenarios for IMS as a transit network are added to the session flow procedures sections.
|
Noted
|
|
