KR970007402B1 - Non-standard default window size set-up method - Google Patents

Abstract

The present invention relates to a method of setting non-standard default window size of packet random user functions. This method includes the steps of accessing originating subscriber information after setting physical path in response to a subscriber's call request into data base, and generating an originating process; when transmitting a call setting request packet, resolving and inspecting this, and then requesting terminating number translation request; after receiving its result, requesting a terminating physical path setting; accessing the originating subscriber information after completely setting the terminating physical path into the data base process; after producing the terminating process, allocating terminating logic channel allocation and setting terminating layer 2 setting; reassembling the originating process' call setting packet according to the completion of originating preparation and reporting inspection results; when a terminal transmits call receipt packet in response to the terminating call packet transmission, coming into a terminating data transmission state by the inspection of the call connection packet received via the originating process and report thereof; and processing a subscriber's call release request after data transmission.

Description

How to set non-standard default window size among packet random user functions

1 is a configuration diagram of hardware to which the present invention is applied;

2 is an overall flow chart of the present invention,

3 is a detailed flowchart of packet call setup processing according to the present invention;

4 is a detailed flowchart of the release process according to the present invention.

* Explanation of symbols for main parts of the drawings

10l: subsystem in charge of digital subscriber registration exchange (ASS_1)

111: processor board (IDPA) for controlling an integrated information communication network (ISDN) D-channel

112: Processor (ISAP) responsible for digital subscriber registration

113: Processor (ASP_I) in charge of digital subscriber access exchange

114: Time Switch Processor (TSP)

102: subsystem (ASS_P) in charge of packet matching exchange

121: Processor (ASP_P) in charge of packet subscriber access exchange

122: module for packet processing (PHM)

123: processor (PLCP) to control the packet layer

124: time switch processor (TSP)

103: internal network subsystem (INS)

131: processor (INP) in charge of the internal connection network

132: Processor for Number Translation (NTP)

104: database

The present invention relates to a method for setting a non-standard default window size among packet random user functions.

In the current communication environment, performance is improved by shortening the system occupancy time, and additionally is granted to the subscribers of the ISDN packet in order to adjust the burden of the fee according to the communication policy. There is a demand for a method in which a window can be operated with a size other than the set 2, and the size of the window can be registered and used by the subscriber in the switch within the range of 1 to 7.

The present invention devised to meet the above requirements is an additional function for all subscribers to ISDN packet subscribers, which is used to operate a window with a size other than 2 set by the switching center. As a function, the size of the window can be registered and used by the subscriber in the switch within the range of 1 to 7, thereby improving performance by reducing the system occupancy time, and a packet that can adjust the burden of charges to the subscriber according to the communication policy. Its purpose is to provide a nonstandard default window size setting method among arbitrary user functions.

In order to achieve the above object, the present invention provides a method for setting a non-standard default window size among packet random user functions applied to an all-electronic exchange. A first step of further performing a preparation process for delivering the registered value only when the subscriber is registered with the non-standard default window size function after accessing the information and verifying the information; A second step of requesting translation of a called number after disassembling and verifying a call setup request packet when it is transmitted; A third step of preparing for the called-party physical path setting request after receiving the called party number translation result and requesting the called-party physical path setting; After the called party physical path setup is completed, the called party information is accessed from the database to verify the information, and then further preparations are made to deliver the registered values only if the subscriber is registered with the non-standard default window size function. Creating a process; After creating the incoming process, allocating the destination logical channel, notifying the destination logical channel assignment result, and then requesting the destination link setup to receive the destination link establishment result: A sixth step of reassembling a call setup request packet including non-standard default window size information to notify the non-standard default window size for the call setup request packet and then notifying the originating information; A seventh step of verifying the incoming packet according to the incoming packet packet verification request received by the incoming process, reassembling non-standard default window size information, and then notifying the result of the incoming packet in the incoming packet; An eighth step of disassembling, verifying and reassembling the received call reception packet after receiving and storing the calling information, transmitting the result, and transitioning to the called party data transmission state; Step 9: Resolving and verifying the call connection packet received by the originating process, notifying the result, and transitioning to the originating data delivery state; and after completing the data delivery, if the subscriber requests call release, the link and the physical path are disconnected. And a tenth step of releasing.

