KR19990034341A - Channel Deletion Request Primitive Processing According to Delay Equalization Protocol - Google Patents

Abstract

The present invention relates to a method for processing a channel deletion request primitive in a DEQ negotiation control layer in a delay equalization protocol structure composed of a call control layer, a delay equalization negotiation control layer, and a delay equalization multiframe control layer.

Conventional protocol implementations receive primitives according to the state after determining the current state, and then run the primitive processing routines according to the determined state. However, since the implementation of the protocol of the present invention classifies received primitives and considers their statuses, it is easy to merge these processing procedures and reduce the code size when the processing procedures of each state are similar or identical for the same primitive. You can expect an increase in speed.

When the channel deletion request primitive is received in the DEQ multiframe control layer, the present invention analyzes the primitive and simultaneously executes an appropriate primitive and a procedure according to the current state to perform channel deletion and transition to the next state.

Description

Method of processing deleting channel require primitive according to delay equalization protocol in ISDN

The present invention relates to a delay equalization protocol for bonding a plurality of 56/64 kbit / s channels in order to deliver broadband data in an ISDN, in particular, call control. In the delay equalization (DEQ) protocol structure consisting of a Control layer, a DEQ Negotiation Control layer, and a DEQ multiframe control layer, a negotiation is performed between the DEQ negotiation control layer and the DEQ multiframe control layer. A method of processing a channel delete request primitive (CC_DEL_REQ).

As the information society has progressed, communication demands have diversified, and the media handled by communication networks such as voice, data, and video have also diversified, so that individual networks established by services cannot provide efficient services. Therefore, the ISDN, which can integrate and digitize individual networks established by services and provide comprehensive services, has emerged. These ISDNs are designed to unify various terminals in order to accommodate users and manganese. The interface is standardized by Digital Subscriber Signaling System (DSS1), and the interface between the network and the network is also standardized by No.7 Common Line Signaling (CCS).

DSS1, which is a signaling method of the user-network interface (UNI) of ISDN, is implemented in layers 1 through 3 by an OSI (Open Systems Interconnection) reference model, as shown in FIG. The overview and its relationship with the recommendations of the ITU-T are shown in Table 1 below.

Digital subscriber line signaling Layer Feature Overview Corresponding recommendations Layer 1 Electrical physical conditions I.430, I.431 Layer 2 Link setting control and error control for message transmission Q.920, Q.921 Layer 3 Set up, opening Q.930, Q.931

Referring to FIG. 1, a first network terminal device NT1 located in a house (or building) is connected to an ISDN exchange located in a telephone station through a subscriber line, and an ISDN terminal TE1 is connected to an ISDN terminal in a building through an S / T point. Alternatively, the second network terminal device NT2 is connected to the first network terminal device NT1.

Here, 'NT1' (network terminal device 1) is a transceiver in a house for transmitting a digital signal to a subscriber line, and 'NT2' (network terminal device 2) is a device corresponding to a private branch exchange (PBX). The terminal TE1 can be accommodated, and the TE1 is an ISDN standard terminal that is directly connected to NT1 and may be connected via NT2, and an existing terminal that does not have an ISDN corresponding function, 'TE2' is not shown. It is connected to the ISDN network through a terminal adapter (TA).

In addition, the interface point between NT1 and NT2 is called 'T' point, and the interface point between NT2 and TE1 is called 'S' point. Since the interface specification of S point is determined to be based on T point, TE1 is The point to be connected is called the 'S / T' point.

In addition, the subscriber terminal, such as the ISDN terminal, is connected according to the above-described protocols of the layers 1 to 3 so as to be connected to the ISDN exchange, and the recommendations for defining such a connection are shown in Table 1 above.

That is, in Table 1, Layer 1 is a user-network interface of the physical layer recommended by ISDN Recommendations I.430 and I431, and has a basic interface of 2B + D access and a primary group speed interface of 23B + D or 30B + D. In the basic interface, the frame structure consists of 48 bits in 250us units.

Layer 2 is commonly referred to as Link Access Procedure on the D channel (LAPD), which first adopts HDLC's BALANCE mode, which is the standard for the standardized data link layer, and its basic format is Flag. And an address field, a control field, an information field, a frame check sequence (FCS), and a flag.

Layer 3 controls the establishment, maintenance, and release of communication paths required by the network and packet switched services, and various additional service requests. The message is analyzed, and a call establishment related message is formed and sent to the other party through the lower layer. General content relating to Layer 3 is described in Q.930, and call processing procedures for basic calls are recommended by Q.931.

