You are on page 1of 12

Technical Manual – Signaling & Protocols HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Table of Contents

Table of Contents
Chapter 9 NbUP and IPBCP......................................................................................................... 1 9.1 Overview........................................................................................................................... 1 9.1.1 Brief Introduction to the Nb Interface......................................................................1 9.1.2 Definition and Function of the Nb ...........................................................................1 9.1.3 Protocol Structure................................................................................................... 2 9.2 Introduction to the Nb UP.................................................................................................. 4 9.2.1 Functions................................................................................................................ 5 9.2.2 Operational Modes................................................................................................. 5 9.2.3 Elementary Procedures.......................................................................................... 6 9.3 Introduction to the IPBCP.................................................................................................. 6 9.3.1 Functions................................................................................................................ 7 9.3.2 Primitive and Message Structure ...........................................................................7 9.3.3 Elementary Procedures.......................................................................................... 8

Huawei Technologies Proprietary i

 The adaptation protocol used in the Nb interface user plane is to transfer data between MGWs. The Nb interface has the following functions:   Providing the service traffic bearer function for the CN Accomplishing being independent from the lower-layer transmission mode based on Nb UP.1.1 Brief Introduction to the Nb Interface As the interface between MGW devices in the CS domain of the UMTS network. and accomplishing bearers of IP/ATM mode. the control plane selects IPBCP for bearer control. The Nb UP frame is the same as the lu UP frame. The Nb interface provides the transmission and bearer function for voice service traffic. and the user plane uses UDP/IP to fulfill the function of speech service traffic bearer.1. In the architecture where call control is independent from bearer.Technical Manual – Signaling & Protocols HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 NbUP and IPBCP 1 Chapter 9 NbUP and IPBCP 9. The Nb interface position and the data adaptation protocols are shown in Figure 1. the Nb interface provides service connection channels between different MGWs. Nb UP is originated by an MGW and acknowledged by the neighbor MGW. The user plane transfers service traffic based on Nb UP.1 Overview 9. whereas the control plane accomplishes bearer feature negotiation based on Nb CP. In the case of IP bearer. the Nb interface is used to connect the service bearer devices in the CN. that is. Huawei Technologies Proprietary 1 . 9. Different bearer modes require different protocols. and the negotiation interaction messages are transmitted through the tunnel provided by the Mc interface and Nc interface.2 Definition and Function of the Nb As a newly defined interface. the Nb interface is divided into two parts as user plane and control plane based on the difference between service traffic and control traffic. and IPBCP is used for the control of voice service traffic transmission in the CN. Providing transparent transmission channels for TDM bearer signaling. IPBCP accomplishes negotiation about the Nb interface bearer features of different MGWs.1. such as between the end office MGW and the gateway office MGW. one PDU type is effective for the both.

Huawei Technologies Proprietary 2 . The only difference between the two protocols is that they are applied to different interfaces. IP Bearer Mode In the WCDMA R4 network. and they both support the two operational modes: pre-defined support mode and transparent transmission mode.3 Protocol Structure The lower layer over the Nb interface has two transmission modes. The most distinctive point of Nb UP is to shield differences of lower layers. so as to bear the service traffic based on different modes. And the IP layer supports IPv4 and IPv6. Different transmission modes call for different user-plane protocols and control-plane adaptation protocols.1. I. The structure of the user-plane protocol stack is shown in Figure 1. which are based on IP and ATM respectively. And over the Nb interface.1 The Nb interface position and the adaptation protocols structure The definition and operation of Nb UP are the same as that of IuUP. Next will introduce the protocol stack structures related to specific transmission modes.Technical Manual – Signaling & Protocols HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 NbUP and IPBCP 1 Iu UP Radio Protocols Iu UP Nb UP Nb UP Transport Layer SRNC Iu MGW Nb MGW Figure 1. the protocols of the user plane are different from the adaptation protocols used by the control plane.1. 9. 3GPP defines the protocol stack structure over the Nb interface when IP transmission mode is selected. Based on IP transmission mode. the complete IP network is recommended for the CN devices. the user plane adopts such a protocol structure as RTP/UDP/IP.

