WO2011140736A1

WO2011140736A1 - Network entity and method for protecting data in unstructured supplementary service data

Info

Publication number: WO2011140736A1
Application number: PCT/CN2010/075070
Authority: WO
Inventors: 盖萌萌; 赵斌
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-05-12
Filing date: 2010-07-08
Publication date: 2011-11-17
Also published as: CN101854607A

Abstract

A method for protecting data in the unstructured supplementary service data (USSD) is provided, and the method includes: a network entity sends and buffers service data based on a service session, and monitors whether the network is abnormal at the same time; when the network is abnormal, the network entity re-monitors the network state in a predetermined period. With the solution of the present invention, when the network is abnormal, the network entity will not discard the current service data, but store the service data according to the network state and monitor the network state in real time; when the network recovers, the network entity will continue transmitting the stored service data to a next-level network entity; if the network can not recover in a short time, the network entity will store the current service session state in the buffer. Thus, the trouble for users caused by the interaction between service sessions is avoided.

Description

Method for protecting data in network entities and unstructured supplementary data services

The present invention relates to the field of mobile communications, and in particular, to a method for protecting data in a network entity and an unstructured supplementary data service. Background technique

The Unstructured Supplementary Service Data (USSD) is an interactive data service based on the Global System for Mobile Communications (GSM). It is a new service based on the short message system of the GSM system. The USSD business mainly includes supplementary services (such as call barring, call forwarding, etc.) and non-structural supplementary services (such as securities transactions, information inquiry, mobile banking, etc.).

The USSD service can be initiated by the mobile station or by the network side. When initiated by the network side, the network side initiates the USSD service entity includes a home location register (HLR, Home Location Register), a visitor location register (VLR, Visitor Location Register), a mobile switching center (MSC, Mobile Switching Center) ₀ network After the entity sends the request, it receives a response from the mobile station or releases the service session after the timer expires. In all service sessions, the mobile station only contacts the MSC directly. The HLR's contact with the mobile station requires the handover of the VLR and the MSC. The connection between the VLR and the mobile station requires the handover of the MSC. In a business session, the handover of the VLR and the MSC is only transparent, ie no processing.

According to the provisions of the USSD protocol, during a service session, when the network status is abnormal due to unstable state, temporary connection interruption, resource conflict, or occupation by high-priority services, the network entity acting as the receiver will send the sender network. The entity returns an error notification and releases the current business session. At this point, the following problem will occur: When an error occurs in the receiving network entity, due to unstable or temporarily interrupted network status, the error notification has not been returned to the sending network entity. The sender network entity still releases the current service session, which will result in the loss of business data. Summary of the invention

The main object of the present invention is to provide a method for protecting data in a network entity and an unstructured supplementary data service, so as to avoid loss of service data when an abnormality occurs in the network.

The present invention provides a method for protecting data in an unstructured supplementary data service, comprising the following steps:

The network entity sends and caches service data based on the service session, and monitors whether the network is abnormal.

When an abnormality occurs in the network, monitor whether the network returns to normal within a predetermined period of time;

When the network returns to normal within a predetermined time period, the network entity resends the cached service data based on the current service session.

Before the network is abnormal, before the network is monitored for a predetermined period of time, the method further includes: the network entity saving the state of the current service session.

The method further includes: when the network does not return to normal within a predetermined time period, the network entity releases the current service session and generates an error report, where the error report includes the status of the current service session.

The method further includes: determining, by the network entity, whether the number of error reports exceeds a preset number, and if the preset number is exceeded, deleting the first error report generated.

The method further includes: when it is detected that no abnormality occurs in the network, the network entity releases the current service session.

A network entity, including:

a sending module, configured to send service data based on the service session; when the network returns to normal within a predetermined time period, resending the cached service data based on the current service session;

a cache module, configured to cache service data sent by the sending module;

a monitoring module for monitoring whether an abnormality occurs in the network, and when an abnormality occurs in the network, Monitor whether the network is back to normal within the scheduled time period.

The cache module is further configured to save the state of the current service session when an abnormality occurs in the network. The network entity further includes a session module, configured to release the current service session and generate an error report when the network does not return to normal within a predetermined time period; and the error report includes a status of the current service session.

