CN1929678B - Method and device for updating user terminal access code - Google Patents

Abstract

The invention discloses a method and a device for updating a user terminal access code. The method and the device set a redistribution logic module for realizing redistribution of UE access codes, and preset UE location information and UE access codes in it. After the reassignment logic module obtains the UE location information, it reassigns the UE access code according to the UE's current location information, and synchronizes the reassigned UE access code to the call execution point UE, or the gsmSCF and the UE. The method of the present invention realizes timely reallocation of UE access codes according to UE location information and updates UE current access codes, ensures that VMSC can identify UE access codes, and enables UE to successfully switch to IMS during CS calls, increasing the number of UE access codes. UE satisfaction and enhanced network reliability.

Description

Method and device for updating user terminal access code

technical field

The invention relates to a cross-domain call technology, in particular to a method and a device for updating an access code of a user terminal (UE) when the user terminal (UE) is in a roaming state.

Background technique

Starting from the 3rd Generation Partnership Release 5 (3GPP R5), the core network of the Universal Mobile Telecommunications System (UMTS) is divided into three subsystems: Circuit Switching (CS), Packet Switching (PS) and IP Multimedia Subsystem (IMS). ). Among them, the CS domain (Circuit Switched Domain) is used to provide users with circuit-type service connections, including several main entities such as Mobile Switching Center (MSC), GMSC, and Interoperability Function (IWF) modules, MSC (MSC Server/CS-MGW ) is used to complete the switching and signaling control functions of circuit-switched services; GMSC is an MSC that completes the routing addressing function of mobile users in a certain network, and can be set up together or separately with MSC; IWF is generally closely related to MSC and is used to complete Intercommunication between Public Land Mobile Network (PLMN) and Integrated Services Digital Network (ISDN), Public Switched Communication Network (PSTN), and Packet Data Network (PDN) mainly completes the function of signaling conversion, and the specific function depends on the type of business and network Differently stipulated.

PS domain (Packet Switched Domain) is used to provide users with packet-based service connections, including: GPRS support node (GSN) and border gateway (BG) two types of entities, wherein, GSN is used to complete the transmission of packet service user packets, GSN also includes Serving GPRS Support Node (SGSN) and Gateway GPRS Support Node (GGSN). SGSN provides the connection between the core network and the BSS and RNS in the wireless access system, and completes functions such as mobility management and session management of packet data services. Manage the mobile and communication services of mobile stations (MS) in the mobile network; GGSN serves as the interface between the mobile communication system and other public data networks, and also has the function of querying location information. Both SGSN and GGSN can provide billing information. The BG is used to complete the intercommunication between the two GPRS networks to ensure the security of the network intercommunication.

In addition, the CS domain and the PS domain also share the following functional entities: HLR/AuC, Home Location Register (HLR) is used to complete the management of user subscription data and location information, where user subscription data includes MSISDN, IMSI, PDP ADDRESS , contracted telecommunication services and supplementary services and their scope of application, etc., location information includes MSRN, MSC/VLR number, SGSN number, GMLC, etc.; Authentication Center (AuC) is used to store user authentication algorithms and passwords key. Visitor location register (VLR), used to process various data information of visiting users; EIR, used to store user equipment identification (IMEI) information; and short message center gateway MSC (SMS-GMSC/SMS IMSC) and so on.

IMS (IP Multimedia Subsystem) is a subsystem superimposed on the existing packet domain in the WCDMA network added in the 3GPP R5 stage. The packet domain is used as the bearer channel for upper layer control signaling and media transmission, and the initial session protocol ( As a service control protocol, SIP provides rich multimedia services by separating service control from bearer control by utilizing the features of SIP, which are simple, easy to expand, and convenient for media combination. The main functional entities in IMS include Call Session Control Function (CSCF) which controls functions such as user registration and session control, Application Server (AS) which provides various business logic control functions, and Home Subscriber Server (HSS) which centrally manages user subscription data. ) and the Media Gateway Control Function/IP Multimedia-Media Gateway Function (MGCF/IM-MGW) for interworking with the circuit switched network. The user accesses the IMS through the proxy CSCF (P-CSCF) at the current location, and the trigger control of sessions and services and the service control interaction with the AS are completed by the home domain serving CSCF (S-CSCF) at the user registration location. Among them, the HSS in the IMS is a superset of the HLR and is functionally compatible with the HLR. However, in a specific networking, the HSS and the HLR of the CS/PS are generally set separately.

The IMS architecture defined by the 3GPP standard comprehensively solves the key operational issues such as roaming billing, QoS, and security guarantees required to provide multimedia services under the IP bearer. Its architecture and ideas have been recognized by the industry. 3GPP2 and TISPAN are both The 3GPP model is used as the basis and reference to define the corresponding IP multimedia network architecture and service system. The research on topics such as the all-IP network (AIPN) of access technology enables users to access IMS through a single multi-mode terminal or multiple types of terminals through access networks using different access technologies according to their own subscription information. In order to obtain unified multimedia services including VoIP services. In the process of research on the topic of accessing IMS through different access networks, the problem of business continuity (VCC, Voice Call Continuity) between CS calls and VoIP services provided by accessing IMS through WLAN was raised, and a solution was proposed The issue of CS/IMS inter-domain routing selection when the user is called is to meet the needs of network and business development.

At present, in order to enable the UE to switch to IMS during a CS call, the current handover scheme stipulates that: when the UE is in a CS call, its control part resides in the IMS; in addition, when the UE switches from the IMS to the CS domain during the call , the public service identity (CCCF PSI) of the Call Continuity Control Function (CCCF PSI) is required by the CS part of the UE to perform the handover.

For the case of CS initial call, when CS-IMS user initiates CS establishment, it needs to be routed to the CCCF of the user's home IMS, thereby triggering the routing back-to-back user agent (B2BUA) function on the CCCF to control the bearer plane of the CS call. For the realization of this purpose, there are several implementation schemes as follows:

Solution 1: The CS part of the UE sends a call setup request to the Visited Mobile Switching Center (VMSC) through a Setup message, and the VMSC triggers an Initial DP message to the network-domain selection On the gsm service control function (gsmSCF) entity of NeDS, NeDS sends an IMS routing number (IMRN) pointing to CCCF in IMS to VMSC through CAMEL connect message, and IMRN carries CCCF PSI information, and VMSC according to the received The CCCF PSI routes the call to the MGCF in the IMS domain through the initial address (IAM) message, and the MGCF sends the call to the CCCF according to the IMRN carried in the IAM message, thereby activating the initial static anchor service of the CS in the CCCF. At this time, the CCCF acts as The static anchor point anchors the call, that is, no matter the subsequent caller switches from the CS domain to the IMS domain or from the IMS domain to the CS domain, the static anchor point performs switching processing on the anchored call.

Solution 2: UE converts the PSI stored by itself pointing to the IMS AS CCCF into a call number in the E.164 number format, and sends a call establishment request to the VMSC, thereby routing the call to the CCCF located in the AS. At the same time, the unstructured supplementary service data (USSD) mechanism is used to send the real called party number, called party subaddress, and any other information that needs to complete the call to the called party to the CCCF in the AS, triggering the CS initialization in the AS Static anchor business.

Solution 3: The UE converts the PSI pointing to the IMS AS CCCF stored by itself into a call number in the E.164 number format, and sends a call establishment request to the VMSC, thereby routing the call to the CCCF located in the AS. At the same time, the SIP notification (Notify) mechanism is used to send the real called party number, called party subaddress, and any other information that needs to complete the call to the called party to CCCF in the AS, triggering the CS initial static anchor service in the AS .

Solution 4: The UE uses its internally configured prefix number, cooperates with the called information parameters to form a called number, and sends a call establishment request to the VMSC. The VMSC performs number analysis based on these numbers, so as to route the call to the CCCF located in the AS, and trigger the initial static anchor service of the CS in the AS. It should be noted that: the UE uses its internally configured prefix number, which has a corresponding relationship with the above-mentioned AS PSI or E.164 number.

In addition, when the UE switches from the IMS to the CS domain during the call process, the CS part of the UE sends a call establishment request to the VMSC according to the normal call flow, and the called number carried in the call establishment request is the E number corresponding to the AS PSI. .164 number, where the CCCF is located in the AS of the IMS. After receiving the call request, the VMSC routes the call to the CCCF in the AS of the user's home IMS network according to the E.164 number, thereby performing a corresponding handover process.

It should be noted that the above-mentioned PSI is the PSI of the AS, hereinafter referred to as the AS PSI. In addition, one E.164 number corresponds to one AS PSI, and different MSCs/VLRs correspond to different E.164 numbers or AS PSIs. The E.164 numbers or AS PSIs are referred to as access codes below, and the access codes related to UE The input code is called UE access code.

