Joint 3GPP

1
Joint 3GPP TISPANWorkshop on NGN-IMS-
NGN-IMS issues handling -

• Alain Le Roux (France Telecom), TISPAN Chairman
• alainxavier.leroux_at_francetelecom.com
• Magnus Olsson (Ericsson), 3GPP SA2 Chairman
  magnus.m.olsson_at_ericsson.com

2
Agenda

• Approval of agenda and Documents (s1)
• Workshop objectives (s1)
• 3GPP and TISPAN organisation (s1)
• NGN Architecture Release 1 definition (s2)
• IMS architecture and capabilities (s2)
• Issues related to reuse of IMS for NGN (s3-s4)
• Support of PSTN/ISDN service emulation (s5)
• Ongoing activities and Workplan (s5)
• Future cooperation/interactions (s6)
• Wrap-up and closure (s6)

3
List of Issues and Resolution (1)

• (6.1) UICC in NGN
• Current 3GPP Specefications assumes that a
  physical UICC is present in the 3GPP UE
• TISPAN is invated to evaluate if it is acceptable
  to require that a physical UICC is also required
  for an NGN UE
• If it is not acceptable TISPAN needs to come back
  to 3GPP whith clear requirements/proposals
• (6.1) Local Access Network with NATand/or
  Firewall
• Not addressed in 3GPP
• IETF is working on solutions
• TISPAN WG2 and 3GPP SA2 should address this issue

4
List of Issues and Resolution (2)

• (6.2) IMS enablers
• General agreement that TISPAN shall reuse the IMS
  enablers like Presence, Messaging, Group
  Management and Conferencing.
• It was agreed that NGN should attempt to make
  URIs used in SIP (except tel) personal to the
  user rather than the device
• It was proposed that NGN should make use of
  capability to indicate presence capabilities is
  mobile/fixed as appropriate (TISAPN WG2 and WG3
  to discuss, 3GPP CN1 to assist if necessary)
• Does NGN need a specified interface between the
  MRFC and MRFP (TISPAN WG2, 3GPP CN3, R6 existing
  WID)
• If NGN intend to place NATs or firewalls in the
  media path, then they will need to specify
  message relays (TISPAN WG12, 3GPP SA2)

5
List of Issues and Resolution (3)

• (6.3) Security requirements and solutions
• Work ongoing in TISPAN WG7
• No specific issues raised in the input
  contribution
• 3GPP SA3 is the main contact point on security
  issues in 3GPP

6
List of Issues and Resolution (4)

• (6.4) Collection of data for the purpose of
  Charging
• No modifications of the information in the 3GPP
  CDRs was seen as necessary
• TISPAN will investigate if and how data related
  to the access (line) needs to be captured
• 3GPP SA5, TISPAN WG1
• Codec
• 3GPP assumes AMR as the default Codec. TISPAN to
  consider the implications, and communicate with
  3GPP
• Need to define default Video-Codec support

7
List of Issues and Resolutions (5)

• 6.5 Bearer QoS classes
• QoS Class support definition and mapping (with
  IMS ones and Y.1541) is required for fixed NGN
  (TISPAN WG5)
• TISPAN WG5 to make a proposal and then
  communicate with 3GPP SA2
• 6.6 Gq Interface
• TISPAN_NGN to proceed with Gq proposed extensions
• TISPAN WG2 (Requirements) and WG3 (Prorocols) to
  communicate with 3GPP CN3

8
List of Issues and Resolutions (6)

• 6.7 Services issues
• Non-issue for 3GPP
• But TISPAN WG1 will further look at service
  capabilities inherently provided by SIP
• TISPAN WG1 to communicate with 3GPP SA2 (and CN1)
• 6.10 SIP Profile
• All requirements to be reviewed by TISPAN_NGN
• Main issues SIP authentication, need to support
  IPv4, pre-conditions, Overlap sending?
• All others to be confirmed by TISPAN WG23
• TISPAN WG23 to communicate the requirements to
  SA2 and CN1

9
IMS Applications Issues (7)

• Based on TD015r1
• Presence
• TISPAN_NGN to attempt making URIs used in SIP
  (except tel) personal to the user rather than
  the device.
• TISPAN WG4 to communicate deliberations to 3GPP
  CN1
• NGN to identify its own work for delivering
  information from presence-unrelated entities to
  the PNA
• TISPAN WG12 (then WG3) to communicate
  deliberations to 3GPP CN1
• NGN to decide if the current range of elements
  within the PIDF definition is sufficient for NGN
  usage.
• any additional specification will need to be done
  via CN1 by IETF (and then used by other groups)
• Conferencing
• NGN need to open any of the interfaces that are
  currently not specified ?
• TISPAN WG4 to communicate deliberations to 3GPP
  CN1

10
IMS Applications Issues (8)

• Based on TD015r1
• Messaging
• The relationship between FMMS and IMS messaging
  is important to be clarified in NGN
• If NGN places NATs or firewalls in the media
  path, then there will need to specify message
  relays (R6 does not use message relays)
• TISPAN WG12 to communicate deliberations to SA2
  (CN1)
• Other Applications
• Scope exists for 3rd party definition of
  capabilities, as well as providing services
  directly to end users (Identity redirection
  services like number portability, Prepay charging
  services)
• TISPAN WG1 to consider own Applications
  opportunities
• OSA/Parlay can provide applications
• Effective coordination arrangements already in
  place

11
3GPP/WLAN interworking reusefor NGN access
independence (9)

• Based on TD09
• Proposal to adopt the concepts of WLAN/3GPP
  interworking as the basis to achieve true access
  independence in NGN, considering that
• Access independence is one of the NGN central
  requirements
• True access independence requires a generic
  approach, which decouples NGN core network
  components and procedures as much as possible
  from the subtleties of access technologies
• 3GPP is on the way to standardize with Release 6
  WLAN/3GPP interworking that allows 3GPP terminals
  to access a 3GPP IMS via WLAN
• The concepts of WLAN/3GPP interworking do not
  rely on the specifics of the WLAN access network
• TISPAN WG2 7 to examine the proposal, in light
  of
• its relationship with the ANAS (Access Network
  Attachment) and RACS (Resource Admission
  Control) functions
• the WLAN access architecture to NGN
• Contributions welcome to help quick decision
  making.

12
NGN-IMS Issues resolution

• TISPAN to review and consolidate requirements,
  e.g.
• Clarify requirements for non-UICC support
• Support of IPv4
• SIP Profile requirements for xDSL access to IMS
• Gq extensions for NGN
• QoS Class and Default codecs support
• TISPAN to consider collocating relevant WG
  meetings with 3GPP SA2 and CN1 when appropriate
• With SA2 to address
• QoS Class mapping
• WLAN access architecture
• With SA1/2/3 to address
• UICC/USIM/ISIM support issues
• With CN1 to address
• SIP Profile requirements
• IMS Applications issues
• With CN3 to discuss Gq extensions

13
Next steps

• TISPAN actions
• To prepare a Document defining reuse of IMS (R6)
  in NGN Release 1 (all aspects and relevant TSs)
• To communicate with relevant 3GPP TSGs
• To collocate relevant WG and 3GPP TSGs when and
  where appropriate
• 3GPP actions
• Consider WIDs to support Fixed NGN requirements
  (refer to TD17r1)
• Joint actions
• A further Workhop February/March 2005
• To discuss IMS and NGN related issues
• A TISPAN 3GPP common (publicly open) NGN-IMS
  mailing list (for info/organisational purpose)