DATA Nb UP AAL2 SAR SSCS(I. The ATM AAL2 link requires virtual circuit transmission.363.1 The structure of the user-plane protocol stack based on ATM bearer As the above figure shown. And RTP shall use the port with an even port number. ATM Bearer Mode The structure of the user-plane protocol stack based on ATM transmission is illustrated in Figure 1. In the structure figure above. please see related introduction to IPBCP.1 The protocol stack structure of the IP bearer user plane One MGW device can have several IP addresses. The types of virtual circuits Huawei Technologies Proprietary 3 . RTP is optional. and “IP address + UDP port number” is used to identify a bearer resource. The bearer feature negotiation is accomplished through the tunnel provided by the Mc interface and the Nc interface. II.366.1. and RTCP shall use the port identified by that even number+1. In the case of IP transmission.2) ATM Figure 1. the protocol stack structure here is the same as that of the lu interface user plane based on ATM bearer. UDP shall assign two successive port numbers to RTP and RTCP.Technical Manual – Signaling & Protocols HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 NbUP and IPBCP 1 DATA Nb UP RTP/RTCP (RFC1889/RFC1990) UDP (RFC768) IPv4(RFC791) or IPv6 (RFC2460) Figure 1.1) AAL2(I. the control plane uses IPBCP (IP Bear Control Protocol). For details.

2630. the UMG8900 device only supports PVC.Technical Manual – Signaling & Protocols HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 NbUP and IPBCP 1 can be PVC and SPVC and SVC.2 Introduction to the Nb UP When the MGW device is applied to the CN. and it also supports transmission error check.1) MTP-3b SAAL AAL5 ATM Figure 1. the interface defined for the bearer devices between end offices. For details. The virtual circuit is released by the initiator.2150.2) STC(Q. 9. please refer to related protocol introduction in the appendix and the lu interface protocol structure introduction in this manual. The Nb interface in ATM transmission mode must support PVC.  Note: At present. reliable and sequenced packets transfer and flow control. the protocol stack structure of the Nb interface control plane is the same as that of the lu interface control plane at the transport layer.2630.AAL2(Q.2. sensitive to delay and with variable packet length.1/ Q. The protocol stack structure of the control plane in ATM transmission mode is illustrated in Figure 1. whereas SPVC and SVC are optional. Q. AAL-2 SAR SSCS is able to provide elementary data packets for segmentation and assembly. other than SPVC and SVC. between an end office and a gateway office is Nb Huawei Technologies Proprietary 4 .2 The protocol stack structure of the control plane in ATM transmission mode The figure shows that in ATM transmission mode. The AAL2 sub-layer can transmit such applications as being low-speed.

and any in-band negotiation process related to bearer set up is not allowed. located between the core network layer (CNL) and the transport network layer (TNL). user data are transmitted based on Nb UP. Nb UP also has two operational modes: support mode for predefined SDU size (SMpSDU) and transparent mode (TrM). Nb UP transmits the frames of the upper layer and the lower layer transparently.2 Operational Modes Like the lu UP protocol. Transparent Mode (TrM) InTrM. If the Nb interface selects IP bearer mode. and control data are transmitted based on Nb CP. Nb UP is independent from the transmission mechanism of the lower layer. which corresponds to a different transmission control protocol from the other. The function of this mode is confined to user data transmission.2. Either IP or ATM can be selected as the transmission protocol at Nb interfaces. for its functions. rather than exchange any information with the opposite-end Nb UP. II.2. please see Huawei Technologies Proprietary 5 . I.1 Functions Nb UP is mainly used for user plane adaptation at Nb interfaces of CS domain of WCDMA CN and service data transmission between MGWs of CN. Nb UP has the following functions:       Transfer of user data Initialization Rate control Time alignment Handling of error events Frame quality classification As Nb UP has the same functions as the lu UP protocol. PDUs frames used for transmitting AMR speech adopt this mode. Nb UP provides lower layer-independent features. if the Nb interface selects ATM bearer mode. When the call-independent bearer architecture is adopted. provides data transmission services for CNL. Support Mode for Predefined SDU Size (SMpSDU) This mode is applied to the condition that the Nb UP layer needs to process data frames through this layer.Technical Manual – Signaling & Protocols HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 NbUP and IPBCP 1 interface. 9. Within the UMG8900 device. Nb UP is the same as the lu UP protocol in terms of location in the network and functions expect the application environments. 9. In support mode. the MASU will be responsible for Nb UP processing and protocol supporting function. Nb UP. the MRPU and MTCA/MTCB will be responsible for Nb UP processing and protocol stack supporting function.

1970 Tunnel: Q.3 Elementary Procedures The basic procedures of Nb UP are transfer of user data procedure. the two interworking entities are located on different MGWs in CN. The procedures are almost the same as those of the lu UP protocol.Technical Manual – Signaling & Protocols HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 NbUP and IPBCP 1 the previous part of the lu UP protocol introduction. the processing of IPBCP protocol stack is performed by configuring MRPU. other than between RNC and MGW. This negotiation is accomplished after a round of successful interaction between request messages and reply messages. IPBCP meets related requirements defined by the ITU-T Q. The logic structure is shown in Figure 1. rate control procedure. The only difference is that for Nb UP. handling of error events procedure and frame quality classification procedure.1: MSC-Server Nc MSC-Server IPBCP: Q.5 TS 29. IPBCP bearer and negotiation processes are completed through Mc interfaces and Nc interfaces.248 protocol stack provided by MPPB.232 Huawei Technologies Proprietary 6 . 9.1 IPBCP bearer logic structure Mc MGW BICC: Q.1970 recommendation.3 Introduction to the IPBCP IPBCP (IP Bear Control Protocol) is engaged in bearer attributes negotiation before the RTP bearer is set up for bearing Nb UP data at Nb interfaces. Within UMG8900. 9. So the basic procedures of Nb UP are not described here and for more information please refer to related part about lu UP protocol procedures. initialization procedure.765.1990 Mc MGW Nb Figure 1.2. IPBCP implements bearer control transmission and tunnel functions at Mc interfaces by means of the extended functions of H. time alignment procedure.

IP address. IPBCP assumes a reliable. Rejected Message: the messages returned when the BIWF of the remote MGW correctly receives the request messages but refuses to process them due to some reason. DTMF and additional attributes of other speech and signals. Time (t) Media description domain Media Announcement 1 (m) Media attributes (a): supporting RTP dynamic payload type. 2)   Huawei Technologies Proprietary 7 .    The SDP domains (Session Description Protocol) included in an IPBCP primitive message are described as below. Confused Message: the messages returned when the BIWF of the remote MGW can not identify the request messages received. port number.Technical Manual – Signaling & Protocols HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 NbUP and IPBCP 1 Nb interface control-plane protocols are defined by the TS 29.232 of 3GPP standard. sequenced.3. Accepted Message: the messages returned when the BIWF of the remote MGW receives and processes the request messages correctly. In IP bearer mode. concerning media stream characteristics. 9.1 Functions IPBCP is mainly engaged in information exchange and negotiation during BICC call establishment. which meet the requirements on Mc interfaces and Nb interfaces defined by the 3GPP standard respectively. 1)       Session and time description domain Protocol version (v) Origin (o): source MGW Session name (s) Connection data (c) Session attribute (a): used to identify IPBCP version and message type. point-to-point signalling transport service between two nodes.3.2 Primitive and Message Structure IPBCP contains the following four types of primitive messages:  Request Message: the messages sent from Bear inter-working Function (BIWF) of MGW to the remote end to request initialized IP bearer set up or modification. the connection between two MGWs for service bearer property negotiation is set up through the path provided by Mc interfaces and the tunnel provided by Nb interfaces. and so on. IPBCP uses the codec type defined by SDP to encode this information. 9.

