1 Kommunikatsiooniteenuste arendus IRT0080 Loeng 7/2010 Avo Ots telekommunikatsiooni õppetool, TTÜ...

1

Kommunikatsiooniteenuste arendusIRT0080

Loeng 7/2010

Avo Otstelekommunikatsiooni õppetool,

TTÜ raadio- ja sidetehnika inst.avots@lr.ttu.ee

2

Slaidimaterjalid allikatest:The 3G IP Multimedia Subsystem (IMS), Third EditionGonzalo 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?sequence=1

Mobiilvõrk, 3GPP Rel_8frozen Dec 2008

VoIP

5

Esmavaade konverentsile

PublicInternet

Agency

Clients

EncryptedVideo and

Audio

6

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

Võrguvõimalused

Prioriteedid

Q-o-S

10

Serveripõhine

11

Full Mesh

12

Realisatsioonide areng

Voice Gateways

Softswitch and GatewaysProxy

ServerIP Phones

RFC 25433GPP

AppsRFC 3261

IVR

NAT/FW Conf IM

Conferencing

1998 2000 20022001 2003 2004 20051996 2006 …1997 1999sip-01

13

“Rich Media Communications”

• Send an instant message• Start a voice conversation• Start a video conversation• Send email• Start a rich media session• Show profile/directory entry• Make a phone call

See availabilityand select peoplein any context

Select method of communication

Decide when to communicate

System does the rest

Only options that make sense appear

• Right now• As soon as possible• First available slot

14

Videokonverentsi standardid (1)http://www.education.purdue.edu/edit/misc/

videoconferencing/

http://www.ietf.org/rfc/rfc4597.txt?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.

15

Videokonverentsi standardid (2)http://www.ietf.org/rfc/rfc4353.txt?

number=4353Informational: 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.

16

ConferencePolicy

ConferenceNotification

ServiceFocus

ConferencePolicyServer

Conference Participant

Conference Functions

SIP Dialog SIP SubscriptionNon-SIP

Konverentsi ülesehitus

17

Konverentsisüsteem (XCON)

18

Konverentsi koosseis

19

Kliendivaade meediaressurssidele

20

Media

Multicast Network

Multisaade

21

SignalingMedia

Hajutatud korraldus

22

SignalingMedia

Conference Server

Tsentraalne korraldus

23

SignalingMedia

Multicast Network

Jaotatud funktsioonid

24

SignalingMedia

-

Server-terminalis mudel

25

“Keskpõranda” /floor/ haldus

26

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.

27

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.

28

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.

29

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.

30

PoC protokollitoetus

31

Lingid (1)

http://www.softarmor.com/sipping/meets/ietf60/slides/pres-ietf60-sipping-camarillo-consent.ppt

https://www.sipit.net/SIPit23_Summary

http://en.wikipedia.org/wiki/Voice_recognition

32

Lingid (2)

http://www.ietf.org/rfc/rfc4597.txt?number=4597

http://www.education.purdue.edu/edit/misc/videoconferencing/