KR19990002611A - Bearer channel connection and disconnection method using ISUP - Google Patents

Abstract

The present invention provides an AIN service switching point to provide resources such as announcement broadcasting, DTMF collection, voice synthesis, voice recording, and fax transmission and reception required for providing next generation intelligent network services in an intelligent information providing system (AIN IP), which is a next-generation intelligent network element. A method of disconnecting a bearer channel between an SSP and an AIN IP by using an ISUP signaling method, wherein the user part control unit (UPC) of an existing ISDN exchange processing ISUP is a protocol processing unit. The ISUP control unit is divided into a basic resource service control unit (BRSC) and a special resource service control unit (SRSC), which are resource control units, and through these blocks, an ISUP message is transmitted between a bearer channel connected between an AIN SSP and an AIN IP and a special resource channel provided by the AIN IP. By providing a procedure to disconnect from the network, a network element for providing special resources such as AIN IP. If the switch node, or the information provider to control the bearer channel to the exchange via the ISUP has an application that can effect.

Description

Bearer channel connection and disconnection method using ISUP

The present invention relates to a bearer channel connection and release method using an integrated service digital network user part (hereinafter referred to as an ISUP) in an intelligent information providing system (hereinafter referred to as AIN).

Conventionally, ISUP has been used mainly in exchanges such as TDX-10 ISDN exchanges and TDX-10 enhanced exchanges in a limited signaling manner in order to connect bearer channels during an exchange.

The bearer channel, which is connected and disconnected by ISUP, is for ISDN user calls and incoming calls.

Therefore, detailed functions of ISUP are divided into ISUP incoming call processing, relay call processing, and outgoing call processing.

In case of an incoming call, after translating the number internally, it plays a role of connecting and releasing the call channel between the called subscriber channel and the incoming line through the time switch, and generates an ISUP message to interface with other stations.

However, the ISUP incoming call processing function, which should be developed in the next-generation intelligent information providing system (Advanced Intelligent Network Intelligent Peripheral, hereinafter referred to as AIN IP), needs to connect the channel between the incoming bearer channel and the special resource channel. The developed ISUP function had some problems that need to be corrected.

In order to solve the above problem, the present invention is to modify the incoming call processing function among the three detailed functions of the ISUP in the incoming bearer channel and the AIN IP connected to the AIN Service Switching Point (hereinafter referred to as AIN SSP). Its purpose is to provide a procedure for establishing and releasing an existing special resource channel.

1 is an AIN IP internal block diagram related to a bearer channel connection between an AIN IP and an AIN SSP to which the present invention is applied.

2A to 2C are flowcharts of a connection operation between an incoming bearer channel and a special resource channel of an AIN IP to which the present invention is applied;

3 is a flowchart illustrating a disconnection operation of an AIN IP by requesting disconnection from an AIN SSP according to the present invention.

4 is a flowchart illustrating a connection release operation of an AIN IP by a connection release request in the AIN IP itself according to the present invention.

5 is a flowchart illustrating a connection release operation of an AIN IP by a dialog release instruction from an AIN SCP according to the present invention;

* Explanation of symbols for the main parts of the drawings *

10: ISDN user part control unit (ISUPC) 20: service control unit

21: basic resource service control unit (BRSC)

22: special resource service control unit (SRSC)

30: IN application protocol (INAP)

40: local switching library (LSL) 50: time switch (TSW)

60: Announcement Broadcaster (ANM) 70: DTMF Digit Collector (DDC)

80: voice recognition unit (SRECOG) 90: voice recording unit (VRECORD)

100: speech synthesis unit (SSYN) 110: FAX processing (FPROC)

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

1 is an AIN IP internal block diagram related to a bearer channel connection between an AIN IP and an AIN SSP to which the present invention is applied, and controls a bearer channel using an AIN SSP and an ISUP signaling scheme, and transmits a special resource to an AIN SSP. Can provide functionality.

This configuration is largely comprised of a protocol processing unit, a service control unit, a time switch unit, and a resource control unit.

The protocol processor is divided into an ISUP control unit (ISDN User Part Control, hereinafter referred to as ISUPC) 10 and an IN application protocol (hereinafter referred to as INAP) 30, and a service control unit. 20 is divided into a basic resource service control (hereinafter referred to as BRSC) 21 and a specialized resource service control (hereinafter referred to as SRSC) 22, and the time switch unit is a time switch. (Time Switch, hereinafter referred to as TSW) 50, and Local Switch Library (hereinafter referred to as LSL) 40.

