KR20020035668A - Interface between MTP2 and MTP3 in SS7 block of base station controller - Google Patents

Abstract

PURPOSE: An interface method between an MTP(Message Transfer Part)1 and an MTP2 for an SS7(Signalling System No.7) block in a base station controller is provided to achieve inter-layer data transmission and reception by adding a new L2 API layer for the interface between an MTP1 and an MTP2 when the MTP 1 and 2, an MTP3, and an SCCP(Signalling Connection Control Part) are installed at different hardwares. CONSTITUTION: An SS7 block judges whether the format of a frame header attached to the front of data is correct(S101). In case that the format of the frame header is wrong, the SS7 block disposes of the present message(S113). If the format of the frame header is correct, the SS7 block confirms what primitive is to be executed and copies necessary parameters to a temporary variable(S103). Then, referring to a structure that mBuf indicates, the SS7 block reads the address value of a data buffer(dBuf)(S105). The SS7 block creates a new message queue and copies the data of the data buffer(S107). Then the SS7 block calls a primitive comprising the parameters and the data buffer address(S109). In case that the called primitive is a Dat/Sat primitive, the SS7 block judges whether the receiving side's confirmation has been conducted(S111).

Description

Interface between MTP2,3 of SS7 block in base station controller {Interface between MTP2 and MTP3 in SS7 block of base station controller}

The present invention relates to a communication system using the number 7 signaling system (SS7: Signaling System No. 7), and more particularly, in the base station controller SS7 (Signalling System No. 7) block MTP (Message Transfer Part) 1, When M2 and MTP3 and Signaling Connection Control Part (SCCP) are mounted on different processors or boards, the interface method between MTP2 and 3 of SS7 blocks in the base station controller enables data transmission between layers by defining their interface method. It is about.

1 is a block diagram of a general mobile communication system, which is connected to a mobile station (10) and a mobile station (10), commonly referred to as a cellular phone, and operated at a point that is not moved or specified, and which is requested by the mobile station. A base station 20 for controlling a mobile station, such as transmitting a call transmission request of a control station 30 to the mobile station 10, and performing signal processing between the base station 20 and the exchange 40. Control station 30 that controls 20 and the communication network connected to the control station 30 and other communication network to the public telephone network 50 or analog network 60 through a public network or a dedicated network to request a call processing request of the mobile station 10 It is composed of a switch (40) for transmitting to enable a mobile communication service.

In the general mobile communication system configured as described above, if the subscriber wants to use the mobile communication service with his mobile station within the service radius of the exchange, the exchange determines the position of the mobile station under the control of the control station, Accordingly, it operates to perform a mobile communication service by performing a voice and fax information service or by connecting with another communication network.

2 is a block diagram of an SS7 block in a base station controller according to the prior art.

As shown, error detection and correction between the message transfer part 1 (MTP1) 100, which is a physical layer defining the electrical and functional characteristics of the signal data link, and two signal points over the signal data link, It defines the MTP2 200 corresponding to the data link layer such as monitoring the sequence message and the error of the signal link, and the transfer functions and procedures common to the independent operation of each signal data link. MTP3 (300), a network layer that performs a signal network management function to maintain message processing capability, and signaling information or maintenance and transportation information for additional services such as inquiries between databases while being used for transmission of non-line correspondence signals. It consists of a Signaling Connection Control Part (SCCP) 400 which is a call connection control layer for transmitting the.

However, when the four SS7 layers configured as described above (MTP1, MTP2, MTP3, SCCP) are all mounted on one processor or board according to the conventional technology, there is no problem in performing the data transmission / reception function of the SS7. If they are mounted on two boards or different processors, each layer must be separated into hardware, and thus, the SS7 block is difficult to implement in various hardware structures.

Therefore, the present invention has been proposed to solve all the problems according to the prior art as described above, the object of the present invention is

When the MTP (Message Transfer Part) 1, 2, MTP3, and SCCP (Signalling Connection Control Part), which is a layer of the SS7 block in the base station controller, is mounted on different hardware, an application interface called L2 for an interface between MTP2 and MTP3; By adding a new API) layer, the present invention provides an interface method between MTP2 and 3 of SS7 blocks in a base station controller that enables data transmission and reception between layers.

In order to achieve the above object, the MTP2,3 interface method of the SS7 block in the base station controller according to the present invention,

Defining primitives that perform requests, confirmations, instructions, and the like;

Defining a frame header pasted to the transmission / reception data;

The method configuration features that the step of making L2 refer to the frame header to make the communication between the MTP2,3 by calling the primitive.

In addition, the MTP2,3 interface method of the SS7 block in the base station controller according to the present invention in order to achieve the above object,

Checking whether the format of the frame header is correct;

Identifying what primitives (functions) and parameters are required for communication between the two layers by referring to a signal ID (sigId) in the frame header, and copying the parameters required for the primitives to a temporary variable;

Reading the address value of dBuf, which is a data buffer, from mBuf, which is the address of the structure;

