CN1477804A - A Method for Realizing One Machine and Multiple Numbers in Code Division Multiple Access System - Google Patents

Abstract

The invention provides a method for realizing one machine with multiple numbers in a code division multiple access system (CDMA). Each mobile user can be assigned an International Mobile Subscriber Identity (IMSI) and a group of mobile user ISDN corresponding to it. (MSISDN), when starting a mobile communication service, if it is determined that the calling party or the called party is a CDMA standard intelligent network user, the mobile service switching point (MSSP) will hand over the service to the service control point (SCP) for corresponding Business logic processing, after corresponding conversion of the calling party or called party MSISDN, instruct MSSP to use the converted MSISDN as the calling party number or called party number to complete subsequent business processing. As can be seen from the above, the method of the present invention utilizes the intelligent network interconnected with the CDMA mobile network, and regards the multi-number service of one machine as an intelligent service independent of the mobile switching to realize, and has no special effect on network equipment such as current HLR, MSC, etc. Require.

Description

A Method for Realizing One Machine and Multiple Numbers in Code Division Multiple Access System

technical field

The invention relates to a method for distributing mobile subscriber numbers in a code division multiple access (CDMA) system, in particular to a method for enabling one CDMA mobile terminal or mobile phone to have multiple mobile subscriber ISDN numbers.

Background technique

Code Division Multiple Access (CDMA) digital cellular communication system has entered the stage of large-scale application. With the increasingly fierce competition in the communication market, CDMA system operators urgently need to strengthen their own market competitiveness by providing various types of services and increasing network coverage. Because some users may need to use different phone numbers according to different purposes, it is a very popular business to have multiple phone numbers for the same CDMA mobile phone.

In the CDMA call service and other services, the mobile station identity code (IMSI) and the mobile subscriber ISDN (MSISDN) are used to characterize the identity information of each mobile subscriber or mobile station, and they are stored in their respective home location registers (HLRs) as user information. HLR) and have a one-to-one correspondence. In the CDMA system, when a mobile station or a CDMA mobile phone makes a call as a calling party, it first sends a request for access information to the system. After receiving the request information, the system confirms the identity of the mobile station and decides whether to allow access. The Mobile Switching Center (MSC) or Mobile Switching Center + Visitor Location Register (VMSC) to which the mobile station belongs sends a confirmation access request message to the mobile station, and the mobile station initiates a call. And when the mobile station is the called party, the calling party sends the MSISDN of the called party to The HLR to which the called party belongs converts the MSISDN into an IMSI, finds out the service area to which the called party belongs according to the IMSI, and sends the IMSI to the VLR in the area to request allocation of a roaming number (MSRN), and the VLR to which the called mobile station belongs will allocate The MSRN of the caller is sent back to the HLR, and then the HLR sends it to the GMSC or VMSC to which the calling party belongs, so that the GMSC or VMSC of the calling party can be routed to the VMSC of the called party.

In order to make a CDMA mobile phone have multiple MSISDN numbers, the method of dual SIM cards is generally adopted at present, that is, two subscriber identification cards (SIM cards) are installed in a CDMA mobile phone, and each SIM card has different MSISDNs, and Each MSISDN corresponds to a different IMSI. It is worth pointing out that the same user has two MSISDNs and two corresponding IMSIs in the HLR at this time. After the mobile phone is turned on, both MSISDNs are activated and in standby mode. When the user dials as a calling party, he can choose one of the MSISDNs as the calling party number, and when called, both MSISDNs can be used as the receiving party's number.

But there is obvious shortcoming in the method for above-mentioned realization CDMA mobile phone one machine multi-number. Specifically, users must purchase mobile phones that support dual SIM cards to enjoy this service, and the selection of mobile phone purchases is relatively small.

Contents of the invention

The purpose of the present invention is to provide a kind of method that realizes one machine many numbers in code division multiple access system (CDMA), and it does not need mobile user to use double SIM card mobile phone, and does not have special requirement to network equipments such as present HLR, MSC.

