WO2012097667A1

WO2012097667A1 - Method for acquiring terminal status, method, apparatus and system for activating terminal

Info

Publication number: WO2012097667A1
Application number: PCT/CN2011/084838
Authority: WO
Inventors: 李志军; 谢宝国; 吴昊; 周成
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-01-21
Filing date: 2011-12-28
Publication date: 2012-07-26
Also published as: CN102612021A; CN102612021B

Abstract

Disclosed in the present invention are a method for acquiring terminal status, a method, apparatus and system activating terminal. The method for acquiring terminal status includes: receiving a request message from an application server, wherein the said request message is used for querying the terminal status; acquiring the terminal status, and sending the status of the terminal to the said application server. The present invention resolves the problem in the related technology that Application Server (AS) can not communicate with the Machine Type Communication (MTC) terminal that does not support Short Message Service (SMS) function; thus enabling the AS to communicate with the MTC terminal that does not support SMS function, thereby processing certain service, such as acquiring terminal status or activating terminal.

Description

The present invention relates to the field of communications, and in particular to a terminal state acquisition method, an activation terminal method, apparatus, and system. BACKGROUND In mobile communication, an application server (Application Server, abbreviated as AS) and an application server proxy (AS Proxy, referred to as an AS proxy) often need to use a network to implement communication with a user terminal (User Equipment, UE for short) (in order to For convenience of description, AS and AS agents will be collectively referred to as AS in this application. For example, in the related art, a Short Message Service (SMS) is often used by an application server to trigger a terminal to establish communication with an application server. 1 is a schematic diagram of an architecture of a terminal accessing a packet domain according to the prior art. As shown in FIG. 1, the structure relates to: UE, UMTS Terrestrial Radio Access Network (UTRAN), and evolution. Terrestrial Radio Access Network (Evolved UMTS for short) E-UTRAN, Serving GPRS Supporting Node (SGSN), Mobile Management Entity (MME), Home Location Register (Home Location) Register, abbreviated as HLR) / Home Subscriber Server (HSS), S-GW Packet Data Network Gateway (P-GW), AS. 2 is a flow chart of the application server AS using the short message service to activate the terminal to communicate with the application server according to the related art. As shown in FIG. 2, the process includes the following steps: Step S201: The terminal accesses the network and is attached to the circuit switch (Circuit Switched) For example, the CS is to be registered with the Mobile Switching Center (MSC). In step S202, the AS wants to activate the terminal to communicate with the AS server, for example, downloading configuration data, and reporting service data by the terminal. The application server AS sends a short message to the terminal, and the short message is routed to the SMS gateway (SMS Gateway, referred to as SMS GW). Step S203, the SMS GW queries the HLR/HSS for the network to which the UE is attached and the corresponding MSC. Step S204, the SMS GW will The short message is routed to the MSC; Step S205, the MSC routes the short message to the UE. Step S206: After receiving the short message, the UE parses the short message content, and determines that the application server needs to establish communication with the UE. Step S207: The UE initiates a Packet Switched (PS) domain. Attached, an IP address is assigned; Step S208, the UE establishes communication with the application server by using an IP communication method. In SMS, a Mobile Subscriber ISDN Number (MSISDN) is used to identify a terminal that the AS uses to communicate with the terminal via SMS. At present, Machine Type Communication (MTC) has been developed. MTC communication is largely a communication between the application server and the terminal. However, in order to reduce costs, some MTC terminals do not provide SMS functionality. This makes it impossible for the MTC AS to communicate with the terminal by SMS to perform certain services. Moreover, other technical means are not provided in the related art, so that the AS can communicate with an MTC terminal that does not support the SMS function. SUMMARY OF THE INVENTION A primary object of the present invention is to provide a terminal state acquisition method, an activation terminal method, apparatus, and system to at least solve the above problems. According to an aspect of the present invention, a terminal state obtaining method is provided, including: receiving a request message from an application server, where the request message is used to query a state of the terminal; acquiring a state of the terminal, and The status of the terminal is sent to the application server. Preferably, the user subscription server receives the request message from the application server, the user subscription server acquires the status of the terminal, and sends the status of the terminal to the application server; or, mobility management The network element receives the request message from the application server, and the mobility management network element locally acquires the status of the terminal, and sends the status of the terminal to the application server. Preferably, before the mobility management network element receives the request message from the application server, the method further includes: the user subscription server receiving a query request sent by the application server, to the application The server sends the mobility management network element currently registered by the terminal. Preferably, the acquiring, by the user subscription server, the status of the terminal includes: the user subscription server locally queries the status of the terminal; and/or the user subscription server queries from the mobility management network element The status of the terminal. Preferably, if the user subscription server locally queries that the status of the terminal is not registered to the network, the user subscription server sends the status of the terminal to the network without being registered to the application server. Preferably, the status of the user subscription server querying the terminal from the mobility management network element includes: in a case that the terminal has been allocated the mobility management network element, the user subscription server is The mobility management network element acquires the status of the terminal. Preferably, the mobility management network element or the user subscription server obtains the status of the terminal from the mobility management network element as: attaching and being assigned an internet protocol IP address or attaching but not assigning an IP address. Preferably, the mobility management network element sends the IP address of the terminal to the user subscription server or the application server, to indicate that the status of the terminal of the user subscription server is attached and assigned an IP address. Preferably, the mobility management network element sends the type of the IP address of the terminal to the user subscription server or the application server. Preferably, the mobility management network element sends the indication information that the terminal does not activate the PDP to the user subscription server or the application server, to indicate that the status of the terminal of the user subscription server is attached but not assigned an IP address. . Preferably, the user subscription server is: an HLR or an HSS; and the mobility management network element is: an MSC, an SGSN or an MME. According to another aspect of the present invention, a method for activating a terminal is provided, including: a mobility management network element receiving a request message for activating a terminal, where the request message carries an identifier of the terminal, the request message The source is the application server; the mobility management network element sends a message to the terminal for activating the terminal. Preferably, before the mobility management network element receives the request message, the method further includes: receiving, by the user subscription server, a request message sent by the application server for activating the terminal, and sending the request message to the mobility management network element. a request message for activating the terminal; or, the mobility management network element receives a request message sent by the application server for activating the terminal. Preferably, before the mobility management network element receives the request message for activating the terminal sent by the application server, the method further includes: the user subscription server receiving the query request sent by the application server, The application server sends the mobility management network element currently registered by the terminal. Preferably, the message that the mobility management network element sends the terminal to activate the terminal includes: the mobility management network element sends a paging Paging message to page the terminal; the mobility management network element After receiving the response message sent by the terminal and responding to the paging message, the NAS message is sent to the terminal, where the NAS message carries the service identifier corresponding to the application server. Preferably, the request message for activating the terminal from the application server further carries a service identifier corresponding to the application server, and the message sent by the mobility management network element to the terminal for activating the terminal The service identifier is also carried in the middle. Preferably, the sending, by the user subscription server, the request message for activating the terminal to the mobility management network element includes: when the terminal has been attached to the network, the mobility of the user subscription server to the terminal is currently registered. The management network element sends a request message to activate the terminal. Preferably, the sending, by the user subscription server, the request message for activating the terminal to the mobility management network element includes: when the terminal is not attached to the network, the user subscription server selects a mobility management network element, and The selected mobility management network element sends a request message to activate the terminal. Preferably, the user subscription server selects the mobility management network element, and the user subscription server selects the mobility management network element according to the service attribute of the terminal subscription; or the user subscription server selects the terminal last time. The registered mobility management network element serves as a mobility management network element that transmits a request message for activating the terminal. Preferably, the sending, by the mobility management network element, the message for activating the terminal to the terminal includes: sending, by the mobility management network element, a non-access stratum NAS message to the terminal according to the identifier of the terminal or Paging a paging message, the NAS message or paging message is used to activate the terminal. Preferably, the message that the mobility management network element sends the terminal to activate the terminal includes: the mobility management network element sends a broadcast message, where the broadcast message further carries the identifier of the terminal . Preferably, the broadcast message is a Paging message or a system broadcast message. Preferably, after the mobility management network element sends the broadcast message, the method further includes: after the terminal monitors the broadcast message, attaching to the network. Preferably, the user subscription server sends a request message for activating the terminal to the mobility management network element, where the request message is further used to query whether the terminal is reachable. Preferably, the user subscription server or the application server sends a request message for activating the terminal to the mobility management network element, where the request message carries a temporary identifier of the terminal, where the temporary identifier In the detachment of the terminal from the network, the mobility management network element sends the temporary identifier to the user subscription server. Preferably, in a case that the application server saves the temporary identifier of the terminal, the user subscription server receives a request message from an activation terminal of the application server, where the request message carries the temporary identifier and service of the terminal. Identifying, in the case that the application server does not save the temporary identifier of the terminal, the user subscription server receives a request message from the application terminal, and the request message carries the identifier of the terminal and the service. Identifying, and replacing the identifier of the terminal with the temporary identifier of the terminal. According to another aspect of the present invention, a terminal state obtaining apparatus is provided, including: a first receiving module, configured to receive a request message from an application server, where the request message is used to query a state of the terminal; And setting to acquire the state of the terminal, and sending the state of the terminal to the application server. Preferably, the first receiving module of the user subscription server is configured to receive the request message from the application server, and the acquiring module located in the user subscription server is configured to acquire the status of the terminal. And sending the status of the terminal to the application server; or the first receiving module located in the mobility management network element is configured to receive the request message from the application server, located at the location The acquiring module of the mobility management network element is configured to acquire the state of the terminal locally, and send the state of the terminal to the application server. According to another aspect of the present invention, a terminal status acquisition system is provided, including: a user subscription server, a mobility management network element, and an application server, where the application server is configured to sign a server or the mobile to the user. The requesting message is used to query the status of the terminal, and the user subscription server or the mobility management network element is configured to acquire the terminal after receiving the request message. a status, and the status of the terminal is sent to the application server. According to another aspect of the present invention, an activation terminal device is provided, which is located in a mobility management network element, and includes: a second receiving module, configured to receive a request message for activating a terminal, where the request message is carried An identifier of the terminal, where the source of the request message is an application server, and a sending module, configured to send a message to the terminal for activating the terminal. Preferably, the sender of the request message received by the second receiving module is a user subscription server, where the signing server receives the request message for activating the terminal sent by the application server, Sending the request message to the mobility management network element; or, the sender of the request message for activating the terminal received by the second receiving module is an application server. According to an aspect of the present invention, an activation terminal system is provided, including: a user subscription server, a mobility management network element, and an application server, the application server being configured to directly log to the mobility management server The network element sends a request message for activating the terminal, where the request message carries an identifier of the terminal; the mobility management network element is configured to send a message for activating the terminal to the terminal. The present invention solves the problem that the AS cannot communicate with the MTC terminal that does not support the SMS function in the related art, so that the AS can communicate with the MTC terminal that does not support the SMS function, and then perform some service, for example, acquiring the terminal status, or Activate the terminal. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, 1 is a schematic diagram of an architecture of a terminal accessing a packet domain according to the prior art; FIG. 2 is a flowchart of an AS using a short message service to activate a terminal to communicate with an AS according to the related art; FIG. 3 is a flowchart according to the present invention. FIG. 4 is a flowchart 1 of a method for activating a terminal according to an embodiment of the present invention. The figure shows an AS sending a terminal activation request to a user subscription server. FIG. 5 is a diagram of a terminal activation request according to an embodiment of the present invention. Flowchart 2 of the method for activating the terminal, the figure shows the AS transmitting a terminal activation request to the mobility management network element; FIG. 6 is a schematic diagram of a network architecture according to an embodiment of the present invention; FIG. 7 is an AS according to an embodiment of the present invention. A flowchart for querying a current status of a terminal by a user subscription server; FIG. 8 is a flowchart of an AS querying a user subscription server for querying a current state of a terminal according to an embodiment of the present invention, where the terminal is not attached to the network; FIG. 9 is a flowchart of an AS querying a user subscription server for querying a current state of a terminal according to an embodiment of the present invention, wherein the terminal is attached to the network and assigned an IP address; FIG. 10 is an AS querying the terminal to the user subscription server according to an embodiment of the present invention; Flowchart of the current state, wherein the terminal is attached to the network but no IP address is assigned; FIG. 11 is a schematic flowchart of the AS querying the mobility management network element for the current state of the terminal according to an embodiment of the present invention; FIG. 12 is a schematic diagram of the current state according to the embodiment of the present invention. FIG. 13 is a flowchart of an AS activating a terminal to a user subscription server according to an embodiment of the present invention; FIG. 14 is a diagram of a terminal attached to a network according to an embodiment of the present invention; FIG. 15 is a flow chart of activating a terminal by a server to a user; FIG. 15 is a flowchart of an AS activating a terminal to a user by a server when the terminal is not attached to the network according to an embodiment of the present invention; FIG. 16 is a temporary use according to an embodiment of the present invention. Identification, a flow chart of the AS signing the server to the user to activate the terminal; FIG. 17 is a use seek in accordance with an embodiment of the present invention. After the message to activate the terminal, sending a flowchart of the service identifier using the NAS message; FIG. 18 is a flowchart of the activation of the terminal to the mobility management network element according to an embodiment of the present invention AS. BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict. It should be noted that the terminal in the following embodiments is applicable to an MTC terminal that does not support the SMS function, and the method in the following embodiments may also be adopted for an MTC terminal that supports the SMS function. Of course, the terminal may not be an MTC terminal, and may be applicable to other types of terminals. In the following embodiments, the MTC terminal (referred to as a terminal in this embodiment) does not provide an SMS function, and the communication between the AS and the MTC terminal adopts an IP-based communication method. This method requires the AS to know the IP address of the terminal. And the network has always assigned this IP to the terminal. To simplify the description, AS is used to represent AS and/or AS agents in the following embodiments, unless otherwise specified.

