CN105828321A - Terminal state acquisition method, system, terminal activation method and system - Google Patents

Terminal state acquisition method, system, terminal activation method and system Download PDF

Info

Publication number
CN105828321A
CN105828321A CN201610258131.9A CN201610258131A CN105828321A CN 105828321 A CN105828321 A CN 105828321A CN 201610258131 A CN201610258131 A CN 201610258131A CN 105828321 A CN105828321 A CN 105828321A
Authority
CN
China
Prior art keywords
terminal
mobility management
network element
management network
message
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.)
Pending
Application number
CN201610258131.9A
Other languages
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN201610258131.9A priority Critical patent/CN105828321A/en
Publication of CN105828321A publication Critical patent/CN105828321A/en
Pending legal-status Critical Current

Links

Classifications

    • 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

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention provides a terminal state acquisition method, a terminal state acquisition system, a terminal activation method and a terminal activation system. The terminal activation method includes the following steps that: a user subscription server receives a terminal activation request message from an application server, wherein the request message carries the identifier of a terminal; the user subscription server sends the terminal activation request message to a mobility management network element, wherein the request message carries the identifier of the terminal; and the mobility management network element sends a message used for terminal activation to the terminal. According to the methods and systems of the invention, the application server can communicate with an MTC (machine type communication) terminal which does not support an SMS function, so that a certain kind of services can be carried out.

Description

