WO2012103732A1

WO2012103732A1 - Controlling method, system and device

Info

Publication number: WO2012103732A1
Application number: PCT/CN2011/076699
Authority: WO
Inventors: 帅扬来
Original assignee: 华为技术有限公司
Priority date: 2011-06-30
Filing date: 2011-06-30
Publication date: 2012-08-09
Also published as: CN102301759A

Abstract

A controlling method, system and device are provided in the present invention. The method includes that: a first device receives an attach request or an update request which carries a terminal identifier from a terminal, and generates Radio Access Technologies/Frequency Selection Priority (RFSP) in using corresponding to the terminal identifier; the terminal identifier and the RFSP in using are provided to a Mobile Switching Center (MSC); wherein the first device is a Mobility Management Entity (MME) or a Serving GPRS Support Node (SGSN). The controlling method, system and device in the present invention solve the problem in the prior art that a terminal may perform ping-pong network reselection between two networks due to inconsistency of RFSP determined by the MSC and RFSP determined by the first device, thereby saving huge resources.

Description

Control method and system and device

Technical field

Embodiments of the present invention relate to communication technologies, and in particular, to a control method, system, and device. Background technique

The second generation/third generation (2rd/3rd Generation; 2G/3G) mobile communication technology network has been deployed for many years and can be regarded as a comprehensive coverage to some extent, but with the evolution of the system architecture (System Architecture Evolution; abbreviated as: SAE)/Long Term Evolution (LTE), High Speed Uplink Packet Access (HSPA), HSPA+, and Worldwide Interoperability for Microwave Access ( Worldwide Interoperability for Microwave Access; Abbreviation: WiMAX) The development of network technologies that have covered some urban and traffic hotspots, resulting in the coexistence of these networks and 2G/3G networks in current communication networks.

For different network bearer mechanisms, the voice calls of the mobile communication can be classified into two types: The first type is the circuit service carried by the Circuit Service (CS) domain network, for example: voice service telephone; The class is a session-based service carried by a packet switching (PS) domain network. It can also be called Voice over Internet Protocol (VoIP)-based services. IP Multimedia System (IP Multimedia) Subsystem; Abbreviation: IMS) Provides Quality of Service (QoS) guarantees, for example: voice calls carried by IP networks. Among them, SAE/LTE, HSPA, HSPA+, WiMAX and other networks that only provide PS domain networks can be collectively referred to as pure PS domain networks.

Currently, when the terminal accesses the 2G/3G CS domain, the Mobile Switching Center (MSC) refers to the radio access technology or frequency selection priority (Radio Access Technologies/Frequency Selection Priority; RFSP). And the operator policy, generating the used RFSP, that is, RFSP in using; when the terminal accesses the PS domain, the terminal can support the terminal The voice capability and configuration are sent to the Mobility Management Mobility (MME)/GPRS Service Node (SGSN), and the MME/SGSN can sign the RFSP according to the reference, the operator policy, and the terminal. Supported voice capabilities and configuration, generating RFSP in using.

Because the RFSP in using generated by the MSC and the MME/SGSN is inconsistent, the terminal has a problem of network reselection of ping-pong between the two networks. Summary of the invention

The embodiment of the present invention provides a control method, system, and device, which are used to solve the problem that the terminal re-selects ping-pong between two networks due to the inconsistency of the RFSP determined by the MSC and the MME/SGSN in the prior art, thereby saving A lot of resources.

The embodiment of the invention provides a control method, including:

The first device receives an attach request or an update request that is sent by the terminal and carries the terminal identifier, and generates a used radio access technology or frequency selection priority RFSP in using corresponding to the terminal identifier; The terminal identifier and the RFSP in using are provided to the mobile switching center; wherein the first device is a mobility management entity or a serving general packet radio service supporting node. The embodiment of the invention further provides a control method, including:

The home subscriber server HSS receives a notification request message that is sent by the first device and carries the radio access technology or frequency selection priority RFSP in using corresponding to the terminal identifier and the terminal identifier, where the first device is a mobility management entity or General packet radio service support node;

The HSS stores the terminal identifier in the notification request message and the RFSP in using corresponding to the terminal identifier;

When receiving the subscription data request that is sent by the mobile switching center and carrying the terminal identifier, the HSS sends the RFSP in using corresponding to the terminal identifier to the mobile switching center.

The embodiment of the invention further provides a control method, including:

The mobile switching center receives a location update request message sent by the first device, where the first device is a mobile device Dynamic management entity/service general packet radio service support node;

The mobile switching center acquires the terminal identifier and the RFSP in using corresponding to the terminal identifier according to the location update request message.

The embodiment of the invention further provides a control method, including:

The mobile switching center sends a subscription data request carrying the terminal identifier to the home subscriber server.

HSS;

Receiving, by the mobile switching center, the terminal identifier returned by the HSS and a used radio access technology or frequency selection priority corresponding to the terminal identifier, RFSP in using ₀

An embodiment of the present invention provides an apparatus, including:

a receiving unit, configured to receive an attach request or an update request that is sent by the terminal, and a generating unit, configured to generate a radio access technology or a frequency selection priority RFSP in using corresponding to the terminal identifier;

And a sending unit, configured to provide the terminal identifier and the RFSP in using to the mobile switching center. An embodiment of the present invention provides an HSS, including:

a receiving unit, configured to receive, by the first device, a notification request message that carries a radio access technology or a frequency selection priority RFSP in using corresponding to the terminal identifier and the terminal identifier, where the first device is a mobility management entity Or a general packet radio service support node;

a storage unit, configured to store a terminal identifier in the notification request message and an RFSP in using corresponding to the terminal identifier;

The receiving unit is further configured to receive a subscription data request that is sent by the mobile switching center and that carries the terminal identifier;

And a sending unit, configured to send the RFSP in using corresponding to the terminal identifier to the mobile switching center.

