WO2011054300A1 - Method and system for controling mtc terminal access - Google Patents

Abstract

A method and system for controlling Machine Type Communication (MTC) terminal are disclosed by the present invention. Wherein, the method includes the following steps: a mobility management network element reports the information of the MTC terminal, which requests to attach to the network or has attached to the network currently, to an access control network element (S601); the access control network element determines to refuse the MTC terminal access based on the MTC terminal information, and transmits an indication of refusing the access of the MTC terminal to the mobility management network element (S603); the mobility management network element receives the indication, and refuses the MTC terminal to access the network based on the indication (S605). By using the present invention, the access control to the MTC terminal can be realized by the access layer without increasing the complexity of the core network, thus reducing the cost of the network construction.

Description

 TECHNICAL FIELD The present invention relates to the field of communications, and in particular to an access control method and system for a machine type communication terminal. BACKGROUND OF THE INVENTION In the traditional mobile network service, human-to-human (Human To Human, 简称2Η) communication occupies a major position. In the Η2Η communication, since both parties involved are people with behavioral control capabilities, the conversation is actually controlled by human behavior. With the development of mobile network services and automation control technology, a new mobile communication method, namely Machine To Machine (M2M) communication, has appeared. In this communication mode, both sides of the communication are machine equipment. . The narrow definition of M2M is machine-to-machine communication, but in a broad sense, M2M includes networked applications and monthly services with the intelligent interaction of machine terminals as the core. M2M is based on intelligent machine terminals and uses multiple communication methods as access means. It can provide customers with information solutions to meet customers' information needs in monitoring, command and dispatch, data collection and measurement. M2M can be used in industrial applications (eg, traffic monitoring, alarm systems, marine rescue, vending machines, paying for cars, etc.), home applications (eg, automatic meter reading, temperature control, etc.) and personal applications (eg, life detection, far End diagnosis, etc.). The most fundamental difference between communication with people is that M2M communicates with the machine, and the communication behavior is automatically controlled, that is, the initiation of communication, the termination of communication, and the control of some access and restrictions in the communication process are automated. the behavior of. This behavior depends on the constraints and control of the behavior of the machine (ie, the terminal in the M2M communication) in the M2M communication. The behavior of the terminal in the M2M communication is constrained by the service subscription data, and the network is based on the service subscription data in the M2M communication. The terminal is managed.

M2M communication, also known as Machine Type Communication (MTC), is the most typical communication between the terminal and the application server. The terminal is called MTC User Equipment (MTC). UE), the application server is called MTC server (MTC Server) „ Under 2G/3G/LTE access, M2M communication mainly uses Packet Service (PS) network as the underlying bearer network. Implement the service layer communication between the MTC terminal and the MTC server News. FIG. 1 is a schematic diagram of an architecture of an M2M communication entity accessing an Evolved Packet System (EPS). In FIG. 1, the underlying bearer network includes: an evolved universal mobile communication system (Evolved Universal Terrestrial Radio Access Network, E-UTRAN for short), and a Mobility Management Entity (MME). Service Gateway (S-GW, or SGW for short), Packet Data Network Gateway (PDN GW, or P-GW, or PGW), Home Subscriber (Home Subscriber) Server, abbreviated as HSS), Policy and Charging Rules Function (PCRF) „ where the main network element of E-UTRAN is eNodeB (Evolved NodeB base station;). In Figure 1, The MME is responsible for the control plane, such as mobility management, non-access stratum signaling processing, and context management in user mobility management. The S-GW is an access gateway device connected to E-UTRAN, in E-UTRAN and The P-GW forwards data and is responsible for buffering paging waiting data. The P-GW is a border network of EPS and Packet Data Network (PDN). Responsible for the PDN access and forwarding of data between the EPS and the PDN; the PCRF is a policy and charging rule function entity, which is connected to the service network protocol (Internet Protocol, IP for short) through the receiving interface Rx. The service information, in addition, can be connected to the gateway device in the network through the Gx interface, and is responsible for initiating the establishment of the IP bearer, ensuring the quality of service (QoS) of the service data, and performing charging control. The HSS provides management of the subscriber's subscription data, and management of important context information accessed by the user to the network. In Figure 1, the MTC UE accesses the EPS network through the E-UTRAN (eNodeB), where the IP address is assigned. After that, an IP channel can be established between the MTC UE and the MTC Server to implement upper layer service communication with the MTC Server. The IP channel established between the MTC UE and the MTC Server is an IP channel that is also serialized, and its physical The path passes through: eNodeB, S-GW, and P-GW. Currently, one way to implement M2M communication is to establish a service layer interface on the IP channel between the MTC UE and the MTC Server. Proposed by the service layer interface protocol, MTC UE and MTC Server interactive service data, while, MTC Server also achieve control of the MTC UE through the service layer protocol. Figure 2 depicts the flow of M2M communication in this way, as shown in Figure 2, in which MTC

The UE accesses through the PS network, and establishing a communication connection with the MTC Server mainly includes the following steps: 5201. The MTC UE initiates an attach request to the MME.

5202. The MME receives the foregoing attach request, and sends a location update request to the HSS. In this step, the HSS downloads subscription data of the MTC UE to the MME, where the subscription data part for the M2M access control is included. S203, the MME sends the SGW/PGW Send a create request, request SGW/PGW to be MTC

The UE creates a suitable payload;

5204. If the PGW needs to obtain policy data from the PCC to establish a suitable bearer according to the PGW, the PGW and the PCC interact to obtain a PCC policy.

5205, the PGW creates a bearer for the MTC UE, and returns a create response. S206: The MME sends an attach response to the MTC UE. After step S206, the MTC UE is attached to the PS network, is assigned an IP address, and establishes a suitable payload. The registration of the business layer can be initiated to the MTC Server.

5207, the MTC UE initiates registration of the service layer to the MTC Server;