Terminal state acquisition method, terminal activation method and system
The application is to the application number: 201110024174.8, filing date: the invention is a divisional application of the original application named as terminal state acquisition method, terminal activation method and system on 21.01.2011.
Technical Field
The invention relates to the field of communication, in particular to a terminal state acquisition method, a terminal activation method and a terminal activation system.
Background
In mobile communication, an application server (AS for short) often needs to communicate with a user equipment (UE for short). In the related art, a Short Message Service (SMS) is often used by an application server to trigger a terminal and the application server to establish communication.
Fig. 1 is a schematic diagram of an architecture for a terminal to access a packet domain according to the prior art, and as shown in fig. 1, the architecture involves: the mobile terminal comprises UE, a UMTS terrestrial radio access network (UMTSTerrestrial radio Access network, referred to AS UTRAN for short), an evolved terrestrial radio access network (evolved UMTS referred to AS E-UTRAN for short), a serving GPRS support node (serving GPRS support node, referred to AS SGSN for short), a mobility management entity (mobility management entity, referred to AS MME for short), a home location register (HLR for short)/a home subscriber server (HSS for short), S-GW, a packet data network gateway (packet data network gateway, referred to AS P-GW for short) and AS. Fig. 2 is a flowchart of communication between an application server AS and an application server using a short message service activation terminal according to the related art, AS shown in fig. 2, the flowchart includes the following steps:
step S201, the terminal accesses the network and attaches to a Circuit Switched (CS) domain, that is, registers to a Mobile Switching Center (MSC);
in step S202, the AS wishes to activate the terminal to communicate with the AS server, for example, download configuration data, report service data by the terminal, and so on. An application server AS sends a short message to a terminal, and the short message is routed to a short message gateway (SMSGaway, abbreviated AS SMSGW);
step S203, SMSGW inquires the network attached by UE and the corresponding MSC to HLR/HSS;
step S204, SMSGW routes the short message to MSC;
step S205, MSC routes the short message to UE;
step S206, after receiving the short message, the UE analyzes the content of the short message and determines that the application server needs to establish communication with the UE;
step S207, the UE initiates attachment of a packet switched domain (PS for short), and is assigned an IP address;
step S208, the UE establishes communication with the application server by using an IP communication mode.
In SMS, a mobile subscriber ISDN number (MSISDN for short) is used to identify a terminal, and the AS communicates with the terminal via SMS using the MSISDN number.
Currently, Machine Type Communication (MTC) is developed, and MTC communication is largely communication between an application server and a terminal. However, some MTC terminals do not provide the SMS function in order to reduce costs. This makes MTCAS unable to communicate with terminals by means of short messages for certain services. Also, other technical means are not provided in the related art to enable the AS to communicate with the MTC terminal that does not support the SMS function.
Disclosure of Invention
The present invention is directed to a method for acquiring a terminal status, a method for activating a terminal, and a system thereof, so as to at least solve the above problems.
According to an aspect of the present invention, there is provided a terminal status acquiring method, including: a user signing server receives a request message from an application server, wherein the request message is used for inquiring the state of a terminal; and the user signing server acquires the state of the terminal and sends the state of the terminal to the application server.
Preferably, the acquiring, by the subscriber subscription server, the state of the terminal includes: the user signing server locally inquires the state of the terminal; and/or, the user subscription server inquires the state of the terminal from a mobility management network element.
Preferably, when the user subscription server locally queries that the state of the terminal is unregistered to the network, the user subscription server sends the state of the terminal that is unregistered to the network to the application server.
Preferably, the querying, by the subscriber subscription server, the state of the terminal from the mobility management network element includes: and under the condition that the terminal is already allocated with the mobility management network element, the user subscription server inquires the state of the terminal from the mobility management network element.
Preferably, the state of the terminal queried by the subscriber subscription server from the mobility management network element is: attached and assigned an internet protocol IP address or attached but not assigned an IP address.
Preferably, the mobility management network element sends the IP address of the terminal to the subscriber subscription server to indicate that the state of the terminal of the subscriber subscription server is attached and allocated with an IP address.
Preferably, the mobility management network element sends the type of the IP address of the terminal to the subscriber subscription server.
Preferably, the mobility management network element sends, to the subscriber subscription server, indication information that the terminal does not activate the PDP, so as to indicate that the state of the terminal of the subscriber subscription server is attached but an IP address is not allocated.
Preferably, the user subscription server is: HLR or HSS; the mobility management network element is as follows: MSC, SGSN, or MME.
According to another aspect of the present invention, there is also provided a method for activating a terminal, including: a user signing server receives a request message of activating a terminal from an application server, wherein the request message carries an identifier of the terminal; the user signing server sends a request message for activating the terminal to a mobility management network element, wherein the request message carries the identifier of the terminal; and the mobility management network element sends a message for activating the terminal to the terminal.
Preferably, the sending, by the mobility management network element, the message for activating the terminal to the terminal includes: the mobility management network element sends a Paging message to page the terminal; and the mobility management network element receives a response message which is sent by the terminal and responds to the paging message, and sends an NAS message to the terminal, wherein the NAS message carries the service identifier corresponding to the application server.
Preferably, the request message from the activation terminal of the application server received by the user subscription server also carries a service identifier corresponding to the application server; the request message for activating the terminal sent by the user subscription server to the mobility management network element also carries the service identifier; and the message which is sent to the terminal by the mobility management network element and used for activating the terminal also carries the service identifier.
Preferably, the sending, by the subscriber subscription server, the request message for activating the terminal to the mobility management network element includes: and under the condition that the terminal is attached to the network, the user subscription server sends a request message for activating the terminal to a mobility management network element which is currently registered by the terminal.
Preferably, the sending, by the mobility management network element, the message for activating the terminal to the terminal includes: and the mobility management network element sends an NAS message or a Paging message to the terminal according to the identifier of the terminal, wherein the NAS message or the Paging message is used for activating the terminal.
Preferably, the sending, by the subscriber subscription server, the request message for activating the terminal to the mobility management network element includes: and under the condition that the terminal is not attached to the network, the user subscription server selects a mobility management network element and sends a request message for activating the terminal to the selected mobility management network element.
Preferably, the selecting, by the subscriber subscription server, the mobility management network element includes: the user signing 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 registered by the terminal last time as the mobility management network element for sending the 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: and the mobility management network element sends a broadcast message, wherein the broadcast message also 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: and the terminal is attached to a network after monitoring the broadcast message.
Preferably, the subscriber subscription server sends a request message for activating the terminal to a mobility management network element, where the request message is further used to query whether the terminal is reachable.
Preferably, the user subscription server sends a request message for activating the terminal to a mobility management network element, where the request message carries a temporary identifier of the terminal, and the temporary identifier is sent to the user subscription server by the mobility management network element when the terminal is detached from the network.
Preferably, under the condition that the application server stores the temporary identifier of the terminal, the user subscription server receives a request message from the application server for activating the terminal, wherein the request message carries the temporary identifier of the terminal and the service identifier; and under the condition that the application server does not store the temporary identifier of the terminal, the user signing server receives a request message from the application server for activating the terminal, wherein 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.
According to another aspect of the present invention, there is also provided a terminal status acquiring system, including: the system comprises a user signing server and an application server, wherein the application server is used for sending a request message to the user signing server, and the request message is used for inquiring the state of a terminal; and the user signing server is used for acquiring the state of the terminal after receiving the request message and sending the state of the terminal to the application server.
Preferably, the user subscription server is configured to locally query the status of the terminal; and/or querying the state of the terminal from a mobility management network element.
According to still another aspect of the present invention, there is provided an activation terminal system including: the mobile terminal comprises a user signing server, a mobile management network element and an application server, wherein the application server is used for sending a request message for activating the terminal to the user signing server, and the request message carries an identifier of the terminal; the user subscription server is used for sending a request message for activating the terminal to the mobility management network element, wherein the request message carries the identifier of the terminal; the mobility management network element is configured to send a message for activating the terminal to the terminal.
The invention solves the problem that the AS can not communicate with the MTC terminal which does not support the SMS function in the related technology, so that the AS can communicate with the MTC terminal which does not support the SMS function to further perform certain service, such AS acquiring the terminal state or activating the terminal.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
fig. 1 is a schematic diagram of an architecture for a terminal to access a packet domain according to the prior art;
fig. 2 is a flowchart of an AS activating a terminal to communicate with the AS using a short message service according to the related art;
fig. 3 is a flowchart of a terminal status acquisition method according to an embodiment of the present invention;
fig. 4 is a flowchart of a method of activating a terminal according to an embodiment of the present invention;
fig. 5 is a flowchart of an AS querying a subscriber sign-up server for a current state of a terminal according to an embodiment of the present invention;
fig. 6 is a flowchart of an AS querying a subscriber subscription server for a current state of a terminal, where the terminal is not attached to a network, according to an embodiment of the present invention;
fig. 7 is a flowchart of the AS querying a subscriber sign-up server for a current state of a terminal, which is attached to a network and assigned an IP address, according to an embodiment of the present invention;
fig. 8 is a flowchart of an AS querying a subscriber sign-up server for a current state of a terminal, which is attached to a network but is not allocated an IP address, according to an embodiment of the present invention;
fig. 9 is a flowchart of an AS activating a terminal to a subscriber sign-up server according to an embodiment of the present invention;
fig. 10 is a flowchart of the AS activating the terminal to the subscriber server according to the embodiment of the present invention;
fig. 11 is a flowchart of an AS activating a terminal to a subscriber server when the terminal is not attached to a network according to an embodiment of the present invention;
fig. 12 is a flowchart of the AS activating a terminal to a subscriber server using a temporary identifier according to an embodiment of the present invention;
fig. 13 is a flowchart of sending a service identifier using NAS messaging after activating a terminal using a paging message according to an embodiment of the present invention.
Detailed Description
The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
It should be noted that the terminal in the following embodiments is applicable to MTC terminals that do not support the SMS function, and the method in the following embodiments may also be adopted for MTC terminals that support the SMS function. Of course, the terminal may not be an MTC terminal, and may be applicable to other types of terminals.
In this embodiment, the MTC terminal (simply referred to AS terminal in this embodiment) does not provide the SMS function, and the MTCAS (simply referred to AS) and the MTC terminal communicate using an IP-based communication method. This approach requires that the AS knows the IP address of the terminal and that the network always assigns this IP to the terminal.
The AS knows the IP address of the terminal, typically when the terminal performs an application layer registration mechanism, the IP address is reported to the AS, and after registration, in order to keep the terminal state updated, the terminal needs to periodically perform registration update to ensure that the AS knows that the terminal is currently active. Many times, after the terminal is attached to the network, the terminal is not assigned an IP address, for example, in a General Packet Radio Service (GPRS) network, the PS attachment and IP address assignment processes of the terminal are separated. In some cases, even if the terminal is assigned an IP address, the terminal may not necessarily perform registration with the AS, or the terminal may not perform a registration update procedure with the AS long AS it is registered with the AS. At this time, when the AS desires to initiate an IP communication to the terminal, there may be no available IP address or the IP address has failed, which will cause the communication initiated by the AS to end up in failure. If the AS fails to initiate IP communication to the terminal in multiple attempts, it is necessary for the AS to know the actual status of the current terminal, such AS: the terminal has been reassigned an IP address, the terminal has been attached but the IP address has been released in GPRS, the terminal has been detached from the network, etc. When the terminal does not support the short message service, the AS cannot communicate with the terminal, and further cannot acquire the state of the terminal.
In this embodiment, a method and a system for acquiring a terminal state are provided, where the system includes a network element configured to execute this embodiment and a preferred embodiment, and the method for acquiring a terminal state is described below, where fig. 3 is a flowchart of the method for acquiring a terminal state according to an embodiment of the present invention, and as shown in fig. 3, the flowchart includes the following steps:
step S302, a subscriber subscription server (for example, HLR or HSS) receives a request message from an AS, wherein the request message is used for inquiring the state of a terminal;
step S304, the user subscription server obtains the state of the terminal, and sends the state of the terminal to the AS.
Through the steps, the AS can acquire the state of the terminal, and service processing between the AS and the terminal is facilitated.
Preferably, in implementation, the subscriber subscription server may acquire the state of the terminal in several ways, which is illustrated below, but is not limited thereto.
In a first manner, the subscriber subscription server may locally query the state of the terminal, for example, in a case that the state of the terminal queried locally by the subscriber subscription server is unregistered to the network, the subscriber subscription server sends the state of the terminal unregistered to the network to the AS.
In a second way, the subscriber subscription server may also query the status of the terminal from a mobility management network element (e.g., MSC, SGSN, or MME). The method comprises the steps that a user subscription server inquires the state of a locally stored terminal to be that the terminal is registered in a network (or attached to the network), and under the condition that the terminal is distributed with a mobility management network element, the user subscription server inquires the state of the terminal from the mobility management network element. For example, the state that the subscriber subscription server inquires the terminal from the mobility management network element is: attached and assigned an IP address or attached but not assigned an IP address. Preferably, when the terminal is in the attached and allocated IP address state, the mobility management network element sends the IP address of the terminal to the subscriber server to indicate that the terminal is in the attached and allocated IP address state, and of course, the type of the IP address of the terminal may also be sent, such as: IPv4, IPv6, public network IP, web IP, etc., or a combination of types. Preferably, when the terminal is in the attached state but not allocated with the IP address, the mobility management network element sends, to the subscriber subscription server, indication information that the terminal does not activate the PDP, so as to indicate that the terminal of the subscriber subscription server is in the attached state but not allocated with the IP address.
A method and a system for activating a terminal, where the system includes a network element for executing the embodiment and the preferred embodiments, the method for activating a terminal is described below, fig. 4 is a flowchart of the method for activating a terminal according to the embodiment of the present invention, and as shown in fig. 4, the flowchart includes the following steps:
step S402, a user signing server receives a request message from an AS for activating a terminal, wherein the request message carries a terminal identifier;
step S404, the user signing server sends a request message for activating the terminal to the mobility management network element, wherein 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.
Through the above steps, the AS may activate the terminal, and of course, if the AS server needs to notify the terminal of its service identifier, the following preferred embodiments may be adopted: the request message from the AS activation terminal received by the user subscription server also carries a 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 also carries the service identifier; and the message which is sent to the terminal by the mobility management network element and used for activating the terminal also carries the service identifier.
Preferably, the service identification may be an identification of the AS, but also of the service implemented by the AS. For example, the identity of the AS may be the IP address of the AS, and the identity of the service implemented by the AS may be an character or number representing a meaning (e.g., SUPL represents a user plane location system).
For example, in order to avoid changing an existing message as much as possible, the mobility management network element may send a Paging message to page the terminal, and after receiving a response message sent by the terminal, send a Non-access stratum (NAS) message to the terminal, where the NAS message carries a service identifier corresponding to the application server. The terminal can be paged by the processing mode without changing the existing Paging message.
Preferably, in case that the terminal has been attached to the network, the subscriber subscription server transmits a request message for activating the terminal to a mobility management network element to which the terminal is currently registered. Then, the mobility management element may send a message for activating the terminal to the terminal, for example, the mobility management element sends a 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 for activating the terminal.
Preferably, in a case where the terminal is not attached to the network, the subscriber subscription server may select a mobility management network element according to a 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 a mobility management network element according to a service attribute subscribed by the terminal; for another example, the subscriber subscription server may select a mobility management network element in which the terminal is registered last time as a mobility management network element that transmits a request message for activating the terminal. Preferably, the service attribute of the terminal subscription may be a range of terminal movement defined in the subscription (e.g., indicating a low-mobility terminal, subscribing to a fixed location area); the validity of selecting the last registered mobility management element may be limited to a certain validity period.
Preferably, after selecting the mobility management network element, the mobility management network element may send a broadcast message (e.g., Paging message or system broadcast message), where the broadcast message also carries an identifier of the terminal. After the mobility management network element sends the broadcast message, the terminal attaches to the network after monitoring the broadcast message.
Preferably, in order to be more secure, the subscriber subscription 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, and the mobility management network element sends the temporary identifier to the subscriber subscription server when the terminal is detached from the network.
Preferably, under the condition that the AS stores the temporary identifier of the terminal, the user subscription server receives a request message from the AS for activating the terminal, wherein the request message carries the temporary identifier and the service identifier of the terminal; and under the condition that the AS does not store the temporary identifier of the terminal, the user signing server receives a request message from the AS for activating the terminal, the request message carries the identifier and the service identifier of the terminal, and the identifier of the terminal is replaced by the temporary identifier of the terminal.
In addition to the above, the network configuration may adopt an oma dm mode, one of which is also currently activating the terminal by SMS, and of course, the activation mode in this embodiment may also be adopted.
The preferred embodiments will be described below with reference to the accompanying drawings.
Preferred embodiment 1
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), an SGSN (GPRS domain), or an MME (EPS domain), wherein the AS sends a service request to the user subscription server to query the current state of the terminal; the user signing server inquires the current state of the terminal from the user signing server, or inquires the current state of the terminal from the mobile management network element, and returns the current state to the AS. This will be explained below.
When the user signing server inquires the state of the terminal from the user signing server, the terminal is not allocated with the mobility management network element, and the current state of the terminal is returned to be not attached to the network; when the user subscription server inquires the state of the terminal from the mobility management network element, the state is as follows: the terminal is currently attached to the network and is allocated with 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 terminal information stored by the mobility management network element. For example, the terminal is currently attached and is assigned with an IP address, and the current state of the terminal returned by the mobility management network element 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 (combination of IPv4, IPv6, public network IP, private network IP and the like); if the terminal is currently attached but not allocated with the IP address, the current state of the terminal returned by the mobility management network element is: attached but not assigned an IP address. This state may be expressed with a non-activated PDP.
The preferred embodiments will be described below with reference to the accompanying drawings.
Fig. 5 is a flowchart of an AS querying a subscriber subscription server about a current state of a terminal according to an embodiment of the present invention, where, AS shown in fig. 5, the flowchart includes the following steps:
step S502, AS inquires the current state of the terminal from the user signing server due to the need of service execution;
step S504, the user subscription server queries the state of the terminal stored locally (for example, the terminal is not currently registered in the network), or queries the current state of the terminal from the mobility management network element, and returns the current state of the terminal to the AS according to the queried state of the terminal.
Since there are many states of the terminal, some states may be returned directly through information stored in the subscriber sign-up server (e.g., the terminal is not currently registered in the network), some states may be queried from the mobility management network element (e.g., the terminal is currently registered in the network but has sub-states: attached and assigned IP address, attached but not assigned IP address, terminal unreachable, etc.). In order to obtain a more detailed status of the terminal in case the terminal is currently registered to the network, the subscriber subscription server may send a query request to the mobility management network element. And finally, the user signing server returns the inquired state of the terminal to the AS.
For example, when the terminal is not currently registered in the network, the user subscription server returns the terminal state as follows: unregistered with a network; the terminal is currently registered in the network, and the user subscription server inquires from the mobility management network element that the current state of the terminal is as follows: attaching and allocating an IP address; the terminal is currently registered in the network, and the user subscription server inquires from the mobility management network element that the current state of the terminal is as follows: attached but not assigned an IP address.
Fig. 6 is a flowchart of an AS querying a subscriber subscription server about a current state of a terminal, where the terminal is not attached to a network, according to an embodiment of the present invention, AS shown in fig. 6, the flowchart includes the following steps:
step S601, AS sends service request to the user signing server, and inquires the current state of the terminal;
step S602, the user signing server judges that the terminal is not registered to the network currently according to the local information;
step S603, returning to the AS that the current state of the terminal is: is not registered to the network.
In this embodiment, the unregistered network is actually that the subscriber subscription server queries the state information of the terminal stored locally, and finds that no mobility management network element (MSC/SGSN/MME) is allocated to the current terminal, and thus considers that the terminal is not currently registered in the network. Therefore, the state that the terminal returned by the user subscription server is not registered to the network currently is equivalent to: no mobility management network element (MSC/SGSN/MME) is allocated to the terminal.
Fig. 7 is a flowchart of the AS querying a subscriber subscription server about a current state of a terminal, where the terminal is attached to a network and is assigned an IP address, according to an embodiment of the present invention, AS shown in fig. 7, the flowchart includes the following steps:
step S701, AS sends a service request to a user signing server, and inquires the current state of a terminal;
step S702, the user signing server judges that the terminal is registered to the network currently according to the local information, and inquires the current state of the terminal to a mobility management network element (such as SGSN or MME); the user signing server can check the existing accessibility, and the message carries an identifier to require the mobile management network element to immediately return to the current state of the terminal; alternatively, a separate message may be newly introduced to query the current state of the terminal.
Step S703, the mobility management element checks the state of the terminal, and the current terminal is already registered in the mobility management element, that is, the terminal is already attached to the network, and the network has already allocated an IP address to the terminal;
step S704, which is a preferred step, the mobility management network element may query the IP address of the terminal to a user plane network element (e.g., GGSN or PGW); 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 element. However, the user plane network element knows the IP address of the terminal, so the mobility management element may further query the user plane network element for the IP address of the terminal;
step S705, the mobility management element returns the current state of the terminal to the user subscription server: attach and assign an IP address. Or directly returning the current IP address of the terminal, namely, the current IP address is equal to the IP address which is attached and allocated to the terminal;
step S706, the user subscription server returns the current state of the UE to the AS.
The above steps can be used for both GPRS domain and EPS domain. However, for the GPRS domain, there is a special case that: the terminal may perform a GPRS attach but without activating a PDP context. This is the case when the terminal is attached to the PS network but is not assigned an IP address.
Fig. 8 is a flowchart of the AS querying a subscriber subscription server about the current status of a terminal, wherein the terminal is attached to a network but is not allocated an IP address, AS shown in fig. 8, and the flowchart includes the following steps:
step S801, AS sends a service request to a user signing server, and inquires the current state of a terminal;
step S802, the user signing server judges that the terminal is registered to the network currently according to the local information, and then inquires the current state of the terminal to a mobility management network element (for example, SGSN);
step S803, the mobility management element checks the state of the terminal, and the current terminal has been registered in the mobility management element, that is, the terminal has been attached to the network, but no IP address has been allocated to the terminal; for example, in a GPRS network, the GPRS attach and IP address assignment process are separated, the terminal may perform the GPRS attach but does not request PDP activation, and the terminal is assigned an IP address only if the PDP is successfully activated;
step S804, the mobility management element returns the current state of the terminal to the user subscription server: attached but unassigned IP addresses; alternatively, the return state may be: the PDP is not activated. These two ways can be considered equivalent;
step S805, the user subscription server returns the current state of the UE to the AS.
Preferred embodiment two
The preferred embodiment provides a method for activating an AS terminal, which comprises the following steps: AS sends a request for activating a terminal to a user signing server, wherein the request carries a terminal identifier and a service identifier; a user subscription server sends a request for activating a terminal to a mobility management network element, wherein the request carries a terminal identifier and a service identifier; and the mobility management network element sends an activation request to the terminal, wherein the activation request carries the service identifier.
The service identifier may be an identifier of the AS or an identifier of a service implemented by the AS.
In the execution process, when the terminal is already attached to the network, the mobility management network element may activate the terminal using the NAS message; when the terminal is not attached to the network, after the user subscription server receives a request for activating the terminal initiated by the AS, the mobility management network element can be selected according to the following principle: (A) selecting a proper mobility management network element according to the service characteristics of the terminal, such as the combination of non-roaming, low mobility and the like; (B) and the user signing server stores the mobile management network element serving the terminal when the terminal is detached from the network last time. And when receiving an activation request of the AS, selecting the mobility management network element. 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 methods such as Paging, system broadcast, and the like on the network side; on the terminal side, the terminal monitors the system broadcast information of the network, such AS Paging information and system broadcast information, in the non-attached state, executes the process of attaching to the network after receiving the activation request, and actively establishes IP communication with the AS. It should be noted that the request for activating the terminal, which is sent by the subscriber subscription server to the mobility management network element, may be a request for querying the accessibility of the terminal.
In this embodiment, the terminal may also be activated using a temporary identity assigned to the terminal by the network. The method comprises the following steps: the terminal is detached from the network, the mobility management network element informs the user signing server of the temporary identifier allocated to the terminal by the network, and the user signing server stores the temporary identifier; when a user subscription server receives a terminal activation request sent by an AS, sending the terminal activation request to a mobility management network element; and the user subscription server sends a terminal activation request to the mobility management network element according to the stored temporary identifier allocated to the terminal by the network.
The preferred embodiments will be described below with reference to the accompanying drawings.
Fig. 9 is a flowchart of activating a terminal by an AS to a subscriber server according to an embodiment of the present invention, where AS, AS shown in fig. 9, issues a request for activating the terminal to a mobility management element (e.g., an MSC, an SGSN, or an MME) via the subscriber server (e.g., an HLR or an HSS), and the mobility management element issues an activation message to the terminal through an appropriate message (e.g., a downlink NAS message, a Paging message, etc.). And then, the terminal actively establishes IP communication with the AS. The process comprises the following steps:
step S902, AS sends the request of activating the terminal to the user signing server, wherein the request carries the service identification;
the service identifier is an identifier of an AS, and may also be an identifier of a service implemented by the AS.
Step S904, the user signing server searches for a proper mobility management network element and forwards the activation request to the mobility management network element;
step S906, the mobility management network element issues the activation request to the terminal, and after the terminal receives the activation request, the terminal can know which service requires the terminal to be activated or which AS sends the activation request according to the service identifier, so that IP communication can be initiated to the AS purposefully.
The above steps can be applied to a terminal in the following case: terminal already attached to the network: in this case, the terminal may have been assigned an IP address, and may initiate IP communication directly to the AS. If the terminal does not allocate an IP address (if only GPRS attach and PDP context is not established), the terminal needs to initiate establishment of an IP bearer, and then initiates IP communication to the AS after the IP address is allocated; terminal not attached to network: in this case, the terminal is required to be able to listen to a broadcast message of a network even if the terminal is not attached to the network; the user subscription server is required to select a proper mobility management network element to send an activation request; the mobility management network element is required to be able to issue the activation request to the base station also in the case of no terminal context.
Fig. 10 is a flowchart of the AS activating the terminal to the subscriber server according to the embodiment of the present invention, where the terminal is attached to the network, and AS shown in fig. 10, the flowchart includes the following steps:
step S1001, AS sends an activation request to a user subscription server (for example, HLR or HSS), carrying a service identifier; the service identifier is carried to let the terminal know which service needs to activate the terminal, or which AS wants to activate the terminal and initiate communication. Such as: for MTC applications, the service identity indicates that it is the MTC application server that wishes to activate the terminal. For SUPL, the service identification indicates that it is a SUPL location Server (SLP) that wishes to activate the terminal.
Step S1002, after receiving an activation request of an AS, a subscriber subscription server queries a mobility management entity (for example, MSC, SGSN, or MME) currently registered by a terminal, and sends the activation request to the mobility management entity; in this step, the subscriber subscription server may use the existing accessibility check message, and carry an 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 may be newly introduced to require activation of the terminal.
Step S1003, 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 newly added message for activating the terminal.
Step S1004, after receiving the activation request, the terminal returns a response;
step S1005, the terminal initiates an IP communication to a specific AS according to the service identifier in the activation request.
In the above step, the mobility management network element sends an NAS message to the terminal to activate the terminal. The mobility management element may further send a Paging message to the terminal to activate the terminal, for example, the mobility management element may activate the terminal using an enhanced Paging message, where the enhanced Paging message carries the service identifier in step S1001.
Fig. 11 is a flowchart of the AS activating the terminal to the subscriber server in the case that the terminal is not attached to the network according to an embodiment of the present invention, and the flowchart is similar to the flowchart shown in fig. 10, but with the following differences:
in step S1102 (which is an added step compared to fig. 10), after the subscriber subscription server (e.g., HLR or HSS) receives the activation request of the AS, it needs to find a suitable mobility management network element (e.g., MSC, SGSN, or MME), the subscriber subscription server may be selected AS follows: for terminals that do not support roaming and have low mobility: selecting a proper mobility management network element according to the mobility range limited in the subscription; the user subscription server (HLR/HSS) stores the mobility management network element registered by the terminal last time, can set a proper timer, and clears the stored mobility management network element after the timer expires; then, within the validity time of the timer, the terminal is considered as still being possible within the coverage of the mobility management network element.
In step S1104, the mobility management network element activates the terminal using Paging, and the Paging parameter carries the service identifier and the ID of the terminal in step S1201. For terminals not attached to the network, it must be able to listen to the Paging message. When the terminal monitors the activation request from the Paging message, a network attachment process needs to be initiated, and then communication is actively initiated to the AS.
In the flow shown in fig. 11, the AS is generally aware of the application layer identity of the terminal, and the subscriber subscription server (HLR/HSS) identifies a terminal by the IMSI. Although the subscriber subscription server (HLR/HSS) may establish a mapping relationship between the application layer identifier of the terminal and the IMSI, at present, the Paging message does not support the application layer identifier, so that the terminal ID carried in the Paging message issued by the mobility management element (MSC/SGSN/MME) needs to use the IMSI. This approach exposes the IMSI to the network, greatly increasing insecurity.
To address the security threat posed by the procedure shown in fig. 11, when a terminal detaches from the network, a mobility management network element (e.g., MSC, SGSN, or MME) saves the temporary identity (e.g., TMSI in the CS domain, P-TMSI in the GPRS domain, GUTI in the EPS domain) assigned to the terminal to a subscriber subscription server (HLR/HSS), so that the saved terminal temporary identity can be used by a subsequent Paging. Further, the mobility management network element or the subscriber subscription server may also send the temporary identifier to the application server.
Fig. 12 is a flowchart of using the temporary identifier to activate the terminal from the AS to the subscriber server according to the embodiment of the present invention, and AS shown in fig. 12, the flowchart includes the following steps:
step S1201, the terminal executes the flow of detaching from the network;
step S1202, the mobility management network element sends a temporary identifier (for example, TMSI, P-TMSI or GUTI) allocated to the terminal by the network to the user subscription server through a notification message; wherein this step may include two variants: s1202a, the temporary identifier of the terminal allocated by the network is sent to the AS and stored; s1202b, the temporary identifier is stored only in the subscription server.
Step S1203, the AS initiates a request for activating the terminal, and the request carries a service identifier and a terminal ID;
in this step, if the temporary identifier assigned to the terminal by the aforementioned network is transmitted to the AS in step S1202, the AS can use the temporary identifier AS the terminal ID. Otherwise, the AS may use the application layer identifier, IMSI, of the terminal AS the terminal identifier.
Step S1204, after the subscriber server receives the activation request, look for the appropriate mobility management network element;
in this step, the subscriber subscription server replaces the terminal ID in the activation request with the temporary identifier of the terminal stored in step S1202 according to the mapping relationship.
Steps S1205 to S1209 may adopt the relevant steps shown in fig. 11, and are not described herein again.
For the terminal with no attached terminal and the terminal with the released attached single radio bearer, the Paging message Paging can be used to activate the terminal. In the flow shown in fig. 10, 11, 12, the Paging message is enhanced to carry the service identification. The method has a large modification cost on the wireless paging message. Fig. 13 is a flowchart of activating a terminal using a Paging message and sending a service identifier using an NAS message according to an embodiment of the present invention, and fig. 13 illustrates a manner of activating the terminal using a Paging message Paging, but the service identifier is downloaded by a mobility management network element to send the service identifier to the terminal via an NAS message after an NAS connection is established between a UE and a core network. By adopting the mode of fig. 13, the Paging message Paging does not need to be modified, and the upgrading cost of the system is reduced. As shown in fig. 13, the process includes the following steps:
step S1301, the mobility management network element receives a terminal activation request, wherein the terminal activation request carries a terminal identifier and a service identifier;
step S1302-S1305, the mobility management network element uses the existing Paging message Paging to page the terminal, and the terminal responds to the Paging message;
in step S1306, the unattached terminal performs a process of attaching to the network and requesting allocation of an IP. The attached terminal initiates a service request and establishes wireless and core network bearing;
step S1307, the mobility network element issues 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;
step S1308, the terminal actively establishes IP communication with the application server.
It should be noted that in the scheme of activating the terminal in the second preferred embodiment, the service identifier is required to be issued to the terminal, so as to prompt the terminal to actively establish communication with the server. However, for terminals that are 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, wherein the service identifier can not be carried in the activation request; when the terminal receives the activation request, it always tries to communicate with the AS unconditionally.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, or they may be separately fabricated into various integrated circuit modules, or multiple modules or steps thereof may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (14)