In order to implement an ISDN terminal, the functions described above should be implemented. The "protocol" is defined as an appointment between the same layers, and the "primitive" is defined as a logical exchange between upper and lower layers. . That is, each layer has entities that implement the functions of the layer, and these entities are configured to exchange information between upper and lower sides through primitives.

These primitives are divided into four types: REQUEST, INDICATE, RESPONSE, and CONFIRM. Most of the primitives related to data transfer are REQUEST passed from the upper layer to the lower layer. ) Primitives, and INDICATE primitives passed from the lower layer to the upper layer.

The CONFIRM primitive is a primitive that notifies the upper tier when a lower tier is obliged to respond to a particular request primitive from a higher tier, and the RESPONSE primitive is for a particular indication primitive from the lower tier. It is a primitive to inform the lower tier if the upper tier is obliged to respond.

Channels provided by ISDN include 64Kbps "B" channel, 16kbps "D" channel, 384Kbps "H0" channel, and 2.048Mbps "H1" channel. The basic interface provided by the combination of these channels is "2B". + D ", and the primary group interface is defined as" 23B + D "or" 30B + D ". However, when a wideband communication connection is required for a video service in narrowband ISDN, multiple (N) 56 or 64 kbit / s channels may be used in combination. That is, if the basic interface or the primary group interface has a fixed bandwidth but various bandwidths are required according to a service, the ISDN network may provide an "N x 56/64 kbit / s" band.

In order to provide "N x 56/64 kbit / s" as described above, bonding of 56/64 kbit / s channels set independently of each other is required. In this case, since each 56/64 kbit / s channels are individually connected by the digital switching network, each channel has an individual delay. Therefore, the key technical details of multiple coupling are related to delay equalization, so follow "Delay EQualization protocol" to provide N x 56/64 kbit / s. That is, the delay equalization protocol is also called a bonding protocol, and is a protocol for equalizing delay between channels when combining N 56/64 kbit / s channels.

As shown in FIG. 2, the delay equalization protocol is composed of a Call Control layer, a DEQ negotiation control layer 22, and a DEQ multiframe control layer 23. User data received from the application layer 21 is transmitted, and primitives are transferred to each other as shown in FIG. 3. In FIG. 2, the DEQ multiframe control layer 23 is connected to the physical medium through each channel control and physical medium dependency (PMDL) layer 24a to 24c below.

Referring to FIG. 3, primitives transmitted from the call control layer 25 to the DEQ negotiation control layer 22 include an initial request (DQ_INIT_REQ), a connection request (DQ_CONN_REQ), a disconnect request (DQ_DISC_REQ), and a channel deletion request (DQ_DEL_CH_REQ). , Channel add request (DQ_ADD_CH_REQ), abandonment request (DQ_ABORT_REQ), and the timers used in the DEQ negotiation control layer 22 include TCID_EXP, TCINIT_EXP, TAINIT_EXP, TANULL_EXP, TCADD01_EXP, and TAADD01_EXP. DEQ negotiation with primitive transmitted to the control layer (22) of the control layer 25 from the DQ_INIT_IND, DQ_DISC_IND, DQ_DISC_CONF, DQ_DEL_CH_CONF, DQ_DEL_CH_IND, DQ_DEL_CH_FAIL_IND, DQ_ADD_CH_IND, DQ_ADD_CH_CONF, DQ_ADD_CH_FAIL_IND, DQ_CID_FAIL_IND, DQ_LLOS_IND, DQ_RLOS_IND, DQ_ABORT_CONF, DQ_LL_IND, DQ_LL_OFF_IND, DQ_RL_IND, DQ_RL_OFF_IND, and the like.

In this case, xx_xxxx_REQ represents a request primitive, xx_xxxx_IND represents an indication primitive, xx_xxxx_RES represents a response primitive, and xx_xxxx_CFM represents an confirm primitive. CC_xxxx_xxx is a primitive between the DEQ multiframe control layer 23 and the DEQ negotiation control layer 22, and DQ_xxxx_xxx is a primitive between the DEQ negotiation control layer 22 and the call control layer 25.

Primitives transmitted from the DEQ negotiation control layer 22 to the DEQ multiframe control layer 23 include CC_ADD_REQ, CC_INFO_REQ, and CC_DEL_REQ. The timers used in this layer include TAFA_EXP and TXDEQ_EXP, and the DEQ multiframe control layer 23 The primitives transmitted to the DEQ negotiation control layer 22 are CC_LSYNCH_IND, CC_RSYNCH_IND, CC_RSYNCH_FAIL_IND, CC_INFO_IND, CC_FAIL_IND, CC_LLOS_IND, and CC_RLOS_IND. These primitives are described in detail in the "Interoperation Specification for Nx56 / 64 kbit / s Call (Version 1.1)" issued by the Bonding Consortium, dated September 2, 1993, and further description thereof is omitted.