An embodiment of the present invention provides an MSC, including:

a receiving unit, configured to receive a location update request message sent by the first device, where the first device is a mobility management entity/service general packet radio service support node; An obtaining unit, configured to acquire, according to the location update request message, a terminal identifier and an RFSP in using the terminal identifier

The embodiment of the invention further provides an MSC, including:

a sending unit, configured to send a subscription data request carrying the terminal identifier to the home subscriber server, and a receiving unit, configured to receive the terminal identifier returned by the home subscriber server and the used radio access technology or frequency selection corresponding to the terminal identifier Priority RFSP in using.

An embodiment of the present invention provides a control system, including: the foregoing device, the foregoing HSS, and the mobile switching center described above.

The control method and system and device of the embodiment of the present invention receive, by the first device, an attach request or an update request that is sent by the terminal and carries the terminal identifier, and generates an RFSP in using corresponding to the terminal identifier, where the first device identifies the terminal and The RFSP in using is provided to the MSC, thereby solving the problem in the prior art that the terminal re-selects the ping-pong between the two networks due to the inconsistency of the RFSP in using determined by the MSC and the first device, and saves a lot of resources. DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description of the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

1 is a flow chart of an embodiment of a control method of the present invention;

2 is a flow chart of another embodiment of a control method of the present invention;

3 is a flow chart of still another embodiment of a control method of the present invention;

4 is a flow chart of still another embodiment of a control method of the present invention;

Figure 5 is a flow chart of another embodiment of the control method of the present invention;

6 is a flow chart of still another embodiment of a control method of the present invention;

Figure 7 is a schematic structural view of an embodiment of the device of the present invention; Figure 8 is a schematic structural view of another embodiment of the apparatus of the present invention;

9 is a schematic structural view of an embodiment of an HSS of the present invention;

10 is a schematic structural diagram of an embodiment of an MSC according to the present invention;

11 is a schematic structural view of another embodiment of an MSC according to the present invention;

12 is a schematic structural diagram of still another embodiment of an MSC according to the present invention;

Figure 13 is a block diagram showing the structure of an embodiment of the control system of the present invention. detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

FIG. 1 is a flowchart of an embodiment of a control method according to the present invention. As shown in FIG. 1, the method in this embodiment includes:

Step 101: The first device receives an attach request or an update request that is sent by the terminal and carries the terminal identifier, and generates an RFSP in using corresponding to the terminal identifier.

Step 102: The first device provides the terminal identifier and the RFSP in using to the MSC.

The first device is a Mobility Management Entity (MME) or a General Packet Radio Service (GPRS) support node (Serving GPRS Support Node; SGSN).

In this embodiment, the terminal initiates an attach procedure to the first device in the PS domain, or the terminal initiates a location area update (Track Area Update; referred to as TAU), or a Routing Area Update (RAA) process. In the process, the first device may generate the used RFSP for the terminal corresponding to the terminal identifier, that is, the used RFSP may also be referred to as the used RFSP corresponding to the terminal identifier. Specifically, the used RFSP may be referred to as RFSP in using; terminal identification can be specific For International Mobile Subscriber i, only the International Mobile Subscriber Identification Number (IMSI).

In addition, the first device may send the generated RFSP in using corresponding to the identifier of the terminal and the terminal identifier in a notification request (Notification Request) message to the home subscriber server (Home Subscriber Server; HSS for short), and then by the HSS Sending an RFSP in using corresponding to the terminal identifier to the MSC according to the received subscription data request that carries the terminal identifier sent by the MSC; or the first device may generate the generated RFSP in using corresponding to the terminal identifier and the terminal The identifier is carried in the location update request message and sent to the MSC, so that the MSC obtains the RFSP in using corresponding to the terminal identifier and the terminal identifier, so that the RFSP in using corresponding to the terminal identifier in the MSC and the terminal identifier in the first device The corresponding RFSP in using is consistent.

In this embodiment, the first device receives an attach request or an update request that is sent by the terminal and carries the terminal identifier, and generates an RFSP in using corresponding to the terminal identifier, where the first device provides the terminal identifier and the RFSP in using to the MSC. Therefore, the problem that the terminal re-selects the ping-pong between the two networks due to the inconsistency of the RFSP in using determined by the MSC and the first device is solved in the prior art, and a large amount of resources are saved.

2 is a flowchart of another embodiment of the control method of the present invention. In this embodiment, the technical solution of the embodiment is introduced in detail by using the HSS mode to implement the RFSP in using in the first device. As shown in FIG. 2, the method in this embodiment includes:

Step 201: The first device receives an attach request or an update request that is sent by the terminal and carries the terminal identifier, sends a subscription data request carrying the terminal identifier to the HSS, and receives a subscribed (subscribed) RSFP corresponding to the terminal identifier sent by the HSS. .

The first device is an MME or an SGSN.

Step 202: The first device generates an RFSP in using corresponding to the terminal identifier according to the obtained voice capability and configuration corresponding to the terminal identifier, the Subscribed RFSP, and the pre-configured carrier policy.

In this embodiment, when the user of the terminal signs the contract, the terminal identifier is correspondingly

The Subscribed RFSP is stored in the HSS, when the terminal initiates the attached flow to the first device in the PS domain network. During the process, the first device sends a subscription data request carrying the terminal identifier to the HSS, and obtains the subscribed RSFP corresponding to the terminal identifier returned by the HSS, and according to the voice capability and configuration corresponding to the terminal identifier, the Subscribed RSFP and the pre-configured operation. The quotient policy generates an RFSP in using corresponding to the terminal identifier.

Step 203: The first device sends a Notification Request message to the HSS, where the notification is

The request message includes the terminal identifier and the RFSP in using corresponding to the terminal identifier, so that the HSS sends the RFSP in using corresponding to the terminal identifier to the MSC when receiving the subscription data request that carries the terminal identifier sent by the MSC.