The session module is further configured to determine whether the number of error reports exceeds a preset number, and when the preset number is exceeded, delete the first error report generated.

The session module is further configured to release the current service session when no abnormality occurs in the network. The method for protecting data in the network entity and the unstructured supplementary data service provided by the present invention, when the network is abnormal, the network entity does not lose the current service data, but saves the service data according to the network state and monitors the network in real time. Status; When the network is restored, the network entity will continue to send the saved service data to the next-level network entity; when the network cannot recover in a short time, the network entity saves the current service session state to the buffer. The saved service session status allows the user to initiate a plurality of services. If the network is abnormal, the network entity determines the current network status. When the network is restored, the service session status is fed back to the mobile station. The state of the session, real-time reminding the user of the current business session operation, rather than throwing away the failed business session. This avoids problems such as interaction between business sessions and problems for users. DRAWINGS

Figure 1 is a schematic diagram showing the connection relationship between the USSD system and the GSM system;

2 is a schematic diagram of an embodiment of a composition structure of a network entity of the present invention;

3 is a flow diagram of an embodiment of a method of protecting data in an unstructured supplementary data service of the present invention. detailed description

The technical solutions of the present invention are further described below in conjunction with the drawings and specific embodiments. FIG. 1 is a schematic diagram showing the connection relationship between the USSD system and the GSM system, as shown in FIG. 1 , wherein an Unstructured Supplementary Data Service Center (USSDC) 70 is used to pass the No. 7 signaling network 60. It is connected to MSC/VLR40 and HLR50 to complete various services required by USSD.

The Internet Short Message Gateway (ISMG) 80 is mainly used to solve the problem of short message intercommunication and access between the Internet and operators, and a dynamic data exchange platform system for sending and receiving short messages.

The USSD Application Server 90 is used to provide various USSD application services. The USSDC90 is the basis of the entire USSD system platform. In the minimum configuration, the various services required by the USSD can be separately completed, and all functional requirements, including accounting, management, and other auxiliary functions, can be completed. The USSDC90 implements the routing function of the USSD message and the service processing of the GSM network interface. The USSDC90 provides the timer function for each service session. In order to supervise the USSD service session and prevent the business session conversation from proceeding properly, the corresponding timer is started for each operation.

The mobile station 10 is a device directly used by the user in the system, such as a mobile phone. The Base Station System (BSS) communicates directly with the mobile station 10 through the wireless interface, and is also connected to the MSC/VLR 40 on the network side, which is the mobile station 10 and the Network and Switching Subsystem (NSS). Provide a transmission path.

The BSS consists of two basic parts: a base transceiver station (BTS, Base Transceiver Station) 30 connected to the mobile station 10 via a wireless interface, and a base station controller (BSC, Base Station Controller) connected to the MSC/VLR 40 side. .

NSS is a network and switching subsystem, including a switching center that implements the main switching functions of GSM and a database needed to manage user data and mobility. The main role is to manage GSM users and Communication between other network users. The NSS includes several functional units: a) MSC/VLR 40: In the present invention, the MSC and the VLR are integrated into the same network entity to form the MSC/VLR 40 to simultaneously implement the functions of the MSC and the VLR. The MSC is the core of the network, and realizes the communication connection between the mobile user and other network users; the VLR stores all relevant information of all users entering the coverage area, and provides necessary conditions for the registered mobile user to establish a call connection; It is a dynamic database, and it needs to exchange a large amount of data with the relevant HLR at any time to ensure the validity of the data. When the user leaves his coverage area, the user's information will be deleted; c) HLR50: HLR is the system's central database, which stores all information related to the user, including the user's roaming authority, basic service, supplementary service and location information. .

The network entity of the present invention includes network entities involved in the USSD service, such as MSC, VLR, and HLR.

2 is a schematic diagram of an embodiment of a component structure of a network entity according to the present invention. As shown in FIG. 2, the network entity 100 includes a sending module 101, a cache module 102, and a monitoring module 103. The sending module 101 is configured to send service data based on the service session. The service data in this embodiment is provided with a service identification (ID). The service data can be either USSD request or USSD data. The service data includes, but is not limited to, information items such as the USSD number, the USSD service name, and the USSD service description. The USSD business name is the name of the USSD service provided by the operator, such as stocks and time markets, telephone banking, market research, etc. The service description item includes network side timer information, and the network side timer information includes a response timeout period and a longest service session time.