On the other hand, the conventional scheme for handling such primitives in Layer 3 has been proposed as SDL in Appendix A (ANNEX A) of the recommendation, which is roughly summarized as shown in FIG.

Referring to FIG. 8, the conventional method first determines a current state of a corresponding layer (S1), and when a primitive is received (S2), drives a primitive processing routine for processing the corresponding primitive according to the determined state (S3). ).

However, in the conventional method of FIG. 8, even though the processing is similar or the same in different states with respect to the same primitive, processing routines may be duplicated according to each state, resulting in a large amount of redundant code and a long processing time in software implementation. There is a problem. If the subroutine call method is used to avoid such code duplication, it is difficult to construct a subroutine that is appropriately divided over various states even though the amount of code is reduced. There was a problem that the processing speed was lowered.

Accordingly, the present invention has been proposed to solve the above-mentioned problems. In the delay equalization protocol, the processing routine according to the primitive is separated after separating the processing routine in consideration of the current state according to the type of the primitive. In particular, an object of the present invention is to provide a channel deletion request primitive processing method that minimizes a processing procedure when a channel deletion request primitive is received.

The channel deletion request primitive processing method of the present invention for achieving the above object comprises the steps of: (a) receiving a channel deletion request primitive (CC_DEL_REQ) generated in the DEQ negotiation control layer in the DEQ multi-frame control layer; (b) analyzing the channel deletion request primitive in the DEQ multiframe control layer, determining a current state, and branching by state according to the contents of the primitive; (c) If, as a result of judgment in b), the channel deletion request primitive requests deletion of all channels, and the current state is the local synchronization synchronization, remote synchronization standby status, mode 1 hand shake, all channel synchronization, and mode 1 active status, Driving a procedure to delete all channels; (d) driving the channel deletion procedure if the current state is an unchecked synchronous search state as a result of the determination of b); (e) As a result of the determination in b), if the channel deletion request primitive specifies the number of channels (N) and the channel identifier (CID = x) and the current state is the remote synchronization standby state and all channel synchronization state, Determining a channel delay equalization after decreasing; (f) if the current state is the local synchronization standby state as a result of the determination of b), deleting the designated channel, examining channel synchronization, and performing channel delay compensation; (g) after step c) or d), transitioning to a null state and ending; (h) after step e), transitioning to a local synchronization standby state and ending; And (i) after step f), transitioning to and exiting from the remote synchronization standby state.

1 shows a user-network connection of an ISDN;

2 shows a reference architecture of a delay equalization protocol;

3 is a schematic diagram illustrating primitives carried between layers to implement a delay equalization protocol in ISDN,

4 illustrates a frame structure in a delay equalization protocol;

5 shows an information message format;

6 is a flowchart illustrating a process of establishing a call in a delay equalization protocol;

7 is a flowchart of processing a channel delete request primitive according to the present invention;

8 is a schematic diagram illustrating a procedure for processing a conventional primitive.

Explanation of symbols on the main parts of the drawings

21: Application Layer 22: Delay Equalization Negotiation Control Layer

23: Delay Equalized Multiframe Control Layer 24a, 24b, 24c: Channel Control Physical Layer

25: call control layer

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings.

FIG. 2 is a diagram illustrating a reference architecture of a delay equalization protocol, FIG. 3 is a schematic diagram illustrating primitives transmitted between three layers for implementing a delay equalization protocol in ISDN, and FIG. 4 is a diagram illustrating a frame structure in a delay equalization protocol. Figure is shown. 5 is a diagram illustrating an information message format.

Referring to FIG. 2, the delay equalization protocol is implemented by a call control (CC) layer 25, a delay equalization negotiation control (DEQ NC) layer 22, and a delay equalization multiframe control (DEQ MC) layer 23. As shown in FIG. 3, various primitives are transmitted between the layers.

In order to deliver the serial bit stream coming down from the application layer by multiple combinations of N 56/64 kbit / s channels, as shown in FIG. 4, framing is required, and the framed data is allocated to each bearer channel. Will be delivered.

