WO2012162965A1 - Procédé, système et élément de réseau pour « pousser » des données d'application - Google Patents

Procédé, système et élément de réseau pour « pousser » des données d'application Download PDF

Info

Publication number
WO2012162965A1
WO2012162965A1 PCT/CN2011/079017 CN2011079017W WO2012162965A1 WO 2012162965 A1 WO2012162965 A1 WO 2012162965A1 CN 2011079017 W CN2011079017 W CN 2011079017W WO 2012162965 A1 WO2012162965 A1 WO 2012162965A1
Authority
WO
WIPO (PCT)
Prior art keywords
identifier
application
mobile terminal
user
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2011/079017
Other languages
English (en)
Chinese (zh)
Inventor
赵建国
倪慧
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201180001829.8A priority Critical patent/CN102388632B/zh
Priority to PCT/CN2011/079017 priority patent/WO2012162965A1/fr
Publication of WO2012162965A1 publication Critical patent/WO2012162965A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H04W8/245—Transfer of terminal data from a network towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals

Definitions

  • 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
  • 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 mobile packet network such as GPRS network
  • 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.
  • PI Push Initiator
  • PPG push proxy gateway
  • 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).
  • 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.
  • the mobile GPRS network will reclaim the mobile terminal.
  • the IP address and the corresponding network resources cause the connection to be interrupted.
  • the server 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.
  • 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. .
  • 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;
  • 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;
  • 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
  • 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;
  • 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.
  • 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.
  • 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.
  • FIG. 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
  • FIG. 3 is a schematic diagram of a specific composition of an identifier distribution network element in an embodiment of the present invention.
  • FIG. 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.
  • Embodiment 6 is a schematic diagram of a signaling flow of Embodiment 5 in an embodiment of the present invention.
  • Embodiment 7 is a schematic diagram of a signaling flow of Embodiment 6 in an embodiment of the present invention.
  • Embodiment 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. 10 is a schematic diagram of signaling flow of Embodiment 9 in the embodiment of the present invention.
  • Embodiment 13 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)
  • IMSI International Mobile Subscriber Identity
  • 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.
  • 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.
  • 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.
  • the information push network element obtains an IMS paging request, and the IMS paging request includes the user application. logo.
  • IMS IP Multimedia Subsystem
  • 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.
  • 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.
  • 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.
  • the application server may also obtain the address information of the network element from the user side or through the configuration information.
  • the user application identifier may not carry the information of the information feed network element.
  • 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.
  • the allocation granularity may be APN granularity, PDN granularity, service granularity, and the like.
  • 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.
  • 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 Networkease mailbox, Sohu mailbox, etc.
  • 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.
  • the temporary user application identifier may be an Open Temporary Mobile Subscriber Identity (O-TMSI) or an Open Temporary Mobile Subscriber Number (O-TMSN).
  • O-TMSI Open Temporary Mobile Subscriber Identity
  • O-TMSN Open Temporary Mobile Subscriber Number
  • 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.
  • 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.
  • 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.
  • 0-TMSI/0-TMSN can be unified into one.
  • 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.
  • 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.
  • the 0-TMSI/0-TMSN described above may have an expiration date.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the mobile terminal 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.
  • 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.
  • 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 identifier allocation network element is any one of a Policy and Charging Rule Function (PCRF), an MSC, and an AAA/HSS
  • PCRF Policy and Charging Rule Function
  • MSC Mobility Management Entity
  • AAA AAA/HSS
  • 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;
  • WiMAX Worldwide Interoperability for Microwave Access
  • 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
  • the information push network element is a WiMAX voice service (WVS) server, a home agent (Home Agent, Any of HA).
  • WVS WiMAX voice service
  • the embodiment of the present invention further describes a wireless network application information pushing system, and each network element in the system.
  • 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.
  • 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.
  • 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.
  • the information receiving unit is further configured to obtain an IMS paging request, where the IMS paging request includes the user. Application ID.
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • the identifier distribution network element 1 may be any one of a PCRF, an MSC, and an AAA/HSS
  • 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.
  • the identifier distribution network element 1 can be any one of AAA and PCRF
  • the identifier maintenance network element 2 can be any one of AAA and PCRF
  • the information push network element 3 can be a WVS server or a HA. Any one.
  • 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.
  • the format of their user identification may vary.
  • 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.
  • 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.
  • 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.
  • 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.
  • the user application identifiers in these embodiments are further described.
  • the user application identifiers in these embodiments may be the foregoing 0-TMSI, 0-IMSN, or APP UID. .
  • the schemes in the embodiments of the present invention are described by taking 0-TMSI, 0-IMSN or APP UID as an example.
  • 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
  • Embodiments 3 and 4 describe two specific cases in a WiMAX network.
  • 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.
  • 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.
  • the MSC/VLR 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.
  • the location update message carries a replacement indication for indicating whether to replace the existing 0-TMSI and 0-TMSN of the mobile terminal.
  • the HLR 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 Example 2:
  • the user application identifier is specifically 0-TMSI or 0-IMSN.
  • the mobile terminal 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • the application server may request the mobile terminal to provide the APP UID for subsequent business processing, such as short message sending. which is.
  • 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. ,
  • the application 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.
  • 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.
  • 0-TMSI or 0-TMSN
  • the process includes the following steps.
  • the application server 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.
  • SMSC-GW or SMSC in this example, the function for implementing the information push network element
  • 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.
  • SMSC-GW 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.
  • 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.
  • 0-TMSI or 0-TMSN also includes mobile network information and access point information.
  • 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.
  • 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.
  • this embodiment includes the following steps.
  • 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.
  • the service paging gateway sends a WAP push request to the push gateway PPG according to the MSISDN.
  • the PPG pushes the file address link to the mobile terminal by means of WAP Push.
  • 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
  • the application server of the mobile Internet transmits a file to 0-TMSI or 0-TMSN.
  • 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.
  • 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.
  • the service paging gateway sends a message to the MME according to the MSISDN.
  • 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.
  • the mobile terminal After receiving the push message, the mobile terminal displays the content or invokes the terminal function to perform corresponding processing.
  • the application server of the mobile Internet uses the 0-TMSI/0-TMSN to push the IP packet to the target terminal.
  • 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.
  • 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.
  • the service paging gateway caches the message and periodically queries the GGSN.
  • the service paging gateway obtains the connection status of the mobile terminal and the IP address thereof according to the MSISDN query GGSN.
  • the service paging gateway uses the IP address to establish an IP connection to the mobile terminal.
  • the service paging gateway sends a message to the mobile terminal.
  • the application server of the mobile Internet uses the APP UID to push the IP packet to the target terminal.
  • 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.
  • 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.
  • 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.
  • the application on the mobile terminal processes the push information included in the IP packet.
  • 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
  • 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.
  • the mobile terminal 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.
  • 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.
  • the mobile terminal 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 Example 11:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the mobile terminal OS 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.
  • a special format service page request can be sent to the mobile terminal.
  • the business process is as follows.
  • 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.
  • the message contains parameters: user application ID, AID, server address (optional), additional parameters (optional).
  • 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.
  • the service paging gateway 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.
  • 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).
  • 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).
  • 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.
  • the mobile Internet server may perform user and service authentication to determine that the user is a legitimate user.
  • the server sends a service access response to the mobile terminal, establishes a service connection with the mobile terminal application, and performs information interaction.
  • a service access response to the mobile terminal, establishes a service connection with the mobile terminal application, and performs information interaction.
  • 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.
  • 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 0-TMSI in the embodiment 14 is user granular, so the AID is required to further distinguish the destination application of the push message.
  • 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.
  • 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".
  • the IMS user after signing the contract, saves the IMSI, the IMPU of the IMS user, and the MSISDN, IMSI, and the like in the 2G/3G network in the HSS.
  • 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.
  • the business process is described below.
  • the IMS user completes the contract, and saves the user's IMPI, IMPU, and MSISDN, IMSI and other information on the HSS.
  • the CSCF 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.
  • 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.
  • the HSS queries the database and returns the query result.
  • the return message contains the MSISDN or IMSI parameters.
  • 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.
  • the IMS terminal 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.
  • the CSCF 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.
  • 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.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)

