Transcript Sidevorgud esimene loengupäev - Raadio

Kommunikatsiooniteenuste
arendus
IRT0080
Loeng 7/2010
Avo Ots
telekommunikatsiooni õppetool,
TTÜ raadio- ja sidetehnika inst.
[email protected]
1
Slaidimaterjalid allikatest:
The 3G IP Multimedia Subsystem (IMS), Third Edition
Gonzalo Camarillo and Miguel A . García-Martín
© 2008 John Wiley and Sons , Ltd.
Aila H. Koponen magistritöö
(kaitstud kevadel 2008)
https://oa.doria.fi/bitstream/handle/10024/38897/afloorco.pdf?se
quence=1
2
Mobiilvõrk, 3GPP Rel_8
frozen Dec 2008
VoIP
Esmavaade konverentsile
Clients
Agency
Public
Internet
Encrypted
Video and
Audio
5
Konverents
•
•
•
•
•
•
3 või enam osapoolt
Osapoolte arv võib muutuda
Meediavood lisanduvad/eemalduvad
Konverentsi põhireeglistik (poliitika)
Heakskiit konverentsil osalemise tarvis
…
•
…Speaker recognition in a conference
6
Võrguvõimalused
Prioriteedid
Q-o-S
Serveripõhine
10
Full Mesh
11
Realisatsioonide areng
Proxy
IP Phones Server
Voice
Gateways
sip-01
1996 1997
RFC 2543
1998
1999
2000
Softswitch
and Gateways
Conferencing
IVR
RFC 3261
3GPP
2001
2002
2003
Apps
Conf IM
2004
NAT/FW
2005 2006 …
12
“Rich Media Communications”
Only options that make sense appear
• Send an instant message
• Start a voice conversation
• Start a video conversation
• Send email
• Start a rich media session
• Show profile/directory entry
• Right now
• Make a phone call
• As soon as possible
• First available slot
See availability
and select people
in any context
Select method of
communication
Decide when to
communicate
System does the rest
13
Videokonverentsi standardid (1)
http://www.education.purdue.edu/edit/misc/videocon
ferencing/
http://www.ietf.org/rfc/rfc4597.tx
t?number=4597
Informational: This document describes
multimedia conferencing scenarios. The
development of these scenarios is intended
to help with the definition and evaluation of
the requirements for the centralized
conferencing (XCON) working group.
14
Videokonverentsi standardid (2)
http://www.ietf.org/rfc/rfc4353.txt?numbe
r=4353
Informational:
Loosely coupled conferences are easily supported in
SIP by using multicast addresses within its session
descriptions.
In another model, referred to as fully distributed
multiparty conferencing, each participant maintains
a signaling relationship with the other participants,
using SIP. This document presents the overall framework
for tightly coupled SIP conferencing, referred to simply as
"conferencing" from this point forward.
15
Konverentsi ülesehitus
Conference Functions
Conference
Policy
Conference
Policy
Server
Non-SIP
Focus
Conference
Notification
Service
SIP Dialog
SIP Subscription
Conference Participant
16
Konverentsisüsteem (XCON)
17
Konverentsi koosseis
18
Kliendivaade meediaressurssidele
19
Multisaade
Multicast Network
Media
20
Hajutatud korraldus
Signaling
Media
21
Tsentraalne korraldus
Conference
Server
Signaling
Media
22
Jaotatud funktsioonid
Multicast Network
Signaling
Media
23
Server-terminalis mudel
Signaling
Media
-
24
“Keskpõranda” /floor/ haldus
25
Indicating User Agent Capabilities
in SIP (S):
[RFC3840] defines a mechanism for
carrying capability information about a
user agent in REGISTER requests and
in dialog-forming requests like INVITE.
It has found use with conferencing (the
is focus parameter declares that a user
agent is a conference server) and with
applications like push-to-talk.
26
Basic Network Media Services with
SIP (I)
[RFC4240] defines a way for SIP
application servers to invoke
announcement and conferencing
services from a media server. This is
accomplished through a set of defined
URI parameters which tell the media
server what to do, such as what file to
play and what language to render it in.
27
Referring to Multiple Resources in SIP
(S):
[RFC5368] allows a UA sending a REFER
to ask the recipient of the REFER to
generate multiple SIP requests, not just
one. This is useful for conferencing,
where a client would like to ask a
conference server to eject multiple
users.
28
A Framework for Consent-Based
Communications in the Session Initiation Protocol
(SIP) (S):
[RFC5360] defines several extensions to SIP,
including the Trigger-Consent and
Permission- Missing header fields. These
header fields, in addition to the other
procedures defined in the document, define a
way to manage membership on "SIP mailing
lists" used for instant messaging or
conferencing. In particular, it helps avoid the
problem of using such amplification services
for the purposes of an attack on the network,
by making sure a user authorizes the addition
of their address onto such a service.
29
PoC protokollitoetus
30
Lingid (1)
http://www.softarmor.com/sipping/meets/ie
tf60/slides/pres-ietf60-sipping-camarilloconsent.ppt
https://www.sipit.net/SIPit23_Summary
http://en.wikipedia.org/wiki/Voice_recognit
ion
31
Lingid (2)
http://www.ietf.org/rfc/rfc4597.txt?number
=4597
http://www.education.purdue.edu/edit/misc/
videoconferencing/
32