According to the method for realizing one machine with multiple numbers in the code division multiple access system (CDMA) of the present invention, wherein, the CDMA mobile communication network is interconnected with the intelligent network, and each mobile user can be assigned an International Mobile Subscriber Identity (IMSI) A group of corresponding mobile subscriber ISDN (MSISDN) becomes a CDMA intelligent network user. The MSISDN belonging to the same group correspond to the same subscription data information in the home location register (HLR) of the CDMA mobile communication network. The difference between IMSI and MSISDN The corresponding relationship between them is stored in the service control point (SCP) of the intelligent network. When the mobile user starts up, he only registers in the corresponding HLR with a number in the MSISDN group assigned by him. When starting a mobile communication service, The system performs the following steps:

(1) The Mobile Service Switching Point (MSSP) of the CDMA mobile communication network determines whether the calling party or the called party is a CDMA intelligent network user according to the subscription data information provided by the HLR;

(2) If it is determined that the calling party or the called party is a CDMA intelligent network user, the MSSP will hand over the service to the SCP for processing; and

(3) The SCP transforms the MSISDNs of the calling party and the called party according to the registration status of the calling party and the called party's MSISDN in the HLR, and instructs the MSSP to use the transformed calling party and called party's MSISDN as the calling party. The caller and called party numbers complete subsequent service processing.

As can be seen from the above, the method for realizing one machine with multiple numbers utilizes the intelligent network interconnected with the CDMA mobile network in the CDMA of the present invention, and regards the one machine with multiple numbers service as an independent intelligent service outside the mobile exchange to realize, to the present There are no special requirements for network equipment such as HLR and MSC.

Description of drawings

Object, feature and advantage of the present invention can be further understood by following detailed description of preferred embodiments of the present invention in conjunction with accompanying drawings, wherein:

Fig. 1 is the calling processing flowchart when using the real number of the mobile subscriber as the calling party number;

Fig. 2 is the calling processing flow chart when using the mobile subscriber's virtual number as the calling party number;

Fig. 3 is the called processing flowchart when using the real number of the mobile subscriber as the called party number; and

Fig. 4 is a flow chart of called processing when the virtual number of the mobile user is used as the called party number.

Detailed ways

In the method for realizing one machine with multiple numbers according to the code division multiple access (CDMA) system of the present invention, the CDMA mobile communication network is interconnected with the intelligent network, and the Mobile Switching Center (MSC) and the Gateway Mobile Switching Center (GMSC) in the mobile communication network ) and mobile switching center + visitor location register (VMSC) can be classified as mobile service switching points (MSSP) due to their mobile service switching functions, while other entities in the mobile network remain unchanged. For each one-machine-multiple-number subscriber, they are all assigned an International Mobile Subscriber Identity (IMSI) and a group of mobile subscriber ISDN (MSISDN) corresponding to it, and the MSISDN belonging to the same group are registered in the home location register ( The HLR) corresponds to the same subscription data information, and the corresponding relationship between the IMSI and the MSISDN is stored in the service control point (SCP) of the intelligent network. Subscription data information includes, but is not limited to, the user's relevant number (IMSI and MSISDN), user category, and intelligent network service supplementary information. It is worth pointing out that the subscription data information of each MSISDN in the same group does not have to be stored in the same HLR, but can be stored in different HLRs. In addition, each MSISDN may belong to a different Service Control Point (SCP).

Under the above-mentioned network structure and mobile subscriber number allocation and registration methods, when starting a service, if the MSSP determines that the calling party or the called party is an ordinary user instead of a CDMA intelligent network user according to the subscription data information, then in the CDMA In the mobile communication network, the service processing is completed according to the service logic that one IMSI corresponds to one MSISDN, and details will not be described here.