5208, the MTC Server accepts the registration of the MTC UE, and returns a registration response. S209: The subsequent MTC UE and the MTC Server exchange data through the service layer protocol. Through the process shown in Figure 2, the MTC UE accesses the PS network and establishes an IP connection with the MTC Server, so that service layer communication between the subsequent and the MTC Server can be realized. In some cases, the service layer needs to restrict access to the MTC terminal device, that is, it is allowed to access only under specified conditions, and the access of the MTC terminal device is denied if the condition is not allowed. For example, in some M2M services, due to the theft of the MTC device and the theft of the SIM card, since the International Mobile Subscriber Identification Number (IMSI) exists on the SIM card, it is the disclosure of the MTC UE. Identity, assigned by the operator. The International Mobile Equipment Identity (IMEI) exists in the terminal equipment provider. If the MTC terminal equipment is limited to use only the specific IMSI and IMEI to access the network, it can be judged when accessing the network. If the IMSI and the IMEI pair do not match, the MTC device or the SIM card is stolen and the access of the MTC terminal device is denied. Or, in some M2M services, the MTC terminal is applied in a fixed location area beyond which the area will not be allowed to be used. Therefore, it is necessary to limit the access location of the MTC terminal device. If the access is in an unacceptable location area, or is moved to an unallowed location area after access, it is necessary to restrict access to the system. Or, in some M2M services, the MTC terminal is restricted from accessing the system within a specified time, and access to the system will not be allowed beyond this time. Therefore, the access time of the MTC terminal device is limited. If the access time is within an unallowable time period, or the access time exceeds the allowed time, it is required to restrict access to the system. Although the above-mentioned service management requirements can be controlled at the access layer, for example, under the E-UTRAN access, the MME controls, which requires the MME to perform various checks and checks for various management requirements. Judging, resulting in a huge increase in the complexity of the core network. SUMMARY OF THE INVENTION The present invention has been made in view of the problem in the prior art that an access control of an MTC terminal by an access layer is required to cause an increase in the complexity of the core network. To this end, the main object of the present invention is to provide an improved M2M terminal. The access control scheme to solve at least one of the above problems. In order to achieve the above object, according to an aspect of the present invention, an access control method of an MTC terminal is provided. The access control method of the MTC terminal according to the present invention includes: the mobility management network element reports to the access control network element information currently attached to the network or the MTC terminal currently attached to the network; the access control network element resides in the MTC terminal The information judgment does not allow the MTC terminal to access, and sends an indication to the mobility management network element to reject the access of the MTC terminal; the mobility management network element receives the indication, and refuses to access the network by the MTC terminal according to the indication. In order to achieve the above object, in another aspect of the present invention, an access control system for an MTC terminal is provided. The access control system of the MTC terminal according to the present invention includes: a user subscription data storage, a mobility management network element, and an access control network element. among them, The user is subscribed to the data storage for storing the subscription data of the MTC terminal in the system; the mobility management network element is connected to the user's subscription data storage, and is configured to receive the current request sent by the user's subscription data storage and attach to the network or is currently attached to the network. The subscription data of the MTC terminal of the network, and the information of the MTC terminal is provided to the access control network element; the access control network element is connected to the mobility management network element, and is used to determine whether the MTC terminal is allowed according to the information of the MTC terminal. And accessing, and not allowing the MTC terminal to access, sending an indication to the mobility management network element to reject the access of the MTC terminal, so that the mobility management network element rejects the MTC terminal from accessing the network. With the present invention, the access control network element of the service layer obtains the information of the MTC terminal through the mobility management network element, and determines whether to allow the MTC terminal to access according to the information of the MTC terminal, so that the MTC terminal can be connected through the service layer. The control is implemented to solve the problem that the complexity of the core network is increased due to the access control of the access layer to the MTC terminal in the prior art, thereby reducing the cost of network construction. BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are set to illustrate,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,, In the accompanying drawings: FIG. 1 is a schematic diagram of an architecture of an M2M communication entity accessing an EPS in a related art; FIG. 2 is a schematic diagram of a related art in which an MTC UE accesses through a PS network and establishes a communication connection with an MTC server; 3 is a schematic structural diagram of an access control system of an MTC UE according to an embodiment of the present invention; FIG. 4 is a structural diagram of an MTC UE accessing an M2M communication through an EPS system according to an embodiment of the present invention; The MTC UE of the embodiment of the present invention accesses the architecture diagram of the M2M communication through the GPRS system; FIG. 6 is a flowchart of the access control method of the MTC terminal according to the embodiment of the present invention; FIG. 7 is a flowchart of information about an MME actively transmitting to an MTC UE on an MTC Server according to an embodiment of the present invention; FIG. 8 is another MME actively reporting an MTC UE to an MTC Server according to an embodiment of the present invention; FIG. 9 is a flowchart of the MTC Server sending an inquiry request to the MME to obtain the information of the MTC UE by using the MTC GW according to the embodiment of the present invention; FIG. 10 is a flowchart of the MTC server subscribing the MTC UE to the MME according to the embodiment of the present invention; A flowchart of a related event to obtain information of the MTC UE; FIG. 11 is a method for acquiring an MTC UE, an address of an MTC Server that is a monthly service of the MTC UE, and an MTC UE for the MTC GW in the embodiment of the present invention; A flow chart of the correspondence between the addresses of the allocated MMEs; FIG. 12 is a flowchart of the method for acquiring the corresponding relationship by the MTC GW in the embodiment of the present invention; FIG. 13 is a third method for using the MTC GW in the embodiment of the present invention. FIG. 14 is a flowchart of Embodiment 1 of the method according to the present invention; FIG. 15 is a flowchart of Embodiment 2 of the method according to the present invention. The embodiment of the present invention provides a flexible access control requirement for the MTC terminal to access the network, and at the same time minimizes the complex transformation of the core network caused by the support of the access restriction service. An improved access control scheme for an MTC terminal. In the embodiment of the present invention, it is considered that the MTC Server may not be a network entity managed by an operator, and may be deployed in a core network. Therefore, in consideration of access security when the MTC Server accesses the core network, the present invention is implemented. For example, the MTC gateway (MTC GW) is added on the core network side, so that all MTC Server accesses pass through the MTC gateway, and the MTC gateway can be hidden by the internal network topology structure, and the MTC is hidden.