As shown in FIG. 4, the framing structure according to the delay equalization protocol is composed of 256 octets, and 64 frames are gathered to form one multiframe. The octets in each frame are numbered from 1 to 256, and four overhead octets are used for information exchange and framing. That is, in one frame, octet 64 is assigned to a frame alignment word (FAW), octet 128 is assigned to an information channel (IC), and octet 192 is assigned to a frame count (FC). Is assigned. Octet 256 is assigned to a cyclic redundancy check (CRC).

Looking more closely at each overhead octet, the FAW (octet 64) has a fixed value of "0001,1011", the IC (octet 128) is used for information exchange between terminals, and the FC (octet 192) is an individual channel. It is used to measure the relative change in delay between modulo 64 counters (6 bits), incremented by 1 per frame. In CRC (octet 256), bit 1 and bit 8 are 1, bit 2 is defined as "A", bit 3 as "E", and bits 4 to 7 are used for CRC4. Here, "A" is an alignment bit, indicating that the remote terminal has lost framing, and "E" is an error bit, indicating that the remote terminal has detected an error by CRC4.

This overhead distributes the overhead octets across all channels as evenly as possible by allowing them to be distributed over each channel at 125usec intervals.

On the other hand, the information channel (IC) message format, as shown in Figure 5, consists of 16 octets to transfer control information between the two terminals. Referring to FIG. 5, the first octet of the information channel frame has a constant value of "0111,1111" as an alignment (ALIGN), and the second octet may dial N calls simultaneously as a channel ID (Channel ID: CID). It is used to identify individual channels in each call setup. CID is a 6-bit binary number encoded with a number in the range of 0 to 63, and a CID of 0 indicates parameter negotiation.

The third octet of the information channel message is a group identifier (GID), which is used to uniquely identify a group of bearer channels associated with a particular call. Octet 4 (bits 2 through 4) indicates the operation mode (MODE), where "0" indicates operation mode 0, "1" indicates operation mode 1, "10" indicates operation mode 2, and "11" indicates operation mode. 3 is shown, respectively.

In octet 5 (bits 2 to 4) of FIG. 5, "RMULT" is the rate multiplier, which, together with "SUBMULT" in octet 6, defines the bandwidth of the application for the call, and the BCR represents the bearer channel rate. 0 indicates 56kbit / s base and 1 indicates 64kbit / s base. In octet 6, " MFG ", if set to 1 as the manufacturer ID flag, indicates that the manufacturer ID is loaded in the digit fields of octets 10-16. In octet 7, " RI " is a remote indicator for informing the counterpart of whether the delay equalization is complete, and a value of 1 indicates an equal delay (delay equalization completion). In octet 7, "RL REQ" indicates a remote loopback request and "RL IND" indicates a remote loopback indication. "REV" represents the revision level, octet 8 represents the subaddress, and octet 9 represents the transfer flag as "XFLAG". Octet 10 to octet 16 indicate telephone number dial digits (Digit-1 to Digit-7).

6 is a sequence diagram illustrating a message flow in call setup.

First, the terms used in the present invention are briefly defined as follows. The answering terminal is a terminal for receiving a call, and the calling terminal is a terminal for initiating a call. The bearer channel is a channel provided by a network used for data transmission, for example, a B channel of BRI or PRI, a T1 DS0, etc., and an information message is a 16 octet message as shown in FIG. It is conveyed through the information channel of the multiframe structure or by the full bandwidth of the master channel during initial parameter negotiation. Master channel is a channel used to communicate control information between each end, which is call setup, channel delete, channel addition, remote loopback ) Provides a path for initial parameter negotiation for call disconnection and the like.

In case of using the delay equalization protocol, four operation modes are defined.

"Operation Mode 0" supports initial parameter negotiation and DIRECTORY NUMBER exchange on the master channel, and then transfers the data without delay equalization when call setup is complete. This mode is useful when the calling endpoint requires a phone number, but delay equalization must be done by other means. That is, in operation mode 0, delay equalization (delay compensation) is not performed.

"Operation Mode 1" is the default (common) mode of the delay equalization protocol that supports the user data rate multiplied by the bearer rate, and does not provide in-band monitoring for errors. Thus, the overhead octets for detecting errors are eliminated after the call is aligned, and one or more on-channel error conditions that prevent all system synchronization are not automatically recognized after the call is ACTIVE.

"Operation Mode 2" supports user data rates that are 63/64 times the bearer rate. This mode of operation provides in-band monitoring and the user data rate is the remaining band after the insertion of the overhead octets. That is, the error is checked while the multiframing structure is maintained even after being activated.