The cache module 102 is configured to cache the service data sent by the sending module 101. In this embodiment, the cache module 102 caches the service data sent by the sending module 101 according to the service ID. A temporary buffer is provided in the network entity 100 and is managed by the cache module 102. The size of the buffer can be allocated according to the current resources of the network entity 100.

The monitoring module 103 is configured to monitor whether an abnormality occurs in the network, and monitor whether the network returns to normal within a predetermined period of time when an abnormality occurs in the network. In this embodiment, the monitoring module 103 is provided with After the sending module 101 sends the service data, the monitoring module 103 starts the timer to start counting. If the success notification is received before the timer expires, the network does not generate an abnormality; if the timer expires, the error notification is received. This indicates that the network is abnormal. The monitoring module 103 turns off the timer when no abnormality occurs in the network, that is, after receiving the success notification. When an abnormality occurs in the network, that is, after receiving the error notification, the monitoring module 103 restarts the timer to monitor whether the network returns to normal within a predetermined period of time. When the monitoring module 103 receives the success notification within the predetermined time period, it indicates that the network returns to normal; if the success notification is not received, the network does not return to normal.

The sending module 101 is further configured to resend the cached service data based on the current service session when the network returns to normal within a predetermined time period. In this embodiment, after the network returns to normal, the sending module 101 calls the service data from the cache module 102 according to the service ID, and then transmits.

Further, the cache module 102 is further configured to save the state of the current service session when an abnormality occurs in the network. At this time, the network entity 100 further includes a session module 104, configured to release the current service session when the network does not return to normal within a predetermined period of time, and generate an error report, where the error report includes the status of the current service session. The session module 104 is further configured to determine whether the number of error reports exceeds a preset number, and when the preset number is exceeded, delete the first error report generated. The session module 104 is further configured to release the current service session when no abnormality occurs in the network.

In this embodiment, the working principle between the modules in the network entity is as follows: After the sending module 101 sends the service data, the cache module 102 temporarily stores the service data in the temporary buffer according to the service ID, and the monitoring module 103 according to the service After the data is sent, the next-level network entity returns a success notification or an error notification to determine whether the network is back to normal. When the next-level network entity returns a success notification, the session module 104 releases the service session; when the next-level network entity returns an error. At the time of notification, the session module 104 temporarily stores the state of the current business session into the buffer of the cache module 102. When the network returns to normal, the sending module 101 resends the cached service data; when the correct result of the service data transmission cannot be received, the session module 104 releases the service session, and generates an error report to be temporarily stored in the storage buffer. Automatically delete time records after the report exceeds a certain number The earliest report item.

3 is a schematic flowchart of an embodiment of a method for protecting data in an unstructured supplementary data service according to the present invention. It is assumed that the method for protecting data in the unstructured supplementary data service in this embodiment is based on a GSM system and can be applied to a network. The entity initiates the service request, and can also be applied to the service request initiated by the mobile phone, and the network entity that is the sender has established a service session with the network entity that is the receiver. As shown in FIG. 3, the method includes the following steps:

Step 300: The network entity sends and caches the service data based on the service session.

In this embodiment, the network entity may be an HLR, a VLR, or an MSC, and is provided with a sending module, where the network entity sends the service data through the sending module; the service data may be a USSD request or a USSD data. The service data includes, but is not limited to, information items such as the USSD number, the USSD service name, and the USSD service description. The USSD business name is the name of the USSD service provided by the operator, such as stock quotes, telephone banking, market research, etc. The service description entry contains network-side timer information, including the response timeout period and the longest service session time. The network entity maintains a wireless connection during the business session, providing end-to-end transparent transmission without storage and forwarding. A cache module is set in the network entity, and the cache module has a temporary buffer and is managed by the cache module. The size of the buffer can be allocated according to the current resource of the network entity. The network entity sends the service data according to the service ID cache through the cache module.

Step 301: The network entity monitors whether the network is abnormal. When an abnormality occurs in the network, the process proceeds to step 303; when no abnormality occurs, the process proceeds to step 302.

