WO2012162965A1

WO2012162965A1 - Method, system and network element for pushing application information

Info

Publication number: WO2012162965A1
Application number: PCT/CN2011/079017
Authority: WO
Inventors: 赵建国; 倪慧
Original assignee: 华为技术有限公司
Priority date: 2011-08-26
Filing date: 2011-08-26
Publication date: 2012-12-06
Also published as: CN102388632A; CN102388632B

Abstract

A method, a system and a network element for pushing application information are provided by the present invention. The method comprises: a network element for pushing information receives application information with a user application identifier from an application server (101), and the user application identifier is used to identify the user corresponding to the application in the mobile terminal; the network element for pushing information, according to the mapping relation between the user application identifier and a user network identifier of the mobile terminal, confirms the user network identifier of the mobile terminal corresponding to the application information (102); the network element for pushing information transmits the application information to the mobile terminal according to the user network identifier (103). The present invention realizes the application information pushing in the wireless network and does not need to provide the user network identifier of the mobile terminal to a service provider, and ensures the network security.

Description

Application information push method, system and network element

The present invention relates to the field of wireless communications, and in particular, to an application information pushing method, system, and network element. Background technique

In the mobile internet, many applications need to push information from the service application server on the network side to the mobile terminal (for example, a mobile phone), and some applications need to transmit messages from the mobile terminal to the mobile terminal. This requires the mobile phone to receive information sent from the network side in real time. At present, there are three main ways to achieve the above objectives: polling, Wireless Application Protocol (WLAN) Push, Internet Protocol (IP) Push.

The so-called polling means that the application installed on the mobile phone periodically (for example, every 15 minutes) moves to the corresponding server through the mobile packet network (such as GPRS network) to retrieve whether there is new information.

The so-called WAP Push refers to the service application server as a Push Initiator (PI), which sends a WAP short message to a phone number through a push proxy gateway (PUSH Proxy Gateway, PPG) to a mobile phone (or an individual) using the number. Computer), the short message contains the server's link and content summary. After the phone is received, you can display a summary of the content, or you can automatically open the link to the server to download the complete information (such as downloading MMS content).

The so-called IP Push refers to the IP packet heartbeat between the mobile terminal and the server, and the connection of the mobile packet network (such as the GPRS network) is always maintained. When no data packet is transmitted through the network, the mobile GPRS network will reclaim the mobile terminal. The IP address and the corresponding network resources cause the connection to be interrupted. When the server has new information, it can immediately transmit new information to the mobile phone through the IP packet through the maintained IP connection.

Both the polling and the IP Push method transmit the user plane of the operator packet network as a transparent pipe class, regardless of the operator's network control. When there are many applications installed on the mobile phone, if these applications use polling or IP Push, the standby time of the mobile phone will be greatly shortened and the transmission resources of the wireless packet network will be greatly consumed due to the polling or heartbeat of each application.

The WAP Push solution uses the operator's signaling message to deliver the push message, and the Service Provider (SP) needs to know the user's phone number, and requires the SP server to directly face the network infrastructure of various operators. Communication, the SP must know the user network identity of the mobile terminal, this It is basically impossible in the mobile Internet. Summary of the invention

The embodiment of the invention provides an application information pushing method, system and network element, which implements pushing information of application information in a wireless network, and the application provider does not need to know the user network identifier of the mobile terminal, thereby ensuring network security. .

To this end, an embodiment of the present invention provides an application information pushing method, including:

The information push network element receives application information from the application server that carries the user application identifier, and the user application identifier is used to identify the user corresponding to the application on the mobile terminal;

Determining, by the information-pushing network element, a user network identifier of the mobile terminal corresponding to the application information, according to a mapping relationship between the user application identifier and a user network identifier of the mobile terminal; The user network identifier sends the application information to the mobile terminal.

The embodiment of the invention further provides an information push network element, including:

An information receiving unit, configured to receive, by the application server, application information that carries a user application identifier, where the user application identifier is used to identify a user corresponding to the application on the mobile terminal;

a mapping unit, configured to determine, according to a mapping relationship between the user application identifier and a user network identifier of the mobile terminal, a user network identifier of the mobile terminal corresponding to the application information;

And an information sending unit, configured to send the application information to the mobile terminal according to the user network identifier.

An embodiment of the present invention further provides an identifier allocation network element, including:

An identifier allocation unit, configured to allocate a user application identifier to the mobile terminal, where the user application identifier is used to identify a user corresponding to the application on the mobile terminal;

And an identifier sending unit, configured to send the user application identifier to the application server.

The embodiment of the present invention further provides a wireless network application information pushing system, where the system includes: an identifier allocation network element, configured to allocate a user application identifier to the mobile terminal, and send the user application identifier to provide the application service. The application server, where the user application identifier is used to identify a user corresponding to the application on the mobile terminal;

An information push network element, configured to receive application information that carries a user application identifier from an application server, and according to a mapping relationship between the user application identifier and a user network identifier of the mobile terminal, Determining a user network identifier of the mobile terminal corresponding to the application information, and sending the application information to the mobile terminal according to the user network identifier.

In the embodiment of the present invention, the user application identifier is used to identify the user who uses the application, and the user is associated with the determined mobile terminal, that is, between the user application identifier and the user network identifier of the mobile terminal is saved on the operator side. The mapping relationship, so that only the user application identifier needs to be notified to the service server, and the service information of the service server can be correctly sent to the specific mobile terminal. In this way, the user network identifier of the mobile terminal does not need to be leaked to the service server, and the service information only needs to be correctly transmitted to the destination mobile terminal through the transit of the carrier network. The real-time, two-way information interaction between the application server and the mobile terminal is realized, and the security of the network is ensured. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are incorporated in the drawings Other drawings can also be obtained from these drawings on the premise of creative labor.

1 is a schematic diagram of a specific process of an application information pushing method in an embodiment of the present invention; FIG. 2 is a schematic diagram of a specific composition of a wireless network application information pushing system in an embodiment of the present invention;

3 is a schematic diagram of a specific composition of an identifier distribution network element in an embodiment of the present invention;

