KR100259768B1 - Method of service process using point-to-point protocol and multilink protocol in the distributed environment - Google Patents

Abstract

PURPOSE: A services processing method using point-to-point protocol and multilink protocol in distributed node environment is provided which divides the protocol function into two separate real-time operation system nodes to allow ISDN to perform multilink protocol header processing, bundle table management, recombination and sequencing of packets and to allow WNAS to carry out link control protocol processing and bundle table management. CONSTITUTION: An ISDN access subsystem receives data from a subscriber to form a packet from the subscriber data and transmits the packet to a webinfoshop network access subsystem (WNAS) using interprocessor communication primitive. The WNAS receives Internet protocol data using the communication primitive to check the message identification information field of the received packet and transmits multilink protocol or point-to-point protocol frame to the subscriber from the received packet.

Description

Service Processing Method using Point-to-Point Protocol and Multilink Protocol in Distributed Node Environment

The present invention relates to a message transmission and reception task using a point-to-point protocol and a multilink protocol and a method of connecting and releasing a multilink call to a broadband network subscriber to provide a high-speed Internet connection service. .

The Point-to-Point Protocol (hereinafter referred to as "PPP") to provide a standard for transporting multiprotocol datagrams over point-to-point links is initially referred to as various hosts, bridges, and routers. It has only been applied to one node.

That is, it is a point-to-point protocol for simple links that transmit packets between two peers, which can provide full-duplex transmission and deliver packets with guaranteed order integrity. The point-to-point protocol consists of three main components: how to encapsulate multiprotocol datagrams, and the Link Control Protocol (hereinafter referred to as "LCP") to establish, manage, and test data link connections. The Network Control Protocol (hereinafter referred to as "NCP") function for establishing and managing other network layer protocols.

Another approach is similar to the multilink protocol described in ISO 7776, but with the additional ability to split and recombine packets, reduce latency, and effectively increase the maximum receive unit (hereinafter referred to as "MRU"). Provide the function. Moreover, there is no requirement for acknowledgment mode operation at the link level and is only allowed selectively. Multiple links are based on the LCP option negotiation and the system is to inform the isosystem that multiple physical links can be bundled.

A telephone network subscriber is included in the Webinfoshop Network Access Subsystem (hereinafter referred to as "WNAS") of the Advanced Communications Processing System (hereinafter referred to as "ACPS"), which is a system to which the present invention is applied. Pure point-to-point protocol functionality has already been implemented to provide Internet services to users.

Therefore, in order to provide 128 Kbps Internet connection service to subscribers in Integrated Services Digital Network (hereinafter referred to as "ISDN") basic speed (BRI) circuit switched mode, multilink control without changing the shape of WNAS There was a problem that only the protocol functionality had to be implemented in the ISDN matching subsystem.