The server accesses the authentication and other means to implement the security guarantee for the MTC Server to access the core network. In addition, in the embodiment of the present invention, the information of the underlying access layer of the MTC terminal is obtained by the service layer (the MTC server or the newly added MTC gateway) through the mobility management network element, and then the obtained MTC is obtained. The information of the terminal controls the access of the MTC terminal. The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. 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. System Embodiment According to an embodiment of the present invention, a control system for an MTC terminal is provided. 3 is a schematic structural diagram of an access control system of an MTC terminal according to an embodiment of the present invention. As shown in FIG. 3, an access control system of an MTC terminal according to an embodiment of the present invention mainly includes: a user subscription data storage 1. The mobility management network element 3 and the access control network element 5. The above various network elements are described below. The user subscription data storage 1 is configured to store the subscription data of the MTC terminal in the system; the mobility management network element 3 is connected to the user subscription data storage 1 and is configured to receive the current request sent by the user subscription data storage 1 to be attached to The network or the subscription data of the MTC terminal currently attached to the network, and provides the information of the MTC terminal to the access control network element 5; in a specific application, when the MTC UE requests to attach to the network, the MTC UE ^! The mobility management network element 3 sends an attach request, and after receiving the attach request of the MTC UE, the mobility management network element 3 sends a location update request to the user subscription data storage 1, and the user subscription data storage 1 receives the location update request. Then, the subscription data of the MTC UE is delivered to the mobility management network element 3, and the mobility management network element 3 receives and stores the subscription data. And, after the MTC UE is attached to the network, if the subscription data of the MTC UE changes, the user subscription data storage 1 sends the updated subscription data of the MTC UE to the mobility management network element 3. The access control network element 5 is connected to the mobility management network element 3, and is configured to determine whether to allow the MTC terminal to access according to the information of the MTC terminal provided by the mobility management network element 3, and not allow the MTC terminal to be connected. In the case of incoming, an indication to reject the access of the MTC terminal is sent to the mobility management network element 3, so that the mobility management network element 3 rejects the access of the MTC terminal to the network. After receiving the indication from the MTC server 5, if the current MTC terminal requests to attach to the network, the mobility management network element 3 rejects the attach request of the MTC terminal, and returns a reject attachment response to the MTC terminal; if the current MTC terminal has When attached to the network, the mobility management network element 3 initiates a detach process to attach the MTC terminal. In the specific implementation process, the access control network element 5 may be an MTC gateway newly added on the core network side in the embodiment of the present invention, where the MTC gateway is connected between the MTC server and the mobility management network element, except for the MTC gateway. And performing security verification on the MTC server according to a predetermined condition of the locally stored MTC UE access or a predetermined condition of the MTC UE access obtained from the core network, and an MTC gateway may perform Serving multiple MTC servers. Alternatively, the access control network element 5 may also be an MTC server, and the MTC server controls access of the MTC terminal according to a predetermined condition of the locally stored MTC UE access or a predetermined condition of the MTC UE access obtained from the core network. And, an MTC gateway is connected between the MTC server and the mobility management network element 3. The MTC gateway is mainly used to forward data between the MTC server and the mobility management network element 3, and may also need to perform necessary protocol conversion. Working, and, the MTC gateway also performs security verification on the MTC server. For example, when the MTC UE accesses the E-UTRAN network, the user subscription data storage 1 is an HSS, and the mobility management network element 3 is an MME. When the MTC UE accesses the GERAN/UTRAN network, the user subscription data storage 1 is The HLR, the mobility management network element 3 is an SGSN. The above system provided by the embodiment of the present invention will be described below by way of specific embodiments. System Embodiment 1 In this embodiment, an MTC UE uses an EPS system to implement access (that is, an MTC UE accesses an E-UTRAN network) as an example. FIG. 4 is a structural diagram of the MTC UE accessing the M2M communication through the EPS system in the embodiment. As shown in FIG. 4, in the embodiment, between the MTC gateway and the MME, and between the MTC gateway and the MTC server, The connection is such that the MTC server obtains information of the underlying access layer of the MTC UE to determine the behavior of the MTC UE. As shown in Figure 4, in the architecture diagram, the MTC GW is deployed in the core network. The MTC server may be deployed outside the carrier's core network or in the core network. An MTC GW can work on multiple MTC Servers on a monthly basis. In the architecture diagram, the MTC GW and the MME establish an interface. For the convenience of description, in this embodiment, the interface is referred to as an M2M-MME. Through the interface, the MTC GW can query the MME for information about a certain MTC UE, for example, the subscription data of the MTC UE and the current bit of the MTC UE. The area i or the current state of the MTC UE, etc.; or, through the interface, the MTC GW may subscribe to the MME for an access layer load event associated with a certain MTC UE, for example, the MTC UE attaches to the PS network, the MTC UE The MME is detached from the PS network, and the MTC UE has an event such as a location move in the PS network. Alternatively, the MME can actively notify the MTC GW of the event of the underlying access layer associated with a certain MTC UE. And after the MTC GW acquires the information of the certain MTC UE or the underlying access layer event, the MTC GW may obtain the reservation according to the MTC UE stored in the MTC GW or the subscription of the MTC UE obtained from the core network. The condition determines whether the access of the MTC UE is allowed. If the MTC UE is not allowed to access, the MME sends a reject message to reject the access of the MTC UE. Or, in the architecture, the MTC GW acts as an intermediary (similar to the proxy) for communication between the MTC Server and the MME, and accepts the query of the MTC UE information performed by the MTC Server, and the subscription of the access layer event related to the MTC UE, Forward the request to the MME. Before forwarding the request, the MTC GW needs to perform security detection on the MTC Server. If the detection passes, the request is forwarded. In the process of forwarding the request, the MTC GW may need to perform necessary protocol conversion work. At the same time, the MTC GW forwards the information of the MTC UE sent by the MME to the MTC Server. And after obtaining the information about the MTC UE, the MTC server may determine whether to allow the MTC UE according to the predetermined condition of the locally stored MTC UE access or the predetermined condition of the MTC UE access obtained from the core network. In the case of determining that the MTC UE is not allowed to access, the MTC GW sends a reject message to the MME to reject the access of the MTC UE. Optionally, in the architecture, the MTC GW can also establish an interface with the HSS. For convenience of description, in this embodiment, the interface is referred to as an M2M-HSS. Through the interface, the MTC GW can query the subscription data of the MTC UE from the HSS; or, through the interface, the MTC GW can query from the HSS to the address of the MME allocated for the MTC UE. Alternatively, if the M2M-HSS interface is not established between the MTC GW and the HSS, the MTC GW may obtain the subscription data of the MTC UE by using the M2M-MME interface with the MME. The MTC GW can actively query the MME for the subscription data of the MTC UE, and the MME can also actively send the subscription data of the MTC UE to the MTC GW. System embodiment two This embodiment is described by taking an example in which an MTC UE accesses a GERAN/UTRAN network. FIG. 5 is a structural diagram of the M2M communication in the METH UE through the GERAN/UTRAN network access in the embodiment. As shown in FIG. 5, the embodiment is basically similar to the system embodiment 1 described above, except that the GERAN/UTRAN network is used. The SGSN in the network is equivalent to the MME in the E-UTRAN network, and is used for the access control and mobility management functions of the PS domain, and the Gateway GPRS Support Node (GGSN) in the GERAN/UTRAN network is equivalent to the E. - SGW and PGW in the UTRAN network, the HLR in GERAN/UTRAN is equivalent to the HSS in the E-UTRAN network. The functions of the specific connections and the functions of the network elements are similar to those of the above-mentioned system embodiment 1, and will not be described again. Method Embodiments According to an embodiment of the present invention, an access control method for an MTC UE is further provided, and the method may be implemented by the foregoing system provided according to an embodiment of the present invention. FIG. 6 is a flowchart of an access control method of an MTC UE according to an embodiment of the present invention. As shown in FIG. 6, an access control method of an MTC UE according to an embodiment of the present invention mainly includes the following steps: Step S601 - Step S605): Step S601: The mobility management network element reports to the access control network element information currently attached to the network or the MTC terminal currently attached to the network; Step S603: The access control network element resides in the MTC terminal The information judgment does not allow the MTC terminal to access, and sends an indication to the mobility management network element to reject the access of the MTC terminal. Step S605: The mobility management network element receives the indication, and according to the indication, rejects the MTC terminal from accessing the network. The processing of each step described above will be further described below. (1) Step S601 In the specific implementation process, the information of the mobility management network element to the MTC server on the MTC server includes, but is not limited to, the following three methods:

(1) The mobility management network element actively reports to the access control network element. For example, the mobility management network element may actively notify the access control network element when an access layer event of an MTC UE occurs, or the mobility management network element actively sends an access control network element when the MTC UE requests attachment. The information of the MTC UE is reported.

(2) The access control network element queries the mobility management network element. For example, the access control network element may send a query request for querying the information of the MTC UE to the mobility management network element, and the mobility management network element receives the access control network. After the query request of the element, the information of the MTC UE corresponding to the access control network element is 4。.

(3) A related event notification that the access control network element subscribes to the mobility management network element to subscribe to the MTC UE. For example, the access control network element may subscribe to the mobility management network element for an access layer event related to a certain MTC UE, mobility. The management network element actively informs the access control network element when the subscribed access layer event occurs, and the notification includes the information of the corresponding MTC UE. In the specific implementation process, the foregoing access control network element may be an MTC gateway or an MTC server. The following uses the MTC server as an example to describe three methods for the access control network element to acquire the information of the MTC UE. ( Α ) The mobility management network element actively sends the access control network element. For example, the mobility management network element may actively send an event notification to the MTC gateway when an access layer event of an MTC UE occurs, or mobility. After receiving the attach request sent by the MTC UE, the management network element may actively report the information of the MTC UE to the MTC gateway; after receiving the event notification or the reported information of the MTC UE, the MTC gateway notifies or reports the MTC UE information of the event. Send to the MTC server. Specifically, when the mobility management network element actively performs the information of the MTC UE, the mobility management network element actively sends the MTC GW to the MTC server according to the indication carried in the MTC UE obtained from the user subscription data storage. MTC UE information. Specifically, the mobility management network element obtains the subscription data of the MTC UE from the user subscription data storage, but is not limited to: indicating the indication information that the mobility management network element reports the MTC UE to the MTC server (specifically, indicating the timing including the reporting, Information such as reported parameters), information of the MTC Server serving the MTC UE. In a specific implementation process, the mobility management network element may actively send the MTC UE information to the MTC server through the MTC GW when the MTC UE initiates the attach request, or may be in the MTC UE after the MTC UE attaches to the network. When the relevant access layer event occurs, it actively passes the MTC. The GW notifies the event notification on the MTC Server, and carries the current information of the MTC UE in the event notification. The following takes the mobility management network element as the MME as an example, and describes the flow of reporting the MME to the MTC Server at these two timings.

(1) When the MTC UE initiates the attach request, the MME actively reports the information of the MTC UE to the MTC server through the MTC GW. FIG. 7 is that, in this case, the MME actively sends the information of the MTC UE to the MTC GW through the MTC GW. Flowchart, as shown in FIG. 7, when the MTC UE initiates an attach request, the information that the MME actively sends to the MTC server through the MTC GW mainly includes the following steps:

S701. The MTC UE initiates an attach request to the MME. S702: The MME sends a location update request to the HSS.