Abstract

La présente invention se rapporte à un procédé, à un système et à un élément de réseau adaptés pour « pousser » des données d'application. Le procédé selon l'invention comprend les étapes suivantes : un élément de réseau utilisé pour pousser des données reçoit des données d'application contenant un identifiant d'application utilisateur en provenance d'un serveur d'application (101), et l'identifiant d'application utilisateur est utilisé pour identifier l'utilisateur correspondant à l'application dans le terminal mobile ; sur la base de la relation de mappage entre l'identifiant d'application utilisateur et un identifiant de réseau d'utilisateur du terminal mobile, l'élément de réseau utilisé pour pousser les données confirme l'identifiant de réseau d'utilisateur du terminal mobile correspondant aux données d'application (102) ; ensuite, l'élément de réseau utilisé pour pousser les données transmet les données d'application au terminal mobile sur la base de l'identifiant de réseau d'utilisateur (103). La solution technique de la présente invention permet de « pousser » des données d'application dans le réseau sans fil sans avoir besoin de fournir l'identifiant de réseau d'utilisateur du terminal mobile à un fournisseur de services, et permet d'autre part de garantir la sécurité du réseau.
PCT/CN2011/079017 2011-08-26 2011-08-26 Procédé, système et élément de réseau pour « pousser » des données d'application Ceased WO2012162965A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201180001829.8A CN102388632B (zh) 2011-08-26 2011-08-26 应用信息推送方法、系统和网元
PCT/CN2011/079017 WO2012162965A1 (fr) 2011-08-26 2011-08-26 Procédé, système et élément de réseau pour « pousser » des données d'application

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/079017 WO2012162965A1 (fr) 2011-08-26 2011-08-26 Procédé, système et élément de réseau pour « pousser » des données d'application