Hereinafter, with reference to the accompanying drawings will be described an embodiment according to the present invention;

FIG. 1 is a block diagram of hardware to which the present invention is applied, and in the drawing, reference numeral 101 denotes a subsystem in charge of digital subscriber registration exchange (hereinafter referred to as ASS-I) and “lll”. Is a processor board for controlling the D-channel of the ICT network (hereinafter referred to as IDPA), and “112” is a processor for digital subscriber matching (ISDN Subscriber Access Processor: hereinafter referred to as ISAP). "113" is a processor for digital subscriber access exchange (Access Switching Processor for ISDN: hereinafter referred to as ASP_I), "114" is a Time Switch Processor (hereinafter referred to as TSP), "102" "Access Switching Subsystem for Packet Switching (hereinafter referred to as ASS_P)," 121 "is a processor that closes the packet subscriber access exchange (Access Switching Processor for Packet (hereinafter referred to as ASP_P)) "122" contains packet processing A packet handling module (hereinafter referred to as PHM), " 123 " is a processor for controlling the packet layer (hereinafter referred to as a PLC Layer Control Processor (PLC)), and " 124 " , TSP), 103 is an Interconnection Network Subsystem (hereinafter referred to as INS), and "131" is an Interconnection Network Processor (hereinafter referred to as INP), "132" Is a processor in charge of number translation (Number Trans1ation Processor (hereinafter NTP)), "104" is composed of a database (hereinafter DB).

In addition to the above hardware configuration, the software blocks required for the non-standard default window size setting processing are as follows.

First, the ASP_I 113 is a block for digital subscriber packet mode control (hereinafter referred to as DPC), and the ISAP 112 is a block for digital subscriber matching (Digital Subscriber Intertace: below). The TSP 114 has a Time Switch Link (hereinafter referred to as TSL), and the ASP_P 121 has a Packet Inward_call Control (PIC) which performs functions such as packet call control / verification and number translation request. , PIC), PDC (Packet caII Direction Control: PDC), and PHM 122 are blocks (B-channel X.25 protocol handlers) that perform link layer and packet layer execution of the X.25 protocol. (Hereinafter referred to as B25H), the PLCP 123 is responsible for controlling the B-channel packet call (B-channel Packet Call Control: hereinafter referred to as BPCC), and the TSP 124 is a time switch link (Time Switch Link: Hereinafter, referred to as TSL), INP (l31) includes a block for controlling the switch network (Switch Network Control: hereinafter referred to as SNC), NTP In 132, a block in charge of number translation (Number TRanslation: hereinafter referred to as NTR) is mounted.

2 is an overall process flow diagram according to the present invention, which will be described in combination with the first diagram.

When the subscriber requests the call setup, it is notified to the PIC of the ASPP 121 via the IDPA 111 through the DSI of the ISAP 112 and the DPC of the ASP_I 113.

The PlC sets the calling physical path and notifies the BPCC of the PLCP 123, and the BPCC examines the calling party status and subscriber information according to the calling physical path establishment completion notification and determines whether an originating call is generated and then determines whether to make a call. In a waiting state for receiving (201).

When call generation is possible, when a call setup request packet is received from the originating terminal to the originating B25H (hereinafter referred to as B25Ho) of the PHM 122, the call setup request packet verification is requested to the originating BPCC (hereinafter referred to as BPCCo). After disassembly and verification of the call setup request packet, the reassembled result is transmitted to B25Ho (202).

In addition, BPCCo requests number translation and destination side physical path establishment request to PDC and PIC of ASP_P 121 (203). Accordingly, PIC requests destination B-channel establishment to DPC to set up destination B-channel. After the B-channel is set up, the PIC establishes the called-party physical path and informs the BPCC of the completed result, so that the BPCC examines the subscriber status and information to determine whether the call is generated (206).

