KR100810336B1 - Basic Camel Call Control Method 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 a basic outgoing signal (CAMEL).

The present invention provides a method for controlling a Camel basic outgoing call in a mobile communication system. Performing a process; transmitting an SRI to a home location register when the routed call type is a mobile termination call; obtaining specific parameters by receiving the SRI response from the home location register; Transmitting a setup request message to a basic call state model terminator; and setting up a call to a calling party according to setup authentication after transmitting the setup request message.

CAMEL, Route Results, Mobile Exchange, OBCSM

Description

METHOD FOR CONTROLLING CUSTOMIZED APPLICATIONS FOR MOBILE NETWORK ENHANCED LOGIC BASIC ORIGINATING CALL IN MOBILE COMMUNICATION SYSTEM}             

1 schematically illustrates a typical mobile communication system configuration

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

3 illustrates another example of an OBCSM operation process according to the prior art;

4 is a diagram illustrating an OBCSM 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 a basic outgoing signal (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 an OBCSM operation process according to the prior art.

First, an entry event (ENTRY EVENT), actions (ACTIONS), and an end event of the O_Null & Authorize_Origination_Attempt_Collect_Info state 211 are as follows.

.ENTRY EVENT

-Basic processing by the release command for ongoing or holding calls or completion to gsmSSF or (G) MSC.

-Anomaly reporting from Analysis_Information or Routing and Alerting PIC.                         

-Exception event reporting.

ACTIONS

The interface is idle.

Outgoing call: The SETUP message includes the dial number received from the wireless terminal. .

Outgoing call: Additional services for all outgoing call restrictions are checked and invoked if necessary.

Outgoing call: ODB categories for all calling restrictions are checked and ODB is invoked if necessary.

Outgoing call: CUG is performed and checked at the originating mobile exchange (MSC) / Visitor Location Register (VLR).

Outgoing and incoming information is analyzed (ie O-CSI is analyzed).

End event

-The calling CSI is analyzed.

One exception condition is shown (Example exception condition: Calling party abandons call). This is because no exception event can be seen because there is no DP.

The entry event, actions and termination events of the Analyse_Information state 213 are as follows.

Entry event:                         

Calling CSI is analyzed (DPCollected Info).

New routing information is received when a Busy event, Route Select Failure event, Not Reachable event or No Answer event is output from the Routing and Alerting PIC.

New routing information is received when a Disconnect event is output from the O_Active PIC.

ACTIONS

-Compare the called party number with dialed service information.

End event

The nature of the address and the usefulness of the routing address (DPAnalysed_Information).

-One exception status (ie wrong number)-this results in the O_Exception PIC

Caller abnormal call. This results in O_Abandon DP.

The entry event, actions (ACTIONS), and termination event of the routing & alerting state 215 are as follows.

Entry event

-The nature of the address and the availability of routing addresses (DPAnalysed_Information).

ACTIONS

The routing address is determined after the information is analyzed and translated / translated according to the dialing plan.

The routing address is interpreted.

Outgoing call: Checked and invoked when the origination restriction service and ODB category are not processed.

The call is handled by the called party's half BCSM. Wait for a response from the called party's half BCSM.

End event

-Incoming half BCSM instructs incoming call accept or answer (DPO_Answer).

-One exception status is carried-this results in an O_Exception PIC

Caller abnormal call. This results in O_Abandon DP.

Busy received from the called party.This results in O_Busy DP.

-Incoming call from the called party cannot be confirmed-This causes O_Busy DP

Destination router selection failed, resulting in Route_Select_Failure DP

DP O_No_Answer timer timeout, which results in O_No_Answer DP

The entry event, the actions and the termination event of the O_Active state 217 are as follows.

Entry event

-Incoming half BCSM instructs incoming call answer or answer (DPO_Answer).

ACTIONS

-Call connection establishment and call monitoring of called party and calling party.                         

-Wait for the call to release.

End event

Receive an indication of the disconnection of the call from the called party through the calling party or the called party half BCSM. (DP9-O_Disconnect)

-An exception status is given

The entry event, actions and termination event of the O_Exception state 219 are as follows.

Entry event

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

ACTIONS

Basic handling of the state provided by the exception state.

-Release the resources associated with the call and transition to a state where a new call is possible.

End event

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

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

First, entry events, actions and termination events in the O_Null state 311 are as follows.

Entry event

-Disconnect the held call or throw an SSF / CCF exception.                         

ACTIONS

-Idle state and monitoring of subscriber line or repeater line

End event

Receive hook off, SETUP, or IAM signals from subscribers

The entry event, actions and termination events of the Authorize_Origination_Attempt state 313 are as follows.

Entry event

-Authentication of the calling terminal.

ACTIONS

The calling terminal must be checked using the calling party number and the service profile.

End event

Result of authentication (if successful, go to next PIC or throw exception)

Entry events, actions and termination events of the Collect_Information state 315 are as follows.

Entry event

-Caller is authorized.

ACTIONS

Collect service codes, prefixes, and dialed digits from the caller.

End event                         

-When the dialed digit is correctly collected from the caller.

-Failed to collect dialed digits from the sender.

The entry event, actions (ACTIONS), and termination event of the Analyse_Information state 317 are as follows.

Entry event

-If the digits are collected normally from the caller or if the corresponding router is busy when selecting a router.

ACTIONS

After the digit is analyzed or translated, the call type and routing address are determined by the dialing plan.

End event

One address is determined to be a routing address. Exception handling by invalid address.

The entry event, actions (ACTIONS), and termination event of the select route state 319 are as follows.

Entry event

-Call type and routing address are available.

ACTIONS

If the routing address and call type are interpreted, select the next router.                         

End event

-Router selected.

-Router selection is not possible.

The entry event, actions (ACTIONS), and termination event of the Authorize_Call_Setup state 321 are as follows.

Entry event

-Router selected.

ACTIONS

-Authenticate the call.

End event

-Call setup authentication result (SS7).

-Call setup authentication failed.

-Abnormal number of outgoing signals.

The entry event, action actions, and termination event of the Send_Call state 323 are as follows.

Entry event

-Call setup authentication event received.

ACTIONS

The service exchange function (SSF) / call control function (CCF) sends the described information about the called party.                         

-charge Number,

-Calling Party ID

-Calling Party BGID

-Calling Party Category

-Bearer Capability

-Called Party ID

-Calling Party Subaddress

-Called Party Subaddress

-Carrier

Route Index

-Carrier Identification Code

Circuit Code

-Carrier Selection

End event

-Acknowledge a route failure event.

-When an Answer Event is received from the called party.

-When a call accepted event is received from the called party.

-If a service feature request is received from the calling subscriber.

-Receive an O_No_Answer Event from the called party.

-Receive O_Called_Party_Busy Event by the called subscriber.                         

-SS7 related authentication failure.

-Caller abnormal call.

Entry events, actions and termination events in the O_Alerting state 325 are as follows.

Entry event

-Receive an O_Term_Seized event from the called party.

ACTIONS

Wait for a response from the called party.

-Receive call progress event of called subscriber.

End event

-When the O_Answer Event for the call is received from the called party.

-If a service feature request is received from the calling subscriber.

-Acknowledge a route failure event.

-Receive an O_No_Answer Event from the called party.

-Receive O_Called_Party_Busy Event from the called party.

-Caller abnormal call.

Entry events, actions and termination events of the O_Active state 327 are as follows.

Entry event

-The called party accepts or answers the call.                         

ACTIONS

-In addition to establishing a connection between the called party and the calling party.

End event

-If a service feature request is received from the calling subscriber.

-When a call release is received from the called party.

-When a call release is received from the calling subscriber.

-Timeout of the reconnection timer.

-Connection failure occurred.

The entry event, actions and termination events in the O_Suspended state 329 are as follows.

Entry event

-Receive a stop instruction for a while when the calling party's call is released.

ACTIONS

The call connection between the called party and the called party is managed and relied on by the called party's network connection.

-When a disconnect instruction is received from the destination T-BCSM.

The call is reestablished when it receives a re-answer indication from the called party's T-BCSM.

End event

Resume from the called party interruption.

-If a service feature request is received from the calling subscriber.                         

-When a call release is received from the called party.

-When a call release is received from the calling subscriber.

-Timeout of the reconnection timer.

-Receive exception event.

Entry events, actions and termination events in the O_Exception state 331 are as follows.

Entry event

-Reception of exception status.

ACTIONS

-Default control of exception status.

End event

-Exception status control by the Service Switching Function Unit (SSF) / Call Control Function Unit (CCF).

In the conventional mobile communication system, the CAMEL basic outgoing signal processing and control process is performed through the mobile communication system internally, and the CAMEL basic outgoing signal processing is performed in a module independent of the mobile communication system. Is being implemented. Thus, since the CAMEL basic outgoing signal is processed in a module independent of the mobile communication system, it is difficult to standardize parts closely related to the mobile communication system, and thus, in maintenance of program change and application, etc. There was a difficulty. 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 CAMEL basic calling signal control method that can be performed independently of the mobile communication system is required. Necessity arose.

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

The present invention for achieving the above object, in the Camel basic outgoing call control method in a mobile communication system, the basic call state model originator controlling the camel basic outgoing call detects the call setup according to the camel basic outgoing call generation And if the call setup is detected, performing the authentication of the outgoing call to perform routing corresponding to the called party's telephone number for the outgoing call; and, if the type of the routed call is a mobile termination call, a home location register. Transmitting SRI (Send Routing Information), which is transmission routing information for identifying the location of the called subscriber, receiving the SRI response from the home location register, obtaining specific parameters, and setting up a setup request corresponding to the acquired parameters. Sending a message to the basic call state model end, and setting up after transmitting the setup request message. It characterized by constituted by any process of setting up a call to the calling party according to the authentication.

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 0BCSM 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 an originating basic call state model (OBCSM), and the call control function unit 157 The originating basic call is handled and controlled, so that the mobile communication system and the basic call processing have an independent call processing structure and reusability is guaranteed.

First, the DP Analyzed_Information state 411 sends an SRI to the Home Location Register (HLR) if the call type is a "mobile termination call." After receiving the SRI response (Ack) from the home location register, the SRI parameters T-CSI, O-CSI, FTN, etc. should be stored. If the SRI acknowledgment includes a T-CSI parameter, the call is transmitted to the T-BCSM by a Setup Request Instruction message including the T-CSI through a "PICs Select_Route and Authorize_Call_Setup" message. do. And, if the PIC Select_Route state 413 is a mobile incoming signal with T-CSI included in the SRI response, "PIC_Select_Route" should be changed so that route selection fails for the call. And, the PIC Authorize_Call_Setup state 415 should be changed so as not to fail the route authentication for the corresponding call if the SRI response includes the T-CSI.

The remaining Send_Call state 417, the O_Alerting state 419, the O_Active state 421, the O_Suspended state 423, and the O_Exception state 425 are as follows.

The entry event (ENTRY EVENT), the function and the end event of the Send_Call state 417 are as follows.

Entry event

-Call setup authentication event received.

.function

The service exchange function (SSF) / call control function (CCF) sends the described information about the called party.

-charge Number,

-Calling Party ID

-Calling Party BGID

-Calling Party Category

-Bearer Capability

-Called Party ID

-Calling Party Subaddress

-Called Party Subaddress

-Carrier

Route Index

-Carrier Identification Code

Circuit Code

-Carrier Selection

End event                     

-Acknowledge a route failure event.

-When an Answer Event is received from the called party.

-When a call accepted event is received from the called party.

-If a service feature request is received from the calling subscriber.

-Receive an O_No_Answer Event from the called party.

-Receive O_Called_Party_Busy Event by the called subscriber.

-SS7 related authentication failure.

-Caller abnormal call.

The entry event, function, and termination event of the O_Alerting state 419 are as follows.

Entry event

-Receive an O_Term_Seized event from the called party.

.function

Wait for a response from the called party.

-Receive call progress event of called subscriber.

End event

-When the O_Answer Event for the call is received from the called party.

-If a service feature request is received from the calling subscriber.

-Acknowledge a route failure event.

-Receive an O_No_Answer Event from the called party.                     

-Receive O_Called_Party_Busy Event from the called party.

-Caller abnormal call.

The entry event, function and termination event of the O_Active state 421 are as follows.

Entry event

-The called party accepts or answers the call.

.function

-In addition to establishing a connection between the called party and the calling party.

End event

-If a service feature request is received from the calling subscriber.

-When a call release is received from the called party.

-When a call release is received from the calling subscriber.

-Timeout of the reconnection timer.

-Connection failure occurred.

The entry event, function, and termination event in the O_Suspended state 423 are as follows.

Entry event

-Receive a stop instruction for a while when the calling party's call is released.

.function

The call connection between the called party and the called party is managed and relied on by the called party's network connection.

-When a disconnect instruction is received from the destination T-BCSM.

The call is reestablished when it receives a re-answer indication from the called party's T-BCSM.

End event

Resume from the called party's interruption.

-If a service feature request is received from the calling subscriber.

-When a call release is received from the called party.

-When a call release is received from the calling subscriber.

-Timeout of the reconnection timer.

-Receive exception event.

The entry event, function, and termination event of the O_Exception state 425 are as follows.

Entry event

-Reception of exception status.

.function

-Default control of exception status.

End event

-Exception status control by the Service Switching Function Unit (SSF) / Call Control Function Unit (CCF).

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.

As described above, the present invention controls the CAMEL basic outgoing signal processing in a mobile communication system to be processed independently of the mobile communication system, thereby ensuring resource reuse and standardizing data related to program modification and service quality improvement. It has the advantage of being possible.

Claims (2)

In the Camel basic outgoing call control method in a mobile communication system, Detecting, by the basic call state model originator controlling the camel basic originating call, call setup according to the camel basic originating call; Detecting the call setup, performing authentication of the outgoing call to perform routing corresponding to a called party's telephone number for the outgoing call; Transmitting SRI (Send Routing Information), which is transmission routing information for identifying a location of a called subscriber, to a home location register when the type of the routed call is a mobile termination call; Receiving the SRI response from the home location register to obtain specific parameters, and transmitting a setup request message corresponding to the acquired parameters to a basic call state model terminator; And transmitting the setup request message and setting up a call to the calling party according to the setup authentication. The method of claim 1, Terminating CAMEL Subscription Information (T-CSI) includes information stored in a subscriber database so that any service can be serviced according to the occurrence of any event in order to control a service required during the call processing according to the SRI response. If it is a mobile incoming call, the basic call signal control method of the camel in the mobile communication system, characterized in that it further comprises the step of changing the route authentication failure for the corresponding call.

Images