WO2011153850A1

WO2011153850A1 - System, method and terminal for implementing real-name system management

Info

Publication number: WO2011153850A1
Application number: PCT/CN2011/071498
Authority: WO
Inventors: 梁西广
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-06-07
Filing date: 2011-03-03
Publication date: 2011-12-15
Also published as: CN101909277A

Abstract

The invention discloses a system, method and terminal for implementing real-name system management. The system includes: an Operation Management Desktop (OMD), for obtaining user characteristic information provided by a user, transmitting the obtained user characteristic information to an authentication center, and receiving an authentication result from the authentication center, wherein the authentication result is used to indicate if the user characteristic information reserved in the authentication center is the same as the user characteristic information transmitted from the OMD, and if they are same, OMD reads out a terminal identification of the user, binds it with the user characteristic information and transmits them; a Subscriber Information Authentication Center (SIAC), for receiving the bound user characteristic information and terminal identification, and saving the bound user characteristic information and terminal identification as the real-name system information of the user, wherein the real-name system information is used to identify whether the terminal has registered in real-name system. The invention can determine the user detail information of each terminal accurately and facilitate a high degree of management and monitor for the terminals.

Description

TECHNICAL FIELD The present invention relates to the field of data network communications, and in particular, to a system and method for implementing real-name management, and a terminal. BACKGROUND With the promotion of mobile communication services and the development of telecommunication technologies, the number of users of terminals (for example, mobile phones) is large, and various communication services provided by terminals can provide great communication and information sharing between terminal users. convenient. Although the powerful communication function of the terminal can provide users with convenience in life, some illegal and bad content will also be widely distributed between terminals, which will not only affect the user experience, but also increase the network burden.

In order to avoid the spread of various bad information, you need to find the source of the information. However, since the current terminal application is not in the real name system, as long as the terminal performs the network registration, it is possible to perform services such as short messages and calls at will. In order to curb the spread of bad and illegal information, the currently commonly used measures are to determine the number of the terminal and locate the terminal, and to filter the content of the communication.

But the above measures are not enough to effectively eliminate the source of information dissemination. With the current technology, only the information transmitted by the short message can be filtered, and the content of the call cannot be managed and controlled, and when the content of the short message is filtered, the keyword and the short message content to be filtered are often used. The matching is performed, but the user who sends the short message can easily modify the content of the short message to avoid the filtering condition, thereby invalidating the filtering condition. In addition, based on the current technology and network architecture, although the terminal number that transmits illegal and bad information can be found, but the user information of the operation terminal cannot be known, the true source of illegal and bad information cannot be found.

In addition to the above problems, since the current terminal does not perform real-name registration, it also causes a variety of problems that are inconvenient for terminal management. However, effective solutions have not been proposed for these problems. SUMMARY OF THE INVENTION In view of the above, in the related art, the real-name system management of the terminal cannot be performed, and the terminal is not easily managed effectively. The present invention provides a real-name system management implementation system and method, and a terminal, which can effectively manage and purify the terminal based on the real-name system. Web environment.

In order to solve the above technical problem, the technical solution of the present invention is implemented as follows: An implementation system for real-name management, including:

An operation management platform OMD, configured to acquire user characteristic information provided by the user, send the obtained user characteristic information to the authentication center, and receive an authentication result from the authentication center, where the authentication result is used to indicate the Whether the user feature information pre-stored in the authentication center is consistent with the user feature information sent by the OMD, and if they are consistent, the terminal identifier of the user is read, and the user feature information is tied to the terminal identifier. Set and send;

The user information authentication center (SIAC) is configured to receive the user feature information and the terminal identifier that are bound, and save the bound user feature information and the terminal identifier as the real name information of the user, where The real name information is used to identify whether the terminal has performed real name registration.

The SIAC is further configured to log off, modify, and/or query the real name information according to the request. The request comes from the terminal or the OMD.

If the request is from a terminal, the request is forwarded by the designated communication network element to the SIAC. The SIAC is further configured to notify the designated communication network element whether the user has performed real-name registration.

The designated communication network element includes one of the following: a mobile switching center MSC, a visitor location register VLR, and a home location register HLR.

The system further includes: a short message monitoring center SMMC, configured to receive a short message sent by the terminal through the short message center, and perform legality verification on the short message, and allow the short message to pass the legality verification. The short message center continues to send the short message.

The system further includes: a network management center NMC, configured to monitor an operating status of the OMD, the SIAC, and the SMMC.

The user characteristic information includes: identity information of the user, or a user identity feature identifier, or a combination of the two; and/or, the terminal identifier includes one of the following: a terminal number.

A terminal, comprising:

a storage module, configured to store real-name information of the terminal;