At this time, when the incoming call generation is possible, the incoming logical channel is allocated (207) and the result is notified to the BPCCo to inform the calling terminal that the call is possible, and the disassembly, reassembly and verification of the incoming call packet received at the called party is performed. A transmission is made to the destination B25H (hereinafter referred to as B25Ht) to be transmitted to the destination terminal (208).

When a call reception packet is received from the called terminal to the called BPCC (hereinafter referred to as BPCCt), the packet is disassembled, verified, and reassembled.

Accordingly, B25Ht transmits the result to B25Ho based on the received call reception packet, and upon receiving the call connection packet verification request from BPCCo, disassembles, verifies, and reassembles the call connection packet (204), and sends the result to B25Ho. The terminal is notified of the result of the call connection. This leads to a packet call connection state.

Detailed flow charts according to the above scheme are the same as those of FIGS. 3 and 4, and the detailed description is as follows.

When the subscriber requests call establishment, when the PIC is notified of the completion of the originating physical path establishment (301), the BPCC accesses the database, reads information on the calling party (302), and then calls through a check on the corresponding line. Check whether the subscriber can be created (303, 306). In this case, when a call request is received in a state in which the corresponding line is not mounted, the caller does not generate an outgoing call through the physical path release request of the calling party (307). It is checked if the line is forbidden for the reason (308, 309). At this time, if prohibited, the caller does not generate an outgoing call through the caller's physical path release request (307), and if it is normal, the subscriber is registered to verify that the subscriber is registered to the non-standard default window size function (310,311). After further performing the preparation process for transferring the value to B25Ho (312), the process for generating the originating process 313 is performed, and if not registered, the basic data storage for the generation of the originating process is prepared (313). . Thereafter, when a call establishment request is received from the terminal (314), an originating process (BPCCo) is generated (315).

When the originating process is generated, communication with the B25Ho is made possible by notifying an identification number (ID) generated by the originating B25H (hereinafter referred to as B25Ho) (318). The BPCCo also decomposes the call setup request packet (319) and checks whether the call setup request packet has been delivered in the correct format (320, 321). At this time, if the abnormality, the B25Ho notifies the call setup request packet error content to be transmitted to the calling subscriber (325) and requests the release of the physical path of the calling party (326) to stop generating the outgoing signal. If the content of the call setup request packet is normal, address verification is performed to determine whether information such as a calling number is received correctly (322, 323). If it is normally delivered, the call forwarding number translation is requested (324). If abnormal, the call setup request packet error is notified to B25Ho to be delivered to the calling subscriber (325). Stop generating call signal.

Upon receiving notification of the called party number translation result (327), a preparation for the called party physical path establishment request (328) is requested (329).

On the other hand, when the called party's physical path is established and notified of the result (304), the subscriber database is accessed to read information about the called party (305), and then a check on the corresponding line is performed to determine whether the subscriber is capable of generating an incoming call. Inspect (303,306). In this case, when an incoming call request is received while the corresponding line is not mounted, the incoming call generation is not generated through the physical path release request (307). When the incoming line is mounted and the incoming call is possible, the subscriber of the corresponding line may be delinquent. It is checked if the line is forbidden for a reason (308, 309). At this time, if prohibited, the originator does not generate an outgoing call through the physical path release request (307), and if it is normal, the subscriber is registered to verify that the subscriber is registered to the non-standard default packet size function (310,311). After performing further preparation process to transfer the value to B25Ho (312), the incoming process generation process (316) is performed, and if not registered, the basic data storage for preparing the incoming process is immediately prepared (316). . Thereafter, an incoming process (hereinafter referred to as BPCCt) is generated (317).

The BPCCt allocates the incoming logical channel (341) and notifies the BPCCo of the incoming logical channel allocation result (342). In addition, the BPCCt requests the establishment of the incoming link to the destination B25H (hereinafter referred to as B25Ht) in order to establish the destination layer 2 (343). After being informed of the result of the incoming link establishment, the BPCCt enters a waiting state for incoming packet packet verification (344).

The BPCCo notified of the result of the incoming logical channel assignment (330) reassembles the call setup request packet including information of the non-standard default window size, etc., and prepares for the notification of the result (331), and the non-standard default window size for the call setup request packet. After notifying to the B25Ho (332) and informs the called party about the calling party (333).

