KR970007403B1 - Non-standard default packet 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 packet size among packet random user functions

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

2 is an overall processing flow diagram according to the present invention,

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

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

* Explanation of symbols for main parts of the drawings

101: subsystem in charge of digital subscriber exchange (ASS-I)

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 in charge of packet matching exchange (ASS-P)

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 packet size among packet random user functions.

It can be additionally assigned to subscribers of ISDN packet, but it can be used to deliver data packet with size other than 128 byte set by exchange. By registering and using a service, a service that can adjust a burden of a fee to a subscriber is required according to a communication policy.

Accordingly, the present invention devised to meet the above requirements is an additional function for the subscriber to the whole electronic switch network (ISDN) packet, and delivers the data packet with a size other than l28 bytes set by the switching center. As a function to be used, the size of a packet is charged to the subscriber according to the communication policy by registering it in the exchange within the range of 16 bytes, 32 bytes, 64 bytes, 128 bytes, 512 bytes, and 1024 bytes. An object of the present invention is to provide a method for setting a non-standard default packet size among packet arbitrary user functions that can adjust a burden.

In order to achieve the above object, the present invention provides a method for setting a non-standard default packet size among packet random user functions, which is used when a data packet is to be delivered with a size other than the feature size set in an electronic switch. If the calling party's physical path setup is completed, the calling party's information is accessed from the database to verify the information, and then further preparation is performed to deliver the registered value only if the subscriber is registered with the non-standard default packet size function. A first step of creating an outgoing process on; A second step of requesting the called party physical path establishment by requesting the called party number translation after receiving the called party number translation result after disassembling and verifying the call setup request packet. ; When the called party's 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 packet size function. Creating a process; A fourth 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 fifth step of reassembling the call setup request packet including the non-standard default packet size information by notifying the terminating logical channel allocation result of the called process by notifying the non-standard default packet size for the call setup request packet and then notifying the originating information; A sixth step of verifying the incoming packet according to the incoming packet packet verification request received by the incoming process, reassembling non-standard default packet size information, and putting the result into the incoming packet to notify the result; After receiving and storing outgoing information, when receiving a call reception packet, it disassembles and verifies and reassembles it, transmits the result, transitions to the destination data transmission state, and disassembles and verifies the call connection packet received by the originating process. A seventh step of notifying the result and then transitioning to a source data transmission state; And an eighth step of releasing the link and the physical path if the subscriber requests call release after completing the data transfer.

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. In the drawing, reference numeral 101 denotes a subsystem in charge of digital subscriber exchange (Access Switching Subsystem for ISDN). Is a processor board for controlling the D-channel of the integrated information communication network (ISDN D-channel contro1 Processor board Assembly (hereinafter referred to as IDPA), and "l12" is a processor for digital subscriber matching (ISDN Subscriber Access Processor: 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 "means Access Switching Processor for Packet (hereinafter referred to as ASP-P). P), " 122 " Is a packet handling module (hereinafter referred to as RHM), "123" is a packet layer control processor (Packet Layer Control Rrocessor: PLCP), "l24" is a time switch processor (hereinafter, TSP) '' L03 '' is the Interconnection Network Subsystem (hereinafter referred to as INS), 131 is the processor responsible for the internal network (Interconnection Network Processor (hereinafter referred to as INP), " 132 "is composed of a number translation processor (hereinafter referred to as NTP) and" 104 "is composed of a database (hereinafter referred to as DB).

In addition to the hardware configuration described above, the following software blocks are required for processing the non-standard default packet size setting.

First, a block in charge of digital subscriber packet mode control (hereinafter referred to as DPC) in the ASP-I 113 is a block in charge of digital subscriber matching (Digital Subscriber Interface: in the following). DSI), the TSP 114 has a Time Switch Link (hereinafter referred to as TSL), and the ASP-P 121 has a PIC (Packet) that performs functions such as packet call control / verification and number translation request. Inward-cal1 Control (hereinafter referred to as PIC), PDC (Packet call Direction Control (hereinafter referred to as PDC)), and PHM 122 include a block (B-) that is responsible for performing the link layer and packet layer of the X.25 protocol. channel X.25 protocol Handler: hereinafter referred to as B25H), PLCP 123 is responsible for controlling B-channel packet calls (B-channel Packet Call Control: hereinafter referred to as BPCC), and TSP 124 is a time switch Link (Time Switch Link: hereinafter referred to as TSL), INP (131) is a block for controlling the switch network (Switch Network Control: hereinafter referred to as SNC) In the NTP 132, a block in charge of number translation (Number Transladon: 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 ASP-P 1121 via the DPA of the ISAP 112 and the DPC of the ASP-I 113 via the IDPA 111.

The PIC sets up the calling physical path and notifies the BPCC of the PLCP 123. The BPCC examines the calling party status and subscriber information according to the calling physical path establishment completion notification, and determines whether the originating signal is generated to determine the call setup request packet. 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 the translation of the number and the establishment of the destination physical path to PDC and PIC of the ASP-P 121 (203). Accordingly, PLC requests the establishment of the destination B-channel to the DPC to set up the destination B-channel. do. After the B-channel is set up, the PIC sets up the called-party physical path and informs the BPCC of the setup 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 can be generated, an 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 reassembly of the incoming call packet received at the called party is verified. It transmits to the called B25H (hereinafter referred to as B25Ht) to be worshiped by the called terminal (208).

When a call receipt 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 receipt of the call connection packet verification request through BPCCo, it disassembles, verifies, and reassembles the call connection packet (204), and sends the result to B25Ho. Inform the terminal 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 to read information about the calling party (302), and then checks the corresponding line. It checks whether the subscriber can make a call (303, 306). In this case, when a call request is received while the corresponding line is not mounted, the caller does not generate an outgoing call through the caller's physical path release request (307). It is checked whether the line is prohibited for some reason (308, 309). In this case, when the call is prohibited, the caller does not generate an outgoing call through the caller physical path release request (307). If the access point is normal, the subscriber is registered to verify that the subscriber is registered to the non-standard default packet size function (310,311). After further performing the preparation process for transferring the value to B25Ho (312), the process for generating the originating process (3l3) is performed, and if not registered, the basic data storage for creating the originating process is prepared (313). . Thereafter, when a call setup request is received from the terminal (314), a call process (BPCCo) is generated (315).

When the calling process is established, communication with the B25Ho is made possible by notifying an identification number (ID) generated by the calling 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 is delivered in the correct format (320, 32l). At this time, if the abnormality, the B25Ho call setup request packet flow notification is notified so as to be delivered to the calling subscriber (325), and the caller requests to release the physical path (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. Check (303.306). In this case, when an incoming call request is received in a state where the corresponding line is not mounted, the incoming call generation is not generated through the physical path release request (307). 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 further performing the preparation process for transferring the value to B25Ho (312), the incoming process generation process (316) is performed, and if not registered, immediately prepares for storing basic data for creating the incoming process (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). The BPCCt also requests an incoming link establishment to the destination B25H (hereinafter referred to as B25Ht) for establishing the called party's layer 2 (343). After notifying the destination link establishment result, the BPCCt enters the standby packet verification waiting state (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 packet size, etc., and prepares for notification of the result (331), and the non-standard default packet 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 packet including the non-standard default packet size information is reassembled (351), and the non-standard default packet size information is included in the incoming packet and transmitted to the B25Ho (352).

After receiving the calling party information from the calling party (353) and storing it for use in a function such as billing (354), the call enters the packet verification request wait state. In this case, after the incoming call packet is transmitted, the B25Ht requests verification of the incoming call packet to the BPCCt when receiving the call reception packet as a response from the called terminal (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 content of the packet is normal (360), the verification result is notified (362) after reassembling the call reception packet (361). 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, BPCCo receives the request for verification of the call connection packet from B25Ho, decomposes the call connection packet (334) and verifies the packet after verifying the packet. Notify that the connection is made (336). If the verification result is not normal (337), after notifying the call connection packet error (341), the physical path release request is requested (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 that received the call release) (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), it requests the physical path release 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 for subscribers of an ISDN packet, which is used when a data packet is to be transmitted in a size other than 128 bytes set by an exchange. The size of the subscriber shall be registered and used by the subscriber in the exchange within the range of 16 bytes, 32 bytes, 64 bytes, 1 byte, 512 bytes, and 1024 bytes. This has the effect of making adjustments such as the burden of charges to the subscriber according to the communication policy.

Claims (1)

Packet used to deliver data packets with a size other than the specific size set by the electronic switching center.The method of setting the non-standard default packet size during random user start-up. A first step of accessing the originating subscriber information in 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 packet size function, and then generating the originating process; A second step of requesting a called party physical path setting by requesting a called party number translation result when receiving a called number translation result after disassembling and verifying the call setup request packet when it is transmitted; Once 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 preparations are made to deliver the registered value only if the subscriber is registered with the non-standard default packet size function. Creating a process; A fourth 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 fifth step of reassembling a call setup request packet including non-standard default packet size information by notifying the non-standard default packet size information of the called process by notifying the non-standard default packet size for the call setup request packet and notifying outgoing information; A sixth step of verifying the incoming packet according to the incoming packet packet verification request received by the incoming process, reassembling non-standard default packet size information, and putting the result into the incoming packet to notify the result; After receiving and storing outgoing information, when receiving a call reception packet, it disassembles and verifies and reassembles it, transmits the result, transitions to the destination data transmission state, and disassembles and verifies the call connection packet received by the originating process. A seventh step of notifying the result and then transitioning to a source data transmission state; And an eighth step of releasing the link and the physical path if the subscriber requests the call release after completing the data forwarding.