a requesting module, configured to send an operation request to the SIAC that stores the real name information of the terminal, and configured to store the real name information from the SIAC in the storage module according to an instruction of the user, where the operation request is used for And requesting to query and/or modify the real-name information of the terminal that is stored by the SIAC; the determining module is configured to determine whether the real-name information of the terminal is stored in the storage module, and if the determination is negative, The use of some or all of the services on the terminal is limited.

A method for realizing real-name management includes: The OMD obtains user characteristic information provided by the user, and sends the user characteristic information to the authentication center, and receives an authentication result from the authentication center, where the authentication result is used to indicate a user pre-saved in the authentication center. Whether the feature information is consistent with the user feature information sent by the OMD, and if they are consistent, the OMD reads the terminal identifier of the user, and binds the user feature information to the terminal identifier; The bound user feature information and the terminal identifier are saved as the real name information of the user, wherein the real name information is used to identify whether the terminal performs real name registration.

By means of the above technical solution of the present invention, the user with invalid user feature information can be effectively prevented from registering by real name system, and the detailed information of the user of each terminal can be accurately determined, which facilitates high-level management and monitoring of the terminal, and facilitates tracking of illegal transmission of the terminal. Content, which helps to clean up the network environment; and provides a reliable basis for applications such as electronic payments that require strict authentication based on the terminal. BRIEF DESCRIPTION OF DRAWINGS FIG. 1 is a schematic structural diagram of an implementation system for real-name management in an embodiment of the present invention;

2 is a schematic structural diagram of an implementation system and an operator network of a real name management system according to an embodiment of the present invention; FIG. 3 is a schematic diagram of a real name system management implementation system and an existing PLMN network element and a terminal according to an embodiment of the present invention;

4 is a schematic diagram of a process of OMD processing logic according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a process of SIAC processing logic according to an embodiment of the present invention; FIG.

6 is a schematic diagram of a process of specifying communication network element processing logic in an operator network according to an embodiment of the present invention; FIG. 7 is a schematic diagram of a process of terminal processing logic according to an embodiment of the present invention;

FIG. 8a is a schematic flowchart 1 of a method for implementing real-name management according to an embodiment of the present invention; FIG.

8b is a schematic diagram of a signaling flow of a real-name system management implementation method according to an embodiment of the present invention; FIG. 9 is a schematic flowchart of a real-name system information registration process according to an embodiment of the present invention;

10 is a schematic flowchart of a process for a terminal to initiate a real-name information query according to an embodiment of the present invention; FIG. 11 is a schematic flowchart of a process for initiating real-name information query by an OMD according to an embodiment of the present invention; FIG. 12 is a schematic diagram of a terminal-initiated real-name system according to an embodiment of the present invention. FIG. 13 is a schematic diagram of a process flow for modifying or deregistering real-name information of an OMD according to an embodiment of the present invention; FIG. 14 is a schematic structural diagram of a terminal according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION The present invention provides a method and system for real-name management, which can be based on whether user feature information is true and It is legal to determine whether to allow users to register real-name information, thereby preventing illegal users from registering, which can effectively prevent illegal users from using the terminal to illegally transmit information, and can accurately determine the detailed information of each terminal user, thereby helping to trace and transmit illegal information. The terminal can effectively clean up the network environment and avoid unnecessary network overhead.

1 is a schematic structural diagram of an implementation system for real-name management in an embodiment of the present invention. As shown in FIG. 1, the system includes:

The operation management platform (OMD) 11 can be distributedly distributed in multiple regions, and the acquired user characteristic information is sent to the certification center (for example, a trusted institution such as a public security network), and the authentication result from the certification center is received, wherein The authentication result is used to indicate whether the pre-stored user feature information in the authentication center is consistent with the user feature information sent by the OMD 11. If the authentication result indicates that the two are consistent, the user terminal identifier is read, and the user feature information and the terminal are The identity is bound and sent. That is to say, the OMD 11 can provide an interface for the user terminal to perform real-name registration, and send the user-characterized information provided by the user to the authentication center, so that the authentication center can judge the user characteristic information provided by the user, if the user characteristic information provided by the user is Real and legal, the user feature information is allowed to be bound to the terminal identifier of the user.

The User Information Authentication Center (SIAC) 12 can be distributedly distributed in multiple regions, and is configured to receive the bound user feature information and the terminal identifier, and save the bound user feature information and the terminal identifier as the user's real name information. And maintenance, wherein the real name information is used to identify whether the terminal has registered the real name system (that is, whether the user has registered the real name system). In this way, when the terminal initiates or the network provides related services to the terminal, it can determine whether the terminal registers the real-name information according to the terminal identifier and the real-name information stored in the SIAC 12, thereby determining whether the services continue to be performed, thereby reaching the terminal. The purpose of real-name management.

With the above system of the present invention, it is possible to effectively prevent users whose user feature information is illegal from registering with the real name system, and ensure that the real name management of the terminal can be implemented in a real and effective manner; and, since the user characteristics information of the terminal user is saved in the SIAC, the accuracy can be accurately The user details of each terminal are determined, and the terminal that transmits illegal or bad content can be traced, which facilitates high-level management and monitoring of the terminal, thereby helping to purify the network environment.