4 is a schematic diagram of a specific composition of an information push network element in an embodiment of the present invention;

FIG. 5 is a schematic diagram of a specific composition of a mobile terminal in an embodiment of the present invention; FIG.

6 is a schematic diagram of a signaling flow of Embodiment 5 in an embodiment of the present invention;

7 is a schematic diagram of a signaling flow of Embodiment 6 in an embodiment of the present invention;

8 is a schematic diagram of a signaling flow of Embodiment 7 in an embodiment of the present invention;

FIG. 9 is a schematic diagram of signaling flow of Embodiment 8 in the embodiment of the present invention; FIG.

FIG. 10 is a schematic diagram of signaling flow of Embodiment 9 in the embodiment of the present invention; FIG.

11 is a schematic diagram of a signaling flow of Embodiment 13 in an embodiment of the present invention;

FIG. 12 is a schematic diagram of a signaling flow of Embodiment 15 in an embodiment of the present invention. detailed description If the application server of the mobile Internet knows the real user network identifier of the mobile terminal using a certain service, such as International Mobile Subscriber Identity (IMSI)

The MSISDN number, etc., the application server can directly send the information to the mobile network, and the mobile network directly addresses the destination mobile terminal according to the user's user network identifier, so that the information can be sent to the user's mobile terminal in real time.

However, due to security issues, users and mobile network providers cannot disclose the user's subscriber network identity to thousands of business application providers on the mobile internet. This makes the current information push technology on the mobile Internet usually only possible through the active access of the mobile terminal to the application server. It is very difficult or costly for the mobile Internet application server to actively push information to the terminal.

In order to solve the above problem, the embodiment of the present invention introduces a method for identifying a user who uses an application by using a user application identifier, thereby indirectly identifying a mobile terminal running the application, and supporting real-time and two-way information between the application server and the mobile user. Interaction.

As shown in FIG. 1, it is a specific embodiment of an application information pushing method in an embodiment of the present invention. The method includes the following steps.

The information push network element receives the application information from the application server that carries the user application identifier, where the user application identifier is used to identify the user corresponding to the application on the mobile terminal.

For example, in an IP Multimedia Subsystem (IMS) service interaction, when the IMS user is called, the information push network element obtains an IMS paging request, and the IMS paging request includes the user application. Logo.

The application server can also push information to the information push network element in various ways, such as SMS-based message push, WAP Push-based file push, packet push based packet network push, based on existing IP connection reports. Text push and so on.

102. The information push network element determines, according to a mapping relationship between the user application identifier and a user network identifier of the mobile terminal, a user network identifier of the mobile terminal corresponding to the application information.

The mapping relationship between the user application identifier and the user network identifier of the mobile terminal may be stored in the information push network element, or may be stored in other network elements in the network, such as the identifier distribution network element to be described below.

The user network identifier in the mapping relationship generally refers to IMSI, IMEI, IMS Private User Identifier (IMTI), MSISDN, IMS Public User Identity (IMS PUbilic). User identifier, IMPU ), NAI, IP address, MAC address.

103. The information push network element sends the application information to the mobile terminal according to the user network identifier.

The user application identifier sent by the information push network element to the application server may include addressing information of the information push network element, such as an IP address, a domain name, and the like, so that the application server obtains the information according to the addressing information and pushes the network element address. That is, the user application identifier further includes information push network element information, so that the application server obtains the address of the information push network element according to the information push network element information, and pushes the address of the network element according to the information. The application information is sent to the information push network element.

Of course, the application server may also obtain the address information of the network element from the user side or through the configuration information. In this case, the user application identifier may not carry the information of the information feed network element.

Before step 101, the method further includes the step of: assigning a network element to allocate a user application identifier to the mobile terminal, and sending the user application identifier to the application server.

When the user application identifier is allocated to the mobile terminal, the allocation granularity may be APN granularity, PDN granularity, service granularity, and the like. Correspondingly, the identifier allocation network element in the embodiment of the present invention may allocate, to the mobile terminal, a user application identifier corresponding to the mobile terminal, or a user application identifier corresponding to an application on the mobile terminal, or corresponding to the User application identification for multiple applications on the mobile terminal. The plurality of applications may refer to multiple applications of the same type on the mobile terminal.

For example, if a plurality of different applications are run on the mobile terminal, the user corresponding to all applications on the mobile terminal may be assigned a user application identifier, and the user application identifier identifies the mobile terminal; or, the mobile terminal is running. Multiple mailbox applications (Netease mailbox, Sohu mailbox, etc.) can allocate the same user application identifier for this type of application on the mobile terminal, or run multiple applications provided by one service provider simultaneously on the mobile terminal. If a service provider provides a mailbox application, an instant messaging application, etc., the same user application identifier can also be assigned to this type of application.

The user application identifier may be a temporary user application identifier. After the temporary user application identifier is invalid, the identifier allocation network element re-allocates the temporary user application identifier to the mobile terminal, and of course, the newly assigned temporary user application identifier is also It is not necessarily assigned after the old temporary user application ID has expired, and the two can coexist. Of course, the user application identifier can also be a long-term identifier.

For example, the temporary user application identifier may be an Open Temporary Mobile Subscriber Identity (O-TMSI) or an Open Temporary Mobile Subscriber Number (O-TMSN). The above two specific temporary user application identifiers can be defined as follows: The domain, IMPI for the IMS domain) is transmitted over the mobile Internet and consists of a combination of characters and numbers. It can be completely independent of the IMSI/IMPI digit string and the information it contains, or even a string of random strings. 0-TMSI is a temporary identifier that distinguishes mobile users. When the mobile network device needs to send the mobile user's message to the mobile Internet, the IMSI/IMPI in the message may be replaced with 0-TMSI, and then sent to the application server of each SP of the mobile internet; when the mobile network device receives the message from When the mobile Internet carries the 0-TMSI message, it identifies the mobile subscriber that is uniquely identified by the IMSI, and performs corresponding service processing or replaces the 0-TMSI with the IMSI/IMPI for subsequent processing. The packet domain, IMPU for the IMS domain) is transmitted over the mobile Internet and consists of a combination of characters and numbers. It can be completely independent of the MSISDN/IMPU digit string and the information it contains, or even a string of random strings. 0-TMSN is a temporary sign that distinguishes mobile users. When the mobile network device needs to send the mobile user's message to the mobile Internet, the MSISDN/IMPU in the message may be replaced with 0-TMSN, and then sent to the application server of each SP of the mobile Internet; when the mobile network device receives the message from When the mobile Internet carries the message of the 0-TMSN, it identifies the mobile subscriber that is uniquely identified by the corresponding MSISDN/IMPU, and performs corresponding service processing or replaces the 0-TMSN with the MSISDN/IMPU for subsequent processing.