If it is determined that the calling party or the called party is a CDMA intelligent network user, the MSSP will hand over the service to the corresponding service control point (SCP) for certain service logic processing. After the SCP makes a corresponding conversion to the MSISDN of the calling party or the called party, it instructs the MSSP to use the converted MSISDN as the calling party number or the called party number to complete subsequent service processing. Specifically, if the SCP determines that the calling party intends to use the MSISDN registered in the HLR as the calling party number or determines that the called party number is an MSISDN registered in the HLR, it instructs the MSSP to use the MSISDN as the calling party number Or the called party number completes the follow-up service processing. If the SCP determines that the calling party intends to use the MSISDN that is not registered in the HLR as the calling party number, it searches for the MSISDN that is to be used as the calling party number according to the corresponding relationship between the IMSI and the MSISDN and Instruct the MSSP to use the searched MSISDN as the calling party number to complete subsequent business processing. If the SCP determines that the called party number is an MSISDN that has not been registered in the HLR, it will search for registrations in the same group in the HLR according to the correspondence between IMSI and MSISDN MSISDN and instructs the MSSP to use the registered MSISDN as the called party number to complete subsequent service processing. The above-mentioned follow-up service processing completed by the MSSP includes switching service processing without the participation of the service control entity in the intelligent network.

The calling party can add a prefix number before the called party number to indicate that the calling party intends to use the MSISDN that is not registered in the HLR as the calling party number, and each prefix number is the same as that of the MSISDN that is not registered in the HLR in the same group. There is one-to-one correspondence between MSISDNs, so the SCP can determine the MSISDN that the calling party intends to enable that is not registered in the HLR according to the prefix number.

As can be seen from the above, in the method of the present invention, each one-machine-multiple-number user is regarded as an intelligent network one-machine multiple-number service user rather than a plurality of mobile network common service users with different MSISDNs, and each one-machine multiple-number service user The service that the machine multi-number user participates in as the calling party or the called party is regarded as an intelligent service and is processed with corresponding business logic.

A specific example of the method according to the invention is described below with the aid of FIGS. 1 to 4 . For the sake of simplicity, assume that a mobile user is assigned an IMSI and two corresponding MSISDNs, and the two MSISDNs are respectively recorded as DN1 and DN2, where DN1 is the home location register HLR1 that stores its subscription information data when the user is turned on. The registered number is called the real number here, and the subscription data of DN2 is the same as that of DN1 and is stored in the home location register HLR2, which is called a virtual number here, and HLR1 and HLR2 may or may not be a home location register. DN1 and DN2 are respectively registered in SCP1 and SCP2 as smart users with multiple numbers in one machine, and SCP1 and SCP2 can be the same or different SCPs. When the calling party wants to use DN2 as the calling party number, add a prefix number before the called party number, for example, 17999.

A. The calling party initiates a call with DN1 as the calling party number

After the user turns on the phone, he registers on HLR1 with DN1, and then HLR1 sends the trigger list to the associated MSC. When the user makes a call with DN1 as the calling party number, that is, directly dials the called number, as shown in Figure 1, the MSC triggers the ORIG_ATTMPT_ATHR trigger and sends an ORREQ message to SCP1 to which DN1 belongs. Real numbers and dialed numbers. If the authentication of the user DN1 is successful, the SCP1 returns the orreq message containing the calling number DN1 and the direct dial number as the called party number to the MSC. MSC triggers the Calling_Routing_ADDR_AVAIL trigger after receiving the orreq message, and sends the ANLYZD message to SCP1. After processing the ANLYZD message, SCP1 sends an anlyzd message to MSC to instruct MSC to use DN1 and the dialed number as the calling party and called party numbers to continue to complete subsequent service processing.

B. The calling party initiates a call with DN2 as the calling party number

After the user turns on the phone, he registers on HLR1 with DN1, and then HLR1 sends the trigger list to the associated MSC. When the user wants to use DN2 as the calling party number, use the special prefix + called number to dial, that is, the dialed number is 17999 + called number. As shown in Figure 2, the MSC triggers the ORIG_ATTMPT_ATHR trigger, and sends an ORREQ message to SCP1 to which DN1 belongs. The message includes the real number of the calling party and the called party number with a special prefix. SCP1 checks the called number and finds that it has a special prefix, so it finds the virtual calling number DN2 and its belonging SCP2 according to the corresponding table between the special prefix and the virtual calling number configured in it.