It can be seen from the above solution that in the prior art, the UE uses the E.164 number format in the CS domain to call the MSC/VLR. When the UE is roaming, the VMSC may use different access numbers depending on the country or region, such as For the fire alarm, it is 119 in China, and it may be 911 in the United States. When the UE roams and attaches to the VMSC, it must use the access number recognized by the local VMSC to access the required services; the access in the VMSC is used for routing analysis The code is pre-configured based on local numbering and routing planning, and cannot be dynamically adjusted in real time. These data are information held by the operator, and the existing solutions for UE handover between the CS domain and the IMS are not based on the location of the UE. The mechanism of updating the UE access code in time, in this way, it is very likely that the VMSC cannot recognize the access code used by the UE, such as the E.164 number or the AS number, because the access code in the UE is inconsistent with the access code in the VMSC. PSI, so that the problem of not being able to perform correct routing for the session occurs, and the UE fails to handover to the IMS during a CS call.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a method for updating the UE access code, which can reallocate and update the UE access code in time, ensure that the VMSC can identify the UE access code, and enable the UE to successfully switch in the CS call to IMS.

Another object of the present invention is to provide a device for updating UE access codes, which can reallocate and update UE access codes in time, ensure that VMSC can identify UE access codes, and enable UE to successfully switch to IMS during a CS call.

In order to achieve the above object, the technical solution of the present invention is specifically realized in the following way:

A method for updating user terminal access codes. A reassignment logic module for reassigning user terminal UE access codes is set, and the corresponding relationship between UE location information and UE access codes is preset in it, and is set for judging whether The reallocation judging module of reallocating new UE access code, the method comprises the following steps:

A11. The reallocation judgment module acquires the update instruction information from the location update response message in the UE location update process; the UE location update process includes:

a. The MSC/VLR to which the UE belongs carries the current location information of the UE in the location update request message, and the reallocation judgment module receives the location update request message, and obtains the current location information of the UE carried in the message, The update request message is forwarded to the home location register HLR;

b. The HLR obtains the current location information of the UE from the received location update request message, and after judging whether the location update is successful, generates and saves update indication information indicating whether the location update is successful and carries it in the location update response message, The reallocation judgment module receives the location update response message, and after obtaining the update indication information carried in the message, forwards the location update response message to the MSC/VLR to which the UE belongs;

A12. If the update indication information shows that the update is successful, the reallocation judging module obtains the current location information of the UE from the location update request message in the UE location update process and sends it to the reallocation logic module;

B. The reassignment logic module reassigns a new UE access code to the UE according to the current location information of the UE and the preset corresponding relationship;

C. The reallocation logic module sends the reallocated UE access code to the call execution point, and the call execution point updates its existing UE access code with the received UE access code.

The entities to which the reallocation judging module and the reallocation logic module belong are both STPs.

The method for the reallocation judgment module in step A12 to send UE current location information to the reallocation logic module is as follows: the reallocation judgment module copies the received location update request message and sends it to the reallocation logic module;

Or carry the acquired current location information of the UE in a custom message and send it to the reallocation logic module.

The entity to which the reallocation judging module belongs is STP; the entity to which the reallocation logic module belongs is HSS or IMS AS.

Described step A11 and step A12 are:

During the UE location update process, the MSC/VLR receives the location update response message from the HLR, and determines that the update indication information carried in the location update response message indicating whether the location update is successful is displayed as a successful update, and the SGSN will carry its own MSC/VLR Temporary Mobile Subscriber Identity MSC/VLR TMSI accepts the location update message and sends it to UE;

After receiving the location update acceptance message, the UE sets a location change identifier and sends it to the reallocation judgment module;

After receiving the location change identifier indicating that the MSC/VLR to which the UE currently belongs has changed, the reallocation judging module obtains the current location information of the UE and sends it to the reallocation logic module.

The method for the UE to send the location change identifier to the reassignment judging module is as follows: the UE carries the set location change identifier in the unstructured supplementary service data USSD and sends it to the reassignment judging module.

The method also includes before: the UE has registered with the IMS according to the agreement, and has subscribed to two-way events with the IMS AS;

The method for the reallocation judging module to receive the location change identifier is as follows: during the UE location update process, after receiving the location update acceptance message, the UE sets the location change identifier and sends it to the reallocation judging module.

The method for the UE to send the location change identifier to the reallocation judgment module is: according to the subscribed two-way event, the UE is triggered to carry the set location change identifier in a SIP notification message or a SIP release message, and send it to Redistribute judgment module.

The method for the reallocation judging module to acquire UE current location information and send it to the reallocation logic module is:

1. the redistribution judgment module carries the preset international mobile subscriber identity IMSI corresponding to the UE in the ATI message and sends it to the HLR;

II.HLR queries the UE current location information corresponding to the IMSI, and carries the UE current location information in the ATI_ack message and sends it to the reallocation judgment module. If the reallocation judgment module checks the received UE current location information and the stored If the local UE location information is inconsistent, the reallocation judging module will send it to the reallocation logic module.

The steps A11 and A12 are: when the reallocation judging module knows that the UE has successfully registered, the reallocation judging module carries the preset international mobile subscriber identity IMSI corresponding to the UE in the ATI message and sends it to the HLR;

The HLR queries the UE current location information corresponding to the IMSI, and carries the UE current location information in the ATI_ack message and sends it to the reallocation judgment module. If the reallocation judgment module checks that the received UE current location information is the same If the UE location information is inconsistent, the reallocation judgment module will send it to the reallocation logic module.

The entities to which the reallocation judging module and the reallocation logic module belong are both STP, or HSS, or IMS AS.

The method for reassigning a new UE access code by the reassignment logic module in step B is as follows: the reassignment logic module selects its own preset UE location that is consistent with the UE current location information according to the received UE current location information The access code corresponding to the information is used as the reassigned UE access code.

The method for sending the UE access code to the call execution point in step C is: the reallocation logic module carries the reallocated UE access code in the USSD, and forwards it to the call execution point via MSC/VLR;

Or the redistribution logic module carries the redistributed UE access code in a SIP notification message and sends it to the call execution point;

Or the reallocation logic module carries the reallocated UE access code in the SIP publish message and sends it to the call execution point.

The UE access code carried in the USSD is an E.164 number; the UE access code carried in the SIP notification message or the SIP announcement message is AS PSI.

The call execution point is UE.

Described step A11 and step A12 are:

When the UE needs to establish a call, the CS part of the UE sends a call establishment request to the VMSC to which it belongs through the Setup message, and the VMSC triggers the initial Initial DP message carrying the current location information of the UE to the NeDS-capable NeDS according to the preset CAMEL subscription information. Redistribution judgment module;

The reallocation judging module receives the UE current location information, and after judging that the UE current location information is inconsistent with its own stored UE location information, sends the UE current location information to the reallocation logic module.

The entities to which the reallocation judging module and the reallocation logic module belong are both gsmSCF.

The reallocation judging module sends the UE current location information carried in the Initial DP message to the reallocation logic module through an existing synchronization mechanism.

The entity to which the reallocation judging module belongs is gsmSCF; the entity to which the reallocation logic module belongs is IMS AS.

The gsmSCF is co-established or separately established with the IMS AS.

The current location information of the UE is the MSC/VLR number of the MSC/VLR to which the UE currently belongs or the VMSC number of the VMSC to which the UE currently belongs.

The method for reassigning a new UE access code by the reassignment logic module in step B is as follows: the reassignment logic module selects its own preset UE location that is consistent with the UE current location information according to the received UE current location information The access code corresponding to the information is used as the reassigned UE access code.

The method for sending the UE access code to the call execution point in step C is: the reallocation logic module carries the reallocated UE access code in the USSD, and forwards it to the first call execution point via the VMSC; or The redistribution logic module carries the redistributed UE access code in the SIP announcement message and sends it to the first call execution point;

When the reassignment logic module is different from the entity to which the reassignment judging module belongs, the reassignment logic module also sends the reassigned UE access code to the second call execution point through the existing synchronization mechanism.

The first call execution point is UE; the second call execution point is gsmSCF.

The UE access code carried in the USSD is an E.164 number; the UE access code carried in the SIP notification message or the SIP announcement message is AS PSI.

If the reallocation logic module has updated the IMS AS as required, before the step A, the method further includes: the reallocation logic module reallocates the IMS AS.

The method for redistributing the IMS AS by the redistribution logic module is: the redistribution logic module redistributes the IMS AS according to the registration status of the user in the IMS,

If the UE is not registered in the IMS, the HSS updates its own initial filtering criterion iFC data according to the updated AS;

If the UE is registered in IMS, and the VCC service of the UE is not occupied in IMS, the IMS AS will carry the user ID and iFC data of the UE in the Profile-Update-Request message, and send the message to the HSS, and the HSS will The UE's user ID and iFC data carried in the Profile-Update-Request message update its own iFC data; then the HSS carries the UE's user ID and iFC data in the Push-Profile-Request message and sends it to the S-CSCF, S- The CSCF updates its own iFC data corresponding to the current user according to the user identifier and iFC data of the UE carried in the Profile-Update-Request message.

If the UE has registered in the IMS, and the VCC service of the UE has been occupied in the IMS, the IMS AS sets a suspension flag indicating that the reallocation of the IMS AS is suspended, and at the same time, the reallocation logic module prohibits the reallocation of the The assigned UE access code is sent to the call execution point until the suspension flag is canceled after the VCC service ends.