3. but they are not useful for IPBCP application. The above domains must be present and be used as RFC 2327 defines. When receiving an IP bearer set up request from the control entity. and analyze the accept message. the interface address for transmitting media streams with R-BIWF of the connect data domain and some optional information in the media attribute domain. 9. Other SDP domains may also exist in an IPBCP message. compatibility process and exceptional events process. the initialing bearer Inter-working function (I-BIWF) will send a request to the receiving BIWF (RBIWF) and meanwhile start a timer (T1) The request message sent to R-BIWF should contains media announcement. IP bearer release.3 Elementary Procedures IPBCP basic procedures involve IP bearer set up. IP Bearer Setup 1) Successful process The interworking in IP bearer set-up process is shown in Figure 1. I-BIWF will stop T1. If the following conditions are satisfied. I-BIWF T1 Request Accepted Check the info Received R-BIWF Figure 1.1.1 Successful IP bearer set up The process is described as follows. I. So they are discarded as not being accepted. but independent of application environment. the IP bearer is Huawei Technologies Proprietary 8 .Technical Manual – Signaling & Protocols HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 NbUP and IPBCP 1  Note: The partial and sub domains listed above are added as SDP requires. IP bearer changing. When receiving accept message returned by R-BIWF.

If the time capability. 1) Successful process The successful IP bearer changing process is shown in Figure 1. I-BIWF will stop T1. the media attribute domain is identical with that in the request message. it can be changed by the control entities of I-BIWF and RBIWF.1. R-BIWF should return the REJECTED message.  Except the port sub domain. tone capability and signal capability are included in the accept message.Technical Manual – Signaling & Protocols HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 NbUP and IPBCP 1 successfully set up. they can be accepted by I-BIWF. ACCEPTED message has errors. release the resources assigned for IP bearer and notify to set up bearer control entities. However. I-BIWF T2 Request Accepted Check the info Received R-BIWF Figure 1. the following abnormal cases may appear. Except time capability. II. The process will be Huawei Technologies Proprietary 9 .   REJECTED message is received. only fmt list in the media announcement parameter and the media attributes used by IP bearer can be changed. The designated media announcement is not supported. IP Bearer Changing After IP bearer is set up. Abnormal process   2) The IP bearer set up fails if R-BIWF can not correctly identify the request message from I-BWF or the accept message returned by R-IWF is wrong. In terms of R-BIW at the receiving side. In terms of I-BIWF at the sending side.1 IP bearer changing Both I-BIWF and R-BIWF can originate IP bearer changing. If so. tone capability and signal capability. the following abnormal cases may appear.   The contents of REQUES received are wrong. the media announcement domain returned is consistent with that in the request message.