In addition, for more efficient management, the system of this embodiment may further include a Short Message Monitoring Center (SMMC) and a Network Management Center (NCC). The SMMC can be deployed in multiple areas in a distributed manner for legality-verification and filtering of short message content.

In practical applications, the real-name system management implementation system is mainly responsible for the real-name system registration work of the end user and the real-name system information management work. For example, the real-name system management implementation system according to the embodiment needs to complete the collection of user feature information and the characteristics of the mobile phone user. The information is compared with the user characteristic information stored in the authentication center, and when the judgment result is that the user characteristic information is legal, the corresponding real name information needs to be generated, and The name information and user feature information are stored and maintained, so that the terminal can be managed by the real name system, and the legitimate user is allowed to modify and query the real name information and the user feature information.

When the user carries the terminal to register the real name system, the user feature information will be input into the OMD by the operator through the input interface provided by the OMD. After that, the OMD will store the real name information in the SIAC. OMD can provide a variety of input interfaces. For example, OMD can identify the user's valid ID, read the information of the terminal smart card (for example, SIM card, UIM card, etc.) (for example, the user's mobile phone number), and, in order to increase the real Sexuality can also collect physiological information such as fingerprint information and/or iris information of users.

The SMMC (which can be implemented by a computer system) can monitor and verify the content of the short message in real time, and verify the validity of the sent short message content and filter the illegal content when the terminal initiates short message communication. Specifically, when performing verification, illegal characters in the short message can be deleted, and the remaining characters are allowed to be transmitted. If too many characters are deleted, the short message may be prohibited from being sent, that is, the short message fails to pass the verification; if the violation is more serious, the public security department may be directly notified to obtain corresponding security measures.

The NMC can be used to manage and maintain OMD, SIAC, and SMMC. Specifically, the NMC can update the programs, judgment rules, and user data in the SIAC and the SMMC according to actual needs; and can summarize the work of each SMMC and SIAC, and report to the certification center according to the predetermined reporting requirements.

2 is a schematic structural diagram of an implementation system and a carrier network of a real name management system according to an embodiment of the present invention. As shown in FIG. 2, the implementation system of real name management includes: OMD, SIAC, NMC, SMMC; the carrier network may include: Base Station (BS), Base Station Controller (BSC), Equipment Identification Register (EIR), Data Service Management Platform (DSMP), Gateway Name Server (GNS), Service Service Provider (SP), Mobile Switching Center (MSC), Visitor Location Register (VLR), Home Location Register (HLR), Short Message Center (Short Message Center, SC).

In an actual network deployment, each SIAC in a distributed deployment can connect to thousands of OMDs to receive and process operational requests from these OMDs. On the network side, a SIAC can be connected to one or more HLRs and provide services related to the user's real name system for these HLRs. The user real name system status unit exists in the HLR and VLR of the existing public land mobile communication network (PLMN) to indicate whether a user has a real name system and as a basis for providing the user with a specified service such as a short message.

As shown in Figure 2, the number of carrier networks supported by the real-name management implementation system can be multiple (in operational considerations, all carrier networks can be connected to the real-name management implementation system to accept real names). Real-name management and service of the implementation system of the management system, for example, the operator network A, the operator network B, and the carrier network C shown in FIG. 2, wherein the implementation of the real-name system management in the embodiment of the present invention When the system communicates with the carrier network, a communication interface can be set between the SIAC and the HLR, and a communication interface is set between the SMMC and the SC. Thus, the HLR can query the SIAC for the real name information of the user, and the SIAC can register the user with the real name system. The notification is sent to the HLR, and when the real name information of the user changes, the SIAC can actively notify the HLR of the changed information. For example, the user cancels the real name information, and the SIAC can notify the HLR that the user does not perform the real name registration to the user's service. The privilege is controlled; and, for the short message flow of the terminal, the SC needs to be able to interact with the SMMC, so that the short message is verified by the SMMC.

Moreover, in order to implement the modification, cancellation, and inquiry of the real-name information, it is also necessary to improve the MSC, the VLR, the HLR, and the terminal, such as the mobile terminal (MS), so as to have the relevant business unit of the real-name information. As shown in FIG. 3, in a specific implementation process, the user sends a request (for example, a real name information modification request, a real name information cancellation request, and a real name information inquiry request) to the SIAC through the terminal or the OMD, and the SIAC can perform real name system on the user according to the request. Information is logged out, modified, and/or queried. It should be noted that if the user sends a request to the SIAC through the terminal (ie, the request comes from the terminal), the request needs to be forwarded to the SIAC by the designated communication network element in the carrier network (for example, the MSC of the terminal and the HLR of the terminal). When the request is transmitted through the designated communication network element, the service MSC of the terminal may receive the request of the terminal, and send the request to the HLR of the terminal, and then the HLR sends the request to the SIAC, and returns the operation result to the terminal at the SIAC. When the real name system information or the like, the above reverse process can be used. In addition to the above methods, other transmission processes may be used for request transmission and message return, and the network elements involved in the transmission may also be changed as needed, and the text is no longer listed.