"Operation Mode 3" is the user data rate is an integer multiple of 8kbit / s, including Nx56 and Nx64. All channels use the same bearer channel rate and provide in-band monitoring to support continuous equalization (CRC) for delay equalization and end-to-end bit error test. The overhead octets required for error monitoring are provided with additional bandwidth. Thus, a sufficient user data rate can be provided, and overhead octets are included in each bearer channel.

Based on the understanding of such a definition, a process of actually setting up a call according to a bonding protocol and transmitting data will be described with reference to FIG. 6.

First, when a high speed serial data stream comes down from the application layer, data is transmitted through N bearer channels. Each bearer channel is then individually connected by digital network exchange. On the originating terminal side, the user data is framed according to the framing structure as shown in FIG. 4 and then delivered to each bearer channel. On the destination terminal side, the received data is synchronized and aligned to restore the original bit stream. do. Framing and synchronization should be transparent to all applications. In the delay equalization protocol, the entire operation is performed by the call establishment process, the process of adding the bandwidth to the existing call after the channel connection is established by the call establishment, and the bandwidth is deleted from the existing call in order to reduce the user data without sudden degradation of the entire call. There is a process.

The call setup process involves establishing an initial channel (called a master channel), adding N-1 other channels by multiple combining after the initial channel is established, and implementing delay equalization when each channel is connected. There is a delay equalization (DEQ) process.

6 is a flowchart illustrating a call setup process, wherein the initial channel setup includes steps 601 to 604, the multiple combining process includes steps 605 and 606, and the DEQ process includes steps 607 to 609. After the call setup is made, user data of the application layer is allocated to each channel through a framing process in an active state.

The initial call setup procedure begins with the connection of the first channel on an N x 56/64 kbit / s call. This channel is called the master channel (601). The parametric negotiation process is performed by this channel, and the originating terminal makes additional calls after the complete negotiation process is completed. Once the originating terminal is connected to the master channel, the originating terminal repeatedly transmits an information message (see FIG. 5) with a channel identifier (CID) set to 0 to start a negotiation process (602). The starter (TCINIT_EXP) timer is started. At this time, the originating terminal transmits by setting each parameter of the information message to a specific value. The group identifier (GID) is set to 0, and RI = 0 and RL = 0, respectively. In the first information message, the calling terminal sets the MFG to 1, sends the manufacturer's ID with the ID in the digit field, and the XFLAG is set to all 1's. If the calling terminal fails to transmit the manufacturer ID, the MFG flag is set to 0 and the digit fields are all set to 1. If the calling terminal supports sub-addressing, the sub-address area includes the sub-address, and if not, the corresponding area is set to all zeros.

When a call is received and connected with the other party, the destination terminal sends all 1s to the channel, starts the destination NULL (TANULL_EXP) timer, and searches for multi-frame information or information message.

Once the end of incoming call detects a valid information message, it considers the channel as the master channel of the new call and stops the terminating null timer (TANULL_EXP). If a multi-frame is detected, the called terminal regards the current call as an additional channel, stops the called party NULL (TANULL_EXP) timer, and uses a group identifier (GID) to identify the current call.

In the master channel of the new call, if the called terminal accepts the requested parameter, it returns the same value as the received value and starts the called party's initial (TAINIT_EXP) timer. If not accepted, the RMULT and SUBMULT = 0 return with the valid mode value in the information message, and the called party initiates the truncation procedure or returns a set value different from the received parameter. In the additional channel of the current call, the called terminal allocates the group identifier (GID) of the call and returns the call in the group identifier (GID) area. The call can be identified in the call received by the group identifier to the called terminal. At this time, the XFLAG region of the information message is set to one.

When the called terminal determines the manufacturer ID return, the MFG flag of the information message is set to 1, puts the ID in the digit field, and returns the information message with other parameters as the initial response to the calling terminal. If the destination terminal does not want to return the manufacturer ID, the MFG flag of the information message is set to 0 and the digit field is set to 1.

The calling terminal detects that the response is from the called terminal when CID = 0 and the MODE receives a valid information message from the called terminal. Therefore, the calling terminal analyzes the parameters of the received information message and performs the truncation procedure if it cannot accept or cannot accept the parameters requested by the called terminal. If the MFG flag of the received information message is 1, the manufacturer ID contained in the digit field is received. If the MFG flag is 0, the digit area is ignored, and the XMFG flag is ignored.

Subsequently, the originating terminal requests an initial telephone number (Directory Number: DN) by transmitting an information message with CID = 0 and a transmission flag set to 1 and all of the digit fields to 1 (603).