The resource control unit includes an announcement unit 60, a DTMF digit collection unit (hereinafter referred to as DDC) 70, a speech recognition unit (hereinafter referred to as SRECOG) 80, and a voice recording unit. (Voice Recoding, hereinafter referred to as VRECORD) 90, Speech Synthesis (hereinafter referred to as SSYN) 100, and Fax Processing (hereinafter referred to as FPROC) 110. FIG.

The ISUPC 10 interprets the ISUP message delivered from the AIN SSP, and notifies the BRSC 21 of the ISUP message.

When receiving a response from the BRSC 21, a protocol processing function such as generating a corresponding response ISUP message and delivering it to the AIN SSP is performed.

In addition, if there is a continuity test request from the AIN SSP before the bearer channel connection, the ISUPC 10 directly instructs the LSL 40 to connect the channel.

The BRSC 21 interfaces with the ISUPC 10 and the INAP 30, receives an incoming bearer channel, an announcement 60, and a DTMF Digit Collection (hereinafter referred to as DDC) 70 The LSL 40 instructs a procedure of connecting a call path between the basic resource channels provided by the TSW 50.

The SRSC 22 performs the procedure of connecting a call path through the TSW 50 between the incoming bearer channel and the special resource channels provided by the SRECOG 80, the VRECORD 90, the SSTN, and the FPROC 110. Instruct 40.

The LSL 40 receives the originating and incoming T switch connection request from the BRSC 21 and the SRSC 22, examines the corresponding switch information data, and then instructs the TSW 50 to connect the incoming bearer channel and the resource channel. .

The TSW 50 connects the incoming / outgoing T switch with the corresponding channel according to the request of the LSL 40.

The ANM 60 provides the announcement broadcast resources, and the DDC 70 is a block for collecting DTMF digits, and these two blocks are driven by the instruction of the BRSC 21.

The SRECOG 80 provides a voice recognition resource, VRECORD 90 provides a voice recording resource, Speech Synthesis (hereinafter referred to as SSYN) 100 provides a voice synthesis resource, fax processing (Fax Processing, hereinafter referred to as FPROC) 110 provides a fax transmission and reception resource.

These four blocks are driven by the instruction of the SRSC 22.

The operation and flow of the present invention configured as described above will be described below with reference to the accompanying drawings.

2A to 2C are flowcharts of a connection operation between an incoming bearer channel and a special resource channel of an AIN IP to which the present invention is applied, and is an example for examining a bearer connection operation according to the configuration of FIG. 1.

2A to 2C are flowcharts of a connection operation between an incoming bearer channel of an AIN IP and a resource channel when an initial address message (hereinafter referred to as IAM) requesting bearer channel connection among ISUP messages is received from an AIN SSP. .

First, the IAM message transmitted from the AIN SSP is input to the ISUPC 10 block after the message transfer part (hereinafter referred to as MTP) processing (S1).

After the ISUPC 10 interprets the IAM message, a child processor is generated for each correlation ID in the IAM message (S2). Subsequently, the ISUPC 10 controls the operation in the ISUPC 10 block.

In addition, if the test request is determined by determining the continuity test request in the IAM message (S3), the generated child processor instructs the LSL 40 to connect the incoming channel (S4), and waits for the Continue message to be input (S5). ).

If the continuous message is input (S6), the LSL 40 instructs the incoming channel connection release (S7).

After the instruction, the ISUPC 10 requests the BRSC 21 to connect the incoming bearer channel and resources (S8).

The request message has a correlation ID, incoming bearer channel ID, and AIN SCP address parameters.

The BRSC 21 searches the database DB to check whether there is a channel that can be provided to the user among resource channels, that is, channels allocated to each resource block 7, 8, 9, 10, 11, 12 (S9). .

At this time, if a certain channel or more is being used to reduce the load of each resource block, it may be determined that the channel no longer exists.

If it is possible to provide the resource (S10), and if the resource is available, the ISUPC 10 notifies that the resource connection is possible (S11), and generates a child processor for managing the bearer channel for each correlation ID (S12), The incoming incoming bearer channel ID is mapped together with the correlation ID (S13).