If SCP1 and SCP2 are the same SCP, then SCP1 will return to MSC an orreq message containing the calling number DN2 and the dialed number without the special prefix as the called party number, the following processing is the same as that of the calling party using DN1 as the calling number Corresponding parts in the processing flow are the same and will not be repeated here.

If SCP1 and SCP2 are not the same SCP, SCP1 will send the orreq message to MSC after successful authentication of user DN1, the message contains calling number DN2, dialed number without prefix, trigger list TriggAddrList2 and instructs MSC to re-trigger ORIG_ATTMPT_ATHR trigger to the parameter RESUMPIC of SCP2. The MSC triggers the ORIG_ATTMPT_ATHR trigger again according to the RESUMPIC parameter and TriggAddrList2 in the orreq message, and sends an ORREQ message to SCP2, in which the calling number is DN2 and the called number is the dialed number without the special prefix. If the SCP2 authenticates the user DN2 successfully, then the SCP2 returns the orreq message containing the calling number DN2 and the direct dial number as the called party number to the MSC. MSC triggers the Calling_Routing_ADDR_AVAIL trigger after receiving the orreq message, and sends the ANLYZD message to SCP2. After SCP2 processes the ANLYZD message, it sends an anlyzd message to the MSC to instruct the MSC to use the DN2 and the dialed number as the calling party and called party numbers to continue to complete subsequent service processing.

C. Call processing flow when the called party uses DN1 as the called party number

As shown in Figure 3, when the GMSC (if the calling party is a fixed subscriber) or MSC (if the calling party is also a mobile subscriber) receives a call whose called party number is DN1, it triggers the Mobile_Termination trigger and sends a LOCREQ message to HLR1 Query the subscription data information of DN1, and HLR1 judges that the mobile user subscribes to the intelligent service, so the locreq message containing the trigger list is sent back to the GMSC. GMSC triggers Init_Termination trigger and sends ANLYZD message to SCP1. After processing the ANLYZD message, SCP1 sends the anlyzd message to the GMSC. The GMSC triggers the LOCATION trigger, and sends a LOCREQ message to HLR1 to request a route to DN1. After receiving the LOCREQ message, HLR1 sends a ROUTREQ to the VMSC to which the called party DN1 belongs, to search for the routing number TLDN of the called party. The VMSC returns the routing number TLDN to the HLR1 through the routreq message, and the HLR1 returns the routing number TLDN to the GMSC through the locreq message. After receiving the locreq message, the GMSC triggers the Calling_Routing_ADDR_AVAIL trigger, and sends the ANLYZD message to SCP1. After processing the ANLYZD message, SCP1 sends an anlyzd message to GMSC to instruct GMSC to use DN1 as the called party number to continue to complete the routing connection to VMSC. When the called party answers, its VMSC triggers the T_Answer trigger and sends a TANSWER message to SCP1. When on-hook, VMSC triggers T_Disconnect trigger, sends TDISCONNECT message to SCP1, and after processing, SCP1 sends tdisconnect message to VMSC as a response.

D. Call processing flow when the called party uses DN2 as the called party number