After the initial response, when the called terminal receives the information message with the XFLAG set to 1, the destination terminal sets the XFLAG of the information message to 1 and carries the telephone number in the digit field and returns the information message again. In this way, the calling terminal and the called terminal exchange telephone numbers (DN). If the number of channels is N, exchange N-1 phone numbers (DNs).

That is, when the calling party receives DQ_CONN_REQ from the call control layer to the DEQ negotiation control layer, the DEQ carries an INIT REQ message on the CC_INFO_REQ primitive and delivers it to the called party. When the called party receives the INIT REQ message through CC_INFO_IND, the called party sends the INIT ACK message to the called party. The calling party sends a DN REQ message to the called party and requests a phone number. When the called party receives a DN REQ message, the called party generates a DN RESP message and sends the telephone number to the calling party. This telephone number exchange operation is repeated N-1 times (603).

Subsequently, when the telephone number exchange is completed, the calling terminal transmits an information message of CID = 1 to signal the end of the negotiation process, and when the called terminal receives an information message of CID = 1, the calling terminal returns an information message of CID = 1 and adds it. Inform that the channel is ready for acceptance. At this time, the called terminal stops the called party initial (TAINIT_EXP) timer and starts the called channel addition (TAADD01_EXP) timer (604,605).

When the originating terminal receives the information message with CID = 1, the originating terminal (TCINIT_EXP) timer is stopped, the originating channel addition (TCADD01_EXP) timer is started, and connection to the additional channel is started (606).

Once each additional channel is connected, each terminal stops the channel add (TXADD01) timer. When each channel is ready, the terminating terminal starts a delay equalization (TXDEQ_EXP) timer and uses a frame counter (FC) to measure the relative delay balance between individual channels of Nx56 / 64 kbit / s (607). . In addition, since the incoming call arrival order cannot be guaranteed to be the same as the call establishment order, each terminal uses the received CID to align the channel (607). Each terminal is rearranged, and if the delay is equalized between channels for the call, RI = 1 of the information message is transmitted in all channels of other terminals (608). In each of the modes 2 and 3, when each terminal receives RI = 1 as an information message in all channels, it will consider that call setup is completed, and the delay equalization (TXDEQ_EXP) timer is stopped and user data transmission is started (609, 610).

In operation mode 1, when each terminal receives RI = 1, it will transmit a ready indication for data transmission to A = 0 in all bearer channels. When A = 0 is transmitted, each UE waits for A = 0 reception on each bearer channel. When each terminal receives A = 0 in the bearer channel, it stops transmitting the framing pattern and considers the call setup to be completed. At this time, each terminal will remove the multiframe structure from all channels. In addition, after transmitting RI = 1 and A = 0, if the frame synchronization loss is detected in all bearer channels before the UE receives A = 0, the call setup is considered complete and the multiframe structure is removed from the bearer channel. In modes 2 and 3, each terminal continuously monitors each channel of the call for delay equalization and frame alignment. Each terminal also monitors bit errors between terminals, transmits RI = 1, and stops the delay equalization (TXDEQ_EXP) timer when it detects RI = 1.

On the other hand, when a call is established by multiple combining in this way, each state of the DEQ multiframe control layer and the DEQ negotiation control layer is defined as shown in Tables 2 to 4 below.

Status of the DEQ negotiation control layer (calling party) State name Mark Contents Null state 0 No call exists Call initiation One Calling party sends INIT REQ on the first channel and waits for INIT ACK Initiate-CID1 Wait 1a Waiting for CID = 1 after completing parameter negotiation and DN exchange at the calling party and sending CID = 1 Wait for phone number 2 Calling party waits for receiving after requesting additional DN Additional Channel 3 Status of setting remaining channel after completing parameter negotiation and DN exchange active 8 All channels are set up so that DEQ multiframe can transmit data Active-Delete Initiation 8a Waiting for response after calling party requests channel deletion Active-start 8b-1 Calling party waits for response after requesting channel Active-Additional Channel 8b-2 The originator sets up additional channels after receiving a positive response to the channel part. Active-CID1 Standby 8c The calling party waits for a response after sending CID = 1 as a signal of completion of a channel addition or deletion. Active mode 1 8d Mode 1 is active and information messages are not exchanged and messages are transferred between CC and DEQ MC. Release request 9 Waiting for response after calling party requests release