The ISUPC 10 receives the notification that the resource connection is possible, generates an Address Complete (ACM) message to be transmitted to the AIN SSP, and transmits it to the MTP (S14).

The ACM ISUP message informs the AIN SSP that all destination address information for bearer connection has been received.

However, if the resource is not available, the BRSC 21 notifies the ISUPC 10 that the resource is not available (S15).

The ISUPC 10 sends a release message to the MTP to notify the incoming channel connection establishment failure (S16).

After transmission, the terminal is in a release complete wait state (S17), and after receiving the RLC message from the MTP (S18), the process ends (S19).

When the resource is available, the child processor generated by the BRSC 21 instructs the TSW 50 to connect the originating time switch and the incoming bearer channel through the LSL 40 (S20).

The destination address used in this AIN IP is a resource channel and is not carried in the IAM message.

Therefore, the BRSC 21 requests the incoming resource channel information to the AIN SCP to obtain the incoming resource channel information.

To do this, the BRSC 21 instructs the INAP 30 to transmit an Assist Request Instruction (ARI) operation (S21).

The INAP 30 generates an ARI INAP operation, sends it to the AIN SCP, and enters an INAP operation reception state from the AIN SCP (S22).

In the operation reception waiting state S22, an operation for requesting resource provision of the AIN IP is received from the AIN SCP (S23).

Operations requiring resource provision include an announcement broadcast resource request, a user interaction resource request, a voice synthesis resource request, a voice recognition resource request, a voice recording resource request, and a FAX transmission resource request operation.

The BRSC 21 determines whether the requested resource can be provided in the corresponding block (S24). If it is not able to provide the request, the BRSC 21 instructs the INAP 30 to inform that the resource cannot be provided (S25), and the INAP 30 indicates each resource. The message that the resource cannot be provided is sent to the response operation corresponding to the request to the AIN SCP (S26), and the operation is awaiting reception from the AIN SCP (S27).

However, if the resource can be provided, it is determined whether the resource to be provided is a resource controlled by the BRSC 21 or a resource controlled by the SRSC 22 (S28).

If it is determined that the resource is supported by the BRSC 21, the BRSC 21 connects the destination side time switch with the channel connectable to the corresponding resource block to the TSW 50 through the LSL 40 (S29). Instructs to drive (S30).

If the resource is supported by the SRSC 22, the SRSC 22 connects the destination side time switch to the TSW 50 through the LSL 40 with a channel connectable to the corresponding resource block (S31), and drives the resource block. Instructed to (S32).

As described above, after connecting the call channel between the incoming bearer channel and the resource channel and driving the resource, the ISUPC 10 is instructed to transmit an ANM message (S33). Create and send to the AIN SSP (S34).

When the ANM message is sent to the AIN SSP, the bearer channel between the AIN SSP and the AIN IP is connected, and the AIN IP transfers resources to the connected bearer channel.

When all resources are delivered to the user through the AIN SSP, the incoming time switch is disconnected (S35), and according to the provided resources, the BRSC and the SRSC instruct the INAP to transmit the resource providing result operation (S36), and the operation is waiting to be received ( S37).

3 is a flowchart illustrating a disconnection operation of an AIN IP by requesting disconnection from an AIN SSP according to the present invention.

If the ISUPC 10 receives a REL ISUP message requesting disconnection from the AIN SSP, the procedure starts (S38).

The ISUPC 10 requests the BRSC 21 to release the bearer channel (S39).

The BRSC 21 instructs the LSL 40 to disconnect the originating time switch with the bearer channel ID which is an internal parameter of the REL (S40), retrieves the correlation ID mapped to the bearer channel ID (S41), and is connected by the correlation ID. If there is a channel connected to the resource block by using the correlation ID mapped to the bearer channel ID (S42), the LSL 40 is requested to disconnect the incoming time switch connected to the corresponding channel (S43).

The BRSC 21 notifies the ISUPC 10 of the bearer channel disconnection result (S44), and the INAP 30 instructs release of the dialog set for operation communication with the AIN SCP (S45), and the child generated by the correlation ID. The processor is destroyed (S46).

