KR20000041932A - Selective origination acceptance method - Google Patents

Abstract

PURPOSE: A selective origination acceptance method is provided to vary a service state according to a request of a subscriber such as an activation or inactivation request of a selective origination acceptance, an addition or delete request of a registration number, and a secret number changing request. CONSTITUTION: In a selective origination acceptance method, a mobile subscriber tries to originate(710), and there is judged whether a selective origination acceptance is at an activation state(720). If a selective origination acceptance is not at an activation state, a call set is accepted(730). If a selective origination acceptance is at an activation state, there is checked whether a destination number is registered(740). If a destination number is registered, the procedure goes to the step(730) in order to accept a call set. If a destination number is not registered, a password is requested(750). There is checked whether the input password is identical to a registered password(760). If so, the procedure goes to the step(730) in order to accept a call set. If not, a call set is rejected(770).

Description

Selective Sending Method (SOS) Method

The present invention relates to a Selective Origination Acceptance (SOA) method of a mobile communication system. Particularly, the present invention relates to a selective origination acceptance service (SOA) method. The present invention relates to a call permission service method.

In general, a mobile communication system divides a wide service area into several radio zones such as cells, installs a base station in each wireless zone, wirelessly communicates between the mobile station and the base station, and fixes a fixed network through a wireless control station. It is a system to connect and make a call to a public public telephone network. In such a conventional mobile communication system, the subscriber cannot limit the transmission range of the terminal and thus cannot block unnecessary transmission in advance.

Accordingly, an object of the present invention is to change the status of a service according to a subscriber's request, such as a request for activating or deactivating a selective call permitting service (hereinafter referred to as "SOA"), a request for adding or deleting a registration number, or a password change request. The present invention provides a method for allowing selective calling of a mobile communication system.

1 is a view schematically showing a mobile communication system;

2 is a view for explaining a process for changing a password requested by a subscriber;

3 is a view illustrating a process of activating and deactivating a selective calling permission (SOA) service of a mobile subscriber (MS);

4 is a view for explaining the addition and deletion of registration numbers;

5 is a reference diagram for explaining a call progress for an unregistered number, a diagram for explaining a case where a normal call proceeds through a password input;

6 is a reference diagram for explaining call progress for an unregistered number, and for explaining a case in which a password input fails.

7 is a flow chart for explaining a selective call admission (SOA) service method.

※ Explanation of codes for main parts of drawing

10: Mobile subscriber (MS) 20: Mobile service exchange center (MSC)

30: Home position register (HLR)

A feature of the present invention for achieving the above object is that in the method of selectively transmitting call service of the mobile communication system, when the mobile subscriber attempts to make a call, the mobile subscriber determines whether the selective call permission (SOA) is activated. If the selective call allowance decision step, and if the selective call allowance (SOA) is inactive state, the call setting is allowed, if the active state, the caller ID registration determination step to determine whether the called party number is registered, if the called party number is registered Allow call setup, request password input if called party number is not registered, determine whether input password and registered password match, allow call setup if input password and registered password match And a password comparison step of rejecting call setup if the passwords do not match. Selective Sending Allowed (SOA) method.

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

1 is a diagram schematically illustrating a mobile communication system. A mobile subscriber (MS) 10 is connected to a mobile switching center (MSC) 20. The mobile service switching center (MSC) 20 is a system for providing communication services to mobile subscribers, and performs circuit switching between subscribers, incoming / outgoing relay call processing, and the like. Home Location Resister (HLR) 30 is connected to MSC 20 and is located at a fixed point in the network for mobile devices to provide subscriber information and location information. It has an in-network database function to manage the back.

The MSC 20 and the Home Location Register (HLR) 30 exchange Remote User Interaction Directives. For convenience of description, the MSC 20 receives a home service from the MSC 20. The remote user conversation instruction sent to the location register (HLR) 30 is lowercase (ruidir), and the remote user conversation instruction sent from the home location register (HLR) 30 to the MSC 20 is In uppercase (RUIDIR). In addition, a feature request signal exchanged between the MSC 20 and the home location register 30 is also transmitted to the MSC 20 for convenience of description. The add-on request sent to the home location register (HLR) 30 is capitalized (FEATREQ), and the add-on request sent from the home location register (HLR) 30 to the MSC 20 is capitalized. (featreq).

Referring to Figure 2 will be described in detail the process for changing the password requested by the subscriber.