Publications (1)

Publication Number Publication Date
WO2012162965A1 true WO2012162965A1 (fr) 2012-12-06

Family

ID=45826521

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/079017 Ceased WO2012162965A1 (fr) 2011-08-26 2011-08-26 Procédé, système et élément de réseau pour « pousser » des données d'application

Country Status (2)

Country Link
CN (1) CN102388632B (fr)
WO (1) WO2012162965A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103716782A (zh) * 2012-10-03 2014-04-09 朱正兴 一种建立imsi和msisdn对应关系的方法
CN113139131A (zh) * 2021-05-17 2021-07-20 北京京东拓先科技有限公司 一种定向信息的发布方法及系统
CN113536134A (zh) * 2021-07-30 2021-10-22 北京乐学帮网络技术有限公司 一种消息推送方法、装置、电子设备以及可读存储介质

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103369457B (zh) * 2012-03-29 2016-08-10 中国移动通信集团公司 一种信息推送方法、装置及系统
CN103686624B (zh) * 2012-09-12 2017-05-03 中国移动通信集团公司 消息推送方法及装置、业务平台
CN102833351B (zh) * 2012-09-14 2015-10-14 魅族科技（中国）有限公司 一种终端应用信息的发送方法、接收方法和相关设备
CN103731449A (zh) * 2012-10-12 2014-04-16 中国移动通信集团公司 将信息推送到移动终端的方法、系统和装置
EP2911343B1 (fr) * 2012-10-17 2019-04-10 Nec Corporation Terminal, système de distribution de message, procédé de distribution de message et programme de réception de message
CN103024050B (zh) * 2012-12-17 2015-11-25 北京奇虎科技有限公司 分发器和对多个服务器进行分发的方法
CN103905374B (zh) * 2012-12-24 2017-06-20 中国移动通信集团公司 一种呼叫方法、系统和设备
CN103905495B (zh) * 2012-12-27 2019-04-23 腾讯科技（深圳）有限公司 一种应用的同步方法及后台服务器
CN103902616B (zh) * 2012-12-28 2017-04-12 腾讯科技（深圳）有限公司 一种推送网页应用消息的方法、装置和系统
CN104113569B (zh) * 2013-04-18 2018-09-25 腾讯科技（深圳）有限公司 一种动态匹配信息来源的方法和开放平台服务器
CN103312702B (zh) * 2013-05-31 2016-05-25 中国联合网络通信集团有限公司 业务推送方法及装置
US9525991B2 (en) * 2013-06-25 2016-12-20 Actiontec Electronics, Inc. Systems and methods for sharing digital information between mobile devices of friends and family using embedded devices
CN104980912B (zh) * 2014-04-11 2019-10-25 中兴通讯股份有限公司 ProSe临时标识的通知与更新方法和装置
CN104158722B (zh) * 2014-07-21 2016-11-09 小米科技有限责任公司 用于轻应用的消息推送方法、装置、终端及服务器
CN105827676B (zh) * 2015-01-04 2019-06-14 中国移动通信集团上海有限公司 一种用户画像信息获取系统、方法及装置
US20180115896A1 (en) * 2015-05-22 2018-04-26 Gogo App Pte. Ltd. Seamless unique user identification and management
CN104991919B (zh) * 2015-06-25 2018-07-03 青岛海信电器股份有限公司 一种智能移动终端信息推送方法和装置
US20180077681A1 (en) * 2016-09-15 2018-03-15 Huawei Technologies Co., Ltd. Method and apparatus for paging an application on a user equipment
CN109104701B (zh) * 2017-06-20 2021-04-30 腾讯科技（深圳）有限公司 基于设备标识码的信息发送方法及服务器
CN107707630B (zh) * 2017-09-15 2020-12-15 百度在线网络技术（北京）有限公司 一种用于文件传输的方法与装置
CN108540831B (zh) * 2018-04-19 2019-10-22 百度在线网络技术（北京）有限公司 用于推送信息的方法和装置
CN109729183B (zh) * 2018-05-16 2021-10-26 平安科技（深圳）有限公司 请求处理方法、装置、设备及存储介质
CN108763433A (zh) * 2018-05-24 2018-11-06 珠海格力电器股份有限公司 信息推送方法和装置
CN109873875B (zh) * 2019-03-19 2022-02-01 维沃移动通信有限公司 一种对应关系建立方法及服务器

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1741507A (zh) * 2004-08-24 2006-03-01 华为技术有限公司 一种实现多媒体消息业务的方法
CN101151918A (zh) * 2005-02-09 2008-03-26 诺基亚公司 用于在通信系统中控制推送操作的方法和装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101277221A (zh) * 2008-05-15 2008-10-01 中兴通讯股份有限公司 一种网管应用程序的部署及应用方法
CN101594642B (zh) * 2009-06-18 2013-05-08 中兴通讯股份有限公司 用于通信网元设备的资源分配方法及装置
CN101969659B (zh) * 2010-09-21 2013-02-06 北京邮电大学 用户事件跟踪方法及系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1741507A (zh) * 2004-08-24 2006-03-01 华为技术有限公司 一种实现多媒体消息业务的方法
CN101151918A (zh) * 2005-02-09 2008-03-26 诺基亚公司 用于在通信系统中控制推送操作的方法和装置

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103716782A (zh) * 2012-10-03 2014-04-09 朱正兴 一种建立imsi和msisdn对应关系的方法
CN113139131A (zh) * 2021-05-17 2021-07-20 北京京东拓先科技有限公司 一种定向信息的发布方法及系统
CN113536134A (zh) * 2021-07-30 2021-10-22 北京乐学帮网络技术有限公司 一种消息推送方法、装置、电子设备以及可读存储介质