The ISUPC 10 generates a Release Complete (RLC) message and delivers it to the MTP for transmission to the AIN SSP (S47), terminates the child processor generated for each correlation ID (S48), and ends (S49). .

4 is a flowchart illustrating a connection release operation of an AIN IP by a connection release request in the AIN IP itself according to the present invention.

In the BRSC 21, the bearer channel is connected to the ISUPC 10 when no further bearer channel is required or the operation is no longer possible due to abnormal operation, and when no operation is input from the AIN SCP for a certain period of time. Request release (S50).

After requesting, normal channel release or request timer end is determined (S51). In case of normal bearer channel release request from AIN SCP and timer end, BRSC 21 instructs ISUPC 10 to send REL message (S52). In operation S53, the LSL 40 is requested to disconnect the source time switch connected by the corresponding correlation ID.

After the request, the ISUPC 10 transmits an REL message to the MTP (S54), and enters the RLC waiting state (S55).

When the RLC message is received in the message reception state from the AIN SSP (S56), the child processor generated by the correlation ID is destroyed (S57).

After annihilation, the bearer release result is notified to the BRSC 21 (S58), and the child processor generated according to the correlation ID in the BRSC is destroyed (S59) and terminated (S60).

However, if the bearer channel is disconnected due to abnormal operation, the BRSC 21 instructs the ISUPC 10 to send a REL message (S61), and the LSL 40 to disconnect the originating time switch connected by the corresponding correlation ID. (S62).

And because of abnormal disconnection, it is possible that resources are currently being provided.

Therefore, the incoming time switch connected by the correlation ID also instructs the disconnection (S63).

The BRSC 21 requests the release of the dialog to the INAP for disconnection with the AIN SCP (S64), and the RLC message is waiting to be received from the AIN SSP (S65).

5 is a flowchart illustrating a connection release operation of an AIN IP by a dialog release instruction from an AIN SCP according to the present invention.

This operation is performed when a transaction termination message (S66) and an ARI failure message (S67) are received from the AIN SCP by a normal disconnection procedure, or when the dialog is forcibly released due to a protocol processing operation error at the counterpart INAP 30 itself. This is the case where the bearer channel connection is requested to the BRSC 21 in step 30 (S68).

The BRSC 21 transmits the bearer channel ID to the ISUPC 10 to transmit the REL message to the AIN SSP (S69).

The BRSC 21 instructs the LSL 40 to disconnect the incoming and outgoing time switch according to the correlation ID (S70), and then transmits an REL message to the MTP (S71), and enters the RLC wait state (S72).

When the RLC is received in the RLC waiting state (S72) after cutting the incoming / outgoing time switch (S73), the bearer channel disconnection result is notified to the BRSC 21 (S74), and the ISUPC 10 informs the correlation ID. The child processor generated by the processor is removed (S75).

After removal, the BRSC 21 destroys the child processor generated for each correlation ID (S76) and ends (S77).

As described above, the present invention relates to a procedure for connecting and releasing a bear channel in AIN IP when AIN IP, which is a network element of a next-generation intelligent network, controls a bearer channel by AIN SSP and ISUP signaling.

AIN IP is a network element that provides users with a variety of voice and fax (FAX) resources, unlike ordinary exchanges.

In other words, it is different from a method of connecting and releasing a bearer channel, which is developed at an existing exchange, as a corresponding resource block in an AIN IP by a called party to be connected to a bearer channel.

The present invention has an effect that can be applied when a network element for providing a special resource such as an AIN IP, for example, a service node or an information provider controls an exchange and a bearer channel through an ISUP. have.

Claims (6)