In step C, before the reallocation logic module sends the reallocated UE access code to the call execution point, the method also includes:

The reallocation logic module judges whether the redistributed UE access code is consistent with the UE access code stored by itself, if not, then continues to perform step C after storing the redistributed UE access code in itself; if consistent, then End the process of the present invention.

A device for updating a UE access code, the device comprising: a location information sending module for acquiring UE current location information; a reallocation logic module for reallocating UE access codes; A redistribution judging module of the UE access code; and a call execution point for updating the UE access code;

The reallocation judging module obtains the update indication information from the location update response message in the UE location updating process; Obtain the current location information of the UE in the request message and send it to the reallocation logic module; the UE location update process includes: the MSC/VLR to which the UE belongs carries the current location information of the UE in the location update request message, and the reallocation judgment module After receiving the location update request message and obtaining the current location information of the UE carried in the message, forward the location update request message to the HLR; the HLR obtains the location update request message from the received location update request message The current location information of the UE, after judging whether the location update is successful, generates and saves the update indication information indicating whether the location update is successful and carries it in the location update response message, and the reallocation judging module receives the location update response message and obtains the After carrying the update indication information, forward the location update response message to the MSC/VLR to which the UE belongs; or,

During the UE location update process, the MSC/VLR receives the location update response message from the HLR, and determines that the update indication information carried in the location update response message indicating whether the location update is successful is displayed as a successful update, and the SGSN will carry its own The location update acceptance message of the temporary mobile subscriber identity MSC/VLR TMSI of MSC/VLR is sent to the UE; after receiving the location update acceptance message, the UE sets the location change identification and sends it to the reallocation judgment module; the reallocation judgment After the module receives the location change identifier indicating that the MSC/VLR to which the UE currently belongs has changed, it obtains the current location information of the UE and sends it to the reallocation logic module; or,

When the reallocation judgment module knows that the UE has successfully registered, the reallocation judgment module carries the preset international mobile subscriber identity IMSI corresponding to the UE in the ATI message and sends it to the HLR; the HLR queries the current location of the UE corresponding to the IMSI information, and carry the UE current location information in the ATI_ack message and send it to the reallocation judgment module. If the reallocation judgment module checks that the received UE current location information is inconsistent with the locally stored UE location information, the reallocation judgment module will be sent to the reallocation logic module; or,

When the UE needs to establish a call, the CS part of the UE sends a call establishment request to the VMSC to which it belongs through the Setup message, and the VMSC triggers the initial Initial DP message carrying the current location information of the UE to the NeDS-capable NeDS according to the preset CAMEL subscription information. A reallocation judging module; the reallocation judging module receives UE current location information, and after judging that the UE current location information is inconsistent with its own stored UE location information, sends the UE current location information to the reallocation logic module;

The reallocation logic module receives the UE current location information from the location information sending module, allocates a new UE access code for the UE according to the preset corresponding relationship and the obtained UE current location information, and connects the new UE to the UE. The code is sent to the call execution point, and the call execution point uses the received UE access code to update its existing UE access code.

The reallocation logic module is further provided with a comparison module, which is used to determine whether the new UE access code is consistent with the UE access code stored in itself, and send the new UE access code to the caller if they are inconsistent. execution point.

The call execution point is UE, or UE and gsmSCF.

The entity to which the reallocation logic module belongs is HSS, and the entity to which the reallocation judgment module belongs is HLR;

Or the entity to which the reallocation logic module belongs is HSS or IMS AS, and the entity to which the reallocation judgment module belongs is STP;

Or the entity to which the reallocation logic module belongs is IMS AS, and the entity to which the reallocation judgment module belongs is gsmSCF;

Or the entities to which the reallocation judging module and the reallocation logic module belong are both gsmSCF;

Or the entities to which the reallocation logic module and the reallocation judgment module belong are both STP, or HSS, or IMS AS.

It can be seen from the above technical solution that the present invention presets the corresponding relationship between the MSC/VLR number and the UE access code in the reallocation logic module for redistribution of the UE access code. When the UE roams and the AS remains unchanged, the After the reallocation logic module obtains the UE location information, it re-allocates the UE access code according to the UE current location information, that is, the AS PSI or E.164 number, and sends the re-allocated UE access code to the call execution point such as the UE, or gsmSCF and UE, the call execution point is updated according to the received UE access code.

In addition, when the UE roams and needs to change the AS, the reassignment logic module of the present invention first reassigns the AS according to the status of the UE in the IMS, and then reassigns the UE according to the above method of reassigning the UE access code based on the current location information of the UE. access code, and send the reassigned UE access code to the call execution point UE, or the gsmSCF and the UE, and the call execution point updates according to the received UE access code.

In addition, in the method for updating the UE access code of the present invention, after the reallocation logic module reallocates the UE access code, the method of the present invention further includes: the reallocation logic module judges that the currently allocated UE access code is different from the locally stored Whether the UE access code is consistent, if not, continue the method of the present invention to send the reallocated UE access code to the UE; if consistent, the reallocation logic module ends the process of the present invention.

The redistribution logic module of the method of the present invention redistributes the UE access code in time according to the UE location information, realizes the update of the current UE access code, and ensures that the VMSC at the place where the UE visits can identify the UE access code, so that the UE is in CS The call was successfully switched to IMS, and the VCC service was used smoothly, which increased user satisfaction and enhanced network reliability.

Description of drawings

Fig. 1 is a flow chart of updating UE access number in the present invention;

Fig. 2 is a flowchart of Embodiment 1 of the present invention;

Fig. 3 is the flowchart of the second embodiment of the present invention;

FIG. 4 is a flowchart of Embodiment 4 of the present invention;

Fig. 5 is a flowchart of Embodiment 5 of the present invention;

FIG. 6 is a flowchart of Embodiment 6 of the present invention;

FIG. 7 is a flowchart of Embodiment 7 of the present invention;

FIG. 8 is a flow chart of Embodiment 8 of the present invention;

FIG. 9 is a flow chart of Embodiment 9 of the present invention;

Fig. 10 is a flowchart of Embodiment 10 of the present invention;

Fig. 11 is a flowchart of Embodiment 11 of the present invention;

Fig. 12 is a flowchart of Embodiment 12 of the present invention;

Fig. 13 is a flowchart of Embodiment 13 of the present invention;

FIG. 14 is a schematic structural diagram of an apparatus for updating a UE access number according to the present invention.

Detailed ways

The core idea of the present invention is to pre-set a redistribution logic module for redistribution of UE access codes, and the redistribution logic module redistributes UE access codes according to the acquired UE location information, It is sent to the call execution point, and the call execution point updates according to the received UE access code. The method further presets a re-allocation judging module for judging whether to re-allocate the UE access code, and sends UE current location information to the re-allocation logic module after the re-allocation judging module judges to re-allocate the UE access code.

Figure 1 is a flow chart of updating UE access numbers in the present invention, assuming that the corresponding relationship between different MSC/VLR numbers and UE access codes is preset in the reallocation logic module for realizing UE access code reallocation, and the UE occurs In the case of roaming and AS unchanged, the method of the present invention mainly includes the following steps:

Step 100: The reallocation logic module acquires UE location information.

The UE location information is generally determined by the VMSC number. If the VMSC number changes, it means that the UE location has changed and the MSC/VLR to which the UE belongs has changed. Different MSC/VLRs are identified by different MSC/VLR numbers. When the MSC/VLR is in a visiting location, the MSC/VLR can be called a VMSC.

According to the agreement, when the location of the UE changes, the location update process will be triggered: the MSC/VLR to which the UE currently belongs will initiate a location update request to the HLR carrying the MSC/VLR number of the MSC/VLR to which the UE currently belongs, and the HLR will return the MSC/VLR to the HLR. The location update response of the VLR will carry the update instruction information indicating whether the location update is successful. If the update instruction information shows that the location update is successful, the MSC/VLR will carry its own Temporary Mobile Subscriber Identity (TMSI) in the location update acceptance message via the SGSN. In this way, the UE can access the network through the MSC/VLR corresponding to the received TMSI. The specific implementation of the location update process can be found in relevant protocols, and will not be repeated here.

Based on the above-mentioned existing location update process, the method for obtaining UE location information by the reallocation logic module of the present invention is roughly divided into:

Method 1: The reassignment judging module for judging whether to reassign the UE access code obtains update indication information indicating whether the location update is successful from the location update response message, and if the update indication information shows that the update is successful, the reassignment judgment The module determines that the MSC/VLR to which the UE belongs has changed, and sends the MSC/VLR number obtained from the location update request message to the reallocation logic module.

Method 2: After receiving the location update acceptance message, the UE sets a location change flag indicating that the MSC/VLR to which the UE currently belongs has changed, and sends the set location change flag to the reassignment judgment module. After that, the reassignment judgment module can The MSC/VLR number of the MSC/VLR to which the UE currently belongs is obtained from the HLR, and the obtained MSC/VLR number is sent to the reallocation logic module.

