11 OBA000210 H.248 Protocol ISSUE2.20 (S+N)

H.
248 Protocol
www.huawei.com
Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

Objectives
Upon completion of this course, you will be able to :
 Describe the functions of H.248 protocol
 Know about the message interaction process of H.248 protocol

Contents
1. NGN Overview
2. H.248 Basic Concepts
3. H.248 Message Structure
4. Call Flow based on h.248

What is NGN
 Next Generation Network (NGN) is a service-oriented
network.
 Through the separation of service and call control, as well

as call control and bearer, the service-independent
architecture is implemented, which makes services
independent of network.
 NGN is a kind of open and integrated network architecture.
 NGN is a kind of brand-new network integrating voice, data,

fax, and video services.

NGN System Architecture
Service Management
Network Control
Core Switch
Edge Access

NGN Solution For UA5000
Application Server
Service Management
Call Control Soft Switch
Core Switch Packet Core Network
Edge Access
UA5000 UA5000

NGN – Call Control
Soft Switch
Signal Packet Core Network
Voice
UA5000 UA5000

Media Gateway Control Protocols
Media Gateway Controller

(MGC)
H.248/
MGCP
Media Gateway
(MG)

Media Gateway Control Protocols
 H.248 and MeGaCo refer to the same kind of protocol.
 It is named H.248 by ITU-T and MeGaCo by IETF.
 MGCP is deficient in its descriptive capability, which

restricts its applications in large gateways.
 For those large-scaled gateways, H.248 is a much better

choice.
 MGCP message transportation depends on UDP packets

over IP network, and H.248 signaling messages could be
based on multiple bearers such as UDP/TCP/SCTP.

Contents
1. NGN Overview

Terms
 Media Gateway (MG):  Media Gateway Controller

 An MG converts media (MGC):
provided in one type of  It controls the call state pertaining
network to the format to connection control of media
required in another channels of MG.
type of network.

Connection Model
 MGC uses H.248 to control the connection in MGW. So to
describe the resource in MGW is very important. We use
connection model to describe these resource.

Connection Model
Media Gateway
Context
Context Termination
SCN Bearer Channel
Termination
RTP Stream
* Termination
SCN Bearer Channel
Context Null Context

Termination Termination
RTP Stream
* SCN Bearer Channel
Context
Termination Termination
RTP Stream
* SCN Bearer Channel

Terms-Termination
 Termination
 A Termination is a logical entity on an MG, capable of sending
and/or receiving one or more streams.
 One termination belongs to one and only one context at any
time.
 Type of Termination
 semi-permanent terminations: TDM channel
 ephemeral terminations: RTP flows
 Termination Function
 Terminations may have signals applied to them
 Terminations may be programmed to detect Events
 Statistics may be accumulated on a Termination
 Termination ID: defined by MGW
Terms-Context
 Context: an association between a number of Terminations.
 Context attribute:
 Context ID: The identifier of a context.
 Topology structure: Who hears/sees whom, flow direction of

media.
 One-way ,both-way and isolate
 Priority: Providing the prior handling information of a context.
 Emergency: Providing the emergent handling information of a

context.

Contents
1. NGN Overview

Protocol Stack
H.248 H.248
UDP/TCP/SCTP MTP3-B
SSCF
IP
SSCOP
Data Link AAL5

ATM
Physical
Physical layer
(a) IP-based H.248 (b) ATM-based H.248

Message Mechanism of H.248
Message Message
Transaction
Transaction 1
Context ContextID1
Command
CMD1 Des-1 Des-n
Descriptor
...CMDn
ContextIDn
TransactionIDn

Protocol Message
 The unit of information is message.
 A message can contain multiple transactions.
 A message has a header, which contains the ID of the

sender.
 Each Message has a version number, indicating the version

followed by the protocol message.
 There is no relationship among the transactions in a

message. They are treated independently.

Message Structure
H.248 message
Transaction Transaction Transaction

Header ....
Req or Reply Req or Reply Req or Reply
Trans Hdr Action .... Action
Ctx Hdr Ctx Properties Command .... Command
Cmd Hdr Descriptor .... Descriptor

Code of Protocol Message
 The code of a protocol message can be in the text format or
the binary format.
 MGC must support both formats, while MG can support

either one.
 Messages have two kinds

 Commands
 Responses

Commands
Commands Direction Description
used to add a Termination to a Context. If no
ContextID is specified, a Context will be
Add MGC→MG
generated and then a Termination is added
into it.
used to modify the properties, events and
Modify MGC→MG
signals of a Termination.
used to remove a Termination from a Context
and return statistics on the Termination's
Subtract MGC→MG participation in the Context. The Subtract
command on the last Termination in a Context
deletes the Context.
used to move a Termination from one Context
Move MGC→MG
to another.

