Vous êtes sur la page 1sur 7

Nb Interface and IPBCP Protocol

Course Objectives:
Understand the Nb Interface and IPBCP Protocol

Contents
IPBCP...............................................................................................................................................................1 1.1 Overview..................................................................................................................................................1 1.2 Tunnelling Transmission of IPBCP.........................................................................................................1 1.3 Message Types of IPBCP.........................................................................................................................2 1.4 Message Content of IPBCP.....................................................................................................................3

IPBCP
1.1 Overview
The IP bearer control protocol (IPBCP) is the control plane protocol of the Nb interface. The IP bearer control commands of the BICC are parsed by the H.248 and then sent to the IPBCP for execution. The IPBCP is used to exchange the information about the IP bearer between the source end and the destination end (including media stream features, port number, IP address, and so on) for setting up, releasing, or modifying IP media stream connections.

1.2 Tunnelling Transmission of IPBCP


The IPBCP adopts the "BICC IP Bearer Control Protocol" defined in ITU-T Q.1970. It is transferred between two MGWs through the Mc and Nc interfaces and the "BICC IP Bearer Control Tunnelling Protocol" defined in defined in ITU-T Q.1990. The major function of the BCTP is to provide a tunnel for exchanging the IPBCP between two related MGWs through the Mc and Nc interfaces. The BCTP provides sequenced and reliable point-to-point transfer of IPBCP. Transfer over the BCTP tunnel: Use the BICC APM on the Nc interface; use the CBC H.248 extended packets on the Mc interface. See Fig. 1.2 -1.

MSC-Server

Nc

MSC-Server

IPBCP: Q.1970

Tunnel: Q.1990

BICC: Q.765.5 Mc Mc TS 29.232 MGW Nb MGW

Fig. 1.2-1 Transmission Path of IPBCP

1.3 Message Types of IPBCP


There are four types of IPBCP messages. Request It is sent by the MGW-O to request the setup of the IP bearer between the MGW-O and the MGW-T. The message carries the local IP address, local port number, and the PayLoad Type value corresponding to the media stream codec. Accepted It is returned by the MGW-T to indicate that the IP bearer setup request is accepted. Confused It is returned by the MGW-T to indicate the MGW-T has questions about some parameters in the Request message. The use of this message is not yet defined in the 3GPP. Rejected It is returned by the MGW-T to indicate that the IP bearer setup request is

Chapter 0 IPBCP

rejected. Fig. 1.3 -2 shows the setup process of the RTP bearer.

Fig. 1.3-2 Setup of IP Bearer

1.

The MGW-O sends the Request message to the MGW-T. The message carries the mandatory parameters "media announcement" and "connection data" and the optional parameter "media attribute". After sending the message, the MGW-O starts the T1 timer.

2.

Upon receiving the Request message, the MGW-T checks the parameters in the message. If the request is accepted, the MGW-T returns the Accepted message. The message also carries the mandatory parameters "media announcement" and "connection data" and the optional parameter "media attribute".

3.

The MGW-O stops the T1 timer and checks the parameters in the Accepted message.

RTB bearer modification: The 3GPP does not support the modification to the established RTP bearer. RTP bearer releasing: The IPBCP has no message interaction for the releasing of an RTP bearer. The releasing of the RTP bear is triggered by the H.248 command of the Mc interface.

1.4 Message Content of IPBCP


The IPBCP uses the SDP codes. It uses the following SDP fields: Protocol Version(v)
3

TN_SP017_E1_0 Nb Interface and IPBCP Protocol

SDP version. Example: v=0 Origin(o) Description of the SDP initiator: o=<username> <session id> <version> <network type> <address type> <address> Example: o=- 0 1 IN IP4 10.1.52.1 Session Name(s) Session name described by the character string. Example: s=0 Connection data(c) Description of the connection data: c=<network type> <address type> <connection address> Example: c=IN IP4 10.1.52.1 Time(t) Description of the start time and end time: t=<start time> <stop time> Example: t=0 0 Session attribute(a) Description of the session attributes: a=ipbcp: < version> <type> Example:
4

Chapter 0 IPBCP

a=ipbcp:1 request Media Announcement (m) Description of the media: m=<media> <port> <transport> <fmt list> Example: m=audio 40128 RTP/AVP 96 Media Attribute (a) Description of the media attributes: a=rtpmap:<payload> <encoding name>/<clock rate> Example: a=rtpmap:96 VND.3GPP.IUFP/16000