When IMSI and MSISDN have a corresponding relationship, 0-TMSI/0-TMSN can be unified into one. When the mobile subscriber is uniquely identified by the IMSI, one IMSI may correspond to one or more 0-TMSIs; when the mobile subscriber is uniquely identified by the MSISDN, one MSISDN may correspond to one to more 0-TMSNs; when the mobile subscriber consists of a set of IMSIs and When a group of MSISDNs are uniquely identified, both the IMSI and the MSISDN can simultaneously correspond to one or more 0-TMSI/ and/or 0-TMSN.

Mobile users' 0-TMSI and 0-TMSN can be generated and used separately, or they can be generated simultaneously or simultaneously. The 0-TMSI and 0-TMSN are generated by the MSC/VLR, GGSN/VLR of the mobile network or by setting up separate network functional entities. And allow for constant replacement.

Of course, the 0-TMSI/0-TMSN described above may have an expiration date. In other embodiments, 0-TMSI/0-TMSN may also be defined to survive until the new 0-TMSI/0-TMSN is replaced. The replacement cycle can be set by the mobile operator. In general, the faster the frequency of replacement, the better the confidentiality. In step 100, when the identifier distribution network element sends the user application identifier to the application server that provides the application service, the user identifier may be sent to the application server by the identifier distribution network element or after receiving the request, or may be moved. The device such as the terminal indirectly provides the user application identifier to the application server. That is, the identifier distribution network element directly sends the user application identifier to an application server that provides the application service, or the identifier distribution network element sends the user application identifier to the mobile terminal, and then The mobile terminal sends the user application identifier to an application service crying port that provides the application service.

In step 100, the timing of assigning the user application identifier may be that, when the mobile terminal enters a new location area in the mobile network, the identifier allocation network element of the location area allocates a user application identifier to the mobile terminal. And notifying the mobile terminal.

That is, whenever the mobile terminal is powered on to the mobile network, requesting location update, session attempt, service activation, or other mobile network signaling interaction process to the mobile network, if the mobile network allows the user to use the mobile network, it may be moved by The identity assignment network element in the network generates a new 0-TMSI/0-TMSN for the mobile terminal and distributes it to the mobile terminal and each service application server.

Alternatively, each application server of the mobile terminal and the mobile internet can also apply to the mobile network at any time through the mobile network signaling or the mobile packet bearer to obtain a new 0-TMSI/0-TMSN.

The new 0-TMSI/0-TMSN can be used to replace the old 0-TMSI/0-TMSN, or it can be used with the old 0-TMSI/0-TMSN until the expiration date is over or replaced.

Since the 0-TMSI/0-TMSN can be redistributed by the mobile network, the mobile terminal, and each service application server after being generated, the 0-TMSI/0-TMSN can be used by an application server of the mobile Internet alone or by mobile. Multiple application servers of the Internet are used together.

In the above method, an identifier maintenance network element may be separately stored for storing the user application identifier, and a mapping relationship between the user application identifier and the user network identifier of the mobile terminal.

Based on the solution described in the foregoing embodiment, after the mobile terminal receives the application information, if the application information received by the mobile terminal carries the user application identifier, the mobile terminal receives the application according to the user application identifier. The information is processed by the corresponding application.

For example, the mobile terminal searches for a corresponding application according to the user application identifier, and sends the information to the application for processing. The processing varies according to the application, such as content display, or information reminding, or automatically linking to a website.

If the callback program is installed on the mobile terminal, the backhaul may be saved in the mobile terminal The mapping between the sequence entry and the user application identifier; the embodiment shown in FIG. 1 may further include the step 104, the mobile terminal according to the received user application identifier in the application information, the callback program The mapping relationship between the portal and the user application identifier is awakened by the callback program to the application in the mobile terminal. The mobile terminal sends a service access request to the application server according to the application program to communicate with the service server. Establish a business connection.

The network elements described in the foregoing methods may be deployed on a single server or on the same server, and may be implemented by different servers in different networks. For example, in the 3GPP network, the identifier allocation network element is any one of a Policy and Charging Rule Function (PCRF), an MSC, and an AAA/HSS, and the identifier maintenance network element is a PCRF, an MSC. AAA/HSS, one of a Home Location Register (HLR), the information push network element is an SMS-GW, an SMSC, a Gateway General Packet Radio Service Support Node (GGSN), a service Any one of the push gateway and the service paging gateway; in the Worldwide Interoperability for Microwave Access (WiMAX) network, the identifier allocation network element is Authorization, Authentication and Accounting (AAA) Any one of the server and the PCRF, the identifier maintenance network element is any one of an AAA server and a PCRF, and the information push network element is a WiMAX voice service (WVS) server, a home agent (Home Agent, Any of HA).

Correspondingly, the embodiment of the present invention further describes a wireless network application information pushing system, and each network element in the system. As shown in Figure 2, it is a schematic diagram of the composition of the system, which includes the following network elements.

The identifier distribution network element 1 is configured to allocate a user application identifier to the mobile terminal, and send the user application identifier to the application server that provides the application service, where the user application identifier is used to identify an application corresponding to the mobile terminal. User. That is, as shown in FIG. 3, the identifier allocation network element 1 includes: an identifier allocation unit 10, configured to allocate a user application identifier to the mobile terminal, where the user application identifier is used to identify a user corresponding to the application on the mobile terminal; The sending unit 12 is configured to send the user application identifier to the application server.