A protocol processing unit (INAP) having an integrated information communication network user unit (ISUP) and an IN application protocol, a service control unit divided into a basic resource service control unit (BRSC) and a special resource service control unit (SRSC), a time switch (TSW), Time switch unit (TSW) consisting of local switch collection unit (LSL), announcement broadcasting unit, DTMF digit collection unit (DDC) and voice recognition unit (SRECOG), voice recording unit (VRECORD), voice synthesis unit (SSYN) and fax In connection and disconnection of a bearer channel using an integrated information communication network user unit of an intelligent information providing system (AIN IP) having a resource controller divided into processing (FPROC), When the ISUPC requests a bearer channel from the ISUPC to the basic resource service control unit (BRSC), a first ARI message is transmitted to the AIN SCP requesting resources to be provided to the next-generation intelligent network service control point (AIN SCP). Process; A second step of, after receiving a resource request operation from the AIN SCP, disconnecting and disconnecting an incoming time switch and transmitting a resource provision result operation from BRSC to INAP; Receiving a connection release request from the AIN service switch (AIN SSP), disconnecting an outgoing time switch, requesting a dialog release from the INAP, and removing a child processor generated at the connection request; Requesting release of a bearer connection from the BRSC, requesting release of the dialog from the INAP, and extinguishing the child processor; And a fifth process of destroying the child processor generated in the BRSC after requesting the release of the connection to the BRSC by the dialog release instruction from the AIN SCP. The method of claim 1, wherein the first process is A first step of inputting the IAM message transmitted from the AIN SSP to the ISUPC 10 after the message transmission unit (MTP) processing (S1); A second step of generating a child processor for each correlation ID in the IAM message after interpreting the IAM message in the ISUPC 10 (S2), and controlling the operation in the ISUPC 10 by the child processor; After the continuity test request is determined in the IAM message (S3), if the test request is generated, the generated child processor instructs the LSL 40 to connect to the incoming channel (S4), and the third message waits for input (S5). Wow; A fourth step of instructing the LSL 40 to release the incoming channel connection (S7) when the continuous message is input (S6); A fifth step of requesting to connect the incoming bearer channel and the resource from the ISUPC 10 to the BRSC 21 after the incoming connection release instruction (S8); A sixth step of checking whether there is a channel available to the user among the channels allocated to each resource block (7, 8, 9, 10, 11, 12) after the DB search in the BRSC 21 (S9); After checking, it is determined whether the provision of resources is possible (S10), if possible, the ISUPC 10 is notified of the availability of resource connection (S11), and a child processor managing a bearer channel for each correlation ID is generated (S12). A seventh step of mapping an incoming bearer channel ID (S13); An eighth step of notifying that the ISUPC 10 is able to connect to the resource, generating an address completion (ACM) message to be transmitted to the AIN SSP, and then transmitting it to the MTP (S14); In step S15, if the resource is not available after the determination, the BRSC notifies the ISUPC that the resource is not available (S15); A tenth step of transmitting (S16) a release message for notifying of an incoming channel connection establishment failure to the MTP by the ISUPC (10); An eleventh step of entering a release completion wait state after transmission (S17), receiving a release completion (RLC) message from the MTP (S18), and ending (S19); If the resource is available after the determination, the child processor of the BRSC 21 instructs the TSW 50 to connect the originating time switch and the incoming bearer channel through the LSL 40 (S20); In order to perform this after the instruction, the BRSC (21) includes a thirteenth step of instructing the INAP (30) to transmit an auxiliary request instruction (ARI) operation, characterized in that the bearer channel connection and disconnection method using the ISUP. The method of claim 1, wherein the second process A first step in which the INAP 30 generates an ARI INAP operation and sends it to the AIN SCP and enters an INAP operation reception state from the AIN SCP (S22); A second step of receiving (S23) an operation for requesting resource provision of AIN IP from an AIN SCP in an operation reception waiting state (S22); If it is not possible to provide the resource requested by the BRSC 21 in the corresponding block (S24), the INAP 30 is notified of the resource provision unavailable (S25), each resource request from the INAP (30) A third step of sending a resource unavailable message to a response operation corresponding to the AIN SCP to the AIN SCP (S26), and waiting to receive an operation from the AIN SCP (S27); A fourth step of determining whether a resource to be provided is a resource controlled by the BRSC (21) or a resource controlled by the SRSC (22) (S28) if the resource can be provided after the determination; After determination, if the resource is supported by the BRSC 21, the BRSC 21 connects the destination side time switch to the TSW 50 through the LSL 40 with a channel connectable to the corresponding resource block (S29). A fifth step of instructing to drive (S30); If the resource is supported by the RSC 22, the SRSC 22 connects the destination side time switch to the TSW 50 through the LSL 40 with a channel connectable in the resource block (S31), and drives the resource block. Indicating (S32) a sixth step; After the instruction connects the call channel between the incoming bearer channel and the resource channel, and after driving the resource, instructs the ISUPC 10 to transmit the ANM message (S33), and the ANM message in the corresponding processor matching the correlation ID in the ISUPC. Generating and sending to the AIN SSP (S34) a seventh step; An eighth step of delivering resources to the connected bearer channel in the AIN IP after the transmission; And a ninth step of cutting the incoming time switch after delivery (S35), instructing the APAP to transmit a resource providing result operation to the INAP according to the provided resource (S36), and putting the operation into a waiting state for receiving the operation (S37). Bearer channel connection and release method using ISUP, characterized in that. The method of claim 1, wherein the third process is A first step of starting a procedure (S38) when receiving a REL ISUP message from the ISUPC (10) requesting disconnection from the AIN SSP; A second step (S39) of requesting the bearer channel connection release from the ISUPC 10 to the BRSC 21; The BRSC 21 instructs the LSL 40 to disconnect the transmission time switch with the bearer channel ID, which is an internal parameter of the REL (S40), and retrieves the correlation ID mapped to the bearer channel ID (S41). Determining whether a connected resource channel exists (S42), if there is a channel connected to the resource block, requesting the LSL 40 to disconnect the incoming time switch connected to the corresponding channel (S43); The BRSC 21 notifies the ISUPC 10 of the bearer channel disconnection result (S44), and instructs the INAP 30 to release the dialog set for communication with the AIN SCP (S45). A fourth step of destroying the old child processor (S46); After generating the release complete (RLC) message in the ISUPC (10), the transfer to the MTP to send to the AIN SSP (S47), and terminates after the child processor generated by the correlation ID (S48) (S49) includes a fifth step Bearer channel connection and release method using ISUP, characterized in that. The method of claim 1, wherein the fourth process If the bearer channel according to the scenario is not needed in the BRSC 21 or the operation is no longer possible due to an abnormal operation, the ISUPC 10 is requested to disconnect the bearer channel when no operation is input from the AIN SCP for a certain period of time. (S50) a first step; After requesting, normal channel release or request timer is determined (S51). In case of normal bearer channel release request from AIN SCP and timer termination, BRSC 21 instructs ISUPC 10 to send REL message (S52). Requesting the LSL 40 to disconnect the originating time switch connected by the corresponding correlation ID (S53); A third step of sending a REL message from the ISUPC 10 to the MTP after the request (S54) and putting the RLC in a waiting state (S55); Receiving a RLC message in the message reception state from the AIN SSP (S56), destroying the child processor generated by the correlation ID (S57); A fifth step of notifying the BRSC 21 of the bearer release result after annihilation (S58), and terminating (S59) the child processor generated according to the correlation ID in the BRSC (S60); If the bearer channel is disconnected due to abnormal operation, the BRSC 21 instructs the ISUPC 10 to send an REL message (S61) and tells the LSL 40 to disconnect the originating time switch connected by the corresponding correlation ID. Requesting (S62) a sixth step; A seventh step of instructing disconnection of the incoming time switch connected by the correlation ID after the request (S63); Using the ISUP, the BRSC 21 includes an eighth step of requesting the release of the corresponding dialogue to the INAP for disconnection from the AIN SCP (S64), and the wait for receiving the RLC message from the AIN SSP (S65). How to connect and disconnect bearer channels. The method of claim 1, wherein the fifth process When receiving the transaction termination message (S66) and the ARI failure message (S67) from the AIN SCP, or when the dialog is forcibly released due to a protocol processing operation error in the counterpart INAP 30 itself, the INAP 30 to the BRSC 21 are released. A first step of requesting bearer channel disconnection (S68); A second step of transmitting a REL message to the AIN SSP by transmitting the bearer channel ID to the ISUPC 10 in the BRSC 21 (S69); After the BRSC 21 instructs the LSL 40 to cut the incoming / outgoing time switch according to the correlation ID (S70), the REL message is transmitted to the MTP (S71), and the RLC wait state (S72). Steps; When the RLC is received in the RLC waiting state (S72) after disconnection of the incoming and outgoing time switch (S73), the bearer channel disconnection result is notified to the BRSC 21 (S74) and generated by the correlation ID in the ISUPC 10. Removing the child processor (S75); After the removal, the BRSC 21 terminates (S76) and terminates (S77) the child processor generated for each correlation ID. The bearer channel connection and release method using the ISUP, characterized in that the step.