1. A method for activating a terminal, comprising:
a user signing server receives a request message of activating a terminal from an application server, wherein the request message carries an identifier of the terminal;
the user signing server sends a request message for activating the terminal to a mobility management network element, wherein the request message carries the identifier of the terminal;
and the mobility management network element sends a message for activating the terminal to the terminal.
2. The method of claim 1, wherein sending, by the mobility management network element, the message to the terminal for activating the terminal comprises:
the mobility management network element sends a Paging message to page the terminal;
and after receiving a response message which is sent by the terminal and responds to the paging message, the mobility management network element sends an NAS message to the terminal, wherein the NAS message carries a service identifier corresponding to the application server.
3. The method of claim 1,
the request message from the activation terminal of the application server received by the user signing server also carries a service identifier corresponding to the application server;
the request message for activating the terminal sent by the user subscription server to the mobility management network element also carries the service identifier;
and the message which is sent to the terminal by the mobility management network element and used for activating the terminal also carries the service identifier.
4. The method of claim 3, wherein the sending, by the subscriber subscription server, the request message for activating the terminal to the mobility management network element comprises:
and under the condition that the terminal is attached to the network, the user subscription server sends a request message for activating the terminal to a mobility management network element which is currently registered by the terminal.
5. The method according to claim 3 or 4, wherein the sending, by the mobility management network element, the message for activating the terminal to the terminal comprises:
and the mobility management network element sends a non-access stratum (NAS) message or a Paging message to the terminal according to the identifier of the terminal, wherein the NAS message or the Paging message is used for activating the terminal.
6. The method of claim 3, wherein the sending, by the subscriber subscription server, the request message for activating the terminal to the mobility management network element comprises:
and under the condition that the terminal is not attached to the network, the user subscription server selects a mobility management network element and sends a request message for activating the terminal to the selected mobility management network element.
7. The method of claim 6, wherein the selecting the mobility management network element by the subscriber subscription server comprises:
the user signing server selects a mobility management network element according to the service attribute signed by the terminal; or,
and the user subscription server selects the mobility management network element registered by the terminal last time as the mobility management network element for sending the request message for activating the terminal.
8. The method according to claim 3 or 7, wherein the sending, by the mobility management network element, the message for activating the terminal to the terminal comprises:
and the mobility management network element sends a broadcast message, wherein the broadcast message also carries the identifier of the terminal.
9. The method of claim 8, wherein the broadcast message is a Paging message or a system broadcast message.
10. The method of claim 8, further comprising, after the mobility management network element sends the broadcast message:
and the terminal is attached to a network after monitoring the broadcast message.
11. The method according to claim 1 or 3, wherein the subscriber subscription server sends a request message for activating the terminal to a mobility management network element, wherein the request message is further used for inquiring whether the terminal is reachable.
12. The method according to claim 1 or 3,
and the user subscription server sends a request message for activating the terminal to a mobility management network element, wherein the request message carries a temporary identifier of the terminal, and the mobility management network element sends the temporary identifier to the user subscription server when the terminal is detached from the network.
13. The method of claim 12,
under the condition that the application server stores the temporary identifier of the terminal, the user signing server receives a request message from the application server for activating the terminal, wherein the request message carries the temporary identifier of the terminal and the service identifier;
and under the condition that the application server does not store the temporary identifier of the terminal, the user signing server receives a request message from the application server for activating the terminal, wherein 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.
14. An activation terminal system comprising: a subscriber subscription server, a mobility management network element and an application server, characterized in that,
the application server is used for sending a request message for activating the terminal to the user signing server, wherein the request message carries the identifier of the terminal;
the user subscription server is used for sending a request message for activating the terminal to the mobility management network element, wherein the request message carries the identifier of the terminal;
the mobility management network element is configured to send a message for activating the terminal to the terminal.
CN201610258131.9A 2011-01-21 2011-01-21 Terminal state acquisition method, system, terminal activation method and system Pending CN105828321A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201610258131.9A CN105828321A (en) 2011-01-21 2011-01-21 Terminal state acquisition method, system, terminal activation method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201610258131.9A CN105828321A (en) 2011-01-21 2011-01-21 Terminal state acquisition method, system, terminal activation method and system

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
CN201110024174.8A Division CN102612021B (en) 2011-01-21 2011-01-21 SOT state of termination acquisition methods, activated terminals method and system