In this embodiment, the HSS may store two types of RFSPs corresponding to the first terminal identifier: one is RFSP in using; the other is subscribed RFSP, and when the MSC sends a subscription data request to the HSS, the HSS may return to the MSC. The RFSP in using corresponding to the terminal identifier in the subscription data request; in addition, when the first device sends the subscription data request to the HSS, the HSS returns the Subscribed RFSP corresponding to the terminal identifier in the subscription data request to the first device.

Step 204: When one or more of the voice capability and configuration corresponding to the terminal identifier, the Subscribed RFSP, and the operator policy change, the first device updates the RFSP in using corresponding to the terminal identifier.

Step 205: The first device sends the updated RFSP in using and the terminal identifier to the HSS in the Notification Request message, where the HSS uses the updated RFSP in using corresponding to the terminal identifier to replace the stored corresponding terminal identifier. The RFSP in using; and the updated RFSP in using corresponding to the terminal identifier and the terminal identifier are carried in the Insert Subscriber Data message and sent to the MSC.

In this embodiment, the first device generates a new RFSP in using corresponding to the terminal identifier according to the voice capability and configuration corresponding to the changed terminal identifier, the Subscribed RFSP, and the operator policy, and identifies the terminal and the terminal. The updated RFSP in using corresponding to the identifier is sent to the HSS in the Notification Request message. After receiving the Notification Request message, the HSS updates the RFSP in using corresponding to the terminal identifier, and receives the updated RFSP in using instead of the stored one. The RFSP in using the terminal identifier and the updated RFSP in using corresponding to the terminal identifier are sent to the MSC in the Insert Subscriber Data, so that the MSC updates the RFSP in using corresponding to the terminal identifier, thereby The RFSP in using corresponding to the terminal identifier in the MSC is consistent with the RFSP in using corresponding to the terminal identifier in the first device, thereby more effectively solving the RFSP inconsistency determined by the MSC and the first device in the prior art. The terminal has a problem of network reselection of ping-pong between the two networks and saves a lot of resources.

Further, in still another embodiment of the present invention, the method may further include:

When the terminal initiates the network revocation process, the first device sends the terminal identifier to the HSS in the Notification Request message, so that the HSS deletes the RFSP in using corresponding to the terminal identifier.

For example, in this embodiment, when the implicit or displayed network exit process is initiated, for example, the terminal, the first device, or the HSS initiated network exit process, the SGs interface between the first device and the MSC is deleted. In addition, if the reconnection is not performed between the terminal and the first device, the signaling connection between the terminal and the first device is released, and the first device notifies the HSS to delete the RFSP in using corresponding to the terminal identifier, for example, The first device sends a Notification Request message carrying the identifier of the terminal, and the Notification Request message does not carry the RFSP in using field, and after receiving the Notification Request message, the HSS deletes the RFSP in using corresponding to the terminal identifier, and Return a notification response message to the first device.

FIG. 3 is a flowchart of still another embodiment of the control method of the present invention. In this embodiment, the SGs interface is used to implement the RFSP in using in the first device as an example, and the technical solution in this embodiment is introduced in detail. As shown in FIG. 3, the method in this embodiment includes:

Step 301: The first device receives the attach request or the update request that is sent by the terminal and carries the terminal identifier, sends a subscription data request carrying the terminal identifier to the HSS, and receives the Subscribed RSFP corresponding to the terminal identifier sent by the HSS.

The first device is an MME or an SGSN.

Step 302: The first device performs, according to the obtained voice capability and configuration corresponding to the terminal identifier,

Subscribed RFSP and pre-configured carrier policy to generate RFSP in corresponding to the terminal identifier Usmg.

For example, in this embodiment, when the user of the terminal signs the contract, the Subscribed RFSP corresponding to the terminal identifier is stored in the HSS in advance, and when the terminal initiates the attach procedure to the MME/SGSN or the TAU/RAU process, the MME The /SGSN sends a subscription data request carrying the terminal identifier to the HSS, and obtains the subscribed RSFP corresponding to the terminal identifier returned by the HSS, and generates according to the voice capability and configuration corresponding to the terminal identifier, the Subscribed RFSP, and the pre-configured operator policy. RFSP in using corresponding to the terminal identifier.

Step 303: The first device sends a location update request (Location Update Request) message to the MSC, where the location update request message includes the terminal identifier and the RFSP in using corresponding to the terminal identifier.

In this embodiment, the MME/SGSN carries the RFSP in using corresponding to the terminal identifier and the terminal identifier in the Location Update Request message, and sends the RFSP in using corresponding to the terminal identifier in the MSC. The RFSP in using is consistent with the terminal identifier, thereby solving the problem that the network reselects the ping-pong between the two networks due to the inconsistency of the RFSP determined by the MSC and the first device in the prior art, and saves a large amount of resources. .

In addition, when the location of the MSC changes or its security configuration expires, the MSC may initiate a location update in the CS domain according to the Location Update Request message, and return a Location Update Response message to the MME/SGSN.

Further, in a further embodiment of the present invention, based on the foregoing method embodiment shown in FIG. 3, step 303 may also be:

The first device sends the terminal identifier and the voice capability and the configuration corresponding to the terminal identifier to the MSC in the Location Update Request message, and the MSC can obtain the terminal identifier from the HSS according to the voice capability and configuration corresponding to the terminal identifier. Corresponding Subscribed RFSP and pre-configured operator policy, generating RFSP in using corresponding to the terminal identifier, where the RFSP in using is synchronized with the RFSP in using generated in the first device, thereby ensuring the MSC and the first device The RFSP in using is consistent with the terminal identifier; or Step 303 can also be:

The first device sends the terminal identifier and the voice capability corresponding to the terminal identifier and the RFSP in using corresponding to the terminal identifier to the MSC in the Location Update Request message, and the MSC can obtain the voice capability and configuration corresponding to the terminal identifier. The subscribed RFSP corresponding to the terminal identifier obtained by the HSS and the pre-configured operator policy generate the RFSP in using corresponding to the terminal identifier, and compare with the RFSP in using corresponding to the terminal identifier obtained from the first device, if the same And storing the RFSP in using corresponding to the terminal identifier; if not, indicating that the RFSP in using corresponding to the terminal identifier in the MSC is inconsistent with the RFSP in using corresponding to the terminal identifier in the first device, deleting the generated The RFSP in using stores the RFSP in using obtained from the first device, thereby more effectively ensuring the RFSP in using in the first device and the MSC.

Further, in another embodiment of the present invention, based on the foregoing method embodiment shown in FIG. 3, the method may further include:

When one or more of the voice capability and configuration corresponding to the terminal identifier, the Subscribed RFSP, and the operator policy change, the first device updates the RFSP in using corresponding to the terminal identifier.

The first device carries the terminal identifier and the updated RFSP in using corresponding to the terminal identifier in

The Location Update Request message is sent to the MSC.

In this embodiment, the first device generates a new RFSP in using corresponding to the terminal identifier according to the voice capability and configuration corresponding to the changed terminal identifier, the Subscribed RFSP, and the operator policy, and identifies the terminal and the terminal. The updated RFSP in using corresponding to the identifier is sent to the MSC in the Location Update Request message. After receiving the Location Update Request message, the MSC replaces the stored RFSP in using corresponding to the terminal identifier by using the updated RFSP in using corresponding to the terminal identifier, so that the identifier of the terminal in the MSC corresponds to the RFSP in using and The RFSP in using corresponding to the identifier of the terminal in the first device is consistent in real time, thereby more effectively solving the problem that the terminal has a network between the two networks due to the inconsistency of the RFSP determined by the MSC and the first device in the prior art. Choosing ping pong problems and saving a lot of resources

4 is a flowchart of still another embodiment of a control method of the present invention. As shown in FIG. 4, this embodiment The methods include:

Step 401: The HSS receives a Notification Request message that is sent by the first device and carries an RFSP in using corresponding to the terminal identifier and the terminal identifier, where the first device is an MME or an SGSN.

Step 402: The HSS stores the terminal identifier in the Notification Request message and the RFSP in using corresponding to the terminal identifier.

Step 403: The HSS receives the subscription data request that is sent by the MSC and carries the terminal identifier, and sends the RFSP in using corresponding to the terminal identifier to the MSC.

In this embodiment, the first device may perform the embodiment of the method shown in FIG. 2, and the principle is similar, and details are not described herein again.

In this embodiment, after receiving the Notification Request message sent by the first device and carrying the RFSP in using corresponding to the terminal identifier, the HSS stores the terminal identifier in the Notification Request message and the RFSP in corresponding to the terminal identifier. Using, in other words, the HSS includes multiple terminal identifiers and RFSP in using corresponding to each terminal identifier. When the MSC sends the subscription data request carrying the terminal identifier, the RFSP in using corresponding to the terminal identifier is sent to the MSC, so that the RFSP in using corresponding to the identifier of the terminal stored in the MSC is stored in the first device. The RFSP in using is consistent with the terminal identifier, which solves the problem that the terminal re-selects the ping-pong between the two networks due to the inconsistency of the RFSP in using by the MSC and the first device in the prior art, and saves a large number of Resources.

Further, in still another embodiment of the present invention, based on the foregoing embodiment of the method shown in FIG. 4, the method may further include:

The HSS receives a notification request message carrying the updated RFSP in using corresponding to the terminal identifier and the terminal identifier;

The HSS replaces the stored RFSP in using corresponding to the terminal identifier by using the updated RFSP in using corresponding to the terminal identifier;

The HSS carries the terminal identifier and the updated RFSP in using corresponding to the terminal identifier in the Insert

The Subscriber Data message is sent to the MSC. In this embodiment, when one or more of the voice capability and the configuration, the Subscribed RFSP, and the operator policy of the terminal identifier change, the MME/SGSN may perform the voice capability corresponding to the changed identifier of the terminal. The configuration, the Subscribed RFSP, and the carrier policy are generated, and the updated RFSP in using is generated, and the updated RFSP in using corresponding to the terminal identifier and the terminal identifier is sent to the HSS in the Notification Request message, so that the HSS uses the The updated RFSP in using corresponding to the terminal identifier replaces the stored RFSP in using corresponding to the terminal identifier, and then the updated RFSP in using corresponding to the terminal identifier and the terminal identifier is sent in the Insert Subscriber Data message. The MSC ensures that the RFSP in using corresponding to the terminal identifier in the MSC is consistent with the RF SP in using corresponding to the terminal identifier in the first device, thereby more effectively solving the prior art determination by the MSC and the first device. The RFSP is inconsistent and causes the terminal to have a problem of network reselection of ping-pong between the two networks.

The HSS receives the Notification Request message of the terminal identifier sent by the MME/SGSN, and deletes the RFSP in using corresponding to the terminal identifier according to the Notification Request message.

FIG. 5 is a flowchart of another embodiment of a control method according to the present invention. As shown in FIG. 5, the method in this embodiment includes:

Step 501: The MSC receives a Location Update Request message sent by the first device, where the first device is an MME or an SGSN.

Step 502: The MSC obtains the terminal identifier and the RFSP in using corresponding to the terminal identifier according to the Location Update Request message.

In this embodiment, the first device may perform the technical solution of the embodiment of the method shown in FIG. 3, and the implementation principles thereof are similar, and details are not described herein again.

