search

reTHINK-project / use-cases

Definition
Artistic License 2.0
2 stars 0 forks source link

Dynamic Media Server or Media Gateway provisioning #13

Open pchainho opened 9 years ago

pchainho commented 9 years ago

Actors

Alice and Bob are Identified Consumer that are Conversation Participants

Alice and Bob are subscribers of different and incompatible Communication Service Providers e.g. WebRTC based and PSTN telephony.

Inter is a Communication Service Provider) providing different Telephony Gateway services.

Pre-conditions:

Similar to #1 but in this case each participant uses different NSPs that implies the usage of a Media Gateway service,

  1. Alice pushes the button to invite Bob for an audio/video conversation.
  2. Different Interoperability Services with a summary of price and quality are recommended to Alice
  3. Alice selects Inter service, the call is notified to Bob and accepted by him.

Remaining procedures are similar to #1

Media Server Variant

The same approach can be followed for other network side Communication services e.g. MCU services to support large Multiparty Conversations.

Differentiation – market relevance

Currently, not possible.

![Uploading Dynamic NE Provisioning.png . . .]()

sbecot commented 9 years ago

I'm not sure this has to be produced in phase 1.

Yudani commented 9 years ago

The concept "Media Gateway" is not defined. Where is this element? a third-party service provider?

rebecca-copeland commented 9 years ago

Hi there, Since there is great confusion about media/signalling-on-the-fly (neither of which is new!!!) and Media gateway/media server functionality - here is my explanation. For anyone who is really  interested, I refer you to my book "Converging NGN Wireline and Mobile Networks with IMS" https://www.crcpress.com/product/isbn/9780849392504 - it describes these different gateways in detail, backed up by the Standards (3GPP, IETF, TISPAN, OMA)  documents. Media Gateway is a well known term (http://en.wikipedia.org/wiki/Media_gateway) used widely in Telecom for many years, with numerous products available. Servers can be either signalling only or media bearing. Media bearing gateways often carry some signalling, i.e. 'inline' signalling to manage the data flows, or signalling that is required for feature translation (like 2G services translated to packet-based services).Media gateways have several functions, but some media gateways are specialized by specific functions that is required in a particular position in the network topology:- Carry media flows (which pure session control signalling servers do not) - Split media into media streams that have the same characteristics of QoS (bandwidth, delay, jitter...) to allow media flow management - Perform media conversion on the fly between different media protocols- Perform border control and security checks between different networks- DTMF detection (buttons pressed)- Direct the routing of the media - Inspect media packets at various levels to detect security risks and confirm routing... and more. Media gateways have various names in the Standards according to their specific set of functions. Examples from 3GPP are:  MGCF (integration of TDM signalling and services), TrGW (transition/translation gateway) , IBCF (inter-network border control), TGW (trunking gateway) and more. In the Internet space, SBC (session border control) is a signalling and media gateway that performs many media functions, including media translation on the fly (see http://en.wikipedia.org/wiki/Session_border_controller).   Please distinguish Media Gateway from Media Server (http://en.wikipedia.org/wiki/Media_server). Media Server - or the MRF (Media Resource Function) delivers media processing functions (i.e.not media flow management) that applications need, and is often part of the applications server itself, but standalone media servers are also marketed (e.g. Rdysis and AudioCode). The media server can be hardware based or software based, or both. Media servers can be defined in two parts: MRFC (Media Resource Function Controller), which is the signalling part and can sit in the core network, and the MRFP (Media Resource Function Platform), which is the media processing part, and this can be distributed to the edge.  The Media Server is used by applications for:- providing voice announcements- share content across several applications- bridging Voice and Video for conferencing- convert media compression protocols... and more. Hence, media gateways are deemed as a part of the network transport that are used by media flows 'automatically', while media servers are regarded as resources that applications call upon for the performance of particular services. Given the wide usage of the term 'media gateway' in Telecom and its generality, does this term need further clarification - as long as it is used correctly?The term 'media server' is less well understood, but I suggest we keep the distinction. My Best  Rebecca Copeland

  From: Yudani Riobó <notifications@github.com>

To: reTHINK-project/use-cases use-cases@noreply.github.com Sent: Thursday, 30 April 2015, 12:01 Subject: Re: [use-cases] Dynamic Media Server or Media Gateway provisioning (#13)

The concept "Media Gateway" is not defined. Where is this element? a third-party service provider?— Reply to this email directly or view it on GitHub.