The identifier allocation unit 10 is further configured to allocate, to the mobile terminal, a user application identifier corresponding to the mobile terminal, or a user application identifier corresponding to an application on the mobile terminal, or corresponding to the User application identification for multiple applications on the mobile terminal. When the mobile terminal enters a new location area in the mobile network, the identity allocation unit 10 in the identity allocation network element 1 of the new location area is further configured to allocate a user application identifier to the mobile terminal, and Notifying the mobile terminal.

The identifier sending unit 12 is further configured to send the user application identifier directly to an application server that provides the application service, or send the user application identifier to the mobile terminal, and push the network element by the mobile terminal information. And determining, by the application server, the application information that carries the user application identifier, and determining, according to the mapping relationship between the user application identifier and the user network identifier of the mobile terminal, the mobile terminal corresponding to the application information. User network identifier, and the application information is sent to the mobile terminal according to the user network identifier. The information push network element is used in the IMS service interaction of the IP multimedia subsystem. When the IMS user is called, the information receiving unit is further configured to obtain an IMS paging request, where the IMS paging request includes the user. Application ID.

That is, as shown in FIG. 4, the information push network element 3 may include: an information receiving unit 30, configured to receive application information from the application server that carries the user application identifier, where the user application identifier is used to identify the application on the mobile terminal. a corresponding user; a mapping unit 32, configured to determine, according to a mapping relationship between the user application identifier and a user network identifier of the mobile terminal, a user network identifier of the mobile terminal corresponding to the application information; The sending unit 34 is configured to send the application information to the mobile terminal according to the user network identifier. Or the information push network element 3 further includes a mapping relationship storage unit 36, configured to store a mapping relationship between the user application identifier and a user network identifier of the mobile terminal. The application information of the user application identifier is sent to the mobile terminal, so that the mobile terminal processes the application information according to the user application identifier.

As shown in FIG. 2, the system may further include a mobile terminal 5, configured to receive the application information including the user application identifier, and process the application information according to the user application identifier.

As shown in FIG. 5, the mobile terminal 5 may include: a storage module 50, configured to store a mapping relationship between a callback program entry and the user application identifier; and a callback module 52, configured to: according to the received user in the application information The application identifier, the mapping relationship between the callback program entry and the user application identifier is used to wake up an application in the mobile terminal by using a callback program, and the service module 54 is configured to: after the callback module wakes up the application, according to the application The program sends a service access request to the application server to establish a service connection with the service server. The user application identifier may be a temporary user application identifier. After the temporary user application identifier is invalid, the identifier distribution network element 1 is further configured to re-allocate the temporary user application identifier to the mobile terminal, and re-allocate The temporary user application identifier is sent to the application server.

The user network identifier may be any one of IMSI, IMEL IMPL MSISDN, IMPU, NAI, IP address, and MAC address.

An identifier maintenance network element 2 may be stored in the system for storing a mapping relationship between the user application identifier and the user network identifier of the mobile terminal. When the wireless network is a 3GPP network, the identifier distribution network element 1 may be any one of a PCRF, an MSC, and an AAA/HSS, and the identifier maintenance network element 2 may be any one of a PCRF, an MSC, an AAA/HSS, and an HLR. The network element 3 can be any one of an SMS-GW, an SMSC, a GGSN, a service push gateway, and a service paging gateway.

When the wireless network is a WiMAX network, the identifier distribution network element 1 can be any one of AAA and PCRF, and the identifier maintenance network element 2 can be any one of AAA and PCRF, and the information push network element 3 can be a WVS server or a HA. Any one.

Of course, the wireless network in the embodiment of the present invention may also be in the network field of WCDMA, LTE, TDSCDMA, CDMA, WiMAX, 3GPP2, and the like. In different networks, the format of their user identification may vary.

According to the description of the foregoing embodiment, in the embodiment of the present invention, the user application identifier is used to indirectly identify the mobile terminal that uses the application, and the operator side saves the user application identifier and the user network identifier. The relationship is mapped, and only the user application identifier is notified to the service server. In this way, on the one hand, the service server can transmit the service information according to the user application identifier, and on the other hand, the user network identifier of the mobile terminal is not leaked to the service server, and the service information can be correctly sent through the analysis of the operator network. Go to the destination mobile terminal. Real-time, two-way information interaction between the application server and the mobile terminal can be supported.

Meanwhile, in the embodiment of the present invention, when the mobile terminal does not access the mobile packet network, the server of the Internet may invite the application on the mobile terminal to perform the session as long as the callback program is installed in the mobile terminal.

In order to further describe the technical details of the embodiments of the present invention, the technical solutions of the embodiments of the present invention are further explained in the following. In order to not make the content of each embodiment too verbose, the specific scheme of the user application identifier distribution and distribution process is described in Embodiment 1-4; Embodiment 5-9 describes the specific information push after the user application identifier is distributed to the network. Program; Embodiments 10-12 further supplement the different granularity allocation manners of the APP IDs; Embodiments 13-14 further describe the process of the Internet server initiating service paging and the application response paging on the mobile terminal; Embodiment 15 describes the IMS paging service procedure.

Before describing the embodiments 1 to 15, the user application identifiers in the embodiments are further described. The user application identifiers in these embodiments may be the foregoing 0-TMSI, 0-IMSN, or APP UID. . In the following embodiments, the schemes in the embodiments of the present invention are described by taking 0-TMSI, 0-IMSN or APP UID as an example. For further explanation of the 0-TMSI/O-TMSN, reference may be made to the foregoing embodiments, and details are not described herein.

Embodiments 1 and 2 describe two specific cases in a 3GPP network, and Embodiments 3 and 4 describe two specific cases in a WiMAX network.

Example 1

In this embodiment, the mobile terminal obtains 0-TMSI/O-TMSN through signaling interaction during the location update process; the mobile terminal provides the 0-TMSI and 0-IMSN to the application server through the application program interface.