Method 3: When the UE needs to establish a call, the reallocation judgment module can obtain the MSC/VLR number of the MSC/VLR to which the UE currently belongs from the initial Initial DP message, and determine that the MSC/VLR number is inconsistent with the MSC/VLR number stored by itself After that, send the obtained MSC/VLR number to the reallocation logic module.

Wherein, the reallocation judging module and the reallocation logic module may be located in different entities, or in the same entity. When the reallocation judging module and the reallocation logic module can be located in different entities, the entities to which the reallocation judging module belongs are: HLR, gsmSCF or redistribution for intercepting location update request messages and location update response messages between MSC/VLR and HLR Judgment module, such as CS domain signaling transfer point (STP), etc.; the entities to which the redistribution logic module belongs are: HSS, IMS AS, etc. When the reallocation judgment module and the reallocation logic module can be located in the same entity, the reallocation judgment module and the reallocation logic module belong to the same entity: HSS, STP, HLR, IMS AS, gsmSCF, etc.

For specific implementation, refer to Embodiment 1 to Embodiment 12 below, which will not be described in detail here.

Step 101: The reassignment logic module reassigns the UE access code according to the UE's current location information and its own preset information.

The preset information in the reallocation logic module has the corresponding relationship between different MSC/VLR numbers and UE access codes. /VLR is inconsistent, then the reassignment logic module reassigns the UE access code; otherwise, ends the current processing flow.

Step 102: The reallocation logic module sends the reallocated UE access code to the call execution point, and the call execution point updates the local existing UE access code with the received UE access code.

Here, the call execution point is UE, or gsmSCF and UE.

It should be noted that, since multiple MSC/VLR numbers correspond to the same UE access codes in practical applications, in the method for updating UE access codes of the present invention, the above steps re-allocate UE access codes in the reallocation logic module. Afterwards, the method of the present invention further includes: the reallocation logic module judges whether the currently allocated UE access code is consistent with the locally stored UE access code, and if not, continues the method of the present invention to send the reallocated UE access code to the UE; if consistent, the reallocation logic module ends the process of the present invention.

In addition, if the reallocation logic module updates the IMS AS as needed, that is, when the UE roams and the AS changes, before step 100 shown in FIG. Allocate the IMS AS of the UE, and the specific implementation includes:

1) If the UE is not registered in the IMS, the HSS performs the AS reallocation operation.

2) If the UE has registered in IMS, and the VCC service of the UE is not occupied in the IMS AS, then the IMS AS performs the AS reallocation operation.

It should be noted that if the UE has registered in IMS and the VCC service of the UE is occupied in IMS, in order to avoid error processing caused by changing the IMS AS in the VCC service, the IMS AS sets the suspend flag to suspend the reallocation of the IMS AS. Therefore, the reallocation logic module will not synchronize the UE access code obtained through the above reallocation to the call execution point. When the VCC service of the UE is not occupied by the IMS AS, cancel the suspension flag and perform the corresponding AS reallocation process. The specific implementation may refer to the following, and will not be described in detail here.

Fig. 14 is a schematic structural diagram of a device for updating UE access codes in the present invention. It can be seen from Fig. 14 that the device for updating UE access codes in the present invention includes: a location information sending module for obtaining UE current location information, and for reassigning UE access The code-entry redistribution logic module, and the call execution point for updating the UE access code, the redistribution logic module receives the UE current location information from the location information sending module, and according to the preset corresponding relationship and the obtained UE current location information The UE allocates a new UE access code, and sends the new UE access code to the call execution point, and the call execution point uses the received UE access code to update its existing UE access code. The call execution point is UE, or UE and gsmSCF.

The device also includes: a reassignment judging module for judging whether to reassign a new UE access code, and the reassignment judging module notifies the location information sending module to obtain UE current location information after receiving the information that the UE location changes.

In addition, the redistribution logic module is further provided with a comparison module, which is used to determine whether the new UE access code is consistent with the UE access code stored in itself, and send the new UE access code to the caller if they are inconsistent. execution point.

To make the purpose, technical solutions and advantages of the present invention more clear, the present invention will be further described in detail below with reference to the accompanying drawings and preferred embodiments.

Fig. 2 is a flow chart of Embodiment 1 of the present invention. In this embodiment, the entity to which the redistribution logic module belongs is HSS, the entity to which the redistribution judgment module belongs is STP, and the AS has not changed; assume that different MSCs/VLRs are preset in the HSS The corresponding relationship between the number and the UE access code, and the position of the UE has changed. According to the agreement, after the MSC/VLR receives the routing update request sent by the UE, the method includes the following steps:

Steps 200 to 203: STP intercepts the location update request (MAP_UPDATE_LOCATION) message and location update response (MAP_UPDATE_LOCATION_ack) message between the MSC/VLR and the HLR.

According to the agreement: the MAP_UPDATE_LOCATION message carries the MSC/VLR number of the MSC/VLR to which the UE currently belongs, that is, the new VMSC number after the UE's location changes; the MAP_UPDATE_LOCATION_ack message carries the update indication information indicating whether the location update is successful: if the update indication If the information shows that the update is successful, it indicates that the current location update of the UE is successful; if the update indication information shows that the update fails, it indicates that the current location update of the UE fails.

Step 204: After the STP detects that the location of the UE has changed, it forwards the VMSC number carried in the intercepted MAP_UPDATE_LOCATION message to the HSS.

If STP detects that the update indication information carried in the MAP_UPDATE_LOCATION_ack message shows that the location update is successful, it means that the MSC/VLR to which the UE belongs has changed. At this time, STP can forward the VMSC number to the HSS through a customized message, or copy a A copy of the intercepted MAP_UPDATE_LOCATION message is forwarded to the HSS.

In this embodiment, the STP forwards the VMSC number to the HSS by copying the intercepted MAP_UPDATE_LOCATION message.

Step 205: The HSS reassigns the UE access code according to the received VMSC number and the access codes corresponding to different MSC/VLR numbers preset in the HSS.

Generally, if the UE access code is sent to the UE by USSD, the reassigned UE access code refers to the E.164 number; and when the UE access code is sent to the UE through the IMS message, the reassigned UE access code refers AS PSI.

It should be noted that in the reallocation logic module, the access codes corresponding to different MSC/VLR numbers can be E.164 numbers or AS PSI. Then, (1) when the redistributed UE access code needs to be an E.164 number, if the access code stored in the reallocation logic module is an E.164 number, it can be used directly; If the access code is AS PSI, the redistribution logic module converts the AS PSI into an E.164 number before using it. (2) The redistributed UE access code needs to be AS PSI. If the access code stored in the reallocation logic module is AS PSI, it can be used directly; if the access code stored in the reallocation logic module is an E1164 number, then The redistribution logic module converts the E.164 number into AS PSI before using it. The corresponding relationship between the E.164 number and the AS PSI belongs to the prior art, and will not be repeated here.

In this step, assuming that the access code stored in the HSS is an E.164 number, then, according to the new VMSC number, the HSS selects the E.164 number corresponding to the MSC/VLR number preset in the HSS that is consistent with the new VMSC number, as Reassigned UE access code.

Steps 206 to 207: HSS carries the reassigned E.164 number in USSD, forwards it to UE via MSC/VLR, and UE updates the local E.164 number.

Fig. 3 is the flow chart of the second embodiment of the present invention, in this embodiment, the entities to which the redistribution logic module and the redistribution judgment module belong are both HSS, and the AS has not changed; it is assumed that different MSC/VLR numbers and UEs are preset in the HSS The corresponding relationship of the access code; the UE position has changed, according to the agreement, after the MSC/VLR receives the routing update request sent by the UE, the method includes the following steps:

Steps 300 to 302: exchange MAP_UPDATE_LOCATION messages and MAP_UPDATE_LOCATION_ack messages between MSC/VLR and HLR; at the same time, MSC/VLR forwards the location update reception (LOCATION_UPDATING_ACCEPT) message to UE via SGSN. In FIG. Forwarded to UE, not sent directly from MSC/VLR to UE.

According to the protocol: MSC/VLR TMSI is carried in the LOCATION_UPDATING_ACCEPT message.

Step 303: After learning that its location has changed, the UE notifies the HSS through the USSD.

The UE checks whether the MSC/VLRTMSI carried in the LOCATION_UPDATING_ACCEPT message is consistent with the MSC/VLR TMSI stored by itself. If not, it means that the MSC/VLR to which the UE belongs may have changed, and the UE sets a location change flag indicating that its current location has changed. And carry it in USSD and send it to HSS.

Steps 304 to 306: After the HSS receives the USSD from the UE and determines that the MSC/VLR to which the UE belongs has changed, the HSS uses the new VMSC number of the MSC/VLR to which the UE currently belongs and the different MSC/VLR numbers preset in the HSS. Enter the code and reassign the UE access code.

