TSACC Test Area

1
NGN User Equipment Standardization Issues
2005.12.15 Jinkyung Hwang KT Convergence BU IP
Service Development. Team, BcN Service
Development. Division jkhwang_at_kt.co.kr
2
Contents

• NGN User Equipment Vision
• UE scope requirements in FGNGN
• KTs first touch to BcN Trial Service Subscriber
  
• BcN Video Phone
• Standardization Issues Direction
• CJK Activities ?

3
NGN User Equipment Vision
PC as SIP terminal
PDA
NGN
Mobile phone
Laptop
Cordless phone
Camcorder
Digital camera
Laptop as H323/SIP terminal
Microphone
Printer
Plain-old phone
Interactive TV
Video phone

• NGN is envisioned with any kinds of terminals
• Fixed or Wireless IP Telephony Data Terminals
• Legacy Terminals
• Home GW, Residential GW, Set-top box, IP PBX
• Communication enabled electronic devices
  Ubiquitous UE
• Through FTTH, WiMAX, WLAN, DMB, HDTV, RFID,
  Ubiquitous access

4
UE in FGNGN Scope
FGNGN-OD-00253

• NGN UE Scope in Release 1
• The NGN should support a variety of user
  equipment.
• This includes gateway legacy terminals (e.g.
  voice telephones, facsimile, PSTN textphones
  etc.), SIP phones, soft-phones (program on PC),
  IP phones with text capabilities, set-top boxes,
  multimedia terminals, PCs, user equipment with
  intrinsic capability to support a simple service
  set, and user equipment that can support a
  programmable service set.
• It is not intended to specify or mandate a
  particular NGN user equipment type or capability,
  beyond compatibility with NGN authentication,
  control and transport protocol stacks.
• NGN supports a mobile terminal that is fully
  compliant with 3GPP specifications only when
  directly connected through a 3GPP IP-CAN.
  Release 1 may not support 3GPP mobile terminals
  when they are not directly connected through a
  3GPP IP-CAN.
• Release 1 should allow the simultaneous use of
  multiple types of access transport functions by a
  single terminal, however there is no requirement
  to co-ordinate the communication. Such terminals
  may therefore appear to be two or more distinct
  terminals from the network point of view.
• The user equipment should enable interface
  adaptation to varying user requirements,
  including the needs by people with disabilities,
  for connection with commonly provided user
  interface devices.

5
UE in FGNGN Requirements
FGNGN-OD-00252

• NGN user equipment general requirements
• NGN user equipment are connected via the customer
  network to the NGN access network and provide
  services to end users. NGN user equipment general
  requirements include
• A variety of user equipment should be supported.
• These include residential gateway, black phones,
  text phones, SIP phones, soft-phones (program on
  PC), set-top box, multimedia terminals, cellular
  phones, PCs, PDAs, etc. These include user
  equipment with intrinsic capability to support a
  simple service set, and user equipment that can
  support a programmable service set
  ETSI-TISPAN-R1-DEF.
• Legacy terminals should be supported
• User equipment should be capable of making an
  emergency call.
• Easy/automatic configuration setup should be
  supported
• For example, remote downloading of setup
  information or software updates from network to
  user equipment (e.g., home gateway) allows
  network operators to undertake user equipment
  setup or software update on behalf of users.
  Then, users have only to connect their equipment
  to the network to access NGN services.

6
Market moves fast ..

• Video communications becomes common sense
• Video phone
• Multiple applications run simultaneously on the
  phone
• Game, text/multimedia messaging, presence,
  health-care, etc..
• Various shapes and types of UEs are required
• Depending on the places, users tastes, usage,

7
KTs first touch to BcN Trial Service Subscriber
BcN Video Phone

• ? Video Phone OS WinCE 4.2
• ? High Quality bidirectional video communication
  using SIP
• Max Network bandwidth 2Mbps
• Quality More than CIF 30FPS, VGA 20FPS
• ? Realtime Video communication
• Bidirectional Media Send/Recv RTP/RTCP
• Unidirectional Streaming RTSP
• ? Audio CODEC
• Realtime Communication G.711, G,723.1, G.729A,
  G.722
• Realtime Decode only Wideband Codec Advanced
  Audio Coding, AMP, MP3
• Automatic Gain Control, Automatic Error
  Correction, Automatic Noise Suppression
• ? Video CODEC
• Realtime Communication H.263, QCIF/CIF/VGA
  Supported
• Realtime Streaming MPEG4 QCIF/CIF/VGA
• ? 6.4 TFT LCD(Touch Screen), 16bit
• ? 420K pixel CCD CAMERA
• ? Network Bandwidth Quality Control
• Application Client S/W supported
• GUI Supported

8
Multiple Services based on Video Phone
B-Learning
Multimedia CID
Multimedia Contents Hosting (VoD, Satellite TV)
Service Web
Health-care (Blood sugar Sensor based)
Presence -Comm.
B-Game
Video Banking
9
Multiple application coordination issues

• UE Requirements in Multiple service environment
• Client priority, coordination control (hold,
  restart), different security level, different QoS
  requirements, etc

Web Server
Multimedia Messaging Server
game
Health Care
3rd party server

BcN App. Server
NGN OSS
SIP
SIP
3rd party domain
HSS
Presence Server
Instant Messenger
SIP
UE Management Server
Diameter
SIP
Softswitch
Media Server
TCP
SIP
TCP
MM1/SIP
MSRP
SNMP/XML
SIP
SIP

• UE Software upgrade (OS, app
• specific clients etc)
• terminal status monitoring
• terminal capability information

BcN UE (User Equipment)
Health client
game client
MMS client
IM client
presence client
call client
Management client
Web browser
10
UNI Issues

• NGN should support various terminals, accesses,
  services..
• NGN Terminal should be interoperable through NGN
  UNI
• What should we start at the first step ?

FGNGN-OD-00261TR-TERM
User Network Interface (UNI) An interface
between the user equipment and a network
termination at which interface the access
protocols apply. Note This interface is not
constrained to a single protocol.
11
CJK activities ?

• Possible Approaches
• Co-development of NGN UE interoperability
  specification protocol profile
• Interoperability tests through CJK Testbed
• c.f. MSF GMI2006

Multi Service Forum (www.msforum.org), Global MSF
Interoperability