Commands (cont.)
Commands Direction meanings
used to return the current state of
AuditValue MGC→MG properties, events, signals and statistics
of Terminations.
used to return a collection of termination
AuditCapabilities MGC→MG
capabilities.
used to allow MG to notify MGC of the
Notify MG→MGC
detected event.
used to allow the MG to notify the MGC
that a Termination or group of
Terminations is about to be taken out of or
into service. ServiceChange is also used
ServiceChange MGC↔MG
by the MG to announce its availability to
an MGC (registration), and used for
notification of MGC suspension and
active/standby switchover.

Response
 All H.248 commands are acknowledged.
 The structure of a response is basically the same as that of

a command.
 Transaction ID correlates a command with its response.
 There are two types of responses

 Reply
 Pending

Contents
1. NGN Overview

Scenario 1 Registration
MG SoftX3000
MEGACO/1 [182.20.20.2]:2944
(1)SVC_CHG_REQ Transaction = 9998 {
Context = - {
ServiceChange = ROOT {
Services {
Method=Restart
(2)SVC_CHG_REPLY
Reason= [901] } } }
}

Scenario 1 Registration(Cont.)
MG SoftX3000
MEGACO/1 [182.20.20.1]:2944
(1)SVC_CHG_REQ Reply = 9998 {
Context = - {
ServiceChange = ROOT {
Services {
(2)SVC_CHG_REPLY } } }
}

Scenario 2 Initiation of MG
MG SoftX3000
MOD_REQ
MOD_REPLY

Scenario 3 Successful call
UserA Termination1 SoftX3000 Termination2 UserB
Off-hook
1 NTFY_REQ
NTFY_REPLY
2 MOD_REQ
dial-tone MOD_REPLY
dialing 3 NTFY_REQ
NTFY_REPLY
4 ADD_REQ
ADD_REPLY 5 ADD_REQ
ADD_REPLY
6 MOD_REQ
7 MOD_REQ Ringing
MOD_REPLY
Ringback tone MOD_REPLY Off-hook
8 NTFY_REQ
NTFY_REPLY
9 MOD_REQ
MOD_REPLY

Scenario 3 Successful call (Cont.)
UserA Termination1 SoftX3000 Termination2 UserB
10 MOD_REQ
MOD_REPLY
Conversation
On-hook 11 NTFY_REQ
NTFY_REPLY
12 MOD_REQ
MOD_REPLY
13 SUB_REQ
14 MOD_REQ
SUB_REPLY
Busy-tone
MOD_REPLY
15 MOD_REQ On-hook
16 NTFY_REQ
MOD_REPLY
NTFY_REPLY
17 SUB_REQ
SUB_REPLY
18 MOD_REQ
MOD_REPLY

Summary
 MGC, MG, termination and context are important concepts
of H.248.
 There are 8 basic commands using in H.248: ADD,

MODIFY, SUBSTRACT, MOVE, AUDITVALUE,
AUDITCAPABILLITIES, NOTIFY and SERVICECHANGE.
 The function of each command in H.248 call flow must be

mastered as the key point.

Thank you
www.huawei.com

11 OBA000210 H.248 Protocol ISSUE2.20 (S+N)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

11 OBA000210 H.248 Protocol ISSUE2.20 (S+N)

Uploaded by

Copyright:

Available Formats

H.

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

 Know about the message interaction process of H.248 protocol

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

2. H.248 Basic Concepts

3. H.248 Message Structure

4. Call Flow based on h.248

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

 Through the separation of service and call control, as well

 NGN is a kind of open and integrated network architecture.

 NGN is a kind of brand-new network integrating voice, data,

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

Call Control Soft Switch

Core Switch Packet Core Network

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

Signal Packet Core Network

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

Media Gateway Controller

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

 It is named H.248 by ITU-T and MeGaCo by IETF.

 MGCP is deficient in its descriptive capability, which

 For those large-scaled gateways, H.248 is a much better

 MGCP message transportation depends on UDP packets

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

2. H.248 Basic Concepts

3. H.248 Message Structure

4. Call Flow based on h.248

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

 Media Gateway (MG):  Media Gateway Controller

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

Context Null Context

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

 Topology structure: Who hears/sees whom, flow direction of

 Priority: Providing the prior handling information of a context.

 Emergency: Providing the emergent handling information of a

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

2. H.248 Basic Concepts

3. H.248 Message Structure

4. Call Flow based on h.248

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

Data Link AAL5

(a) IP-based H.248 (b) ATM-based H.248

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

 A message can contain multiple transactions.

 A message has a header, which contains the ID of the

 Each Message has a version number, indicating the version

 There is no relationship among the transactions in a

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

Transaction Transaction Transaction

Trans Hdr Action .... Action

Ctx Hdr Ctx Properties Command .... Command

Cmd Hdr Descriptor .... Descriptor

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

 MGC must support both formats, while MG can support

 Messages have two kinds

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2006 Huawei Technologies Co., Ltd. All rights reserved.

 The structure of a response is basically the same as that of

 Transaction ID correlates a command with its response.