KR100754672B1 - Basic Camel Call Control in Mobile Communication System - Google Patents

Abstract

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a mobile communication system, and more particularly, to a method for controlling basic incoming call control (CAMEL).

According to the present invention, in a Camel basic incoming call control method in a mobile communication system, when a call is received in an idle state, arming may be triggered so that Camel subscriber information (T-CSI) to be processed according to the call state is triggered, and the call is moved. Checking whether there is a route result of the mobile incoming call when the incoming call is received; transmitting an incoming authentication request message when the route result does not exist; and transmitting the incoming authentication message to the camel subscriber information. Changing the (T-CSI) to include the trigger detection request (TDP-R) for the camel basic call, and changing the trigger detection request (TDP-R) to include the location of the called subscriber to the home location register. Transmitting a transmission routing information (SRI) message to the home location register and corresponding to the transmission routing information (SRI) message Checking whether an incoming call forwarding number (FTN) is included in a transmission routing information response (SRI_ack) message received from the home location register; and the incoming call switching is included in the transmission routing information response (SRI_ack) message as a result of the inspection. If the number (FTN) is included, the process consists of transmitting an initialization message requesting control of the call forwarding service.

CAMEL, Route Results, Mobile Exchange, TBCSM

Description

METHODE FOR CONTROLLING CUSTOMIZED APPLICATIONS FOR MOBILE NETWORK ENHANCED LOGIC BASIC INCOMING CALL IN MOBILE COMMUNICATION SYSTEM}             

1 schematically illustrates a typical mobile communication system configuration

2 is a diagram illustrating an example of a TBCSM operation process according to the prior art;

3 illustrates another example of a TBCSM operation process according to the prior art;

4 is a diagram illustrating a TBCSM operation process according to an embodiment of the present invention.

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a mobile communication system, and more particularly, to a method for controlling basic incoming call control (CAMEL).

1 is a diagram schematically showing a typical mobile communication system configuration.

In FIG. 1, a Universal Mobile Terrestrial System (UMTS) system of a mobile communication system will be described as an example. In the UMTS, a core network application program includes a mobile switching center (MSC) 111 and a managed intelligent platform (MIP) 150. The management intelligence platform 150 converts the signaling message into an application message (general message) and a signaling interface agent (SIA) 151 that provides a signal interface. A Radio Access Network Application Part Signaling Agent (RANAP SA) or an SUPSA (153) and a resource of the radio access network are controlled and a Visitor Location Register (VLR) interface is provided. Provided Radio Access Control Function (RACF) 155, Call Control Function (CCF) 157 in charge of CAMEL basic call processing, and Service Exchange Function (SSF) Service Switching Function) 159.

2 is a diagram illustrating an example of a TBCSM operation process according to the prior art.

First, entry events, actions, and exit events of the T_Null state 211 are as follows.

. Entry event

Basic call processing by the release command for the ongoing or holding call, or by the completion of gsmSSF or mobile exchange operation.

Abnormal report from incoming call handling PIC                         

-Exception event reporting

.action

Interface is idle

Receive ISUP_IAM and analyze the received number ISUP_IAM to obtain information

Send a "Send_Info_For_Incoming_Call" request to the visitor location register of the mobile switch 111. Here, when the mobile exchange is GMSC, it sends a "Send_Routing_Info" request to a Home Location Register (HLR). In case of GMSC, it checks and invokes additional services of "barring of all incoming calls" and "barring of incoming calls when roaming", and selects ODB categories of "barring of all incoming calls" and "barring of incoming calls when roaming". Check and Invoke, and check and invoke the "CUG" side service.

Receive and analyze T-CSI / VTCSI

End event

-Receive response from home location register / visitor location register and analyze "terminating CSI"

Example exception condition: Calling party abandons call because no exception event can be seen because there is no DP.

The entry event, action, and termination event of the terminating call handling state 213 are as follows.                         

Entry event

-Receive response from home location register / visitor location register and analyze "terminating CSI" (DPTerminating_Attempt_Authorized)

When a "Busy" or "No Answer" event is reported from the called party's call handling PIC, new routing information is received.