The method for the HSS to determine whether the MSC/VLR to which the UE belongs is as follows: the HSS carries the International Mobile Subscriber Identity (IMSI) of the UE in the ATI message, and sends the ATI message to the HLR for query, and the HLR will correspond to the MSC/VLR of the IMSI. The VLR number is carried in the ATI_ack and returned to the HSS; the HSS checks whether the received MSC/VLR number is consistent with the locally stored MSC/VLR number corresponding to the UE. If not, it means that the MSC/VLR to which the UE belongs has changed. At this time, the current new VMSC number of the UE is the MSC/VLR number carried in the ATI_ack.

In this step, assuming that the access code stored in the HSS is an E.164 number, then, according to the new VMSC number, the HSS selects the E.164 number corresponding to the MSC/VLR number preset in the HSS that is consistent with the new VMSC number, as Reassigned UE access code.

Step 307-Step 308: HSS carries the re-assigned E.164 number in USSD, forwards it to UE via MSC/VLR, and UE updates the local E.164 number.

Embodiment 3: The entity to which the re-allocation logic module and the re-allocation judgment module belong is both the HSS, and the AS has not changed. The UE can also initiate registration to trigger the update of the UE access code. When the HSS learns that the UE has successfully registered, the HSS uses the methods described in steps 304 to 306 to determine that the MSC/VLR to which the UE belongs changes and then reassigns the UE access code, and reassigns the obtained E.164 The number is sent to the UE in steps 307 to 308, and the UE updates the local E.164 number. It should be noted that if the UE is initially registered, that is, there is no location information of the UE before registration in the HSS, then the HSS directly reassigns the UE access code according to the current location information of the UE obtained in steps 304 to 306 . Here, the UE registration process and the HSS knowing that the UE has successfully registered belong to the existing known technology, which can be referred to related protocols, and will not be repeated here.

The UE initiates the registration, and the I-CSCF queries the HSS after receiving the registration message, obtains the S-CSCF name or S-CSCF capability set, and continues the registration process. After the HSS knows that the UE has registered, the HSS uses steps 304 to 306 The method described in determines that the MSC/VLR to which the UE belongs changes and reassigns the UE access code, and sends the reassigned E.164 number to the UE using steps 307 to 308, and the UE updates the local E.164 number .

Fig. 4 is a flow chart of Embodiment 4 of the present invention. In this embodiment, the entity to which the redistribution logic module and the redistribution judgment module belong is the same IMS AS, and the AS has not changed; it is assumed that different MSC/VLR numbers are preset in the IMS AS The corresponding relationship with the UE access code; and assuming that the UE has registered with the IMS according to the protocol, after the S-CSCF returns a successful registration response to the UE, it will make a routing policy decision according to the initial filter criterion (iFC) data in the UE subscription data The AS of the point initiates the third-party registration, and the IMS AS as the routing policy decision point returns a registration success response. Afterwards, UE and IMS AS bidirectionally carry out event subscription (SUBSCRIBE), and this method also includes the following steps:

Step 400-Step 401: During the existing UE location update process, after the UE receives the location update acceptance message, it sets the location change flag indicating that its current location has changed. Event subscription, thus triggering the UE to carry the location change identifier in the SIP Notify (Notify) message and send it to the IMS AS.

When the UE registers, the IMS AS and the UE perform two-way event subscription. Therefore, after the location of the UE is updated, the UE can know from the IMS AS that the MSC/VLR it currently belongs to may have changed through the event subscription.

Step 402: After the IMS AS receives the SIP Notify message from the UE and determines that the MSC/VLR to which the UE belongs has changed, according to the new VMSC number of the MSC/VLR to which the UE currently belongs and the different MSC/VLR numbers preset in the IMS AS Access code, reassign the UE access code.

In this step, the method for the IMS AS to determine whether the MSC/VLR to which the UE belongs is completely consistent with that of steps 304 to 306. It is only necessary to change the reallocation logic module in steps 304 to 306 to IMS AS, which will not be repeated here. .

In addition, in this step, assuming that the access code stored in the IMS AS is the AS PSI, then, according to the new VMSC number, the IMSAS selects the AS PSI corresponding to the MSC/VLR number preset in the IMS AS that is consistent with the new VMSC number, as Reassigned UE access code.

Step 403: The IMS AS carries the reallocated AS PSI in the SIP Notify message and forwards it to the UE, and the UE updates the local AS PSI.

Fig. 5 is a flow chart of Embodiment 5 of the present invention. In this embodiment, the entity to which the redistribution logic module and the redistribution judgment module belong is the same IMS AS, and the AS has not changed; assume that different MSC/VLR numbers are preset in the IMS AS The corresponding relationship with the UE access code; and assuming that the UE has registered in the IMS according to the agreement and the UE and the IMS AS perform two-way event subscription; the method also includes the following steps:

Steps 500 to 501: During the existing UE location update process, after the UE receives the location update acceptance message, it sets the location change flag indicating that its current location has changed. Event subscription, thus triggering the UE to carry the location change identifier in the SIP Notify (Notify) message and send it to the IMS AS.

Step 502: After the IMS AS receives the SIP PUBLISH message from the UE and determines that the MSC/VLR to which the UE belongs has changed, according to the new VMSC number of the MSC/VLR to which the UE currently belongs and the different MSC/VLR numbers preset in the IMS AS Access code, reassign the UE access code.

The specific implementation method of this step is the same as that of step 402, and will not be repeated here.

Step 503: The IMS AS carries the reallocated AS PSI in the SIP PUBLISH message and forwards it to the UE, and the UE updates the local AS PSI.

The difference between Embodiment 5 and Embodiment 4 is that in Embodiment 4, the IMS AS carries the reallocated AS PSI in the SIP Notify message and forwards it to the UE; in Embodiment 2, the reallocated AS PSI is carried in the SIP PUBLISH message and forwards to UE.

Fig. 6 is a flow chart of Embodiment 6 of the present invention. In this embodiment, the entity to which the reallocation logic module belongs is IMS AS, the entity to which the reallocation judgment module belongs is STP, and the AS has not changed; assuming that different MSC/MSCs are preset in the IMSAS The corresponding relationship between the VLR number and the UE access code, the position of the UE has changed, according to the agreement, after the MSC/VLR receives the routing update request sent by the UE, the method includes the following steps:

Step 600-Step 603: The CS domain STP intercepts the MAP_UPDATE_LOCATION message and MAP_UPDATE_LOCATION_ack message between the MSC/VLR and the HLR.

The implementation of this step is completely consistent with that of steps 200 to 203, and will not be repeated here.

Step 604: After the STP detects that the location of the UE has changed, it sends the new VMSC number carried in the intercepted MAP_UPDATE_LOCATION message to the IMS AS in the SIP PUBLISH message.

Step 605: The IMS AS reassigns the UE access code according to the received new VMSC number and the access codes corresponding to different MSC/VLR numbers preset in the IMS AS.

The reallocation method is exactly the same as that in step 205, and will not be repeated here.

In this step, it is assumed that the access code stored in the IMS AS is AS PSI.

Step 606: The IMS AS carries the reallocated AS PSI in the SIP PUBLISH message and forwards it to the UE, and the UE updates the local AS PSI.

7 is a flow chart of Embodiment 7 of the present invention. In this embodiment, the entity to which the reallocation logic module and the reallocation judgment module belong is the same STP, and the AS has not changed; it is assumed that different MSC/VLR numbers and UEs are preset in the STP. The corresponding relationship of the access code, the position of the UE has changed, according to the agreement, after the MSC/VLR receives the routing update request sent by the UE, the method includes the following steps:

Steps 700 to 703: STP intercepts the digital MAP_UPDATE_LOCATION message and MAP_UPDATE_LOCATION_ack message between the MSC/VLR and the HLR.

The specific implementation of this step is completely consistent with that of steps 200 to 203, and will not be repeated here.

Step 704: After the STP detects that the location of the UE has changed, it obtains the new VMSC number from the intercepted MAP_UPDATE_LOCATION message, and reassigns it according to the new VMSC number and the access codes corresponding to different MSC/VLR numbers preset in the STP UE access code

The method for the STP to detect whether the location of the UE has changed is exactly the same as that in step 204, and will not be repeated here.

In this step, it is assumed that the access code stored in the STP is an E.164 number.

Step 705 - Step 706: STP carries the reassigned E.164 number in the USSD and forwards it to the UE via the MSC/VLR, and the UE updates the local E.164 number.

Fig. 8 is a flow chart of Embodiment 8 of the present invention. In this embodiment, the entities to which the redistribution logic module and the redistribution judgment module belong are both STPs, and the AS has not changed; assuming that different MSC/VLR numbers and UEs are preset in the STP The corresponding relationship of the access code, the position of the UE has changed, according to the agreement, after the MSC/VLR receives the routing update request sent by the UE, the method includes the following steps:

Step 800-Step 802: exchange MAP_UPDATE_LOCATION message and MAP_UPDATE_LOCATION_ack message between MSC/VLR and HLR; at the same time, MSC/VLR forwards location update receiving (LOCATION_UPDATING_ACCEPT) message to UE via SGSN. .

The implementation of this step is completely consistent with that of steps 300 to 302, and will not be repeated here.

Step 803: After learning that its location has changed, the UE notifies the STP through the USSD.