Also Published As

Publication number Publication date
CN102388632A (zh) 2012-03-21
CN102388632B (zh) 2016-11-02

Similar Documents

Publication Publication Date Title
WO2012162965A1 (fr) Procédé, système et élément de réseau pour « pousser » des données d'application
US11039381B2 (en) SMF selection based on supported DNN
CN100459735C (zh) 用于在因特网协议网络环境中推送数据的系统和方法
CN102316423B (zh) 一种信息推送方法、装置和系统
US10757645B2 (en) Access control in communications network comprising slices
US8503300B2 (en) Efficient messaging over internet protocol
JP2020515126A (ja) モノのインターネット通信方法、モノのインターネット装置、及びモノのインターネットシステム
WO2011137792A1 (fr) Procédé et appareil permettant la coopération entre des dispositifs push
JP2014505445A (ja) ネットワーク・アプリケーション・サーバからのｕｅアプリケーション・トリガー要求について、モバイル・ネットワークを通じてユーザ装置ｕｅに通知
CN103067857B (zh) 一种通过用户承载标识获取用户位置的系统和方法
US9001741B2 (en) Base-station provided access to IMS services
CN102413453B (zh) 一种mtc设备用户号码的共享方法和系统
WO2017201903A1 (fr) Procédé de contrôle de service de données, et dispositif associé
CN101569216B (zh) 移动电信系统和方法
CN116210252A (zh) 接收用于边缘计算的用户同意的网络操作
CN100549941C (zh) 一种网络推送业务定制方法
WO2018113536A1 (fr) Procédé et système permettant de réaliser une communication connectée à dispositifs multiples
CN101552723B (zh) 一种获取andsf实体的ip地址的方法、系统及装置
CN107612894B (zh) 一种语音业务的处理方法、系统和装置
CN101741812A (zh) 一种用户信息的获取方法、装置和系统
KR20180107763A (ko) 사용자 트래픽 연결 관리 방법
CN101521676A (zh) 一种usi接口调用方法及设备
CN102130917A (zh) Sip终端注册及业务处理的方法、及相关设备
CN102238532A (zh) 一种获取mtc服务器地址的方法及系统
CN101568096B (zh) 一种通用业务接口系统注册的方法与系统

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 201180001829.8

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11866625

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11866625

Country of ref document: EP

Kind code of ref document: A1