In this embodiment, the MSC obtains the RFSP in using corresponding to the terminal identifier and the terminal identifier according to the Location Update Request message, so that the RFSP in using corresponding to the terminal identifier in the MSC and the RFSP corresponding to the terminal identifier in the first device are obtained. In using consistent, which effectively solves In the prior art, due to the inconsistency of the RFSP determined by the MSC and the first device, the terminal has a problem of network reselection of ping-pong between the two networks.

Specifically, the MSC obtains the RFSP in using mode in the following manner: The first mode: The MSC receives the location update request message sent by the first device, including the voice capability and configuration corresponding to the terminal identifier, and the MSC is in the CS domain. The location update, the subscribed RFSP corresponding to the terminal identifier is obtained from the HSS, and the RFSP in using, the RFSP in using and the first device are generated according to the voice capability and configuration corresponding to the terminal identifier, the Subscribed RFSP and the preset operator policy. The generated RFSP in using is consistent.

The second type: the MSC receives the location update request message sent by the first device, including the terminal identifier and the RFSP in using corresponding to the terminal identifier, so that the MSC can directly obtain the RFSP in using corresponding to the terminal identifier in the MME/SGSN.

The third type: the MSC receives the location update request message sent by the first device, including the terminal identifier, the RFSP in using corresponding to the terminal identifier, and the voice capability and configuration corresponding to the terminal identifier, where the MSC updates the location in the CS domain and obtains the information from the HSS. a subscribed RFSP corresponding to the terminal identifier, and based on the voice capability and configuration corresponding to the terminal identifier, the Subscribed RFSP and the preset operator policy, generating the RFSP in using corresponding to the terminal identifier, and acquiring the obtained from the MME/SGSN The RFSP in using corresponding to the terminal identifier is stored, if the same, the RFSP in using corresponding to the generated terminal identifier is stored; if not, the generated RFSP in using corresponding to the generated terminal identifier is deleted, and the storage is from the first device. Obtain the RFSP in using corresponding to the terminal identifier.

Further, based on the foregoing method embodiment shown in FIG. 5, the method may further include:

The MSC receives an Indication Request message that is sent by another MSC and carries a terminal identifier.

The MSC sends an Indication Response message to the other MSC according to the Indication Request message, where the Indication Response message includes the RFSP in using corresponding to the terminal identifier and/or the voice capability and configuration corresponding to the terminal identifier.

In this embodiment, when the terminal initiates an access procedure to a new MSC, for example: the access process It may be the initial access of the terminal, or may be the cell Assisted Cell Chang (NACC)/Cell Change Order (CCO) from other access technologies. In the access process to the 2G/3G network, the new MSC (another MSC) sends an Indication Request message carrying the terminal identifier to the MSC, and the MSC can correspond to the RFSP in using and/or the terminal identifier corresponding to the terminal identifier. The voice capability and configuration are carried in the Indication Response message and sent to the new MSC. The new MSC may directly obtain the RFSP in using corresponding to the terminal identifier; or may generate the RFSP in using corresponding to the terminal identifier according to the voice capability and configuration, the Subscribed RFSP, and the preset operator policy; or The voice capability and configuration corresponding to the terminal identifier, the Subscribed RFSP, and the preset operator policy, generate the RFSP in using corresponding to the terminal identifier, and compare with the RFSP in using corresponding to the terminal identifier obtained from the MSC, if they are the same, The RFSP in using corresponding to the generated terminal identifier is stored; if not, the generated RFSP in using is deleted, and the RFSP in using corresponding to the terminal identifier obtained from the MSC is stored.

FIG. 6 is a flowchart of still another embodiment of the control method of the present invention. As shown in FIG. 6, the method in this embodiment includes:

Step 601: The MSC sends a subscription data request carrying the terminal identifier to the HSS.

Step 602: The MSC receives the terminal identifier returned by the HSS and the RFSP in using corresponding to the terminal identifier.

In this embodiment, the HSS may perform the technical solution of the method embodiment shown in FIG. 4, and the implementation principle is similar, and details are not described herein again.

FIG. 7 is a schematic structural diagram of an apparatus according to an embodiment of the present invention. As shown in FIG. 7, the device in this embodiment may be specifically an MME or an SGSN, and the device specifically includes: a receiving unit 11, a generating unit 12, and a sending unit 13, The receiving unit 11 is configured to receive an attach request or an update request that is sent by the terminal and carry the terminal identifier. The generating unit 12 is configured to generate an RFSP in using corresponding to the terminal identifier. The sending unit 13 provides the terminal identifier and the RFSP in using to the MSC. .

The device in this embodiment can perform the technical solution of the method embodiment shown in FIG. Similar, it will not be described here. In this embodiment, the device receives the attach request or the update request that is sent by the terminal and carries the terminal identifier, and generates an RFSP in using corresponding to the terminal identifier, and the device provides the terminal identifier and the RFSP in using to the MSC, thereby solving the problem. In the prior art, due to the inconsistent RFSP in using determined by the MSC and the device, the terminal has a problem of network reselection of ping-pong between the two networks, and saves a lot of resources.

FIG. 8 is a schematic structural diagram of another embodiment of the device according to the present invention. As shown in FIG. 8, on the basis of the foregoing embodiment shown in FIG. 7, the sending unit 13 is further configured to send a subscription carrying the terminal identifier to the HSS of the terminal. The data request is received by the receiving unit 11 to receive the subscribed RFSP corresponding to the terminal identifier sent by the HSS. The generating unit 12 is further configured to: according to the obtained voice capability and configuration corresponding to the terminal identifier, the Subscribed RFSP, and the pre-configured operator policy. Generate RFSP in using corresponding to the terminal identifier.

Further, when the message is a notification request message, the sending unit 13 is specifically configured to send a notification request message to the HSS, where the notification request message includes the terminal identifier and the RFSP in using corresponding to the terminal identifier; the HSS carries the carried by the MSC. When the subscription data of the terminal identifier is requested, the sending terminal identifier and the RFSP in using corresponding to the terminal identifier are sent to the MSC; or