Status of DEQ negotiation control layer (receive side) State name Mark Contents Null state 0 No call exists Receive call 4 The called party receives the channel connection request INIT Receive 5 Received INIT ACK and received INIT ACK Additional Channel Standby 6 Waiting for setting for the rest of channel after parameter negotiation and DN exchange are completed at called party active 8 All channels are set up so that DEQ multiframe can transmit data Active-Delete Initiation 8a Called party waits for response after requesting channel deletion Active-start 8b-1 The called party waits for a response after requesting channel addition Active-Additional Channel 8b-2 The called party sets up additional channels after receiving a positive response to the channel part. Active-CID1 Standby 8c The called party waits for a response after sending CID = 1 as a signal of completion of a channel addition or deletion. Active mode 1 8d Mode 1 is active and information messages are not exchanged and messages are transferred between CC and DEQ MC. Release request 9 Waiting for response after called party requests to release

DEQ multiframe control layer State name Mark Contents Null state 0 Waiting for channel to be connected to multi-frame function Unknown synchronous search state 0a After the called party is connected to the channel, it is waiting to receive an information message such as multi-frame synchronization or initial channel. Local synchronous standby One The endpoint waits for multiframe synchronization for all channels while sending a multiframe pattern Remote Sync Standby 2 Waiting for the endpoint to be multi-frame synchronized after multi-frame synchronization for all channels is complete Mode 1 Handshake 2a In mode 1, the endpoint is waiting for A = 0 or loss of synchronization after sending RI = 1 or A = 0. All Channel Synchronization 3 Multi-frame synchronization and DEQ equalization completed on all channels Mode 1 active 3a Framing is removed and data is passed in mode 1

In the delay compensation protocol, the channel deletion request primitive is transmitted from the DEQ negotiation control layer side to the DEQ multiframe control layer side, and is for requesting to disconnect the connected channel. The primitive is also used to notify the DEQ multiframe control layer by requesting the number of channels N to use without deleting the channel. For example, if the TXADD01 timer of the DEQ negotiation control layer is stopped or slowed down. This is to specify a new channel identifier and the number of channels when generated. In addition, in mode 3, a new RMULT / SUBMULT for redistributing data without deleting the connected channel may be determined and transmitted to the DEQ multiframe control layer. As shown in FIG. 7, the procedure for transitioning to the next state after proceeding with appropriate primitives and procedures according to the current situation in which the channel deletion primitive is generated is shown.

7 is a flowchart illustrating a flow of processing a channel delete request primitive according to the present invention. 7 is represented using a symbol according to the definition of the SDL diagram.

In step (a), if the channel delete request primitive (CC_DEL_REQ) generated in the DEQ negotiation control layer is received in the DEQ multiframe control layer, the channel delete request primitive (CC_DEL_REQ) is analyzed to delete all channels or only a specific channel. In step (b), the current state of the DEQ multiframe control layer is determined and branched according to the primitive analysis result and the current state.

In step (c), the channel deletion request primitive requests the deletion of all channels, and the current state is the local synchronization state (1), the remote synchronization state (2), the mode 1 hand shake (2a), If channel sync 3 or mode 1 active 3a is deleted, all channels are deleted. It then transitions to the null state in step (g).

In step (d), if the current state is the unchecked sync search state (0a), the requested channel is deleted. In this case, the number of channels requested to be deleted may be all channels or a specific number or one. Thereafter, the transition to the null state of step (g).

In the step (e), the channel deletion request primitive (CC_DEL_REQ) designates the number of channels (N) and channel identifier (CID = x) to be newly connected, and the current state is the remote synchronization standby state (2) or all channels. In the case of the synchronous state (3), the number of alignment frame connection channels is reduced (e2, m = m-1). After that, it is judged whether the channel delay equalization loss occurred while the number of connected channels is reduced (e3), and if the loss occurs, the remote primitive compensation completion flag (RI) is turned off in addition to the confirmation primitive (DEQ_LLOSS_IND). In other words, an information channel message indicating RI = 0 is transmitted (e4). Thereafter, the state transitions to the local synchronization standby state (1) of step (h).

In step (f), if the current state is the local synchronization standby state (1) as a result of the determination of (b), if the received channel with the channel deletion request primitive is received and the channel is deleted (f2), Investigate channel synchronization (f3). If the channel synchronization is not performed, the framing search timer TXFA_EXP of the channel is stopped, and the frame alignment bit A = 1 of the information message is allotted to 1 and transmitted (f4). This indicates that the remote sort is complete. If channel synchronization is performed, the number of aligned frame-linked channels is reduced (f5, m = m-1). After the step (f4) or after the step (f5), the number of channels requested by the channel deletion request primitive (CC_DEL_REQ) ( It is determined whether N) and the number of frame connection channels m currently aligned are the same (f6).