As shown in FIG. 3, in order to implement real-name management of the user terminal, it is necessary to set network elements such as OMD, SIAC, and SMMC (not shown) and NMC (not shown) in the implementation system of real-name management according to this embodiment. The user name information of the user is stored in the SIAC. The OMD can read the user identity information such as the user ID, the user identity, and the SIM card and forward it to the authentication center for verification. The PLMN needs to have the network element capable of communicating with the SIAC. These network elements may be HLRs, VLRs, etc. (corresponding to location update units in existing mobile communication networks, these network elements need to be able to store terminal identifiers of user terminals and corresponding real-name information); in order to enable real-name information to be at the terminal, The PLMN network element and the implementation system of the real name management system can also perform corresponding logical update on the PLMN network element, thereby realizing the transmission of the real name information; and, preferably, the terminal can also retain the real name information of the terminal, so as to When the user operates the terminal to communicate, the terminal can be based on the real name information in the terminal. To save, to limit the user's actions. In this way, through the terminal, PLMN network element and real The implementation system of the name management system can cooperate with each other to complete the management operations such as input, modification, query, and logout of the user's real name information. When restricting the operation of the user, the method of restricting the service may be used. For example, limiting the time of the terminal in a certain period of time, limiting the number of short messages sent by the terminal in a certain period of time, or directly prohibiting the terminal. Call and short message transmission.

FIG. 4 is a schematic diagram of the process of the OMD processing logic in the embodiment of the present invention. As shown in FIG. 4, the OMD can perform the entry, modification, and deregistration of the real name information. The following three operations are separately described.

Entry or modification of real-name information:

Read the user's valid ID (for example, the user's ID) and determine whether it is necessary to read the user-identified user identification features (such as the user's fingerprint, the user's facial features).