The mobile subscriber (hereinafter referred to as "MS") 10 sends a feature code to the mobile service switching center (hereinafter referred to as "MSC") 20 by pressing a dial of the terminal (SEND). (Step a). The MSC 20 receives a digit (hereinafter, referred to as a "digit") from a terminal of the mobile subscriber MS, and analyzes it to detect a feature code. The MSC 20 includes the received digit DGTSDIAL and a transaction capability (TRANSCAP) parameter for transmitting and receiving general data in the FEATREQ signal and the home position register (hereinafter referred to as "HLR"). "," (Step b). The HLR 30 approves the SOA registration request, displays a prompt for input of a previous personal identification number (PIN) of the MS 10, and receives a digit input from a terminal of the MS 10. The remote user interactive instruction (RUIDIR) including a guide list (ANNLIST) indicating the message is transmitted to the MSC 20 (step c). The MSC 20 receives the RIDIR and becomes a call connection (step d). The MSC 20 prompts for entry of a previous Personal Identification Number (PIN) according to the Digit Collection Control (DGTCC) parameter, which is the information of the Remote User Interactive Instruction (RUIDIR) received in step c. Is displayed on the terminal of the MS 10 (step e). MS 10 responds to the call by entering its previous personal identification number (PIN) (step f). The MSC 20 sends a remote user interactive instruction (ruidir) including the digit (DGTDIAL) dialed by the user to the home position register (HLR) (step g). The HLR 30 displays a prompt for input of a new personal identification number (PIN) of the MS 10, and sends a remote user interactive instruction (RUIDIR) instructing the reception of a digit from the terminal of the MS 10 (MSC 20). (Step h). The MSC 20 prompts the terminal of the MS 10 for input of a new personal identification number (PIN) according to the digit collection control (DGTCC) parameter, which is information of the RIDIR received in step g. Display (step i). MS 10 responds to the call by entering its new personal identification number (PIN) (step j). The MSC 20 sends a remote user interactive instruction (ruidir) including the digit (DGTDIAL) dialed by the user to the home position register (HLR) (step k). The Home Location Register (HLR) displays a prompt for re-entry of a new Personal Identification Number (PIN) of the MS 10 and instructs the remote user interactive instruction (RUIDIR) to instruct to receive a digit input from the terminal of the MS 10. ) Is sent to the MSC 20 (step l). The MSC 20 prompts the terminal of the MS 10 for a re-entry of a new personal identification number (PIN) according to the digit collection control (DGTCC) parameter, which is the information of the RIDIR received in step l. (Step m). MS 10 responds by re-entering a new PIN (step n). The MSC 20 sends a remote user interactive instruction (ruidir) including the digit DGTDIAL dialed by the user to the HLR 30 (step o). The HLR 30 updates the registration information of the selective calling permission (SOA) service of the corresponding MS 10 and outputs a MSF signal including a feature result parameter indicating a successful add-on operation. (20) (step p). The MSC 20 provides the add-on check to the MS 10 (step q). The MSC 20 then releases the call associated with the MS 10 (step r).

3 is a diagram illustrating a process of activating and deactivating a selective call permission (SOA) service of the MS 10.

The mobile subscriber MS sends a feature code to the MSC 20 by pressing the dial of the terminal (step a). The MSC 20 receives a digit from the terminal of the MS 10, hereinafter referred to as a digit, and analyzes it to detect a feature code. The MSC 20 transmits the received digit DGTSDIAL and the Transaction Capablity (TRANSCAP) parameter for transmitting and receiving the general data to the HLR 30 by including it in the FEATREQ signal ( Step b). The HLR 30 displays a prompt for inputting a personal identification number (PIN) of the MS 10, and sends a remote user dialogue instruction (RUIDIR) instructing reception of a digit input from a terminal of the MS 10 (MSID). 20) (step c). The MSC 20 receives the RIDIR and becomes a call connection (step d). The MSC 20 displays a prompt for input of a personal identification number (PIN) on the terminal of the MS 10 according to the digit collection control (DGTCC) parameter, which is information of the RIDIR received in step c. (Step e). The user MS responds with its own personal identification number (PIN) (step f). The MSC 20 sends a remote user interactive instruction (ruidir) including the digit DGTDIAL dialed by the user to the HLR 30 (step g). After verifying the input PIN, the HLR 30 updates the activation state of the selective calling permission (SOA) service of the corresponding MS 10 and adds a FEATRESULT parameter indicating successful add-on operation. Transmits to the MSC 20 an additional function signal comprising a (step h). The MSC 20 provides the add-on check to the corresponding MS 10 as indicated in the add-on signal (step i). The MSC 20 then releases the connected call (step j).

4 is a view for explaining the addition and deletion of a registration number.