That is, the mobile terminal initiates a location update request to the MSC/VLR in the mobile network (in this example, the MSC/VLR has the function of identifying the assigned network element) when entering the new location area of the mobile network. After the MSC/VLR confirms the identity of the user, the MSC/VLR generates corresponding 0-TMSI and 0-TMSN for the user, and transmits it to the mobile terminal in the location update response message, which is used when the mobile terminal accesses the mobile internet. At the same time, the location update message carries a replacement indication for indicating whether to replace the existing 0-TMSI and 0-TMSN of the mobile terminal.

In the HLR (in this example, the HLR has the function of identifying the maintenance network element), the mapping relationship between 0-TMSI/O-TMSN and IMSI/MSISDN is stored. 0-TMSI and 0-TMSN can also be transmitted to the HLR by the MSC/VLR during the signaling interaction process. The HLR establishes a corresponding index table to facilitate other network elements to query the real user identity according to 0-TMSI or 0-TMSN. Logo. The mobile terminal notifies the application server of the 0-TMSI/OTMSN through the application layer message for subsequent communication. Example 2:

In this embodiment, the user application identifier is specifically 0-TMSI or 0-IMSN. In this embodiment, after obtaining the IP address, the mobile terminal obtains 0-TMSI/O-TMSN through signaling interaction of the mobile packet bearer; the mobile terminal provides the 0-TMSI, 0-IMSN through the application program interface. Give the application server.

Service paging gateway (in this example, the service paging gateway has the function of identifying the assigned network element and storing

0-TMSI/O-TMSN mapping relationship with IMSI/MSISDN) Responsible for generating the corresponding 0-TMSI/O-TMSN for IMSI/MSISDN. When the service application installed on the mobile terminal needs to obtain 0-TMSI/O-TMSN, the application is opened to the service paging gateway of the mobile network through the user plane channel established by the mobile packet network. The service paging gateway queries the GGSN of the user's IMSI through network signaling according to the IP address of the mobile terminal in the received IP packet, and generates corresponding 0-TMSI and 0-TMSN for the IMSI, and responds The message is passed to the mobile terminal. The mobile terminal notifies the service server of the 0-TMSI/O-TMSN and the information push network element address through the application layer for subsequent communication. Example 3:

The Internet in this embodiment is a WiMAX network, and the user application identifier is specifically an APP UID corresponding to the NAI. In this embodiment, after the application server obtains the NAI, the application network element is directly allocated to the identifier to obtain the APP UID.

The PCRF in the WiMAX network (in this example, the PCRF has the function of identifying the assigned network element and storing the mapping relationship between 0-TMSI/O-TMSN and IMSI/MSISDN) is responsible for generating the corresponding APP UID for the user NAI. The application server obtains the user NAI identifier from the mobile terminal through an application layer protocol, such as HTTP or SIP.

The application server sends an APP UID request message to the PCRF of the WiMAX network, where the message carries the NAI identifier of the user. After receiving the request message, the PCRF allocates a corresponding APP UID for the application of the user, or acquires an APP UID assigned by the application with another application of the same type. The PCRF saves the mapping relationship between the APP UID and the NAI, and sends the APP UID to the application server through a response message. Example 4:

In this embodiment, the user application identifier is specifically an APP UID corresponding to the IP address, and the application of the same APN shares the same APP UID.

The user installs the mobile application locally on the mobile terminal. When the user runs the mobile application and thereby interacts with the application server of the mobile internet, the application server may request the mobile terminal to provide the APP UID for subsequent business processing, such as short message sending. which is. When the mobile terminal interacts with the application server, obtains an identification request from the application server (the request is used to obtain the APP UID), and the mobile terminal retrieves the APP UID or assigns/maintains the server to the identifier in this example (in this example, the identifier is allocated/maintained) The server has the function of identifying the assigned network element, and stores the mapping relationship between the 0-TMSI/0-TMSN and the IMSI/MSISDN. The request is to allocate the APP UID, and after the mobile terminal knows the APP UID, the mobile terminal notifies the service server. ,

After obtaining the user application identifier by using the foregoing embodiments, the application server further uses the user application identifier to push the information to the user. The following embodiments describe a specific information push scheme.

Example 5

In this embodiment, the application server of the mobile Internet sends a short message to the user identified by the 0-TMSI or the 0-TMSN.

The application server saves the 0-TMSI (or 0-TMSN) of the mobile user. For the identification assignment in this example, refer to Embodiment 1. As shown in Figure 6, the process includes the following steps.

601. When the application server has a message to send, the application server sends the message to the mobile operator's SMSC-GW or SMSC (in this example, the function for implementing the information push network element), and sends the indication to the 0-TMSI (or 0-TMSN ) The identified user.

602. The SMSC-GW or the SMSC queries the HLR according to the 0-TMSI or the 0-TMSN to obtain the real IMSI, MSISDN of the user.

603. The SMSC-GW or SMSC sends a short message to the MSC/VLR according to the IMSI. 604. The MSC/VLR sends the short message to the mobile terminal. Example 6:

In this embodiment, the application server of the mobile Internet transmits a file to 0-TMSI or 0-TMSN. The service paging gateway (PI) is used in this example to implement the function of the information push network element.

In this example, 0-TMSI or 0-TMSN also includes mobile network information and access point information. When the application server wants to send the application information, the service paging gateway address is obtained according to the service paging gateway addressing information carried in the 0-TMSI/0-TMSN.

That is, the application server first parses the access from 0-TMSI/0-TMSN before sending the message. The URL address of the point. For example, the 0-TMSI string consists of "mobile network ID" + "access host name" + random string, for example com.MNOcmcc.HOSTguangdong.User987654321, from which the application server can resolve the access point domain name to "guangdong."Cmcc.com" and can further obtain the IP address of the access point through DNS.

As shown in FIG. 7, this embodiment includes the following steps.

701. When the application server has a file to send, obtain a service paging gateway address according to 0-TMSI/0-TMSN. Send the address link of the file to the service paging gateway, and send the indication to 0-TMSI

(or 0-TMSN) The identified user.

702. The service paging gateway queries local information or queries the HLR according to the 0-TMSI or the 0-TMSN, and obtains the real MSISDN of the user.

703. The service paging gateway sends a WAP push request to the push gateway PPG according to the MSISDN.