As shown in Figure 4, when the GMSC (if the calling party is a fixed subscriber) or MSC (if the calling party is also a mobile subscriber) receives a call whose called party number is DN2, the Mobile_Termination trigger is triggered and a LOCREQ message is sent to HLR2 Query the subscription data information of DN2, HLR1 judges that the mobile user subscribes to the smart service, so the locreq message containing the trigger list TriggAddr is sent back to the GMSC. GMSC triggers Init_Termination trigger and sends ANLYZD message to SCP2. SCP2 processes the ANLYZD message and finds that the called number DN2 is a virtual number with multiple numbers on one machine and belongs to SCP2. If SCP1 and SCP2 are the same SCP, then SCP2 will change the called party number in the anlyzd message sent to GMSC to DN1, the following processing is the same as the corresponding part in the above-mentioned processing flow of the called party using DN1 as the calling number, and will not be repeated here. If SCP1 and SCP2 are not the same SCP, then SCP2 will change the called party number to DN1 and add trigger list TriggAddr2 in the anlyzd message sent to GMSC, in which T_ANWSER and T_DISCONNECT triggers are added. After receiving the anlyzd message, the GMSC triggers the LOCATION trigger and sends a LOCREQ message to the HLR1 to which DN1 belongs to request a route to the VMSC to which DN1 belongs. The message includes the called party number DN1. After receiving the LOCREQ message, HLR1 sends a ROUTREQ to the VMSC to which the called party DN1 belongs, to search for the routing number TLDN of the called party. The VMSC returns the routing number TLDN to the HLR1 through the routreq message, and the HLR1 returns the routing number TLDN to the GMSC through the locreq message. After receiving the locreq message, the GMSC triggers the Calling_Routing_ADDR_AVAIL trigger, and sends the ANLYZD message to SCP2. After processing the ANLYZD message, SCP2 sends the anlyzd message to the GMSC to instruct the GMSC to use DN1 as the called party number to continue to complete the routing connection to the VMSC. When the called party answers, the GMSC triggers the T_Answer trigger and sends a TANSWER message to SCP2. And VMSC triggers T_Answer trigger, sends TANSWER message to SCP1, but is discarded by SCP1. When on-hook, GMSC triggers T_Disconnect trigger, sends TDISCONNECT message to SCP2, after processing, SCP2 sends tdisconnect message to GMSC as a response. And VMSC triggers T_Disconnect trigger, sends TDISCONNECT message to SCP1, but is discarded by SCP1.

In the above processing flow where the called party uses DN2 as the called party number, SCP1 discards the received TANSWER and TDISCONNECT messages to prevent invalid operations. Another better way is that when a multi-number user registers on one machine, the HLR does not issue T_ANSWER and T_DISCONNECT triggers to such intelligent users, but always sends these two triggers to the originating MSC by the SCP.

E. Other business

(1) For calling number display, when the calling party uses DN2 as the calling number, the MSC to which the called party belongs shall use the calling party number DN2 included in the SCP delivery operation as the calling number.

(2) For SCP-based forwarding services CFU, CFNA, CFB, and CFD, when DN2 is used as the called party number, although the called party number has been converted by SCP2 to DN1, but since the forwarding trigger still triggers to SCP2, SCP2 stores the information of converting DN2 to DN1, so that the SCP-based forwarding service of the virtual number can still be realized.

(3) For supplementary services such as CW, CC, 3WC, etc., they are similar to the process of calling and calling, so these supplementary services can also be realized under the virtual number.

Claims (12)