The MS 10 sends a feature code to the MSC 20 by pressing the dial of the terminal (step a). The MSC 20 receives a digit from the terminal of the MS 10, hereinafter referred to as a digit, and analyzes it to detect a feature code. The HLR 30 approves the registration change of the called number of the selective calling permission (SOA) service and transmits a remote user interactive instruction (RUIDIR) to the MSC 20 (step c). The MSC 20 receives a remote user interactive instruction (RUIDIR) and answers the call as indicated by the received message (step d). The MSC 20 displays a prompt for input of a personal identification number (PIN) on the terminal of the MS 10 according to the digit collection control (DGTCC) parameter, which is information of the RIDIR received in step c. Wait for digit input (step e). The MS 10 responds by entering its own personal identification number (PIN) (step f). The MSC 20 sends a remote user interactive instruction (ruidir) containing the digit DGTDIAL dialed by the user to the HLR 30 (step g). The HLR 30 sends a remote user interactive instruction (RUIDIR) to the MSC 20 requesting the called party's permission number to add / delete to the calling user (step h). The MSC 20 informs the user of the information carried in the received Remote User Interactive Instruction (RUIDIR) (step i). The MS 10 responds with the desired number to add / delete. When no more add / delete is desired, respond with a fixed digit (add / delete completed digit) (step j). The MSC 20 sends a remote user interactive instruction (ruidir) containing the digit dialed by the user to the HLR 30 (step k). If the digit included in the remote user interactive instruction (ruidir) is a digit added / deleted, the HLR 30 updates the registration information of the SOA service of the corresponding MS 10 and completes the successful add-on ( A function request signal indicating the FEATRESULT is transmitted to the MSC 20. However, if it is not a complete digit, a signal is sent to the MSC 20 requesting the MS 10 to input the number to be added / deleted (step l). If the digit is not completed, steps h to l are repeated. The MSC 20 provides the add-on check to the MS 10 (step m). MSC 20 releases the call (step n).

When a subscriber requests a call for a registered number, the call setup method is the same as a general call setup method, and a call progress for an unregistered number will be described with reference to FIGS. 5 and 6 below. .

FIG. 5 is a diagram illustrating a call progress for an unregistered number, and illustrates a case where a normal call proceeds through a password input.

MS 10 attempts to originate (step a). The MSC 20 may include an Origination Request (ORREQ) including an Origination Request (ORREQ) that indicates that the MS 10 can support dialed digits (DGTDIAL) and a Remote User Interactive Directive (RUIDIR). 30) (step b). The HLR 30 confirms the number, recognizes that a password is required, and sends a Remote User Interactive Instruction (RUIDIR) to the MSC 20 carrying a password request signal (step c). The MSC 20 receives a Remote User Interactive Instruction (RUIDIR) and responds to the call according to the received message (step d). The MSC 20 sends a password request announcement to the MS 10 (step e). MSC 20 returns a password to MS 10 (step f). The MSC 20 sends a remote user interactive instruction (ruidir) including the digit received from the MS 10 to the HLR 30 (step g). The HLR 30 verifies the password on the remote user interactive instruction (ruidir) and then transmits an outgoing request (orreq) including routing information and service confirmation announcement to the MSC 20 (step h). The MSC 20 sends a call permission announcement to the MS 10 as specified in the call request (orreq) (step i). MSC 20 sets up the call (step j).

FIG. 6 is a diagram for explaining call progress for an unregistered number, and illustrates a case where a password input fails. Steps a to g are the same as those shown in FIG. 5, and the HLR 30 confirms that the password of the remote user interactive instruction (ruidir) is not correct and indicates an action code and an outgoing call indicating that the call should be released. An outgoing request (orreq) containing the prohibition announcement is sent to the MSC 20 (step h). The MSC 20 sends a prohibition announcement to the MS 10 (step i). The MSC releases the call (step j).

7 is a flowchart illustrating a method for selectively transmitting call (SOA) service. MS 10 attempts to originate (step 710). The MS 10 determines whether the selective call permission (SOA) is activated (step 720). If SOA is not enabled, call setup is allowed (step 730). However, if SOA is activated, it is determined whether the called number is registered (step 740). If the called number is registered, the flow advances to step 730 to allow call setup. If the called number is not registered, a password input is requested (step 750). It is determined whether the input password and the registered password match (step 760). If the passwords match, the process proceeds to step 730, and if the passwords do not match, the call setup is rejected (step 770).

As described above, the present invention can prevent illegal use of the terminal by the user when the terminal is lost or absent, and can prevent the use of the terminal. In addition, it is possible to block unnecessary transmission in advance by limiting the transmission range of the terminal.

Claims (3)

In the selective transmission allowance service method of a mobile communication system, (a) when the mobile subscriber attempts to make a call, a selective call permission determining step of determining whether the mobile subscriber is in a state of selective call permission (SOA) being activated; (b) allowing the call setup if the selective calling permission (SOA) is in an inactive state, and determining whether the called number is registered if the called number is registered; (c) allowing call setup if the called number is registered, and requesting a password input if the called number is not registered; (d) determining whether the input password matches the registered password; And (e) Selective dialing permit (SOA) method comprising a password comparison step of allowing call setup if the input password and the registered password match, and rejecting call setup if the password does not match. The method of claim 1, wherein step (a) An additional function detecting step of receiving a digit input from the mobile subscriber and analyzing the detected digit code; Requesting entry of a personal identification number in response to the call; And If the inputted personal identification number is a registered user, updating the activation state of the mobile subscriber's selective calling allowance (SOA) service, and providing an add-on check optional SOA characterized in that it comprises a step Way. The method of claim 1, wherein step (a) further comprises adding and deleting registration numbers.