When a "Disconnect" event is reported from the T_Active PIC, new routing information is received.

New routing information is received when a "terminating party not reachable" event is reported from the called party's call handling PIC.

.action

-Response analysis received from the home location register / visitor location register.

The routing address and call type are interpreted. The next router or incoming access is selected.

The called party is " alert ". The call waits for an "Answer" from the called party.

-"call forwarding" GSM supplementary service is invoked.

End event

The call is "accepted" or "answered" by the called party.

One exception status is carried (this results in the T_Exception PIC).

Incoming party abnormal call (this results in the T_Abandon DP)                         

-The destination access on the VMSC is "busy" or the GMSC receives a "busy" indication from the destination exchange (this results in the T_Busy DP).

If the VMSC cannot determine the subscriber's location, the GMSC cannot select the destination route, or encounters an unlocated event (this results in a T_Busy DP).

Timeout of "DP T_No_Answer" (this results in T_No_Answer DP)

The entry event, action, and end event of the T_Active state 215 are as follows.

Entry event

Incoming subscriber's call acceptance or response indication (DPT_Answer)

.action

Call connection establishment and call monitoring between called party and calling party

-Wait for the call to release

End event

When receiving a "disconnection indication" from the called party or receiving a "disconnection indication" through the calling half BCSM (DPT_Disconnect)

-An exception status is given Exception events include the type of failure.

The entry event, action, and end event of the T_Exception state 217 are as follows.                         

Entry event

-An exception status is given Exception events include the type of failure.

.action

Basic handling of the state provided by the exception

Release the resource associated with the call and transition to a state where a new call is possible

End event

-gsmSSF / (G) Basic handling of exceptions in MSC.

3 is a diagram illustrating another example of a TBCSM operation process according to the prior art.

First, an entry event, a function, and an exit event of the T_Null state 311 are as follows.

Entry event

-Disconnection of a held call or exception handling of the service switching function / call control function.

.function

-Idle state and monitoring of subscriber line or repeater line

End event

Receive an indication of the incoming call from the calling BCSB

-Receive exception events in progress of the call                         

The event, function, and termination event of the Authorize_Termination_Attempt state 313 are as follows.

Entry event

-Receive an incoming call event.

.function

Authentication and verification of routing for incoming call access

End event

"Termination_Attempt_Authorized" event for authentication

"Termination Denied" event for authentication

"Termination Denied" event for authentication

-Receive an abnormal event from the calling party of the call.

The entry event and the function and end events of the Select Facility state 315 are as follows.

Entry event

"Termination_Attempt_Authorized" event for authentication

.function

The busy / idle state for the called party access is determined.

End event

-"Facility_Selected_and_Available" event occurs when called party access is not busy                         

-Receive a "T_Abandon" event from the calling party.

The entry event, the function, and the termination event of the present call state 317 are as follows.

Entry event

-If the called party's access is not Busy, receive the "Facility_Selected_and_Available" event.

.function

Incoming call source information

End event

If the called party is alerted, the call is accepted by the called party.

Receive originating abnormal indication from calling BCSM.

-Send timer timeout of the circuit reservation message.

-Presentation Presentation Failure.

The entry event, function and termination event of the T_Alerting state 319 are as follows.

. Entry event

-The called party is alerted.

.function

If the called party is alerted, send an alerted indication to the calling party's BCSM.

End event                         

The call is accepted or answered by the called party.

-Exception and abnormal handling of calls.

The entry event, function and termination event of the T_Active state 321 are as follows.

Entry event

-The call has been accepted or answered by the called party.

.function

If the called party accepts or responds, it sends this indication to the calling BCSM.

-It provides call setup and monitoring function of called party and calling party.

End event

-Receive the request of the service or service function from the called party (DTMF, hook flash, Hold, Retrieve ..).

-Receive a call release from the called party.

Receive call release from the calling party.

-Timeout of the reset timer of the arc.

-Call failed.

The entry event, function, and termination event in the T_Suspended state 323 are as follows.

Entry event

-Receive an indication for the called party's release from the calling network (on hook).                         

.function

The call allocates physical resources while maintaining the connection.