Publications (1)

Publication Number Publication Date
CN105828321A true CN105828321A (en) 2016-08-03

Family

ID=56527314

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201610258131.9A Pending CN105828321A (en) 2011-01-21 2011-01-21 Terminal state acquisition method, system, terminal activation method and system

Country Status (1)

Country Link
CN (1) CN105828321A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111163457A (en) * 2019-12-25 2020-05-15 中国联合网络通信集团有限公司 Processing method, device and storage medium for access terminal
CN115334464A (en) * 2022-07-18 2022-11-11 中国电信股份有限公司 Method and device for sending activation short message, electronic equipment and storage medium

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1736083A (en) * 2002-11-25 2006-02-15 诺基亚有限公司 Method and system for session management wherein a client session identifier is used
US20060291484A1 (en) * 2005-06-24 2006-12-28 Naqvi Shamim A Method of avoiding or minimizing cost of stateful connections between application servers and S-CSCF nodes in an IMS network with multiple domains
CN101588630A (en) * 2008-05-20 2009-11-25 华为技术有限公司 A kind of professional trigger method and device
CN101931931A (en) * 2009-06-25 2010-12-29 华为技术有限公司 Information process method, system and mobility management network element

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1736083A (en) * 2002-11-25 2006-02-15 诺基亚有限公司 Method and system for session management wherein a client session identifier is used
US20060291484A1 (en) * 2005-06-24 2006-12-28 Naqvi Shamim A Method of avoiding or minimizing cost of stateful connections between application servers and S-CSCF nodes in an IMS network with multiple domains
CN101588630A (en) * 2008-05-20 2009-11-25 华为技术有限公司 A kind of professional trigger method and device
CN101931931A (en) * 2009-06-25 2010-12-29 华为技术有限公司 Information process method, system and mobility management network element

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111163457A (en) * 2019-12-25 2020-05-15 中国联合网络通信集团有限公司 Processing method, device and storage medium for access terminal
CN111163457B (en) * 2019-12-25 2022-09-13 中国联合网络通信集团有限公司 Processing method, device and storage medium for access terminal
CN115334464A (en) * 2022-07-18 2022-11-11 中国电信股份有限公司 Method and device for sending activation short message, electronic equipment and storage medium