Accordingly, the present invention has been made to solve the problems of the prior art as described above, by separating the protocol function into two separate real-time operating system nodes ISDN Network Access Subsystem ( Hereinafter referred to as "INAS" performs multilink protocol header processing, bundle table management, recombination and ordering of packets, and WNAS performs a point-to-point protocol and a distributed node environment in which link control protocol processing and bundle table management are performed. The object of the present invention is to provide a message transmission and reception task using a multilink protocol and a method of connecting and releasing a multilink call.

1 is an exemplary configuration diagram of a mass communication processing system to which the present invention is applied.

2 is an exemplary configuration diagram of an ISDN matching subsystem to which the present invention is applied.

3 is a schematic diagram for explaining a link control protocol and a multilink control protocol to which the present invention is applied;

4 is an exemplary configuration diagram of a bundle management table applied to the present invention.

5A and 5B are exemplary views of a configuration of a protocol data unit for interprocessor communication applied to the present invention.

6A and 6B are a flowchart illustrating one embodiment of a message transmission and reception task method according to the present invention;

7A and 7B are flow diagrams of one embodiment of a multilink call connection and call release method according to the present invention;

* Explanation of symbols for main parts of the drawings

101: public switched telephone network 102: integrated information network

103: mass communication processing system 104: telephone network matching subsystem

105: integrated information network matching subsystem 106: high-speed switching structure

109: packet network matching subsystem 110: web infoshop node matching subsystem

111: frame network matching subsystem 112: ATM network matching subsystem

In order to achieve the above object, the present invention provides a message transmission / reception task method using a point-to-point protocol and a multilink protocol in a distributed node environment, wherein the integrated information network matching subsystem receives data from a subscriber and creates a packet from the subscriber data. Sending a packet to the webinfo shop node matching subsystem using an internal interprocessor communication primitive; And the webinfo shop node matching subsystem receives internet protocol data using an interprocessor communication primitive, inspects a message identification field of a received packet, and transmits a multilink protocol or a point-to-point protocol frame from the received packet to a subscriber. A second step is included.

In addition, the present invention for achieving the above object, in a multi-link call connection and disconnection method using a point-to-point protocol and a multi-link protocol in a distributed node environment, the data channel call is connected and the integrated information network network matching subsystem is Web Transmitting a data on at least one channel by transmitting an internal connection request to an infoshop node matching subsystem and performing a link establishment and authentication procedure for the data channel; And when the link release procedure for the data channel between the subscriber and the webinfo shop node matching subsystem is performed, the integrated information network matching subsystem receives a disconnection from the webinfo shop node matching subsystem to call the data channel connection. It includes a second step of releasing.

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

1 is an exemplary configuration diagram of an Advanced Communications Processing System (ACPS) to which the present invention is applied.

As shown in the figure, a large capacity communication processing system (ACPS) 103 is a public switched telephone network 101, an ISDN 102, a packet switched data network 113, the Internet 114, a frame relay network 115, asynchronous Accepts connections, such as delivery mode (ATM) network 116. The High Speed Switching Fabric (hereinafter referred to as "HSSF") 106 is a high speed connection between the various network matching subsystems constituting the ACPS, the service support subsystem and the communication processing subsystem. And it provides the function of the internal high speed interconnection network in charge of transport of service traffic.

The network matching subsystem interworking with the subscriber side includes a telephone network matching subsystem (TNAS) 101 and an ISDN matching subsystem (INAS) 102. The network matching device interworking with the information provider side includes a packet network matching subsystem (Packet). Network Access Subsystem (hereinafter referred to as "PNAS") 109, Webinfoshop Network Access Subsystem (hereinafter referred to as "WNAS") 110, Frame Network Matching Subsystem (Frame Network) Access Subsystem (hereinafter referred to as "FNAS") 111, and Asynchronous Network Mode Subsystem (ATM Network Access Subsystem) (hereinafter referred to as "ANAS") 112 and the like.

FIG. 2 is an exemplary configuration diagram of an ISDN matching subsystem to which the present invention is applied. FIG. 2 shows an ISDN matching subsystem (INAS) for providing various communication services of a mass communication processing system to a user connected to an ISDN. It is a block diagram.

The Integrated Services Network Matching Subsystem (INAS) 201 is a Primary Rate Interface Assembly (hereinafter referred to as "PRIA") module 203, HSSF, for interfacing with an Integrated Services Network (ISDN). It consists of a High Speed Network Assembly (hereinafter referred to as "HSNA") module 205 for interfacing with a service processing (SP) module for controlling them and processing services. The service processing module is an ISDN Data Processing Assembly (hereinafter referred to as "IDPA") module that handles functions such as subscriber ISDN modem speed determination, ISDN modem error detection, subscriber information transmission, reception, initialization and self-diagnosis. 202 and an ISDN Service Processing Assembly (hereinafter referred to as "ISPA") module 204 that is responsible for service processing and control. The ISDN service processing assembly (ISPA) module 204 uses Interprocesser Communications (IPC) for data communication with the IDPA module 202 and transmits data in an interrupt manner through common memory. The processor for IPC communication communicates with three IDPA modules via a serial communication bus, respectively. The IDPA module 202 consists of one main and two slaves. The main of the IDPA module 202 transmits and receives data in serial communication between the slave and the ISPA module 204. Monitor the PRIA module 203 through the alarm port. Application programs performed on the IDPA module 202 board are largely divided into master and slave modules. The master module performs a function of connecting communication between the slave module and the ISPA module 204, while the slave module transfers data received from the subscriber through the network interface module to the ISPA module 204 through the master module or the ISPA module ( It transmits the data received from the 204 to the subscriber, and performs functions such as PAD processing, subscriber channel monitoring.

3 is a schematic diagram illustrating a link control protocol and a multilink control protocol to which the present invention is applied.

ACPS's WNAS already implements the Link Control Protocol (LCP) 306 and 307 functions in a pure point-to-point protocol to provide Internet services to telephone network subscribers.

Therefore, in order to provide 128 Kbps Internet connection service to subscribers in ISDN Basic Rate Interface (BRI) circuit switched mode, only the multilink control protocol (MLCP) 305 function needs to be implemented in INAS without changing the shape of WNAS.

INAS performs multilink protocol (MP) header processing, bundle table management, packet reassembly and ordering, etc., while WNAS performs link control protocol (LCP) 306, 307 processing and bundle table management. .

4 is an exemplary configuration diagram of a bundle management table applied to the present invention.

As shown in the figure, in order to distinguish a link connection from a frame, a relationship between a B channel ID and a master logical channel unit number (hereinafter, referred to as "LUN") was defined. In terms of receiving messages, the channel task allocates a unique master LUN for all links in the same bundle. That is, the same master LUN is allocated for all frames encapsulated by the network layer packet transmitted by the sibling system. In terms of message transmission, frames are alternately transmitted using multiple links with the same master LUN.

Therefore, the receiving side requires a table for mapping a plurality of links to the master LUN. The bundle management table includes a destination call number 401, a multilink flag 402, a multilink state 403, a logical channel unit number (LUN) state 404, a next channel 405, and a data sequence number on receipt (406). ), A data sequence number 407 at the time of transmission, a multilink option 408, and the like. The multilink option 408 includes a Max Receive Reconstructed Unit (MRRU) 409, a Protocol Field Compression (PFC) 410, an Address and Control Field Compression (ACFC). (411), Sequence Number Header Format (SNHF) 412, and the like.

Whenever an ISDN call connection is requested, the channel task searches the bundle management table with an index of pairs of <destination call number, multilink flag>. If a <same destination call number, MLPPP> pair exists in the bundle table, the channel task changes the object in the bundle table for the master LUN, and the <destination call number, multilink flag>, multilink state, for the new slave LUN. Inserts the LUN status, next channel, and multilink options as slaves into the table. If not, the channel task inserts an object in the table for the new master LUN, with the LUN status set to MASTER.

5A and 5B are exemplary views of the configuration of a protocol data unit for interprocessor communication according to the present invention.

In particular, FIG. 5A is an exemplary configuration diagram of a data protocol data unit, wherein an internal processor-to-processor protocol data unit (PDU) includes a fixed length header part and a variable length user data part. The PDU is for user data transmission and control information transmission. The data PDU includes protocol and message type fields to distinguish the type of data, and the control PDU is used to establish or release a connection. As a result, the parameters used may vary, so they contain variable parameter fields.

In particular, FIG. 5B is an exemplary configuration diagram of a control protocol data unit. The control PDU includes fields for transmitting various parameters such as an address of a source or a destination, status information, message information, and the like. Also, considering the efficiency of PDU processing, the head lengths of the data PDU and the control PDU are the same.

6A and 6B are flowcharts illustrating an embodiment of a message transmission and reception task method according to the present invention.

In particular, FIG. 6A is a flowchart of a message receiving task method, in which the message receiving task first obtains a LUN corresponding to a channel number (601). The subscriber-sent data is received from the reception data queue using the system call kc_qpend of the INAS real-time kernel (IRTK) (602). A master LUN corresponding to the channel number is obtained from the bundle management table (603), and a transmission packet is created using the subscriber data (604). A transmission packet is transmitted to the WNAS by using hssf_data_send, which is one of primitives for interprocessor communication between the INAS and the WNAS (605). The information on the bundle management table determines whether the bundle state is a single link (single link mode) or a multilink (multiple link mode) (606). If the bundle status is single link, the LUN number is not changed. If the bundle status is multilink, the LUN of the next channel belonging to the same bundle is obtained (607). In other words, there are multiple links on the same bundle, so there are a number of LUNs between INAS and WNAS, and data transfer between the two systems is alternately made using multiple LUNs.

In particular, FIG. 6B is a flowchart of a message transmission task method in which the message transmission task first obtains a LUN corresponding to a channel number (701). Internet protocol data is received from the WNAS using the primitive hssf_data_recv for internal interprocessor communication between the INAS and the WNAS (702). The message ID field of the received packet is checked (703) and the corresponding function is performed for each type. If it is determined whether the message ID field is data to be transmitted to the subscriber (704), data information is extracted from the received packet, and a packet frame is created by adding header information corresponding to the multilink protocol (MP) or the point-to-point protocol (PPP). In operation 705, the INAS real-time kernel system call kc_sendsig is alternately transmitted to the subscriber side on a plurality of links belonging to the same bundle (706).

On the other hand, it is determined whether the message ID field is data to be transmitted to the subscriber (704). If it is not data to be transmitted to the subscriber, it is determined whether the message ID field is communication between multilink processors (707). If it is interprocessor communication, the bundle management table is updated (708).

On the other hand, the message transmission related tasks consisted of five types of tasks: an IDPA reception task, an IDPA reception command controller, a channel task, a message transmission task, and a reception task.

First, the IDPA Receive task checks for IDPA initialization from the data send task on the IDPA board, checks for periodic management (PM) requests, sends X.3 pad recalls, reports DCD status, checks for board alive, data It receives and processes signals such as transmit, interrupt, and reset, and posts them to the DPA receive command queue and DPA receive data queue according to the signal type. In addition, the IDPA Receive task manages memory blocks to store data.

The IDPA Receive Instruction Controller also holds an IDPA Receive Instruction Queue to process signals and return instruction memory parts. The channel task is generated whenever a channel occupancy signal is reported from the primary rate interface board assembly receiving controller. The channel task creates or removes a message receiving task and a message sending task as the subscriber call connection is established or released.

7A and 7B are a flowchart illustrating an embodiment of a method for connecting and releasing a multilink call according to the present invention.

The channel task performs the function of establishing, releasing, and maintaining link connections to the link control protocol (LCP) and multilink protocol (MLCP) layers. The bundle management table manages all link connection information and maintains relationships between multiple links.

In particular, FIG. 7A is a flow diagram of a multilink call connection, performing B channel call connection (801) and searching the bundle management table (802). Thereafter, the UE sends an internal connection request to the WNAS, receives a response according to the request (803), establishes a link on the B channel between the subscriber and the WNAS, and performs an authentication procedure (804).

Subsequently, the multi-link state is received from the WNAS (805), the multi-link mode is determined (806), and in the multi-link mode, the bundle management table is updated (807), and data is transmitted on one B channel (808). If not in the link mode, the bundle management table is updated (809) and data is transmitted on two B channels (810).

In other words, after the ISDN call setup step, the application on INAS acquires one LUN as the call reference point to open the communication channel. The application then searches the bundle management table to determine whether this call is in point-to-point or multilink protocol mode. When the connection request packet (CONN_REQ) is sent by the INAS driver to the WNAS driver to request a call, the WNAS driver allocates a LUN to a higher application and sends a connection confirmation packet (CONN_CNF) to the INAS driver. Once the connection is established successfully, a channel is available that can transmit information in both directions. In order to establish communication on the point-to-point link, first, the subscriber station of the WNAS and the point-to-point protocol link transmits a link control protocol packet to configure and test the data link, and the peer performs an authentication procedure. The point-to-point protocol then transmits a network control protocol (NCP) packet to select and configure one or more network layer protocols. Once the selected network layer protocols are configured, an MP_IPC packet is received at the INAS driver to update the bundle table, and datagrams from each network layer protocol can be sent over the link. If the MP_IPC packet received in multilink mode is not in multilink mode, the bundle management table is updated to a single link, and data is transmitted on one B channel. In the multilink mode due to the second B channel call connection, the bundle management table is updated to the multilink, and data is transmitted on the B channels consisting of two bundles.

In particular, FIG. 7B is a flow diagram of a multilink call release in which the link remains connected for communication until LCP or NCP packets release the link, or an external event such as an inactivity timer or an network management operation occurs. The data is transmitted on two channels (901).

Thereafter, the LCP releases the connection through the exchange of end packets to perform a link release procedure for the B channel between the subscriber and the WNAS (902). After the exchange of end packets, the application sends a signal to the driver to release the call, and the WNAS driver sends a release request packet (CLR_REQ) to the INAS driver, which releases the LUN allocation and release acknowledgment packet (CLR_CNF). Is transmitted to the WNAS (903).

Thereafter, it is determined whether the received packet is in the multi-link mode (904). If the received packet is in the multi-link mode, the bundle management table is updated to the single-link mode (905). The application releases the B channel through the network, and In order to release the call reference information, each UE is notified. When the B channel call is released, data is transmitted on one B channel (906). In order to release another link belonging to the same bundle, a procedure of disconnection procedure 902 for the B channel between the subscriber and the WNAS and internal disconnection reception and acknowledgment transmission 903 from the WNAS is performed.

On the other hand, it is determined whether the received packet is in the multi-link mode (904), if not in the multi-link mode due to the release of the link on the second B channel, and updates the bundle management table to the link NULL state (908), and releases the B channel call ( 909).

Meanwhile, Table 1 below shows signal types for multilink call processing in a transmission service.

On the other hand, the transport service consists of three main operations: connection establishment, data transmission, and disconnection. First, in the connection establishment phase, various parameters related to the connection are negotiated between the two transmitting entities and one-to-one connection is established in the confirmed mode. Once the connection is established successfully, the data transmission phase sends and receives user data streams based on the negotiated parameters. Finally, in the disconnect phase, one-to-one connection is established.

The dialogue mode between the two transmitting and receiving entities (dialogue mode) is a full duplex mode (user can transmit and receive bidirectional transmission on the transmission connection). In this transmission mode, both subsystems can send and receive data at the same time.

Meanwhile, the proposed method is performed separately between INAS and WNAS.

First, multilink is established at the time of initial LCP option negotiation. One system notifies the other peer system of the multilink operation by sending the multilink option as part of the initial LCP option negotiation. In order to establish communication on the point-to-point link, the WNAS first transmits and receives LCP packets for establishing a data link with the subscriber station at the link establishment stage. After the link is established, PPP provides an authentication step that uses an authentication protocol to verify the identity associated with each system connected to the link.

Thereafter, the WNAS transmits an NCP packet to the subscriber station in order to select and configure a network layer protocol. WNAS can combine multiple physical links into one logical link.

Thereafter, once the multilink is successfully negotiated, the INAS may send an encapsulated and decomposed PDU with the multilink header. The INAS may receive the decomposed upper layer PDUs using the multilink header and reassemble the original PDU.

The INAS may then receive PDUs of the specified size as part of the option, even if the PDUs are larger than the MRU for one physical link.

The established link is then open for communication until the LCP or NCP packet releases the link, or until there is an inactivity timer or network management control.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the spirit of the present invention for those skilled in the art to which the present invention pertains, and the above-described embodiments and accompanying It is not limited to the drawing.

Therefore, as described above, in the present invention, the INAS performs multilink protocol header processing, bundle table management, packet reassembly and ordering, etc., while the WNAS performs link control protocol processing and bundle table management, It is possible to provide broadband subscribers with high-speed internet connection services, which can ultimately activate the information society.

Claims (6)

In the method for transmitting and receiving a message in a distributed node environment, The integrated information network matching subsystem includes a first step of receiving data from a subscriber, creating a packet from the subscriber data, and transmitting the packet to the webinfo shop node matching subsystem using an interprocessor communication primitive; And The webinfo shop node matching subsystem receives internet protocol data using an internal interprocessor communication primitive, inspects a message identification field of a received packet, and transmits the multilink protocol or the point-to-point protocol frame from the received packet to a subscriber. 2nd step Message transmission and reception task method using a point-to-point protocol and a multilink protocol in a distributed node environment including a. The method of claim 1, The first step is, A third step of obtaining a logical channel unit number corresponding to the channel number and receiving subscriber data from a receive data queue using a comprehensive information network real-time kernel system call; A fourth step of obtaining a master logical channel unit number of a channel from a bundle management table, creating a transmission packet from subscriber data, and transmitting the transmission packet using an internal interprocessor communication primitive; And A fifth step of obtaining a logical channel unit number of the next order channel from the same bundle when the received packet is in multi-mode Message transmission and reception task method using a point-to-point protocol and a multilink protocol in a distributed node environment comprising a. The method according to claim 1 or 2, The second step, A sixth step of obtaining a logical channel unit number corresponding to the channel number, receiving Internet protocol data using an internal interprocessor communication primitive, and checking message identification information of a received packet; A seventh step of creating the multi-link protocol or the point-to-point protocol frame from a received packet; And An eighth step of alternating transmission on the same bundle links using the ICT matching subsystem real-time kernel system call to send the multi-link protocol or the point-to-point protocol frame to a subscriber; Message transmission and reception task method using a point-to-point protocol and a multilink protocol in a distributed node environment comprising a. In the method of connecting and disconnecting multilink calls in a distributed node environment, A data channel call connection is performed and the integrated information network matching subsystem transmits an internal connection request to the webinfo shop node matching subsystem and performs link establishment and authentication procedures for the data channel to transmit data on at least one channel. First step; And If the link release procedure for the data channel between the subscriber and the webinfo node matching subsystem is performed, the integrated network matching subsystem receives a disconnection from the webinfo node matching subsystem and receives a call of the data channel connection. 2nd step to release Call connection and release method using a point-to-point protocol and a multilink protocol in a distributed node environment including a. The method of claim 4, wherein The first step is, Connecting a data channel call and searching a bundle management table to receive an internal connection request and a response corresponding to the request to the webinfo shop node matching subsystem; Performing a link establishment and authentication procedure for a data channel between a subscriber and the webinfo shop node matching subsystem, receiving a multilink state from the webinfo shop node matching subsystem, and determining whether to be in a multilink mode; A fifth step of updating the bundle management table and transmitting data on one channel in the multi-link mode; And A sixth step of updating the bundle management table and transmitting data on two channels when the link mode is not in the multilink mode; Call connection and release method using a point-to-point protocol and a multilink protocol in a distributed node environment including a. The method according to claim 4 or 5, The second step, A seventh step of performing a link release procedure for a data channel between a subscriber and the webinfo shop node matching subsystem; An eighth step of receiving an internal disconnection from the webinfo shop node matching subsystem and determining whether it is in a multilink mode; A ninth step of updating the bundle management table, releasing a data channel call and transmitting data on one data channel in a multilink mode; And A tenth step of updating the bundle management table and releasing a data channel call when not in a multilink mode Call connection and release method using a point-to-point protocol and a multilink protocol in a distributed node environment including a.

Images