704. The PPG pushes the file address link to the mobile terminal by means of WAP Push.

705. After receiving the push message, the mobile terminal may display the content according to the operation instruction in the WAP message, or invoke the terminal function to perform corresponding processing, or establish a mobile packet bearer connection and open an address link of the file to automatically download the address from the application server. file. Example 7

In this embodiment, the application server of the mobile Internet transmits a file to 0-TMSI or 0-TMSN. In this example, the service paging gateway is used to implement the function of the information push network element, and the target terminal is in an idle state.

The application server saves the mobile user's 0-TMSI (or 0-TMSN). As shown in Fig. 8, this embodiment includes the following steps.

801. When the application server has a message to send, send a message transmission request to the service paging gateway, and indicate to send the user identified by 0-TMSI (or 0-TMSN).

802. The service paging gateway queries the local information according to 0-TMSI or 0-TMSN or queries the HLR to obtain the real MSISDN of the user.

803. The service paging gateway sends a message to the MME according to the MSISDN.

804. The MME accesses the mobile terminal in the wireless network, and transmits the message content to the mobile terminal by signaling in the signaling interaction with the mobile terminal.

805. After receiving the push message, the mobile terminal displays the content or invokes the terminal function to perform corresponding processing. Example 8

In this embodiment, the application server of the mobile Internet uses the 0-TMSI/0-TMSN to push the IP packet to the target terminal. In this example, the service paging gateway is used to implement the function of the information push network element.

The application server saves the mobile user's 0-TMSI (or 0-TMSN). As shown in Fig. 9, this embodiment includes the following steps.

901. When the application server has a message to send, send a message transmission request to the service paging gateway, and indicate to send the user identified by 0-TMSI (or 0-TMSN).

902. The service paging gateway queries the local information or queries the HLR according to the 0-TMSI or the 0-TMSN to obtain the real MSISDN of the user.

903. If the mobile terminal is offline, the service paging gateway caches the message and periodically queries the GGSN.

904. If the mobile terminal is online, the service paging gateway obtains the connection status of the mobile terminal and the IP address thereof according to the MSISDN query GGSN.

905. If the GGSN has assigned an IP address to the mobile terminal and the mobile terminal is online, the service paging gateway uses the IP address to establish an IP connection to the mobile terminal.

906. The service paging gateway sends a message to the mobile terminal. Example 9

In this embodiment, the application server of the mobile Internet uses the APP UID to push the IP packet to the target terminal. In this example, the service push gateway is used to implement the function of the information push network element.

The application server saves the APP UID of the mobile user. As shown in FIG. 10, this embodiment includes the following steps.

1001: When the application server has a message to send, send a message sending request to the service push gateway, and send the message to the user identified by the APP UID.

1002. The service push gateway queries the local information according to the APP UID or queries the HSS to obtain the IP address of the user.

1003. The service push gateway establishes an IP connection to the mobile terminal according to the IP address and sends a message to the mobile terminal.

1004. The application on the mobile terminal processes the push information included in the IP packet. After the application server on the mobile Internet obtains the user application identifier of the mobile user directly or indirectly from the mobile terminal, the mobile network or other application server, the mobile terminal can be invited to access the application server for business operations, such as answering the network call. The following embodiments further describe application scenarios for user application identification of different granularities in service paging and push. Example 10:

In this embodiment, the user application identifier is 0-TMSI/0-TMSN. The allocation granularity of the identity is the application granularity, that is, each application on the mobile terminal is assigned a different 0-TMSI/0-TMSN.

After the user installs the application on the mobile terminal and enables it, the mobile terminal applies for each application and its functions to one or more separate 0-TMSI or 0-TMSN and transmits it to the corresponding application server on the mobile Internet. When the application server needs to invite the mobile terminal to access the system, the application server pushes the message to the mobile terminal and includes 0-TMSI in the message content. After receiving the message containing 0-TMSI, the mobile terminal invokes the application corresponding to the 0-TMSI to communicate with the corresponding application server on the mobile Internet. Example 11:

In this embodiment, the user application identifier is 0-TMSI/0-TMSN. The allocation granularity of the identity is the user granularity, that is, all applications of the user (or mobile terminal) are assigned the same 0-TMSI/0-TMSN.

All applications on the mobile terminal deliver the same 0-TMSI or 0-TMSN to the mobile Internet application server. When each application server needs to invite the mobile terminal to access the system, the application server carries the respective Application IDs to the same 0-TMSI push message content. After receiving the pushed message, the mobile terminal invokes the application corresponding to the Application ID and its service to communicate with the corresponding application server on the mobile internet. Example 12:

In this embodiment, the user application identifier is APP UID. The assigned network element is classified by the APN, or the service type is categorized by the service type. The same type of service shares the same APP UID. In the embodiment, the service type granularity is taken as an example, and other granularities are used in a similar manner. Different APP UIDs contain different information to push network element address information, thereby implementing information push by category.

In this embodiment, application 1 and application 2 belong to different types of applications, such as short message classes and browsing. View application. The mobile terminal separately applies the APP UID1 and the APP UID2 to the identifier allocation/maintenance network element. The identifier includes the user identifier of the user, and the IP address of the information push network element and the information push network element corresponding to the two types of services.

The mobile terminal sends two APP UIDs to the service server 1 and the service server 2, respectively. When the service server 2 needs to push the information to the terminal, the service server 2 sends an IP data message push request to the information push network element according to the address information included in the APP UID2, and the request includes the APP UID2. The information push network element obtains the IP address of the user corresponding to the APP UID2 from the identifier distribution/maintenance network element or the local storage information, and sends the packet to the terminal through the mobile network. After the application server on the mobile Internet obtains the user application identifier of the mobile user directly or indirectly from the mobile terminal, the mobile network or other application server, the mobile terminal can be invited to access the application server for business operations, such as answering the network call. The following embodiments 13 and 14 further describe the process by which the application server actively invites a mobile terminal that does not have an application to open to establish a service connection. Example 13

In this embodiment, various applications are installed on the mobile terminal, and each application registers a callback program on the mobile terminal and obtains a corresponding application identifier AID.