If so. The designated Media announcement is not supported. I-BIWF will acknowledge the ACCEPTED message. I-BIWF sends a REQUEST message to request to modify IP bearer. The following abnormal cases may happen to the receiving side. I-BIWF stops T2 and checks the message according to the following rules. tone capability and signal capability.Technical Manual – Signaling & Protocols HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 NbUP and IPBCP 1 described later with I-BIWF being the initiating side as example. the contents of media announcement in the ACCEPTED message should be consistent with those in the REQUEST message.   The REQUEST message is wrong. they must be accepted by R-BIWF. If all those rules are met. R-BIWF will check the message.  For the Media announcement. The IP bearer changing process originated by R-BIWF is the same as that by I-BIWF. other media attributes should be consistent with the media attributes in the REQEUST message. IP Bearer Release IP bearer release concerns no IPBCP message interworiking. 2) IP bearer changing fails The following abnormal cases may happen to the initiating side. If no abnormality is found. and the IP bearer modification is completed at the initiating side. III. Such parameters are included in the message as media announcement and media attribute. the initiating side will stop T2 and demand to modify the bearer control entity. tone capability and signal capability are included in the ACCEPTED message. After receiving the ACCEPTED message. Except time capability. I-BIWF starts a timer (T2). The receiving end should return the REJECTED message. IPBCP is applied to Huawei Technologies Proprietary 10 . After that.   If time capability.   The REJECTED message is received. The ACCEPTED message is wrong. After the REQUEST message is sent. the upper-layer control part is notified about the information that the IP bearer has been changed. the ACCEPTED message will be returned containing such parameters as media announcement and media attribute. except the port number. except that messages involved are in the reverse flow. Upon receiving the REQUEST message. And except time. other options of media attribute should be identical with those in the REQUEST message. other information should be consistent with that in the REQUEST message I-BIWF sends. The ACCEPTED message sent by the receiving side means that the IP bearer modification is completed at the receiving side. Except the port number.

.1. the receiving side will return the CONFUSE message which contains the version number T-Version it supports.. Huawei Technologies Proprietary 11 ..Technical Manual – Signaling & Protocols HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 9 NbUP and IPBCP 1 BICC environment. If it is not supported. The process is shown in Figure 1. When receiving the CONFUSED message.. the receiving side will use this version number in all the messages sent to the remote side later. If t I-Version is supported. and IP bearer release is triggered by CSF...1 Capability interworking process The REQUEST message includes the version number parameter I-Version.] R-BIWF Figure 1. the initiating side will resend REQUEST....] Request[T-Version .. I-BIWF Request[I-Version . the initiating side will report to the control entity. Capability Interworking This process is to negotiate the IP BCP version of the two interwroking sides. using T-Version.. If it is not supported. it will check the version number. IV. If T-version is supported... the initiating side will check the version number T-version contained in the message. When the receiving side receives the REQUEST message..] Confused[T-Version ..