Also, the BPCCt decomposes the incoming call packet according to the incoming call packet verification request received from the B25Ht (345) (346) and checks whether the incoming call packet is delivered in the correct format (347, 348). If the correct packet is not delivered, an incoming call packet error notification is transmitted (349) to reject the incoming call generation and request the physical path release (350). If normal, the incoming call packet including the non-standard default window size information is reassembled (351), and the non-standard default window size information is included in the incoming call packet and transmitted to the B25Ho (352).

After receiving the calling party information from the calling party (353), it enters the call reception packet verification request waiting state after storing (354) for use in a function such as charging. At this time, when the incoming call packet is transmitted, the B25Ht receives a call reception packet as a response from the called terminal and requests verification thereof from the BPCCt (355). Accordingly, the BPCCt decomposes the incoming call packet (356), performs its verification (357, 358), and if an abnormal packet is received, notifies the received packet error (359), and then requests physical path release to generate an incoming call. If the contents of the packet are normal (36l), then the verification result is notified (362). In this case, if the data transmission status is notified from the calling party (363), the called party also transitions to the data delivery status (364).

In addition, after receiving a request for verifying a call access packet from B25Ho, the BPCCo decomposes the call access packet (334), verifies the packet, and then notifies the call connection packet verification result to B25Ho, indicating that the call is connected to the calling terminal. Inform 336. If the verification result is not normal (337), after notifying the call connection packet error (341), it is requested to release the physical path to release the call (342). However, if the verification result is normal (337), after notifying the call connection packet verification result (338), the calling party informs the called party that the data is delivered (339), and then transitions to the data delivery (340). This establishes a call connection state.

If the subscriber requests release to terminate the call after all data has been delivered (401), the BPCC stops the process (the originating or incoming process for which the release was received) (402) and releases the occupying Layer 2 resource. In order to transmit the link release request to the B25H (403), and after receiving the link release result (404), the physical path release request to the PIC (405). Upon notification of completion of physical path release (406), all information related to the link is initialized (407).

As described above, the present invention provides an additional function to the subscribers of the ISDN packet, which is used when the window is operated with a size other than 2 set by the switching center. By allowing the subscriber to register and use in the exchange in the range of 1 to 7, it is possible to improve the performance by reducing the system occupancy time and to adjust the burden of charges to the subscriber according to the communication policy.

Claims (1)

Non-standard default window size setting method among packet random user functions used when operating window with size other than the specific size set by electronic switching center, and when calling party's physical path setting is completed according to subscriber's call request A first step of accessing the subscriber information from the database and verifying the information, further performing preparation for delivering the registered value only if the subscriber is registered with the non-standard default window size function, and then generating an outgoing process; A second step of requesting a called number translation after disassembling and verifying a call setup request packet when it is transmitted; A third step of preparing for the called-party physical path setting request after receiving the called party number translation result and requesting the called-party physical path setting; When the called party's physical path setup is completed, the called party's information is accessed from the database to verify the information, and then further preparation is made to deliver the registered value only if the subscriber is registered with the non-standard default window size function. Creating a process; A fifth step of allocating an incoming logical channel after notifying the incoming logical channel allocation result after generating the incoming process and requesting the incoming link establishment to receive the incoming link establishment result; A sixth step of reassembling the call setup request packet including the non-standard default window size information by notifying the non-standard default window size information of the called process by notifying the non-standard default window size for the call setup request packet when notified of an incoming logical channel allocation result of the incoming process; A seventh step of verifying the incoming call packet according to the incoming call packet verification request received by the incoming process, reassembling non-standard default window size information, and notifying the result by putting the result in the incoming call packet; An eighth step of disassembling, verifying and reassembling the received call reception packet after receiving and storing the calling information, transmitting the result, and transitioning to the called party's data transfer state; A ninth step of disassembling and verifying the call connection packet received by the originating process, notifying the result, and transitioning to the originating data transmission state; And a tenth step of releasing the link and the physical path if the subscriber requests the call release after completing the data transfer.