Similar Documents

Publication Publication Date Title
US8311042B2 (en) System and method for automatic detection and reporting of the mapping between device identity and network address in wireless networks
CN102244854B (en) The method of MTC group selection packet data network gateway and mobile management network element
CN102098655B (en) Method and system for controlling activation of ISR (Idle mode Signaling Reduction) and UE (user equipment)
US8886183B2 (en) Attaching to an access network
CN109417702B (en) Access control in a communication network comprising slices
US10708826B2 (en) Selection of a network element
CN102612021A (en) Terminal state obtaining method as well as method and system for activating terminal
US9237429B2 (en) Method and system for implementing packet switch domain short message service, and user equipment
KR20130031289A (en) Tmsi allocation device and method thereof, and network attachment and location area update methods in m2m communication
WO2008132213A1 (en) A system and method for utilizing a temporary user identity in a telecommunications system
CN102413453B (en) A kind of shared method and system of MTC device Subscriber Number
CN101001262B (en) IP address release method
WO2016162051A1 (en) Paging towards multiple devices in a group of devices
CN100455138C (en) Method for resharing service after kernal network fault recovery
US20240007983A1 (en) Method, device, and system for core network device re-allocation in wireless network
US20230370992A1 (en) Method, device, and system for core network device re-allocation in wireless network
CN102905369B (en) User equipment calling method and system when mobile management unit fails or restarts
CN105828321A (en) Terminal state acquisition method, system, terminal activation method and system
CN102369700B (en) Method, system and gateway equipment for service initiation
EP3163920B1 (en) Method for processing prose service authorization change, first network element and second network element
CN102177757B (en) Method, device and system for implementing registration
CN105430591B (en) Method and device for recovering device-to-device service and home subscriber server
US20240292298A1 (en) Method, device, and system for core network node re-allocation in wireless network

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20160803