5703. The HSS returns a location update response to the MME, where the update response carries the subscription data of the MTC UE, where the subscription data includes: indication information indicating that the MME reports the information of the MTC UE to the MTC server, and is the monthly information of the MTC UE. Information about the MTC Server (specifically, the information may be the IP address of the MTC Server, or may be the information such as the monthly service identifier of the MTC Server);

S704, the MME parses the address of the MTC server according to the information of the MTC server serving the MTC UE.

S705, the MME sends the information of the foregoing MTC UE to the MTC GW, and the information of the MTC server that is parsed in the step S704 is further included in the information of the MME to the MTC GW. S706, the information of the MTC UE is used by the MTC GW. Send to the MTC corresponding to the above address

Server„

(2) After the MTC UE is attached to the network, the MME actively reports the information of the MTC UE to the MTC Server through the MTC GW. FIG. 8 is a flow of the information that the MME actively sends the MTC UE to the MTC Server through the MTC GW. As shown in FIG. 8, after the MTC UE is attached to the network, the information that the MME actively sends to the MTC server through the MTC GW mainly includes the following steps:

S801. The MTC UE is attached to the PS network. In the process of attaching the MTC UE to the PS network, the MME obtains the subscription data of the MTC UE from the HSS, including the subscription data for the M2M service part. The M2M service subscription data includes an address of the MTC server serving the MTC UE (which may also be an identifier information of the MTC server), and an indication that the MME is requested to actively forward to the MTC Server a predetermined event related to the MTC UE. The requesting MME sends an event notification to the MTC server when the MTC UE generates a predetermined event, where the predetermined event is an access layer event related to the MTC UE, specifically, the foregoing predetermined event includes but is not limited to one of the following Or any combination thereof:

(1) The subscription data of the MTC UE changes. After the HSS changes the subscription data of the MTC UE, the HSS needs to re-issue the new subscription data to the MME. After receiving the new subscription data, the MME may notify the MTC Server that the subscription data has Change, or directly send new subscription data to the MTC Server;

(2) The MTC UE has a large state change; for example, the MTC UE is attached to the network, the MTC UE is detached from the network, the MTC UE is changed from the connected state to the idle state, and the MTC UE is changed from the idle state to the connected state;

(3) The change of the location area i of the MTC UE; for example, the location movement of the MTC UE, etc., when the location movement of the MTC UE occurs, the MTC UE sends a location update message to the MME, so that the MME can capture the MTC UE. Position movement has occurred;

(4) The network change of the MTC UE; for example, the MTC UE has a handover of the base station and the network. In this case, the MTC UE sends a handover message to the MME, so that the MME can capture the network change event of the MTC.

(5) The relationship between the IMSI and the IMEI used by the MTC UE changes; for example, the pairing relationship between the IMSI and the IMEI that the MTC UE should use is specified in the subscription data, but the current MTC UE replaces the terminal, such as changing the SIM card to the non- On the MTC terminal. In this case, the MTC Server needs to obtain the IMSI and IMEI pairing used by the MTC UE.

5802, the foregoing predetermined event, that is, an access layer event related to the MTC UE occurs;

5803, the MME actively notifies the MTC GW of the occurrence of the predetermined event. Specifically, the event notification sent by the MME to the MTC GW includes current information of the MTC UE. 5804. The MTC GW obtains, according to the identifier of the pre-acquired MTC UE, the address of the mobility management network element allocated for the MTC UE, and the address of the MTC server that is used for the MTC UE, to obtain the service for the MTC UE. The address of the MTC Server;

5805. The MTC GW sends the above event notification to the MTC Server. It should be noted that, in the process shown in FIG. 8, the access layer event of S802 may occur in step S801. For example, if the event is an attach event, the MME should notify the MTC Server when the MTC UE attaches to the network. Send an event notification. Specifically, in the foregoing processes of FIG. 7 and FIG. 8 , the information of the MME to the MTC UE on the MTC Server includes, but is not limited to, one of the following or any combination thereof: A) the current service of the MTC UE obtained by the MME from the HSS. Contract data

B) IMSI, IMEI used by the MTC UE; where the IMSI used by the MTC is MTC

The UE is carried in the attach message sent when the UE is attached to the network, and the IMEI may be provided by the MTC UE to the network when it is attached, or may be obtained by the network to the MTC UE according to the need; C) The MTC UE is in the MME. The context information, for example, the current location area i of the MTC UE and/or the current state of the MTC UE; wherein, the current location area of the MTC UE may be: a Tracking Area (TA) of the MTC UE, The current Cell cell of the MTC UE, and the current state of the MTC UE may be one of an attached state, a detached state, a connected state, an idle state, and the like. D) the current mobility event of the MTC UE, for example, the MTC UE is attached to the network,

The MTC UE detaches from the network, the MTC UE location update, the MTC UE base station handover, the MTC UE network handover, and the like.

(B) The access control network element queries the mobility management network element specifically. After the MTC UE is attached to the network, the MTC Server sends a query request to the mobility management network element through the MTC GW, requesting to query the information of the MTC UE, and moving. After receiving the query request, the MTU GW reports the information of the MTC UE to the MTC GW, and the MTC GW sends the MTC UE information to the MTC Server. After the MTC GW receives the query request sent by the MTC server, the MTC GW needs to perform security verification on the MTC server. Specifically, the MTC GW can obtain information about the MTC Server that the core network is allowed to access. For example, the service identifier, the IP address, and the like, determining whether the MTC server is within the range of the MTC server that is allowed to access, and if yes, continuing to process the query request, according to the identifier of the pre-acquired MTC UE, being the MTC UE Obtaining, by the address of the allocated mobility management network element and the address of the MTC server address of the MTC UE, obtaining the address of the mobility management network element allocated for the MTC UE, and forwarding the query request to the Mobility management network element; otherwise, the MTC GW rejects the query request. Specifically, the E-UTARN network is taken as an example. FIG. 9 is a flowchart of the MTC Server sending an inquiry request to the MME through the MTC GW to obtain information about the access layer of the MTC UE. As shown in FIG. 9, the MTC Server passes the MTC GW. Sending a query request to the MME, and obtaining the information of the MTC UE mainly includes the following steps:

5901, the MTC UE is attached to the PS network;

5902, the MTC UE initiates a service layer registration with the MTC Server; S903, after the MTC UE registers with the MTC Server, if the MTC Server is for the purpose of service control, the MTC UE determines that the current information of the MTC UE needs to be queried (mainly refers to the access layer information). In this step, the MTC Server may need to obtain information about the MTC UE for a variety of possible purposes, for example:

The MTC Server wants to know the IMSI and IMEI conditions used by the MTC UE to check whether the SIM card provided by the MTC UE is stolen, that is, whether the IMSI or IMEI binding relationship is normal; or

The MTC Server needs to know the current location information (such as the TA area, the cell cell, and the like) of the MTC UE to determine whether the MTC UE accesses in the location area that is not allowed, or moves to the location area that is not allowed; S904, The MTC Server sends a query request to the MTC GW to query the information of the MTC UE, where the query request may carry the identifier of the MTC UE and the address of the MTC Server;

S905: The MTC GW receives the foregoing query request, performs legal authentication on the MTC Server, and determines that the MTC Server is legal. 5906. The MTC GW acquires, according to the identifier of the pre-acquired MTC UE, the address of the MME allocated to the MTC UE, and the address of the MTC server that is used for the MTC UE, the MME allocated for the MTC UE. address;

5907, the MTC GW forwards the foregoing query request to the MME; S908, the MME returns the current information of the MTC UE to the MTC GW according to the current context of the MTC UE, and the MTC GW sends the current information of the MTC UE to the MTC Server. Through the steps S903-S908, the MTC Server obtains the current information of the MTC UE from the MME through the MTC GW, so that the current behavior of the MTC UE can be determined according to the current information of the MTC UE, and the behavior of the MTC UE can be further controlled. . Specifically, in the foregoing step, the information of the MTC UE requested by the MTC Server to the MME includes, but is not limited to, one of the following or any combination thereof:

A) The current service subscription data of the MTC UE obtained by the MME from the HSS.

B) IMSI, IMEI used by the MTC UE; specifically, the IMSI used by the MTC UE is required to be carried in the attach message when the MTC UE attaches to the network, and the MME can obtain the IMSI used by the MTC UE from the attach message, and The IMEI may be provided to the network by the MTC UE when it is attached, or may be obtained by the network querying the MTC UE according to the need.

C) Context information of the MTC UE on the MME, for example, the current location area of the MTC UE (the location areas may be: TA area, Cell) and/or the current status of the MTC UE (eg:

The MTC UE is currently attached, connected, idle, etc.). (C) The access control network element subscribes to the relevant event port of the MTC UE to the mobility management network element. Due to the need of service management, the MTC Server needs to know the event sent by the underlying access layer in time (for example, the MTC UE attaches and detaches from the network) , location change, etc., and make corresponding decisions based on these events to control the behavior of the MTC UE. Therefore, the MTC Server can subscribe to these access layer events to the mobility management network element through the MTC GW, and the mobility management network element When the corresponding access layer event occurs, the MTC GW reports the event notification to the MTC server in time, and the event notification carries the current information of the MTC UE. In this case, the processing of the MTC Server is basically the same as the processing of the above (B). After the MTC Server sends a query request for the relevant event of the subscription to the MTC UE to the MTC GW, the MTC GW The MTC server needs to perform security verification. After the authentication is valid, the query request is forwarded to the mobility management network element allocated to the MTC UE. The specific method is the same as the above, and is not mentioned here. Moreover, before forwarding, the MTC GW also needs to obtain the address of the mobility management network element allocated for the MTC UE. The difference from the above (B) is that the query request sent by the MTC Server to the mobility management network element through the MTC GW is related to the event for subscribing to the MTC UE, that is, requesting the mobility management network element to access in connection with the MTC UE. When a layer event occurs, the MTC GW notifies the event to the MTC Server. FIG. 10 is a flow chart of the MTC server subscribing to the MME to obtain the information about the MTC UE by using the E-UTRAN network as an example. The information about obtaining the MTC UE mainly includes the following steps:

5101, the MTC UE is attached to the PS network;

5102: The MTC UE initiates a service layer registration with the MTC Server; S103, after the MTC UE registers with the MTC Server, according to the needs of the service management, the MTC

The Server needs to know the events related to the MTC UE that occur in the underlying access layer in time, and therefore, it is determined that the MME subscribes to these events;

5104. The MTC Server sends a query request for the access layer event related to the MTC UE to the MTC GW. It is clear that the MTC Server can subscribe to only one or one type of access layer event at a time, or can subscribe to multiple or more at a time. Class access layer events.

5105, the MTC GW receives the above query request, and performs a security-risk certificate on the MTC Server, and the insurance card is legal;

The MTC GW obtains the MME allocated for the MTC UE according to the correspondence between the identifier of the MTC UE, the address of the MME allocated for the MTC UE, and the address of the MTC server for the MTC UE. Address

5107. The MTC GW forwards the foregoing query request to the MME, and subscribes to the MME for an access layer event related to the MTC UE. 5108, an access layer event corresponding to the subscription subscribed by the MTC server occurs;

5109. After the access layer event occurs, the MME actively sends an event notification to the MTC GW to the event of the access layer event, where the event notification carries the current related information of the MTC UE.

5110. The MTC GW sends the received event notification to the MTC Server. In the process shown in FIG. 10, the access layer event related to the MTC UE subscribed by the MTC server may be one of the following events or thousands:

A) The change of the subscription data of the MTC UE; after the HSS changes the subscription data of the MTC UE, the HSS needs to re-issue the new subscription data to the MME, and after receiving the new subscription data, the MME may notify the MTC Server that the subscription data has changed. , or directly send new contract data to the MTC Server;

B) the state change of the MTC UE; for example, the MTC UE is attached to the network, detached from the network, changed from the connected state to the idle state, changed from the idle state to the connected state, and the like;

C) a change in the location area of the MTC UE; for example, a location change or the like occurs in the MTC UE, a location update message is sent to the MME, etc.; D) a network change of the MTC UE; for example, a handover of the base station and the network occurs in the MTC UE,

The MME sends a handover message or the like. In the specific implementation process, the methods for obtaining the MTC UE described in (B) and (C) above may be used alone or in combination. For example, in the foregoing process shown in FIG. 9, the information of the MTC UE that the MTC Server requests to query in the step S aggregation S903 may further include: D) a mobility event that occurs in the MTC UE, for example, the MTC UE is attached to Network, MTC

The UE detaches from the network, the MTC UE location update, the MTC UE base station handover, the MTC UE network handover, and the like. Then, when the event occurs, the MME sends an event notification to the MTC server through the MTC GW, so that the MTC server knows the current event of the MTC UE and the current information of the MTC UE.

The MTC Server may further perform the step S103 in FIG. 10 and the subsequent steps after acquiring the current information of the MTC UE after step S908 of FIG. 9, or in the above step S902. Then, step S903 and step S103 are simultaneously performed to subscribe to the related events of the MTC UE, so that when these events occur, the event notifications are notified by the event notification, and the current information of the MTC UE is further acquired. The MTC Server may obtain the information of the MTC UE from the MME through the MTC GW, and may be the subscription data of the MTC UE, the current state of the MTC UE, the location area information of the MTC UE, and the like. The method for obtaining the information of the MTC UE may be that the MTC server actively queries the MME through the MTC GW, or after the MTC server subscribes the related event to the MME through the MTC GW, the MME notifies the MTC Server when the event occurs, or may be The MME actively notifies the access layer event to the MTC Server through the MTC GW according to the indication in the subscription data of the MTC UE. When the MTC Server obtains the information of the MTC UE from the underlying access layer, the MTC Server can further determine the behavior of the MTC UE by using the information, and make a decision according to the service to control the behavior of the MTC UE (for example, when the MTC UE is in the non- When the access time is allowed, the MTC Server may request to attach the MTC UE; when the MTC UE moves to the non-allowed area, the MTC Server may request to attach the MTC UE, etc.). In the above method, in order to implement data interaction between the MTC Server and the mobility management network element, the MTC GW needs to acquire and save the identifier of the MTC UE, the address of the mobility management network element allocated for the MTC UE, and the MTC UE. The corresponding relationship between the addresses of the MTC servers of the monthly service. In the specific implementation process, the MTC Server obtains the corresponding relationship, including but not limited to the following three methods: Method 1: The MTC Server sends the carried message to the MTC GW for the MTC UE. The registration notification message of the identification information of the assigned mobility management network element; specifically, after the MTC UE sends the registration request to the MTC Server after the MTC UE is attached to the network, the mobility request is allocated to the MTC UE in the registration request. After receiving the registration request, the MTC Server sends a registration notification message to the MTC GW, where the message carries the identification information of the mobility management network element allocated for the MTC UE, and the registration notification message is used. The MTC GW can obtain the above correspondence. For example, in the EPS network, the MTC UE may carry the Global Unique Temporary Identity (GUTI) of the MTC UE in the registration message sent to the MTC Server, and the GUTI includes the MTC UE. MME ID The information is sent by the MTC Server to the MTC GW in the registration notification message. The MTC GW can obtain the address of the MME allocated to the MTC UE by parsing the GUTI, so that the corresponding relationship can be obtained. Method 2 is an MTC UE. The allocated mobility management network element and the MTC server for the MTC UE are actively notified to the MTC GW of their respective addresses, and the MTC GW establishes the corresponding relationship after receiving the information of the two on the MTC GW; Method 3, MTC The GW obtains the address of the mobility management network element allocated for the MTC UE from the user subscription data storage through the interface between the user and the data storage of the user, and acquires the MTC Server actively notified by the MTC server of the MTC UE. Relevant information, thereby establishing the above correspondence. The following takes the E-UTRAN network as an example to describe the method for obtaining the addresses of the above three mobility management network elements. Method 1 FIG. 11 is a flow chart showing the correspondence between the MTC GW, the identifier of the MTC UE, the address of the MTC Server serving the MTC UE, and the address of the MME allocated for the MTC UE, as shown in FIG. The MTC GW obtains the corresponding relationship mainly including the following steps:

5111, the MTC UE is attached to the PS network, and the MTC UE is allocated a GUTI in the attaching process, and the GUTI is included in the attach response and sent to the MTC UE. According to the composition of the GUTI in the prior art, the GUTI includes The ID information of the MME allocated by the MTC UE can be addressed to the MME allocated for the MTC UE according to the MME ID.

After the access to the PS network, the MTC UE initiates application layer registration to the MTC server, and carries the GUTI information in the registration message.

After receiving the registration request of the MTC UE, the MTC Server sends a registration notification message to the MTC GW. The registration notification message carries: MTC UE information, MTC Server information,

GUTI information (ie GUTI information). The information of the MTC UE includes: an IMSI of the MTC UE and/or an IP address of the MTC UE; the information of the MTC Server includes: a monthly service identifier of the MTC Server and/or an IP address of the MTC Server. 5114. The MTC GW parses the address of the MME allocated by the MTC UE according to the GUTI information carried in the registration notification message. Meanwhile, the MTC GW locally saves the identifier of the MTC UE and the MTC Server of the MTC UE. The correspondence between the address and the address of the MME allocated for the MTC UE, so that the association of the three can be achieved.

5115. If the MTC Server determines to allow the MTC UE to register according to the service data, a registration response is returned. In this registration response, it is possible to carry thousands of service layer parameters to the MTC UE. Method 2 FIG. 12 illustrates a process in which the MTC GW uses the method MTC UE, the address of the MTC server for the MTC UE, and the address of the MME allocated for the MTC UE, as shown in FIG. The MTC GW obtains the corresponding relationship mainly including the following steps:

5211. The MTC UE sends an attach request to the network, where the MTC UE sends an attach request to the MME.

5212: The MME sends a location update request to the HSS. S213: The HSS sends a location update response to the MME. In the process, the HSS sends the subscription data of the MTC UE to the MME, where the M2M subscription data is included in the M2M subscription data. The information of the MTC server serving the MTC UE (which may be a domain name or an IP address), according to which the address of the corresponding MTC Server can be resolved. S214. The MME instructs the SGW/PGW to create a suitable payload for the MTC UE.

5215. The MME sends an attach response to the MTC UE.