The sending unit 13 is specifically configured to send a Location Update Request message to the MSC, where the location update request message includes the terminal identifier and the RFSP in using corresponding to the terminal identifier. The MSC, the location update request message includes a terminal identifier and a voice capability and a configuration corresponding to the terminal identifier, so that the MSC can obtain the subscribed RFSP and the preset corresponding to the terminal identifier obtained from the HSS according to the voice capability and configuration corresponding to the terminal identifier. The configured carrier policy is generated according to the voice capability and configuration corresponding to the terminal identifier, the Subscribed RFSP, and the pre-configured carrier policy, and the RFSP in using corresponding to the terminal identifier is generated; or

The sending unit 13 is specifically configured to send a Location Update Request message to the MSC, where the Location Update Request message includes a terminal identifier, a voice capability and a configuration corresponding to the terminal identifier, and an RFSP in using corresponding to the terminal identifier, for the MSC to use the terminal identifier. Corresponding voice capabilities and configuration, The subscribed RFSP corresponding to the terminal identifier obtained from the HSS and the pre-configured operator policy are used to generate the RFSP in using corresponding to the terminal identifier, and are compared with the RFSP in using corresponding to the terminal identifier obtained by the slave device. And storing the RFSP in using corresponding to the terminal identifier; if not, indicating that the RFSP in using corresponding to the terminal identifier in the MSC is inconsistent with the RFSP in using corresponding to the identifier of the terminal in the device, deleting the generated RFSP in Using, storing RFSP in using„ from the device

Further, the sending unit 12 is further configured to: when the terminal initiates the network retreating process, the terminal identifier is carried in the notification request message and sent to the HSS, so that the HSS deletes the RFSP in corresponding to the terminal identifier according to the notification request message. Using„

Further, the device further includes an updating unit 14 configured to update the RFSP in using corresponding to the terminal identifier when one or more of the voice capability and configuration corresponding to the terminal identifier, the Subscribed RFSP, and the operator policy are changed. ;

The sending unit 13 is further configured to: send the updated RFSP in using and the terminal identifier to the HSS in the notification request message; or

The sending unit 13 is further configured to carry the updated RFSP in using and terminal identifier in the Location

The Update Request message is sent to the MSC.

The device in this embodiment may perform the technical solution of the method embodiment shown in FIG. 2 or FIG. 3, and the implementation principles are similar, and details are not described herein again.

In this embodiment, the device receives the attach request or the update request that is sent by the terminal and carries the terminal identifier, and generates an RFSP in using corresponding to the terminal identifier, and the device provides the terminal identifier and the RFSP in using to the MSC, thereby solving the problem. In the prior art, due to the inconsistent RFSP in using determined by the MSC and the device, the terminal has a problem of network reselection of ping-pong between the two networks, and saves a lot of resources.

FIG. 9 is a schematic structural diagram of an embodiment of an HSS according to the present invention. As shown in FIG. 9, the HSS of this embodiment includes: a receiving unit 21, a storage unit 22, and a sending unit 23, wherein the receiving unit 21 is configured to receive the first device. A notification request sent by the RFSP in using carrying the terminal identifier and the terminal identifier The first device is the MME or the SGSN, and the storage unit 22 is configured to store the terminal identifier in the notification request message and the RFSP in using corresponding to the terminal identifier. The receiving unit 21 is further configured to receive the subscription data that is sent by the MSC and carries the terminal identifier. The sending unit 23 is configured to send the RFSP in using corresponding to the terminal identifier and the terminal identifier to the MSC.

The HSS of this embodiment may perform the technical solution of the method embodiment shown in FIG. 4, and the implementation principles thereof are similar, and details are not described herein again.

Further, in another embodiment of the present invention, on the basis of the foregoing embodiment shown in FIG. 9, the receiving unit 21 is further configured to receive the updated RFSP in using notification request that carries the terminal identifier and the terminal identifier. The message to the HSS also includes:

And an updating unit, configured to replace, by using the updated RFSP in using corresponding to the terminal identifier, the stored RF SP in using corresponding to the terminal identifier;

The sending unit 23 is further configured to carry the updated RFSP in using corresponding to the terminal identifier and the terminal identifier to the MSC in the inserted user data message.

In addition, the receiving unit 21 is further configured to receive a notification request message that is sent by the MME/SGSN and that carries the identifier of the deleted terminal. The second update unit is further configured to delete the RFSP in corresponding to the identifier of the deleted terminal according to the notification request message. Using.

Further, the receiving unit 21 is further configured to receive, by the first device, the identifier that carries the terminal identifier And the notification request message, the HSS further includes: a deleting unit, configured to delete the RFSP in using the terminal identifier according to the notification message

FIG. 10 is a schematic structural diagram of an embodiment of an MSC according to the present invention. As shown in FIG. 10, the MSC in this embodiment includes: a receiving unit 31 and an obtaining unit 32, where the receiving unit 31 is configured to receive a location update sent by the MME/SGSN. The requesting unit 32 is configured to obtain the RFSP in using corresponding to the terminal identifier and the terminal identifier according to the location update request message.

The MSC of this embodiment can implement the technical solution of the method embodiment shown in FIG. 5, and the implementation principle is similar, and details are not described herein again.

In this embodiment, the MSC obtains the RFSP in using corresponding to the terminal identifier and the terminal identifier according to the Location Update Request message, so that the RFSP in using corresponding to the terminal identifier in the MSC and the RFSP corresponding to the terminal identifier in the first device are obtained. The in using is consistent, thereby effectively solving the problem in the prior art that the terminal re-selects the ping-pong between the two networks due to the inconsistency of the RFSP determined by the MSC and the first device.