The AS knows the IP address of the terminal. Generally, when the terminal performs the application layer registration mechanism, the IP address is reported to the AS, and after registration, in order to keep the terminal status updated, the terminal needs to periodically perform registration update to ensure that the AS knows. The terminal is currently active. In many cases, after the terminal is attached to the network, no IP address is assigned. For example, in the General Packet Radio Service (GPRS) network, the process of PS attachment and IP address allocation of the terminal is separated. In some cases, even if the terminal is assigned an IP address, the terminal does not necessarily perform registration with the AS, or the registration update process is not performed to the AS long after the terminal registers with the AS. At this time, when the AS desires to initiate IP communication to the terminal, there may be no available IP address, or the IP address has expired, which will cause the communication initiated by the AS to fail. If the AS fails to initiate IP communication to the terminal multiple times, it is necessary for the AS to know the fact state of the current terminal, for example: the terminal has been reassigned the IP address, although the terminal is attached but the IP address has been released in the GPRS, the terminal has gone from the network. Attached, etc. When the terminal does not support the short message service, the AS cannot communicate with the terminal, and thus the status of the terminal cannot be known. In this embodiment, a method, a device, and a system for acquiring a terminal state are provided. The network element included in the system is used to implement the present embodiment and a preferred implementation manner. The method includes the following steps: Step S12: Receive a request message from an application server, where the request message is used to query the status of the terminal. Step S14: acquire the status of the terminal, and send the status of the terminal to the application server. Through the above steps, the application server can obtain the state of the terminal, and any network element that can obtain the state of the terminal and send it to the application server can perform the above steps, for example, the user subscription server or the mobility management network element, and implemented in the following In the example, the two network elements are taken as an example, but are not limited to the two network elements. For example, the user subscription server receives the request message from the application server, acquires the status of the terminal, and sends the status of the terminal to the application server. Alternatively, the mobility management network element receives the request message from the application server, and obtains the terminal information from the local terminal. Status, and the status of the terminal is sent to the application server. Preferably, the application server may obtain the mobility management network element currently registered by the terminal by sending a query request to the user subscription server. In this embodiment, a terminal state obtaining apparatus is provided, including: a first receiving module, and an acquiring module connected to the first receiving module. As used hereinafter, the term "module" may implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and conceivable. The first receiving module is configured to receive a request message from the application server, where the request message is used to query the status of the terminal, and the acquiring module is configured to acquire the status of the terminal, and send the status of the terminal to the application server. Preferably, the first receiving module located in the user subscription server is configured to receive the request message from the application server, and the acquiring module located in the user subscription server is configured to acquire the state of the terminal, and send the state of the terminal to the application server; or The first receiving module of the mobility management network element is configured to receive the request message from the application server, and the acquiring module of the mobility management network element is configured to obtain the state of the terminal locally, and send the status of the terminal to application server. FIG. 3 is a flowchart of a method for acquiring a terminal state according to an embodiment of the present invention. As shown in FIG. 3, the process includes the following steps: Step S302: a user subscription server (for example, an HLR or an HSS), or a mobility management network element ( For example, the SGSN/MME receives the request message from the AS, where the request message is used to query the status of the terminal; and in step S304, the user subscription server, or the mobility management network element acquires the status of the terminal, and the status of the terminal is Send to AS. Through the above steps, the AS can obtain the status of the terminal, which facilitates the service processing between the AS and the terminal. Preferably, in the implementation, the user subscription server, or the mobility management network element can obtain the status of the terminal in several ways, which is exemplified below, but is not limited thereto. In the first mode, the user subscription server can locally query the status of the terminal. For example, if the status of the terminal is not registered to the network by the user subscription server, the user subscription server sets the status of the terminal to be unregistered to the network. Give AS. In the second mode, the user subscription server may also query the status of the terminal from the mobility management network element (for example, MSC, SGSN, or MME). The user subscription server queries the status of the locally stored terminal to register the terminal in the network (or is attached to the network). In the case that the terminal has been assigned the mobility management network element, the user subscription server queries the mobility management network element. The status to the terminal. For example, the status of the user subscription server querying from the mobility management network element to the terminal is: Attached and assigned an IP address or attached but not assigned an IP address. Preferably, when the terminal status is attached and the IP address is assigned, the mobility management network element sends the IP address of the terminal to the user subscription server, to indicate that the status of the user subscription server terminal is attached and is assigned an IP address, and of course, may also be sent. The type of the IP address of the terminal, such as: IPv4, IPv6, public network IP, screen IP, etc., or a combination of types. Preferably, when the terminal status is attached but the IP address is not assigned, the mobility management network element sends the indication information of the packet data protocol (PDP) of the terminal to the user subscription server to indicate the user subscription server terminal. The status is attached but not assigned an IP address. In the third mode, the user subscription server returns the address of the mobility management network element allocated to the terminal to the AS, and the AS queries the mobility management network element for the status of the terminal, and the mobility management network element returns the status of the terminal to the AS. The status of the terminal returned by the mobility management NE is the same as that of the second method. An activation terminal method, apparatus and system, the network element included in the system being arranged to perform the present embodiment and a preferred embodiment. The method for activating the terminal includes: Step S102: The mobility management network element receives a request message for activating the terminal, where the request message carries the identifier of the terminal, and the source of the request message is an application server; Step S104, the mobility management network element The terminal sends a message for activating the terminal. In the above steps, the application server may directly send a request message to the mobility management network element, or may send a request message to the mobility management network element via other network elements. For example, the user subscription server receives the application server to send the activation terminal. The message is requested and a request message for activating the terminal is sent to the mobility management network element. Preferably, the application server may obtain the mobility management network element currently registered by the terminal by sending a query request to the user subscription server. In the present embodiment, an activation terminal device is provided, which is located in a mobility management network element. As used hereinafter, the term "module" can implement a combination of software and/or hardware of a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and conceivable. The device includes: a second receiving module, and a sending module connected to the second receiving module, where the second receiving module is configured to receive a request message for activating the terminal, where the request message carries the identifier of the terminal, and the request message The source is the application server; the sending module is configured to send a message to the terminal for activating the terminal. Preferably, the sender of the request message received by the second receiving module is a user subscription server, where the signing server sends a request to the mobility management network element after receiving the request message for activating the terminal sent by the application server. Or the sender of the request message for activating the terminal received by the second receiving module is an application server. FIG. 4 is a flowchart 1 of a method for activating a terminal according to an embodiment of the present invention. As shown in FIG. 4, the process includes the following steps: Step S402, the user subscription server receives the request message of the activation terminal from the AS, where the request message carries the identifier of the terminal. Step S404, the user subscription server sends a request message for activating the terminal to the mobility management network element, where The request message carries the identifier of the terminal. Step S406: The mobility management network element sends a message for activating the terminal to the terminal. FIG. 5 is a second flowchart of a method for activating a terminal according to an embodiment of the present invention. As shown in FIG. 5, the process includes the following steps: Step S502: The AS queries a user subscription server to query a current serving network element of the terminal, that is, the terminal is currently registered. Mobility management network element. The user subscription server returns the current service network element of the terminal to the AS. In step S504, the AS sends a request message for activating the terminal to the mobility management network element, where the request message carries the identifier of the terminal. Step S506, the mobility management network element The terminal sends a message for activating the terminal. Preferably, the AS may cause the user subscription server to return the current service network element of the terminal to the AS by querying the current subscription network element of the terminal (ie, the mobility management network element currently registered by the terminal) to the user subscription server. The above-mentioned FIG. 4 and FIG. 5 show the following process: the user subscription server, or the mobility management network element receives the request message of the activation terminal from the AS, wherein the request message carries the identifier of the terminal; the user subscription server, or the mobile The service management network element sends a request message for activating the terminal, where the request message carries the identifier of the terminal. In the above manner, the AS can activate the terminal. Of course, if the AS server needs to notify the terminal of its service identifier, the following preferred implementation manner can be adopted: the user subscription server, or the mobility management network element receives the request from the activation terminal of the AS. The message also carries the service identifier corresponding to the AS; the request message for activating the terminal sent by the user subscription server to the mobility management network element further carries the service identifier; the mobility management network element The message sent by the terminal for activating the terminal further carries the service identifier. Preferably, the service identifier may be an identifier of the AS or an identifier of the service implemented by the AS. For example, the identifier of the AS may be the IP address of the AS, and the service identifier implemented by the AS may be a character or a number representing a certain meaning (for example, SUPL stands for User Face Location System). There are many ways for the mobility management network element to send a message to the terminal for activating the terminal. For example, in order to avoid changes to existing messages as much as possible, the mobility management network element may send a paging message to page the terminal, and After receiving the response message sent by the terminal, the device sends a non-access stratum (Non-Access Stratum, NAS for short) message to the terminal, where the NAS message carries the service identifier corresponding to the application server. By such a processing method, the terminal can be paged without any modification to the existing Paging message. Preferably, the AS sends a request message for activating the terminal to the user subscription server, so that the subscription server sends a request message for activating the terminal to the mobility management network element. Preferably, in a case where the terminal has been attached to the network, the user subscription server sends a request message for activating the terminal to the mobility management network element currently registered by the terminal. Then, the mobility management network element may send a message for activating the terminal to the terminal. For example, the mobility management network element sends a NAS message or a paging message to the terminal according to the identifier of the terminal, where the NAS message Or a Paging message is used to activate the terminal. Preferably, in a case that the terminal is not attached to the network, the user subscription server may select the mobility management network element according to the predetermined policy, and send a request message for activating the terminal to the selected mobility management network element. For example, the user subscription server may select the mobility management network element according to the service attribute of the terminal subscription; for example, the user subscription server may select the mobility management network element that the terminal last registered as the mobility management network that sends the request message of the activation terminal. yuan. Preferably, the service attribute of the terminal subscription may be a range of terminal movement defined in the subscription (for example, indicating a low mobility terminal, signing a fixed location area); selecting the last registered mobility management network element Effectiveness can be limited to a certain effective duration. Preferably, the AS sends a request message for activating the terminal to the mobility management network element currently registered by the terminal, and the mobility management network element may send a message for activating the terminal to the terminal. Before the AS sends a request message for activating the terminal to the mobility management network element, the AS may query the user subscription server for the mobility management network element currently registered by the terminal, and the user subscription server returns the mobility management network element currently registered by the terminal to the AS. Preferably, after the mobility management network element is selected, the mobility management network element may send a broadcast message (for example, a Paging message or a system broadcast message), where the broadcast message further carries the identifier of the terminal. After the mobility management network element sends the broadcast message, after the terminal listens to the broadcast message, it attaches to the network. Preferably, for more security, the user subscription server sends a request message for activating the terminal to the mobility management network element, where the request message carries the temporary identifier of the terminal, wherein the temporary identifier is in the terminal detach from the network, and mobility management The network element sends the temporary identifier to the user's subscription server. Preferably, in the case that the AS holds the temporary identifier of the terminal, the user subscription server receives the request message from the active terminal of the AS, where the request message carries the temporary identifier and the service identifier of the terminal; In the case where the user subscription server receives the request from the active terminal of the AS The request message carries the identifier of the terminal and the service identifier, and replaces the identifier of the terminal with the temporary identifier of the terminal. In addition to the above, the network configuration may adopt the OMA DM mode. One of the modes is currently activated by the SMS. The activation mode in this embodiment may also be adopted. The preferred embodiments are described below in conjunction with the drawings. 6 is a schematic diagram of a network architecture according to an embodiment of the present invention, and the difference between the architecture diagram of FIG. 1 is that an AS/AS proxy and a user subscription server (HLR/HSS), a mobility management network element (SGSN/MME), and the like. Establish the appropriate interface as needed. The interface with the user subscription server (HLR/HSS) and the mobility management network element can be provided to the AS to query the status of the UE and the ability to send a terminal activation request. The preferred embodiment of the present invention provides a method for the AS to query the status of the terminal. In the preferred embodiment, the user subscription server may be an HLR or an HSS, and the mobility management network element is an MSC (CS domain) and an SGSN ( GPRS domain), MME (EPS domain), where the AS sends a service request to the user subscription server to query the current state of the terminal; the user subscription server queries the current state of the terminal from itself, or queries the current state of the terminal from the mobility management network element. And return the current state to the AS. This will be explained below. When the subscriber subscription server queries the terminal from the state that the terminal is not assigned the mobility management network element, the current status of the return terminal is not attached to the network; when the user subscription server queries the terminal from the mobility management network element, the status is: The terminal is currently attached to the network and is assigned a mobility management network element. The user subscription server sends a query request to the mobility management network element, and the mobility management network element returns the current state of the terminal according to the terminal information saved by itself. For example, the terminal is currently attached and assigned an IP address, and the current state of the mobility management network element returning to the terminal is: Attached and assigned an IP address. The state can be expressed by the IP address of the terminal, and the mobility management network element can further return the type of the IP address (a combination of IPv4, IPv6, public network IP, private network IP, etc.); if the terminal is currently attached, but not The IP address is assigned, and the current status of the mobility management NE returns to the terminal is: Attached but not assigned an IP address. This state can be expressed by an inactive PDP. The preferred embodiment will now be described with reference to the accompanying drawings. FIG. 7 is a flowchart of querying the current status of the terminal by the AS to the user subscription server according to the embodiment of the present invention. As shown in FIG. 7, the process includes the following steps: Step S702: The AS queries the terminal for the user to subscribe to the terminal due to the requirement of the service execution. Current state of Step S704, the user subscription server queries the status of the locally saved terminal (for example, the terminal is not currently registered in the network), or queries the mobility management network element for the current status of the terminal, and returns the status according to the status of the queried terminal. AS. Since there are many states of the terminal, some states can be directly returned through the information stored in the user subscription server (for example, the terminal is not currently registered in the network), and some states can be queried to the mobility management network element (for example, the terminal is currently Registered into the network, but with sub-states: attach and assign IP address, attach but not assigned IP address, terminal is not available, etc.). In the case where the terminal is currently registered to the network, in order to obtain a more detailed state of the terminal, the user subscription server may send a query request to the mobility management network element. Finally, the user subscription server returns the status of the queried terminal to the AS. For example, the terminal is not currently registered in the network, and the user subscription server returns the terminal status as: not registered to the network; the terminal is currently registered in the network, and the user subscription server queries the mobility management network element to query the current status of the terminal as: The IP address is assigned; the terminal is currently registered in the network, and the current subscription status of the user subscription server from the mobility management network element to the terminal is: Attached but not assigned an IP address. FIG. 8 is a flowchart of querying a current status of a terminal by a user to a user subscription server according to an embodiment of the present invention. The terminal is not attached to the network. As shown in FIG. 8, the process includes the following steps: Step S801: The AS signs a server with the user. Sending a service request, querying the current status of the terminal; Step S802, the user subscription server determines, according to the local information, that the terminal is not currently registered to the network; Step S803, returning the current status of the terminal to the AS is: not registered to the network. In this embodiment, the so-called unregistered to the network is actually that the user subscription server queries the state information of the locally stored terminal, and finds that the mobility management network element (MSC/SGSN/MME) is not allocated to the current terminal, and thus the terminal is considered Currently not registered to the network. Therefore, the terminal returned by the user subscription server is not currently registered to the network, and is equivalent to: the mobility management network element (MSC/SGSN/MME) is not assigned to the terminal. FIG. 9 is a flowchart of querying a current status of a terminal by a user to a user subscription server according to an embodiment of the present invention. The terminal is attached to the network and assigned an IP address. As shown in FIG. 9, the process includes the following steps: Step S901, AS Sending a service request to the user subscription server to query the current status of the terminal. Step S902: The user subscription server determines, according to the local information, that the terminal is currently registered to the network, and then queries the mobility management network element (for example, the SGSN or the MME) for the current status of the terminal. State; where, the user is contracted to the server The existing accessibility check message may be sent, and the identifier may be carried in the message to request the mobility management network element to immediately return to the current state of the terminal; or, the current state of the independent message query terminal may be newly introduced. Step S903, the mobility management network element checks the status of the terminal, the current terminal has been registered to the mobility management network element, that is, the terminal has been attached to the network, and the network has assigned the IP address to the terminal; in step S904, the step is In a preferred step, the mobility management network element may query the user plane network element (eg, GGSN or PGW) for the IP address of the terminal; the mobility management network element does not always know the IP address of the terminal. For example, under some IPv6 address allocation methods, the IP address of the terminal is not known to the mobility management network element. However, the user plane network element knows the IP address of the terminal, and the mobility management network element can further query the IP address of the terminal to the user plane network element. Step S905: The mobility management network element returns the current status of the terminal to the user subscription server. : Attach and assign

IP address. Or, directly returning the current IP address of the terminal, that is, equivalent to the terminal attaching and allocating the IP address; Step S906, the user subscription server returns the current state of the UE to the AS. The above steps can be used for both the GPRS domain and the EPS domain. However, for the GPRS domain, there is a special case where the terminal can perform GPRS attach but does not activate the PDP context. In this case, the terminal is attached to the PS network but is not assigned an IP address. 10 is a flowchart of querying a current status of a terminal by a user to a user subscription server according to an embodiment of the present invention. The terminal is attached to the network but is not assigned an IP address. As shown in FIG. 10, the process includes the following steps: Step S1001, AS Sending a service request to the user subscription server to query the current status of the terminal. Step S1002: The user subscription server determines, according to the local information, that the terminal is currently registered to the network, and then queries the mobility management network element (for example, the SGSN) for the current state of the terminal. Step S1003: The mobility management network element checks the status of the terminal, and the current terminal has been registered to the mobility management network element, that is, the terminal has been attached to the network, but the terminal is not assigned an IP address; for example, in the GPRS network, The GPRS attach and IP address allocation process is separate. The terminal can perform GPRS attach but does not request PDP activation. Only when the PDP is successfully activated, the terminal is assigned an IP address. Step S1004, the mobility management network element returns the terminal to the user subscription server. Current status: Attached but not assigned an IP address; or, return status That: not activated PDP. The two methods can be regarded as equivalent; in step S1005, the user subscription server returns the current state of the UE to the AS. Preferred Embodiment 2 This preferred embodiment provides a modified embodiment of Embodiment 1. The AS sends a service node query request to the user subscription server to query the mobility management network element currently registered by the terminal, and the user subscription server returns the mobility management network element currently registered by the terminal to the AS; the AS moves to the mobility management network element to the mobility The management NE queries the current status of the terminal. The preferred embodiment will now be described with reference to the accompanying drawings. 11 is a flowchart of querying a current state of a terminal from a mobility management network element according to an embodiment of the present invention. As shown in FIG. 11, the process includes the following steps: Step S1102: The AS signs a server to the user due to service execution requirements. The mobility management network element currently registered by the terminal is queried, and the user subscription server returns the mobility management network element currently registered by the terminal to the AS. If there is no mobility management network element currently registered by the storage server in the user subscription server, that is, the terminal is not registered/attached to the network, the user subscription server returns to the application server that the terminal is not currently registered, or returns an empty mobility management network element. List. According to the response, the application server can determine that the terminal is not registered in the network, and step S 1104 need not be performed. The application server queries the user subscription server to query the mobility management network element currently registered by the terminal. If the current mobility management network element of the terminal is not stored in the user subscription server, step S1104 is performed. Step S1104: The AS queries the mobility management network element for the current state of the terminal, and the mobility management network element returns the current state of the terminal to the AS. After the application server obtains the mobility management network element from the user subscription server, the application server queries the mobility management network element for the status of the terminal. After receiving the query request from the application server, the mobility management network element uses the method in the first embodiment to determine the state of the terminal and return an appropriate response. FIG. 12 is a flowchart of querying the current state of the terminal by the AS to the mobility management network element according to the embodiment of the present invention. As shown in FIG. 12, the process includes the following steps: Step S1201: The AS sends a service request to the user subscription server, and queries the terminal. The current service node, that is, the mobility management network element currently registered by the terminal; Step S1202, the user subscription server returns the current service node of the terminal to the AS; Step S1203, the AS sends a request to the mobility management network element to query the current state of the terminal; Step S1204: The mobility management network element determines a current state of the terminal. The mobility management network element uses the method described in Figures 9-10 to determine the current state of the terminal. In step S1205, the mobility management network element returns the current state of the terminal to the AS. The preferred embodiment of the present invention provides a method for an AS to activate a terminal. The method includes: the AS sends a request for activating the terminal to the user subscription server, where the terminal identifier and the service identifier are carried; and the user subscription server moves to the mobility management network element. Sending a request for activating the terminal, where the terminal identifier and the service identifier are carried; the mobility management network element sends an activation request to the terminal, where the service identifier is carried. The service identifier may be an identifier of the AS or an identifier of the service implemented by the AS. In the process of execution, when the terminal has been attached to the network, the mobility management network element can activate the terminal by using the NAS message; when the terminal is not attached to the network, the user subscription server receives the request initiated by the AS to activate the terminal, The mobility management network element may be selected according to the following principles: (A) selecting a suitable mobility management network element according to the service characteristics of the terminal, for example, a combination of non-roaming and low mobility; (B) the last terminal from the network When the user is detached, the user subscription server saves the mobility management network element as a terminal service. When the activation request of the AS is received, the mobility management network element is selected. It should be noted that, when the terminal is not attached to the network, the mobility management network element and the base station may activate the terminal by using a method such as paging or system broadcast on the network side. On the terminal side, the terminal first listens to the system broadcast of the network in an unattached state. Information, such as Paging information, system broadcast information, after the terminal receives the activation request, performs the process of attaching to the network, and the terminal actively establishes IP communication with the AS. It should be noted that the request of the user subscription server to send the activation terminal to the mobility management network element may be a query for the terminal accessibility request. In this embodiment, the terminal may also be activated by using a temporary identifier assigned to the terminal by the network. The method includes: the terminal is detached from the network, the mobility management network element notifies the user of the temporary identifier of the network to the user, and the user subscription server saves the temporary identifier; when the user subscription server receives the terminal activation request sent by the AS Sending a terminal activation request to the mobility management network element; the user subscription server sends a terminal activation request to the mobility management network element according to the temporary identifier assigned by the saved network to the terminal. The preferred embodiment will now be described with reference to the accompanying drawings. 13 is a flow chart of an AS activating a terminal to a subscriber subscription server according to an embodiment of the present invention. As shown in FIG. 13, the AS communicates to a mobility management network element (eg, MSC, SGSN via a subscriber subscription server (eg, HLR or HSS). The MME sends a request to activate the terminal, and the mobility management network element sends the activation message to the terminal by using a suitable message (for example, a downlink NAS message, a Paging message, and the like). Thereafter, the terminal actively establishes IP communication with the AS. The process includes the following steps: Step S1302: The AS sends a request for activating the terminal to the user subscription server, where the service identifier is carried. The service identifier is an identifier of the AS, and may also be an identifier of the service implemented by the AS. Step S1304: The user subscription server searches for a suitable mobility management network element, and forwards the activation request to the mobility management network element. Step S1306: The mobility management network element sends the activation request to the terminal. After the terminal receives the activation request, Based on the service identifier, it can be known which service requires the terminal to be activated, or which AS has sent the activation request, so that IP communication can be initiated to the AS in a targeted manner. The above steps can be applied to terminals that have been attached to the network: In this case, the terminal may have been assigned an IP address, and IP communication can be initiated directly to the AS. The terminal may also not assign an IP address (if only GPRS is attached, no PDP context is established), the terminal needs to initiate the establishment of an IP bearer, and then assigns an IP address to initiate an IP communication to the AS; a terminal that is not attached to the network: In this case, the terminal is required to listen to the broadcast message of the network even if it is not attached to the network; the user subscription server is required to select an appropriate mobility management network element to send an activation request; the mobility management network element is required to have no terminal context. In this case, the activation request can also be delivered to the base station. FIG. 14 is a flowchart of a terminal attaching to a network in a network, and an AS activating a terminal to a user by a server according to an embodiment of the present invention. As shown in FIG. 14, the process includes the following steps: Step S1401: The AS signs a server to the user (for example, an HLR or The HSS) sends an activation request, carrying a service identifier; wherein the service identifier is carried in order to let the terminal know which service needs to activate the terminal, or which AS wants to activate the terminal and initiate communication. For example: For an MTC application, the service identifier indicates that the MTC application server wishes to activate the terminal. For SUPL, the service identifier indicates that the SUPL Location Server (SLP) wishes to activate the terminal. Step S1402: After receiving the activation request of the AS, the user subscription server queries the mobility management entity (for example, MSC, SGSN, or MME) currently registered by the terminal, and sends an activation request to the mobility management entity. In this step, the user The subscription server can use the existing accessibility check message, and carry the identifier in the message to request the mobility management network element to activate the terminal. The identifier should carry the service identifier in step S1001. Alternatively, a separate message can be newly introduced to activate the terminal. Step S1403: After receiving the activation request, the mobility management entity activates the terminal by using the NAS message. In this step, the mobility management network element carries the service identifier in step S1001 in the NAS message to activate the terminal. The NAS message may be an existing NAS message carrying an activation identifier, or may be a new message for activating the terminal. Step S1404: After receiving the activation request, the terminal returns a response. Step S1405: The terminal initiates IP communication to the specific AS according to the service identifier in the activation request. In the above steps, the mobility management network element sends a NAS message to the terminal to activate the terminal. The mobility management network element may also send a Paging message to the terminal to activate the terminal. For example, the mobility management network element may activate the terminal by using the enhanced Paging message, where the service identifier in step S 1401 is carried. 15 is a flowchart of an AS activating a terminal to a user subscription server in a network that is not attached to a network according to an embodiment of the present invention. The flow shown in the figure is similar to the flow shown in FIG. 14, but has the following differences: In step S1502 (this step is an incremental step compared to FIG. 14), when the user signs up for the server (eg,

After receiving the activation request of the AS, the HLR or HSS needs to find a suitable mobility management network element (for example, MSC, SGSN or MME), and the user subscription server can select by: for not supporting roaming, and having low mobility Sex terminal: According to the mobility range defined in the contract, select the appropriate mobility management network element; the user subscription server (HLR/HSS) saves the mobility management network element registered by the last terminal, and can set a suitable one. The timer clears the saved mobility management network element after the timer expires; in the validity time of the timer, the terminal is considered to be still within the coverage of the mobility management network element. In step S1504, the mobility management network element activates the terminal by using Paging, and carries the service identifier and the ID of the terminal in step S1302 in the Paging parameter. For terminals that are not attached to the network, there must be the ability to listen for Paging messages. After the terminal listens to the activation request from the Paging message, it needs to initiate a network attach procedure, and then initiates communication to the AS. In the flow shown in Figure 15, the AS is generally known as the application layer identifier of the terminal, and the IMRI is used to identify a terminal in the user subscription server (HLR/HSS). Although the user subscription server (HLR/HSS) can establish a mapping relationship between the application layer identifier of the terminal and the IMSI, the current paging message does not support the application layer identifier, and thus the mobility management network element (MSC/SGSN/MME) In the sent Paging message, the terminal ID carried needs to use the IMSI. This approach exposes the IMSI to the network, greatly increasing insecurity. In order to solve the security threat brought by the process shown in FIG. 15, when the terminal detaches from the network, the mobility management network element (for example, MSC, SGSN or MME) will assign a temporary identifier to the terminal (for example, in the CS domain) TMSI, P-TMSI in the GPRS domain, GUTI in the EPS domain) is saved to the user subscription server (HLR/HSS) Medium, so that subsequent Paging can use the saved terminal temporary identifier. Further, the mobility management network element or the user subscription server may also send the temporary identifier to the application server. FIG. 16 is a flowchart of activating a terminal by using a temporary identifier by the AS to the user subscription server. As shown in FIG. 16, the process includes the following steps: Step S1601: The terminal performs a process of detaching from the network; Step S1602 The mobility management network element sends the temporary identifier (for example, TMSI, P-TMSI or GUTI) of the network to the terminal to the user subscription server through the notification message; wherein, the step may include two variants: S1602a, the network is allocated to the terminal The temporary identifier is sent to the AS and saved; S1602b, the temporary identifier is only stored in the subscription server. In step S1603, the AS initiates a request to activate the terminal, and carries the service identifier and the terminal ID. In this step, if the temporary identifier allocated by the network to the terminal in the foregoing step S1602 is transmitted to the AS, the AS may use the temporary identifier as the terminal ID. Otherwise, the AS may use the application layer identifier of the terminal and IMSI as the terminal identifier. Step S1604: After the user subscription server receives the activation request, search for a suitable mobility management network element. In this step, the user subscription server replaces the terminal ID in the activation request with the step according to the mapping relationship.

The temporary identifier of the terminal saved in S1202. Steps S1605 to S1609, the steps shown in FIG. 15 may be used, and details are not described herein again. For the terminal that has not attached the terminal and the attached single radio bearer is released, the paging message Paging may be used to activate the terminal. In the flow shown in Figures 14, 15, and 16, the Paging message is enhanced to carry the service identity. In this way, the cost of retrofitting wireless paging messages is relatively large. 17 is a flowchart of using a paging message to activate a terminal to transmit a service identifier using a NAS message, and FIG. 17 illustrates a manner of activating a terminal using a paging message Paging, but downloading a service identifier is performed according to an embodiment of the present invention. After the NAS connection is established between the UE and the core network, the mobility management network element sends a service identifier to the terminal through the NAS message. In the manner of FIG. 17, the paging message Paging does not need to be modified, which reduces the upgrade cost of the system. As shown in FIG. 17, the process is as follows: Step S1701: The mobility management network element receives a terminal activation request, where the terminal identifier and the service identifier are carried; and steps S1702 to S1705, the mobility management network element uses the existing paging message. Paging to page the terminal, and the terminal responds to the paging message; Step S1706: The non-attached terminal performs a process of attaching to the network and requesting to allocate an IP. The attached terminal initiates a service request to establish a wireless and core network bearer. In step S1707, the mobility NE sends the service identifier to the terminal through the NAS message. Through the service identifier, the terminal can know which service needs to activate the terminal, or which application server needs to activate the terminal. In step S1708, the terminal actively establishes IP communication with the application server. It should be noted that, in the solution of the activation terminal of the third embodiment, the service identifier is required to be sent to the terminal, so that the terminal actively establishes communication with the server. However, for a terminal that is fixedly communicating with only a single AS, the activation behavior can be simpler: the AS sends an activation request to the terminal through the core network, in which the service identifier can be not carried; when the terminal receives the activation request, it is always Try to communicate with AS unconditionally. Preferred Embodiment 4 This preferred embodiment is a modified embodiment of the preferred embodiment 3. The main difference from the third embodiment is that the AS sends a request to activate the terminal to the mobility management network element. The method for the AS to subscribe to the server to query the mobility management entity registered by the terminal is consistent with the description of the second embodiment. The method for the mobility management to send an activation request to the terminal is consistent with the third embodiment. The preferred embodiment will now be described with reference to the accompanying drawings. 18 is a flow diagram of an AS activating a terminal to a mobility management network element in accordance with an embodiment of the present invention. As shown in FIG. 18, the AS obtains the mobility management network element currently registered by the terminal from the user subscription server (HLR/HSS), and sends a request to activate the terminal to the mobility management network element (SGSN/MME). The process includes the following steps: Step S1801, the AS sends a request to the user subscription server, and queries the current service node of the terminal, that is, the mobility management network element currently registered by the terminal; Step S1802, the user subscription server returns the current service node of the terminal to the AS; In step S1803, the AS sends a terminal activation request to the mobility management network element. In step S1804, the mobility management network element sends an activation request to the terminal. In this step, the mobility management network element may adopt the method in the third embodiment. 14-17) Sending an activation request to the terminal; Step S1805, the mobility management network element returns an activation response to the AS. In another embodiment, software is also provided for performing the technical solutions described in the above embodiments and preferred embodiments. In another embodiment, a storage medium is provided, the software being stored, including but not limited to: an optical disk, a floppy disk, a hard disk, a rewritable memory, and the like. Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device so that they may be stored in the storage device by the computing device, or they may be separately fabricated into individual integrated circuit modules, or Multiple modules or steps are made into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

A method for obtaining a terminal state, including:

Receiving a request message from an application server, where the request message is used to query a status of the terminal;

Obtaining a status of the terminal, and transmitting the status of the terminal to the application server.

2. The method according to claim 1, wherein

The user subscription server receives the request message from the application server; the user subscription server acquires the status of the terminal, and sends the status of the terminal to the application server; or

The mobility management network element receives the request message from the application server; the mobility management network element locally acquires the status of the terminal, and sends the status of the terminal to the application server.

The method according to claim 2, wherein, before the mobility management network element receives the request message from the application server, the method further includes:

The user subscription server receives the query request sent by the application server, and sends the mobility management network element currently registered by the terminal to the application server.

The method according to claim 2, wherein the obtaining, by the user subscription server, the status of the terminal comprises:

The user subscription server locally queries the status of the terminal; and/or the user subscription server queries the mobility management network element for the status of the terminal.

The method according to claim 4, wherein, when the user subscription server locally queries that the status of the terminal is not registered to the network, the user subscription server sets the status of the terminal as unregistered. Send to the application server to the network.

The method according to claim 4, wherein the querying, by the user subscription server, the status of the terminal from the mobility management network element comprises: In a case that the terminal has been allocated the mobility management network element, the user subscription server acquires the state of the terminal from the mobility management network element.

The method according to claim 2 or 6, wherein the mobility management network element or the user subscription server obtains the status of the terminal from the mobility management network element as: Protocol IP address or attached but not assigned an IP address.

The method according to claim 7, wherein the mobility management network element sends an IP address of the terminal to the user subscription server or the application server to indicate that the user subscribes to the server. The status is attached and assigned an IP address.

9. The method according to claim 8, wherein the mobility management network element sends the type of the IP address of the terminal to the user subscription server or the application server.

The method according to claim 7, wherein the mobility management network element sends the indication information that the terminal does not activate the PDP to the user subscription server or the application server, to indicate that the user subscription server is The state of the terminal is attached but not assigned an IP address.

11. The method according to claim 2, wherein

The user subscription server is: HLR or HSS;

The mobility management network element is: an MSC, an SGSN, or an MME.

12. A method of activating a terminal, comprising:

The mobility management network element receives a request message for activating the terminal, where the request message carries an identifier of the terminal, and the source of the request message is an application server;

The mobility management network element sends a message to the terminal for activating the terminal.

13. The method of claim 12, wherein before the mobility management network element receives the request message, the method further comprises:

The user subscription server receives a request message sent by the application server for activating the terminal, and sends a request message for activating the terminal to the mobility management network element;

Or,

The mobility management network element receives a request message sent by the application server for activating the terminal.

The method according to claim 13, wherein before the mobility management network element receives the request message for activating the terminal sent by the application server, the method further includes:

The method according to claim 12, wherein the sending, by the mobility management network element, the message for activating the terminal to the terminal comprises:

Transmitting, by the mobility management network element, a paging Paging message to page the terminal;

After receiving the response message sent by the terminal in response to the paging message, the mobility management network element sends a NAS message to the terminal, where the NAS message carries the service corresponding to the application server. Logo.

The method according to claim 12, wherein the request message for activating the terminal from the application server further carries a service identifier corresponding to the application server, and the mobility management network element is directed to the terminal The service identifier is also carried in the sent message for activating the terminal.

The method according to claim 13, wherein the sending, by the user subscription server, the request message for activating the terminal to the mobility management network element comprises:

In the case that the terminal has been attached to the network, the user subscription server sends a request message for activating the terminal to the mobility management network element currently registered by the terminal.

The method according to claim 16, wherein the sending, by the user subscription server, the request message for activating the terminal to the mobility management network element comprises:

If the terminal is not attached to the network, the user subscription server selects the mobility management network element, and sends a request message for activating the terminal to the selected mobility management network element.

19. The method of claim 18, wherein the selecting a mobility management network element by the user subscription server comprises:

The user subscription server selects a mobility management network element according to the service attribute signed by the terminal; or

The user subscription server selects the mobility management network element that the terminal last registered as a mobility management network element that sends a request message to activate the terminal.

The method according to any one of claims 12 to 19, wherein the sending, by the mobility management network element, the message for activating the terminal to the terminal comprises: The mobility management network element sends a non-access stratum NAS message or a paging Paging message to the terminal according to the identifier of the terminal, where the NAS message or the paging message is used to activate the terminal.

The method according to any one of claims 12 to 19, wherein the sending, by the mobility management network element, the message for activating the terminal to the terminal comprises:

The mobility management network element sends a broadcast message, where the broadcast message further carries an identifier of the terminal.

22. The method according to claim 21, wherein the broadcast message is a Paging message or a system broadcast message.

The method according to claim 21, wherein after the mobility management network element sends the broadcast message, the method further includes:

After the terminal listens to the broadcast message, it attaches to the network.

The method according to claim 13 or 14, wherein the user subscription server sends a request message for activating the terminal to the mobility management network element, where the request message is further used to query whether the terminal is reachable. .

25. The method according to claim 13, wherein

The user subscription server or the application server sends a request message for activating the terminal to the mobility management network element, where the request message carries a temporary identifier of the terminal, where the temporary identifier is in the office The terminal detaches from the network, and the mobility management network element sends the temporary identifier to the user subscription server.

The method according to claim 25, wherein, in a case that the application server saves the temporary identifier of the terminal, the user subscription server receives a request message from an activation terminal of the application server, the request message Carrying the temporary identifier and the service identifier of the terminal;

If the application server does not save the temporary identifier of the terminal, the user subscription server receives a request message from the application server, and the request message carries the identifier of the terminal and the service identifier. And replacing the identifier of the terminal with the temporary identifier of the terminal.

27. A terminal state acquiring device, comprising: a first receiving module, configured to receive a request message from an application server, where the request message is used to query a status of the terminal;

An obtaining module is configured to obtain a state of the terminal, and send the state of the terminal to the application server.

28. The device according to claim 27, wherein

The first receiving module located at the user subscription server is configured to receive the request message from the application server; the obtaining module located at the user subscription server is configured to acquire the status of the terminal, and Sending the status of the terminal to the application server;

Or,

The first receiving module of the mobility management network element is configured to receive the request message from the application server; the acquiring module located in the mobility management network element is configured to be obtained locally The status of the terminal, and the status of the terminal is sent to the application server.

29. A terminal status acquisition system, comprising: a user subscription server, a mobility management network element, and an application server, where

The application server is configured to send a request message to the user subscription server or the mobility management network element, where the request message is used to query the status of the terminal;

The user subscription server or the mobility management network element is configured to acquire a status of the terminal after receiving the request message, and send the status of the terminal to the application server.

30. An activation terminal device, located in the mobility management network element, comprising:

The second receiving module is configured to receive a request message for activating the terminal, where the request message carries an identifier of the terminal, and the source of the request message is an application server;

And a sending module, configured to send a message to the terminal for activating the terminal.

The device according to claim 30, wherein the sender of the request message received by the second receiving module is a user subscription server, wherein the signing server receives the application server to send for activation. After the request message of the terminal, sending the request message to the mobility management network element;

Or,

The sender of the request message for activating the terminal received by the second receiving module is an application server. An activation terminal system includes: a user subscription server, a mobility management network element, and an application server, where

The application server is configured to send a request message for activating the terminal to the mobility management network element by using the user subscription server, where the request message carries the identifier of the terminal; the mobility management network The element is arranged to send a message to the terminal for activating the terminal.