After receiving the message containing the special format of the AID from the network side, the mobile terminal OS calls the callback program to perform the wake-up service of the application. At the same time, the operating system OS of the mobile terminal obtains its own user application identifier 0-TMSI/0-TMSN from the service paging gateway. After the application is installed on the mobile terminal, through the process of assigning and maintaining the user application identifier, the mobile terminal corresponding to the application also stores related information of the mobile terminal, including the user application identifier 0-TMSI/0-TMSN and AID.

When the mobile Internet server needs to invite the mobile user to join the server, a special format service page request can be sent to the mobile terminal. As shown in Figure 11, the business process is as follows.

1101. Mobile subscriber identity and AID initialization. The mapping table of "AID, Callback Program Entry" is saved on the mobile terminal OS. The mapping table of User Application Identity, IMSI/MSISDN is saved on the service paging gateway. The user application identifier and AID information of the mobile terminal application are saved on the Internet server.

1102: When the mobile internet needs to invite the mobile user to join the server, for example, inviting the user to play the game together, and sending a service page request to the service paging gateway. The message contains parameters: user application ID, AID, server address (optional), additional parameters (optional). The server address parameter is used to specify that the mobile terminal accesses to a specific server, such as a game server, and the parameter is optional. Additional parameters are used to specify some optional parameter information related to the application.

1103. After receiving the service paging request, the service paging gateway sends a message to the MSC or the SGSN where the mobile terminal is located, and the message includes parameters: MSISDN/IMSL AID, server address (optional), and additional parameters (optional). The MSISDN is derived from the service paging gateway querying the result obtained by the User Application Identity, IMSI/MSISDN mapping table, and thereby determining the MSC or SGSN to which the mobile terminal is currently attached.

1104. The MSC/SGSN queries the current attachment status of the mobile terminal, and then transmits the message to the mobile terminal operating system according to the current attachment status of the mobile terminal. If the mobile terminal and the MSC/SGSN already have a signaling connection, the message is sent to the mobile terminal operating system via the already existing signaling connection. If the mobile terminal is in an idle state and there is no signaling connection with the MSC/SGSN, the MSC/SGSN initiates a network page to the mobile terminal, and then transmits a message to the mobile terminal operating system after the mobile terminal responds to the network page. Parameters included in the message: AID, server address (optional), additional parameters (optional).

1105. The mobile terminal operating system searches the “AID, Callback Program Entry” mapping table according to the AID in the received message, and wakes up the application on the mobile terminal through the callback program. The wake-up indication can include parameters: server address (optional), additional parameters (optional).

1106. After the application on the mobile phone wakes up, instruct the mobile operating system to establish a connection with the wireless packet network and obtain an IP address, and send a service paging response & service access request to the server through the connection. The service paging response & service access request includes service parameter information such as user identity. If the server address is included in the wakeup indication, the service access response is sent to the specified address. Additional parameters in the wakeup indication can be used by the application to determine the content of the service access response.

1107. After receiving the service paging response & service access request, the mobile Internet server may perform user and service authentication to determine that the user is a legitimate user.

1108. After the authentication is passed, the server sends a service access response to the mobile terminal, establishes a service connection with the mobile terminal application, and performs information interaction. Such as multiplayer games, voice chat, etc. Example 14

In this embodiment, various applications are installed on the mobile terminal. After each application is installed and initialized, it obtains its own user application ID 0-TMSI/0-TMSN from the service paging gateway. Pass Through the process of assigning and maintaining the user application identifier, the relevant information of the mobile terminal is also saved on the mobile internet server corresponding to each application, including the user application identifier 0-TMSI/0-TMSN. At the same time, the user application identifier obtained by each application and its corresponding callback program are also saved on the operating system of the mobile terminal. After the mobile terminal operating system receives the message containing the special format of the user application identifier from the network side, the callback program is called to perform the wake-up service of the application.

When the mobile Internet server needs to invite the mobile user to join the server, a special format service page request can be sent to the mobile terminal. The service process is similar to that in the embodiment 14. The difference is that the 0-TMSI in the embodiment 14 is user granular, so the AID is required to further distinguish the destination application of the push message. In the embodiment 15, the 0-TMSI is the application granularity. Therefore, there is no need to have an AID, and it is also possible to determine which application the message is sent to according to 0-TMSI. Correspondingly, in the flow of this embodiment, the mapping table saved on the mobile terminal OS in the embodiment 14 is replaced by the mapping table of "AID, callback program entry" to "user application identifier, callback program entry". Example 15

In this embodiment, after signing the contract, the IMS user saves the IMSI, the IMPU of the IMS user, and the MSISDN, IMSI, and the like in the 2G/3G network in the HSS. When the CSCF receives a SIP call initiated by another user to the IMS user, the CSCF first invites the IMS user to the IMS network by paging, and then performs a SIP call connection and a SIP session. Therefore, it is not necessary to maintain a long-term IP connection between the IMS network and the IMS client, which reduces the resource consumption of the wireless packet network and reduces the security risk faced by the IMS terminal. As shown in Figure 12, the business process is described below.

1201. The IMS user completes the contract, and saves the user's IMPI, IMPU, and MSISDN, IMSI and other information on the HSS.

1202: When the CSCF receives a SIP call initiated by another user to the user, the CSCF suspends the SIP call and initiates an IMS page request to the service paging gateway. The IMS paging request message includes the called IMPU or the called IMPI. Optionally include a CSCF address.

1203. The service paging gateway initiates an inquiry request to the HSS, and queries a network paging identifier corresponding to the called IMPU, such as MSISDN or IMSI. The called request contains the called IMPU.

1204. The HSS queries the database and returns the query result. The return message contains the MSISDN or IMSI parameters.

1205. The service paging gateway passes the CS network or the PS network according to the obtained MSISDN or IMSI. The IMS paging is initiated to the IMS terminal by means of SMS or the like.

1206. After receiving the IMS paging message, the IMS terminal initiates a SIP request to the CSCF measured by the network as a response message of the IMS paging. A typical SIP method can use the registration/re-registration method.