The specific implementation of this step is exactly the same as that of step 303, only need to replace the HSS in step 303 with STP, which will not be repeated here.

Steps 804 to 806: After the STP receives the USSD from the UE and determines that the MSC/VLR to which the UE belongs has changed, the STP corresponds to the new VMSC number of the MSC/VLR to which the UE currently belongs and the different MSC/VLR numbers preset in STP. Enter the code and reassign the UE access code.

The specific implementation of this step is exactly the same as that of steps 304 to 306, and it is only necessary to replace the HSS in steps 304 to 306 with STP, which will not be repeated here.

Steps 807 to 808: STP carries the reassigned E.164 number in the USSD and forwards it to the UE via the MSC/VLR, and the UE updates the local E.164 number.

Fig. 9 is a flow chart of Embodiment 9 of the present invention. In this embodiment, the entity to which the redistribution logic module belongs is HSS, the entity to which the redistribution judgment module belongs is HLR, and the AS is changed; assuming that different MSC/VLRs are preset in the HSS The corresponding relationship between the number and the UE access code, and the position of the UE has changed. According to the agreement, after the MSC/VLR receives the routing update request sent by the UE, the method includes the following steps:

Step 900-901: exchange MAP_UPDATE_LOCATION message and MAP_UPDATE_LOCATION_ack message between MSC/VLR and HLR.

Step 902: After the HLR detects that the location of the UE has changed, the HLR forwards the new VMSC number carried in the received MAP_UPDATE_LOCATION to the HSS.

In this step, the HLR detects whether the MSC/VLR number corresponding to the UE stored in itself has changed.

In this embodiment, the HLR forwards the received MAP_UPDATE_LOCATION to the HSS.

Step 903: The HSS reassigns the UE access code according to the new VMSC number carried in the received MAP_UPDATE_LOCATION and the access codes corresponding to different MSC/VLR numbers preset in the HSS.

In this step, it is assumed that the access code stored in the HSS is an E.164 number.

Step 904 - Step 905: HSS carries the re-assigned E.164 number in USSD, forwards it to UE via MSC/VLR, and UE updates the local E.164 number.

Fig. 10 is a flow chart of Embodiment 10 of the present invention. In this embodiment, the entity to which the redistribution logic module and the redistribution judgment module belong is the same HLR, and the AS has not changed; it is assumed that different MSC/VLR numbers and UEs are preset in the HLR. The corresponding relationship of the access code, the position of the UE has changed, according to the agreement, after the MSC/VLR receives the routing update request sent by the UE, the method includes the following steps:

Step 1000 - Step 1001: exchange MAP_UPDATE_LOCATION message and MAP_UPDATE_LOCATION_ack message between MSC/VLR and HLR.

Step 1002: The HLR reassigns the UE access code according to the new VMSC number corresponding to the VMSC to which the UE belongs after the location update, and the access codes corresponding to different MSC/VLR numbers preset in the HLR.

The HLR knows whether the VMSC of the current UE has changed. If there is a change, the HLR will reassign the UE access code according to the new VMSC number carried in the received MAP_UPDATE_LOCATION message and the access code corresponding to the different MSC/VLR number preset in the HLR. Encode.

In this step, it is assumed that the access code stored in the HLR is an E.164 number.

Step 1003 - Step 1004: HSS carries the reassigned E.164 number in USSD, forwards it to UE via MSC/VLR, and UE updates the local E.164 number.

The above-mentioned embodiments 1 to 9 of the present invention are proposed in view of the schemes 2, 3 and 4 in the prior art. In this way, when the UE sends the call establishment request again, the local updated E.164 number is used, and the The call establishment request is sent to the VMSC, which ensures that the VMSC correctly routes the call according to the new E.164 number.

Fig. 11 is a flow chart of the eleventh embodiment of the present invention. The flow shown in Fig. 11 is proposed for the solution 1 of implementing a call in the prior art. The main idea is to update the UE access code before the UE establishes a call connection, so that the UE uses The access code corresponding to the current location establishes a call connection, thereby ensuring the correctness of call routing. The UE includes an IMS part and a CS part. In this embodiment, the entities to which the reallocation logic module and the reallocation judgment module belong are both gsmSCF; assuming that the corresponding relationship between different MSC/VLR numbers and UE access codes is preset in the gsmSCF, the specific implementation of the tenth embodiment includes the following steps:

Steps 1100 to 1102: The CS part of the UE sends a call setup request to the VMSC through a Setup message, and the VMSC triggers an Initial DP message to the gsmSCF module with the NeDS function according to the CAMEL subscription information, and sends an executing message to the CS part of the UE. Call Proceeding messages.

The Initial DP message carries the location information of the UE, such as the VMSC number, the CELL number, etc., and the gsmSCF stores the MSC/VLR number of the MSC/VLR to which the UE belongs before this call.

Step 1103: If the gsmSCF determines that the VMSC number carried in the Initial DP message is inconsistent with the locally stored MSC/VLR number, then the gsmSCF uses the VMSC number carried in the Initial DP message and the corresponding MSC/VLR number preset in gsmSCF Access code, reassign the UE access code.

In this step, it is assumed that the access code stored in the gsmSCF is an E.164 number.

Step 1104 ~ Step 1105: gsmSCF saves the reassigned E.164 number and carries the E.164 number in the CAMEL connect message, sends it to MSC/VLR, and at the same time gsmSCF carries the reassigned E.164 number in USSD and sends it For the UE, the UE updates the local E.164 number.

Steps 1106 to 1107: VMSC routes the call to the MGCF in the IMS domain through the IAM message according to the received E.164 number, and the MGCF sends the call to the correct AS according to the E.164 number carried in the IAM message.

Such processing ensures that the call is switched by the correct AS.

Fig. 12 is a flow chart of Embodiment 12 of the present invention. The flow shown in Fig. 12 is proposed for solution 1 of implementing a call in the prior art. The main idea is to update the UE access code before the UE establishes a call connection, so that the UE uses The access code corresponding to the current location establishes a call connection, thereby ensuring the correctness of call routing. The UE includes an IMS part and a CS part. In this embodiment, the entity to which the redistribution logic module belongs is the IMS AS, and the entity to which the redistribution judgment module belongs is gsmSCF; the IMS AS and the gsmSCF can be jointly or separately established, and there is a synchronization mechanism between the IMS AS and the gsmSCF. The corresponding relationship between different MSC/VLR numbers and UE access codes is preset in the AS, and the specific implementation of the eleventh embodiment includes the following steps:

Steps 1200 to 1202: The CS part of the UE sends a call establishment request to the VMSC through a Setup message, and the VMSC triggers an Initial DP message to the gsmSCF module with NeDS function according to the CAMEL subscription information, and sends a Call Proceeding message to the CS part of the UE.

The implementation of this step is completely consistent with that of steps 1100 to 1102, and will not be repeated here.

Step 1203: The gsmSCF uses a synchronization mechanism to send the VMSC number of the VMSC to which the UE currently belongs to the IMS AS.

The synchronization mechanism between the IMS AS and the gsmSCF belongs to the existing technology, which can be referred to related agreements, and will not be repeated here.

Step 1204: If the IMS AS determines that the VMSC number from the gsmSCF is inconsistent with the locally stored VMSC number of the VMSC to which the UE belongs before this call, then the IMS AS will use the received VMSC number and different MSCs/VLRs preset in the IMS AS The access code corresponding to the account number is reassigned to the UE access code.

In this step, it is assumed that the access code stored in the IMS AS is an E.164 number.

Step 1205-Step 1206: The IMS AS uses the synchronization mechanism to send the reallocated E.164 number to the gsmSCF, and the gsmSCF saves the received E.164 number locally and carries the E.A64 number in the CAMEL connect message. Send to MSC/VLR.

Step 1207: The IMS AS carries the reallocated E.164 number in the USSD and sends it to the UE, and the UE updates the local E.164 number.

Steps 1208 to 1209: VMSC routes the call to the MGCF in the IMS domain through the IAM message according to the received E.164 number, and the MGCF sends the call to the correct AS according to the E.164 number carried in the IAM message.

Such processing ensures that the call is switched by the correct AS.

Fig. 13 is a flow chart of Embodiment 13 of the present invention. The flow shown in Fig. 13 is proposed for solution 1 of implementing a call in the prior art. The main idea is to update the UE access code before the UE establishes a call connection, so that the UE uses The access code corresponding to the current location establishes a call connection, thereby ensuring the correctness of call routing. The UE includes an IMS part and a CS part. In this embodiment, the entity to which the redistribution logic module belongs is also the IMS AS, and the entity to which the redistribution judgment module belongs is gsmSCF; assuming that the IMSAS and the gsmSCF can be jointly established or separately established, and there is a synchronization mechanism between the IMS AS and the gsmSCF, as The corresponding relationship between different MSC/VLR numbers and UE access codes is preset in the IMS AS of the reallocation logic module, and the specific implementation of the eleventh embodiment includes the following steps:

Steps 1300 to 1302: The CS part of the UE sends a call establishment request to the VMSC through a Setup message, and the VMSC triggers an Initial DP message to the gsmSCF module with NeDS function according to the CAMEL subscription information, and sends a Call Proceeding message to the CS part of the UE.

The implementation of this step is completely consistent with that of steps 1100 to 1102, and will not be repeated here.

Step 1303: The gsmSCF uses a synchronization mechanism to send the VMSC number of the VMSC to which the UE currently belongs to the IMS AS.

The synchronization mechanism between the IMS AS and the gsmSCF belongs to the existing technology, which can be referred to related agreements, and will not be repeated here.

Step 1304: If the IMS AS determines that the VMSC number from the gsmSCF is inconsistent with the locally stored VMSC number of the VMSC to which the UE belongs before this call, the IMS AS will use the received VMSC number and different MSCs/VLRs preset in the IMS AS The access code corresponding to the account number is reassigned to the UE access code.

In this step, it is assumed that the access code stored in the IMS AS is an E.164 number.

Steps 1305 to 1306: The IMS AS uses a synchronization mechanism to send the reallocated E.164 number to the gsmSCF, and the gsmSCF saves the received E.164 number locally and carries the E.A64 number in the CAMEL connect message. Send to MSC/VLR.

Step 1307: The IMS AS carries the reallocated AS PSI in the PUBLISH message and sends it to the UE, and the UE updates the local E.164 number.

In this embodiment, the same as the tenth and eleventh embodiments, after step 1307, the VMSC routes the call to the MGCF in the IMS domain through the IAM message according to the received E.164 number, and the MGCF The E.164 number routes the call to the correct AS. Such processing ensures that the call is switched by the correct AS.

In addition, if the redistribution logic module updates the AS as required, before the redistribution logic module is the HSS and IMS AS flow process in the flow shown in Figures 2 to 13, the method of the present invention also includes:

The reallocation logic module executes the following different processes according to the user's registration status in IMS:

1) If the UE is not registered in the IMS, the HSS performs the AS reallocation operation, that is, the HSS only needs to update its own iFC data according to the updated AS. Wherein, different iFC data correspond to different ASs.

2) If the UE has registered in the IMS, and the VCC service of the UE is not occupied in the IMS, the IMS AS performs the AS reallocation operation.

The specific implementation is as follows: IMS AS carries the UE's user ID and iFC data in the Profile-Update-Request message, and sends the message to the HSS, and the HSS according to the UE's user ID and iFC data carried in the Profile-Update-Request message The data updates itself corresponding to the current user's iFC data; then the HSS carries the UE's user ID and iFC data in the Push-Profile-Request message and sends it to the S-CSCF, and the S-CSCF carries in the Profile-Update-Request message The UE's user ID and iFC data update itself corresponding to the current user's iFC data. In this way, after the user initiates the VCC service, the new iFC data can be used to carry out the service, and the reallocated AS can be used.

3) If the UE is registered in IMS, and the VCC service of the UE is occupied in IMS, in order to avoid error processing caused by changing the AS in the VCC service, the IMS AS sets the suspend flag to suspend the reallocation of the AS. Correspondingly, the IMS AS does not Synchronize the E.164 number to the UE. When the VCC service of the UE is not occupied by the IMS AS, cancel the suspend flag, and execute the AS reassignment process when the UE is already registered with the IMS.

In addition, it should be noted that since multiple MSC/VLR numbers correspond to the same UE access codes in practical applications, in the method for updating UE access codes in the present invention, the UE access codes are reassigned in the reallocation logic module. Afterwards, the method of the present invention further includes: the reallocation logic module judges whether the UE access code currently allocated is consistent with the UE access code stored locally, and if not, the reallocation logic module will redistribute the UE access code in the After self-storage, the method of the present invention is continued to send the reallocated UE access code to the UE; if they are consistent, the reallocation logic module ends the process of the present invention.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (32)

1. method of upgrading user terminal switch-in code, it is characterized in that, be provided for redistributing the heavy allocation logic module of user terminal UE access code, and the corresponding relation of default therein UE positional information and UE access code, be provided for judging whether heavily to distribute the heavily distribution judge module of new UE access code, this method may further comprise the steps:

A11. the position of described heavy distribution judge module from the UE position updating process upgraded in the response message and obtained described renewal indication information; Described UE position updating process comprises:

MSC/VLR is carried at the UE current location information in the location update request message under the a.UE, heavily distribute judge module to receive described location update request message, and after obtaining the described UE current location information that carries in this message, this location update request message is transmitted to attaching position register HLR;

B.HLR obtains described UE current location information from the described location update request message that receives, after judging that whether success is upgraded in the position, whether successful generate and preserve indicating positions upgrades renewal indication information and is carried in the position renewal response message, heavily distribute judge module to receive described position and upgrade response message, and after obtaining the described renewal indication information that carries in this message, response message is upgraded in this position be transmitted to the affiliated MSC/VLR of described UE;

A12. if described renewal indication information display update is successful, obtains described UE current location information and send to described heavy allocation logic module in the location update request message of described heavy distribution judge module from the UE position updating process;

B. described heavy allocation logic module is according to UE current location information and default corresponding relation, for described UE redistributes new UE access code;

C. described heavy allocation logic module is sent to the UE access code of redistributing to call out carries out point, calls out the execution point and upgrades self existing UE access code with the UE access code that receives.

2. method according to claim 1 is characterized in that: entity is all STP under described heavy distribution judge module and the heavy allocation logic module.

3. method according to claim 1 is characterized in that: heavily distribute judge module with the method that the UE current location information sends to heavy allocation logic module to be described in the steps A 12: the location update request message of heavily distributing judge module to duplicate to receive also sends to heavy allocation logic module;

Or the described UE current location information that obtains is carried at sends to heavy allocation logic module in the self-defined message.

4. method according to claim 3 is characterized in that: entity is STP under the described heavy distribution judge module; Entity is HSS or IMS AS under the described heavy allocation logic module.

5. method according to claim 1 is characterized in that, described steps A 11 and steps A 12 are:

In the UE position updating process, MSC/VLR receives from the position of HLR and upgrades response message, and judge this position upgrade the indicating positions that carries in response message whether upgrade successful renewal indication information be shown as upgrades successfully after, will carry the position renewal of the Temporary Mobile Subscriber Identity MSC/VLR TMSI of self MSC/VLR through SGSN and accept information and sending to UE;

UE receive the position upgrade accept message after, the change in location sign is set and sends to described heavy distribution judge module;

Described heavy distribution judge module receive expression UE current under after the change in location sign that changed of MSC/VLR, obtain the UE current location information and send to described heavy allocation logic module.

6. method according to claim 5, it is characterized in that described UE with the method that the change in location sign sends to described heavy distribution judge module is: UE is carried at the change in location sign that sets to send among the unstructured supplementary service data USSD and heavily distributes judge module.

7. method according to claim 5 is characterized in that, also comprise before this method: UE registers at IMS according to agreement, and has carried out two-way event subscription with IMS AS;

The method that described heavy distribution judge module receives described change in location sign is: in the UE position updating process, after UE receives that message is accepted in the position renewal, the change in location sign is set and sends to described heavy distribution judge module.

8. method according to claim 7, it is characterized in that, described UE with the method that the change in location sign sends to described heavy distribution judge module is: according to described two-way incident of having subscribed to, trigger UE the change in location sign that sets is carried at during SIP notification message or SIP give out information, send to and heavily distribute judge module.

9. method according to claim 5 is characterized in that, the method that described heavy distribution judge module obtains the UE current location information and sends to described heavy allocation logic module is:

I. heavily distribute the IMSI International Mobile Subscriber Identity IMSI of the described UE correspondence that judge module will preset to be carried in the ATI message and send to HLR;

The UE current location information that the II.HLR inquiry is corresponding with described IMSI, and this UE current location information is carried to send in the ATI_ack message heavily distributes judge module, if heavily distribute the UE positional information of judging the UE current location information that the mould inspection receives and being stored in this locality inconsistent, then heavily distribute judge module will send to heavy allocation logic module.

10. method according to claim 1, it is characterized in that, described steps A 11 and steps A 12 are: when heavily distributing judge module to know that UE successfully registers, heavily distribute the IMSI International Mobile Subscriber Identity IMSI of the described UE correspondence that judge module will preset to be carried in the ATI message and send to HLR;

The UE current location information that the HLR inquiry is corresponding with described IMSI, and this UE current location information is carried to send in the ATI_ack message heavily distributes judge module, if heavily distribute the UE positional information of judging the UE current location information that the mould inspection receives and being stored in this locality inconsistent, then heavily distribute judge module will send to heavy allocation logic module.

11., it is characterized in that entity is all STP under described heavy distribution judge module and the heavy allocation logic module, or HSS, or IMS AS according to claim 9 or 10 described methods.

12. according to claim 1,5 or 10 described methods, it is characterized in that, the method that heavy allocation logic module is redistributed new UE access code described in the step B is: heavy allocation logic module is according to the described UE current location information that receives, select self default UE positional information corresponding access code consistent, as the UE access code of redistributing with the UE current location information.