In this embodiment, the network entity is provided with a monitoring module, and the monitoring module is provided with a timer. After the sending module sends the service data, the monitoring module starts the timer to start counting. If the success notification is received before the timer expires, the network is indicated. No exception occurred; if an error notification is received before the timer expires, the network has an exception. When the network does not have an abnormality, that is, after receiving the success notification, the monitoring module turns off the timer. When an abnormality occurs in the network, that is, after receiving the error notification, the monitoring module restarts the timer to monitor whether the network is restored within a predetermined period of time. It is normal. When the monitoring module receives the success notification within the predetermined time period, it indicates that the network is back to normal; if the success notification is not received, the network is not restored.

Step 302: The network entity releases the current service session.

In this embodiment, the network entity is configured with a session module, and when the network does not have an abnormality, the current session can be released through the session module.

Step 303: The network entity saves the state of the current service session.

In this embodiment, the network entity saves the state of the current service session through the session module. Step 304: The network entity monitors whether the network returns to normal within a predetermined period of time. When the network returns to normal within the predetermined time period, the process proceeds to step 305; when the network does not return to normal within the predetermined time period, the process proceeds to step 306. In this embodiment, after the monitoring module receives the success notification within the predetermined time period, the network returns to normal; if the success notification is not received, the network does not return to normal.

Step 305: The network entity resends the cached service data based on the current service session.

In this embodiment, after the network returns to normal, the sending module of the network entity calls the service data from the cache module according to the service ID, and then sends the data.

Step 306: The network entity releases the current business session and generates an error report.

In this step, the network entity releases the current service session through the session module, and generates an error report, where the error report includes the status of the current service session. The network entity can also use the session module to determine whether the number of error reports exceeds a preset number, and when the preset number is exceeded, delete the first error report generated.

The network entity provided by the present invention and the method for protecting data in the unstructured supplementary data service, when the network is abnormal, the network entity does not lose the current service data, but saves the service data according to the network state and monitors the network status in real time. When the network recovers, the network entity will continue to send the saved service data to the next-level network entity; when the network cannot recover in a short time, the network entity saves the current service session state to the buffer. The state of the saved business session allows the user to determine when the network entity is abnormal when the network is initiating multiple services. The former network state, when the network is restored, the service session state is fed back to the upper-level network entity, and the mobile station promptly reminds the user of the current service session operation according to the state of each service session, instead of throwing the failed service session. Thereby avoiding the mutual influence of business sessions and causing problems for users.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the patents. The equivalent structure or equivalent process transformations made by the description of the present invention and the drawings are directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of the present invention.

Claims

Claim

A method for protecting data in an unstructured supplementary data service, comprising: the network entity sending and buffering service data based on a service session, and monitoring whether the network is abnormal;

The method according to claim 1, wherein the method further comprises: before the network is abnormal, monitoring whether the network returns to normal within a predetermined time period, the method further comprising: the network entity saving the state of the current service session.

3. The method according to claim 2, wherein the method further comprises: when the network does not return to normal within a predetermined time period, the network entity releases the current service session, and generates an error report, the error report Includes the status of this business session.

The method according to claim 3, wherein the method further comprises: determining, by the network entity, whether the number of error reports exceeds a preset number, and if the preset number is exceeded, deleting the first generated error report.

The method according to any one of claims 1 to 4, wherein the method further comprises: when it is detected that no abnormality occurs in the network, the network entity releases the current service session.

6. A network entity, comprising:

a cache module, configured to cache service data sent by the sending module;

The monitoring module is configured to monitor whether the network is abnormal, and monitor whether the network returns to normal within a predetermined period of time when an abnormality occurs in the network.

The network entity according to claim 6, wherein the cache module is further Used to save the status of this business session when an abnormality occurs on the network.

The network entity according to claim 7, wherein the network entity further includes a session module, configured to release the current service session and generate an error report when the network does not return to normal within a predetermined time period;

The error report includes the status of the current business session.

The network entity according to claim 8, wherein the session module is further configured to: determine whether the number of error reports exceeds a preset number, and when the preset number is exceeded, delete the first error report generated.

The network entity according to any one of claims 6 to 9, wherein the session module is further configured to release the current service session when no abnormality occurs in the network.