1. a kind of method that realizes one machine many numbers in code division multiple access system (CDMA), it is characterized in that, CDMA mobile communication network is interconnected with intelligent network, and each mobile subscriber can be assigned an International Mobile Subscriber Identification Code ( IMSI) and a corresponding group of mobile subscriber ISDN (MSISDN) become CDMA intelligent network users, and the MSISDN belonging to the same group correspond to the same subscription data information in the home location register (HLR) of the CDMA mobile communication network. IMSI and The corresponding relationship between MSISDN is stored in the service control point (SCP) of the intelligent network. When the mobile user starts up, he only registers in the corresponding HLR with a number in the MSISDN group assigned by him. When starting a mobile communication service , the system performs the following steps: (1) The Mobile Service Switching Point (MSSP) of the CDMA mobile communication network determines whether the calling party or the called party is a CDMA intelligent network user according to the subscription data information provided by the HLR; (2) If it is determined that the calling party or the called party is a CDMA intelligent network user, the MSSP will hand over the service to the SCP for processing; and (3) The SCP transforms the MSISDNs of the calling party and the called party according to the registration status of the calling party and the called party's MSISDN in the HLR, and instructs the MSSP to use the transformed calling party and called party's MSISDN as the calling party. The caller and called party numbers complete subsequent service processing. 2. The method according to claim 1, characterized in that the MSISDNs belonging to the same group can be stored in different HLRs. 3. method as claimed in claim 1, is characterized in that, in step (1), if determine that calling party and called party are not CDMA intelligent network user, then in CDMA mobile communication network, correspond to a MSISDN according to an IMSI The business logic completes the mobile communication service. 4. The method according to claim 1, wherein in step (3), the calling party adds a prefix number before the called party number to indicate that the calling party intends to use the MSISDN not registered in the HLR As the calling party number, and each prefix number corresponds to the MSISDN not registered in the HLR in the same group. 5. The method according to any one of claims 1, 2 or 4, wherein in step (3), if the SCP determines that the calling party intends to use the MSISDN registered in the HLR as the calling party number Or determine that the called party number is an MSISDN registered in the HLR, then instruct the MSSP to use the MSISDN as the calling party number or called party number to complete subsequent business processing, if the SCP determines that the calling party intends to use the MSISDN that is not registered in the HLR MSISDN as the calling party number, search for the MSISDN to be used as the calling party number according to the correspondence between IMSI and MSISDN, and instruct the MSSP to use the found MSISDN as the calling party number to complete subsequent service processing, if the SCP determines the called party number If it is an MSISDN not registered in the HLR, search for the MSISDN registered in the HLR in the same group according to the corresponding relationship between IMSI and MSISDN, and instruct the MSSP to complete subsequent service processing with the registered MSISDN as the called party number. 6. The method according to claim 5, wherein the MSSP comprises a Mobile Switching Center (MSC), a Gateway Mobile Switching Center (GMSC) and a Mobile Switching Center+Visitor Location Register (VMSC) in the CDMA mobile communication network. 7. the method for claim 6 is characterized in that, in step (2), if MSSP determines that calling party is a CDMA intelligent network user, then by sending to SCP the ORREQ that comprises calling party and called party number The message and the ANLYZD message hand over the business to the SCP. 8. the method for claim 7 is characterized in that, in step (3), SCP is by sending to MSSP the orreq message and the anlyzd message that comprise the calling party after the conversion process and the called party's number and indicate MSSP to finish follow-up business processing. 9. The method as claimed in claim 8, wherein the calling party intends to use the MSISDN not registered in the HLR as the calling party number and this number is different from the MSISDN registered in the HLR in the same group SCP, then in step (3), when searching for the MSISDN that is intended as the calling party number according to the corresponding relationship between IMSI and MSISDN, the SCP to which the MSISDN registered at the HLR belongs at first sends an orreq message to the MSSP, indicating that the MSSP requests The SCP to which the calling party number belongs searches for the MSISDN to be used as the calling party number according to the correspondence between the IMSI and the MSISDN. 10. The method according to claim 6, characterized in that, in step (2), if the MSSP determines that the called party is a CDMA intelligent network user, then the service is handed over to the SCP by sending an ANLYZD message to the SCP. 11. The method according to claim 10, characterized in that, in step (3), the SCP instructs the MSSP to complete subsequent service processing by sending an onlyzd message comprising the converted calling party and called party numbers to the MSSP. 12. method as claimed in claim 11 is characterized in that, called party number is the MSISDN that is not registered in HLR and this number belongs to different SCP with the MSISDN that has registered in HLR in the same group, then in step In (3), when searching for the MSISDN registered in the HLR in the same group according to the corresponding relationship between IMSI and MSISDN, the SCP to which the called party's MSISDN belongs first sends an anylzd message to the MSSP, indicating that the MSSP requests the registered MSISDN in the HLR The SCP to which the MSISDN belongs searches for the MSISDN to be used as the called party number according to the correspondence between the IMSI and the MSISDN.

Images