13. method according to claim 12, it is characterized in that, described in the step C UE access code being sent to the method for calling out the execution point is: heavy allocation logic module will be redistributed the UE access code that obtains and be carried among the USSD, be transmitted to described calling via MSC/VLR and carry out point;

Or heavy allocation logic module will be redistributed the UE access code that obtains and be carried at and send to described calling in the SIP notification message and carry out point;

Or heavy allocation logic module will be redistributed the UE access code that obtains and be carried at SIP and send to described calling in publishing the news and carry out point.

14., it is characterized in that the described UE access code that is carried among the USSD is number E.164 according to right method according to claim 13; UE access code during the described SIP of being carried at notification message or SIP publish the news is AS PSI.

15. method according to claim 13 is characterized in that, described calling is carried out point and is UE.

16. method according to claim 1 is characterized in that, described steps A 11 and steps A 12 are:

When UE need set up calling, the CS part of UE sends setup requests by setting up Setup message VMSC under self, this VMSC triggers the initial Initial DP message of carrying the UE current location information and sends to the heavily distribution judge module with NeDS function according to default CAMEL Subscription Information;

Described heavy distribution judge module receives the UE current location information, and after judging that the UE positional information of this UE current location information and self storage is inconsistent, the UE current location information is sent to described heavy allocation logic module.

17. method according to claim 16 is characterized in that: entity is all gsmSCF under described heavy distribution judge module and the heavy allocation logic module.

18. method according to claim 16 is characterized in that, described heavy distribution judge module sends to described heavy allocation logic module by existing synchronization mechanism with the UE current location information that carries in the described Initial DP message.

19. method according to claim 18 is characterized in that, entity is gsmSCF under the described heavy distribution judge module; Entity is IMS AS under the described heavy allocation logic module.

20. method according to claim 19 is characterized in that, described gsmSCF and IMS AS close if set up separately.

21., it is characterized in that described UE current location information is MSC/VLR number or VMSC number of the current affiliated VMSC of UE of the current affiliated MSC/VLR of UE according to claim 1,3,9,10,16 or 18 each described methods.

22. method according to claim 16, it is characterized in that, the method that heavy allocation logic module is redistributed new UE access code described in the step B is: heavy allocation logic module is according to the described UE current location information that receives, select self default UE positional information corresponding access code consistent, as the UE access code of redistributing with the UE current location information.

23. method according to claim 22, it is characterized in that, described in the step C UE access code being sent to the method for calling out the execution point is: heavy allocation logic module will be redistributed the UE access code that obtains and be carried among the USSD, be transmitted to first calling via described VMSC and carry out point; Or heavy allocation logic module will be redistributed the UE access code that obtains and be carried at SIP and send to first in publishing the news and call out and carry out point;

When heavy allocation logic module with heavily distribute judge module under entity not simultaneously, heavy allocation logic module also will be redistributed the UE access code that obtains by existing synchronization mechanism and send to second and call out and carry out point.

24. method according to claim 23 is characterized in that, described first calls out the execution point is UE; Described second calls out the execution point is gsmSCF.

25. method according to claim 23 is characterized in that, the described UE access code that is carried among the USSD is number E.164; UE access code during the described SIP of being carried at notification message or SIP publish the news is AS PSI.

26., it is characterized in that if heavy allocation logic module has been upgraded IMS AS as required, before described steps A 11, this method also comprises: described heavy allocation logic module is heavily distributed IMS AS according to claim 1,5,10 or 16 each described methods.

27. method according to claim 26 is characterized in that, described heavy allocation logic module heavily distributes the method for IMS AS to be: heavy allocation logic module is heavily distributed IMSAS according to the user at the login state of IMS,

If UE is unregistered at IMS, then HSS upgrades self initial filter standard or norm iFC data according to the AS that has upgraded;

If UE is registered at IMS, and the VCC business of this UE is unoccupied at IMS, then IMS AS with the user ID of UE and iFC data carry in Profile-Update-Request message, and this message sent to HSS, HSS is according to user ID and iFC Data Update self the iFC data of the UE that carries in the Profile-Update-Request message; Then HSS with the user ID of UE and iFC data carry in Push-Profile-Request message, and sending to S-CSCF, S-CSCF is according to the user ID of the UE that carries in this Profile-Update-Request message and the corresponding active user's of iFC Data Update self iFC data.

If UE is registered at IMS, and the VCC business of this UE is occupied at IMS, then IMS AS is provided for representing to postpone redistributing the postponement sign of IMS AS, simultaneously, described heavy allocation logic module forbids that the UE access code that described heavy distribution obtains is sent to calling carries out point, and sign is postponed in cancellation after the VCC service ending.

28., it is characterized in that among the step C, described heavy allocation logic module is sent to the UE access code of redistributing before the calling execution point according to claim 1,5,10 or 16 described methods, this method also comprises:

Heavy allocation logic module judges whether the described UE access code of redistributing is consistent with the UE access code of self storing, if inconsistent, then the UE access code of redistributing is continued execution in step C after self stores; If consistent, then finish flow process of the present invention.

29. a device that upgrades the UE access code is characterized in that, described device comprises: the positional information sending module that is used to obtain the UE current location information; Be used to redistribute the heavy allocation logic module of UE access code; Be used to judge whether heavily to distribute the heavily distribution judge module of new UE access code; And point is carried out in the calling of upgrading the UE access code;

The position of described heavy distribution judge module from the UE position updating process upgraded in the response message and obtained described renewal indication information; If described renewal indication information display update success is obtained described UE current location information and is sent to described heavy allocation logic module in the location update request message of described heavy distribution judge module from the UE position updating process; Described UE position updating process comprises: MSC/VLR is carried at the UE current location information in the location update request message under the UE, heavily distribute judge module to receive described location update request message, and after obtaining the described UE current location information that carries in this message, this location update request message is transmitted to described HLR; HLR obtains described UE current location information from the described location update request message that receives, after judging that whether success is upgraded in the position, whether successful generate and preserve indicating positions upgrades renewal indication information and is carried in the position renewal response message, heavily distribute judge module to receive described position and upgrade response message, and after obtaining the described renewal indication information that carries in this message, response message is upgraded in this position be transmitted to the affiliated MSC/VLR of described UE; Or,

In the UE position updating process, MSC/VLR receives from the position of HLR and upgrades response message, and judge this position upgrade the indicating positions that carries in response message whether upgrade successful renewal indication information be shown as upgrades successfully after, will carry the position renewal of the Temporary Mobile Subscriber Identity MSC/VLR TMSI of self MSC/VLR through SGSN and accept information and sending to UE; UE receive the position upgrade accept message after, the change in location sign is set and sends to described heavy distribution judge module; Described heavy distribution judge module receive expression UE current under after the change in location sign that changed of MSC/VLR, obtain the UE current location information and send to described heavy allocation logic module; Or,

When heavily distributing judge module to know that UE successfully registers, heavily distribute the IMSI International Mobile Subscriber Identity IMSI of the described UE correspondence that judge module will preset to be carried in the ATI message and send to HLR; The UE current location information that the HLR inquiry is corresponding with described IMSI, and this UE current location information is carried to send in the ATI_ack message heavily distributes judge module, if heavily distribute the UE positional information of judging the UE current location information that the mould inspection receives and being stored in this locality inconsistent, then heavily distribute judge module will send to heavy allocation logic module; Or,

When UE need set up calling, the CS part of UE sends setup requests by setting up Setup message VMSC under self, this VMSC triggers the initial Initial DP message of carrying the UE current location information and sends to the heavily distribution judge module with NeDS function according to default CAMEL Subscription Information; Described heavy distribution judge module receives the UE current location information, and after judging that the UE positional information of this UE current location information and self storage is inconsistent, the UE current location information is sent to described heavy allocation logic module;

Described heavy allocation logic module receives the UE current location information from the positional information sending module, UE current location information according to default corresponding relation and acquisition is that described UE distributes new UE access code, and new UE access code is sent to described calling carry out point, described calling is carried out point and is upgraded self existing UE access code with the UE access code that receives.

30. device according to claim 29, it is characterized in that, further be provided with comparison module in the described heavy allocation logic module, be used for determining whether described new UE access code is consistent with the UE access code of self storing, and when inconsistent new UE access code sent to described calling and carries out point.

31. device according to claim 29 is characterized in that, described calling is carried out point and is UE, perhaps UE and gsmSCF.

32. device according to claim 29 is characterized in that: entity is HSS under the described heavy allocation logic module, and entity is HLR under the described heavy distribution judge module;

Entity is HSS or IMS AS under the perhaps described heavy allocation logic module, and entity is STP under the described heavy distribution judge module;

Entity is IMS AS under the perhaps described heavy allocation logic module, and entity is gsmSCF under the described heavy distribution judge module;

Entity is all gsmSCF under perhaps described heavy distribution judge module and the heavy allocation logic module;

Perhaps described heavy allocation logic module and distribute heavily that entity is all STP under the judge module, or HSS, or IMS AS.

Images