As a result of the determination in (f6), if the required number of channels and the number of frame-linked channels are the same (N = m), the local synchronization designation primitive (CC_LSYNCH_IND) is transmitted to the DEQ negotiation control layer to synchronize and delay local multi-frame of the connected call. Confirm that compensation has been made (f7). Then, perform the remote channel delay compensation procedure to equalize the delay of all channels, and then assign the remote delay compensation complete flag of the information message to ON to send RI = 1 to the DEQ negotiation control layer to indicate that the call setup is completed. f8, f9). Then, after starting the framing delay compensation timer (TXDEQ), the transition to the remote synchronization standby state (2) of the next step (i).

On the other hand, if the requested number of channels and the number of frame-linked channels are not equal (N ≠ m) as a result of the determination of (f6), the state transitions to the local synchronization wait state (1) of (h).

As described above, when the channel deletion request primitive is generated, the present invention analyzes the primitive, grasps the current state, and drives appropriate primitives and procedures to transition to the next state. This is in contrast to a method of receiving a primitive according to the state after the determination of the conventional state and driving the primitive processing routine according to the determined state again, since the present invention classifies the primitive and considers the state thereof. Even when the processing procedures in each state are similar or identical, it is easy to merge the processing procedures and the code size can be reduced to improve the processing speed.

Claims (4)

Delay equalization protocols for multiplexing N channels to provide the required broadband for service and equalizing the delay of the combined channels include a call control layer (CC), a delay equalization negotiation control layer (DEQ NC), and a delay equalization multi In a general information communication network including a frame control layer (DEQ MC), (a) receiving, at the DEQ multiframe control layer, a channel deletion request primitive (CC_DEL_REQ) generated at the DEQ negotiation control layer; (b) analyzing the channel deletion request primitive in the DEQ multiframe control layer, determining a current state, and branching by state according to the contents of the primitive; (c) If, as a result of judgment in b), the channel deletion request primitive requests deletion of all channels, and the current state is the local synchronization synchronization, remote synchronization standby status, mode 1 hand shake, all channel synchronization, and mode 1 active status, Driving a procedure to delete all channels; (d) driving the channel deletion procedure if the current state is an unchecked synchronous search state as a result of the determination of b); (e) As a result of the determination in b), if the channel deletion request primitive specifies the number of channels (N) and the channel identifier (CID = x) and the current state is the remote synchronization standby state and all channel synchronization state, Determining a channel delay equalization after decreasing; (f) if the current state is the local synchronization standby state as a result of the determination of b), deleting the designated channel, examining channel synchronization, and performing channel delay compensation; (g) after step c) or d), transitioning to a null state and ending; (h) after step e), transitioning to a local synchronization standby state and ending; And (i) after the step f), transitioning to the remote synchronization standby state and terminating the channel deletion request primitive processing method according to the delay equalization protocol in the integrated information communication network. The method according to claim 1, wherein if the current state of the DEQ multiframe control layer in step (e) is a remote synchronization standby state or a full channel synchronization state, the delay compensation loss occurs after reducing the number of alignment frame connection channels. And judging, if a loss occurs, transmitting a message (RI = 0) indicating that a delay compensation loss has occurred. According to claim 1, If the current state of the DEQ multi-frame control layer in the step (f) is the local synchronization standby state, f2) deleting the designated channel; f3) checking whether the connected channels are synchronized after deleting the designated channel; f4) if the channel synchronization has not been performed, stopping the framing search timer of the channel and sending the frame alignment bit A = 1, all of the data to 1 to indicate that a remote frame alignment has been obtained; (f5) reducing the number of aligned frame connection channels if channel synchronization has been performed; (f6) after step f4) or f5), determining whether the number of channels requested in the channel deletion request primitive and the number of frame-linked channels currently aligned are the same; (f7) transmitting the local synchronization designating primitive to the DEQ negotiation control layer when the requested number of channels and the number of frame connection channels are the same as the result of determination in f6); (f8) after step f7), driving a channel delay compensation procedure; (f9) after performing channel delay compensation, transmitting a message (RI = 1) indicating that the call setup is completed evenly to the remote channel delay to the DEQ negotiation control layer; (f10) a method of processing a channel deletion request primitive according to a delay equalization protocol in a general information communication network, comprising starting a framing delay compensation timer. 4. The channel according to the delay equalization protocol in the integrated information communication network according to claim 3, wherein if the requested number of channels and the number of frame-linked channels are not the same as the result of the determination in f6), the method comprises transitioning to the step (h). How to handle delete request primitives.