1207. After receiving the IMS paging response, the CSCF forwards the suspended SIP call message according to the contact information of the IMS terminal carried in the response message, and continues the original IMS session process.

1208. The terminal and the network side perform a standard IMS session process to complete execution processing of the IMS service. It can be understood from the detailed description of the foregoing embodiments that the introduction of the user application identifier enables the service server of the mobile Internet to transmit the message to the client program on the mobile terminal without the user network identifier, and realize real-time information transmission. At the same time, the security of the network is guaranteed.

A person skilled in the art can understand that all or part of the process of implementing the above embodiment method can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. In execution, the flow of an embodiment of the methods as described above may be included. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

The above is a preferred embodiment of the present invention, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present invention. These improvements and retouchings are also considered. It is the scope of protection of the present invention.

Claims

Rights request

An application information pushing method, comprising:

The method according to claim 1, wherein before the information push network element receives the application information from the application server that carries the user application identifier, the method includes:

The identifier allocation network element allocates the user application identifier to the mobile terminal, and sends the user application identifier to the application server.

The method according to claim 2, wherein the assigning the network element to the mobile terminal to allocate the user application identifier comprises:

The identifier allocation network element assigns a user application identifier corresponding to the mobile terminal to the mobile terminal, or a user application identifier corresponding to an application on the mobile terminal, or a user corresponding to multiple applications on the mobile terminal Application ID.

4. The method according to claim 3, wherein the plurality of applications on the mobile terminal are multiple applications of the same type on the mobile terminal.

When the mobile terminal enters a new location area in the mobile network, the identity allocation network element of the location area allocates a user application identifier to the mobile terminal, and notifies the mobile terminal.

The method according to any one of claims 2 to 5, characterized in that the user application The identifier is a temporary user application identifier. After the temporary user application identifier is invalid, the identifier allocation network element re-allocates the temporary user application identifier to the mobile terminal.

The method according to any one of claims 2 to 5, wherein the sending the user application identifier to the application server comprises:

The identifier distribution network element directly sends the user application identifier to an application server that provides the application service, or

Sending, by the identifier distribution network element, the user application identifier to the mobile terminal, and then moving by the mobile terminal

The method according to claim 1, wherein the user application identifier further includes information push network element information, so that the application server obtains the information push network element according to the information push network element information. Addressing, and sending the application information to the information push network element according to the information pushing the address of the network element.

The method of claim 1, wherein the transmitting the network element to the mobile terminal according to the user network identifier comprises:

Sending, by the information sending network element, the application information that carries the user application identifier to the mobile terminal according to the user network identifier, so that the mobile terminal performs the application information according to the user application identifier. deal with.

The method according to claim 9, wherein the mobile terminal is installed with a callback program, and the mobile terminal stores a mapping relationship between the callback program entry and the user application identifier.

The method further includes:

And the mobile terminal wakes up the application in the mobile terminal by using a callback procedure according to the received user application identifier, the mapping relationship between the callback program entry and the user application identifier;

And the mobile terminal sends a service access request to the application server according to the application to establish a service connection with the service server.

The method according to claim 1, wherein the mapping relationship between the user application identifier and the user network identifier of the mobile terminal is stored in the identifier maintenance network element or the information push network element.

The method according to claim 1, wherein the method is used in an IMS service interaction of an IP multimedia subsystem, and when the IMS user is called, the information push network element obtains an IMS page request, where The user application identifier is included in the IMS paging request.

An information push network element, where the information push network element includes:

The information sending network element according to claim 13, wherein the information sending unit is further configured to send the application information carrying the user application identifier to the mobile according to the user network identifier. And the terminal, so that the mobile terminal processes the application information according to the user application identifier.

The information push network element according to claim 13, wherein the information push network element further includes a mapping relationship storage unit, configured to store a mapping between the user application identifier and a user network identifier of the mobile terminal. relationship.

The information push network element according to any one of claims 13 to 15, wherein the information push network element is used in an IMS service interaction of an IP multimedia subsystem, and when the IMS user is called, The information receiving unit is further configured to obtain an IMS paging request, where the IMS paging request includes the user application identifier.

An identifier allocation network element, wherein the identifier distribution network element comprises: an identifier allocation unit, configured to allocate a user application identifier to the mobile terminal, where the user application identifier is used to identify an application on the mobile terminal Corresponding user;

The identification distribution network element according to claim 17, wherein the identification distribution unit is a user application identifier of an application on the mobile terminal, or a user application identifier corresponding to multiple applications on the mobile terminal.

The identifier distribution network element according to claim 17, wherein when the mobile terminal enters a new location area in the mobile network, the identifier of the new location area allocates an identifier in the network element. The allocating unit is further configured to allocate a user application identifier to the mobile terminal, and notify the mobile terminal.

The identifier distribution network element according to any one of claims 17 to 19, wherein the identifier sending unit is further configured to send the user application identifier directly to an application server that provides the application service, or The user application identifier is sent to the mobile terminal, and the mobile terminal sends the user application identifier to an application server that provides the application service.

21. A wireless network application information push system, the system comprising:

An identifier allocation network element, configured to allocate a user application identifier to the mobile terminal, and send the user application identifier to an application server that provides the application service, where the user application identifier is used to identify an application corresponding to the mobile terminal User;

An information push network element, configured to receive application information that carries a user application identifier from an application server, and determine, according to a mapping relationship between the user application identifier and a user network identifier of the mobile terminal, a location corresponding to the application information. Describe a user network identifier of the mobile terminal, and send the application information to the mobile terminal according to the user network identifier.

The system according to claim 21, wherein the identifier distribution network element is further used to User application identifier of one application, or user application identifier corresponding to multiple applications on the mobile terminal.

The system according to claim 21, wherein the information push network element is further configured to send the application information that carries the user application identifier to the mobile terminal according to the user network identifier, The mobile terminal processes the application information according to the user application identifier.

The system according to any one of claims 21 to 23, wherein the system further comprises a mobile terminal, configured to receive the application information including the user application identifier, according to the user application identifier The application information is processed.