Creating a new message queue (Que) to copy the data in dBuf;

Calling a primitive comprising a parameter and a data buffer address;

When the called primitive is Dat or Sta primitive, it is characterized in that the method configuration is performed to check whether there is confirmation of the receiving end.

1 is a block diagram of a general mobile communication system,

2 is a block diagram of a SS7 block in a base station controller according to the prior art,

3 is a configuration diagram of an SS7 block in a base station controller according to the present invention;

4 is a configuration diagram of primitives used between MTP2 and MTP3 of FIG. 3,

5 is a flowchart illustrating an interface method between MTP2 and 3 of SS7 blocks in a base station controller according to the present invention.

<Explanation of symbols for the main parts of the drawings>

30: control station

200: MTP2 (Message Transfer Part 2)

400: Signaling Connection Control Part (SCCP)

Hereinafter, the MTP2,3 interface method of the SS7 block in the base station controller according to the present invention as described above in detail based on the accompanying drawings.

3 is a block diagram of an SS7 block in a base station controller according to the present invention.

As shown in the figure, an MPC750 (66) processor and an MPC860 (77) processor are mounted in a call control processor (CCP) 88, and the two processor layers of the SS7 block (MTP1, MTP2, MTP3 and SCCP) are implemented separately.

In more detail, the MPC750 (66) of the two processors constituting the CCP (88), the call processing processor, SCCP (11) in charge of call connection control and MTP3 (22) of the network layer The MPC860 (77) processor is equipped with MTP1, 2 (33) and is in charge of the physical layer and the data link layer, respectively.

In addition, the L2 (44), which is an API (Application Inerface) layer, is inserted for the interface of the separated layer, and is responsible for communicating with the MTP3 mounted in the MPC750 (66) processor and the MTP2 mounted in the MPC860 (77) processor. Appointments between two tiers are set to convert messages into understandable message formats.

In addition, the SM 55 (Stack Manager) reports the status of each layer and reports it to a base station manager (BSM). In addition, it receives various MMC (Man Machine Command) commands and makes each layer execute this command.

In the above configuration, MTP2 and MTP3 request from the upper end to the lower end in relation to the state of each other or the transmission and reception of data and disconnection of the signal link, and the lower end confirms the request of the upper end, and the state or link of each layer. The interface functions such as reporting to the upper stage about the change of the. It is defined through a primitive (function) in a program used between MTP2 and MTP3.

4 is a configuration diagram of primitives (functions) used between MTP2 and MTP3 of FIG. 3.

As shown, MTP2 (93), which is the lower stage, and MTP3 (97), which is the upper stage, are designated as symbols of Sd (91) and Sn (92), respectively.The symbol indicating the request of the upper stage for the lower stage is Req (Request). (94). In addition, the symbol representing the confirmation of the lower stage for the request of the upper stage is Cfm (Confirm) 95, and the symbol used when the lower stage reports to the upper stage without the command of the upper stage is Ind ( Indication 96). Sdt 98 is a Service Access Point (SAP) that acts as a bridge between MTP2 and MTP3.

For example, when describing SdUiSdtDatInd among primitives, this primitive is used when MTP2 reports to MTP3 when data is input from MTP2 to MTP3. Followed by Ui, representing MTP3. In addition, Sdt representing a service access point (SAP), which plays an intermediate role between MTP2 and MTP3, comes after Ui, Dat means data, and Ind reporting that data comes from a large country is added to SdUiSdtDatInd.

Primitive components not described above include Sta and Disc, which means that the signal link is inactive, that is, the link is disconnected. When the upper end requests the lower end to disconnect the signal link ( SdUiSdtDiscReq) or to report to the higher level (SdUiSdDiscInd) when a signal link suddenly becomes inactive.

In addition, Sta means Status, which is used when the higher level asks the lower level to change to something (SdUiSdtStaReq), or to report to the higher level when a status change occurs in each layer (SdUiSdtStaInd). Used.

When the system is running, the lower stage has different processors, so the configuration is performed by itself.When ConReq is transferred from the MTP2 to the lower stage, when the data is received from the large station after opening the port at MTP1, the ConCfm is raised to the MTP2. After receiving this, MTP2 starts the initial sort. After initial sorting, ConCfm is raised to MTP3 again. MTP3 starts data transmission from this time.

The types of primitives defined as above are as follows.

SdUiSdtConReq (lnkNmb, status)

SdUiSdtConCfm (suId)

SdUiSdtDiscReq (lnkNmb, reason)

SdUiSdtDiscInd (suId, reason)

SdUiSdtStaReq (lnkNmb, action, status)

SdUiSdtStaCfm (suId, action, status)

SdUiSdtStaInd (suId, status)

SdUiSdtDatReq (lnkNmb, mBuf)

SdUiSdtDatInd (suId, mBuf)

SdUiSdtDatCfm (suId, mBuf, status)