5216, MTC GW MME sends a notification message to inform the MME address is assigned MTC UE; and, alternatively, may MME ^ ¹ month MTC UE that works to the MTC Server address is also included in the notification message, so that The MTC GW can obtain the correspondence between the MTC UE, the address of the MTC server for the MTC UE, and the address of the MME allocated for the MTC UE by using the notification message. Specifically, the foregoing notification message may be an independent notification message, or may exist in other messages sent by the MME to the MTC GW (for example, when the MTC UE is attached, the MME sends an attach event to the MTC GW). The following information is included in the notification message: the identifier information of the MTC UE (which may include: the identifier of the MTC UE (such as the IMSI) and/or the IP address of the MTC UE) and the identifier information of the MME (specifically, the identifier of the MME may be included: / or MME's IP address ;). The MTC GW can learn the address information of the MME allocated for the MTC UE according to the correspondence between the identifier information of the MTC UE and the MME carried in the notification message.

5217, the MTC UE initiates registration of the service layer to the MTC Server;

The MTC Server sends a registration notification message to the MTC GW. Specifically, the parameters that the MTC Server carries in the notification message include: the identifier information of the MTC UE and the MTC Server. Specifically, the identifier information of the MTC UE may include: The identifier of the MTC Server (for example, IMSI) and/or the IP address of the MTC server may include: a monthly service identifier and/or an IP address of the MTC Server.

After receiving the registration notification message, the MTC GW can obtain the address of the MTC server served by the MTC UE and the address of the MME allocated to the MTC UE, thereby establishing the identifier of the MTC UE and the MTC of the MTC UE. The correspondence between the address of the server and the MME assigned to the MTC UE. In the flow shown in FIG. 12, it should be noted that the step S216 may be sent after the step S215, or may be sent after the step S213, and the specific step is performed after the step, which has the same effect, and is not limited in the present invention. . Method 3 FIG. 13 is a flowchart of the correspondence between the MTC GW, the MTC server address of the MTC UE, and the address of the MME allocated for the MTC UE, as shown in FIG. The MTC GW obtains the corresponding relationship mainly includes the following steps: S311: The MTC UE is attached to the PS network. In the process of attaching the MTC UE to the network, the address of the MME allocated for the MTC UE is saved in the HSS.

S312: The MTC UE initiates a service layer registration with the MTC Server. S313. The MTC Server sends a registration notification message to the MTC GW. The registration notification message carries the identifier information of the MTC UE and the identifier information of the MTC server, where the identifier information of the MTC UE includes: an identifier of the MTC UE (for example, IMSI) and / or IP address, MTC Server identification information includes: MTC Server's monthly service ID and / or IP address.

5314, the MTC GW queries the HSS for the address of the MME allocated for the MTC UE, and the HSS returns the address of the MME allocated by the MTC UE; thus, by the steps S313 and S314, the MTC GW obtains the identifier of the MTC UE, and the MTC UE is the elapsed time. The correspondence between the address of the MTC Server and the address of the MME allocated for the MTC UE.

5, the MTC Server sends a registration response to the MTC UE. In the process shown in FIG. 13, the MTC GW queries the HSS for the address of the MME allocated to the MTC UE, which may be: The MTC GW queries the HSS for the MTC UE. The contract data, the HSS returns the address of the MME allocated to the MTC UE while returning the subscription data of the MTC UE; or: the MTC GW queries the HSS for the address of the MME allocated for the MTC UE, and the HSS only returns the allocation to the MTC UE. The address of the MME. The foregoing is an example in which the access control network element is an MTC server. If the access control network element is an MTC gateway, in the foregoing method (A), the MTC gateway only needs to interact with the mobility management network element, but does not need to The step of interacting with the MTC server, and in the foregoing method (B) and the foregoing method (C), when receiving the registration request sent by the MTC UE, the MTC server may send a registration notification message to the MTC gateway, and the MTC gateway receives the After the registration notification message is sent, the information about the MTC UE or the access layer event is queried or subscribed to the mobility management network element, and the specific implementation process can be obtained from the above process, and the details are not mentioned.

(2) Step S603 In a specific application, the access control network element may determine whether the MTC UE is allowed to access by obtaining the information of the MTC UE of the underlying access layer from the mobility management network element, and determining whether the MTC UE satisfies a predetermined condition. And, if it is determined that the MTC UE is not allowed to access, send an indication to the mobility management network element to reject the access of the MTC UE, to control access of the MTC UE. Specifically, the foregoing predetermined conditions include, but are not limited to, one of the following or any combination thereof: a time when the MTC UE is allowed to access, a location area i that allows the MTC UE to access, or a binding relationship between the IMSI and the IMEI that the MTC UE is allowed to use, The network to which the MTC UE is allowed to be attached, the number of times the MTC UE is allowed to access, and the like. In a specific implementation process, the foregoing predetermined condition may be saved in the user subscription data storage as the subscription data of the MTC UE, or may be saved in the access control network element. For example, if one of the predetermined conditions is: The duration of the MTC UE accessing within one month is not more than 24 hours, the user may subscribe to the data store to save the rule as the subscription data of the MTC UE, by accessing The control network element records the total duration of the access of the MTC UE in one month. Specifically, the access control network element may obtain the subscription data of the MTC UE from the mobility management network element, and notify the attached event according to the received event. Determining the time difference of the event notification to calculate the duration of each access of the MTC UE, and recording the total duration of the MTC UE access in the month according to the duration, and determining that the MTC UE accesses in the month according to the duration Whether the total duration is more than 24 hours, so that when the next access receives the notification of the attachment event, it is determined whether the MTC UE is not allowed to access. Similarly, for other predetermined conditions, the access control network element may also perform judgment according to the current information of the MTC UE, and the specific determination process may be performed according to specific conditions. Specifically, the access control network element determines that the MTC UE is not allowed to access, including but not limited to one of the following or any combination thereof:

(1) determining that the MTC UE requests to attach to the network during the non-permitted time; (2) determining that the MTC UE requests to attach to the network in the non-permitted location area;

(3) determining that the MTC UE exceeds the number of allowed accesses;

(4) determining that the MTC UE requests to attach to the network by using a binding relationship between the IMSI and the IMEI that is not allowed;

(5) determining that the MTC UE moves to an unallowable location area; (6) determining that the time when the MTC UE is attached to the network exceeds the allowed access time;

(7) It is judged that the MTC UE switches to an unallowable network. Further, if the access control network element determines that the MTC UE does not allow access when the MTC UE requests attachment, the access control network element sends an indication to the mobility management network element to reject the attachment of the MTC UE; The access control network element is configured to determine that the MTC UE is not allowed to access after the MTC UE has attached to the network, and the access control network element sends an indication to the mobility management network element to attach the MTC UE. In the specific implementation process, if the access control network element is an MTC gateway, the MTC gateway may directly send an indication to the mobility management network element after determining that the MTC UE is not allowed to access the network; if the access control network element is the MTC After the server determines that the MTC UE is not allowed to access the network, the MTC server sends an indication to the mobility management network element through the MTC gateway. (3) Step 4: S605 In the specific implementation process, after receiving the foregoing indication sent by the access control network element in step S603, the mobility management network element performs the corresponding operation and performs the corresponding operation. Specifically, if the mobility management network element is in the process of initiating an attach request by the MTC UE, and receiving the foregoing indication (when the access control network element indicates to reject the MTC UE attach), the mobility management network element rejects the attachment of the MTC UE. Returning an attach rejection response to the MTC UE; if the mobility management network element receives the indication after the MTC UE attaches to the network (the access control network element indicates to attach the MTC UE), the mobility management network element Perform a detach process to attach the MTC UE. To further understand the above technical solutions provided by the embodiments of the present invention, the following solutions are described by using an EPS network as an example. Method Embodiment 1 This embodiment describes a flow in which the MTC Server controls the access of the MTC UE by using the information of the MTC UE obtained from the MME after the MTC UE is attached. FIG. 14 is a flowchart of the MTC server de-attaching the MTC UE according to the queried MTC UE information after the MTC UE is attached. As shown in FIG. 14, the MTC Server detaches the MTC UE according to the queried MTC UE information. The MTC UE mainly includes the following steps:

S401. The MTC UE accesses the network.

S402. The MTC UE initiates a service layer registration with the MTC Server. S403, the MTC Server queries the MTC GW for the information of the MTC UE, or subscribes to the MTC GW for the access layer event related to the MTC UE, and the MTC GW sends the query and the subscription request to the MME; if the MTC GW is used by the MTC GW After the access control is performed, in step S403, the MTC Server may send a registration notification message to the MTC GW, and after receiving the registration message, the MTC GW sends a query or subscription request to the MME.

5404. An access layer event related to the MTC UE occurs. This step occurs after the MTC Server subscribes to the access layer event.

S405: The MME returns the information of the queried MTC UE to the MTC GW, or the MME notifies the MTC GW of the access layer event after the MTC server subscribes the access layer event to the MME through the MTC GW, and the access layer event occurs (S404). . The MTC GW sends the queried information or event notification to the MTC Server;

5406, after the MTC Server obtains the information of the MTC UE, or obtains the event notification of the access layer, the MTC Server needs to be in the service management, and determines that the MTC UE needs to be attached; S407, the MTC Server sends a detach request to the MTC GW. The MTC GW sends a detach request to the MME;

After the MME receives the detach request, the MME performs a detach procedure to attach the MTC UE.

5409. The MME sends a detach response to the MTC GW, and the MTC GW sends a detach response to the MTC Server. In the above process, if the MTC GW is to perform the detachment of the MTC UE, the MTC GW may obtain the information of the MTC UE returned by the MME or the event notification of the last 4 , in the above step S405, and may determine according to the service management requirement. Whether to attach the MTC UE, if yes, send a detach request to the MEE, and then perform steps S408 and S409, and in S409, the MTC GW may send the detach response to the MTC Server, or may not send to the MTC Server. De-attach response. Method embodiment two This embodiment describes a flow in which the MTC Server controls the access of the MTC UE by using the information of the MTC UE obtained from the MME when the MTC UE is used. In most cases, there are four important parts in the control of the MTC UE in the M2M communication: access control, including: controlling the access time, the number of accesses, and the access location of the MTC UE. If the current access of the MTC UE is not within the allowable range, the network should reject the attachment of the MTC UE, or attach the MTC UE, and further issue an indication to the network. When a similar situation occurs, the network may refuse the network. MTC UE attach request. In this application, the MME may actively send an attach event notification to the MTC GW when the MTC UE attaches, and the MTC GW sends the event notification to the MTC Server, and the MTC Server determines whether the attach is allowed. Similarly, the MTC GW may not send the event notification to the MTC Server, but directly determine whether the attachment of the MTC UE is allowed according to the event notification. FIG. 15 is a schematic diagram of a flow of an attach event notification sent by the MME to the MTC GW when the MTC UE is attached, and the MTC GW/MTC Server determines whether to allow the MTC UE to attach. As shown in FIG. 15 , the method mainly includes the following steps: S501 , MTC UE to the network Sending an attach request, specifically sending an attach request to the MME;

After the MME receives the attach request, the MME sends a location update to the HSS. In the process, the HSS sends the subscription data of the MTC UE to the MME.

5503. The MME sends an attach event notification to the MTC GW.

5504. Optionally, if the MTC GW determines whether the attach is allowed, the MTC GW needs the service management after receiving the notification of the attach event, and determines whether the MTC UE is allowed to be attached. In this embodiment, the MTC GW needs to be in the service management manner. It is determined that the MTC UE is not allowed to attach; in the attach event, the MME may include the thousands of information of the attached, for example: the accessed network, the location of the access, the time of the access, the IMSI and the IMEI used by the MTC UE. Binding relationships, etc. The MTC GW according to the information of the MTC UE's allowed access, for example, the time the MTC UE allows access, the location area allowed to access, the number of times the access is allowed, the network allowed to access, the IMSI and the IMEI that are allowed to be used. Binding relationship, etc., determining that the current MTC UE is attached to the non-permitted time, or the non-allowed location area, or the number of times the current access times of the MTC UE has exceeded the allowed access, or the IMSI and IMEI that the MTC UE uses are not allowed. If the MTC UE requests to attach to an unallowed network or the like, the MTC GW determines that the MTC UE is not allowed to attach. After determining that the MTC UE is not allowed to attach, the MTC GW performs step S508. The following steps S505 to S506 are steps performed by the MTC Server to determine whether to allow the MTC UE to be attached. In the case where steps S505 to S507 are performed, the above step S504 is not performed. S505. The MTC GW sends the event notification to the MTC Server.

5506. After receiving the attachment event of the MME, the MTC Server needs to perform service management, and determines that the access of the MTC UE should be denied.

5507: The MTC Server sends a reject access indication to the MTC GW.

S508: The MTC GW sends a reject access indication to the MME. S509: After receiving the reject attachment indication, the MME rejects the access of the MTC UE, and returns an attach rejection response to the MTC UE. Since the MTC GW is operator-controlled, in this embodiment, if judged by the MTC GW, the operator can have more flexible access control rights. Although the E-UTRAN (EPS) network is taken as an example in the above embodiment, in fact, for GPRS access of the GERAN/UTRAN network, the SGSN in the GERAN/UTRAN network is equivalent to the MME in the E-UTRAN network, acting as the PS. The access control and mobility management functions of the domain, and the GGSN in the GERAN/UTRAN network is equivalent to the SGW+PGW in the E-UTRAN network, and the HLR in the GERAN/UTRAN is equivalent to the HSS in the E-UTRAN network. Therefore, according to the above description of the embodiments of the present invention, those skilled in the art can directly apply the foregoing technical solutions provided by the embodiments of the present invention to the PS domain in the GERAN/UTRAN network. It should be noted that the steps shown in the flowchart of the accompanying drawings may be performed in a computer system such as a set of computer executable instructions, and, although the logical order is shown in the flowchart, in some cases, The steps shown or described may be performed in an order different than that herein. As described above, in the embodiment of the present invention, the access control network element (MTC GW/MTC Server) of the service layer obtains the information of the MTC UE of the access layer from the mobility management network element, and further, according to the acquired MTC UE The information is effectively controlled for access by the MTC UE. In addition, in the embodiment of the present invention, the MTC server can also perform the security-risk certificate to the MTC server through the MTC GW, and only the MTC server that is allowed to access can access the core network, and the access is denied to the illegal MTC server. Thereby the security of the core network can be guaranteed. In addition, in the embodiment of the present invention, the access of the MTC UE can be controlled by the MTC GW, so that the operator can flexibly control the access of the MTC UE when the MTC Server is a non-operator network element. . 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, such 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 they may be 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 scope of the present invention are intended to be included within the scope of the present invention.

Claims

The access control method for a machine type communication MTC terminal is characterized in that it comprises:  The mobility management network element reports to the access control network element information currently attached to the network or the MTC terminal currently attached to the network;  The access control network element determines, according to the information of the MTC terminal, that the MTC terminal is not allowed to access, and sends an indication to the mobility management network element to reject the access of the MTC terminal; the mobility management network element Receiving the indication, according to the indication, denying the MTC terminal to access the network. The method according to claim 1, wherein the information that the mobility management network element sends to the access control network element to the MTC terminal comprises:  And the mobility management network element reports the information of the MTC terminal to the access control network element according to the indication of the subscription data of the MTC terminal that is obtained from the user subscription data storage. The method according to claim 2, wherein the subscription data includes: a first indication that the mobility management network element sends information of the MTC terminal to the access control network element Information  And the information that the mobility management network element reports to the access control network element to the MTC terminal includes:  After receiving the location update response, the mobility management network element reports the information of the MTC terminal to the access control network element according to the indication of the first indication information included in the subscription data. The method according to claim 2, wherein the subscription data further comprises: instructing the mobility management network element to access the access control network when an access layer event related to the MTC terminal occurs The second indication information of the element sending event notification; The information that the mobility management network element reports to the access control network element of the MTC terminal includes: And the mobility management network element sends an event notification to the access control network element when the access layer event related to the MTC terminal occurs, and the event notification is sent to the access control network element, where the event notification is It carries information about the currently described MTC terminal. The method according to claim 1, wherein the information that the mobility management network element sends to the access control network element to the MTC terminal comprises:  After the MTC UE is attached to the network, the access control network element sends a query request to the mobility management network element, requesting to query information of the MTC terminal;  After receiving the query request, the mobility management network element sends information of the MTC terminal to the access control network element. The method according to claim 1, wherein the information that the mobility management network element sends to the access control network element to the MTC terminal comprises:  After the MTC UE is attached to the network, the access control network element sends a query request to the mobility management network element to subscribe to an access layer event related to the MTC terminal; the mobility management network element is The access layer event notification is sent to the access control network element when the access layer event occurs, where the access layer event notification carries the information of the MTC terminal. The method of claim 4 or 6, wherein the access layer event associated with the MTC terminal comprises one or any combination of the following:  The subscription data of the MTC terminal changes;  The location of the MTC terminal changes;  The state of the MTC terminal changes;  The network of the MTC terminal changes;  The binding relationship between the international subscriber identity code IMSI used by the MTC terminal and the international mobile device identifier IMEI is changed. The method according to any one of claims 1 to 6, wherein the information of the MTC terminal comprises one or any combination of the following:  The current service subscription data of the MTC terminal; The international subscriber identity code IMSI and the international mobile equipment identity IMEI used by the MTC terminal; Context information of the MTC terminal on the mobility management network element. The method according to claim 8, wherein the context information of the MTC terminal on the mobility management network element comprises: current location area information of the MTC terminal and/or current status of the MTC terminal Status information. The method according to claim 8, wherein the access control network element determines that the MTC terminal access is not allowed to include:  Determining, by the access control network element, whether the obtained information of the MTC terminal meets a predetermined condition, and determining that the MTC terminal is not allowed to access if the determination is not satisfied;  The predetermined condition includes one of the following or any combination thereof: a time for allowing the MTC terminal to access, a location area for allowing the MTC terminal to access, and an IMSI binding relationship between the IMSI and the IMEI used by the MTC terminal. And a network that allows the MTC terminal to attach, and the number of times the MTC terminal is allowed to access. The method according to claim 10, wherein the access control network element determines that the MTC terminal is not allowed to access in the following one or any combination thereof:  Determining that the MTC terminal requests to attach to the network during an unallowed time;  Determining that the MTC terminal requests to attach to the network in the non-permitted location area; determining that the MTC terminal exceeds the number of allowed accesses;  Determining that the MTC terminal is attached to the network by a binding request of IMSI and IMEI that are not allowed;  Determining that the MTC terminal moves to an unallowable location area;  Determining that the time when the MTC terminal is attached to the network exceeds the allowed access time; determining that the MTC terminal switches to an unallowable network. The method according to any one of claims 1 to 6, wherein, if the MTC terminal currently requests to attach to the network, the indication of rejecting the access of the MTC terminal comprises: rejecting the attachment of the MTC terminal Instructions;  The mobility management network element denying the MTC terminal to access the network according to the indication includes: The mobility management network element rejects the attachment of the MTC terminal, and returns an attach rejection response to the MTC terminal. The method according to any one of claims 1 to 6, wherein, if the MTC terminal is currently attached to the network, the indication of rejecting the access of the MTC terminal comprises: detaching the MTC terminal Instructions;  The mobility management network element denying the MTC terminal to access the network according to the indication includes:  The mobility management network element performs a detach process to attach the MTC terminal. The method according to any one of claims 1 to 6, wherein the mobility management network element comprises: a 艮 通用 General Packet Radio Service Support Node SGSN or a mobility management unit MME. The method according to claim 2 or 3, wherein the user subscription data storage comprises: a home location register HLR or a home subscriber server HSS. The method according to any one of claims 1 to 6, wherein the access control network element comprises: an MTC gateway or an MTC server. The method of claim 16, wherein, in the case that the access control network element is the MTC server, the MTC server and the mobility management network element are performed by using an MTC gateway. communication. An access control system for an MTC terminal, comprising: a user subscription data storage, a mobility management network element, and an access control network element, where  The user subscription data storage is used to store subscription data of the MTC terminal in the system;  The mobility management network element is connected to the user subscription data storage, and is configured to receive subscription data that is sent by the user subscription data store and is attached to a network or an MTC terminal that is currently attached to the network, and The access control network element provides information about the MTC terminal; The access control network element is connected to the mobility management network element, and is configured to determine whether to allow the MTC terminal to access according to the information of the MTC terminal, and not allow the MTC terminal to access In case, the mobility management network element is sent to reject the MTC terminal An indication of end access, such that the mobility management network element denies the MTC terminal from accessing the network. The system according to claim 18, wherein the access control network element is an MTC gateway. The system according to claim 18, wherein the access control network element is an MTC server, the system further includes:  The MTC gateway is connected between the MTC server and the mobility management network element, and is configured to forward data between the MTC server and the mobility management network element, and perform security verification on the MTC server.