FIG. 11 is a schematic structural diagram of another embodiment of an MSC according to the present invention. As shown in FIG. 11, on the basis of the foregoing embodiment of the method shown in FIG. 10, the obtaining unit 32 includes: a contracted RFSP obtaining sub-unit 321 and a sub-unit 322 is generated, where the subscribed RFSP acquisition sub-unit 321 is used for location update in the CS domain, and the subscribed RFSP corresponding to the terminal identifier is obtained from the HSS; the generating sub-unit 322 is configured to use the voice capability and configuration corresponding to the terminal identifier, The Subscribed RFSP and the pre-configured carrier policy generate RFSP in using corresponding to the terminal identifier.

Further, the receiving unit 31 is further configured to receive an identifier request message that is sent by another MSC and that carries the identifier of the terminal. The MSC further includes: the sending unit 33 is further configured to send the identifier response message to another MSC according to the identifier request message. The identifier response message includes a voice capability and a configuration corresponding to the RFSP in using and/or the terminal identifier corresponding to the terminal identifier.

FIG. 12 is a schematic structural diagram of still another embodiment of an MSC according to the present invention. As shown in FIG. 12, the MSC includes: a sending unit 41 and a receiving unit 42, where the sending unit 41 is configured to send a subscription data request carrying the terminal identifier to The receiving unit 42 is configured to receive the terminal identifier and the terminal identifier returned by the HSS. Know the corresponding RFSP in using.

The MSC of this embodiment can perform the technical solution of the method embodiment shown in FIG. 6, and the implementation principle is similar, and details are not described herein again.

In this embodiment, the MSC sends a subscription data request carrying the terminal identifier to the HSS, and receives the RFSP in using corresponding to the terminal identifier and the terminal identifier returned by the HSS, because the RFSP in using corresponding to the terminal identifier is from the first Obtained in the device, so that the RFSP in using corresponding to the terminal identifier in the MSC is consistent with the RFSP in using corresponding to the terminal identifier in the first device, thereby effectively solving the prior art determination by the MSC and the first device. The RFSP is inconsistent and causes the terminal to have a problem of network reselection of ping-pong between the two networks.

12 is a schematic structural diagram of an embodiment of a control system according to the present invention. As shown in FIG. 12, the system of this embodiment includes: a device 51, an HSS 52, and an MSC 53, wherein the device 51 can perform the operations shown in FIG. 1 to FIG. The technical solution of the method embodiment, the HSS 52 can perform the technical solution of the method embodiment shown in FIG. 4, and the MSC 53 can perform the technical solution of the method embodiment shown in FIG. 5 or FIG. 6, and the implementation principle is similar, and the details are not described herein. .

In the embodiment, the system solves the problem that the terminal re-selects the ping-pong between the two networks due to the inconsistency of the RFSP in using determined by the MSC and the device in the prior art, and saves a lot of resources.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

It should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that: The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced; and the modifications or substitutions do not deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

Rights request

A control method, comprising:

The first device receives an attach request or an update request that is sent by the terminal and carries the terminal identifier, and generates a used radio access technology or frequency selection priority corresponding to the terminal identifier.

The first device provides the terminal identifier and the RFSP in using to a mobile switching center; wherein the first device is a mobility management entity or a serving general packet radio service supporting node.

The control method according to claim 1, wherein the generating the RF SP in using with the terminal identifier comprises:

Sending, to the home subscriber server HSS of the terminal, a subscription data request carrying the terminal identifier, and receiving an RFSP that is sent by the HSS and corresponding to the terminal identifier;

Generating RFSP in using corresponding to the terminal identifier according to the obtained voice capability and configuration corresponding to the terminal identifier, the signed RFSP, and the pre-configured operator policy.

The control method according to claim 1, wherein the first device sends the terminal identifier and the RFSP in using to the mobile switching center to send a message, including:

The first device sends a notification request message to the HSS, where the notification request message includes the terminal identifier and the RFSP in using corresponding to the terminal identifier; and the HSS receives the carried terminal identifier sent by the mobile switching center. Sending the terminal identifier and the RFSP in using corresponding to the terminal identifier to the mobile switching center; or

The first device sends a location update request message to the mobile switching center, where the location update request message includes the terminal identifier and the RFSP in using corresponding to the terminal identifier.

The control method according to claim 3, wherein the location update request message further includes a voice capability and a configuration corresponding to the identifier of the terminal, and the voice capability and configuration corresponding to the terminal identifier are used to generate an RFSP in using .

The control method according to claim 3, further comprising:

When the terminal initiates a network exit process, the first device carries the terminal identifier in the Sending to the HSS in the request message, so that the HSS deletes the RFSP in using corresponding to the terminal identifier.

The control method according to any one of claims 2 to 5, further comprising: one or more of a voice capability and configuration corresponding to the terminal identifier, the signed RFSP, and the operator policy. When the item changes, the first device updates the RFSP in using corresponding to the terminal identifier.

7. The control method according to claim 6, further comprising:

The first device sends the updated RFSP in using and the terminal identifier to the HSS in the notification request message; or

The first device sends the updated RFSP in using and the terminal identifier in the location update request message to the mobile switching center.

8. A control method, comprising:

The HSS receives the subscription data request that is sent by the mobile switching center and carries the terminal identifier, and sends the RFSP in using corresponding to the terminal identifier to the mobile switching center.

The control method according to claim 8, further comprising:

Receiving, by the HSS, a notification request message that carries the updated RFSP in using corresponding to the terminal identifier and the terminal identifier;

The HSS carries the updated RFSP in using corresponding to the terminal identifier and the terminal identifier in an inserted user data message and sent to the mobile switching center.

The control method according to claim 8 or 9, further comprising: the HSS receiving the notification request that is sent by the first device and carrying the terminal identifier:

And according to the notification request message, the RFSP in using corresponding to the terminal identifier is deleted.

11. A control method, comprising:

Receiving, by the mobile switching center, a location update request message sent by the first device, where the first device is a mobile management entity/service general packet radio service support node;

The control method according to claim 11, wherein the location update request message includes the terminal identifier and the RFSP in using generated by the first device and corresponding to the terminal identifier.

The control method according to claim 11, wherein the location update request message includes the voice identity and configuration corresponding to the terminal identifier and the terminal identifier acquired by the first device, and the mobile switching center Acquiring the terminal identifier and the terminal identifier of the RF SP in using according to the location update request message, including:

The mobile switching center is updated in the circuit domain service domain, and the RFSP corresponding to the terminal identifier is obtained from the home subscriber server;

The mobile switching center generates an RFSP in using corresponding to the terminal identifier according to the voice capability and configuration corresponding to the terminal identifier, the RFSP subscribed by the user, and the pre-configured operator policy.

The control method according to claim 13, further comprising:

The mobile switching center receives an identifier request message that is sent by another mobile switching center and carries a terminal identifier;

The mobile switching center sends an identifier response message to the another mobile switching center according to the identifier request message, where the identifier response message includes an RFSP in using corresponding to the terminal identifier and/or the terminal identifier Voice capabilities and configuration.

15. A control method, comprising:

The mobile switching center sends a subscription data request carrying the terminal identifier to the home subscriber server HSS;

Receiving, by the mobile switching center, the terminal identifier returned by the HSS and a used radio access technology or frequency selection priority corresponding to the terminal identifier, RFSP in using „

16. An apparatus, wherein the apparatus comprises:

And a sending unit, configured to provide the terminal identifier and the RFSP in using to the mobile switching center.

17. Apparatus according to claim 16 wherein:

The sending unit is further configured to send, to the home subscriber server HSS of the terminal, a subscription data request that carries the terminal identifier;

The receiving unit is further configured to receive an RFSP that is sent by the HSS and is associated with the terminal identifier;

The generating unit is further configured to generate, according to the voice capability and configuration corresponding to the terminal identifier, the signed RFSP, and the pre-configured operator policy, the RFSP in using corresponding to the terminal identifier. .

The device according to claim 16, wherein the sending unit is configured to send a notification request message to the HSS, where the notification request message includes the terminal identifier and the RFSP in using corresponding to the terminal identifier; Receiving, by the mobile switching center, the subscription data request that carries the terminal identifier, the HSS sends the terminal identifier and the RFSP in using corresponding to the terminal identifier to the mobile switching center; or

The sending unit is specifically configured to send a location update request message to the mobile switching center, where the location update request message includes the terminal identifier and the RFSP in using corresponding to the terminal identifier.

The device according to claim 18, wherein the sending unit is further used to When the terminal initiates the network exit process, the terminal identifier is carried in the notification request message and sent to the HSS, so that the HSS deletes the RFSP in using corresponding to the terminal identifier.

The device according to any one of claims 17 to 19, further comprising: an updating unit, configured to: when the terminal identifies a corresponding voice capability and configuration, the signed RFSP, and the operator When one or more of the policies change, the RFSP in using corresponding to the terminal identifier is updated.

The device according to claim 20, wherein the sending unit is further configured to: send the updated RFSP in using and the terminal identifier to the HSS in the notification request message; or

The sending unit is further configured to send the updated RFSP in using and the terminal identifier to the mobile switching center in the location update request message.

22. A home subscriber server, comprising:

The home subscriber server according to claim 22, wherein the receiving unit is further configured to receive a notification request message that carries the updated RFSP in using corresponding to the terminal identifier and the terminal identifier;

The home subscriber server further includes:

An updating unit, configured to replace the existing RFSP in using corresponding to the terminal identifier Stored RFSP in using corresponding to the terminal identifier;

The sending unit is further configured to carry the updated RFSP in using corresponding to the terminal identifier and the terminal identifier in an inserted user data message and send the message to the mobile switching center.

The home subscriber server according to claim 22 or 23, wherein the receiving unit is further configured to receive the notification request that is sent by the first device and that carries the terminal identifier:

The home subscriber server further includes: a deleting unit, configured to delete the RFSP in using corresponding to the terminal identifier according to the notification request message.

25. A mobile switching center, comprising:

a receiving unit, configured to receive a location update request message sent by the first device, where the first device is a mobility management entity/service general packet radio service support node;

An obtaining unit, configured to acquire, according to the location update request message, a terminal identifier and an RFSP in using the terminal identifier

The mobile switching center according to claim 25, wherein, if the location update request message includes the voice capability and configuration corresponding to the terminal identifier and the terminal identifier acquired by the first device, the acquiring The unit includes:

The contracted RFSP acquisition subunit is configured to update the location in the circuit domain service domain, and obtain the contracted RFSP corresponding to the terminal identifier from the home subscriber server;

And generating a sub-unit, configured to generate an RFSP in using corresponding to the terminal identifier according to the voice capability and configuration corresponding to the terminal identifier, the RFSP subscribed by the user, and the pre-configured operator policy.

The mobile switching center according to claim 26, further comprising: the receiving unit is further configured to receive an identifier request message that is sent by another mobile switching center and that carries a terminal identifier;

Then the mobile switching center further includes:

a sending unit, configured to send an identifier response message to the another mobile switching center according to the identifier request message, where the identifier response message includes an RFSP in using and the terminal identifier / or the voice capability and configuration corresponding to the terminal identifier.

28. A mobile switching center, comprising:

a sending unit, configured to send a subscription data request carrying the terminal identifier to the home subscriber server, and a receiving unit, configured to receive the terminal identifier returned by the home subscriber server and the used radio access technology or frequency selection corresponding to the terminal identifier Priority RFSP in using ₀

A control system, comprising: the apparatus according to any one of claims 16 to 21, the home subscriber server according to any one of claims 22 to 24, and the claims 25 to 28 A mobile switching center as described.