Send a pause to the calling BCSM.

End event

If the called party receives a reconnect or resume message before the timer times out in this state, the call is reactivated.

-Timer time out.

-Receive a call release from the called party.

Receive call release from the calling party.

-Exception handling of arcs.

The entry event, function, and termination event of the T_Exception state 325 are as follows.

Entry event

-Receive an exception status during call processing.

.function

-Send an indication of the exception to the calling BCSM.

End event

Basic control of the exception status by the end event service exchange function / call control function

In the conventional mobile communication system, the CAMEL basic call processing and control process is performed through the mobile communication system internally, and the CAMEL basic call processing is implemented in a module independent of the mobile communication system. It is becoming. Thus, since the CAMEL basic call is processed in a module that is not independent of the mobile communication system, it is difficult to standardize the parts closely related to the mobile communication system, so it is difficult in maintenance such as program change and application. There was this. Therefore, if you want to accommodate different types of call processing, it is necessary to create a separate program or combine separate call processing, and the need for a CAMEL basic call control method that can be performed independently of the mobile communication system. This has risen.

Accordingly, an object of the present invention is to provide a method capable of controlling independent CAMEL basic call processing with a mobile communication system.

According to the present invention for achieving the above object, in the Camel basic incoming call control method in a mobile communication system, when a call is received in an idle state, Camel subscriber information (T-CSI) to be processed according to the call state is triggered. Arming the mobile call and checking whether there is a route result of the incoming call when the call is a mobile incoming call, and transmitting an incoming authentication request message when the route result does not exist; After transmitting the process and changing to include the trigger detection request (TDP-R) for the camel basic call in the camel subscriber information (T-CSI), and after the change to include the trigger detection request (TDP-R) Send a routing routing information (SRI) message to a home location register to identify the location of the called subscriber to a home location register; Checking whether an incoming call forwarding number (FTN) is included in the transmission routing information response (SRI_ack) message received from the home location register in response to a message information (SRI) message; If the SRI_ack message includes the incoming call forwarding number (FTN), it is characterized in that the process of transmitting an initialization message requesting control of the incoming call forwarding service.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that in the following description, only parts necessary for understanding the operation according to the present invention will be described, and descriptions of other parts will be omitted so as not to distract from the gist of the present invention.

4 is a diagram illustrating a TBCSM operation process according to an embodiment of the present invention.

First, in the embodiment of the present invention, in the mobile communication system described with reference to FIG. 1, the call control function unit 157 becomes a terminating basic call state model (TBCSM), and the call control function unit 157 In this case, the originating basic call is processed and controlled, so that the mobile communication system and the basic call processing have an independent call processing structure and reusability is guaranteed.