The parameters in parentheses in the primitives are as follows. lnkNmb and suId are parameters required for all primitives, which means a signaling link. Among them, lnkNmb is a symbol for link number, and MTP1,2 exists on the actual board, so it is necessary to indicate which MTP1,2 should be requested when requesting the lower level from MTP3.

Therefore, the four primitives (SdUiSdtConReq, SdUiSdtDiscReq, SdUiSdtStaReq, SdUiSdtDatReq) containing the Req symbol used when the upper level requests the lower level need the lnkNmb parameter indicating one of several MTP1,2.

Conversely, the lower tier must identify itself to the higher tier when checking or reporting to the higher tier. Thus, all primitives containing Cfm and Ind symbols require a suId parameter, which stands for Service User ID.

In addition, reason is a parameter that indicates the reason when the lower level reports to the higher level because the signaling link becomes inactive, or when the higher level commands the lower level to deactivate the signaling link. This parameter is used to report to the upper part when the state change occurs in the upper part, or to instruct the lower part to change to some state.

MTP2 and MTP3 transmit the data that they want to send to each other with a frame header composed of the following code.

typedef struct FrameHeader

{

Word32 destId;

Word32 srcld;

Word16 sigId;

Word16 Msglen;

Word8 action;

Word8 reason;

Buffer * mBuf;

} FRAME_HD;

In the frame header, destId, srcId, sigId and Msglen are information on data sent between layers. destId (Destination ID) represents the address of the hardware on which the reception block is mounted, and srcId (Source ID) represents the address of the hardware on which the transmission block is mounted. In addition, sigId, which stands for Signal ID, contains information about what primitives (functions) to execute, and Msglen, which stands for Message Length, contains information about the total length of data transmitted and received.

In addition, in the frame header, action, reason, * mBuf are parameters required for invoking a primitive (function), and status means status in StaInd (status indication), StaReq (status request), and StaCfm (status check) among the primitives. The action value is used, and action is a parameter used when the lower level asks for an action in StaReq.

reason is when the higher level commands the lower level to indicate the reason for the deactivation of the signal link, or when the lower level reports the reason to the upper level when the signal link becomes inactive for some reason. This parameter is used to represent the address of a structure containing mBuf information about a data buffer containing actual data.

5 is a flowchart illustrating an interface method between MTP2 and 3 of SS7 blocks in a base station controller according to the present invention.

First, it is determined whether the format of the frame header prepended to the data is correct (S101).

As a result of the determination in step S101, if the format of the frame header is incorrect, the message is discarded and then proceeds to the next message (S113).

If, as a result of the determination in step S101, if the format of the frame header is correct, the sigId is checked to determine what primitives (functions) to execute and the parameters necessary for the primitives are copied to a temporary variable (S103).

Next, the address value of dBuf (data buffer) is read with reference to the structure indicated by mBuf (S105).

Subsequently, a new message queue Que is created and the data in dBuf is copied (S107).

Then call the primitive that contains the parameters and data buffer address. (S109)

Subsequently, if the primitive called in step S109 is a Dat or Sta primitive, it is determined whether there is an acknowledgment on the receiving side (S111), and if there is an acknowledgment on the receiving side, the transmission is terminated.

As a result, the MTP2,3 interface method of the SS7 (Signalling System No.7) block in the base station controller according to the present invention defines an application interface (API) called L2 between MTP2 and MTP3 implemented in hardware. Thus, L2 refers to a frame header containing information and parameters necessary for data communication such as sigId and Msglen, thereby enabling error-free data communication between MTP2 and MTP3.

As described above, the MTP2,3 interface method of the SS7 block in the base station controller according to the present invention defines the interface method when MTP1,2, MTP3, SCCP are mounted on different hardware in the SS7 block of the base station controller. Data communication between layers can be performed smoothly to perform the functions of each block, and SS7 (Signalling System No. 7) can be implemented in various hardware structures.

Claims (2)

In the interface method between the MTP2, 3 of the SS7 block in the base station controller according to the present invention, Defining a primitive for performing a request, confirmation, indication, etc. between MTP2 and MTP3; Defining a frame header pasted to the transmission / reception data; And causing L2 to refer to the frame header to invoke the primitive to make communication between MTP2,3, MTP2,3 interface method of the SS7 block in the base station controller. The method of claim 1, wherein the L2 enables transmission and reception of primitives and data between MTP2 and 3 with reference to a frame header. Checking whether the format of the frame header is correct; Identifying what primitives (functions) and parameters are required for communication between the two layers by referring to sigId in the frame header, and copying the parameters required for the primitives to temporary variables; Reading the address of dBuf, which is the data buffer, from mBuf, which is the address of the structure; Creating a new message queue (Que) to copy the data in dBuf; Calling a primitive comprising a parameter and a data buffer address; If the called primitive is a Dat or Sta primitive, checking whether the receiving end has been confirmed or not; and performing an MTP2,3 interface method of the SS7 block in the base station controller.