Abstract:
Disclosures are a user equipment (UE) registration method, entity, system and a computer storage medium. The method comprises: a common service entity (CSE) in a UE sending an equipment registration request to a machine type communication-inter working function entity (MTC-IWF), wherein the equipment registration request contains an identifier of the UE in an underlying network, an application port identifier of the UE, an identifier of a machine-to-machine/man (M2M) service provider subscribed to by the UE, and an identifier of an application entity (AE) of the M2M service provider.

Description:
TECHNICAL FIELD 
       [0001]    The disclosure relates to the management technology of a terminal in a machine type communication (MTC) in the field of the terminal communications, and in particular to a user equipment (UE) registration method, entity, system and computer storage medium. 
       BACKGROUND 
       [0002]    The machine-to-machine/man (M2M) communication system is constituted by respective M2M nodes and an underlying network. The communication between M2M nodes is realized through the underlying network. A M2M node at least includes an application entity (AE) or a common service entity (CSE). The AE is a logic unit for executing the actual M2M application, and the CSE a logic unit for managing and serving the application. The underlying network services entity (NSE) provides services of equipment management, position serving, equipment triggering etc. for the CSE. The NSE is, for example, a home subscriber server (HSS), or a MTC inter working function (MTC-IWF) entity, etc. 
         [0003]    The communication between the M2M applications is realized through the interaction of CSEs. The registration of the M2M to the CSE and the registration between the CSEs are needed, so as to realize the interaction of the M2M application through the communication between the CSE. A M2M system architecture is shown in  FIG. 1 . In the M2M system architecture, an application node is an execution node at end of the M2M system, such as an intelligent electric meter, a temperature measurement and control sensor, a fire alarm, and an intelligent appliance etc.; a middle node (MN) is a middle element connecting the end execution node to a network side server, such as a gateway; an infrastructure node (IN) is a server at the network side, the application registered in the IN can be a management platform of the M2M service provider (SP), and the binding relationship between the M2M node and the identifier of the CSE, the identifier in the underlying network is maintained by the M2M SP. 
         [0004]    The application node can be categorized into two types according to differences in functions: a node including the CSE and a node not including the CSE. For example, an application dedicated node (ADN) at least includes a AE, not including the CSE; and an application service node (ASN) at least includes a AE and a CSE, and the ASN or MN is physically corresponding to the UE. 
         [0005]    In actual application, when creating, retrieving, updating or deleting operation is executed, by the application entity registered in the infrastructure node, on resources in the UE, the connection between the CSE on the ASN and the CSE in the IN is triggered to be created, or the connection between the CSE on the MN and the CSE in the IN is triggered to be created, as the server on the network side, a triggering message is transmitted through the underlying network, and the following information is provided, by the server, to the underlying network so as to trigger the UE: 
         [0006]    1) a M2M external identifier (M2M-Ext-ID): arranged to identify the target UE of a triggering request; 
         [0007]    2) a triggering message recipient identifier (Trigger-Recipient-ID): arranged to be the identifier for routing the triggering message to a target ASN/MN-CSE in the UE; 
         [0008]    3) a IN-CSE identifier. 
         [0009]    The M2M external identifier serves as one of the necessary information provided by the server to the underlying network for triggering the UE. However, in related art, there is not any effective mechanism for the IN-CSE to obtain the M2M-Ext-ID. The process of triggering the UE thus cannot be performed. 
       SUMMARY 
       [0010]    The disclosure is intended to provide a user equipment (UE) registration method, entity, system and a computer storage medium, enabling the network side server to obtain a M2M external identifier of the UE, so as to realize the triggering of the UE by the server. 
         [0011]    The technical solution of the disclosure is implemented as follows. 
         [0012]    An embodiment of the disclosure provides a user equipment (UE) registration method, which includes: sending, by a common service entity (CSE) in the UE, an equipment registration request to a machine type communication inter-working function entity (MTC-IWF), in which the equipment registration request includes an identifier of the UE in an underlying network, an application port identifier of the UE, an identifier of a machine-to-machine/man (M2M) service provider subscribed to by the UE, and an identifier of an application entity (AE) of the M2M service provider. 
         [0013]    An embodiment of the disclosure further provides a CSE set in the UE, in which the CSE includes: 
         [0014]    a registration requesting unit, arranged to generate an equipment registration request; and 
         [0015]    a first sending unit, arranged to send the registration request to the MTC-IWF, the registration request including an identifier of the UE in the underlying network, an application port identifier of the UE, an identifier of the M2M service provider subscribed to by the UE, and an identifier of the AE of the M2M service provider. 
         [0016]    An embodiment of the disclosure further provides a MTC-IWF, which includes: 
         [0017]    a first receiving unit, arranged to receive a registration request sent by the CSE in the UE; and 
         [0018]    an analyzing unit, arranged to analyze the identifier of the UE in the underlying network, the application port identifier of the UE, the identifier of the M2M service provider subscribed to by the UE, and the identifier of the AE of the M2M service provider, included in the equipment registration request. 
         [0019]    An embodiment of the disclosure further provides a CSE set in a server in which the UE is registered, in which the CSE includes: 
         [0020]    a third receiving unit, arranged to receive a registration request sent by the MTC-IWF; 
         [0021]    an authenticating unit, arranged to authenticate the UE; and 
         [0022]    a fourth sending unit arranged to, after the authentication of the authenticating unit is passed, send the registration request to the AE according to the identifier of the AE, in which the registration request sent by the fourth sending unit includes the M2M external identifier of the UE and the application port identifier of the UE. 
         [0023]    An embodiment of the disclosure further provides a registration system, which includes: a MTC-IWF, a CSE set in the UE and a AE of the M2M service provider subscribed to by the UE; 
         [0024]    the CSE set in the UE is arranged to send a registration request to the MTC-IWF, in which the registration request includes an identifier of the UE in the underlying network, an application port identifier of the UE, an identifier of the M2M service provider subscribed to by the UE, and an identifier of the AE of the M2M service provider; and 
         [0025]    the MTC-IWF is arranged to receive the equipment registration request. 
         [0026]    An embodiment of the disclosure further provides a computer storage medium which stores computer executable instructions used for executing the registration method of the UE. 
         [0027]    In the disclosure, the equipment registration request is sent to the MTC-IWF by the CSE in the UE, the registration request including the identifier of the UE in the underlying network, the application port identifier of the UE, the identifier of the M2M service provider subscribed to by the UE, and the identifier of the AE of the M2M service provider. Thus, the M2M external identifier of the UE can be requested from the HSS by the MTC-IWF according to the identifier of the UE in the underlying network and the identifier of the M2M service provider subscribed to by the UE, and the M2M external identifier of the UE can be obtained by the CSE in the server in subsequent registration process, so as to finish the registration process of the UE and realize the triggering of the UE by the server. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0028]      FIG. 1  is a schematic diagram of a M2M system architecture. 
           [0029]      FIG. 2  is a schematic diagram of a registration method according to an embodiment of the disclosure. 
           [0030]      FIG. 3  is a structural diagram of a CSE in UE. 
           [0031]      FIG. 4 a    is a structural diagram  1  of a MTC-IWF according to an embodiment of the disclosure. 
           [0032]      FIG. 4 b    is a structural diagram  2  of a MTC-IWF according to an embodiment of the disclosure. 
           [0033]      FIG. 4 c    is a structural diagram  3  of a MTC-IWF according to an embodiment of the disclosure. 
           [0034]      FIG. 4 d    is a structural diagram  4  of a MTC-IWF according to an embodiment of the disclosure. 
           [0035]      FIG. 4 e    is a structural diagram  5  of a MTC-IWF according to an embodiment of the disclosure. 
           [0036]      FIG. 4 f    is a structural diagram  6  of a MTC-IWF according to an embodiment of the disclosure. 
           [0037]      FIG. 5 a    is a structural diagram  1  of a CSE set in a server to which a AE is registered according to an embodiment of the disclosure. 
           [0038]      FIG. 5 b    is a structural diagram  2  of a CSE set in a server to which a AE is registered according to an embodiment of the disclosure. 
           [0039]      FIG. 5 c    is a structural diagram  3  of a CSE set in a server to which a AE is registered according to an embodiment of the disclosure. 
           [0040]      FIG. 6 a    is a structural diagram  1  of a registration system according to an embodiment of the disclosure. 
           [0041]      FIG. 6 b    is a structural diagram  2  of a registration system according to an embodiment of the disclosure. 
           [0042]      FIG. 6 c    is a structural diagram  1  of a registration system according to an embodiment of the disclosure. 
       
    
    
     DETAILED DESCRIPTION 
       [0043]    The purpose, technical solutions and advantages of the disclosure will be more clear and definite through the further description of the disclosure below with reference to the drawings and embodiments. It should be noted that the embodiments described here are used for illustrating the disclosure only, not limiting. 
         [0044]    As shown in  FIG. 2 , an embodiment of the disclosure provides a registration method, which includes the following steps: 
         [0045]    Step  201 : an equipment registration request is sent to the MTC-IWF by the CSE in the UE. The registration request includes an identifier of the UE in the underlying network, an application port identifier of the UE, an identifier of the M2M service provider subscribed to by the UE, and an identifier of the AE of the M2M service provider. 
         [0046]    In an embodiment, when the equipment registration request is received by the MTC-IWF, the method further includes: a subscription information request is sent to the HSS by the MTC-IWF. The subscription information request includes the identifier of the UE in the underlying network and the identifier of the M2M service provider. 
         [0047]    In an embodiment, when the subscription information request is received by the HSS, the method further includes: a M2M external identifier of the UE is retrieved by the HSS according to the identifier of the UE in the underlying network and the identifier of M2M service provider, and then the M2M external identifier of the UE is fed back to the MTC-IWF through a subscription information response. 
         [0048]    In an embodiment, when the subscription information response is received by the MTC-IWF, the method further includes: a registration request is sent to the CSE in the server by the MTC-IWF according to the identifier of the CSE in the server to which the AE is registered. The registration request includes the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the AE. 
         [0049]    In an embodiment, when the registration request is received by the CSE in the server, the method further includes: the UE is authenticated by the CSE in the server, and after the authentication is passed, the registration request is sent to the AE according to the identifier of the AE. The registration request includes the M2M external identifier of the UE and the application port identifier of the UE. 
         [0050]    In an embodiment, when the registration request is received by the AE, the method further includes: the UE is verified by the AE, after the verification is passed, the binding relationship between the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the CSE in the UE is determined, the registration response is sent to the CSE in the server. The registration response includes the binding relationship. 
         [0051]    In an embodiment, when the registration response is received by the CSE in the server, the method further includes: the binding relationship and a state information of the UE are cached in the CSE of the server, an equipment registration response is sent to the UE by the MTC-IWF. The registration response includes the identifier of the CSE in the server. 
         [0052]    In an embodiment, when the equipment registration request is received by the MTC-IWF, the method further includes: the subscription information request is sent to the HSS by the MTC-IWF. The subscription information request includes the identifier of the UE in the underlying network, the identifier of M2M service provider and the identifier of the CSE in the server to which the AE is registered. 
         [0053]    In an embodiment, when the subscription information request is received by the HSS, the method further includes: the M2M external identifier and a routing information of the UE are retrieved by the HSS according to the identifier of the UE in the underlying network and the identifier of M2M service provider, the authentication of the CSE in the server is searched according to the identifier of the CSE in the server, and the M2M external identifier of the UE, the routing information of the UE and the authentication of the CSE in the server are fed back to the MTC-IWF through the subscription information response. 
         [0054]    In an embodiment, when the subscription information response is received by the MTC-IWF, the method further includes: 
         [0055]    the routing information of the UE and the authentication of CSE in the server are cached in the MTC-IWF, the registration request is sent to the CSE in the server by the MTC-IWF according to the identifier of the CSE in the server. The registration request includes the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the AE. 
         [0056]    In an embodiment, when the registration request is received by the CSE in the server, the method further includes: 
         [0057]    the UE is authenticated by the CSE in the server, after the authentication is passed, the registration request is sent to the AE according to the identifier of the AE. The registration request includes the M2M external identifier of the UE and the application port identifier of the UE. 
         [0058]    In an embodiment, when the registration request is received by the AE, the method further includes: 
         [0059]    the UE is verified by the AE, after the verification is passed, the binding relationship between the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the CSE in the UE is determined, the registration response is sent to the CSE in the server. The registration response includes the binding relationship. 
         [0060]    In an embodiment, when the registration response is received by the CSE in the server, the method further includes: 
         [0061]    the binding relationship and the state information of the UE are cached in the CSE of the server, the equipment registration response is sent to the UE by the MTC-IWF. The registration response includes the identifier of the CSE in the server. 
         [0062]    In an embodiment, when the equipment registration response is sent, by the CSE of the server, to the UE via the MTC-IWF, the method further includes: 
         [0063]    a resource operation request is sent to the CSE of the server by the AE, the resource operation request includes the identifier of CSE in the UE. 
         [0064]    In an embodiment, after the resource operation request is received by the CSE of the server, the method further includes: 
         [0065]    the state information of the UE is checked by the CSE of the server according to the identifier of the CSE in the UE, and an equipment triggering request is sent to the MTC-IWF. The equipment triggering request includes the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the CSE in the server. 
         [0066]    In an embodiment, after the equipment triggering request is received by the MTC-IWF, the method further includes: 
         [0067]    the authentication of the CSE, the identifier and routing information of the UE in the underlying network are requested, by the MTC-IWF, from the HSS according to the identifier of CSE in the sever and the M2M external identifier of the UE, or the authentication of the CSE, the identifier and routing information of the UE in the underlying network are searched for according to the identifier of CSE in the sever and the M2M external identifier of the UE; and 
         [0068]    a triggering process is executed in the underlying network according to the authentication of the CSE, the identifier and routing information of the UE in the underlying network, and an equipment triggering request receipt confirmation is fed back to the CSE in the sever. 
         [0069]    An embodiment of the disclosure further discloses a computer storage medium for storing computer executable instructions, which are used for executing the registration method shown in  FIG. 2 . 
         [0070]    An embodiment of the disclosure further discloses a CSE set in the UE, as shown in  FIG. 3 . The CSE includes: 
         [0071]    a registration requesting unit  31 , arranged to generate an equipment registration request; 
         [0072]    and a first sending unit  32 , arranged to send the registration request to the MTC-IWF, and the registration request includes an identifier of the UE in the underlying network, an application port identifier of the UE, an identifier of the M2M service provider subscribed to by the UE, and an identifier of the AE of the M2M service provider. 
         [0073]    An embodiment of the disclosure further discloses a MTC-IWF, as shown in  FIG. 4 a   , and the MTC-IWF includes: 
         [0074]    a first receiving unit  41 , arranged to receive the registration request sent by the CSE is in the UE; 
         [0075]    and an analyzing unit  42 , arranged to analyze the identifier of the UE in the underlying network, the application port identifier of the UE, the identifier of the M2M service provider subscribed to by the UE, and the identifier of the AE of the M2M service provider, included in the equipment registration request. 
         [0076]    In an embodiment, as shown in  FIG. 4 b    and based on the  FIG. 4 a   , the MTC-IWF further includes: 
         [0077]    a second sending unit  43 , arranged to send a subscription information request to the HSS when the equipment registration request is received by the first receiving unit  41 . The subscription information request includes the identifier of the UE in the underlying network and the identifier of M2M service provider. 
         [0078]    Preferably, the first receiving unit  41  is further arranged to receive a subscription information response sent by the HSS. The subscription information response is generated when the subscription information request is received by the HSS. The subscription information response includes the M2M external identifier of the UE retrieved by the HSS according to the identifier of the UE in the underlying network and the identifier of M2M service provider. 
         [0079]    Preferably, the second receiving unit  43 , is further arranged to when the subscription information response is received by the first receiving unit  41 , send a registration request to the CSE in the server according to the identifier of the CSE in the server to which the AE is registered. The registration request includes the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the AE. 
         [0080]    In an embodiment, as shown in  FIG. 4 c    and based on the  FIG. 4 b   , the MTC-IWF further includes a first equipment triggering unit  44 ; 
         [0081]    the first receiving unit  41  is further arranged to receive an equipment triggering request sent by the CSE in the server. The equipment triggering request includes the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the CSE in the server; 
         [0082]    the second receiving unit  43  is further arranged to feed back an equipment triggering request receipt conformation to the CSE in the server; and 
         [0083]    the first equipment triggering unit  44  is arranged to execute the equipment triggering process in the underlying network according to the authentication of the CSE, the identifier and routing information of the UE in the underlying network. 
         [0084]    In another embodiment, as shown in  FIG. 4 d    and based on the  FIG. 4 b   , the MTC-IWF further includes: 
         [0085]    a third sending unit  45 , arranged to send a subscription information request to the HSS when the equipment registration request is received by the first receiving unit  41 . The subscription information request includes the identifier of the UE in the underlying network, the identifier of M2M service provider and the identifier of the CSE in the server to which the AE is registered; 
         [0086]    the first receiving unit  41  is further arranged to receive a subscription information response sent by the HSS. The subscription information response includes the M2M external identifier, the routing information of the UE retrieved by the HSS according to the identifier of the UE in the underlying network and the identifier of M2M service provider, and the authentication of the CSE in the server searched for by the HSS according to the identifier of CSE in the server. 
         [0087]    Preferably, as shown in  FIG. 4 e    and based on the  FIG. 4 d   , the MTC-IWF further includes a first caching unit  46 , when the subscription information response is received by the first receiving unit  41 , arranged to cache the routing information of the UE and the authentication of the CSE in the server; and 
         [0088]    the third sending unit  45  is further arranged to send a registration request to the CSE in the server according to the identifier of CSE in the server. The registration request includes the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the AE. 
         [0089]    In an embodiment, as shown in  FIG. 4 f    and based on the  FIG. 4 e   , the first receiving unit  41  is further arranged to receive the equipment triggering request sent by the CSE in the server. The equipment triggering request includes the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the CSE in the server; 
         [0090]    the MTC-IWF further includes a searching unit  47 , arranged to locally search for the authentication of the CSE, the identifier and routing information of the UE in the underlying network according to the identifier of the CSE in the server and the M2M external identifier of the UE; 
         [0091]    the third sending unit  45  is further arranged to feed back an equipment triggering request receipt conformation to the CSE in the server; and 
         [0092]    the MTC-IWF further includes a second equipment triggering unit  48 , arranged to execute the equipment triggering process in the underlying network according to the authentication of the CSE, the identifier and routing information of the UE in the underlying network. 
         [0093]    The MTC-IWF can be implemented by one or multiple servers in actual applications. The first receiving unit  41 , the analyzing unit  42 , the second sending unit  43 , the first equipment triggering unit  44 , the third sending unit  45 , the searching unit  47  and the second equipment triggering unit  48  can be implemented by a central processing unit (CPU), a digital signal processor (DSP) or a field programmable gate array (FPGA) in the server. The first caching unit  46  can be implemented by a nonvolatile storage medium in the server. 
         [0094]    An embodiment of the disclosure further provides a CSE set in a server to which the AE is registered, as shown in  FIG. 5 a   . The CSE includes: 
         [0095]    a third receiving unit  51 , arranged to receive a registration request sent by MTC-IWF; 
         [0096]    an authenticating unit  52 , arranged to authenticate the UE; and 
         [0097]    a fourth sending unit  53 , after the authentication of the authenticating unit  52  is passed, arranged to send the registration request to the AE according to the identifier of the AE. The registration request sent by the fourth sending unit  53  includes the M2M external identifier of the UE and the application port identifier of the UE; 
         [0098]    preferably, the third receiving unit  51  is further arranged to receive a registration response. When the registration response is received by the AE, the UE is verified, the verification is passed, the registration response is sent by the AE after the binding relationship between the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the CSE in the UE is determined. The registration response includes the binding relationship between the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the CSE in the UE; 
         [0099]    As shown in  FIG. 5 b    and based on  FIG. 5 a   , the CSE further includes a second caching unit  54 , arranged to cache the binding relationship and the state information of the UE; and 
         [0100]    the fourth sending unit  53  is further arranged to send the equipment registration response to the UE via the MTC-IWF, and the equipment registration response includes the identifier of the CSE in the sever. 
         [0101]    In an embodiment, the third receiving unit  51  is further arranged to receive the resource operation request, the resource operation request is sent by the AE when the equipment registration response is sent, by the fourth sending unit  53 , to the UE via the MTC-IWF. The resource operation request includes the identifier of CSE in the UE; 
         [0102]    as shown in  FIG. 5 c    and based on  FIG. 5 b   , the CSE further includes a detecting unit  55 , arranged to detect the state information of the UE according to the identifier of the CSE in the UE; and 
         [0103]    the fourth sending unit  53  is further arranged to send the equipment triggering request to the MTC-IWF. The equipment triggering request includes the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the CSE in the server. 
         [0104]    The CSE can be implemented by one or multiple servers in actual applications. The third receiving unit  51 , the authenticating unit  52 , the fourth sending unit  53  and the detecting unit  55  can be implemented by a central processing unit (CPU), a digital signal processor (DSP) or a field programmable gate array (FPGA) in the server. The second caching unit  54  can be implemented by a nonvolatile storage medium in the server. 
         [0105]    An embodiment of the disclosure further provides a registration system, as shown in  FIG. 6 a   . The system includes: a MTC-IWF  61 , a CSE  62  in the UE and a AE  63  of the M2M service provider subscribed to by the UE; 
         [0106]    the CSE  62  in the UE is arranged to send an equipment registration request to the MTC-IWF  61 . The equipment registration request includes an identifier of the UE in the underlying network, an application port identifier of the UE, an identifier of the M2M service provider subscribed to by the UE, and an identifier of the AE  63  of the M2M service provider; 
         [0107]    the MTC-IWF  61  is arranged to receive the equipment registration request. 
         [0108]    In an embodiment, as shown in  FIG. 6 b    and based on the  FIG. 6 a   , the system further includes a HSS  64 ; 
         [0109]    the MTC-IWF  61  is further arranged to send a subscription information request to the HSS when the equipment registration request is received. The subscription information request includes the identifier of the UE in the underlying network and the identifier of M2M service provider. 
         [0110]    In an embodiment, the HSS  64  is further arranged to, when the subscription information request is received, retrieve the M2M external identifier of the UE according to the identifier of the UE in the underlying network and the identifier of M2M service provider, and feed back the M2M external identifier of the UE to the MTC-IWF  61  through the subscription information response. 
         [0111]    In an embodiment, the MTC-IWF  61  is further arranged to, when the subscription information response is received, send the registration request to the CSE  62  in the server according to the identifier of the CSE  62  in the server to which the AE  63  is registered. The registration request includes the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the AE  63 . 
         [0112]    In an embodiment, the CSE  62  in the server is further arranged to, when the registration request is received, authenticate the UE, and send the registration request to the AE  63  according to the identifier of the AE  63  after the authentication is passed. The registration request includes the M2M external identifier of the UE and the application port identifier of the UE. 
         [0113]    In an embodiment, the AE  63  is further arranged to, when the registration request is received, verify the UE, determine the binding relationship between the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the CSE  62  in the UE after the verification is passed, and send the registration response to the CSE  62  in the server. The registration response includes the binding relationship. 
         [0114]    In an embodiment, the CSE  62  in the server is further arranged to, when the registration response is received, cache the binding relationship and the state information of the UE, send the equipment registration response to the UE via the MTC-IWF  61 . The registration response includes the identifier of the CSE  62  in the server. 
         [0115]    In an embodiment, as shown in  FIG. 6 c    and based on the system shown in  FIG. 6 a   , the system further includes a HSS  65 ; 
         [0116]    the MTC-IWF  61  is further arranged to send the subscription information request to the HSS  65  when the equipment registration request is received; the subscription information request includes the identifier of the UE in the underlying network, the identifier of M2M service provider and the identifier of the CSE  62  in the server to which the AE  63  is registered. 
         [0117]    In an embodiment, the HSS  65 , when the subscription information request is received, is further arranged to retrieve the M2M external identifier and the routing information of the UE according to the identifier of the UE in the underlying network and the identifier of M2M service provider, search the authentication of the CSE  62  in the server according to the identifier of the CSE  62  in the server, and feed back the M2M external identifier, the routing information of the UE and the authentication of the CSE  62  in the server to the MTC-IWF  61  through the subscription information response. 
         [0118]    In an embodiment, the MTC-IWF  61  is further arranged to cache the routing information of the UE and the authentication of the CSE  62  in the server when the subscription information response is received, and send the registration request to the CSE  62  in the server according to the identifier of the CSE  62  in the server. The registration request includes the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the AE  63 . 
         [0119]    In an embodiment, the CSE  62  in the server is further arranged to authenticate the UE when the registration request is received, send the registration request to the AE  63  according to the identifier of the AE  63  after the authentication is passed. The registration request includes the M2M external identifier of the UE and the application port identifier of the UE. 
         [0120]    In an embodiment, the AE  63  is further arranged to verify the UE when the registration request is received, determine the binding relationship between the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the CSE  62  in the UE after the verification is passed, and send the registration response to the CSE  62  in the server. The registration response includes the binding relationship. 
         [0121]    In an embodiment, the CSE  62  in the server is further arranged to cache the binding relationship and the state information of the UE when the registration response is received, send the equipment registration response to the UE through the MTC-IWF  61 . The equipment registration response includes the identifier of the CSE  62  in the server. 
         [0122]    In an embodiment, the CSE  62  in the server is further arranged to send the resource operation request to the CSE  62  in the server when the equipment registration response is sent to the UE via the MTC-IWF  61 . The resource operation request includes the identifier of the CSE  62  in the server. 
         [0123]    In an embodiment, the CSE  62  in the server is further arranged to, after the resource operation request is received, check the state information of the UE according to the identifier of the CSE  62  in the server, send the equipment triggering request to the MTC-IWF  61 . The equipment triggering request includes the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the CSE  62  in the server. 
         [0124]    In an embodiment, the MTC-IWF  61  is further arranged to, when the equipment triggering request is received, request the authentication of the CSE  62 , the identifier and the routing information of the UE in the underlying network from the HSS according to the identifier of the CSE  62  in the server and the M2M external identifier of the UE, or locally search for the authentication of the CSE  62 , the identifier and the routing information of the UE in the underlying network according to the identifier of the CSE  62  in the server and the M2M external identifier of the UE; and 
         [0125]    further execute the equipment triggering process according to the authentication of the CSE  62 , the identifier and the routing information of the UE in the underlying network, and feed back the equipment triggering request receipt confirmation to the CSE  62  in the server. 
         [0126]    The user equipment registration method of the disclosure is further described below with reference to specific application scenes. 
         [0127]    In a scene 1, the user equipment registration process includes the following steps: 
         [0128]    S 701 : the UE is registered in a network side server when powered on at a first time, and the equipment registration request is sent to the MTC-IWF by the CSE in the UE, the request message including following registration parameters: 
         [0129]    1) Device-ID: the identifier of the UE in the underlying network, such as the international mobile subscriber identity (IMSI); 
         [0130]    2) Trigger-Recipient-ID: trigger message recipient identifier, which is the application port identifier of the UE; 
         [0131]    3) M2M-SP-ID: the identifier of the M2M service provider subscribed to by the UE; 
         [0132]    4) AE-ID: the identifier of AE of the M2M service provider, which is the IN-AE identifier; 
         [0133]    S 702 : the equipment registration request of the UE is received by the MTC-IWF, and a subscription information request is sent to the HSS by the MTC-IWF. The request message including the identifier of the UE in the underlying network and the identifier of the M2M service provider; 
         [0134]    S 703 : the subscription information request sent by the MTC-IWF is received by the HSS, the M2M external identifier (M2M-Ext-ID) of corresponding UE is retrieved according to the identifier of the UE in the underlying network and the identifier of the M2M service provider, and then fed back to the MTC-IWF through the subscription information response; 
         [0135]    a list of one-to-one mapping relationship between the M2M external identifier of the UE and the identifier of the M2M service provider subscribed to by the UE can be created in an information storage of the HSS in application; 
         [0136]    S 704 : the subscription information response sent by the HSS is received by the MTC-IWF, the identifier of the CSE in the server, to which the AE is registered, is searched for in a local information storage according to the identifier of the AE, which is the identifier of the IN-CSE, and the equipment registration request is sent to the CSE in the server according to the identifier of the CSE in the server; the request message including: 
         [0137]    1) M2M-Ext-ID: the M2M external identifier of the UE; 
         [0138]    2) Trigger-Recipient-ID: the application port identifier of the UE; 
         [0139]    3) AE-ID: the identifier of the AE; 
         [0140]    S 705 : the equipment registration request sent by the MTC-IWF is received by the CSE in the server, after the equipment of the UE is authenticated, the registration request is sent to the AE according to the identifier of the AE; the request message including: 
         [0141]    1) M2M-Ext-ID: the M2M external identifier of the UE; 
         [0142]    2) Trigger-Recipient-ID: the application port identifier of the UE; 
         [0143]    S 706 : the registration request sent by the CSE in the server is received by the AE, the binding relationship between the M2M external identifier of the UE, the trigger message recipient identifier and the identifier of the CSE in the UE is determined after the registration parameters of the UE are verified, and the registration response is fed back to the CSE in the server. The response message includes the identifier of the CSE in the UE; 
         [0144]    a list of the binding relationship between the identifier of the CSE in the UE, which is the ASN/MN-CSE identifier, and the external identifier of the UE, the trigger message recipient identifier can be created in the information storage of the AE in application; 
         [0145]    S 707 : the registration response sent by the AE is received by the CSE in the server, and the state parameters of the UE are cached. The parameters include: 
         [0146]    1) CSE-ID: the identifier of the CSE in the UE; 
         [0147]    2) M2M-Ext-ID: the M2M external identifier of the UE; 
         [0148]    3) Trigger-Recipient-ID: the application port identifier of the UE; 
         [0149]    4) State: registration (/connection/sleep/power off/logout); 
         [0150]    the equipment registration response is sent to the MTC-IWF. The response message including: 
         [0151]    1) M2M-Ext-ID: the M2M external identifier of the UE; 
         [0152]    2) Local CSE-ID: the identifier of the CSE in the server; 
         [0153]    3) Remote CSE-ID: the identifier of the CSE in the UE (optional parameter); 
         [0154]    S 708 : the equipment registration response sent by the CSE in the server is received by the MTC-IWF, then sent to the CSE in the UE according to the identifier of the UE in the underlying network. The response message including: 
         [0155]    1) Device-ID: the identifier of the UE in the underlying network; 
         [0156]    2) Remote CSE-ID: the identifier of the CSE in the server; 
         [0157]    3) Local CSE-ID: the identifier of the CSE in the UE (optional parameter); 
         [0158]    S 709 : the equipment registration response sent by the MTC-IWF is received by the CSE in the UE, and the registration process is finished; 
         [0159]    S 710 : the resource operation request is sent to the CSE in the server by the AE. The request message includes the identifier of the CSE in the UE; 
         [0160]    S 711 : the information in the request message is cached by the CSE in the server, the state information of the UE is checked according to the identifier of the CSE in the UE, then the equipment triggering request is sent to the MTC-IWF. The request message includes the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the CSE in the server; 
         [0161]    S 712 , according to the identifier of the CSE in the server and the M2M external identifier of the UE, the authentication of the CSE, the identifier and routing information of the UE in the underlying network are requested from the HSS by the MTC-IWF, the equipment triggering request receipt conformation is fed back to the CSE in the server, and the equipment triggering process is executed in the underlying network. 
         [0162]    In a scene 2, the user equipment registration process includes the following steps: 
         [0163]    S 801 : the UE is registered in a network side server when powered on at a first time, the equipment registration request is sent to the MTC-IWF by the CSE in the UE. The request message includes following registration parameters: 
         [0164]    1) Device-ID: the identifier of the UE in the underlying network, such as the international mobile subscriber identity (IMSI); 
         [0165]    2) Trigger-Recipient-ID: trigger message recipient identifier, which is the application port identifier of the UE; 
         [0166]    3) M2M-SP-ID: the identifier of the M2M service provider subscribed to by the UE; 
         [0167]    4) AE-ID: the identifier of AE of the M2M service provider, which is the IN-AE identifier; 
         [0168]    S 802 : the equipment registration request of the UE is received by the MTC-IWF, the identifier of the CSE in the server, to which the AE is registered, is searched for in an local information storage according to the identifier of the AE, which is the identifier of the IN-CSE, the subscription information request is sent to the HSS. The request message including: 
         [0169]    1) Device-ID: the identifier of the UE in the underlying network; 
         [0170]    2) M2M-SP-ID: the identifier of the M2M service provider; 
         [0171]    3) CSE-ID: the identifier of the CSE in the UE; 
         [0172]    S 803 : the subscription information request sent by the MTC-IWF is received by the HSS, according to the identifier of the UE in the underlying network and the identifier of the M2M service provider, the M2M external identifier (M2M-Ext-ID) and routing information of corresponding UE are retrieved, the authentication of the CSE in the server is searched for according to the identifier of the CSE in the server, and then fed back to the MTC-IWF through the subscription information response; 
         [0173]    a list of one-to-one mapping relationship between the M2M external identifier of the UE and the identifier of the M2M service provider subscribed to by the UE can be created in an information storage of the HSS in application; 
         [0174]    S 804 : the subscription information response sent by the HSS is received by the MTC-IWF, the routing information of the UE and the authentication of the CSE in the server are cached, and the equipment registration request is sent to the CSE in the server according to the identifier of the CSE in the server. The request message including: 
         [0175]    1) M2M-Ext-ID: the M2M external identifier of the UE; 
         [0176]    2) Trigger-Recipient-ID: the application port identifier of the UE; 
         [0177]    3) AE-ID: the identifier of the AE; 
         [0178]    S 805 : the equipment registration request sent by the MTC-IWF is received by the CSE in the server, and after the equipment of the UE is authenticated, the registration request is sent to the AE according to the identifier of the AE. The request message includes: 
         [0179]    1) M2M-Ext-ID: the M2M external identifier of the UE; 
         [0180]    2) Trigger-Recipient-ID: the application port identifier of the UE; 
         [0181]    S 806 : the registration request sent by the CSE in the server is received by the AE, the binding relationship between the M2M external identifier of the UE, the trigger message recipient identifier and the identifier of the CSE in the UE is determined after the registration parameters of the UE are verified, and the registration response is fed back to the CSE in the server. The response message includes the identifier of the CSE in the UE; 
         [0182]    the list of the binding relationship list between the identifier of the CSE in the UE, which is the ASN/MN-CSE identifier, and the external identifier of the UE, the trigger message recipient identifier can be created in the information storage of the AE in application; 
         [0183]    S 807 : the registration response sent by the AE is received by the CSE in the server, and the state parameters of the UE are cached, the parameters including: 
         [0184]    1) CSE-ID: the identifier of the CSE in the UE; 
         [0185]    2) M2M-Ext-ID: the M2M external identifier of the UE; 
         [0186]    3) Trigger-Recipient-ID: the application port identifier of the UE; 
         [0187]    4) State: registration (/connection/sleep/power off/logout); 
         [0188]    the equipment registration response is sent to the MTC-IWF, the response message including: 
         [0189]    1) M2M-Ext-ID: the M2M external identifier of the UE; 
         [0190]    2) Local CSE-ID: the identifier of the CSE in the server; 
         [0191]    3) Remote CSE-ID: the identifier of the CSE in the UE (optional parameter); 
         [0192]    S 808 : the equipment registration response sent by the CSE in the server is received by the MTC-IWF, then sent to the CSE in the UE according to the identifier of the UE in the underlying network. The response message including: 
         [0193]    1) Device-ID: the identifier of the UE in the underlying network; 
         [0194]    2) Remote CSE-ID: the identifier of the CSE in the server; 
         [0195]    3) Local CSE-ID: the identifier of the CSE in the UE (optional parameter); 
         [0196]    S 809 : the equipment registration response sent by the MTC-IWF is received by the CSE in the UE, and the registration process is finished; 
         [0197]    S 810 : the resource operation request is sent to the CSE in the server by the AE. The request message including the identifier of the CSE in the UE; 
         [0198]    S 811 : the information in the request message is cached by the CSE in the server, the state information of the UE is checked according to the identifier of the CSE in the UE, then the equipment triggering request is sent to the MTC-IWF. The request message including the M2M external identifier of the UE, the application port identifier of the UE and the identifier of the CSE in the server; 
         [0199]    S 812 : according to the identifier of the CSE in the server and the M2M external identifier of the UE, the authentication of the CSE, the identifier and routing information of the UE in the underlying network are locally searched for, the equipment triggering request receipt conformation is fed back to the CSE in the server, and the equipment triggering process is executed in the underlying network. 
         [0200]    As mentioned above, in the disclosure, the equipment registration request is sent to the MTC-IWF by the CSE in the UE, and the registration request includes the identifier of the UE in the underlying network, the application port identifier of the UE, the identifier of the M2M service provider subscribed to by the UE, and the identifier of the AE of the M2M service provider. Thus, the M2M external identifier of the UE can be requested from the HSS by the MTC-IWF according to the identifier of the UE in the underlying network and the identifier of the M2M service provider subscribed to by the UE, and the M2M external identifier of the UE can be obtained by the CSE in the server in subsequent registration process, so as to finish the registration process of the UE and realize the triggering of the UE by the server. 
         [0201]    It is understood by those skilled in the art that: all or part of the steps, implementing the above method, can be implemented using a hardware associated to instructions of a program. The program, which can be stored in a computer readable storage medium, is executed for performing the steps included in the method embodiment above. The storage medium includes all kinds of mediums capable of storing program codes, such as a portable storage device, a random access memory (RAM), a read-only memory (ROM), a disc or an optical disc etc. 
         [0202]    Or, when the integrated units of the disclosure are implemented in a form of software functional modules and sold or used as independent products, it can also be stored in a computer readable storage medium. Based on this, the technical solution of the disclosure or the part contributed to related art can be embodied in a form of software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (it can be a personal computer, a server or a network device etc.) to execute all or part of the method in each embodiment of the disclosure. And the storage medium includes all kinds of mediums capable of storing a program code, such as a portable storage device, a RAM, a ROM, a disc or an optical disc etc. 
         [0203]    The above is only the detailed embodiments of the disclosure, not intent to limit the scope of protection of the disclosure, those skilled in the art can make various variations and replacements to the disclosure within the technical range of the disclosure, the variations and replacements fall within the scope of protection of the disclosure. Thus, the scope of protection of the disclosure is the scope of the claims of the disclosure.