Before describing the operation of the TBCSM according to an embodiment of the present invention with reference to Figure 4, the terms used below are briefly summarized. The terms used below are well known in the art to which the present invention is applied, and thus will be apparent to those skilled in the art, even if replaced by a simple description.
Rectangular blocks indicated by reference numerals 411, 413, 417, 425, 419, 426, 427, 429 and 431 in FIG. Detects detection points that detect any events that act as conditions that change.
First, the PIC T_Null state 411 needs to be changed to arm the T_CSI trigger. The PIC T_Null state 411 is an idle state of the TBCSM. When the incoming call is received in the PIC T_Null state 411, the TICN_Null state 411 starts driving for incoming call control. The PIC T_Null state 411 represents Termination_Null state of the 'Point-In-Call' state. When an incoming call is received in the PIC T_Null state 411, the TBCSM is a service to be processed according to the state of the incoming call (T- Arm CSI: Terminating_CAMEL Subscriber Information) to be triggered. The 'aming' refers to an operation of preparing any service according to the occurrence of any event, and the 'trigger' refers to the armed call state according to the occurrence of any event in any call state. It refers to an operation of switching to another call state, and the information armed in all the processes of performing the incoming call is used effectively in all the states shown in FIG. 4, and is destroyed when the incoming call state returns to the PIC T_Null state. Self-explanatory
The Subscriber Data Base (SDB) cannot find information unless the call type is a mobile incoming signal and there is no route result. The SDB is a component constituting the mobile communication system and is included in the MSC of FIG. 1. The SDB stores the received subscriber information in the T-CSI when the mobile subscriber registers the location with the MSC and receives the corresponding subscriber information from the home location register. When the incoming call is started in the PIC T_Null state, the SDB may control arming for the incoming call if the incoming call type is a mobile arrival signal and the corresponding T_CSI of the mobile arrival signal. However, if the T_CSI cannot be found in the SDB, a procedure of receiving subscriber information by routing information for finding a home location register in the MSC must be performed. If there is no route result in the MSC, the corresponding T_CSI cannot be found.
The PIC Authorize_Termination_Attempt state 413 is a state of authenticating an incoming call. If the call type is a mobile incoming call and there is no route result, the PIC Authorize_Termination_Attempt state 413 performs an authentication procedure by transmitting an "Auth_Term_Attempt" incoming authentication request message to an access control function. This state is changed after requesting to. The PIC Authorize_Termination_Attempt state 413 is generated when a Send Routing Information Acknowledgment (SRI_ack) message is received from a mobile switching center (GMSC) from a Home Location Register (HLR). That is, the MSC sends an SRI to the home location register for basic mobile call processing, and performs an authentication procedure for incoming call processing when receiving a response message from the home location register.
In addition, the DP Termination_Attempt_Authorized state 415 is a state in which authentication for an incoming call is completed, and 'DP' is an abbreviation of Detection Point. Changes to the next call processing state to include Trigger Detection Point-Request (TDP-R) for the Customized Applications for Mobile Network Enhanced Logic (CAMEL) basic call in the T-CSI base. After authentication is completed, the call processing status is changed under the following conditions. When the incoming call authentication is completed, it is checked whether gsmSCF has already been triggered before triggering T-CSI. If the call type is a mobile incoming call and there is no route result, the call is in the PIC_Mobile_Continue_Termination_Handling state for mobile subscriber call processing. Proceed to (417). The PIC_Mobile_Continue_Termination_Handling state 417 is a state for controlling an incoming call of a mobile subscriber. If the call type is an incoming / outgoing call and there is a route result, the call proceeds to the general PIC_Select_Facility state 419 for performing the relay call. The state of the reference number 419 is a state of controlling the incoming call or relay call of the mobile subscriber.

In the PIC Mobile_Continue_Termination_Handling state 417, the incoming call of the mobile subscriber is controlled, and it is checked whether the "SRI_ack" message received from the home location register includes a forwarded to number (FTN) for the call forwarding service. do. If the received "SRI_ack" message includes the FTN, the DP_FTN_Encountered state 421 for requesting the incoming call service is performed. If the FTN is not included, then the DP_T_Query_HLR for the other incoming call service is performed. "State 423". In this case, the DP FTN_Encountered state 421 sends an initialization message (InitDP) for requesting control such as notification information of the calling subscriber for the call forwarding service to the "local SCF" for handling of the call forwarding service. In this case, whether or not the trigger is transmitted (ie, whether to send the initialization message) is determined based on the result already armed by T-CSI. The "local SCF" is implemented as a service control logic included in the MSC to control the supplementary service. Then, the service key in the initialization message sent to the local SCF in the DP FTN_Encountered state is the FTN and the call is handled to the local SCF. (I.e. call forwarding). In addition, the DP T_Query_HLR state 423 is a state for handling the case where no T-CSI service is included in the SRI_ack. If a trigger for the DP_T_Query_HLR state 423 occurs, the SRI message concealing the CAMEL basic call is generated. Send to the home location register. The 'CAMEL basic call transmits the concealed SRI message to the home location register' means that the home location register is requested to ignore any T-CSI service. Thus, the SRI_ack received from the home location includes a mobile subscriber number (MSRN) or FTN for basic call processing. After that, the call processing state is changed to PIC Mobile_Analyse_Info_Select_Route state for analyzing the called party's number.

The PIC Mobile_Analyse_Info_Select_Route state 425 indicates that if the FTN is received from the SRI_ack, the call proceeds to the DP_FTN_Encountered state 421, and if the MSRN is received, the call is processed after the number translation and routing for the received MSRN and the call is the PIC_T_Null. Is changed to state 411.