If the user identity feature needs to be read, the user identity feature provided by the user is read, and the user identity feature provided by the user is sent to the authentication center, waiting for the verification result, if the verification result is the provided user identity feature and If the user identity identifiers pre-stored by the authentication center are inconsistent, the verification fails. Otherwise, if the verification result is consistent (that is, the user identity feature provided by the user is consistent with the user identity feature of the user saved in the authentication center), then Read the terminal identifier of the user (for example, the SIM card number), and determine whether the information of the terminal needs to be read. If not, directly bind the valid ID information of the user to the SIAC, if necessary, After the information of the terminal is read, the valid ID information of the user is bound to the mobile terminal identifier and the mobile device information, and is sent to the SIAC. The operation result of the SIAC is received, and the operation result returned by the SIAC is received, where the operation result includes: a return code, Result (operation succeeded or fucked The failure and the reason description (for example, the reason for the operation failure); if the result is successful, the entry or modification operation is successful, and if the result is an operation failure, the entry or modification result fails;

If the user identity feature is not required to be read, the terminal identifier of the user (for example, a SIM card number) is read, and it is determined whether the information of the terminal needs to be read, and if necessary, the information of the terminal is read, if not required to be read. The information of the terminal is bound to the terminal identifier of the user and sent to the SIAC, and waits for the operation result of the SIAC to receive the operation result returned by the SIAC. The operation result includes: a return code, a result (operation success or operation failure) And the reason description (for example, the reason for the operation failure); if the result is successful, the entry or modification operation is successful, and if the result is an operation failure, the entry or modification result fails.

Logout of real-name information: After receiving the real-name information deregistration request from the operator, the OMD reads the real-name information that needs to be logged off, and sends the real-name system logout request to the SIAC to wait for the SIAC operation result; receives the operation result returned by the SIAC, where, The results include: return code, result (operation success or operation failure), and reason description (for example, the reason for the operation failure); if the result is successful, the logout operation succeeds, if the If the operation fails, the logout result fails. In addition, before reading the real-name information that needs to be logged off, the operator's cancellation qualification can be further verified, that is, whether the operator has the right to cancel the real-name information, and after the verification is passed, the real-name information that needs to be logged off is read.

5 is a schematic diagram of a process of SIAC processing logic according to an embodiment of the present invention. As shown in FIG. 5, SIAC stores real-name information of a user, and can query, modify, and log out the saved real-name information. In the specific implementation process, First, the SIAC obtains a service request from a message source, for example, a real name information deregistration request, a real name information inquiry request, a real name information status inquiry request, a service authentication request, and a real name information creation/modification or other operation request; The request performs the corresponding operation, that is, creating the real name information, modifying the real name information, unregistering the real name information, querying the real name information, querying the status of the real name information, and the business permission judgment; then, the SIAC returns the operation result to the message source. The message source may be a terminal or an OMD, that is, the user may input the request through the terminal or the OMD, and the terminal or the OMD forwards the request to the SIAC, optionally, for information security and guaranteeing the real name information. In consideration, the OMD can be used as the sole source of the real-name information creation request. That is, the user must be able to create real-name information through the OMD, but not through the terminal. It should be noted that, if the user sends a request to the SIAC through the terminal (that is, the message source is the terminal), the terminal needs to forward the request to the SIAC via the designated communication network element (for example, the MSC and the HLR) in the carrier network, and at the same time, the communication The network element is also responsible for forwarding the operation results from the SIAC to the corresponding message source. The processing logic of the designated communication network element in the process will be described below by taking FIG. 6 as an example; and the processing logic of the terminal in the process will be described by taking FIG. 7 as an example.

6 is a schematic diagram of a process of processing logic of a designated communication network element (MSC or VLR or HLR) in an operator network according to an embodiment of the present invention. As shown in FIG. 6, in a specific implementation process, first, a communication network element is specified. Receiving a service request from a message source (for example, a terminal), for example, a real name information modification request, a real name information deregistration request (not shown), a real name information inquiry request, a real name information status inquiry request, a service authentication request; Waiting timer, wherein, for the real name information modification request, setting a modification waiting timer; setting a query waiting timer for the real name information query request; setting a status waiting timer for the real name information status query request; for the service authentication request, Set the authentication wait timer; forward the service request to the SIAC, wait for the result of the operation; if the result is received or the corresponding timer expires, return the operation result from the SIAC to the message source (terminal), for the request from the OMD, SIAC Can be received directly and straight The result is sent to the OMD, or no need for forwarding the request result through other communication network elements.

7 is a schematic diagram of a process of terminal processing logic according to an embodiment of the present invention. As shown in FIG. 7, a user inputs a service request in a terminal, for example, a real name information query request, a real name information modification request, and a mobile service request. The processing of these three requests will be described separately below.

Real-name information query request: The terminal receives the real-name information query request input by the user, sets the query waiting timer, sends the real-name information query request to the designated communication network element, and waits for the query result; if the query wait timer expires, the specified communication If the operation result is successful, the specified communication network element sends the real name information of the user to the terminal, and the terminal fails to return the operation result. The real name information will be saved, and the real name information will be displayed to the user. If the operation fails, the designated communication network element will send the reason for the operation failure to the terminal, and the terminal displays the reason for the user's operation failure.

Mobile service request: The terminal receives the mobile service request input by the user, determines whether the mobile service is restricted by the real name system status, and if the mobile service is not restricted by the real name system status, the mobile service is normally processed; if the mobile service is subject to the real name system If the status is restricted, it is necessary to determine whether the user has already performed real-name registration. If the real-name registration is not performed, the service processing fails. If the user performs real-name registration, the service is normally processed.

Real-name information modification request: The terminal receives the real-name information modification request input by the user, sets the modification waiting timer, sends the real-name information modification request to the designated communication network element, and waits for the modification result; if the query modifies the waiting timer, the timer is found. If the modification succeeds, the specified communication network element will be the user. If the modification succeeds, the specified communication network element will not return the operation result. If the operation fails, and the operation result returned by the specified communication network element is received before the modification wait timeout expires, if the modification is successful, the designated communication network element will be the user. The modified real name information is sent to the terminal, and the terminal saves and displays the modified real name information to the user. If the modification fails, the designated communication network element sends the reason for the modification failure to the terminal, and the terminal displays the reason for the modification failure. To the user.

In order to enable the existing PLMN to support the above functions, the location update protocol of the user interface of the designated communication network element in the PLMN and the MAP protocol (the part related to the location update) of the network side may be updated correspondingly to enable the transmission of the PLMN network element. The message unit can carry information related to the user's real name information. In addition, in order to support the real-time query and modification of the real-name information by the user through the terminal, and to improve the security of the operation of the user terminal side, the protocol for real-name management of the user can also be implemented separately in the PLMN, so as to carry the query of the real-name information of the user, Request messages such as modification, logout operations, etc., which can be used as a subset of the MAP protocol.

According to an embodiment of the present invention, an implementation method of real name management is also provided.

As shown in FIG. 8a, the implementation method of real name management according to an embodiment of the present invention includes:

Step 801a: The OMD in the real-name system implementation system acquires user feature information provided by the user, and sends the user feature information and the terminal identifier to the authentication center (for example, a trusted institution such as a public security network), and receives the recognition. The authentication result of the certificate center, wherein the authentication result is used to indicate whether the pre-stored user feature information in the authentication center is consistent with the user feature information sent by the OMD. If they are consistent, the OMD reads the user's terminal identifier, and the user feature information is The terminal identifier is bound, where the terminal identifier includes one of the following: a terminal number (for example, a mobile phone number of the user).

Step 803a: The SIAC in the real-name system implementation system saves the bound user feature information and the terminal identifier as the user's real-name system information, wherein the real-name system information is used to identify whether the terminal performs real-name registration or provides the real-name information according to a predetermined rule. For example, if the communication content (voice, text, picture, image, video, etc.) is found to be in violation, the sender and receiver of the communication can be determined using the real name information.

Preferably, the user characteristic information comprises: the user's identity information, or the user identity feature, or a combination of the two.

FIG. 8b is a schematic diagram of a signaling flow of an implementation method of real-name management according to an embodiment of the present invention. As shown in FIG. 8b, the following steps are included:

Step 801b, the implementation system of real-name management acquires user characteristic information provided by the user, and sends the user characteristic information to the public security network, and the public security network compares the user characteristic information of the real-time system realization realization system with the user characteristic information saved in the public security network. If the user feature information is consistent, the real-name management implementation system reads the user's terminal identifier, and binds the user feature information to the terminal identifier.

Step 803b: The implementation system of the real name management saves the bound user characteristic information and the terminal identifier as the real name information of the user, wherein the real name information is used to identify whether the terminal performs the real name registration.

The user feature information includes: a user identity information, or a user identity feature identifier, or a combination of the two. The terminal identifier includes one of the following: a terminal number.

The various processing flows in the system will be described in detail below in conjunction with the system described previously.

Preferably, in order to ensure the authenticity of the real name information, the registration of the real name information must be performed by the OMD, and the user performs the registration with the assistance of the operator. FIG. 9 is a schematic diagram of the processing flow of the real name information registration according to the embodiment of the present invention, such as As shown in Figure 9, the following steps are included:

Step 901: The OMD reads the user identity feature identifier (for example, the user's fingerprint, the user's facial feature, and the like) provided by the user, and determines the real information of the user itself based on the user identity identifier of the user.

Step 902, the OMD reads the identity information provided by the user (for example, the identity information on the user's valid ID information can be read).

Step 903: The OMD sends the user identity feature identifier and identity information provided by the user to the public security network through the interface between the OMD and the public security network, so that the public security network can verify the authenticity of the user and the user identity. Step 904: The public security network compares the user identity feature identifier provided by the user with the user identity feature identifier of the user saved by the public security network, and compares the identity information provided by the user with the user identity information saved by the public security network, if both If they are all consistent, the verification passes, and the process proceeds to step 905. If one of the two is inconsistent, the verification fails, and the process ends.

Step 905: The OMD reads the terminal identifier of the user, for example, a SIM card number.

Step 906: The OMD binds the user feature information and the SIM card number, and sends the bound user feature information and the SIM card number to the SIAC through the interface between the OMD and the SIAC to implement real-name information input. The user feature information may be the identity information of the user, or the identity of the user identity, or a combination of the two.

Step 907: The SIAC receives the bound user feature information and the SIM card number, creates a real name information record, and saves the user feature information and the SIM card number as the user's real name information.

In step 908, the SIAC returns the operation result to the OMD. For example, the operation result shows that the real name information is successfully entered.

Step 909, the OMD displays the above operation result to the user.

The user can perform the query of the real name information on the OMD, or perform the query of the real name information on the terminal, which will be described below in conjunction with FIG. 10 and FIG.

FIG. 10 is a schematic flowchart of a process for a terminal to initiate real-name information query according to an embodiment of the present invention. As shown in FIG. 10, the method includes the following steps:

Step 1001: The user selects and starts a function for querying real-name information in the terminal, and the terminal responds to the user selection to generate a real-name information query request;

Step 1002: The terminal sends a real-name information query request to the designated communication network element in the carrier network, where the query request carries the terminal identifier, for example, a SIM card number.

Step 1003: The designated communication network element forwards the real-name information query request to the SIAC.

Step 1004: The SIAC searches for the real-name information of the user according to the SIM card number in the real-name information query request, and obtains the query result.

Step 1005: The SIAC sends the query result to the designated communication network element. If the query is successful, the query result is the corresponding real name information; if the query fails, the query fails to be returned, and the reason for the query failure is returned, wherein the query fails. The reason may be that the user does not have the query permission, or the real name information does not exist, etc.;

Step 1006: The designated communication network element forwards the query result to the terminal.

Step 1007: The terminal receives the query result, and if the query is successful, saves the real name information;

In step 1008, the terminal outputs the query result, and displays the result to the user. In addition to the query operation, the modification of the user's real name information can also be initiated by the user through the terminal that has registered the real name information. At this point, the user should be considered to be authentic, and the user has the right to modify the real-name information corresponding to his terminal identifier. The modification operation may be supported by an application in the terminal, and the application should be able to guide the user to input the required information, generate a real name information modification operation request, and transmit the modification operation request to the designated communication network element in the network, and finally reach the SIAC. After the modified application receives the result of the operation, it should display the result of the operation. After the modification request is sent, the terminal may start the modification waiting timer. If the timer expires and the terminal still does not receive the operation result, the operation of the request is considered to have failed. The process of logout is similar to the above process, except that the content of the request message and the processing method on the network side are different. In addition, the query, modification, and logout of the real-name information may be initiated by the user through the terminal, and the method of querying may also be sending a short message to a specific service number or dialing a phone number of a specific service.

In addition, in the case that the terminal initiates the real-name information status query, a process similar to that of FIG. 10 can also be used. The difference is that the request sent by the terminal is a real-name information status query request, and the query result obtained by the SIAC indicates whether the user has performed. Status information of real-name registration.

FIG. 11 is a schematic flowchart of a process for an OMD to initiate a real-name information query according to an embodiment of the present invention. As shown in FIG. 11, the method includes the following steps:

Step 1101: The OMD enters the real-name query information provided by the user, where the query information is a terminal identifier, for example, a SIM card number;

Step 1102: The OMD generates a real-name information query request, and sends a real-name information query request to the SIAC. Step 1103: The SIAC queries the real-name information of the user according to the SIM card number in the real-name information query, and obtains the query result.

Step 1104: The SIAC sends the query result to the OMD. If the query is successful, the query result is set to the corresponding real name information; if the query fails, the query fails to be returned, and the reason for the query failure is returned, wherein the reason for the query failure may be There is no query permission for the user, or the real name information does not exist, etc.;

In step 1105, the OMD outputs the query result and displays the result to the user.

In addition, in the case that the OMD initiates the real-name information status query, a process similar to that of FIG. 11 can also be used. The difference is that the request sent by the OMD is a real-name information status query request, and the result obtained by the SIAC is whether the user has performed. Status information of real-name registration.

The user can perform modification or cancellation of the real name information on the OMD, and can also perform modification or cancellation of the real name information on the terminal. Since the process of modification and cancellation is similar, in the following description, the modification will be performed with reference to FIG. 12 and FIG. The process and the logout process are combined. FIG. 12 is a schematic flowchart of a process for modifying or deregistering real-name information by a terminal according to an embodiment of the present invention. As shown in FIG. 12, the method includes the following steps:

Step 1201: The user selects and starts a function of modifying or deregistering the real name information in the terminal, and the terminal responds to the user's selection to generate a real name information modification or cancellation request;

Step 1202: The terminal sends a real-name information modification or cancellation request to the designated communication network element in the operation network, where the modification or cancellation request carries the terminal identifier (for the modification operation, the request should also include new real-name information), for example, SIM Card number

Step 1203, the designated communication network element forwards the real name system information modification or cancellation request to the SIAC;

In step 1204, the SIAC modifies or deregisters the terminal identifier in the request according to the real name information (for the modification operation, there is also a new real name information), and modifies or deregisters the real name information of the user, and obtains the modified result or the logout result; Step 1205, the SIAC will modify The result or the logout result is sent to the specified communication network element. If the modification or logout is successful, the modified real name information is returned or the logout is successful. If the modification or logout fails, the modification or logout failure is returned, and the reason for the modification or logout failure is also returned. The reason for the modification or cancellation failure may be that the user has no modification or logout permission, or the real name information does not exist, or the operation wait result is not received when the wait timer/logout wait timer expires;

Step 1206: The designated communication network element forwards the modification result or the logout result to the terminal.

Step 1207: The terminal receives the modification result or the logout result. If the modification succeeds, the modified real name system information is saved, and if the logout is successful, the real name system information saved by the terminal is deleted;

Step 1208: The terminal outputs the modification result or the logout result, and displays the result to the user.

FIG. 13 is a schematic flowchart of a process for modifying or deregistering real-name information by an OMD according to an embodiment of the present invention. As shown in FIG. 13, the method includes the following steps:

Step 1301, the OMD enters the real name modification or cancellation information provided by the user, and the modification or cancellation information is a terminal identifier (for the modification operation, the new real name information is also included), for example, a SIM card number (such as a user's mobile phone number);

Step 1302, the OMD generates a real name system information modification or cancellation request, and sends the real name system information modification or cancellation request to the SIAC;

Step 1303: The SIAC modifies or deregisters the terminal identifier in the request according to the real name information (including the new real name information for the modification operation), and modifies or cancels the real name information of the user, and obtains the modified result or the logout result; Step 1304, the SIAC will modify The result or the logout result is sent to the OMD. If the modification or logout is successful, the modified real name information is returned or the logout is successful; if the modification or logout fails, the modification or logout failure is returned. At the same time, the reason for the modification or cancellation failure is returned. The reason for the modification or cancellation failure may be that the user has no modification or cancellation permission, or the real name information does not exist;

In step 1305, the OMD outputs a modification or logout result, and displays the result to the user.

In addition, for the process of querying the user's real name information status, usually, the process is generally initiated by the HLR or VLR and triggered by the user's location update process. When the terminal performs location update, the VLR will query the HLR of the terminal user for the real name information of the user. The HLR then establishes and sends a real name information status query request to the SIAC. After receiving the successful operation result, the user real name status is returned to the VLR. If the timeout does not receive the result of the operation, or if the result of the failed operation is received, the processing is considered to have failed.

Therefore, it can be seen from the processing shown in FIG. 10 and FIG. 11 that when initiating the operation of querying, modifying, etc. of the real name information of the user, regardless of whether the initiator is a terminal or an OMD, as long as the user has the right to perform the corresponding operation, on the network side There should be corresponding processing, and eventually SIAC needs to be involved in the process.

FIG. 14 is a schematic structural diagram of a terminal in the embodiment of the present invention. As shown in FIG. 14, the terminal includes: a storage module 141, configured to store real-name information of the terminal;

The requesting module 142 is connected to the storage module 141, configured to send an operation request to the SIAC storing the real name information of the terminal, and configured to store the real name information from the SIAC in the storage module 141 according to the user's instruction, where the operation request is used for Requesting to query and/or modify the real name information of the terminal stored by the SIAC; the determining module 143 is connected to the storage module 141, and is configured to determine whether the real name information of the terminal is stored in the storage module, and the terminal is determined to be no. There are restrictions on the use of some or all of the business.

The limitation on the service may include: limiting the time of the terminal call in a certain period of time, limiting the number of short messages sent by the terminal in a certain period of time, and directly prohibiting the call and short message transmission of the terminal.

Through the terminal, the implementation system of the real-name system management can be further improved, the management strength can be further improved, the effective implementation of the real-name system can be ensured, and the user can manage the real-name information on the terminal side, which is convenient for the user's application.

In summary, the above technical solution of the present invention can effectively prevent users whose user feature information is illegal from registering by real name system, and can accurately determine the detailed information of the user of each terminal, thereby facilitating high-level management and monitoring of the terminal, and facilitating tracing. The terminal transmits illegal and bad content, which helps to purify the network environment; and provides a reliable basis for electronic payment and other applications that need to be strictly based on the terminal for authentication.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., which are included in the spirit and scope of the present invention, should be included in the present invention. Within the scope of protection.

Claims

Claim

1. An implementation system for real-name management, characterized in that it comprises:

2. The implementation system of claim 1 wherein:

The SIAC is further configured to log off, modify, and/or query the real name information according to the request.

3. The implementation system according to claim 2, wherein the request is from a terminal or the OMD.

4. The implementation system of claim 3, wherein if the request is from a terminal, the request is forwarded by the designated communication network element to the SIAC.

The implementation system according to claim 4, wherein the SIAC is further configured to notify the designated communication network element whether the user has performed real-name registration.

The implementation system according to claim 4, wherein the designated communication network element comprises one of the following: a mobile switching center MSC, a visitor location register VLR, and a home location register HLR.

The implementation system according to any one of claims 1 to 6, wherein the system further comprises: a short message monitoring center SMMC, configured to receive a short message sent by the terminal via the short message center, and the short message The message is verified for legality, and in the case that the short message passes the validity verification, the short message center is allowed to continue to send the short message.

The implementation system of claim 7, wherein the system further comprises:

The network management center NMC is configured to monitor the running status of the OMD, the SIAC, and the SMMC.

9. An implementation system according to any one of claims 1 to 6, characterized in that

The user feature information includes: a user identity information, or a user identity feature identifier, or both Combination; and/or,

The terminal identifier includes one of the following: a terminal number.

10. A terminal, comprising:

a storage module, configured to store real-name information of the terminal;

11. A method for realizing real name management, characterized in that it comprises:

The OMD obtains user characteristic information provided by the user, and sends the user characteristic information to the authentication center, and receives an authentication result from the authentication center, where the authentication result is used to indicate a user pre-saved in the authentication center. Whether the feature information is consistent with the user feature information sent by the OMD, and if they are consistent, the OMD reads the terminal identifier of the user, and binds the user feature information to the terminal identifier; The bound user feature information and the terminal identifier are saved as the real name information of the user, wherein the real name information is used to identify whether the terminal performs real name registration.

The method according to claim 11, wherein the method further comprises:

The SIAC cancels, modifies, and/or queries the real name information upon request.

The implementation method according to claim 12, wherein the request is from a terminal or the OMD.

14. The implementation method according to claim 13, wherein if the request is from a terminal, the request is forwarded by the designated communication network element to the SIAC.

The method according to claim 14, wherein the method further comprises: the SIAC notifying the user of the real name registration to the designated communication network element.

16. The method according to any one of claims 11 to 15, characterized in that

The user feature information includes: a user identity information, or a user identity feature identifier, or a combination of the two; and/or,

The terminal identifier includes one of the following: a terminal number.