The remaining states, which are not described above, of the present_Call state 426, the T_Alerting state 427, the T_Active state 429, the T_Suspended state 431, and the T_Exception state 433 are as follows.
Among the states transitioned from the general PIC Select_Facility state 419, the Present_Call state 426 means a state in which an incoming call is not in a call (mobile subscriber incoming or calling relay state). The T_Alerting state 427 means a state in which the called party is not busy and can accept a call, and the T_Active state 429 means a state in which the called subscriber is in a call state. The T_Suspended state 431 refers to a state in which a subscriber who is in a call stops the call for a while and suspends a call between the network and the terminal. The T_Exception state 433 becomes a state in which call processing cannot be performed during incoming call processing. Or when the call is terminated. The detailed processing details of each state are as follows.

The entry event, function, and exit event of the Present_Call state 426 are as follows.

Entry event

-If the called party's access is not Busy, receive the "Facility_Selected_and_Available" event.

.function

Incoming call source information

End event

If the called party is alerted, the call is accepted by the called party.

Receive originating abnormal indication from calling BCSM.

-Send timer timeout of the circuit reservation message.

-Presentation Presentation Failure.                     

The entry event, function, and termination event of the T_Alerting state 427 are as follows.

. Entry event

-The called party is alerted.

.function

If the called party is alerted, send an alerted indication to the calling party's BCSM.

End event

The call is accepted or answered by the called party.

-Exception and abnormal handling of calls.

The entry event, function, and termination event of the T_Active state 429 are as follows.

Entry event

-The call has been accepted or answered by the called party.

.function

If the called party accepts or responds, it sends this indication to the calling BCSM.

-It provides call setup and monitoring function of called party and calling party.

End event

-Receive the request of the service or service function from the called party (DTMF, hook flash, Hold, Retrieve ..).

-Receive a call release from the called party.                     

Receive call release from the calling party.

-Timeout of the reset timer of the arc.

-Call failed.

Entry events, functions, and termination events in the T_Suspended state 431 are as follows.

Entry event

-Receive an indication for the called party's release from the calling network (on hook).

.function

The call allocates physical resources while maintaining the connection.

Send a pause to the calling BCSM.

End event

If the called party receives a reconnect or resume message before the timer times out in this state, the call is reactivated.

-Timer time out.

-Receive a call release from the called party.

Receive call release from the calling party.

-Exception handling of arcs.

The entry event, function, and termination event of the T_Exception state 433 are as follows.

Entry event                     

-Receive an exception status during call processing.

.function

-Send an indication of the exception to the calling BCSM.

End event

Basic control of the exception status by the end event service exchange function / call control function

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by the equivalents of the claims.

The present invention as described above, by controlling the CAMEL basic call processing to be processed independently from the mobile communication system in the mobile communication system ensures the reuse of resources and it is possible to standardize data related to program modification and service quality improvement Has the advantage.

Claims (2)

In the Camel basic incoming call control method in a mobile communication system, When a call is received in the idle state, arming the triggered Camel subscriber information (T-CSI) to be processed according to the call state, and checking whether a route result of the mobile incoming call exists if the call is a mobile incoming call; , Transmitting an incoming authentication request message when the test result does not exist; Changing the Camel subscriber information (T-CSI) to include a trigger detection request (TDP-R) for a camel basic call after transmitting the incoming authentication message; After changing the trigger detection request (TDP-R) to include a transmission routing information (SRI) message to confirm the location of the incoming subscriber to the home location register to the home location register, the transmission routing information (SRI) message Checking whether an incoming call forwarding number (FTN) is included in a transmission routing information response (SRI_ack) message received from the home location register corresponding to In the mobile communication system, if the transmission routing information response (SRI_ack) message includes the incoming call forwarding number (FTN), the initialization message requesting control of the incoming call forwarding service is transmitted. Camel basic call control. The method of claim 1, wherein the initialization message, And a service key indicating that the call is a call forwarding number and requires a separate call forwarding.

Images