WO2012024941A1 - 一种m2m业务的优化方法及装置 - Google Patents

一种m2m业务的优化方法及装置 Download PDF

Info

Publication number
WO2012024941A1
WO2012024941A1 PCT/CN2011/073735 CN2011073735W WO2012024941A1 WO 2012024941 A1 WO2012024941 A1 WO 2012024941A1 CN 2011073735 W CN2011073735 W CN 2011073735W WO 2012024941 A1 WO2012024941 A1 WO 2012024941A1
Authority
WO
WIPO (PCT)
Prior art keywords
feature
supported
activated
activatable
terminal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2011/073735
Other languages
English (en)
French (fr)
Inventor
时书锋
陈中平
闫学霞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2012024941A1 publication Critical patent/WO2012024941A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/06—Registration at serving network Location Register, VLR or user mobility server
    • H04W8/065—Registration at serving network Location Register, VLR or user mobility server involving selection of the user mobility server

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for optimizing an M2M service.
  • M2M Machine to Machine business is one of the most representative communication services.
  • M2M services are mostly carried on the CS/PS domain (ie, circuit bearer domain/data domain) network.
  • CS/PS domain ie, circuit bearer domain/data domain
  • the users of the M2M service are the same as the ordinary network service users, and there is no clear distinction.
  • network services the number of users of M2M services continues to increase. When the number of users reaches a certain level, it will bring huge impact to the network.
  • 3GPP 3rd Generation Partnership Project
  • HSS Home Subscriber Server
  • HLR Home Location Register
  • the network can determine which features should be adopted according to the features supported by the mobility management unit capability, the features supported by the terminal, and the characteristics of the user subscription. Feature, and perform network optimization policies and M2M services; industry users or operators can also activate and deactivate M2M services or different features through interfaces such as WEB (Internet) and OMC (Operations & Maintenance Center).
  • WEB Internet
  • OMC Operaations & Maintenance Center
  • the existing optimization method of the M2M service generally includes the following steps:
  • Step 1 The UE (User Equipment, Terminal) sends a NAS (Network Access Service message between the network and the terminal to the MME (Mobility Management Entity)/SGSN (Servicing GPRS Support Node).
  • the message is transmitted between the terminal and the network, and the message may include the Feature supported by the UE, the IMSI (International Mobile Subscriber Identity) of the UE, and the like;
  • Step 2 After receiving the NAS message, the MME/SGSN routes to the HSS/HLR to which the UE belongs according to the IMSI and the like of the UE.
  • Step 3 The MME/SGSN sends a ULR (UpdateloactionRequest) message to the HSS/HLR, where the message may carry the MME/SGSN capability (mobility management unit capability);
  • ULR UpdateloactionRequest
  • Step 4 After receiving the ULR, the HSS/HLR determines, according to the MME/SGSN capability, the activated Feature supported by the MME/SGSN capability in the Feature of the user subscription, and uses the Feature as a Feature that can be delivered by the user.
  • Step 5 The HSS/HLR sends the Feature that can be delivered to the corresponding MME/SGSN.
  • Step 6 the MME/SGSN detects whether the Feature delivered by the HSS/HLR matches the Feature supported by the MME/SGSN capability;
  • Step 7 the MME/SGSN notifies the HSS/HLR of the Feature that is not supported by the MME/SGSN operation capability but is activated by the user through a NOR (notify request) message;
  • Step 8 The HSS/HLR returns a response message to the MME/SGSN.
  • Step 9 The HSS/HLR notifies the MTC Server (Machine Type Communications Server, Machine Type Communications Server) / Web (Internet) / OMC (Operations & Maintenance Center) for the Feature that is not supported by the MME/SGSN capability but is activated by the user. Maintenance center)
  • MTC Server Machine Type Communications Server
  • Web Internet
  • OMC Operations & Maintenance Center
  • Step 10 The MTC Server/Web/OMC performs deactivation processing on the Feature that is not supported by the MME/SGSN but is activated by the user, and the MME/SGSN notifies the UE that the connection is successful.
  • the M2M service management entity cannot know the optimization scheme supported by the UE and/or the MME/SGSN, which will make the M2M The business is not optimized, and even the M2M service cannot be effectively executed. Summary of the invention
  • the embodiment of the present invention provides an optimization method and device for the M2M service, so that the M2M service management entity can timely learn the optimization scheme supported by the UE and/or the MME/SGSN, so that the M2M service is optimized.
  • An optimization method for M2M (machine-to-machine communication) services including:
  • At least one of the feature supported by the terminal and the feature supported by the mobility management unit is transmitted to the M2M service management entity.
  • An optimization method for M2M services including:
  • an activatable feature refers to a feature supported by both the terminal and the mobility management unit capability in the feature of the user subscription of the M2M service, after removing the feature that has been activated or is being activated.
  • An optimization method for M2M services including:
  • the activatable feature refers to a feature of the user signing the M2M service, after removing the feature that has been activated or being activated, the terminal and The feature that the mobility management unit capability supports;
  • the deactivated feature refers to a feature that is not supported by the terminal and the feature that is not supported by the mobility management unit capability in the activated feature of the M2M service;
  • An activatable feature and/or a deactivating feature is sent to the M2M service processing entity.
  • An optimization method for M2M services including:
  • the activatable feature refers to a feature that is supported by the terminal of the M2M service, after the feature that has been activated or is activated, is supported by the terminal and the mobility management unit.
  • the deactivating feature refers to a feature that is not supported by a feature and/or a mobility management unit capability that is not supported by the terminal in an activated feature of the M2M service;
  • An optimization device for M2M services including:
  • Supporting a feature obtaining unit configured to acquire at least one of a feature supported by the terminal and a feature supported by the mobility management unit;
  • a feature sending unit configured to send, to the M2M service management entity, at least one of a feature supported by the terminal acquired by the support feature acquiring unit and a feature supported by the mobility management unit capability.
  • An optimization device for M2M services including:
  • Supporting a feature receiving unit configured to receive at least one of a feature supported by the terminal and a feature supported by the mobility management unit;
  • An activatable feature determining unit configured to perform at least one of a feature supported by the terminal and a feature supported by the mobility management unit capability acquired by the support feature receiving unit, and a feature of the user subscription and/or a business strategy of the operator Determining an activatable feature and performing an activation process on the activatable feature; wherein the activatable feature refers to a feature that is subscribed by a user of the M2M service, after removing the activated or active feature, the terminal and the mobility management unit Features that are supported by capabilities.
  • An optimization device for M2M services including:
  • a feature determination processing unit configured to determine an activatable feature and/or deactivate according to at least one of a feature supported by the terminal and a feature supported by the mobility management unit capability, and a feature of the user subscription and/or an operator's business policy Feature, performing activation processing on the activatable feature and/or deactivating the deactivated feature;
  • the activatable feature refers to a feature that is supported by both the terminal and the mobility management unit capability after the feature that has been activated or is activated in the feature of the user subscription of the M2M service;
  • the deactivated feature refers to the M2M service.
  • an optimized feature sending unit configured to send, to the M2M service processing entity, the activatable feature and/or the deactivating feature determined by the feature determining processing unit.
  • An optimization device for M2M services including:
  • An optimized feature receiving unit configured to receive an activatable feature and/or a deactivating feature; wherein the activatable feature refers to a feature that is subscribed by a user of the M2M service, after removing the feature that has been activated or being activated, the terminal and the mobile Features that are supported by the capabilities of the STP; the deactivated features are features that are not supported by features not supported by the terminal and/or capabilities of the mobility management unit in the activated features of the M2M service;
  • an optimized feature processing unit configured to perform an activation process on the activatable feature received by the optimized feature receiving unit and/or to deactivate the deactivated feature.
  • the M2M service optimization method and apparatus send at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability to the M2M service management entity
  • the M2M service management entity refers to an entity that manages the M2M service, and the corresponding M2M service management entity may include, but is not limited to, the MTC Server/Web/OMC, so that the M2M service management entity can know the UE and/or in time.
  • the optimization scheme supported by the MME/SGSN so that the M2M service is optimized.
  • FIG. 1 is a schematic flowchart of processing of an existing M2M service optimization method according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart 1 of a processing procedure of an M2M service optimization method according to an embodiment of the present invention
  • FIG. 3 is a second schematic diagram of a processing flow of an M2M service optimization method according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart 3 of a processing flow of an M2M service optimization method according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram 4 of a processing flow of an M2M service optimization method according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram 5 of a processing flow of an M2M service optimization method according to an embodiment of the present disclosure
  • FIG. 7 is a schematic flowchart of a process flow of an M2M service optimization method according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart of a processing flow of an M2M service optimization method according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a processing flow of an M2M service optimization method according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a processing flow of an M2M service optimization method according to an embodiment of the present invention.
  • FIG. 11 is a schematic flowchart of a processing flow of an M2M service optimization method according to an embodiment of the present invention.
  • FIG. 12 is a schematic flowchart of a processing flow of an M2M service optimization method according to an embodiment of the present invention.
  • FIG. 13 is a schematic flowchart of a processing flow of an M2M service optimization method according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram 1 of an M2M service optimization apparatus according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram 2 of an M2M service optimization apparatus according to an embodiment of the present disclosure.
  • FIG. 16 is a schematic structural diagram 3 of an M2M service optimization apparatus according to an embodiment of the present disclosure.
  • FIG. 17 is a schematic structural diagram 4 of an M2M service optimization apparatus according to an embodiment of the present disclosure.
  • FIG. 18 is a schematic structural diagram 5 of an M2M service optimization apparatus according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic structural diagram 6 of an M2M service optimization apparatus according to an embodiment of the present disclosure.
  • FIG. 20 is a schematic structural diagram 7 of an M2M service optimization apparatus according to an embodiment of the present disclosure.
  • FIG. 21 is a schematic structural diagram 8 of an M2M service optimization apparatus according to an embodiment of the present disclosure.
  • FIG. 22 is a schematic structural diagram IX of an M2M service optimization apparatus according to an embodiment of the present invention
  • FIG. 23 is a schematic structural diagram 10 of an M2M service optimization apparatus according to an embodiment of the present disclosure
  • FIG. 24 is a schematic structural diagram 11 of an M2M service optimization apparatus according to an embodiment of the present invention. Concrete
  • the existing MME/SGSN or the HSS/HLR does not send the Feature supported by the UE and the Feature supported by the MME/SGSN capability to the M2M service management entity, so that the M2M service management entity cannot know the UE and/or the MME/
  • the optimization scheme supported by the SGSN will not optimize the M2M service, and even the M2M service cannot be effectively executed.
  • the specific implementation process of the M2M service optimization method provided by the embodiment of the present invention relates to an M2M service communication entity (the corresponding M2M service communication entity may include, but is not limited to, the MME/SGSN or the HSS/HLR), and the M2M service management entity ( The corresponding M2M service management entity may include, but is not limited to, MTC Server/Web/OMC.
  • the terminal described in the embodiment of the present invention may include a communication device such as a mobile phone, a PDA (PDA), various smart phones, and the like, and may also include other electrical devices installed with an M2M service terminal, such as a notebook computer. Desktop, camera, washing machine, air conditioner, rice cooker, etc.
  • the terminal in the embodiment of the present invention includes, but is not limited to, the above-described device, and the following description is made by way of example only, but does not constitute a limitation of the present invention.
  • the corresponding M2M service communication entity in the embodiment of the present invention and the specific processing procedure that the M2M service management entity needs to perform are respectively described below.
  • the operation performed by the corresponding M2M service communication entity may specifically include the following steps:
  • Step 21 Obtain at least one of a Feature supported by the UE and a Feature supported by the MME/SGSN capability.
  • at least one of the Feature of the corresponding UE supported Feature and MME/SGSN capability support may include:
  • the MME/SGSN acquires at least one of a Feature supported by the UE and a Feature supported by the MME/SGSN capability;
  • the Feature supported by the MME/SGSN capability may include a Short Messaging Service (SMS) feature, a PS only (Packet Switch only) , only the packet domain) Feature, Anti-theft Feature, Group Management Feature, Time Control Feature, Low Mobility Feature, Monitoring Feature, Online Data Transfer Feature, Offline Data Transfer Feature, etc.
  • SMS Short Messaging Service
  • PS only Packet Switch only
  • M2M defined feature is obvious, so no need
  • the MME/SGSN can acquire the Feature supported by the UE carried in the message by receiving the NAS message sent by the UE.
  • the Feature supported by the UE may include the Feature for SMS.
  • Embodiment 1 It is assumed that an M2M service terminal M1 supports the anti-theft feature and the group management feature, and the MME/SGSN that provides the M2M service terminal M1 supports the anti-theft feature and the time control feature, and the M2M service terminal M1 subscribes to the feature.
  • the MME/SGSN that provides the service to the M2M service terminal M1 can receive the NAS message sent by the M2M service terminal M1, and obtain the Feature supported by the M2M service terminal M1 from the message. (corresponding to the M2M service terminal Feature supported by M1 can include anti-theft feature and group management feature);
  • the HSS/HLR acquires at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability;
  • the HSS/HLR may obtain at least one of the Feature supported by the Feature and the MME/SGSN capability supported by the UE by receiving the ULR message sent by the MME/SGSN, and the Feature supported by the corresponding UE may be supported by the corresponding MME/SGSN capability.
  • the corresponding MME/SGSN may receive the NAS message sent by the UE, and obtain the Feature supported by the UE, and then carry the Feature supported by the UE and the Feature transmission supported by the MME/SGSN capability in the ULR message.
  • the HSS/HLR can receive the ULR message, and obtain the Feature supported by the UE and the Feature supported by the MME/SGSN capability;
  • Embodiment 2 Assuming that an M2M service terminal M2 supports the monitoring feature and the PS only Feature, the MME/SGSN serving the M2M service terminal M2 can support the monitoring feature and the time control feature, and the feature signed by the M2M service terminal M1 can include The MME/SGSN that provides the service to the M2M service terminal M2 can receive the NAS message sent by the M2M service terminal M2, and obtain the feature supported by the M2M service terminal M2, and then carry the feature in the ULR message.
  • the Feature supported by the M2M service terminal M2 and the Feature supported by the MME/SGSN capability are sent to the HSS/HLR to which the M2M service terminal M2 belongs; the HSS/HLR to which the M2M service terminal M2 belongs can receive the ULR message, and The Feature supported by the M2M service terminal M2 is obtained (the Feature supported by the M2M service terminal M2 may include the monitoring Feature and the PS only Feature) and the Feature supported by the corresponding MME/SGSN capability (the Feature supported by the corresponding MME/SGSN capability may include monitoring Feature and Time Control Feature);
  • Step 22 Send at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability to the M2M service management entity.
  • the corresponding M2M service management entity may include MTC Server/Web/OMC, and the like;
  • the step may specifically include: (1) For the case where the MME/SGSN is an M2M service communication entity, the MME/SGSN to the MTC
  • Server/Web/OMC or the like transmitting at least one of a Feature supported by the UE and a Feature supported by the MME/SGSN capability;
  • the MME/SGSN when the MME/SGSN is an M2M service communication entity, the MME/SGSN obtains at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN, and the MME/SGSN sends the MTC Server/Web/ to the MTC Server/Web/ Transmitting, by the OMC, at least one of Feature supported by the Feature and MME/SGSN capabilities supported by the UE;
  • the MME/SGSN serving the M2M service terminal M1 obtains the Feature supported by the M2M service terminal M1 and the Feature supported by the MME/SGSN capability
  • the MME/SGSN may be the current M2M.
  • the MTC Server/Web/OMC that the service terminal M1 provides the service sends the Feature supported by the M2M service terminal M1 (the Feature supported by the M2M service terminal M1 may include the anti-theft feature and the group management feature) and the corresponding MME/SGSN capability support.
  • Feature the anti-theft feature and time control feature supported by the corresponding MME/SGSN capabilities
  • the HSS/HLR When the HSS/HLR is an M2M service communication entity, the HSS/HLR transmits at least one of the Feature Supported by the UE and the Feature and B MME/SGSN capability supported by the UE to the MTC Server/Web/OMC or the like/OMC. ;
  • the HSS/HLR when the HSS/HLR is an M2M service communication entity, the HSS/HLR acquires at least one of the feature supported by the UE and the Feature supported by the MME/SGSN capability, and the HSS/HLR sends the MSC Server/Web/ to the MTC Server/Web/ The OMC or the like transmits at least one of a Feature supported by the UE and a Feature supported by the MME/SGSN capability;
  • the M2M service terminal M2 belongs to the HSS/HLR
  • the M2M service end is obtained.
  • the HSS/HLR may send the Feature supported by the M2M service terminal M2 to the MTC Server/Web/OMC currently serving the M2M service terminal M2.
  • the Feature supported by the M2M service terminal M2 may include a Feature Feature and a PS Only Feature) and a Feature supported by the corresponding MME/SGSN capability (the Feature of the corresponding MME/SGSN capability support may include a monitoring Feature and a Time Control Feature).
  • the corresponding M2M service communication entity may further include the following operational steps in the specific implementation process:
  • Step 31 Obtain at least one of the feature supported by the UE and the feature supported by the MME/SGSN capability. Specifically, the technical solution of the step is completely the same as the technical solution described in step 21, and is not described here; Step 32: According to The feature supported by the UE, the Feature supported by the MME/SGSN capability, and the Feature subscribed by the user determine that the Feature cannot be used;
  • the corresponding unusable Feature refers to the Feature and/or MME/SGSN capabilities that are not supported by the UE in the Feature that has been activated or is being activated.
  • the step may specifically include:
  • the MME/SGSN saves according to the Feature supported by the UE and the Feature supported by the MME/SGSN capability acquired in step 31, and the MME/SGSN.
  • the feature signed by the user or the HSS/HLR is determined to be unavailable for the Feature; corresponding Embodiment 1:
  • the MME/SGSN is the M2M service communication entity, the M2M service terminal M1 is provided.
  • the MME/SGSN of the service according to the Feature supported by the M2M service terminal M1 obtained in step 31 (the Feature supported by the M2M service terminal M1 may include an anti-theft feature and a group management feature) and a feature supported by the corresponding MME/SGSN capability (corresponding The feature supported by the MME/SGSN capability may include an anti-theft feature and a time-controlled feature, and a feature signed by the MME/SGSN or issued by the HSS/HLR (the feature signed by the M2M service terminal M1 may include anti-theft).
  • Use Feature and Group Management Feature to determine that Feature is not available (the corresponding Unavailable Feature includes group management Feature and Time) Control Feature);
  • step 31 After performing step 31, for the case where the HSS/HLR is an M2M service communication entity, the HSS/HLR according to the Feature and MME/SGSN capability supported by the UE obtained in step 31, and the HSS/HLR The saved activated feature determines that the Feature cannot be used;
  • step 31 After the step 31 is performed, if the HSS/HLR is an M2M service communication entity, the HSS/HLR to which the M2M service terminal M2 belongs is supported by the M2M service terminal M2 obtained in step 31.
  • the Feature supported by the M2M service terminal M2 may include a monitoring Feature and a PS Only Feature
  • a Feature supported by the corresponding MME/SGSN capability (the Feature supported by the corresponding MME/SGSN capability may include a monitoring Feature and a Time Control Feature)
  • the HSS/ The activated feature saved by the HLR (the feature signed by the M2M service terminal M1 may include the monitoring feature and the PS only Feature) to determine that the Feature is not available (the corresponding unusable Feature includes the PS only Feature and the Time Control Feature);
  • Step 33 Send the unavailable feature to the M2M service management entity.
  • the corresponding M2M service management entity may include MTC Server/Web/OMC, and the like;
  • this step is basically similar to step 22, and the unavailable features and steps in this step can be used.
  • At least one of the feature supported by the UE and the feature supported by the MME/SGSN capability in the 22 is simultaneously sent to the MTC Server/Web/OMC, etc., and the specific implementation may include:
  • the MME/SGSN When the MME/SGSN is an M2M service communication entity, the MME/SGSN sends at least one of the Feature and MME/SGSN capability supported by the UE to the MTC Server/Web/OMC, and the Use Feature;
  • the M2M service is used.
  • the MME/SGSN to which the terminal M1 provides the service transmits the Feature supported by the M2M service terminal M1 to the MTC Server/Web/OMC or the like currently serving the M2M service terminal M2.
  • the Feature supported by the M2M service terminal M1 may include the anti-theft feature and the Feature.
  • the Feature Management Feature and the Feature of the corresponding MME/SGSN Capability Support (the Feature of the corresponding MME/SGSN capability support may include at least one of the theft prevention feature and the time control feature), and the unavailable feature (the corresponding unusable feature) Feature includes group management feature and time control feature);
  • the HSS/HLR is an M2M service communication entity
  • at least one of the feature supported by the UE and the Feature supported by the MME/SGSN capability is sent by the HSS/HLR to the MTC Server/Web/OMC, and the Use Feature;
  • the HSS/HLR is an M2M service communication entity
  • the HSS/HLR to which the M2M service terminal M2 belongs sends the MTC Server/Web/OMC that is currently serving the M2M service terminal M2.
  • the Feature supported by the M2M service terminal M2 (the Feature supported by the M2M service terminal M2 may include the Feature Feature and the PS only Feature) and the Feature supported by the corresponding MME/SGSN capability (the Feature supported by the corresponding MME/SGSN capability may include monitoring the Feature and time)
  • At least one of the Control Features, and the Unusable Feature (the corresponding Unusable Feature includes the PS Only Feature and the Time Control Feature).
  • the specific operation steps of the corresponding M2M service communication entity may further include:
  • the MME/SGSN receives an activatable Feature and/or deactivates the Feature, and notifies the HSS/HLR of the activatable Feature and/or Deactivating Feature; the HSS/HLR is further activated Feature performs activation processing and/or deactivates the deactivated Feature;
  • the activateable feature refers to a Feature that is supported by both the UE and the MME/SGSN after removing the feature that has been activated or being activated in the Feature subscribed by the user of the M2M service;
  • the deactivated Feature refers to a Feature and/or MME/SGSN capability that is not supported by the UE in the activated Feature of the M2M service;
  • the MME/SGSN may first receive the activateable Feature and/or the deactivated Feature, and then determine to receive according to at least one of a Feature supported by the UE saved in the MME/SGSN and a Feature supported by the MME/SGSN capability.
  • the activated feature can be activated, and if activated, notify the HSS/HLR of the activatable Feature, and the HSS/HLR activates the activatable Feature again; if not, The activatable Feature is also notified to the HSS/HLR as a deactivated Feature, and the HSS/HLR further deactivates the deactivated Feature; for the deactivated Feature received by the MME/SGSN, the Notifying the HSS/HLR that the HSS/HLR further deactivates the deactivated Feature;
  • the MME/SGSN that provides the service to the M2M service terminal M1 may first receive the activated feature returned by the MTC Server/Web/OMC currently serving the M2M service terminal M1 (the corresponding activatable Feature may be Including anti-theft features and/or de-activating features (the corresponding de-activating features may include group management features and time-control features), and then according to the UE-supported features and MME/SGSN capabilities saved in the MME/SGSN At least one of the supported Feature determines whether the received activatable Feature (the corresponding activatable Feature may include a theft feature) can be activated, because the activatable Feature can be activated, so the activateable Feature is notified to the HSS /HLR, the HSS/HLR further activates the activatable Feature (the corresponding activatable Feature may include an anti-theft feature); for the deactivated Feature received by the MME/SGSN, the HSS may be directly notified to the
  • the HSS/HLR directly receives an activateable Feature and/or deactivates the Feature, performs activation processing on the activatable Feature, and/or deactivates the deactivated Feature;
  • the HSS/HLR may first receive the activateable Feature and/or deactivate the Feature, and then determine to receive according to at least one of a Feature supported by the UE saved in the HSS/HLR and a Feature supported by the MME/SGSN capability. Whether the activated feature can be activated, if activated, the activation feature is activated; if not, the activatable feature is also used as the deactivateable feature, and the can be deactivated Activate the Feature for deactivation; for the deactivated Feature received by the HSS/HLR, the deactivation process can be directly performed;
  • the HSS/HLR to which the M2M service terminal M2 belongs may first receive an active feature returned by the MTC Server/Web/OMC currently serving the M2M service terminal M2 (the corresponding activatable Feature may include Monitor Feature and/or Deactivate Feature (the corresponding Deactivated Feature can include PS Only Feature and Time Control Feature), and then support the Feature supported by the UE in the HSS/HLR and the Feature supported by the MME/SGSN capability.
  • the corresponding activatable Feature may include Monitor Feature and/or Deactivate Feature (the corresponding Deactivated Feature can include PS Only Feature and Time Control Feature)
  • At least one of the determined activateable features (the corresponding activatable features may include a monitoring feature) can be activated, because the activatable feature can be activated, so the activatable feature can be activated (the corresponding activatable feature can be activated) Including the monitoring feature for activation processing; for the deactivating Feature received by the HSS/HLR (the corresponding deactivated feature can include the PS only Feature and the Time Control Feature), the deactivation process can be directly performed.
  • the operation performed by the M2M service management entity corresponding to the foregoing M2M service communication entity may specifically include the following steps:
  • Step 41 Receive at least one of a feature supported by the UE and a Feature supported by the MME/SGSN capability.
  • the MTC Server/Web/OMC and the like receive at least one of a Feature supported by the UE and a Feature supported by the MME/SGSN capability.
  • the MTC Server/Web/OMC that currently provides the service to the M2M service terminal M1 receives the Feature supported by the M2M service terminal M1 sent by the MME/SGSN serving the M2M service terminal M2 (the M2M service)
  • the Feature supported by the terminal M1 may include a feature for the anti-theft feature and a group management feature and a feature supported by the corresponding MME/SGSN capability (the feature supported by the corresponding MME/SGSN capability may include an anti-theft feature and a time-controlled feature);
  • the MTC Server/Web/OMC that is currently serving the M2M service terminal M2 receives the Feature supported by the M2M service terminal M2 sent by the HSS/HLR to which the M2M service terminal M2 belongs (the M2M service terminal)
  • the Feature supported by M2 may include a Feature Feature and a PS Only Feature) and a Feature supported by the corresponding MME/SGSN capability (a feature supported by the corresponding MME/SGSN capability may include a monitoring Feature and a Time Control Feature);
  • Step 42 Determine an activatable feature according to at least one of a feature supported by the UE and a feature supported by the MME/SGSN capability, and a feature of the user subscribed to the feature and/or the operator, and perform the feature on the activatable feature.
  • the corresponding activateable Feature refers to the Feature that is supported by the UE and the MME/SGSN capability after the Feature that has been activated or activated by the user in the M2M service.
  • the MTC Server/Web/OMC or the like determines, according to at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability, and the Feature and/or the operator's management policy signed by the user, the Activateable Feature is determined, and Activating the activation of the activateable feature;
  • the MTC Server/Web/OMC that is currently serving the M2M service terminal M1 and the like supported by the M2M service terminal M1 (the Feature supported by the M2M service terminal M1 may include the anti-theft feature and group management) Feature) and the corresponding MME/SGSN capability supported features (corresponding The Feature supported by the MME/SGSN capability may include at least one of a Security Feature and a Time Control Feature, and a Feature that the user subscribes to (the corresponding user-signed Feature may include an Anti-Theft Feature and a Group Management Feature) and/or an operation.
  • the business strategy of the business may include no longer determining whether the activated feature is activated for the activated feature. Determining the activatable feature (the corresponding activatable feature may include the anti-theft feature), and The activation feature can be activated for activation;
  • the MTC Server/Web/OMC currently serving the M2M service terminal M2 and the like supported by the M2M service terminal M2 (the Feature supported by the M2M service terminal M2 may include the monitoring Feature and the PS only Feature) And the Feature supported by the corresponding MME/SGSN capability (the Feature of the corresponding MME/SGSN capability can include at least one of the Monitoring Feature and the Time Control Feature), and the Feature subscribed by the user (the corresponding user-signed Feature can include the Monitoring Feature) And PS only Feature) and/or the operator's business strategy (the corresponding operator's business strategy may include determining that the activated feature is no longer determined for the activated feature) (the corresponding activatable feature can be Including monitoring the feature), and activating the activatable feature;
  • the step may further include determining a process of deactivating the feature, the specific processing content of which is as follows: according to at least one of a Feature supported by the UE and a Feature supported by the MME/SGSN capability, And the user-signed feature and/or the operator's business strategy determines that the feature can be deactivated, and the deactivated feature is deactivated;
  • the corresponding deactivated Feature refers to a Feature that is not supported by the UE and a Feature that is not supported by the MME/SGSN capability in the activated Feature of the M2M service;
  • the MTC Server/Web/OMC or the like determines that the Feature can be deactivated according to at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability, and the Feature and/or the operator's management policy of the user subscription, Deactivating the deactivated feature;
  • the MTC Server/Web/OMC that is currently serving the M2M service terminal M1 and the like supported by the M2M service terminal M1 (the Feature supported by the M2M service terminal M1 may include the anti-theft feature and group management) Feature) and the corresponding MME/SGSN capability supported Feature (the corresponding MME/SGSN capability supported feature may include anti-theft feature and time control feature), and the user-signed feature (the corresponding user-signed feature may include Anti-theft feature and group management feature and/or operator's business strategy (the corresponding operator's business strategy may include determining whether the activated feature is deactivated or not). Determining the deactivateable feature (corresponding The deactivated feature may include a time control feature and a group management feature, and deactivate the deactivated feature;
  • the MTC Server/Web/OMC currently serving the M2M service terminal M2 and the like supported by the M2M service terminal M2 (the Feature supported by the M2M service terminal M2 may include the monitoring Feature and the PS only Feature) And the Feature supported by the corresponding MME/SGSN capability (the Feature of the corresponding MME/SGSN capability can include at least one of the Monitoring Feature and the Time Control Feature), and the Feature subscribed by the user (the corresponding user-signed Feature can include the Monitoring Feature) And PS only Feature) and/or the operator's business strategy (the corresponding operator's business strategy may include determining whether the activated Feature is deactivated or not).
  • the Feature may include a PS only Feature and a Time Control Feature, and deactivate the Deactivated Feature.
  • the corresponding M2M service communication entity may further include the following steps in the specific implementation process:
  • Step 51 Receive at least one of Feature and MME/SGSN capability supported by the UE, and not use Feature;
  • the corresponding unusable Feature means that the UE does not support the Feature that has been activated or is being activated. Feature and/or MME/SGSN capabilities are not supported by Feature;
  • the unusable Feature may be received at the same time as receiving at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN, and the specific processing is similar to that in Step 41, and is not described in detail;
  • Step 52 Determine, according to at least one of a feature supported by the UE and a feature supported by the MME/SGSN capability, and at least one of a feature signed by the user and an operation policy of the operator, and the unavailable feature is determined to be activated. Feature, and activation processing of the activatable feature;
  • the unavailable feature is used as an auxiliary condition for determining an activateable feature and/or a deactivateable feature; for example, if a feature is not available, then It can be determined that this feature is a deactivated Feature;
  • the MTC Server/Web/OMC that is currently serving the M2M service terminal M1 receives the Feature and the corresponding MME supported by the M2M service terminal M1 sent by the MME/SGSN serving the M2M service terminal M2. At least one of the features supported by the SGSN capability, and the feature not available; the corresponding MTC Server/Web/OMC, etc.
  • the Feature supported by the M2M service terminal M1 and the Feature supported by the corresponding MME/SGSN capability are not available Use Feature (the corresponding Unavailable Feature can include Time Control Feature and Group Management Feature), as well as the user's contracted Feature and/or the operator's business strategy (the corresponding operator's business strategy can include if the Feature is not available)
  • Directly judged to be deactivated Feature Determine the activateable Feature (the corresponding activateable Feature can include the theft feature) and/or deactivate the Feature (the corresponding deactivated Feature can include the Time Control Feature and the Group Management Feature) And performing an activation process on the activatable feature for deactivating the Feature is deactivated;
  • the MTC Server/Web/OMC that is currently serving the M2M service terminal M2 receives the Feature and the corresponding MME/SGSN supported by the M2M service terminal M2 sent by the HSS/HLR to which the M2M service terminal M2 belongs. At least one of the capabilities supported by the capability, and the feature not available; the corresponding MTC Server/Web/OMC, etc.
  • the corresponding unusable Feature can include PS only Feature and Time Control Feature
  • the corresponding operator's business strategy can include directly determining if it is not available) Yes to deactivate the Feature
  • Deactivate the Feature the corresponding Activateable Feature can include the Monitoring Feature
  • Deactivate the Feature the corresponding Deactivated Feature can include the PS Only Feature and the Time Control Feature
  • Deactivating the Feature for activation processing deactivating the deactivated Feature Management.
  • the M2M business management entity determines that the Feature can be activated and/or the Feature can be deactivated
  • the M2M service management entity may also perform the following operations: MTC Server/Web/OMC, etc., sending the activation
  • the MTC Server/Web/OMC or the like currently serving the M2M service terminal M1 sends the activateable Feature to the corresponding MME/SGSN or HSS/HLR (the corresponding activatable Feature may include the anti-theft feature) And/or the deactivated Feature (the corresponding deactivated Feature may include a Time Control Feature and a Group Management Feature);
  • the MTC Server/Web/OMC or the like currently serving the M2M service terminal M2 sends the activateable Feature to the corresponding MME/SGSN or HSS/HLR (the corresponding activatable Feature may include a monitoring feature) And/or the deactivated Feature (the corresponding deactivated Feature may include PS only
  • the M2M service optimization method provided by the embodiment of the present invention further includes another similar solution, so that the M2M service management entity learns the optimization scheme supported by the UE and/or the MME/SGSN.
  • the corresponding M2M service communication entities in the other solution and the specific parts that the M2M service management entity needs to perform will be separately described below. Process.
  • the operation performed by the corresponding M2M service communication entity may specifically include the following steps:
  • Step 61 Determine, according to at least one of a Feature supported by the UE and a Feature supported by the MME/SGSN capability, and a Feature and/or an operator's management policy that the user subscribes to determine an activateable Feature and/or a Deactivate Feature, and Deactivating an Feature for activation processing and/or deactivating the Deactivated Feature;
  • the corresponding activateable Feature refers to the Feature that is supported by the UE and the MME/SGSN capability after the Feature that has been activated or activated by the user in the M2M service.
  • the corresponding deactivated Feature refers to a Feature that is not supported by the UE and a Feature that is not supported by the MME/SGSN capability in the activated Feature of the M2M service;
  • the determining, according to at least one of the feature supported by the UE and the feature supported by the MME/SGSN capability, and the user-signed feature and/or the operator's business policy, determining the activatable feature and/or deactivating the feature may include:
  • the MME/SGSN determines the activatable Feature and/or the deactivateable Feature according to at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability, and the Feature and/or the operator's business policy signed by the user;
  • the third embodiment of the M2M service terminal M3 supports the anti-theft feature and the group management feature.
  • the MME/SGSN serving the M2M service terminal M3 may be included according to the Feature supported by the M2M service terminal M3.
  • the Feature supported by the M2M service terminal M3 may include an anti-theft feature and a group management feature.
  • a feature supported by the corresponding MME/SGSN capability may include at least one feature of the anti-theft feature and the time-controlled feature
  • a feature signed by the user (the corresponding user-signed feature may include anti-theft) Use Feature and Time to control the feature and/or the operator's business strategy (the corresponding operator's business strategy can include no longer determining whether the activated feature is activated for the activated feature).
  • Determine the activatable feature (corresponding activation) Feature can include anti-theft features and/or Feature activation (may deactivate the respective group management may include Feature Feature Feature and time control); or
  • the HSS/HLR determines the activatable feature and/or deactivates the feature according to at least one of the feature supported by the UE and the Feature supported by the MME/SGSN capability, and the feature signed by the user and/or the operator's business policy;
  • Embodiment 4 It is assumed that an M2M service terminal M4 supports a time control Feature and a PS only Feature, and an MME/SGSN serving the M2M service terminal M4 can support a monitoring feature and a time control feature, and the feature signed by the M2M service terminal M4 can be The monitoring feature and the time control feature are included; the HSS/HLR to which the M2M service terminal M4 belongs is based on the Feature supported by the M2M service terminal M4 (the Feature supported by the M2M service terminal M4 may include a time control Feature and a PS only Feature) and a corresponding MME.
  • the corresponding MME/SGSN capable features can include at least one of the monitoring feature and the time-controlled feature), as well as the user-signed feature (the corresponding user-signed feature can include the monitoring feature and the time-control feature) And/or the operator's business strategy (the corresponding operator's business strategy may include determining that the activated feature is no longer determined for the activated feature) (the corresponding activatable feature may include the time control feature) ) and / or can deactivate Feature (the corresponding deactivated Feature can include PS) Only Feature and Monitoring Feature; further, correspondingly performing activation processing on the activatable Feature and/or on the deactivated Feature Deactivation processing can include:
  • the MME/SGSN is an M2M service communication entity
  • the MME/SGSN determines the activateable Feature and/or deactivates the Feature
  • the Activated Feature and/or Deactivated Feature is sent to the HSS/HLR. And then the activation process of the activatable feature is performed by the HSS/HLR and/or the deactivation process is deactivated;
  • the MME/SGSN serving the M2M service terminal M3 determines an activateable Feature (the corresponding activatable Feature may include an anti-theft feature) and/or After the feature can be deactivated (the corresponding deactivated feature can include a group management feature and a time control feature), the activatable feature and/or the deactivated feature can be sent to the HSS/HLR to which the M2M service terminal M3 belongs. And the HSS/HLR to which the M2M service terminal M3 belongs to activate the activation of the activateable feature and/or deactivate the deactivated feature;
  • the HSS/HLR is an M2M service communication entity
  • the HSS/HLR determines that the Feature can be activated and/or the Feature can be deactivated
  • the HSS/HLR directly activates the Activated Feature and/or Deactivate the Feature for deactivation
  • the HSS/HLR to which the M2M service terminal M4 belongs determines an activateable Feature (the corresponding activatable Feature may include a time control Feature) and/or may After deactivating the Feature (the corresponding deactivated Feature may include the PS Only Feature and the monitoring Feature), the HSS/HLR directly activates the activation feature and/or deactivates the deactivated Feature;
  • Step 62 Send an activateable Feature and/or deactivate the Feature to the M2M service processing entity;
  • the corresponding M2M service management entity may include MTC Server/Web/OMC, but is not limited to these network elements;
  • the step may specifically include: (1) When the MME/SGSN is an M2M service communication entity, the MME/SGSN sends an activateable Feature and/or to the M2M service processing entity. Or you can deactivate the Feature;
  • the MME/SGSN may send an activateable Feature to the MTC Server/Web/OMC, etc. while transmitting the activateable Feature and/or the deactivateable Feature to the HSS/HLR. And/or can deactivate the Feature;
  • the MME/SGSN serving the M2M service terminal M3 may send an activateable Feature and/or to the HSS/HLR to which the M2M service terminal M3 belongs.
  • the Feature may be deactivated, and an activateable Feature may be sent to the MTC Server/Web/OMC or the like currently serving the M2M service terminal M3 (the corresponding activatable Feature may include an anti-theft feature) and/or the feature may be deactivated (
  • the corresponding deactivated Feature may include a group management feature and a time control feature;
  • the HSS/HLR is an M2M service communication entity
  • the HSS/HLR sends an activateable Feature and/or deactivates the Feature to the MTC Server/Web/OMC;
  • the HSS/HLR to which the M2M service terminal M4 belongs can be activated by sending an MTC Server/Web/OMC that is currently serving the M2M service terminal M4.
  • Feature the corresponding activatable feature can include a time-controlled feature
  • the feature can be deactivated (the corresponding deactivated feature can include the PS only Feature and the Feature).
  • the M2M service management entity corresponding to the foregoing M2M service communication entity may perform the following operations: Step 71: Receive an activateable Feature and/or deactivate the Feature;
  • the corresponding activateable Feature refers to the Feature that is supported by the UE and the MME/SGSN capability after the Feature that has been activated or activated by the user in the M2M service.
  • the corresponding deactivated Feature refers to a Feature that is not supported by the UE and a Feature that is not supported by the MME/SGSN capability in the activated Feature of the M2M service;
  • the MTC Server/Web/OMC or the like can receive the activatable Feature and/or the deactivated Feature; corresponding Embodiment 3: The MTC Server/Web/OMC or the like currently serving the M2M service terminal M3 can receive the activation.
  • Feature the corresponding activatable feature may include anti-theft features
  • de-activated features the corresponding de-activateable features may include group management features and time-controlled features
  • the MTC Server/Web/OMC or the like currently serving the M2M service terminal M4 can receive an activatable Feature (the corresponding activatable Feature can include a time control Feature) and/or can deactivate the Feature (corresponding Deactivated features can include PS only Feature and Monitoring Feature);
  • Step 72 perform activation processing on the inactivated feature and/or deactivate the deactivated feature
  • the MTC Server/Web/OMC or the like activates the activation theme and/or deactivates the deactivated feature
  • the MTC Server/Web/OMC or the like currently serving the M2M service terminal M3 performs activation processing on the activateable Feature (the corresponding activatable Feature may include an anti-theft feature) and/or
  • the feature can be deactivated (the corresponding deactivated feature can include a group management feature and a time control feature) for deactivation processing;
  • the MTC Server/Web/OMC or the like currently serving the M2M service terminal M4 performs activation processing on the activateable Feature (the corresponding activatable Feature may include a time control Feature) and/or The Feature can be deactivated (the corresponding Deactivated Feature can include the PS Only Feature and the Monitoring Feature) for deactivation.
  • the corresponding activatable Feature may include a time control Feature
  • the Feature can be deactivated (the corresponding Deactivated Feature can include the PS Only Feature and the Monitoring Feature) for deactivation.
  • the M2M service optimization method provided by the embodiment of the present invention is described by using an M2M service terminal M5 as an example. It is assumed that the M2M service terminal M5 supports the anti-theft feature and the time control feature, and the MME/SGSN that provides the M2M service terminal M5 supports the anti-theft feature, the time control feature and the PS only Feature, and the feature signed by the M2M service terminal M5 includes For the anti-theft feature, the time control feature and the PS only feature, the user-signed feature saved in the HSS/HLR to which the M2M service terminal M5 belongs is partially activated (the corresponding partially activated feature may include the time control feature and the PS).
  • Step 101 The UE sends a NAS message to the MME/SGSN, and the message may carry the IMSI of the UE, and the Feature and the like supported by the UE.
  • the corresponding M2M service terminal M5 sends a NAS message to the MME/SGSN serving the M2M service terminal M5, and the NAS message may carry the IMSI of the M2M service terminal M5, and the Feature supported by the M2M service terminal M5. And other information.
  • Step 102 After receiving the NAS message, the MME/SGSN first saves the Feature supported by the UE, and then determines the ULR of the HSS/HLR to which the UE belongs according to the IMSI of the UE.
  • the corresponding MME/SGSN first supports the M2M service terminal M5.
  • the feature is saved, and then the ULR of the HSS/HLR to which the M2M service terminal M5 belongs is determined according to the IMSI of the M2M service terminal M5;
  • Step 103 The MME/SGSN is routed to the HSS/HLR to which the UE belongs according to the ULR, and may carry the Feature supported by the UE and the Feature supported by the MME/SGSN capability in the corresponding ULR;
  • the corresponding MME/SGSN may be routed to the HSS/HLR to which the M2M service terminal M5 belongs according to the corresponding ULR; wherein the corresponding ULR may carry the corresponding Feature and corresponding MME/supported by the M2M service terminal M5. Feature supported by SGSN capability;
  • Step 104 After receiving the ULR, the HSS/HLR may determine, according to the Feature supported by the UE and the Feature supported by the MME/SGSN capability uploaded by the MME/SGSN, whether the Feature that has been activated in the Feature of the user subscription is available;
  • determining, according to the feature supported by the UE and the feature supported by the MME/SGSN capability, whether the feature that the user subscribes to can be used includes: determining whether the feature supported by the UE and/or the feature supported by the MME/SGSN capability is subscribed to the feature of the user. If the features supported by the UE and the features supported by the MME/SGSN are matched with the features subscribed by the user, the feature subscribed by the user can be used; if the feature supported by the UE does not match the feature signed by the user and/or If the feature supported by the MME/SGSN capability does not match the feature signed by the user, the feature signed by the user is unavailable.
  • the corresponding HSS/HLR may determine the Feature supported by the M2M service terminal M5 according to the Feature supported by the M2M service terminal M5 and the Feature supported by the MME/SGSN capability uploaded by the corresponding MME/SGSN (corresponding M2M)
  • the Feature supported by the service terminal M5 may include the Feature and Time Control Feature for burglary and the Feature supported by the MME/SGSN capability (the corresponding MME/SGSN capability supported Feature may include the Anti-Theft Feature, Time Control Feature, and PS Only Feature).
  • the feature that has been activated in the feature signed by the user may include the time control feature and the PS only Feature), thereby determining whether the feature that has been activated in the feature signed by the user is usable;
  • the HSS/HLR sends the available Feature to the MME/SGSN;
  • the feature that has been activated in the user's contracted Feature can include Time Control Feature and PS Only Feature
  • the Feature supported by the M2M Service Terminal M5 may include a Feature and a Time Control Feature and a Feature supported by the corresponding MME/SGSN capability
  • the Feature supported by the corresponding MME/SGSN capability may include a Security Feature, a Time Control Feature, and a PS Only Feature
  • the activated Feature (the corresponding activated Feature can include a Time Control Feature) can be used, then the corresponding HSS/HLR will use the Feature (the corresponding Feature that can be used)
  • the time control feature may be included and sent to the MME/SGSN;
  • Solution 1 The HSS/HLR determines the activatable feature and the deactivating feature according to at least one of the feature supported by the UE and the Feature supported by the MME/SGSN capability, and the feature and the operator's management policy signed by the user; for example: signing the user
  • the Feature that has been activated in the Feature can include the Time Control Feature and the PS Only Feature
  • Supported features can include anti-theft features and time-controlled features, excluding PS only Feature) or MME/SGSN-capable features (the corresponding MME/SGSN-capable features can include anti-theft features, time-controlled features, and PS only Feature).
  • the activated Feature (the corresponding activated Feature can include PS only Feature) cannot be used; then, the corresponding HSS/HLR According to the Feature supported by the M2M service terminal M5 (the corresponding Feature supported by the M2M service terminal M5 may include the anti-theft feature and the time control feature) and the corresponding MME/SGSN capability support Feature (the corresponding MME/SGSN capability supported Feature may be Including the anti-theft feature, time control feature and PS only Feature), as well as the user-signed feature (the corresponding user-signed feature can include anti-theft feature, time control feature and PS only feature) and operator business strategy (corresponding operator management)
  • the policy may include determining that the activatable feature is no longer determined for the activated feature (because the time control Feature has been activated and can be used, so the corresponding activatable feature may include a theft feature) and the deactivating feature (corresponding Deactivated features may include PS only Feature);
  • the HSS/HLR may send at least one of a Feature supported by the MME/SGSN capability, a Feature supported by the UE, a Feature that is not supported by the MME/SGSN capability in the activated Feature, or a Feature not supported by the UE.
  • MTC Server/Web/OMC etc.
  • the feature that has been activated in the user's contracted Feature can include Time Control Feature and PS Only Feature
  • the Feature supported by the M2M Service Terminal M5 may include the anti-theft feature and the time control feature, and does not include the PS only Feature
  • the corresponding MME/SGSN capability supported feature may include the anti-theft feature, time control
  • the activated feature can include PS only Feature
  • the corresponding HSS/HLR can send the corresponding MME/ Feature supported by the SGSN capability (the feature supported by the corresponding MME/SGSN capability may include the anti-theft feature, the time control feature, and the PS only feature).
  • the feature supported by the M2M service terminal M5 (the corresponding feature supported by the M2M service terminal M5 may include Anti-theft feature and time Feature and the Feature that is not supported by the M2M service terminal M5 in the activated Feature (the corresponding feature that the M2M service terminal M5 does not support may include the PS only Feature) is sent to the MTC Server currently serving the M2M service terminal M5. /Web/OMC, etc.;
  • the step is: The MME/SGSN notifies the UE that the registration is successful, that is, the processing of the Feature that can be used ends;
  • the corresponding ME/SGSN notifies the M2M service terminal that the M5 registration is successful, that is, the processing of the feature that can be used ends;
  • this step is:
  • the HSS/HLR sets an activation status identification update of the activatable feature to activation, and sets an activation status identification update of the deactivated feature to deactivation;
  • the corresponding HSS/HLR sets the activation status identification update of the activatable feature (the corresponding activatable feature may include the anti-theft feature) to active, and the deactivated feature (the corresponding deactivating feature may include PS only) Feature)
  • the activation status flag update is set to deactivate;
  • Solution 2 MTC Server/Web/OMC determines at least one of the features supported by the UE and the Feature supported by the MME/SGSN capability, and the user-signed feature and/or operator management policy to determine the activatable feature and the deactivating feature. ;
  • the corresponding MTC Server/Web/OMC can be supported according to the Feature supported by the M2M service terminal M5 (the corresponding Feature supported by the M2M service terminal M5 can include the anti-theft feature and the time control feature) and the corresponding MME/SGSN capability support.
  • the corresponding MME/SGSN capable features can include anti-theft features, time-controlled features, and PS only Feature
  • user-signed features can include anti-theft features, time-controlled features, and PS only Feature
  • the operator's business strategy may include no longer determining the activatable feature for the activated feature to determine the activatable feature (because the time control feature is activated and available, the corresponding activatable feature may Includes anti-theft features and deactivation features (corresponding deactivating features can include PS only Feature);
  • this step is:
  • the HSS/HLR sends the activatable and deactivated features to the MTC Server/Web/OMC, etc.; for example: the corresponding HSS/HLR can activate the features (the corresponding activatable features can include anti-theft
  • the deactivating feature (the corresponding feature of the deactivating feature may include the PS only Feature) sent to the MTC Server/Web/OMC, etc. currently serving the M2M service terminal M5;
  • MTC Server/Web/OMC or the like activates the activatable feature, deactivates the deactivated feature; and transmits the activatable feature and/or deactivatable feature to the HSS/ The HLR is activated;
  • a corresponding MTC Server/Web/OMC or the like performs an activation process on the activatable feature (the corresponding activatable feature may include an anti-theft feature), and the deactivating feature may be included (the corresponding deactivating feature may include a PS) Only Feature) performing a deactivation process; and transmitting the activatable feature and the deactivating feature to the HSS/HLR for activation;
  • this step is:
  • the HSS/HLR may send the activatable feature to the MME/SGSN; at the same time, the MTC Server/Web/OMC or the like activates the activatable feature to deactivate the deactivated feature;
  • the corresponding HSS/HLR may send the feature of the activatable feature (the corresponding activatable feature may include the anti-theft feature) to the corresponding MME/SGSN; meanwhile, the corresponding MTC Server/Web/OMC, etc.
  • the activation feature (the corresponding activatable feature may include an antitheft feature) performing an activation process, and deactivating the deactivating feature (the corresponding deactivating feature may include a PS only Feature);
  • the HSS/HLR checks whether the activating feature can be activated according to the Feature and UE supported Feature supported by the MME/SGSN capability, and if activated, sets the activation state identity update of the activating feature to active. Otherwise, the activation feature activation failure information is notified to the corresponding MTC Server/Web/OMC, etc., and the corresponding MTC Server/Web/OMC, etc. deactivates the activation-deactivated activation feature; for the deactivating feature, HSS/HLR Directly set the activation status identifier update of the deactivated feature to deactivate;
  • the corresponding HSS/HLR further checks whether the activatable feature can be activated according to the Feature supported by the MME/SGSN capability and the Feature supported by the M2M service terminal M5. If yes, the activation status identification update of the activatable feature (the corresponding activatable feature may include the anti-theft feature) is set to be activated, otherwise, the activatable feature activation failure information is notified to the corresponding MTC Server/Web/OMC, etc.
  • the corresponding MTC Server/Web/OMC, etc. then deactivate the activation-deactivated feature; for the de-activating feature (the corresponding deactivating feature can include the PS only Feature), the corresponding HSS/HLR directly deactivates the feature
  • the activation status identifier update is set to deactivate;
  • this step is:
  • Solution 1 The MME/SGSN sends a response message to the HSS/HLR, that is, the processing of the activated Feature is terminated by the first scheme;
  • the corresponding MME/SGSN sends a response message to the corresponding HSS/HLR, that is, the processing of the activated Feature is terminated by the first scheme;
  • the HSS/HLR may send the activatable feature to the MME/SGSN;
  • the corresponding HSS/HLR may send the activatable feature (the corresponding activatable feature may include the theft prevention feature) to the corresponding MME/SGSN;
  • Solution 2 The MME/SGSN sends a response message to the HSS/HLR, that is, the feature processing of the activated second is completed.
  • the corresponding MME/SGSN sends a response message to the corresponding HSS/HLR, that is, the processing of the activated Feature is terminated by the second scheme;
  • the implementation of the embodiment of the present invention enables the M2M service management entity to know the optimization scheme supported by the UE and/or the MME/SGSN in time, and can support the Feature and/or according to the MME/SGSN capability when the Feature subscribed by the user is unavailable.
  • the feature supported by the UE or the deactivated feature is determined to optimize the M2M service.
  • the M2M service optimization method provided by the embodiment of the present invention is described by using an M2M service terminal M6 as an example. If the M2M service terminal M6 is already registered to the corresponding MME/SGSN, and the FE2 and the HLR to which the M2M service terminal M6 belongs, the Feature and corresponding support of the M2M service terminal M6 registered by the M2M service terminal M6 are already saved.
  • the specific implementation steps may include:
  • Step 201 the MTC Server/Web/OMC, etc. sends the Feature that needs to be activated to the HSS/HLR;
  • the MTC Server/Web/OMC that is currently serving the M2M service terminal M6 sends an anti-theft feature that needs to be activated to the HSS/HLR to which the M2M service terminal M6 belongs;
  • Step 202 The HSS/HLR determines, according to the Feature supported by the UE and the Feature supported by the MME/SGSN capability, whether the Feature to be activated can be activated.
  • the corresponding HSS/HLR can determine whether the anti-theft feature that needs to be activated can be activated according to the Feature supported by the M2M service terminal M6 and the Feature supported by the corresponding MME/SGSN capability;
  • Hypothesis 1 If the HSS/HLR determines that the Feature to be activated can be activated, the HSS/HLR can set the activation status identification update of the Feature that can be activated to active, and pass the newly activated Feature through the IDR message (insert user message) For transmitting the MME/SGSN that is currently serving the user terminal to the corresponding MME/SGSN after the feature of the user subscription in the HSS/HLR is changed;
  • the M2M service terminal M6 supports the Feature and the corresponding MME/SGSN capability support
  • the Feature can support the anti-theft feature, and the corresponding HSS/HLR can determine that the anti-theft feature can be activated; then, the corresponding HSS/HLR sets the activation status flag update of the anti-theft feature to active, and will
  • the anti-theft feature is delivered to the MME/SGSN serving the M2M service terminal M6 by using an IDR message;
  • the HSS/HLR may activate the activation failure information of the Feature that cannot be activated, and the Feature and/or UE supported by the MME/SGSN capability supported by the UE. Feature sent to MTC Server/Web/OMC, etc.;
  • the corresponding HSS/HLR may determine that the anti-theft feature cannot be activated. Then, the corresponding HSS/HLR can send the activation failure information of the anti-theft feature, and the Feature supported by the M2M service terminal M6 and the Feature supported by the corresponding MME/SGSN capability to the MTC currently serving the M2M service terminal M6. Server/Web/OMC, etc.;
  • the step is: The MME/SGSN returns a response message to the HSS/HLR, and the activation process ends;
  • the step is: MTC Server/Web/OMC determines whether there is an activatable feature according to the Feature supported by the MME/SGSN capability uploaded by the HSS/HLR and/or the Feature supported by the UE. If yes, re-execute the step. 201, otherwise, exit the activation process;
  • Step 201 is performed to enter an activation process of the activatable feature; if there is no activatable feature, the activation process of the anti-theft feature is exited.
  • the implementation of the embodiment of the present invention enables the M2M service management entity to know the optimization scheme supported by the UE and/or the MME/SGSN in time, and can support the Feature and/or according to the MME/SGSN capability when the Feature subscribed by the user is unavailable.
  • the feature supported by the UE or the deactivated feature is determined to optimize the M2M service.
  • an M2M service terminal M7 is taken as an example to describe an M2M service optimization method provided by an embodiment of the present invention. If the M2M service terminal M7 supports the anti-theft feature and the time control feature, the MME/SGSN serving the M2M service terminal M7 supports the anti-theft feature, the time control feature and the PS only Feature, and the feature signed by the M2M service terminal M7 includes Anti-theft feature, time control feature and PS only Feature; If the M2M service terminal M7 has successfully registered to the MME/SGSN, but does not perform the normal exit mode to register due to exhaustion, etc., it is in the MME/SGSN The feature of the user subscription signed by the HSS/HLR at the time of successful registration is saved (the feature saved in the corresponding MME/SGSN may include a time control feature and a PS only Feature), and then the M2M service terminal M7 uses the M2M service optimization provided by the present invention.
  • Step 301 The UE sends a NAS message to the MME/SGSN, and the message may carry the IMSI of the UE, and the Feature and the like supported by the UE.
  • the corresponding M2M service terminal M7 sends a NAS message to the MME/SGSN, and the NAS message may carry the IMSI of the M2M service terminal M7, and the Feature supported by the M2M service terminal M7.
  • Step 302 The MME/SGSN may determine, according to the Feature supported by the UE and the Feature supported by the MME/SGSN capability, whether the Feature subscribed by the user saved in the MME/SGSN is available.
  • the features subscribed by the users are all activated; then, according to the support of the M2M service terminal M7.
  • Feature The corresponding M2M service terminal M7 supports Feature can include anti-theft feature and time control feature
  • the corresponding MME/SGSN capability support Feature determines the Feature supported by the M2M service terminal M7 and the corresponding MME/SGSN capability support Feature (Features supported by the corresponding MME/SGSN capabilities may include the Anti-Theft Feature, Time Control Feature, and PS Only Feature) Whether or not the Feature saved in the MME/SGSN (the corresponding Feature saved in the MME/SGSN may include Time Control Feature and PS) Only Feature) matches to determine whether the feature signed by the user saved in the MME/SGSN is available for use;
  • the MME/SGSN For the Feature that can be used in the Feature saved by the MME/SGSN, the MME/SGSN notifies the HSS/HLR of the available Feature;
  • the MME/SGSN For the Feature that can be used in the Feature saved by the corresponding MME/SGSN (the corresponding usable Feature can include the Time Control Feature), the MME/SGSN notifies the HSS/HLR of the available Feature.
  • the MME/SGSN supports the feature supported by the M2M service terminal M7 (corresponding to the M2M)
  • the Feature supported by the service terminal M7 may include a Feature and Time Control Feature, and a Feature supported by the corresponding MME/SGSN capability (the Feature supported by the corresponding MME/SGSN capability may include an Anti-Theft Feature, a Time Control Feature, and a PS Only Feature).
  • the feature that cannot be used is notified to the HSS/HLR to which the M2M service terminal M7 belongs;
  • the step is: The HSS/HLR returns a response message to the MME/SGSN;
  • the corresponding HSS/HLR returns a response message to the MME/SGSN serving the M2M service terminal M7;
  • Solution 1 The HSS/HLR deactivates the feature that cannot be used, and notifies the MTC Server/Web/OMC, etc., of the deactivated Feature;
  • the corresponding HSS/HLR deactivates the unavailable feature (the corresponding unavailable feature may include the PS only Feature), and notifies the deactivated Feature to the M2M service terminal M7.
  • Provide services such as MTC Server/Web/OMC;
  • Solution 2 The HSS/HLR deactivates the unavailable feature, and notifies the MTC Server/ at least one of the deactivated Feature and the Feature supported by the UE and the Feature supported by the MME/SGSN capability. Web/OMC, etc.;
  • the corresponding HSS/HLR deactivates the unavailable feature (the corresponding unavailable feature may include PS only Feature), and the deactivated Feature and the M2M service terminal M7 support Feature (The corresponding M2M service terminal M7 supports features that can include anti-theft feature and time control feature) and corresponding MME/SGSN capability support features (the corresponding MME/SGSN capability support features can include anti-theft feature, time control feature And at least one of the PS only Feature) is notified to the MTC Server/Web/OMC, etc. currently serving the M2M service terminal M7;
  • the step is: The MME/SGSN notifies the UE that the registration is successful, and the process can be exited;
  • Solution 1 The deactivated Feature is deactivated by the MTC Server/Web/OMC, and the HSS/HLR determines the Feature that is suitable for activation according to the Feature supported by the UE and the Feature supported by the MME/SGSN capability;
  • the Feature may include a PS only Feature) for deactivation processing, and the corresponding HSS/HLR according to the Feature supported by the M2M service terminal M7 (the corresponding Feature supported by the M2M service terminal M7 may include an anti-theft feature and a time-controlled Feature) and Feature corresponding to the corresponding MME/SGSN capability (the corresponding MME/SGSN capability supported feature can include anti-theft feature, time control Featur and PS only Feature) to determine the feature suitable for activation (the corresponding feature suitable for activation can include anti-theft feature)
  • Scheme 2 MTC Server/Web/OMC, etc. deactivate the deactivated Feature, and Determining a feature suitable for activation according to the Feature supported by the UE and the Feature supported by the MME/SGSN capability, and performing activation processing;
  • the corresponding MTC Server/Web/OMC or the like deactivates the deactivated Feature (the deactivation may include a PS only Feature), and according to the Feature supported by the M2M service terminal M7 (corresponding to the M2M) Feature supported by service terminal M7 may include Feature and Time Control Feature for Anti-Theft and corresponding Feature Supported by MME/SGSN Capabilities (Features supported by corresponding MME/SGSN capabilities may include Anti-theft Feature, Time Control Featur and PS only Feature) Determining a feature that is suitable for activation (the corresponding feature suitable for activation may include an anti-theft feature) and performing an activation process;
  • the HSS/HLR sets the activation status identification update for the feature that is suitable for activation to active; for example: The corresponding HSS/HLR will be activated for the activated feature (the corresponding suitable feature for the feature can include the anti-theft feature) Set to activate;
  • Solution 2 The MTC Server/Web/OMC or the like notifies the HSS/HLR of the feature suitable for activation; for example: the corresponding MTC Server/Web/OMC, etc., the feature suitable for activation (the corresponding feature suitable for activation may include Anti-theft feature) to notify the corresponding HSS/HLR;
  • Solution 1 The HSS/HLR notifies the MTC Server/Web/OMC, etc. of the feature that is suitable for activation; for example: the corresponding HSS/HLR will apply the feature suitable for activation (the corresponding feature suitable for activation may include an anti-theft feature) Notify the MTC currently serving the M2M service terminal M7
  • the HSS/HLR sets the activation status identification update of the feature suitable for activation to be activated; for example: the corresponding HSS/HLR will apply the feature suitable for activation (the corresponding suitable activation feature may include an anti-theft feature)
  • the activation status flag update is set to active;
  • Solution 1 The HSS/HLR sends the feature suitable for activation to the corresponding MME/SGSN, and the MTC Server/Web/OMC or the like activates the feature suitable for activation;
  • the corresponding HSS/HLR delivers the feature that is suitable for activation (the corresponding feature suitable for activation can include the anti-theft feature) to the corresponding MME/SGSN, and the corresponding MTC Server/Web/OMC, etc.
  • Feature (the corresponding feature suitable for activation may include anti-theft feature) for activation processing;
  • the HSS/HLR sends the feature suitable for activation to the corresponding MME/SGSN;
  • the corresponding HSS/HLR delivers the feature that is suitable for activation (the corresponding feature suitable for activation may include the theft protection feature) to the corresponding MME/SGSN;
  • Step 309 For the Feature that cannot be used in the Feature saved by the MME/SGSN, the step is:
  • the MME/SGSN sends a response message to the corresponding HSS/HLR;
  • the corresponding MME/SGSN sends a response message to the corresponding HSS/HLR;
  • the implementation of the embodiment of the present invention enables the M2M service management entity to know the optimization scheme supported by the UE and/or the MME/SGSN in time, and can support the Feature and/or according to the MME/SGSN capability when the Feature subscribed by the user is unavailable.
  • the feature supported by the UE or the deactivated feature is determined to optimize the M2M service.
  • an M2M service terminal M8 is taken as an example to describe an M2M service optimization method provided by an embodiment of the present invention. It is assumed that the M2M service terminal M8 supports the anti-theft feature and the time control feature, and the MME/SGSN serving the M2M service terminal M8 supports the anti-theft feature, the time control feature and the PS only Feature, and the feature signed by the M2M service terminal M8 includes the anti-theft.
  • Feature Time Control Feature and PS Only Feature
  • the user-signed Feature saved in the HSS/HLR to which the M2M Service Terminal M8 belongs has been partially activated (the corresponding activated Feature may include Time Control Feature and PS Only Feature).
  • the M2M service terminal M8 registers with the MME/SGSN by using the M2M service optimization method provided by the present invention. Specific implementation steps may include:
  • Step 401 The UE sends a NAS message to the MME/SGSN, and the message may carry the IMSI of the UE and the Feature and the like supported by the UE.
  • the corresponding M2M service terminal M8 sends a NAS message to the MME/SGSN, and the NAS message may carry the IMSI of the M2M service terminal M8, and the Feature supported by the M2M service terminal M8.
  • Step 402 After receiving the NAS message, the MME/SGSN first saves the Feature supported by the UE, and then determines the ULR of the HSS/HLR to which the UE belongs according to the IMSI of the UE.
  • the MME/SGSN that provides the service to the M2M service terminal M8 first saves the feature supported by the M2M service terminal M8, and then determines the M2M service according to the information such as the IMSI of the M2M service terminal M8.
  • Step 405 the MME/SGSN is routed according to the ULR to the HSS/HLR to which the UE belongs;
  • the corresponding MME/SGSN is routed to the HSS/HLR to which the M2M service terminal M8 belongs according to the ULR;
  • Step 404 After receiving the ULR, the HSS/HLR sends the activated feature of the user-consigned Feature saved by the HSS/HLR to the MME/SGSN.
  • the HSS/HLR to which the M2M service terminal M8 belongs receives the ULR, the feature that has been activated in the contract signed by the HSS/HLR (the corresponding activated feature may include the time control Feature and PS). Only Feature) is sent to the corresponding MME/SGSN;
  • Step 405 The MME/SGSN is supported according to the Feature supported by the UE and the MME/SGSN capability.
  • At least one item in the Feature determines whether the activated Feature delivered by the HSS/HLR is available
  • the corresponding HSS/HLR supports the Feature supported by the M2M service terminal M8 (the corresponding M2M service terminal M8 supports the Feature may include the anti-theft feature and the time control feature) and the corresponding MME/SGSN capability supported Feature (corresponding MME)
  • Features supported by the /SGSN capability may include time control features, PS only Feature, and anti-theft features. Determine whether the activated features issued by the HSS/HLR (the corresponding activated features may include the time control feature and the PS only Feature) can use;
  • the MME/SGSN For the Feature that can be used in the activated Feature, the MME/SGSN notifies the UE that the registration is successful, that is, the processing flow of the Feature that can be used is completed;
  • the MME/SGSN notifies the M2M service terminal M8 that the registration is successful, that is, the process flow of the feature that can be used is completed;
  • the MME/SGSN supports the Feature and the UE-supported Feature according to the MME/SGSN capability. At least one of the characteristics, and the user-signed feature and/or operator business strategy determine the feature that is suitable for activation; for example, a feature that cannot be used in an already activated Feature (the corresponding feature that cannot be used may include PS only Feature) Then, the corresponding MME/SGSN supports the Feature according to the MME/SGSN capability (the corresponding MME/SGSN capability supported Feature may include anti-theft feature, time control feature and PS only Feature) and the feature supported by the M2M service terminal M8 (corresponding The features supported by the M2M service terminal M8 can include the Feature and Time Control feature, as well as the Feature that the user subscribes to (the corresponding user-signed Feature can include the Anti-Theft Feature, Time Control Feature and PS Only Feature) and the operator's business strategy.
  • the corresponding operator's business strategy may include the feature that has been activated without determining whether it is a feature that is suitable for activation.) Determining a feature that is suitable for activation (the corresponding feature suitable for activation may include an anti-theft feature);
  • the MME/SGSN may support the Feature supported by the MME/SGSN capability, the Feature supported by the UE, the Feature that is not supported by the MME/SGSN capability in the activated Feature, or the Feature that the UE does not support (that is, the said may not At least one of the used features is sent to MTC Server/Web/OMC, etc.;
  • the MME/SGSN may support the MME/SGSN capability (the corresponding MME/SGSN capability is supported).
  • the Feature may include an anti-theft feature, a time control feature, and a PS only Feature.
  • the feature supported by the M2M service terminal M8 (the corresponding M2M service terminal M8 supported feature may include an anti-theft feature and a time-controlled feature), and the unusable Feature corresponding to the feature that may not be used may include at least one of PS only Feature) sent to the MTC Server/Web/OMC currently serving the M2M service terminal M8;
  • Solution 1 The MME/SGSN transmits the feature suitable for activation to the HSS/HLR and the MTC Server/Web/OMC, etc.;
  • the corresponding MME/SGSN transmits the suitable active feature (the corresponding suitable active feature can include the theft protection feature) to the corresponding HSS/HLR and MTC Server/Web/OMC, etc.;
  • Solution 2 The MTC Server/Web/OMC determines at least one of the Feature and the UE-supported Feature supported by the MME/SGSN capability uploaded by the MME/SGSN, and the Feature and Carrier Management Policy signed by the user to determine the Feature that is suitable for activation. ;
  • the corresponding MTC Server/Web/OMC and other features supported by the MME/SGSN capability uploaded by the MME/SGSN may include anti-theft features, time control features, and PS only Feature
  • the feature supported by the M2M service terminal M8 (the corresponding M2M service terminal M8 supports the Feature may include the anti-theft feature and the time control feature), and the user-signed feature (the corresponding user-signed feature may include the anti-theft feature, the time control feature And PS only Feature) and the operator's business strategy (the corresponding operator's business strategy may include the activated feature without determining whether it is suitable for the activated feature) to determine the feature that is suitable for activation (the corresponding feature suitable for activation may include the anti-theft feature) ;
  • Solution 1 The MTC Server/Web/OMC or the like activates the feature suitable for activation; meanwhile, the HSS/HLR sets the activation status identification update of the feature suitable for activation to be activated, and sends a response message to the MME/SGSN. ;
  • the corresponding MTC Server/Web/OMC, etc. activates the feature that is suitable for activation (the corresponding feature suitable for activation may include the anti-theft feature); meanwhile, the corresponding HSS/HLR will activate the feature
  • the activation feature identifier update of the live Feature (the corresponding suitable activation feature may include the anti-theft feature) is set to be activated, and a response message is sent to the MME/SGSN;
  • MTC Server/Web/OMC etc. activates the Feature that is suitable for activation and transmits it to the MME/SGSN;
  • the corresponding MTC Server/Web/OMC, etc. will be suitable for the activated Feature (correspondingly suitable for activation)
  • Feature can include anti-theft feature) to activate and transmit to MME/SGSN;
  • Option 2 The MME/SGSN transmits the suitable active Feature to the HSS/HLR;
  • the corresponding MME/SGSN transmits the Feature that is suitable for activation (the corresponding Feature that is suitable for activation can include the theft feature) to the HSS/HLR;
  • Option 2 The HSS/HLR sets the activation status identification update of the suitable activated Feature to active, and sends a response to the MME/SGSN. Message
  • the corresponding HSS/HLR sets the activation status identification update of the suitable activation feature (the corresponding suitable activation feature can include the theft prevention feature) to be activated, and sends a response message to the corresponding MME/SGSN;
  • the implementation of the embodiment of the present invention enables the M2M service management entity to know the optimization scheme supported by the UE and/or the MME/SGSN in time, and can support the Feature and/or according to the MME/SGSN capability when the Feature subscribed by the user is unavailable.
  • the UE-supported Feature determines the activatable feature to optimize the M2M service.
  • an M2M service terminal M9 is taken as an example to describe an M2M service optimization method provided by an embodiment of the present invention. It is assumed that the M2M service terminal M5 supports the anti-theft feature and the time control feature, and the MME/SGSN serving the M2M service terminal M9 supports the anti-theft feature, the time control feature and the PS only Feature, and the feature signed by the M2M service terminal M9 includes the anti-theft. Use Feature, Time Control Feature and PS only
  • the HSS/HLR is issued when the successful registration is saved in the MME/SGSN.
  • User-signed Feature the corresponding Feature saved in MME/SGSN can include time control
  • the specific implementation steps of the M2M service terminal M9 re-registering to the MME/SGSN by using the M2M service optimization method provided by the present invention may include:
  • Step 501 The UE sends a NAS message to the MME/SGSN, and the message may carry the IMSI of the UE and the Feature and the like supported by the UE.
  • the corresponding M2M service terminal M9 sends a NAS message to the MME/SGSN, and the NAS message may carry the IMSI of the M2M service terminal M9, and the Feature supported by the M2M service terminal M9.
  • Step 502 The MME/SGSN may determine, according to the Feature supported by the UE and the Feature supported by the MME/SGSN capability, whether the Feature subscribed by the user saved in the MME/SGSN is available.
  • the feature signed by the user saved in the MME/SGSN is saved when the M2M service terminal M9 is successfully registered last time, so the features subscribed by the users are all activated; then, according to the support of the M2M service terminal M9
  • the feature supported by the Feature and the corresponding MME/SGSN capability determines the Feature supported by the M2M service terminal M9 (the corresponding M2M service terminal M9 supports the Feature may include the anti-theft feature and the time control feature) and the corresponding MME/SGSN capability supported Feature (Features supported by the corresponding MME/SGSN capability may include the anti-theft feature, time control feature, and PS only Feature).
  • Whether the feature saved in the MME/SGSN may include time control in the corresponding MME/SGSN.
  • the Feature and the PS Only Feature are matched to determine whether the feature signed by the user saved in the MME/SGSN can be used;
  • the MME/SGSN informs that the UE is successfully registered, that is, the processing flow of the Feature that can be used is completed;
  • the feature that can be used in the feature saved by the MME/SGSN may include a time control feature
  • the corresponding MME/SGSN notifies the M2M service terminal that the registration of the M9 is successful, that is, the feature that can be used is completed. Processing flow
  • Solution 1 The MME/SGSN determines, according to at least one of the Feature and the UE-supported Feature supported by the MME/SGSN capability, and the Feature and operator management policies saved in the MME/SGSN, the Feature that is suitable for activation;
  • the corresponding MME/SGSN may include Feature and Time Control Feature for anti-theft and corresponding Feature supported by MME/SGSN capability (corresponding MME/SGSN capability supported features may include anti-theft feature, time control feature and PS only Feature ), and the user-signed Feature (the corresponding user-signed Feature can include the Anti-Theft Feature, Time Control Feature, and PS Only Feature) and the carrier's business strategy (the corresponding operator's business strategy can include the activated Feature without determining whether it is Feature suitable for activation) Determine the feature that is suitable for activation (the corresponding feature suitable for activation may include the anti-theft feature);
  • Scenario 2 The Feature Supported by the UE, the Feature Supported by the MME/SGSN Capability, and the Feature and/or the MME/not supported by the UE in the Feature saved by the MME/SGSN in the MME/SGSN At least one of the features (not described in the Feature) that are not supported by the SGSN capability is notified to the MTC Server/Web/OMC, etc.;
  • the MME/SGSN supports the feature supported by the M2M service terminal M9 (the corresponding M2M service)
  • the Feature supported by the terminal M9 may include an anti-theft feature and a time control feature.
  • the feature supported by the MME/SGSN capability (the corresponding MME/SGSN capability supported feature may include anti-theft feature, time control feature, and PS only feature) and
  • the feature that cannot be used (the corresponding feature that cannot be used may include the PS only Feature) is notified to the MTC Server/Web/OMC that is currently serving the M2M service terminal M9;
  • Solution 1 The MME/SGSN transmits the feature suitable for activation to the HSS/HLR and the MTC Server/Web/OMC, etc.;
  • the corresponding MME/SGSN transmits the suitable active feature (the corresponding suitable activation feature can include the theft protection feature) to the HSS/HLR and the MTC Server/Web/OMC, etc.;
  • the MTC Server/Web/OMC determines a feature suitable for activation according to at least one of a feature supported by the MME/SGSN capability supported by the MME/SGSN and a Feature supported by the UE, and a Feature and an operator management policy subscribed by the user;
  • the corresponding MTC Server/Web/OMC and the like support the Feature supported by the M2M service terminal M9 (the corresponding Feature supported by the M2M service terminal M9 may include the anti-theft feature and the time control feature) and the corresponding MME/SGSN capability support.
  • Feature the corresponding MME/SGSN capability support feature can be Includes anti-theft features, time-controlled features, and PS only Feature), as well as user-signed features (the corresponding user-contracted features can include anti-theft features, time-controlled features, and PS only feature) and carrier business strategies (corresponding carriers)
  • the business strategy may include the feature that has been activated without determining whether it is a feature suitable for activation.
  • the feature that is suitable for activation may be included (the corresponding feature suitable for activation may include a theft feature);
  • Solution 1 The MTC Server/Web/OMC or the like performs activation processing on the feature that is suitable for activation, and at the same time, the HSS/HLR sets the activation status identification update of the feature suitable for activation to be activated, and sends a response message to the MME/SGSN. ;
  • the corresponding MTC Server/Web/OMC or the like activates the suitable activated feature (the corresponding suitable activated feature may include the anti-theft feature), and the corresponding HSS/HLR will apply the activated feature.
  • the activation status identifier update is set to be activated, and a response message is sent to the MME/SGSN;
  • the MTC Server/Web/OMC or the like transmits the suitable activated Feature to the MME/SGSN; for example: corresponding MTC Server/Web/OMC And transmitting the feature suitable for activation (the corresponding feature suitable for activation may include the anti-theft feature) to the corresponding MME/SGSN;
  • Solution 2 The MME/SGSN transmits the suitable active theme to the HSS/HLR;
  • the corresponding MME/SGSN transmits the suitable active feature (the corresponding suitable activation feature can include the anti-theft feature) to the corresponding HSS/HLR;
  • the HSS/HLR sets the activation status identification update of the Feature that is suitable for activation to be activated, and sends a response message to the MME/SGSN;
  • the corresponding HSS/HLR sets the activation status identification update for the activation-enabled Feature (the corresponding suitable activation feature can include the theft protection feature) to be activated and sends a response cancellation to the MME/SGSN.
  • the implementation of the embodiment of the present invention enables the M2M service management entity to know the optimization scheme supported by the UE and/or the MME/SGSN in time, and can support the Feature and/or according to the MME/SGSN capability when the Feature subscribed by the user is unavailable.
  • the UE-supported Feature determines the activatable feature to optimize the M2M service.
  • an M2M service terminal M10 is taken as an example to describe an M2M service optimization method provided by an embodiment of the present invention. If the M2M service terminal M10 is already registered to the corresponding MME/SGSN, and the FE2 and the HLR to which the M2M service terminal M10 belongs, the Feature and corresponding support of the M2M service terminal M10 registered by the M2M service terminal M10 are already saved.
  • the Feature of the MME/SGSN capability support when the M2 Server/Web/OMC currently serving the M2M service terminal M10 needs to use the M2M service optimization method provided by the present invention to add a new Feature to the M2M service terminal M10 (corresponding When the newly added feature of the M2M service terminal M10 can be activated for the anti-theft feature, the specific implementation steps may include:
  • Step 601 The MTC Server/Web/OMC waits to query the HSS/HLR for the information of the MME/SGSN registered by the UE;
  • MTC Server/Web/OMC currently serving the M2M service terminal M10 waits for the M2M service.
  • the information about the MME/SGSN registered by the M2M service terminal M10 is queried in the HSS/HLR to which the terminal M10 belongs (the information of the corresponding MME/SGSN may include information indicating the MME/SGSN registered by the M2M service terminal M10) ;
  • Step 602 The HSS/HLR returns the information of the MME/SGSN registered by the UE to the MTC Server/Web/OMC, etc. - for example, the corresponding HSS/HLR returns the information of the MME/SGSN registered by the corresponding M2M service terminal M10 to the corresponding MTC Server/Web/OMC, etc.;
  • Step 603 The MTC Server/Web/OMC sends the Feature that needs to be activated to the MME/SGSN.
  • the corresponding MTC Server/Web/OMC sends the burglary feature that needs to be activated to the MME registered by the M2M service terminal M10.
  • SGSN the MTC Server/Web/OMC sends the burglary feature that needs to be activated to the MME registered by the M2M service terminal M10.
  • Step 604 The MME/SGSN determines, according to the Feature and/or the Feature supported by the UE supported by the MME/SGSN capability, whether the Feature that needs to be activated, such as the MTC Server/Web/OMC, can be activated.
  • the feature supported by the M2M service terminal M10 registered by the M2M service terminal M10 is already stored in the corresponding MME/SGSN, so the MME/SGSN can support the Feature supported by the MME/SGSN capability and the M2M service terminal M10.
  • the Feature determines whether the anti-theft feature that needs to be activated, such as the MTC Server/Web/OMC, can be activated.
  • the MME/SGSN may notify the HSS/HLR and the MTC Server/Web/OMC, etc., of the Feature that can be activated;
  • the Feature can support the anti-theft feature, and the corresponding MME/SGSN can determine that the anti-theft feature can be activated; then, the corresponding MME/SGSN can notify the corresponding HSS/HLR and MTC of the anti-theft feature.
  • the MME/SGSN may activate the activation failure information of the Feature that cannot be activated, the Feature supported by the MME/SGSN capability, and/or the Feature supported by the UE, and the MME.
  • Features that are not supported by the /SGSN capability and/or features that are not supported by the UE are sent to the MTC Server/Web/OMC, etc.;
  • the corresponding MME/SGSN may determine that the anti-theft feature cannot be activated; then, the MME/SGSN may The activation failure information of the anti-theft feature, the Feature supported by the corresponding MME/SGSN capability, and/or the Feature supported by the M2M service terminal M10, and the Feature and/or the Feature not supported by the UE that are not supported by the MME/SGSN capability are sent. To MTC Server/Web/OMC, etc.;
  • the step is: MTC Server/Web/OMC, etc. activates the feature that needs to be activated, and at the same time, the HSS/HLR sets the activation status identifier update of the feature to be activated to be activated, and to the MME/SGSN Return a response message;
  • the corresponding MTC Server/Web/OMC and the like activate the anti-theft feature, and at the same time, the corresponding HSS/HLR sets the activation status identification update of the anti-theft feature to be activated, and returns one to the corresponding MME/SGSN.
  • Response information For example: the corresponding MTC Server/Web/OMC and the like activate the anti-theft feature, and at the same time, the corresponding HSS/HLR sets the activation status identification update of the anti-theft feature to be activated, and returns one to the corresponding MME/SGSN.
  • the step is: MTC Server/Web/OMC, etc. uploaded according to MME/SGSN
  • the Feature supported by the MME/SGSN capability and/or the Feature supported by the UE determine whether there is a Feature suitable for activation. If yes, perform step 603 again, otherwise, exit the activation process;
  • the corresponding MTC Server/Web/OMC, etc. according to the Feature supported by the MME/SGSN capability uploaded by the MME/SGSN and/or the Feature supported by the M2M service terminal M10, determine whether there is a feature suitable for activation, if there is a suitable activation. Feature, then step 603 is re-executed, that is, the activation process of the feature suitable for activation is entered; if there is no feature suitable for activation, the activation process of the anti-theft feature is exited.
  • the implementation of the embodiment of the present invention enables the M2M service management entity to know the optimization scheme supported by the UE and/or the MME/SGSN in time, and can support the Feature and/or according to the MME/SGSN capability when the Feature subscribed by the user is unavailable.
  • the UE-supported Feature determines the activatable feature to optimize the M2M service.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
  • the M2M service optimization apparatus provided by the embodiment of the present invention may be specifically configured in an M2M service communication entity (the corresponding M2M service communication entity may include an MME/SGSN or an HSS/HLR, etc.), and an M2M service management entity (a corresponding M2M service management entity) Can be included in MTC Server/Web/OMC, etc.).
  • the specific structure of the apparatus for the M2M service optimization apparatus may include:
  • supporting feature acquiring unit 1001 configured to acquire at least one of a feature supported by the terminal and a feature supported by the mobility management unit capability
  • the corresponding support feature acquiring unit 1001 may specifically include:
  • the first support feature acquiring unit 10011 is configured in the MME/SGSN, and is configured to acquire at least one of a feature supported by the terminal and a feature supported by the mobility management unit capability;
  • the second support feature obtaining unit 10012 is configured in the HSS/HLR, and is configured to acquire at least one of a feature supported by the terminal and a feature supported by the mobility management unit capability;
  • a support feature sending unit 1002 configured to send, to the M2M service management entity, at least one of a feature supported by the terminal acquired by the support feature acquiring unit 1001 and a feature supported by the mobility management unit capability;
  • the corresponding support feature sending unit 1002 may be disposed in the MME/SGSN, or may be disposed in the HSS/HLR, or respectively provided with different optimized feature sending units 3002;
  • the support feature sending unit 1002 provided in the MME/SGSN may acquire the unit to the first support feature
  • the support feature transmitting unit 1002 provided in the HSS/HLR may acquire at least one of the feature supported by the terminal and the feature supported by the mobility management unit capability acquired by the second support feature acquiring unit 10012.
  • the M2M service optimization apparatus provided by the embodiment of the present invention may further include:
  • the feature determining unit 1003 is configured to determine, according to the feature supported by the terminal and the feature supported by the mobility management unit capability acquired by the support feature acquiring unit 1001, and the feature of the user subscription, determining an unusable feature; wherein, corresponding The unusable feature refers to a feature that is not supported by the terminal and/or a feature that the mobility management unit capability does not support in the feature that has been activated or is being activated;
  • the corresponding unsupported feature determining unit 1003 may be set in the MME/SGSN, or may be set in
  • the unsupported feature determining unit 1003 configured in the MME/SGSN may determine the unusable feature according to the feature supported by the terminal acquired by the first supporting feature acquiring unit 10011 and the feature supported by the mobility management unit capability, and the feature signed by the user. ;
  • the unsupported feature determining unit 1003 disposed in the HSS/HLR may acquire the unit according to the second supporting feature
  • the feature sending unit 1004 is not configured to send the unusable feature determined by the unsupported feature determining unit 1003 to the M2M service management entity.
  • the corresponding unsupported feature sending unit 1004 may be set in the MME/SGSN, or may be set in the HSS/HLR, or respectively provided with different unsupported feature determining units 1003;
  • the unsupported feature sending unit 1004 disposed in the MME/SGSN may send the unusable feature determined by the unsupported feature determining unit 1003 set in the MME/SGSN to the M2M service management entity;
  • the unsupported feature sending unit 1004 disposed in the HSS/HLR may send the unusable feature determined by the unsupported feature determining unit 1003 set in the HSS/HLR to the M2M service management entity; specifically, the corresponding unsupported feature
  • the sending unit 1004 may be performed simultaneously with the supporting feature sending unit 1002, that is, at least one of the feature supported by the terminal acquired by the feature acquiring unit 1001 and the feature supported by the mobility management unit capability, and the unsupported feature determining The unusable features determined by unit 1003 are simultaneously sent to the M2M service management entity.
  • the M2M service optimization apparatus may further include:
  • the activatable feature refers to a feature that is supported by the terminal and the mobility management unit capability after the feature that has been activated or is activated is removed from the feature that is subscribed to by the user of the M2M service;
  • the deactivating feature refers to a feature that is not supported by the terminal and the feature that is not supported by the mobility management unit capability in the activated feature of the M2M service.
  • the corresponding first feature receiving processing unit 1005 may include:
  • the first feature reception determination processing unit 10051 is configured in the MME/SGSN, configured to receive an activatable feature, and determine, according to at least one of a feature supported by the UE and a feature supported by the MME/SGSN capability, whether the received activatable feature is received. Can be activated to acquire features that can be activated in the activatable feature and/or features that cannot be activated, and to treat the feature that cannot be activated as a deactivated feature; then, the MME/SGSN will activate the feature And/or deactivation feature notification to the HSS or HLR; the HSS or HLR then activates the activatable feature to deactivate the deactivated feature;
  • the activatable feature refers to a feature that is supported by the terminal and the mobility management unit capability after the feature that has been activated or is activated is removed from the feature that is subscribed to by the user of the M2M service;
  • the deactivating feature refers to a feature that is not supported by the terminal and the feature that is not supported by the mobility management unit capability in the activated feature of the M2M service.
  • the corresponding second feature receiving processing unit 1006 may include:
  • the second feature reception determination processing unit 10061 is configured in the HSS/HLR, configured to receive the activatable feature, and is determined according to at least one of a feature supported by the UE and a feature supported by the MME/SGSN capability saved in the HSS/HLR. Whether the received activatable feature can be activated to acquire a feature that can be activated in the activatable feature and/or a feature that cannot be activated, and to use the feature that cannot be activated as a deactivated feature; The HSS/HLR activates the activatable feature and deactivates the deactivated feature.
  • the specific structure of the device that is set in the M2M service management entity may include:
  • supporting feature receiving unit 2001 configured to receive at least one of a feature supported by the terminal and a feature supported by the mobility management unit;
  • the M2M service optimization apparatus may further include: a first support feature receiving unit 20011, configured in the MTC Server/Web/OMC, and the like, configured to receive features supported by the terminal. And at least one of the features of the mobility management unit capability support;
  • an activatable feature determining unit 2002 configured to perform at least one of a feature supported by the terminal and a feature supported by the mobility management unit capability acquired by the support feature receiving unit 2001, and a feature of the user subscription and/or The operator's business strategy determines an activatable feature and activates the activatable feature;
  • the corresponding activatable feature refers to a feature that is supported by the terminal and the mobility management unit capability after the feature that has been activated or is activated is removed from the feature that is subscribed to by the user of the M2M service;
  • the corresponding activatable feature determining unit 2002 may also be disposed in the MTC Server/Web/OMC or the like, and according to the feature supported by the terminal acquired by the first supporting feature receiving unit 20011 and the feature supported by the mobility management unit capability. At least one item, and a user-signed feature and/or an operator's business strategy determine an activatable feature and activate the activatable feature.
  • the M2M service optimization apparatus may further include: a deactivation feature determining unit 2003, configured to acquire, according to the feature and movement supported by the terminal acquired by the support feature receiving unit 2001. At least one of the characteristics of the sexual management unit capability support, and the characteristics of the user subscription and/or the operator's business strategy determine the deactivated feature, and deactivate the deactivated feature;
  • the corresponding deactivating feature refers to a feature that is not supported by the terminal and the feature that is not supported by the mobility management unit capability in the activated feature of the M2M service;
  • the corresponding deactivated feature determining unit 2003 may be disposed in the MTC Server/Web/OMC or the like, and may be simultaneously executed with the activatable feature determining unit 2002 to simultaneously determine the deactivated feature and the activatable feature.
  • the M2M service optimization apparatus may include: an unsupported feature receiving unit 2004, configured to receive an unusable feature, and sent to the activatable feature determining unit 2002. Activation feature determination processing and/or transmission to deactivated feature determination unit 2003 for deactivating feature determination processing;
  • the corresponding unusable feature refers to a feature that is not supported by the terminal and/or a feature that the mobility management unit capability does not support in the feature that has been activated or is being activated;
  • the corresponding unsupported feature receiving unit 2004 may be set in the MTC Server/Web/OMC or the like, and executed simultaneously with the support feature receiving unit 2001, and respectively received the unsupported features and support features sent by the M2M service communication entity. .
  • the M2M service optimization apparatus may further include: a feature sending unit 2005, configured in the MTC Server/Web/OMC, and the like, configured to send the activatable feature. Determining the activatable feature determined by the unit 2002 and/or the deactivatable feature determined by the deactivatable feature determining unit 2003;
  • the corresponding feature sending unit 2005 can be set in the MTC Server/Web/OMC or the like for
  • the M2M service communication entity transmits the activatable feature determined by the activatable feature determining unit 2002 and/or the deactivating feature determined by the deactivatable feature determining unit 2003.
  • the M2M service optimization apparatus provided by the embodiment of the present invention further includes another similar scheme, so as to enable the M2M service management entity to learn the optimization scheme supported by the UE and/or the MME/SGSN.
  • the specific structure of the apparatus for the M2M service optimization apparatus may include:
  • the feature determination processing unit 3001 is configured to determine the activatable feature and/or according to at least one of a feature supported by the terminal and a feature supported by the mobility management unit capability, and a feature of the user subscription and/or an operation policy of the operator. Or deactivating the feature, and performing activation processing on the activatable feature and/or deactivating the deactivated feature; wherein the corresponding activatable feature refers to a feature signed by a user of the M2M service, Features that are supported by both the terminal and mobility management unit capabilities, except for features that have been activated or are being activated;
  • the corresponding deactivating feature refers to a feature that is not supported by the terminal and the feature that is not supported by the mobility management unit capability in the activated feature of the M2M service;
  • the M2M service optimization apparatus may further include: a first feature determining unit 30011, configured in the MME/SGSN, according to the feature and mobility management unit supported by the terminal. At least one of the features of the capability support, and the characteristics of the user subscription and/or the operator's business strategy determine the activatable feature and/or the deactivating feature;
  • the second feature determining unit 30012 is configured in the HSS/HLR, configured to determine at least one of a feature supported by the terminal and a feature supported by the mobility management unit, and a feature of the user subscription and/or an operation policy of the operator.
  • the feature can be activated and/or the feature can be deactivated.
  • an optimized feature sending unit 3002 configured to send the feature determining processing unit to the M2M service processing entity
  • the corresponding optimized feature sending unit 3002 may be disposed in the MME/SGSN, or may be disposed in the HSS/HLR, or respectively provided with different optimized feature sending units 3002;
  • the optimized feature sending unit 3002 disposed in the MME/SGSN may send the activatable feature and/or the deactivating feature determined by the first feature determining unit 30011 to the M2M service processing entity;
  • the optimized feature transmitting unit 3002 provided in the HSS/HLR may transmit the activatable feature and/or the deactivating feature determined by the second feature determining unit 30012 to the M2M service processing entity.
  • the specific structure of the M2M service optimization apparatus provided by the embodiment of the present invention, and the corresponding apparatus configured in the M2M service management entity may include:
  • an optimized feature receiving unit 400 configured to receive an activatable feature and/or a deactivating feature
  • the corresponding activatable feature refers to a feature that is supported by the terminal and the mobility management unit capability after the feature that has been activated or is activated is removed from the feature that is subscribed to by the user of the M2M service;
  • the corresponding deactivating feature refers to a feature that is not supported by the terminal and the feature that is not supported by the mobility management unit capability in the activated feature of the M2M service;
  • the corresponding optimized feature receiving unit 4001 may specifically include:
  • a first optimized feature receiving unit 40011 configured in the MTC Server/Web/OMC or the like, for receiving an activatable feature and/or a deactivating feature
  • the use of the corresponding first optimized feature receiving unit 40011 may include at least one of the following:
  • the first optimized feature receiving unit 40011 set in the MTC Server/Web/OMC or the like may Receiving an activatable feature;
  • the first optimization feature receiving unit 40011 set in the MTC Server/Web/OMC or the like can receive the deactivating feature
  • an optimization feature processing unit 4002 configured to perform an activation process on the activatable feature received by the optimized feature receiving unit 4001 and/or deactivate the deactivated feature;
  • the use of the corresponding optimized feature processing unit 4002 can include at least one of the following:
  • the optimized feature receiving unit 4001 receives the activatable feature
  • the corresponding optimized feature processing unit 4002 performs an activation process on the activatable feature
  • the optimized feature receiving unit 4001 receives the deactivating feature
  • the corresponding optimized feature processing unit 4002 performs a deactivation process on the deactivated feature
  • the implementation of the device embodiment enables the M2M service management entity to know the optimization scheme supported by the UE and/or the MME/SGSN in time, and can support the Feature and/or according to the MME/SGSN capability when the Feature subscribed by the user is unavailable.
  • the feature supported by the UE or the deactivated feature is determined to optimize the M2M service.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

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

Description

一种 M2M业务的优化雄及装置
技术领域
本发明涉及通信技术领域， 尤其涉及一种 M2M业务的优化方法及装置。
背景技术
随着科技的发展， 通信业务的类型越来越多， M2M ( Machine to Machine, 机器到机 器通信） 业务就是极具代表性的通信业务之一。 在现有网络中， M2M 业务大都承载在 CS/PS域 (即电路承载域 /数据域)网络上运营。对于网络来说， M2M业务的用户与普通网络 业务用户一样， 没有明确的分别。 随着网络业务的发展， M2M业务的用户数量不断增加， 当用户数量达到一定程度后， 会给网络带来巨大的冲击。
为了减少对网络的冲击， 3GPP (3rd Generation Partnership Project, 第三代合作伙 伴计划） 根据 M2M终端的特性对 M2M业务进行了分类， 并且给每种类型的 M2M业务定 义了不同的 Feature (特征）； 这些 Feature 及其激活状态标识都保存在 HSS ( Home Subscriber Server, 归属用户服务器） /HLR ( Home Location Register, 归属位置寄存器） 中。
M2M业务的用户可以签约不同的 Feature, 针对这些不同的 Feature网络可以进行不 同的优化；具体地，网络可以根据移动性管理单元能力支持的 Feature、终端支持的 Feature 以及用户签约的 Feature判断应该采用哪些 Feature, 并执行网络优化策略和 M2M业务； 行业用户或者运营商还可以通过 WEB (互联网）、 OMC(Operations & Maintenance Center, 操作维护中心） 等接口对 M2M业务或者不同的 Feature进行激活、 去激活。
目前， 如图 1所示， 现有的 M2M业务的优化方法大致包括如下步骤：
步骤 1， UE ( User Equipment, 终端） 向 MME ( Mobility Management Entity, 移动 管理实体） /SGSN (Servicing GPRS Support Node, GPRS服务支持节点）发出 NAS (网 络和终端之间的网络接入服务消息， 用于终端和网络的交互） 消息， 在该消息中可以携带 UE支持的 Feature、 UE的 IMSI ( International Mobile Subscriber Identity, 国际移动用户 识别码） 等信息；
步骤 2， MME/SGSN收到上述 NAS消息后， 根据 UE的 IMSI等信息路由到上述 UE 所归属的 HSS/HLR;
步骤 3， MME/SGSN向 HSS/HLR发送 ULR ( Updateloactionrequest,位置更新请求） 消息， 在该消息中可以携带有 MME/SGSN能力 （移动性管理单元能力）；
步骤 4， HSS/HLR收到 ULR后，根据所述 MME/SGSN能力确定在用户签约的 Feature 中 MME/SGSN能力支持的已经激活的 Feature, 并将该 Feature作为可以下发的用户签约 的 Feature;
步骤 5， HSS/HLR将可以下发的 Feature下发给相应的 MME/SGSN;
步骤 6， MME/SGSN检测 HSS/HLR下发的 Feature与 MME/SGSN能力所支持的 Feature是否匹配；
步骤 7， MME/SGSN通过 NOR ( notify request, 通知请求）消息将 MME/SGSN运营 能力不支持但用户激活的 Feature通知给 HSS/HLR;
步骤 8， HSS/HLR向 MME/SGSN返回一个响应消息；
步骤 9， HSS/HLR将 MME/SGSN 能力不支持但用户激活的 Feature 通知给 MTC Server ( Machine Type Communications Server, 机器通信业务月艮务器） /Web (互联网） /OMC (Operations & Maintenance Center, 操作维护中心） 等；
步骤 10， MTC Server/Web/OMC 等对所述 MME/SGSN 能力不支持但用户激活的 Feature进行去激活处理， 同时 MME/SGSN通知 UE连接成功。
发明人发现现有技术提供的上述处理流程中至少存在如下问题：
M2M业务管理实体无法得知 UE和 /或 MME/SGSN所支持的优化方案，这样会使 M2M 业务得不到优化， 甚至会使 M2M业务不能有效执行。 发明内容
本发明实施例提供了一种 M2M业务的优化方法及装置， 以便于 M2M业务管理实体能 够及时获知 UE和 /或 MME/SGSN所支持的优化方案， 从而使 M2M业务得到优化。
一种 M2M (机器到机器通信） 业务的优化方法， 包括：
获取终端支持的特征和移动性管理单元能力支持的特征中的至少一项；
向 M2M 业务管理实体发送所述终端支持的特征和移动性管理单元能力支持的特征中 的至少一项。
一种 M2M业务的优化方法， 包括：
接收终端支持的特征和移动性管理单元能力支持的特征中的至少一项；
根据所述终端支持的特征和移动性管理单元能力支持的特征中的至少一项， 以及用户 签约的特征和 /或运营商的经营策略确定可激活特征， 并对所述可激活特征进行激活处理； 所述的可激活特征是指在 M2M业务的用户签约的特征中，除去已经激活或正在激活的特征 后， 终端和移动性管理单元能力均支持的特征。
一种 M2M业务的优化方法， 包括：
根据终端支持的特征和移动性管理单元能力支持的特征中的至少一项， 以及用户签约 的特征和 /或运营商的经营策略确定可激活特征和 /或可去激活特征， 并对所述可激活特征进 行激活处理和 /或对所述可去激活特征进行去激活处理； 所述的可激活特征是指在 M2M 业 务的用户签约的特征中， 除去已经激活或正在激活的特征后， 终端和移动性管理单元能力 均支持的特征； 所述的可去激活特征是指在 M2M业务的已经激活的特征中， 终端不支持的 特征和 /或移动性管理单元能力不支持的特征；
向 M2M业务处理实体发送可激活特征和 /或可去激活特征。
一种 M2M业务的优化方法， 包括：
接收可激活特征和 /或可去激活特征； 所述的可激活特征是指在 M2M 业务的用户签约 的特征中， 除去已经激活或正在激活的特征后， 终端和移动性管理单元能力均支持的特征; 所述的可去激活特征是指在 M2M 业务的已经激活的特征中， 终端不支持的特征和 /或移动 性管理单元能力不支持的特征；
对所述可激活特征进行激活处理和 /或对所述可去激活特征进行去激活处理。
一种 M2M业务的优化装置， 包括：
支持特征获取单元， 用于获取终端支持的特征和移动性管理单元能力支持的特征中的 至少一项；
支持特征发送单元，用于向 M2M业务管理实体发送所述支持特征获取单元所获取的终 端支持的特征和移动性管理单元能力支持的特征中的至少一项。
一种 M2M业务的优化装置， 包括：
支持特征接收单元， 用于接收终端支持的特征和移动性管理单元能力支持的特征中的 至少一项；
可激活特征确定单元， 用于根据所述支持特征接收单元所获取的终端支持的特征和移 动性管理单元能力支持的特征中的至少一项， 以及用户签约的特征和 /或运营商的经营策略 确定可激活特征， 并对所述可激活特征进行激活处理； 所述的可激活特征是指在 M2M业务 的用户签约的特征中， 除去已经激活或正在激活的特征后， 终端和移动性管理单元能力均 支持的特征。
一种 M2M业务的优化装置， 包括：
特征确定处理单元， 用于根据终端支持的特征和移动性管理单元能力支持的特征中的 至少一项， 以及用户签约的特征和 /或运营商的经营策略确定可激活特征和 /或可去激活特 征， 并对所述可激活特征进行激活处理和 /或对所述可去激活特征进行去激活处理； 所述的 可激活特征是指在 M2M业务的用户签约的特征中， 除去已经激活或正在激活的特征后， 终 端和移动性管理单元能力均支持的特征；所述的可去激活特征是指在 M2M业务的已经激活 的特征中， 终端不支持的特征和 /或移动性管理单元能力不支持的特征；
优化特征发送单元，用于向 M2M业务处理实体发送所述特征确定处理单元所确定的可 激活特征和 /或可去激活特征。
一种 M2M业务的优化装置， 包括：
优化特征接收单元， 用于接收可激活特征和 /或可去激活特征； 所述的可激活特征是指 在 M2M业务的用户签约的特征中， 除去已经激活或正在激活的特征后， 终端和移动性管理 单元能力均支持的特征； 所述的可去激活特征是指在 M2M业务的已经激活的特征中， 终端 不支持的特征和 /或移动性管理单元能力不支持的特征；
优化特征处理单元， 用于对所述优化特征接收单元所接收的可激活特征进行激活处理 和 /或对所述可去激活特征进行去激活处理。
由上述本发明提供的技术方案可以看出，本发明实施例提供的 M2M业务优化方法及装 置将 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少一项发送给了 M2M 业务管理实体（M2M业务管理实体是指对 M2M业务进行管理的实体，相应的 M2M业务管 理实体可以包括 MTC Server/Web/OMC等， 但不限于这些实体）， 因此使 M2M业务管理 实体能够及时获知 UE和 /或 MME/SGSN所支持的优化方案， 从而使 M2M业务得到优化。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对实施例或现有技 术描述中所需要使用的附图作简单地介绍， 显而易见地， 下面描述中的附图仅仅是本发明 的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动的前提下， 还可以根 据这些附图获得其他的附图。
图 1为本发明实施例提供的现有 M2M业务优化方法的处理流程示意图；
图 2为本发明实施例提供的 M2M业务优化方法的处理流程示意图一；
图 3为本发明实施例提供的 M2M业务优化方法的处理流程示意图二；
图 4为本发明实施例提供的 M2M业务优化方法的处理流程示意图三；
图 5为本发明实施例提供的 M2M业务优化方法的处理流程示意图四；
图 6为本发明实施例提供的 M2M业务优化方法的处理流程示意图五；
图 7为本发明实施例提供的 M2M业务优化方法的处理流程示意图六；
图 8为本发明实施例提供的 M2M业务优化方法的处理流程示意图七；
图 9为本发明实施例提供的 M2M业务优化方法的处理流程示意图八；
图 10为本发明实施例提供的 M2M业务优化方法的处理流程示意图九；
图 11为本发明实施例提供的 M2M业务优化方法的处理流程示意图十；
图 12为本发明实施例提供的 M2M业务优化方法的处理流程示意图十一；
图 13为本发明实施例提供的 M2M业务优化方法的处理流程示意图十二；
图 14为本发明实施例提供的 M2M业务优化装置的结构示意图一；
图 15为本发明实施例提供的 M2M业务优化装置的结构示意图二；
图 16为本发明实施例提供的 M2M业务优化装置的结构示意图三；
图 17为本发明实施例提供的 M2M业务优化装置的结构示意图四；
图 18为本发明实施例提供的 M2M业务优化装置的结构示意图五；
图 19为本发明实施例提供的 M2M业务优化装置的结构示意图六；
图 20为本发明实施例提供的 M2M业务优化装置的结构示意图七；
图 21为本发明实施例提供的 M2M业务优化装置的结构示意图八；
图 22为本发明实施例提供的 M2M业务优化装置的结构示意图九； 图 23为本发明实施例提供的 M2M业务优化装置的结构示意图十；
图 24为本发明实施例提供的 M2M业务优化装置的结构示意图十一。 具体实 «式
下面将结合本发明实施例中的附图， 对本发明实施例中的技术方案进行清楚、 完整地 描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而不是全部的实施例。 基于本 发明中的实施例， 本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实 施例， 都属于本发明保护的范围。
现有的 MME/SGSN或者 HSS/HLR均未将 UE支持的 Feature禾 Π/或 MME/SGSN能力 支持的 Feature发送给 M2M业务管理实体， 从而致使 M2M业务管理实体无法得知 UE和 / 或 MME/SGSN所支持的优化方案， 这样会使 M2M业务得不到优化， 甚至会使 M2M业务 不能有效执行。
下面将结合附图对本发明实施例作进一步地详细描述。
本发明实施例提供的 M2M业务优化方法的具体实现过程涉及 M2M业务通信实体（相 应的 M2M业务通信实体可以包括 MME/SGSN或者 HSS/HLR， 但不仅限于这些网元）， 以 及 M2M业务管理实体 （相应的 M2M业务管理实体可以包括 MTC Server/Web/OMC等， 但不仅限于这些网元）。 需要说明的是在本发明实施例当中描述的终端既可以包括手机、 PDA (掌上电脑）、 各种智能手机等通信电子设备， 还可以包括其他安装有 M2M业务终端 的电器设备， 如笔记本电脑、 台式机、 摄像头、 洗衣机、 空调、 电饭煲等。 本发明实施例 中的终端包括但不限于上述设备， 下面描述中仅举几个实例进行说明， 但这并不构成对本 发明的限制。
下面将分别说明本发明实施例中相应的 M2M业务通信实体， 以及 M2M业务管理实体 需要执行的具体处理过程。
(一） M2M业务通信实体
如图 2所示，本发明实施例提供的 M2M业务优化方法在具体实现过程中，相应的 M2M 业务通信实体执行的操作具体可以包括以下步骤：
步骤 21， 获取 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少一项； 例如，相应的获取 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少一 项可以包括：
( 1 ) MME/SGSN获取 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的 至少一项；
具体地， 对于 MME/SGSN 而言， MME/SGSN 能力支持的 Feature (例如， 相应的 MME/SGSN能力支持的 Feature可以包括 SMS (Short Messaging Service, 短消息业务） 用 Feature、 PS only ( Packet Switch only, 只有分组域） Feature、 防盗用 Feature、 群 组管理 Feature、时间控制 Feature、低移动性 Feature、监控 Feature、在线数据传输 Feature、 离线数据传输 Feature等 M2M定义的 Feature)是显而易见的， 所以不需要获取； 至于 UE 支持的 Feature, MME/SGSN只需通过接收 UE发送来的 NAS消息就能够获取到携带于该 消息中的 UE支持的 Feature (例如，相应的 UE支持的 Feature可以包括 SMS用 Feature、 PS only Feature、防盗用 Feature、群组管理 Feature、时间控制 Feature、低移动性 Feature、 监控 Feature等 M2M定义的 Feature);
实施例一： 假设某 M2M业务终端 M1支持防盗用 Feature和群组管理 Feature, 为该 M2M业务终端 M1提供服务的 MME/SGSN支持防盗用 Feature和时间控制 Feature, 该 M2M业务终端 M1所签约的 Feature可以包括防盗用 Feature和群组管理 Feature; 为该 M2M业务终端 M1提供服务的 MME/SGSN可以接收该 M2M业务终端 M1发送的 NAS消 息， 并从该消息中获取到该 M2M业务终端 M1支持的 Feature (相应的该 M2M业务终端 M1支持的 Feature可以包括防盗用 Feature和群组管理 Feature);
或者，
(2) HSS/HLR获取 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少 一项；
例如， HSS/HLR可以通过接收 MME/SGSN发送的 ULR消息来获取 UE支持的 Feature 禾口 MME/SGSN能力支持的 Feature中的至少一项， 相应 UE支持的 Feature可以与相应 MME/SGSN能力支持的 Feature相同； 具体地， 相应的 MME/SGSN可以接收 UE发送来 的 NAS消息， 并从中获取 UE支持的 Feature, 然后在 ULR消息中携带所述 UE支持的 Feature和自身 MME/SGSN能力支持的 Feature发送给 HSS/HLR; HSS/HLR可以接收该 ULR消息， 并从中获取到 UE支持的 Feature和 MME/SGSN能力支持的 Feature;
实施例二：假设某 M2M业务终端 M2支持监控 Feature和 PS only Feature,为该 M2M 业务终端 M2提供服务的 MME/SGSN能够支持监控 Feature和时间控制 Feature，该 M2M 业务终端 M1所签约的 Feature可以包括监控 Feature和 PS only Feature;为该 M2M业务 终端 M2提供服务的 MME/SGSN可以接收该 M2M业务终端 M2发送来的 NAS消息， 并 从中获取该 M2M业务终端 M2支持的 Feature, 然后在 ULR消息中携带所述 M2M业务终 端 M2支持的 Feature和自身 MME/SGSN能力支持的 Feature发送给该 M2M业务终端 M2所归属的 HSS/HLR; 该 M2M业务终端 M2所归属的 HSS/HLR可以接收该 ULR消息， 并从中获取到该 M2M业务终端 M2支持的 Feature (该 M2M业务终端 M2支持的 Feature 可以包括监控 Feature和 PS only Feature) 和相应 MME/SGSN能力支持的 Feature (相 应 MME/SGSN能力支持的 Feature可以包括监控 Feature和时间控制 Feature);
步骤 22，向 M2M业务管理实体发送所述 UE支持的 Feature和 MME/SGSN能力支持 的 Feature中的至少一项；
其中， 相应的 M2M业务管理实体可以包括 MTC Server/Web/OMC等；
具体地， 针对步骤 21中不同的 M2M业务通信实体， 则该步骤具体可以包括： ( 1 ) 对于 MME/SGSN 为 M2M 业务通信实体的场合， MME/SGSN 向 MTC
Server/Web/OMC等发送所述 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的 至少一项；
进一步地， 对于 MME/SGSN为 M2M业务通信实体的场合主要是指 MME/SGSN获取 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少一项， 则由 MME/SGSN 向 MTC Server/Web/OMC等发送所述 UE支持的 Feature禾 Π MME/SGSN 能力支持的 Feature中的至少一项；
相应的实施例一： 当为该 M2M业务终端 M1提供服务的 MME/SGSN获取到该 M2M 业务终端 M1支持的 Feature和自身 MME/SGSN能力支持的 Feature后， 该 MME/SGSN 可以向当前为该 M2M业务终端 M1提供服务的 MTC Server/Web/OMC等发送该 M2M业 务终端 M1支持的 Feature (该 M2M业务终端 M1支持的 Feature可以包括防盗用 Feature 和群组管理 Feature) 和相应 MME/SGSN能力支持的 Feature (相应 MME/SGSN能力支 持的防盗用 Feature和时间控制 Feature)
或者，
( 2 ) 对于 HSS/HLR 为 M2M 业务通信实体的场合， HSS/HLR 向 MTC Server/Web/OMC等 /OMC等发送所述 UE支持的 Feature禾 B MME/SGSN 能力支持的 Feature中的至少一项；
进一步地， 对于 HSS/HLR为 M2M业务通信实体的场合主要是指 HSS/HLR获取 UE 支持的 Feature和 MME/SGSN能力支持的 Feature中的至少一项，则由 HSS/HLR向 MTC Server/Web/OMC等发送所述 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的 至少一项；
相应的实施例二： 当该 M2M业务终端 M2所归属的 HSS/HLR获取到该 M2M业务终 端 M2支持的 Feature和自身 MME/SGSN能力支持的 Feature后， 该 HSS/HLR可以向当 前为该 M2M业务终端 M2提供服务的 MTC Server/Web/OMC等发送该 M2M业务终端 M2 支持的 Feature (该 M2M业务终端 M2支持的 Feature可以包括监控 Feature和 PS only Feature)和相应 MME/SGSN能力支持的 Feature (相应 MME/SGSN能力支持的 Feature 可以包括监控 Feature和时间控制 Feature) 中的至少一项。 在上述步骤 21所述技术方案的基础上， 如图 3所示， 相应的 M2M业务通信实体在具 体实施过程中， 还可以包括如下的操作步骤：
步骤 31： 获取 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少一项； 具体地， 该步骤的技术方案与步骤 21所述的技术方案完全相同， 此处不在赘述； 步骤 32: 根据 UE支持的 Feature、 MME/SGSN能力支持的 Feature和用户签约的 Feature确定不可使用 Feature;
其中， 相应的不可使用 Feature是指在已经激活或正在激活的 Feature中， UE不支持 的 Feature禾口 /或 MME/SGSN能力不支持的 Feature;
具体地， 针对步骤 31中不同的 M2M业务通信实体， 则该步骤具体可以包括：
( 1 )在进行完步骤 31后，对于 MME/SGSN为 M2M业务通信实体的场合， MME/SGSN 根据步骤 31 中获取的 UE 支持的 Feature和 MME/SGSN 能力支持的 Feature, 以及 MME/SGSN所保存的或 HSS/HLR所下发的用户签约的 Feature确定不可使用 Feature; 相应的实施例一： 在进行完步骤 31后， 对于 MME/SGSN为 M2M业务通信实体的场 合，为该 M2M业务终端 M1提供服务的 MME/SGSN根据步骤 31中获取的该 M2M业务终 端 M1支持的 Feature (该 M2M业务终端 M1支持的 Feature可以包括防盗用 Feature和 群组管理 Feature) 和相应 MME/SGSN能力支持的 Feature (相应 MME/SGSN能力支持 的 Feature可以包括防盗用 Feature和时间控制 Feature), 以及 MME/SGSN所保存的或 HSS/HLR所下发的用户签约的 Feature (该 M2M业务终端 M1所签约的 Feature可以包括 防盗用 Feature和群组管理 Feature) 确定不可使用 Feature (相应的不可使用 Feature包 括群组管理 Feature和时间控制 Feature);
或者，
(2) 在进行完步骤 31后， 对于 HSS/HLR为 M2M业务通信实体的场合， HSS/HLR 根据从步骤 31 中获取的 UE支持的 Feature和 MME/SGSN能力支持的 Feature, 以及该 HSS/HLR所保存的已经激活的 Feature确定不可使用 Feature;
相应的实施例二： 在进行完步骤 31后， 对于 HSS/HLR为 M2M业务通信实体的场合， 该 M2M业务终端 M2所归属的 HSS/HLR根据步骤 31中获取的该 M2M业务终端 M2支持 的 Feature (该 M2M业务终端 M2支持的 Feature可以包括监控 Feature和 PS only Feature) 和相应 MME/SGSN能力支持的 Feature (相应 MME/SGSN能力支持的 Feature可以包括 监控 Feature和时间控制 Feature), 以及该 HSS/HLR所保存的已经激活的 Feature (该 M2M业务终端 M1所签约的 Feature可以包括监控 Feature和 PS only Feature)确定不可 使用 Feature (相应的不可使用 Feature包括 PS only Feature和时间控制 Feature);
步骤 33: 向 M2M业务管理实体发送所述不可使用 Feature;
其中， 相应的 M2M业务管理实体可以包括 MTC Server/Web/OMC等；
具体地， 该步骤的处理基本与步骤 22相似， 可将本步骤中的不可使用 Feature与步骤
22中的 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少一项同时发送给 所述 MTC Server/Web/OMC等， 其具体实现可以包括：
( 1 ) 对于 MME/SGSN 为 M2M 业务通信实体的场合， 由 MME/SGSN 向 MTC Server/Web/OMC等发送 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少 一项， 以及所述不可使用 Feature;
相应的实施例一： 对于 MME/SGSN为 M2M业务通信实体的场合， 由为该 M2M业务 终端 M1 提供服务的 MME/SGSN 向当前为该 M2M 业务终端 M2 提供服务的 MTC Server/Web/OMC等发送该 M2M业务终端 M1支持的 Feature (该 M2M业务终端 M1支 持的 Feature可以包括防盗用 Feature和群组管理 Feature)和相应 MME/SGSN能力支持 的 Feature (相应 MME/SGSN能力支持的 Feature可以包括防盗用 Feature和时间控制 Feature) 中的至少一项， 以及所述不可使用 Feature (相应的不可使用 Feature包括群组 管理 Feature和时间控制 Feature);
或者，
( 2 ) 对于 HSS/HLR 为 M2M 业务通信实体的场合， 由 HSS/HLR 向 MTC Server/Web/OMC等发送 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少 一项， 以及所述不可使用 Feature;
相应的实施例二： 对于 HSS/HLR为 M2M业务通信实体的场合， 由该 M2M业务终端 M2所归属的 HSS/HLR向当前为该 M2M业务终端 M2提供服务的 MTC Server/Web/OMC 等发送该 M2M业务终端 M2支持的 Feature (该 M2M业务终端 M2支持的 Feature可以包 括监控 Feature 禾 Π PS only Feature ) 和相应 MME/SGSN 能力支持的 Feature (相应 MME/SGSN能力支持的 Feature可以包括监控 Feature和时间控制 Feature) 中的至少一 项， 以及所述不可使用 Feature (相应的不可使用 Feature包括 PS only Feature和时间控 制 Feature )。 此外， 对于 M2M业务管理实体返回消息的场合， 相应的 M2M业务通信实体的具体操 作步骤还可以包括：
( 1 ) MME/SGSN 接收可激活 Feature 和 /或可去激活 Feature, 并将所述的可激活 Feature和 /或可去激活 Feature通知给 HSS/HLR;所述 HSS/HLR再对所述可激活 Feature 进行激活处理和 /或对所述可去激活 Feature进行去激活处理；
其中， 所述的可激活 Feature是指在 M2M业务的用户签约的 Feature中， 除去已经激 活或正在激活的 Feature后， UE和 MME/SGSN能力均支持的 Feature;
其中， 所述的可去激活 Feature是指在 M2M业务的已经激活的 Feature中， UE所不 支持的 Feature禾口 /或 MME/SGSN能力不支持的 Feature;
可选地， MME/SGSN 可以先接收可激活 Feature和 /或可去激活 Feature, 然后根据 MME/SGSN中所保存的 UE支持的 Feature和该 MME/SGSN能力支持的 Feature中的至 少一项确定接收到的可激活 Feature 是否能够被激活， 如果能够被激活， 则将该可激活 Feature通知给 HSS/HLR， 所述 HSS/HLR再对所述可激活 Feature进行激活处理； 如果 不能够被激活， 则将该可激活 Feature也作为可去激活 Feature通知给 HSS/HLR, 所述 HSS/HLR再对所述可去激活 Feature进行去激活处理； 对于 MME/SGSN接收到的可去激 活 Feature, 可以直接将其通知给 HSS/HLR， 所述 HSS/HLR再对所述可去激活 Feature 进行去激活处理；
相应的实施例一： 为该 M2M业务终端 M1提供服务的 MME/SGSN可以先接收当前为 该 M2M业务终端 M1提供服务的 MTC Server/Web/OMC等返回的可激活 Feature (相应 的可激活 Feature 可以包括防盗用 Feature) 和 /或可去激活 Feature (相应的可去激活 Feature可以包括群组管理 Feature和时间控制 Feature),然后根据 MME/SGSN中所保存 的 UE支持的 Feature和该 MME/SGSN能力支持的 Feature中的至少一项确定接收到的可 激活 Feature (相应的可激活 Feature可以包括防盗用 Feature) 是否能够被激活， 因为该 可激活 Feature能够被激活， 所以将该可激活 Feature通知给 HSS/HLR, 所述 HSS/HLR 再对所述可激活 Feature (相应的可激活 Feature可以包括防盗用 Feature)进行激活处理； 对于 MME/SGSN 接收到的可去激活 Feature, 可以直接将其通知给 HSS/HLR， 所述 HSS/HLR再对所述可去激活 Feature (相应的可去激活 Feature可以包括群组管理 Feature 和时间控制 Feature) 进行去激活处理； 或者，
(2 ) HSS/HLR 直接接收可激活 Feature 和 /或可去激活 Feature, 并对所述可激活 Feature进行激活处理和 /或对所述可去激活 Feature进行去激活处理；
可选地， HSS/HLR 可以先接收可激活 Feature 和 /或可去激活 Feature , 然后根据 HSS/HLR中所保存的 UE支持的 Feature和该 MME/SGSN能力支持的 Feature中的至少 一项确定接收到的可激活 Feature是否能够被激活，如果能够被激活，则将该可激活 Feature 进行激活处理； 如果不能够被激活， 则将该可激活 Feature也作为可去激活 Feature, 并对 所述可去激活 Feature进行去激活处理；对于 HSS/HLR接收到的可去激活 Feature可以直 接进行去激活处理；
相应的实施例二：该 M2M业务终端 M2所归属的 HSS/HLR可以先接收当前为该 M2M 业务终端 M2提供服务的 MTC Server/Web/OMC等返回的可激活 Feature (相应的可激活 Feature可以包括监控 Feature) 和 /或可去激活 Feature (相应的可去激活 Feature可以包 括 PS only Feature和时间控制 Feature), 然后根据 HSS/HLR 中所保存的 UE支持的 Feature和该 MME/SGSN能力支持的 Feature中的至少一项确定接收到的可激活 Feature (相应的可激活 Feature可以包括监控 Feature) 是否能够被激活， 因为该可激活 Feature 能够被激活， 所以将该可激活 Feature (相应的可激活 Feature可以包括监控 Feature) 进 行激活处理； 对于 HSS/HLR接收到的可去激活 Feature (相应的可去激活 Feature可以包 括 PS only Feature和时间控制 Feature) 可以直接进行去激活处理。 (二） M2M业务管理实体
如图 4所示，本发明实施例提供的 M2M业务优化方法在具体实现过程中，与前述 M2M 业务通信实体相对应的 M2M业务管理实体执行的操作具体可以包括以下步骤：
步骤 41， 接收 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少一项； 具体地， MTC Server/Web/OMC等接收 UE支持的 Feature和 MME/SGSN能力支持 的 Feature中的至少一项；
相应的实施例一： 当前为该 M2M业务终端 M1提供服务的 MTC Server/Web/OMC等 接收为该 M2M业务终端 M2提供服务的 MME/SGSN发送的该 M2M业务终端 M1支持的 Feature (该 M2M 业务终端 M1 支持的 Feature 可以包括防盗用 Feature 和群组管理 Feature)和相应 MME/SGSN能力支持的 Feature (相应 MME/SGSN能力支持的 Feature 可以包括防盗用 Feature和时间控制 Feature) 中的至少一项；
相应的实施例二： 当前为该 M2M业务终端 M2提供服务的 MTC Server/Web/OMC等 接收该 M2M业务终端 M2所归属的 HSS/HLR发送的该 M2M业务终端 M2支持的 Feature (该 M2M业务终端 M2支持的 Feature可以包括监控 Feature和 PS only Feature)和相应 MME/SGSN 能力支持的 Feature (相应 MME/SGSN 能力支持的 Feature可以包括监控 Feature和时间控制 Feature) 中的至少一项；
步骤 42， 根据所述 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少 一项， 以及用户签约的 Feature和 /或运营商的经营策略确定可激活 Feature,并对所述可激 活 Feature进行激活处理；
其中， 相应的可激活 Feature是指在 M2M业务的用户签约的 Feature中， 除去已经激 活或正在激活的 Feature后， UE和 MME/SGSN能力均支持的 Feature;
具体地， MTC Server/Web/OMC等根据所述 UE支持的 Feature和 MME/SGSN能力 支持的 Feature中的至少一项， 以及用户签约的 Feature和 /或运营商的经营策略确定可激 活 Feature, 并对所述可激活 Feature进行激活处理；
相应的实施例一： 当前为该 M2M业务终端 M1提供服务的 MTC Server/Web/OMC等 根据该 M2M业务终端 M1支持的 Feature (该 M2M业务终端 M1支持的 Feature可以包括 防盗用 Feature 和群组管理 Feature) 和相应 MME/SGSN 能力支持的 Feature (相应 MME/SGSN能力支持的 Feature可以包括防盗用 Feature和时间控制 Feature) 中的至少 一项， 以及用户签约的 Feature (相应的用户签约的 Feature可以包括防盗用 Feature和群 组管理 Feature) 和 /或运营商的经营策略 （相应的运营商的经营策略可以包括对于已经激 活的 Feature 就不再判断是否为定可激活 Feature) 确定可激活 Feature (相应的可激活 Feature可以包括防盗用 Feature), 并对所述可激活 Feature进行激活处理；
相应的实施例二： 当前为该 M2M业务终端 M2提供服务的 MTC Server/Web/OMC等 根据该 M2M业务终端 M2支持的 Feature (该 M2M业务终端 M2支持的 Feature可以包括 监控 Feature 禾 Π PS only Feature ) 和相应 MME/SGSN 能力支持的 Feature (相应 MME/SGSN能力支持的 Feature可以包括监控 Feature和时间控制 Feature) 中的至少一 项，以及用户签约的 Feature (相应的用户签约的 Feature可以包括监控 Feature和 PS only Feature ) 和 /或运营商的经营策略 （相应的运营商的经营策略可以包括对于已经激活的 Feature就不再判断是否为定可激活 Feature)确定可激活 Feature (相应的可激活 Feature 可以包括监控 Feature), 并对所述可激活 Feature进行激活处理；
与上述确定可激活 Feature的过程相类似地， 该步骤还可以包括确定可去激活 Feature 的过程，其具体处理内容如下：根据 UE支持的 Feature和 MME/SGSN能力支持的 Feature 中的至少一项， 以及用户签约的 Feature和 /或运营商的经营策略确定可去激活 Feature,并 对所述可去激活 Feature进行去激活处理；
其中， 相应的可去激活 Feature是指在 M2M业务的已经激活的 Feature中， UE不支 持的 Feature禾口 /或 MME/SGSN能力不支持的 Feature;
具体地， MTC Server/Web/OMC等根据所述 UE支持的 Feature和 MME/SGSN能力 支持的 Feature中的至少一项， 以及用户签约的 Feature和 /或运营商的经营策略确定可去 激活 Feature, 并对所述可去激活 Feature进行去激活处理；
相应的实施例一： 当前为该 M2M业务终端 M1提供服务的 MTC Server/Web/OMC等 根据该 M2M业务终端 M1支持的 Feature (该 M2M业务终端 M1支持的 Feature可以包括 防盗用 Feature 和群组管理 Feature) 和相应 MME/SGSN 能力支持的 Feature (相应 MME/SGSN能力支持的 Feature可以包括防盗用 Feature和时间控制 Feature) 中的至少 一项， 以及用户签约的 Feature (相应的用户签约的 Feature可以包括防盗用 Feature和群 组管理 Feature) 和 /或运营商的经营策略 （相应的运营商的经营策略可以包括仅对已经激 活的 Feature进行判断是否为定可去激活 Feature) 确定可去激活 Feature (相应的可去激 活 Feature可以包括时间控制 Feature和群组管理 Feature), 并对所述可去激活 Feature 进行去激活处理；
相应的实施例二： 当前为该 M2M业务终端 M2提供服务的 MTC Server/Web/OMC等 根据该 M2M业务终端 M2支持的 Feature (该 M2M业务终端 M2支持的 Feature可以包括 监控 Feature 禾 Π PS only Feature ) 和相应 MME/SGSN 能力支持的 Feature (相应 MME/SGSN能力支持的 Feature可以包括监控 Feature和时间控制 Feature) 中的至少一 项，以及用户签约的 Feature (相应的用户签约的 Feature可以包括监控 Feature和 PS only Feature ) 和 /或运营商的经营策略 （相应的运营商的经营策略可以包括仅对已经激活的 Feature 进行判断是否为定可去激活 Feature) 确定可去激活 Feature (相应的可去激活 Feature可以包括 PS only Feature和时间控制 Feature), 并对所述可去激活 Feature进行 去激活处理。 除此之外， 如图 5所示， 相应的 M2M业务通信实体在具体实施过程中， 还可以包括如 下的操作步骤：
步骤 51： 接收 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少一项， 以及不可使用 Feature;
其中， 相应的不可使用 Feature是指在已经激活或正在激活的 Feature中， UE不支持 的 Feature禾口 /或 MME/SGSN能力不支持的 Feature;
具体地，可以在接收 UE支持的 Feature和 MME/SGSN能力支持的 Feature中至少一 项的同时接收不可使用 Feature, 该步骤具体处理与步骤 41中相似， 不在赘述；
步骤 52: 根据所述 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少 一项，以及用户签约的 Feature和运营商的经营策略中的至少一项，和所述不可使用 Feature 确定可激活 Feature, 并对所述可激活 Feature进行激活处理；
具体地， 在步骤 42所述技术方案的基础上， 将所述不可使用 Feature作为确定可激活 Feature和 /或可去激活 Feature的辅助条件； 例如， 可以为如果一个 Feature是不可使用 Feature, 那么就可以确定这个 Feature为可去激活 Feature;
相应的实施例一： 当前为该 M2M业务终端 M1提供服务的 MTC Server/Web/OMC等 接收为该 M2M业务终端 M2提供服务的 MME/SGSN发送的该 M2M业务终端 M1支持的 Feature和相应 MME/SGSN能力支持的 Feature中的至少一项， 以及不可使用 Feature; 相应的 MTC Server/Web/OMC 等根据该 M2M 业务终端 M1 支持的 Feature 和相应 MME/SGSN 能力支持的 Feature 中的至少一项和不可使用 Feature (相应的不可使用 Feature可以包括时间控制 Feature和群组管理 Feature), 以及用户签约的 Feature禾口/或 运营商的经营策略 (相应的运营商的经营策略可以包括如果是不可使用 Feature就直接判断 成是可去激活 Feature ) 确定可激活 Feature (相应的可激活 Feature 可以包括防盗用 Feature) 和 /或可去激活 Feature (相应的可去激活 Feature可以包括时间控制 Feature和 群组管理 Feature), 并对所述可激活 Feature进行激活处理， 对所述可去激活 Feature进 行去激活处理；
相应的实施例二： 当前为该 M2M业务终端 M2提供服务的 MTC Server/Web/OMC等 接收该 M2M业务终端 M2所归属的 HSS/HLR发送的该 M2M业务终端 M2支持的 Feature 和相应 MME/SGSN 能力支持的 Feature 中的至少一项， 以及不可使用 Feature; 相应的 MTC Server/Web/OMC等根据该 M2M业务终端 M2支持的 Feature和相应 MME/SGSN 能力支持的 Feature中的至少一项和不可使用 Feature (相应的不可使用 Feature可以包括 PS only Feature和时间控制 Feature),以及用户签约的 Feature和 /或运营商的经营策略（相 应的运营商的经营策略可以包括如果是不可使用 Feature 就直接判断成是可去激活 Feature) 确定可去激活 Feature (相应的可激活 Feature可以包括监控 Feature) 和 /或可 去激活 Feature (相应的可去激活 Feature可以包 PS only Feature和时间控制 Feature), 并对所述可激活 Feature进行激活处理， 对所述可去激活 Feature进行去激活处理。 此外，在 M2M业务管理实体确定出可激活 Feature和 /或可去激活 Feature后，相应的
M2M业务管理实体还可以执行如下操作步骤： MTC Server/Web/OMC等发送所述可激活
Feature禾口 /或所述可去激活 Feature;
相应的实施例一： 当前为该 M2M业务终端 M1提供服务的 MTC Server/Web/OMC等 向相应的 MME/SGSN或 HSS/HLR发送所述可激活 Feature (相应的可激活 Feature可以 包括防盗用 Feature)和 /或所述可去激活 Feature (相应的可去激活 Feature可以包括时间 控制 Feature和群组管理 Feature);
相应的实施例二： 当前为该 M2M业务终端 M2提供服务的 MTC Server/Web/OMC等 向相应的 MME/SGSN或 HSS/HLR发送所述可激活 Feature (相应的可激活 Feature可以 包括监控 Feature)和 /或所述可去激活 Feature (相应的可去激活 Feature可以包括 PS only
Feature和时间控制 Feature)。 除了上述技术方案外，本发明实施例提供的 M2M业务优化方法还包括另一种与之类似 的方案， 以使 M2M业务管理实体获知 UE和 /或 MME/SGSN所支持优化方案。下面将分别 说明另一种方案中相应的 M2M业务通信实体， 以及 M2M业务管理实体需要执行的具体处 理过程。
(一） M2M业务通信实体
如图 6所示，本发明实施例提供的 M2M业务优化方法在具体实现过程中，相应的 M2M 业务通信实体执行的操作具体可以包括以下步骤：
步骤 61， 根据 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少一项， 以及用户签约的 Feature 和 /或运营商的经营策略确定可激活 Feature 和 /或可去激活 Feature, 并对所述可激活 Feature进行激活处理和 /或对所述可去激活 Feature进行去激活 处理；
其中， 相应的可激活 Feature是指在 M2M业务的用户签约的 Feature中， 除去已经激 活或正在激活的 Feature后， UE和 MME/SGSN能力均支持的 Feature;
其中， 相应的可去激活 Feature是指在 M2M业务的已经激活的 Feature中， UE不支 持的 Feature禾口 /或 MME/SGSN能力不支持的 Feature;
其中，相应的根据 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少一 项， 以及用户签约的 Feature 和 /或运营商的经营策略确定可激活 Feature 和 /或可去激活 Feature可以包括：
( 1 ) MME/SGSN根据 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的 至少一项， 以及用户签约的 Feature和 /或运营商的经营策略确定可激活 Feature和 /或可去 激活 Feature;
实施例三： 假设某 M2M业务终端 M3支持防盗用 Feature和群组管理 Feature, 为该 M2M业务终端 M3提供服务的 MME/SGSN支持防盗用 Feature和时间控制 Feature, 该 M2M业务终端 M3所签约的 Feature可以包括防盗用 Feature和时间控制 Feature; 为该 M2M业务终端 M3提供服务的 MME/SGSN根据该 M2M业务终端 M3支持的 Feature (该 M2M业务终端 M3支持的 Feature可以包括防盗用 Feature和群组管理 Feature) 和相应 MME/SGSN能力支持的 Feature (相应 MME/SGSN能力支持的 Feature可以包括防盗用 Feature和时间控制 Feature) 中的至少一项， 以及用户签约的 Feature (相应的用户签约 的 Feature可以包括防盗用 Feature和时间控制 Feature)和 /或运营商的经营策略（相应的 运营商的经营策略可以包括对于已经激活的 Feature就不再判断是否为定可激活 Feature) 确定可激活 Feature (相应的可激活 Feature 可以包括防盗用 Feature) 和 /或可去激活 Feature (相应的可去激活 Feature可以包括群组管理 Feature和时间控制 Feature); 或者，
(2) HSS/HLR根据 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少 一项， 以及用户签约的 Feature和 /或运营商的经营策略确定可激活 Feature和 /或可去激活 Feature;
实施例四： 假设某 M2M业务终端 M4支持时间控制 Feature和 PS only Feature, 为 该 M2M业务终端 M4提供服务的 MME/SGSN能够支持监控 Feature和时间控制 Feature, 该 M2M业务终端 M4所签约的 Feature可以包括监控 Feature和时间控制 Feature;该 M2M 业务终端 M4所归属的 HSS/HLR根据该 M2M业务终端 M4支持的 Feature (该 M2M业务 终端 M4支持的 Feature可以包括时间控制 Feature和 PS only Feature)和相应 MME/SGSN 能力支持的 Feature (相应 MME/SGSN能力支持的 Feature可以包括监控 Feature和时间 控制 Feature) 中的至少一项， 以及用户签约的 Feature (相应的用户签约的 Feature可以 包括监控 Feature和时间控制 Feature)和 /或运营商的经营策略（相应的运营商的经营策略 可以包括对于已经激活的 Feature就不再判断是否为定可激活 Feature)确定可激活 Feature (相应的可激活 Feature可以包括时间控制 Feature)和 /或可去激活 Feature (相应的可去 激活 Feature可以包括 PS only Feature和监控 Feature); 进一步地， 相应的对所述可激活 Feature进行激活处理和 /或对所述可去激活 Feature 进行去激活处理可以包括：
( 1 ) 对于 MME/SGSN 为 M2M 业务通信实体的场合， MME/SGSN 确定出可激活 Feature和 /或可去激活 Feature后， 将所述可激活 Feature和 /或可去激活 Feature发送给 HSS/HLR; 再由 HSS/HLR 对所述可激活 Feature 进行激活处理和 /或对所述可去激活 Feature进行去激活处理；
相应的实施例三： 对于 MME/SGSN为 M2M业务通信实体的场合， 为该 M2M业务终 端 M3提供服务的 MME/SGSN确定出可激活 Feature (相应的可激活 Feature可以包括防 盗用 Feature)和 /或可去激活 Feature (相应的可去激活 Feature可以包括群组管理 Feature 和时间控制 Feature)后， 将所述可激活 Feature和 /或可去激活 Feature发送给该 M2M业 务终端 M3所归属的 HSS/HLR;再由该 M2M业务终端 M3所归属的 HSS/HLR对所述可激 活 Feature进行激活处理和 /或对所述可去激活 Feature进行去激活处理；
或者，
(2) 对于 HSS/HLR为 M2M业务通信实体的场合， HSS/HLR确定出可激活 Feature 和 /或可去激活 Feature后， HSS/HLR直接对所述可激活 Feature进行激活处理和 /或对所 述可去激活 Feature进行去激活处理
相应的实施例四：对于 HSS/HLR为 M2M业务通信实体的场合，该 M2M业务终端 M4 所归属的 HSS/HLR 确定出可激活 Feature (相应的可激活 Feature 可以包括时间控制 Feature) 和 /或可去激活 Feature (相应的可去激活 Feature可以包括 PS only Feature和 监控 Feature) 后， HSS/HLR直接对所述可激活 Feature进行激活处理和 /或对所述可去激 活 Feature进行去激活处理；
步骤 62， 向 M2M业务处理实体发送可激活 Feature和 /或可去激活 Feature;
其中， 相应的 M2M业务管理实体可以包括 MTC Server/Web/OMC， 但不限于这些网 元等；
具体地， 针对步骤 61中不同的 M2M业务通信实体， 则该步骤具体可以包括： ( 1 )对于 MME/SGSN为 M2M业务通信实体的场合， MME/SGSN向 M2M业务处理 实体发送可激活 Feature和 /或可去激活 Feature;
进一步地， 对于 MME/SGSN 为 M2M业务通信实体的场合， MME/SGSN 可以在向 HSS/HLR发送可激活 Feature和 /或可去激活 Feature的同时， 向 MTC Server/Web/OMC 等发送可激活 Feature和 /或可去激活 Feature;
相应的实施例三： 对于 MME/SGSN为 M2M业务通信实体的场合， 为该 M2M业务终 端 M3提供服务的 MME/SGSN可以在向该 M2M业务终端 M3所归属的 HSS/HLR发送可 激活 Feature和 /或可去激活 Feature的同时， 向当前为该 M2M业务终端 M3提供服务的 MTC Server/Web/OMC 等发送可激活 Feature (相应的可激活 Feature 可以包括防盗用 Feature) 和 /或可去激活 Feature (相应的可去激活 Feature可以包括群组管理 Feature和 时间控制 Feature);
或者，
( 1 ) 对于 HSS/HLR 为 M2M 业务通信实体的场合， HSS/HLR 向 MTC Server/Web/OMC等发送可激活 Feature和 /或可去激活 Feature;
相应的实施例四：对于 HSS/HLR为 M2M业务通信实体的场合，该 M2M业务终端 M4 所归属的 HSS/HLR向当前为该 M2M业务终端 M4提供服务的 MTC Server/Web/OMC等 发送可激活 Feature (相应的可激活 Feature可以包括时间控制 Feature) 和 /或可去激活 Feature (相应的可去激活 Feature可以包 PS only Feature禾口监控 Feature )。
(二） M2M业务管理实体
如图 7所示，本发明实施例提供的 M2M业务优化方法在具体实现过程中，与前述 M2M 业务通信实体相对应的 M2M业务管理实体执行的操作具体可以包括以下步骤： 步骤 71， 接收可激活 Feature和 /或可去激活 Feature;
其中， 相应的可激活 Feature是指在 M2M业务的用户签约的 Feature中， 除去已经激 活或正在激活的 Feature后， UE和 MME/SGSN能力均支持的 Feature;
其中， 相应的可去激活 Feature是指在 M2M业务的已经激活的 Feature中， UE不支 持的 Feature禾口 /或 MME/SGSN能力不支持的 Feature;
具体地， MTC Server/Web/OMC等可以接收可激活 Feature和 /或可去激活 Feature; 相应的实施例三： 当前为该 M2M业务终端 M3提供服务的 MTC Server/Web/OMC等 可以接收可激活 Feature (相应的可激活 Feature可以包括防盗用 Feature)和 /或可去激活 Feature (相应的可去激活 Feature可以包括群组管理 Feature和时间控制 Feature);
相应的实施例四： 当前为该 M2M业务终端 M4提供服务的 MTC Server/Web/OMC等 可以接收可激活 Feature (相应的可激活 Feature可以包括时间控制 Feature)和 /或可去激 活 Feature (相应的可去激活 Feature可以包括 PS only Feature和监控 Feature);
步骤 72， 对所述可激活 Feature进行激活处理和 /或对所述可去激活 Feature进行去激 活处理；
具体地， MTC Server/Web/OMC等对所述可激活 Feature进行激活处理和 /或对所述可 去激活 Feature进行去激活处理；
相应的实施例三： 当前为该 M2M业务终端 M3提供服务的 MTC Server/Web/OMC等 对所述可激活 Feature (相应的可激活 Feature可以包括防盗用 Feature)进行激活处理和 / 或对所述可去激活 Feature (相应的可去激活 Feature可以包括群组管理 Feature和时间控 制 Feature) 进行去激活处理；
相应的实施例四： 当前为该 M2M业务终端 M4提供服务的 MTC Server/Web/OMC等 对所述可激活 Feature (相应的可激活 Feature可以包括时间控制 Feature) 进行激活处理 和 /或对所述可去激活 Feature (相应的可去激活 Feature可以包括 PS only Feature和监控 Feature) 进行去激活处理。 为使本发明的目的、 技术方案和优点更加清楚， 下面列举实施例并结合附图， 对本发 明实施例提供的 M2M业务通讯实体与 M2M业务管理实体整体交互过程作进一步地详细描 述。
实施例五
如图 8所示， 以某 M2M业务终端 M5为例， 阐述本发明实施例提供的 M2M业务优化 方法。 假设该 M2M业务终端 M5支持防盗用 Feature和时间控制 Feature, 为该 M2M业 务终端 M5提供服务的 MME/SGSN支持防盗用 Feature、 时间控制 Feature和 PS only Feature, 该 M2M业务终端 M5所签约的 Feature包括防盗用 Feature、 时间控制 Feature 和 PS only Feature, 则当该 M2M业务终端 M5所归属的 HSS/HLR中保存的用户签约的 Feature已经部分激活 （相应的已经部分激活的 Feature可以包括时间控制 Feature和 PS only Feature), 并且在为该 M2M业务终端 M5服务的 MME/SGSN上没有保存与该 M2M 业务终端 M5有关的 Feature时， 该 M2M业务终端 M5运用本发明提供的 M2M业务优化 方法注册到 MME/SGSN上的具体实现步骤可以包括：
步骤 101， UE向 MME/SGSN发出 NAS消息，并且在该消息中可以携带有 UE的 IMSI， 以及 UE支持的 Feature等信息；
例如， 相应的该 M2M业务终端 M5向为该 M2M业务终端 M5服务的 MME/SGSN发 出 NAS消息， 并且在 NAS消息中可以携带有该 M2M业务终端 M5的 IMSI， 以及该 M2M 业务终端 M5支持的 Feature等信息。
步骤 102， MME/SGSN在收到上述 NAS消息后， 先将 UE支持的 Feature进行保存， 再根据 UE的 IMSI确定 UE所归属的 HSS/HLR的 ULR;
例如， 相应的 MME/SGSN在收到上述 NAS消息后， 先将该 M2M业务终端 M5支持 的 Feature进行保存，再根据该 M2M业务终端 M5的 IMSI确定该 M2M业务终端 M5所归 属的 HSS/HLR的 ULR;
步骤 103， MME/SGSN按照 ULR路由到 UE所归属的 HSS/HLR, 在相应的 ULR中 可以携带 UE支持的 Feature和 MME/SGSN能力支持的 Feature;
例如， 相应的 MME/SGSN可以按照相应的 ULR路由到该 M2M业务终端 M5所归属 的 HSS/HLR;其中，在相应的 ULR中可以携带相应的该 M2M业务终端 M5支持的 Feature 和相应的 MME/SGSN能力支持的 Feature;
步骤 104， HSS/HLR接收到 ULR后，可以根据 MME/SGSN上传的 UE支持的 Feature 和 /或 MME/SGSN能力支持的 Feature确定用户签约的 Feature中已经激活的 Feature是 否可以使用；
具体地， 根据 UE支持的 Feature和 /或 MME/SGSN能力支持的 Feature确定用户签 约的 Feature是否可以使用包括 ： 判断 UE支持的 Feature和 /或 MME/SGSN能力支持的 Feature是否与用户签约的 Feature相匹配，如果 UE支持的 Feature禾 Π/或 MME/SGSN能 力支持的 Feature均与用户签约的 Feature相匹配， 则用户签约的 Feature可以使用； 如果 UE支持的 Feature与用户签约的 Feature不匹配和 /或 MME/SGSN能力支持的 Feature与 用户签约的 Feature不匹配， 则用户签约的 Feature不可用；
例如， 相应的 HSS/HLR接收到 ULR后， 可以根据相应的 MME/SGSN上传的该 M2M 业务终端 M5支持的 Feature和 MME/SGSN能力支持的 Feature确定该 M2M业务终端 M5支持的 Feature (相应的 M2M业务终端 M5支持的 Feature可以包括防盗用 Feature和 时间控制 Feature) 和 MME/SGSN能力支持的 Feature (相应的 MME/SGSN能力支持的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature)是否与用户签约 的 Feature中已经激活的 Feature (相应的用户签约的 Feature中已经激活的 Feature可以 包括时间控制 Feature和 PS only Feature) 相匹配， 从而判断用户签约的 Feature中已经 激活的 Feature是否可以使用；
步骤 105，
( 1 ) 对于已经激活的 Feature 中可以使用的 Feature, HSS/HLR将所述可以使用的 Feature下发给 MME/SGSN ;
例如： 对于用户签约的 Feature中已经激活的 Feature (相应的用户签约的 Feature中 已经激活的 Feature可以包括时间控制 Feature和 PS only Feature)而言， 如果在该 M2M 业务终端 M5支持的 Feature (相应的该 M2M业务终端 M5支持的 Feature可以包括防盗 用 Feature和时间控制 Feature)和相应 MME/SGSN能力支持的 Feature (相应 MME/SGSN 能力支持的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature) 中 均存在与其匹配的 Feature, 则该已经激活的 Feature (相应的已经激活的 Feature可以包 括时间控制 Feature) 可以使用， 那么相应的 HSS/HLR将所述可以使用的 Feature (相应 的可以使用的 Feature可以包括时间控制 Feature) 下发给 MME/SGSN;
(2) 对于已经激活的 Feature中不可以使用的 Feature, 则该步骤可以存在如下两种 处理方案：
方案 1： HSS/HLR根据 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的 至少一项， 以及用户签约的 Feature和运营商经营策略确定可激活特征和可去激活特征； 例如： 对于用户签约的 Feature中已经激活的 Feature (相应的用户签约的 Feature中 已经激活的 Feature可以包括时间控制 Feature和 PS only Feature)而言， 如果在该 M2M 业务终端 M5支持的 Feature (相应的该 M2M业务终端 M5支持的 Feature可以包括防盗 用 Feature和时间控制 Feature, 而不包括 PS only Feature) 或者 MME/SGSN能力支持 的 Feature (相应 MME/SGSN 能力支持的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature)中存在无法与其匹配的 Feature,则该已经激活的 Feature (相 应的已经激活的 Feature可以包括 PS only Feature)不可以使用； 那么， 相应的 HSS/HLR 根据该 M2M业务终端 M5支持的 Feature (相应的该 M2M业务终端 M5支持的 Feature 可以包括防盗用 Feature和时间控制 Feature) 和相应的 MME/SGSN能力支持的 Feature (相应 MME/SGSN能力支持的 Feature可以包括防盗用 Feature、时间控制 Feature和 PS only Feature),以及用户签约的 Feature (相应用户签约的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature) 和运营商经营策略 （相应的运营商经营策略可以包 括对于已经激活的 Feature不再确定可激活特征）确定可激活特征（因为时间控制 Feature 已经激活被并且可以使用， 所以相应的可激活特征可以包括防盗用 Feature)和可去激活特 征 （相应的可去激活特征可以包括 PS only Feature);
方案 2: HSS/HLR可以将 MME/SGSN能力支持的 Feature、 UE支持的 Feature、 在 已经激活的 Feature中 MME/SGSN能力不支持的 Feature禾 Π/或 UE不支持的 Feature中的 至少一项发送给 MTC Server/Web/OMC等；
例如： 对于用户签约的 Feature中已经激活的 Feature (相应的用户签约的 Feature中 已经激活的 Feature可以包括时间控制 Feature和 PS only Feature)而言， 如果在该 M2M 业务终端 M5支持的 Feature (相应的该 M2M业务终端 M5支持的 Feature可以包括防盗 用 Feature和时间控制 Feature, 而不包括 PS only Feature) 或者 MME/SGSN能力支持 的 Feature (相应 MME/SGSN 能力支持的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature)中存在无法与其匹配的 Feature,则该已经激活的 Feature (相 应的已经激活的 Feature可以包括 PS only Feature)不可以使用； 那么， 相应的 HSS/HLR 可以将相应的 MME/SGSN能力支持的 Feature (相应 MME/SGSN能力支持的 Feature可 以包括防盗用 Feature、 时间控制 Feature和 PS only Feature)^ 该 M2M业务终端 M5支 持的 Feature (相应的该 M2M业务终端 M5支持的 Feature可以包括防盗用 Feature和时 间控制 Feature)和在已经激活的 Feature中该 M2M业务终端 M5不支持的 Feature (相应 的该 M2M业务终端 M5不支持的 Feature可以包括 PS only Feature)发送给目前为该 M2M 业务终端 M5服务的 MTC Server/Web/OMC等；
步骤 106，
( 1 )对于已经激活的 Feature中可以使用的 Feature, 则该步骤为： MME/SGSN通知 UE注册成功， 即对于可以使用的 Feature的处理结束；
例如： 相应的 ME/SGSN 通知该 M2M 业务终端 M5 注册成功， 即对于可以使用的 Feature的处理结束；
(2) 对于已经激活的 Feature中不可以使用的 Feature, 则该步骤为：
方案 1 : HSS/HLR将所述可激活特征的激活状态标识更新设置为激活， 将所述可去激 活特征的激活状态标识更新设置为去激活；
例如： 相应的 HSS/HLR 将所述可激活特征 （相应的可激活特征可以包括防盗用 Feature) 的激活状态标识更新设置为激活， 将可去激活特征 （相应的可去激活特征可以包 括 PS only Feature) 的激活状态标识更新设置为去激活；
方案 2: MTC Server/Web/OMC等根据 UE支持的 Feature和 MME/SGSN能力支持 的 Feature中的至少一项， 以及用户签约的 Feature和 /或运营商经营策略确定可激活特征 和可去激活特征；
例如：相应的 MTC Server/Web/OMC等可以根据该 M2M业务终端 M5支持的 Feature (相应的该 M2M 业务终端 M5 支持的 Feature 可以包括防盗用 Feature 和时间控制 Feature)和相应的 MME/SGSN能力支持的 Feature (相应 MME/SGSN能力支持的 Feature 可以包括防盗用 Feature、时间控制 Feature和 PS only Feature),以及用户签约的 Feature (相应用户签约的 Feature可以包括防盗用 Feature、时间控制 Feature和 PS only Feature) 和运营商经营策略 (相应的运营商经营策略可以包括对于已经激活的 Feature不再确定可激 活特征）确定可激活特征（因为时间控制 Feature已经激活被并且可以使用， 所以相应的可 激活特征可以包括防盗用 Feature)和可去激活特征（相应的可去激活特征可以包括 PS only Feature);
步骤 107，
对于已经激活的 Feature中不可以使用的 Feature, 则该步骤为：
方案 1： HSS/HLR将可激活特征和可去激活特征发送给 MTC Server/Web/OMC等； 例如： 相应的 HSS/HLR 可以将可激活特征 （相应的可激活特征可以包括防盗用
Feature)和可去激活特征（相应的可去激活特征的 Feature可以包括 PS only Feature)发 送给目前为该 M2M业务终端 M5服务的 MTC Server/Web/OMC等；
方案 2: MTC Server/Web/OMC等对所述可激活特征进行激活处理， 对所述可去激活 特征进行去激活处理； 并且将所述可激活特征和 /或可去激活特征传送给 HSS/HLR进行激 活；
例如： 相应的 MTC Server/Web/OMC等对所述可激活特征（相应的可激活特征可以包 括防盗用 Feature)进行激活处理， 对所述可去激活特征（相应的可去激活特征可以包括 PS only Feature) 进行去激活处理； 并且将所述可激活特征和可去激活特征传送给 HSS/HLR 进行激活；
步骤 108，
对于已经激活的 Feature中不可以使用的 Feature, 则该步骤为：
方案 1： HSS/HLR 可以将可激活特征下发给 MME/SGSN； 同时， MTC Server/Web/OMC 等对所述可激活特征进行激活处理， 对所述可去激活特征进行去激活处 理；
例如： 相应的 HSS/HLR可以将可激活特征的 Feature (相应的可激活特征可以包括防 盗用 Feature) 下发给相应的 MME/SGSN; 同时， 相应的 MTC Server/Web/OMC等对所 述可激活特征 （相应的可激活特征可以包括防盗用 Feature) 进行激活处理， 对所述可去激 活特征 （相应的可去激活特征可以包括 PS only Feature) 进行去激活处理；
方案 2: 对于可激活特征， HSS/HLR根据 MME/SGSN能力支持的 Feature和 UE支 持的 Feature检查可激活特征是否可以激活，如果可以激活，则将可激活特征的激活状态标 识更新设置为激活，否则，将可激活特征激活失败信息通知给相应的 MTC Server/Web/OMC 等， 相应的 MTC Server/Web/OMC等再将激活失败的可激活特征去激活； 对于可去激活特 征， HSS/HLR直接将可去激活特征的激活状态标识更新设置为去激活；
例如：对于可激活特征（相应的可激活特征可以包括防盗用 Feature),相应的 HSS/HLR 根据 MME/SGSN能力支持的 Feature和该 M2M业务终端 M5支持的 Feature进一步检查 可激活特征是否可以激活， 如果可以， 则将可激活特征 （相应的可激活特征可以包括防盗 用 Feature) 的激活状态标识更新设置为激活， 否则， 将可激活特征激活失败信息通知给相 应的 MTC Server/Web/OMC等， 相应的 MTC Server/Web/OMC等再将激活失败的可激活 特征去激活； 对于可去激活特征（相应的可去激活特征可以包括 PS only Feature), 相应的 HSS/HLR直接将可去激活特征的激活状态标识更新设置为去激活；
步骤 109，
对于已经激活的 Feature中不可以使用的 Feature, 则该步骤为：
方案 1 : MME/SGSN 向 HSS/HLR发送响应消息， 即方案一的对已经激活的 Feature 处理结束；
例如： 相应的 MME/SGSN向相应的 HSS/HLR发送响应消息， 即方案一的对已经激活 的 Feature处理结束；
方案 2: HSS/HLR可以将可激活特征下发给 MME/SGSN;
例如： 相应的 HSS/HLR 可以将可激活特征 （相应的可激活特征可以包括防盗用 Feature) 下发给相应的 MME/SGSN;
步骤 110，
对于已经激活的 Feature中不可以使用的 Feature, 则该步骤为： 方案 2: MME/SGSN 向 HSS/HLR发送响应消息， 即方案二的对已经激活的 Feature 处理结束；
例如： 相应的 MME/SGSN向相应的 HSS/HLR发送响应消息， 即方案二的对已经激活 的 Feature处理结束；
可见， 本发明实施例的实现使 M2M业务管理实体能够及时获知 UE和 /或 MME/SGSN 所支持的优化方案， 并且在用户签约的 Feature不可使用时， 能够根据 MME/SGSN能力支 持的 Feature和 /或 UE支持的 Feature确定出可激活特征和可去激活特征，从而使 M2M业 务得到优化。
实施例六
如图 9所示， 以某 M2M业务终端 M6为例， 阐述本发明实施例提供的 M2M业务优化 方法。 假如该 M2M业务终端 M6已经注册到相应的 MME/SGSN上， 并且在该 M2M业务 终端 M6所归属的 HSS/HLR中已经保存了该 M2M业务终端 M6注册的该 M2M业务终端 M6支持的 Feature和相应的 MME/SGSN能力支持的 Feature,则当目前为该 M2M业务终 端 M6服务的 MTC Server/Web/OMC等需要运用本发明提供的 M2M业务优化方法对一个 该 M2M业务终端 M6新增的 Feature (相应的该 M2M业务终端 M6新增的 Feature可以为 防盗用 Feature) 进行激活时， 其具体实现步骤可以包括：
步骤 201， MTC Server/Web/OMC等将需要激活的 Feature发送给 HSS/HLR;
例如： 目前为该 M2M业务终端 M6服务的 MTC Server/Web/OMC等将需要激活的防 盗用 Feature发送给该 M2M业务终端 M6所归属的 HSS/HLR;
步骤 202， HSS/HLR根据 UE注册的 UE支持的 Feature禾 Π/或 MME/SGSN能力支持 的 Feature判断需要激活的 Feature是否能够被激活；
例如： 由于相应的 HSS/HLR可以根据该 M2M业务终端 M6支持的 Feature和相应的 MME/SGSN能力支持的 Feature判断需要激活的防盗用 Feature是否能够被激活；
步骤 203，
假设 1： 如果 HSS/HLR判断出需要激活的 Feature能够被激活， 则 HSS/HLR可以将 能够被激活的 Feature的激活状态标识更新设置为激活，并且将新激活的 Feature通过 IDR 消息（插入用户消息， 用于当 HSS/HLR中用户签约的 Feature发生变更后， 通知给目前正 为用户终端服务的 MME/SGSN ) 下发给相应的 MME/SGSN;
例如： 如果该 M2M业务终端 M6支持的 Feature和相应的 MME/SGSN能力支持的
Feature都能够支持所述的防盗用 Feature, 则相应的 HSS/HLR可确定该防盗用 Feature 能够被激活；那么，相应的 HSS/HLR将该防盗用 Feature的激活状态标识更新设置为激活， 并且将该防盗用 Feature 通过 IDR 消息下发给为该 M2M 业务终端 M6 提供服务的 MME/SGSN;
假设 2: 如果 HSS/HLR判断出需要激活的 Feature不能被激活， 则 HSS/HLR可将不 能被激活的 Feature的激活失败信息、以及 UE注册的 MME/SGSN能力支持的 Feature和 /或 UE支持的 Feature发送给 MTC Server/Web/OMC等；
例如： 如果该 M2M业务终端 M6支持的 Feature和相应的 MME/SGSN能力支持的 Feature中的至少一项不支持所述的防盗用 Feature, 则相应的 HSS/HLR可确定该防盗用 Feature不能被激活； 那么， 相应的 HSS/HLR可将该防盗用 Feature的激活失败信息， 以 及该 M2M业务终端 M6支持的 Feature和相应的 MME/SGSN能力支持的 Feature发送给 目前为该 M2M业务终端 M6服务的 MTC Server/Web/OMC等；
步骤 204，
对于假设 1， 则该步骤为： MME/SGSN向 HSS/HLR返回响应信息， 则该激活流程结 束；
例如： 相应的 MME/SGSN向相应的 HSS/HLR返回响应信息， 则该防盗用 Feature的 激活流程结束；
对于假设 2，则该步骤为： MTC Server/Web/OMC等根据 HSS/HLR上传的 MME/SGSN 能力支持的 Feature和 /或 UE支持的 Feature判断是否存在可激活特征， 如果存在， 则重 新执行步骤 201， 否则， 退出该激活流程；
例如： 相应的 MTC Server/Web/OMC等根据 HSS/HLR上传的该 M2M业务终端 M6 支持的 Feature和相应的 MME/SGSN能力支持的 Feature判断是否存在可激活特征，如果 存在可激活特征， 则重新执行步骤 201， 进入可激活特征的激活流程； 如果不存在可激活特 征， 则退出该防盗用 Feature的激活流程。
可见， 本发明实施例的实现使 M2M业务管理实体能够及时获知 UE和 /或 MME/SGSN 所支持的优化方案， 并且在用户签约的 Feature不可使用时， 能够根据 MME/SGSN能力支 持的 Feature和 /或 UE支持的 Feature确定出可激活特征和可去激活特征，从而使 M2M业 务得到优化。 实施例七
如图 10所示， 以某 M2M业务终端 M7为例， 阐述本发明实施例提供的 M2M业务优化 方法。 假如该 M2M业务终端 M7支持防盗用 Feature和时间控制 Feature, 为该 M2M业 务终端 M7提供服务的 MME/SGSN支持防盗用 Feature、 时间控制 Feature和 PS only Feature, 该 M2M业务终端 M7所签约的 Feature包括防盗用 Feature、 时间控制 Feature 和 PS only Feature; 若该 M2M业务终端 M7曾经成功注册到 MME/SGSN上， 但因为电 量耗尽等原因未执行正常退出方式去注册， 所以在该 MME/SGSN 中就保存了成功注册时 HSS/HLR下发的用户签约的 Feature (相应的 MME/SGSN中保存的 Feature可以包括时 间控制 Feature和 PS only Feature), 那么该 M2M业务终端 M7运用本发明提供的 M2M 业务优化方法再次注册到该 MME/SGSN上的具体实现步骤可以包括：
步骤 301， UE向 MME/SGSN发出 NAS消息，并且在该消息中可以携带有 UE的 IMSI， 以及 UE支持的 Feature等信息；
例如， 相应的该 M2M业务终端 M7向 MME/SGSN发出 NAS消息， 并且在 NAS消息 中可以携带有该 M2M业务终端 M7的 IMSI， 以及该 M2M业务终端 M7支持的 Feature等
I Ή自、 .；
步骤 302， MME/SGSN 可以根据 UE 支持的 Feature 禾 Π MME/SGSN 能力支持的 Feature确定 MME/SGSN中所保存的用户签约的 Feature是否可以使用；
例如： 由于 MME/SGSN中所保存的用户签约的 Feature是该 M2M业务终端 M7上次 成功注册时所保存的， 所以这些用户签约的 Feature均处于激活状态； 那么， 根据该 M2M 业务终端 M7支持的 Feature (相应的 M2M业务终端 M7支持的 Feature可以包括防盗用 Feature和时间控制 Feature) 和相应的 MME/SGSN能力支持的 Feature确定该 M2M业 务终端 M7支持的 Feature和相应的 MME/SGSN能力支持的 Feature (相应的 MME/SGSN 能力支持的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature) 是 否与 MME/SGSN中保存的 Feature (相应的 MME/SGSN中保存的 Feature可以包括时间 控制 Feature和 PS only Feature) 相匹配， 从而判断 MME/SGSN中所保存的用户签约的 Feature是否可以使用；
步骤 303，
( 1 ) 对于 MME/SGSN所保存的 Feature中可以使用的 Feature, 则 MME/SGSN将 所述可以使用的 Feature都通知给 HSS/HLR;
例如： 对于相应 MME/SGSN所保存的 Feature中可以使用的 Feature (相应的可以使 用的 Feature可以包括时间控制 Feature), 则 MME/SGSN将所述可以使用的 Feature通 知给 HSS/HLR;
(2) 对于 MME/SGSN所保存的 Feature中不可以使用的 Feature, 贝 U MME/SGSN 将所述 UE支持的 Feature、 所述 MME/SGSN能力支持的 Feature、 以及在 MME/SGSN 所保存的 Feature中 MME/SGSN能力不支持的 Feature禾 Π/或 UE不支持的 Feature (即所 述不可以使用的 Feature) 通知给 HSS/HLR;
例如： 对于相应 MME/SGSN所保存的 Feature中不可以使用的 Feature (相应的不可 以使用的 Feature可以包括 PS only Feature), 则 MME/SGSN将该 M2M业务终端 M7支 持的 Feature (相应的该 M2M业务终端 M7支持的 Feature可以包括防盗用 Feature和时 间控制 Feature)、相应的 MME/SGSN能力支持的 Feature (相应 MME/SGSN能力支持的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature ) 以及所述不可 以使用的 Feature通知给该 M2M业务终端 M7所归属的 HSS/HLR;
步骤 304，
( 1 ) 对于 MME/SGSN所保存的 Feature中可以使用的 Feature, 则该步骤为： HSS/HLR给 MME/SGSN返回一个响应信息；
例如： 相应的 HSS/HLR给为该 M2M业务终端 M7提供服务的 MME/SGSN返回一个 响应信息；
(2) 对于 MME/SGSN所保存的 Feature中不可以使用的 Feature, 则该步骤可以存 在如下两种处理方案：
方案 1： HSS/HLR将所述不可以使用的 Feature进行去激活，并将所述去激活的 Feature 通知给 MTC Server/Web/OMC等；
例如： 相应的 HSS/HLR将所述不可以使用的 Feature (相应的不可以使用的 Feature 可以包括 PS only Feature)进行去激活， 并将所述去激活的 Feature通知给目前为该 M2M 业务终端 M7提供服务的 MTC Server/Web/OMC等；
方案 2 : HSS/HLR 将所述不可以使用的 Feature 进行去激活， 并将所述去激活的 Feature, 以及 UE支持的 Feature和 MME/SGSN能力支持的 Feature中的至少一项通知 给 MTC Server/Web/OMC等；
例如： 相应的 HSS/HLR将所述不可以使用的 Feature (相应的不可以使用的 Feature 可以包括 PS only Feature)进行去激活， 并将所述去激活的 Feature, 以及该 M2M业务终 端 M7支持的 Feature (相应的 M2M业务终端 M7支持的 Feature可以包括防盗用 Feature 和时间控制 Feature) 和相应的 MME/SGSN能力支持的 Feature (相应的 MME/SGSN能 力支持的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature) 中的 至少一项通知给目前为该 M2M业务终端 M7提供服务的 MTC Server/Web/OMC等；
步骤 305，
( 1 ) 对于 MME/SGSN所保存的 Feature中可以使用的 Feature, 则该步骤为： MME/SGSN通知 UE注册成功， 即可退出该处理流程；
例如：相应的 MME/SGSN通知该 M2M业务终端 M7注册成功，即可退出该处理流程； (2) 对于 MME/SGSN所保存的 Feature中不可以使用的 Feature, 则该步骤可以存 在如下两种处理方案：
方案 1： MTC Server/Web/OMC等对所述去激活的 Feature进行去激活处理， 同时， HSS/HLR根据 UE支持的 Feature和 MME/SGSN能力支持的 Feature确定适合激活的 Feature;
例如： 相应的 MTC Server/Web/OMC 等对所述去激活的 Feature (所述去激活的
Feature可以包括 PS only Feature)进行去激活处理，同时，相应的 HSS/HLR根据该 M2M 业务终端 M7支持的 Feature (相应的该 M2M业务终端 M7支持的 Feature可以包括防盗 用 Feature 和时间控制 Feature) 和相应的 MME/SGSN 能力支持的 Feature (相应的 MME/SGSN能力支持的 Feature可以包括防盗用 Feature、 时间控制 Featur和 PS only Feature)确定适合激活的 Feature (相应的适合激活的 Feature可以包括防盗用 Feature); 方案 2: MTC Server/Web/OMC等对所述去激活的 Feature进行去激活处理， 同时， 根据 UE支持的 Feature和 MME/SGSN能力支持的 Feature确定适合激活的 Feature并进 行激活处理；
例如： 相应的 MTC Server/Web/OMC等对所述去激活的 Feature (所述去激活可以包 括 PS only Feature)进行去激活处理，同时，根据该 M2M业务终端 M7支持的 Feature (相 应的该 M2M业务终端 M7支持的 Feature可以包括防盗用 Feature和时间控制 Feature) 和相应的 MME/SGSN能力支持的 Feature (相应的 MME/SGSN能力支持的 Feature可以 包括防盗用 Feature、 时间控制 Featur和 PS only Feature) 确定适合激活的 Feature (相 应的适合激活的 Feature可以包括防盗用 Feature) 并进行激活处理；
步骤 306，
对于 MME/SGSN所保存的 Feature中不可以使用的 Feature, 则该步骤可以存在如下 两种处理方案：
方案 1： HSS/HLR将适合激活的 Feature的激活状态标识更新设置为激活； 例如： 相应的 HSS/HLR将适合激活的 Feature (相应的适合激活的 Feature可以包括 防盗用 Feature) 的激活状态标识更新设置为激活；
方案 2: MTC Server/Web/OMC等将所述适合激活的 Feature通知给 HSS/HLR; 例如： 相应的 MTC Server/Web/OMC等将所述适合激活的 Feature (相应的适合激活 的 Feature可以包括防盗用 Feature) 通知给相应的 HSS/HLR;
步骤 307，
对于 MME/SGSN所保存的 Feature中不可以使用的 Feature, 则该步骤可以存在如下 两种处理方案：
方案 1： HSS/HLR将所述适合激活的 Feature通知给 MTC Server/Web/OMC等； 例如： 相应的 HSS/HLR将所述适合激活的 Feature (相应的适合激活的 Feature可以 包括防盗用 Feature ) 通知给目前为该 M2M 业务终端 M7 提供服务的 MTC
Server/Web/OMC等；
方案 2: HSS/HLR将所述适合激活的 Feature的激活状态标识更新设置为激活； 例如： 相应的 HSS/HLR将所述适合激活的 Feature (相应的适合激活的 Feature可以 包括防盗用 Feature) 的激活状态标识更新设置为激活；
步骤 308，
对于 MME/SGSN所保存的 Feature中不可以使用的 Feature, 则该步骤可以存在如下 两种处理方案：
方案 1 : HSS/HLR将所述适合激活的 Feature下发给相应的 MME/SGSN, 同时， MTC Server/Web/OMC等对所述适合激活的 Feature进行激活处理；
例如： 相应的 HSS/HLR将适合激活的 Feature (相应的适合激活的 Feature可以包括 防盗用 Feature) 下发给相应的 MME/SGSN, 同时， 相应的 MTC Server/Web/OMC等对 所述适合激活的 Feature (相应的适合激活的 Feature可以包括防盗用 Feature) 进行激活 处理；
方案 2: HSS/HLR将所述适合激活的 Feature下发给相应的 MME/SGSN;
例如： 相应的 HSS/HLR将所述适合激活的 Feature (相应的适合激活的 Feature可以 包括防盗用 Feature) 下发给相应的 MME/SGSN;
步骤 309，对于 MME/SGSN所保存的 Feature中不可以使用的 Feature,则该步骤为：
MME/SGSN向相应的 HSS/HLR发送响应消息；
例如： 相应的 MME/SGSN向相应的 HSS/HLR发送响应消息；
可见， 本发明实施例的实现使 M2M业务管理实体能够及时获知 UE和 /或 MME/SGSN 所支持的优化方案， 并且在用户签约的 Feature不可使用时， 能够根据 MME/SGSN能力支 持的 Feature和 /或 UE支持的 Feature确定出可激活特征和可去激活特征，从而使 M2M业 务得到优化。 实施例八
如图 11所示， 以某 M2M业务终端 M8为例， 阐述本发明实施例提供的 M2M业务优化 方法。 假设该 M2M业务终端 M8支持防盗用 Feature和时间控制 Feature, 为该 M2M业 务终端 M8服务的 MME/SGSN支持防盗用 Feature、时间控制 Feature和 PS only Feature, 该 M2M业务终端 M8所签约的 Feature包括防盗用 Feature、时间控制 Feature和 PS only Feature,则当该 M2M业务终端 M8所归属的 HSS/HLR中保存的用户签约的 Feature已经 部分激活（相应的已经激活的 Feature可以包括时间控制 Feature和 PS only Feature), 并 且在为该 M2M业务终端 M8服务的 MME/SGSN上没有保存与该 M2M业务终端 M8有关 的 Feature 时， 该 M2M 业务终端 M8 运用本发明提供的 M2M 业务优化方法注册到 MME/SGSN上的具体实现步骤可以包括：
步骤 401，UE向 MME/SGSN发出 NAS消息，并且在该消息中可以携带有 UE的 IMSI， 以及 UE支持的 Feature等信息；
例如， 相应的该 M2M业务终端 M8向 MME/SGSN发出 NAS消息， 并且在 NAS消息 中可以携带有该 M2M业务终端 M8的 IMSI， 以及该 M2M业务终端 M8支持的 Feature等
I Ή自、 .；
步骤 402， MME/SGSN在收到上述 NAS消息后， 先将相应的 UE支持的 Feature进 行保存， 再根据 UE的 IMSI确定 UE所归属的 HSS/HLR的 ULR;
例如， 为该 M2M业务终端 M8提供服务的 MME/SGSN在收到上述 NAS消息后， 先 将该 M2M业务终端 M8支持的 Feature进行保存， 再根据该 M2M业务终端 M8的 IMSI 等信息确定该 M2M业务终端 M8所归属的 HSS/HLR的 ULR;
步骤 405， MME/SGSN按照 ULR路由到 UE所归属的 HSS/HLR;
例如， 相应的 MME/SGSN 按照所述 ULR 路由到该 M2M 业务终端 M8 所归属的 HSS/HLR;
步骤 404， HSS/HLR接收到 ULR后， 将 HSS/HLR所保存的用户签约的 Feature中已 经激活的 Feature下发给 MME/SGSN;
例如： 该 M2M业务终端 M8所归属的的 HSS/HLR接收到 ULR后， 将 HSS/HLR所保 存的该公司签约的 Feature中已经激活的 Feature (相应的已经激活的 Feature可以包括时 间控制 Feature和 PS only Feature) 下发给相应的 MME/SGSN;
步骤 405， MME/SGSN根据所述 UE支持的 Feature和该 MME/SGSN能力支持的
Feature中的至少一项确定 HSS/HLR所下发的已经激活的 Feature是否可以使用；
例如： 相应的 HSS/HLR根据该 M2M业务终端 M8支持的 Feature (相应的 M2M业务 终端 M8 支持的 Feature 可以包括防盗用 Feature 和时间控制 Feature ) 和相应的 MME/SGSN能力支持的 Feature (相应的 MME/SGSN能力支持的 Feature可以包括时间 控制 Feature、 PS only Feature和防盗用 Feature) 确定 HSS/HLR所下发的已经激活的 Feature (相应的已经激活的 Feature可以包括时间控制 Feature和 PS only Feature)是否 可以使用；
步骤 406，
( 1 ) 对于已经激活的 Feature中可以使用的 Feature, 则 MME/SGSN通知 UE注册 成功， 即完成可以使用的 Feature的处理流程；
例如： 对于已经激活的 Feature中可以使用的 Feature (当相应的可以使用的 Feature 可以包括时间控制 Feature), 则 MME/SGSN通知该 M2M业务终端 M8注册成功， 即完成 可以使用的 Feature的处理流程；
(2) 对于已经激活的 Feature中不可以使用的 Feature, 则该步骤可以存在如下两种 处理方案：
方案 1： MME/SGSN根据 MME/SGSN能力支持的 Feature和 UE支持的 Feature中 的至少一项， 以及用户签约的 Feature和 /或运营商经营策略确定适合激活的 Feature; 例如：对于已经激活的 Feature中不可以使用的 Feature (相应的不可以使用的 Feature 可以包括 PS only Feature), 则相应的 MME/SGSN根据 MME/SGSN能力支持的 Feature (相应的 MME/SGSN能力支持的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature) 和该 M2M业务终端 M8支持的 Feature (相应的 M2M业务终端 M8支 持的 Feature可以包括防盗用 Feature和时间控制 Feature), 以及用户签约的 Feature (相 应的用户签约的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature) 和运营商经营策略 (相应的运营商经营策略可以包括已经激活的 Feature不用确定是否为适 合激活的 Feature) 确定适合激活的 Feature (相应的适合激活的 Feature可以包括防盗用 Feature);
方案 2: MME/SGSN可以将 MME/SGSN能力支持的 Feature、 UE支持的 Feature、 在已经激活的 Feature中 MME/SGSN能力不支持的 Feature禾 Π/或 UE不支持的 Feature (即 所述不可以使用的 Feature) 中的至少一项发送给 MTC Server/Web/OMC等；
例如：对于已经激活的 Feature中不可以使用的 Feature (相应的不可以使用的 Feature 可以包括 PS only Feature), 则 MME/SGSN可以将 MME/SGSN能力支持的 Feature (相 应的 MME/SGSN能力支持的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature ) 该 M2M业务终端 M8支持的 Feature (相应的 M2M业务终端 M8支持的 Feature可以包括防盗用 Feature和时间控制 Feature)、所述不可以使用的 Feature相应的 不可以使用的 Feature可以包括 PS only Feature) 中的至少一项发送给当前为该 M2M业 务终端 M8提供服务的 MTC Server/Web/OMC等；
步骤 407，
对于已经激活的 Feature中不可以使用的 Feature, 则该步骤可以存在如下两种处理方 案：
方案 1 : MME/SGSN 将所述适合激活的 Feature 分别传输给 HSS/HLR 和 MTC Server/Web/OMC等；
例如： 相应的 MME/SGSN将所述适合激活的 Feature (相应的适合激活的 Feature可 以包括防盗用 Feature) 分别传输给相应的 HSS/HLR和 MTC Server/Web/OMC等；
方案 2: MTC Server/Web/OMC等根据 MME/SGSN所上传的 MME/SGSN能力支持 的 Feature和 UE支持的 Feature中的至少一项， 以及用户签约的 Feature和运营商经营策 略确定适合激活的 Feature;
例如：相应的 MTC Server/Web/OMC等根据 MME/SGSN所上传的 MME/SGSN能力 支持的 Feature (相应的 MME/SGSN能力支持的 Feature可以包括防盗用 Feature、 时间 控制 Feature和 PS only Feature) 和该 M2M业务终端 M8支持的 Feature (相应的 M2M 业务终端 M8支持的 Feature可以包括防盗用 Feature和时间控制 Feature), 以及用户签 约的 Feature (相应的用户签约的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature)和运营商经营策略（相应的运营商经营策略可以包括已经激活的 Feature 不用确定是否为适合激活的 Feature)确定适合激活的 Feature (相应的适合激活的 Feature 可以包括防盗用 Feature);
步骤 408，
对于已经激活的 Feature中不可以使用的 Feature, 则该步骤可以存在如下两种处理方 案：
方案 1 : MTC Server/Web/OMC 等对所述适合激活的 Feature 的进行激活； 同时， HSS/HLR将所述适合激活的 Feature的激活状态标识更新设置为激活，并且向 MME/SGSN 发送响应消息；
例如： 相应的 MTC Server/Web/OMC等对所述适合激活的 Feature (相应的适合激 活的 Feature可以包括防盗用 Feature) 进行激活； 同时， 相应的 HSS/HLR将所述适合激 活的 Feature (相应的适合激活的 Feature可以包括防盗用 Feature) 的激活状态标识更新 设置为激活， 并且向 MME/SGSN发送响应消息；
方案 2 : MTC Server/Web/OMC 等将适合激活的 Feature 进行激活， 并传输给 MME/SGSN;
例如： 相应的 MTC Server/Web/OMC 等将适合激活的 Feature (相应的适合激活的
Feature可以包括防盗用 Feature) 进行激活， 并传输给 MME/SGSN;
步骤 409，
对于已经激活的 Feature中不可以使用的 Feature, 则该步骤可以存在如下处理方案： 方案 2: MME/SGSN将所述适合激活的 Feature传输给 HSS/HLR;
例如： 相应的 MME/SGSN将适合激活的 Feature (相应的适合激活的 Feature可以包 括防盗用 Feature) 传输给 HSS/HLR;
步骤 410，
对于已经激活的 Feature中不可以使用的 Feature, 则该步骤可以存在如下处理方案： 方案 2: HSS/HLR将所述适合激活的 Feature的激活状态标识更新设置为激活， 并且 向 MME/SGSN发送响应消息；
例如： 相应的 HSS/HLR将所述适合激活的 Feature (相应的适合激活的 Feature可以 包括防盗用 Feature) 的激活状态标识更新设置为激活， 并且向相应的 MME/SGSN发送响 应消息；
可见， 本发明实施例的实现使 M2M业务管理实体能够及时获知 UE和 /或 MME/SGSN 所支持的优化方案， 并且在用户签约的 Feature不可使用时， 能够根据 MME/SGSN能力支 持的 Feature和 /或 UE支持的 Feature确定出可激活特征， 从而使 M2M业务得到优化。 实施例九
如图 12所示， 以某 M2M业务终端 M9为例， 阐述本发明实施例提供的 M2M业务优化 方法。 假设该 M2M业务终端 M5支持防盗用 Feature和时间控制 Feature, 为该 M2M业 务终端 M9服务的 MME/SGSN支持防盗用 Feature、时间控制 Feature和 PS only Feature, 该 M2M业务终端 M9所签约的 Feature包括防盗用 Feature、时间控制 Feature和 PS only
Feature; 假如该 M2M业务终端 M9曾经成功注册到 MME/SGSN上， 但因为电量耗尽等 原因未执行正常退出方式去注册， 所以在该 MME/SGSN中就保存了成功注册时 HSS/HLR 下发的用户签约的 Feature (相应的 MME/SGSN 中保存的 Feature 可以包括时间控制
Feature和 PS only Feature)，那么该 M2M业务终端 M9运用本发明提供的 M2M业务优化 方法再次注册到该 MME/SGSN上的具体实现步骤可以包括：
步骤 501， UE向 MME/SGSN发出 NAS消息，并且在该消息中可以携带有 UE的 IMSI， 以及 UE支持的 Feature等信息；
例如， 相应的该 M2M业务终端 M9向 MME/SGSN发出 NAS消息， 并且在 NAS消息 中可以携带有该 M2M业务终端 M9的 IMSI， 以及该 M2M业务终端 M9支持的 Feature等
I Ή自、 .；
步骤 502， MME/SGSN可以根据 UE支持的 Feature和该 MME/SGSN能力支持的 Feature确定 MME/SGSN中所保存的用户签约的 Feature是否可以使用；
例如： 由于 MME/SGSN中所保存的用户签约的 Feature是该 M2M业务终端 M9上次 成功注册时所保存的， 所以这些用户签约的 Feature均处于激活状态； 那么， 根据该 M2M 业务终端 M9支持的 Feature和相应的 MME/SGSN能力支持的 Feature确定该 M2M业务 终端 M9支持的 Feature (相应的 M2M业务终端 M9支持的 Feature可以包括防盗用 Feature 和时间控制 Feature) 和相应的 MME/SGSN能力支持的 Feature (相应的 MME/SGSN能 力支持的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature) 是否 与 MME/SGSN中保存的 Feature (相应的 MME/SGSN中保存的 Feature可以包括时间控 制 Feature和 PS only Feature) 相匹配， 从而判断 MME/SGSN 中所保存的用户签约的 Feature是否可以使用；
步骤 503，
( 1 ) 对于 MME/SGSN所保存的 Feature中可以使用的 Feature, 则 MME/SGSN通 知 UE注册成功， 即完成可以使用的 Feature的处理流程；
例如： 对于 MME/SGSN所保存的 Feature中可以使用的 Feature (相应的可以使用的 Feature可以包括时间控制 Feature), 相应的 MME/SGSN通知该 M2M业务终端 M9注册 成功， 即完成可以使用的 Feature的处理流程；
(2) 对于 MME/SGSN所保存的 Feature中不可以使用的 Feature, 则该步骤可以存 在如下两种处理方案：
方案 1 : MME/SGSN根据该 MME/SGSN能力支持的 Feature和 UE支持的 Feature 中的至少一项， 以及 MME/SGSN 中保存的 Feature 和运营商经营策略确定适合激活的 Feature;
例如： 对于 MME/SGSN所保存的 Feature中不可以使用的 Feature (相应的不可以使 用的 Feature可以包括 PS only Feature), 则相应的 MME/SGSN根据该 M2M业务终端 M9支持的 Feature (相应的该 M2M业务终端 M9支持的 Feature可以包括防盗用 Feature 和时间控制 Feature) 和相应的 MME/SGSN能力支持的 Feature (相应的 MME/SGSN能 力支持的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature), 以及 用户签约的 Feature (相应的用户签约的 Feature可以包括防盗用 Feature、时间控制 Feature 和 PS only Feature ) 和运营商经营策略 （相应的运营商经营策略可以包括已经激活的 Feature不用确定是否为适合激活的 Feature) 确定适合激活的 Feature (相应的适合激活 的 Feature可以包括防盗用 Feature);
方案 2: MME/SGSN将所述 UE支持的 Feature、所述 MME/SGSN能力支持的 Feature、 以及在所述 MME/SGSN 所保存的 Feature 中所述 UE 不支持的 Feature 和 /或所述 MME/SGSN能力不支持的 Feature (所述的不可以使用的 Feature) 中的至少一项通知给 MTC Server/Web/OMC等；
例如： 对于 MME/SGSN所保存的 Feature中不可以使用的 Feature (相应的不可以使 用的 Feature可以包括 PS only Feature), 则 MME/SGSN将该 M2M业务终端 M9支持的 Feature (相应的该 M2M业务终端 M9支持的 Feature可以包括防盗用 Feature和时间控制 Feature ) 所述 MME/SGSN能力支持的 Feature (相应的 MME/SGSN能力支持的 Feature 可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature ) 以及所述的不可以使用 的 Feature (相应的不可以使用的 Feature可以包括 PS only Feature)通知给当前为该 M2M 业务终端 M9服务的 MTC Server/Web/OMC等；
步骤 504，
对于 MME/SGSN所保存的 Feature中不可以使用的 Feature, 则该步骤可以存在如下 两种处理方案：
方案 1 : MME/SGSN 将所述适合激活的 Feature 分别传输给 HSS/HLR 和 MTC Server/Web/OMC等；
例如： 相应的 MME/SGSN将所述适合激活的 Feature (相应的适合激活的 Feature可 以包括防盗用 Feature) 分别传输给 HSS/HLR和 MTC Server/Web/OMC等；
方案 2: MTC Server/Web/OMC等根据 MME/SGSN上传的 MME/SGSN能力支持的 Feature和 UE支持的 Feature中的至少一项， 以及用户签约的 Feature和运营商经营策略 确定适合激活的 Feature;
例如：相应的 MTC Server/Web/OMC等根据该 M2M业务终端 M9支持的 Feature (相 应的该 M2M业务终端 M9支持的 Feature可以包括防盗用 Feature和时间控制 Feature) 和相应的 MME/SGSN能力支持的 Feature (相应的 MME/SGSN能力支持的 Feature可以 包括防盗用 Feature、时间控制 Feature和 PS only Feature), 以及用户签约的 Feature (相 应的用户签约的 Feature可以包括防盗用 Feature、 时间控制 Feature和 PS only Feature) 和运营商经营策略 (相应的运营商经营策略可以包括已经激活的 Feature不用确定是否为适 合激活的 Feature) 确定适合激活的 Feature (相应的适合激活的 Feature可以包括防盗用 Feature);
步骤 505，
对于 MME/SGSN所保存的 Feature中不可以使用的 Feature, 则该步骤可以存在如下 两种处理方案：
方案 1 : MTC Server/Web/OMC等对所述适合激活的 Feature进行激活处理， 同时， HSS/HLR将所述适合激活的 Feature的激活状态标识更新设置为激活，并且向 MME/SGSN 发送响应消息；
例如： 相应的 MTC Server/Web/OMC等对所述适合激活的 Feature (相应的适合激活 的 Feature可以包括防盗用 Feature) 进行激活处理， 同时， 相应的 HSS/HLR将所述适合 激活的 Feature的激活状态标识更新设置为激活， 并且向 MME/SGSN发送响应消息； 方案 2: MTC Server/Web/OMC等将所述适合激活的 Feature传输给 MME/SGSN; 例如： 相应的 MTC Server/Web/OMC等将所述适合激活 （相应的适合激活的 Feature 可以包括防盗用 Feature) 的 Feature传输给相应的 MME/SGSN;
步骤 506，
对于 MME/SGSN所保存的 Feature中不可以使用的 Feature, 则该步骤可以存在如下 两种处理方案：
方案 2: MME/SGSN将所述适合激活的 Feature传输给 HSS/HLR;
例如： 相应的 MME/SGSN将所述适合激活的 Feature (相应的适合激活的 Feature可 以包括防盗用 Feature) 传输给相应的 HSS/HLR;
步骤 507，
对于 MME/SGSN所保存的 Feature中不可以使用的 Feature, 则该步骤可以存在如下 两种处理方案：
方案 2: HSS/HLR将所述适合激活的 Feature的激活状态标识更新设置为激活， 并且 向 MME/SGSN发送响应消息；
例如： 相应的 HSS/HLR将所述适合激活的 Feature (相应的适合激活的 Feature可 以包括防盗用 Feature) 的激活状态标识更新设置为激活， 并且向 MME/SGSN发送响应消 自 .
可见， 本发明实施例的实现使 M2M业务管理实体能够及时获知 UE和 /或 MME/SGSN 所支持的优化方案， 并且在用户签约的 Feature不可使用时， 能够根据 MME/SGSN能力支 持的 Feature和 /或 UE支持的 Feature确定出可激活特征， 从而使 M2M业务得到优化。 实施例十
如图 13所示， 以某 M2M业务终端 M10为例， 阐述本发明实施例提供的 M2M业务优 化方法。假如该 M2M业务终端 M10已经注册到相应的 MME/SGSN上， 并且在该 M2M业 务终端 M10所归属的 HSS/HLR中已经保存了该 M2M业务终端 M10注册的该 M2M业务 终端 M10支持的 Feature和相应的 MME/SGSN能力支持的 Feature, 则当目前为该 M2M 业务终端 M10服务的 MTC Server/Web/OMC等需要运用本发明提供的 M2M业务优化方 法对一个该 M2M业务终端 M10新增的 Feature (相应的该 M2M业务终端 M10新增的 Feature可以为防盗用 Feature) 进行激活时， 其具体实现步骤可以包括：
步骤 601， MTC Server/Web/OMC等到 HSS/HLR中查询 UE注册的 MME/SGSN的 信息；
例如： 目前为该 M2M业务终端 M10服务的 MTC Server/Web/OMC等到该 M2M业务 终端 M10所归属的 HSS/HLR中查询该 M2M业务终端 M10注册的 MME/SGSN的信息（相 应的 MME/SGSN的信息中可以包括用于指明该 M2M业务终端 M10所注册的 MME/SGSN 的信息）；
步骤 602， HSS/HLR将 UE注册的 MME/SGSN的信息返回给 MTC Server/Web/OMC 等- 例如：相应的 HSS/HLR将相应的该 M2M业务终端 M10注册的 MME/SGSN的信息返 回给相应的 MTC Server/Web/OMC等；
步骤 603， MTC Server/Web/OMC等将需要激活的 Feature发送给 MME/SGSN ; 例如： 相应的 MTC Server/Web/OMC等将需要激活的防盗用 Feature发送给该 M2M 业务终端 M10注册的 MME/SGSN;
步骤 604， MME/SGSN 根据该 MME/SGSN 能力支持的 Feature和 /或 UE支持的 Feature判断 MTC Server/Web/OMC等下发的需要激活的 Feature是否能够被激活；
例如：由于相应的 MME/SGSN中已经保存有该 M2M业务终端 M10注册的该 M2M业 务终端 M10支持的 Feature，所以 MME/SGSN可以根据该 MME/SGSN能力支持的 Feature 和该 M2M业务终端 M10支持的 Feature判断出 MTC Server/Web/OMC等下发的需要激活 的防盗用 Feature是否能够被激活；
步骤 605，
假设 1： 如果 MME/SGSN判断出需要激活的 Feature能够被激活， 则 MME/SGSN可 以将该能够被激活的 Feature通知给 HSS/HLR和 MTC Server/Web/OMC等；
例如： 如果所述 MME/SGSN 能力支持的 Feature和该 M2M业务终端 M10支持的
Feature都能够支持所述的防盗用 Feature，则相应的 MME/SGSN可确定该防盗用 Feature 能够被激活； 那么， 相应的 MME/SGSN可以将该防盗用 Feature通知给相应的 HSS/HLR 禾口 MTC Server/Web/OMC等；
假设 2: 如果 MME/SGSN判断出需要激活的 Feature不能被激活， 则 MME/SGSN可 将不能被激活的 Feature的激活失败信息、 MME/SGSN能力支持的 Feature和 /或 UE支持 的 Feature, 以及 MME/SGSN能力不支持的 Feature禾 Π/或 UE不支持的 Feature发送给 MTC Server/Web/OMC等；
例如：如果相应的 MME/SGSN能力不支持防盗用 Feature和 /或该 M2M业务终端 M10 不支持防盗用 Feature,则相应的 MME/SGSN可确定该防盗用 Feature不能被激活；那么， MME/SGSN 可将该防盗用 Feature 的激活失败信息、 相应的 MME/SGSN 能力支持的 Feature和 /或该 M2M业务终端 M10支持的 Feature, 以及 MME/SGSN 能力不支持的 Feature禾口 /或 UE不支持的 Feature发送给 MTC Server/Web/OMC等；
步骤 606，
对于假设 1， 则该步骤为： MTC Server/Web/OMC等对需要激活的 Feature进行激活 处理， 同时， HSS/HLR将该需要激活的 Feature的激活状态标识更新设置为激活， 并且向 MME/SGSN返回一个响应信息；
例如： 相应的 MTC Server/Web/OMC等对该防盗用 Feature进行激活处理， 同时， 相 应的 HSS/HLR 将该防盗用 Feature 的激活状态标识更新设置为激活， 并且向相应的 MME/SGSN返回一个响应信息；
对于假设 2， 则该步骤为： MTC Server/Web/OMC 等根据 MME/SGSN 上传的
MME/SGSN 能力支持的 Feature 和 /或 UE 支持的 Feature 判断是否存在适合激活的 Feature, 如果存在， 则重新执行步骤 603， 否则， 退出该激活流程；
例如：相应的 MTC Server/Web/OMC等根据所述 MME/SGSN上传的 MME/SGSN能 力支持的 Feature和 /或该 M2M业务终端 M10支持的 Feature判断是否存在适合激活的 Feature, 如果存在适合激活的 Feature, 则重新执行步骤 603， 即进入适合激活的 Feature 的激活流程； 如果不存在适合激活的 Feature, 则退出该防盗用 Feature的激活流程。 可见， 本发明实施例的实现使 M2M业务管理实体能够及时获知 UE和 /或 MME/SGSN 所支持的优化方案， 并且在用户签约的 Feature不可使用时， 能够根据 MME/SGSN能力支 持的 Feature和 /或 UE支持的 Feature确定出可激活特征， 从而使 M2M业务得到优化。
本领域普通技术人员可以理解： 实现上述实施例方法中的全部或部分流程是可以通过 程序来指令相关的硬件来完成， 所述的程序可存储于一计算机可读取存储介质中， 该程序 在执行时， 可包括如上述各方法的实施例的流程。 其中， 所述的存储介质可为磁碟、 光盘、 只读存储记忆体 （Read-Only Memory , ROM ) 或随机存储记忆体 （Random Access Memory, RAM) 等。 本发明实施例提供的 M2M业务优化装置的具体可以设置于 M2M业务通信实体 （相应 的 M2M业务通信实体可以包括 MME/SGSN或者 HSS/HLR等）， 以及 M2M业务管理实体 (相应的 M2M业务管理实体可以包括 MTC Server/Web/OMC等） 中。
下面结合附图， 分别说明本发明实施例中设置于 M2M业务通信实体或 M2M业务管理 实体中装置的具体结构。
(—） M2M业务通信实体
如图 14所示， 本发明实施例提供的 M2M业务优化装置， 相应的设置于 M2M业务通 信实体中的装置的具体结构可以包括：
( 1 ) 支持特征获取单元 1001， 用于获取终端支持的特征和移动性管理单元能力支持 的特征中的至少一项；
具体地， 如图 15所示， 相应的支持特征获取单元 1001具体可以包括：
第一支持特征获取单元 10011，设置于 MME/SGSN中，用于获取终端支持的特征和移 动性管理单元能力支持的特征中的至少一项；
或者，
第二支持特征获取单元 10012， 设置于 HSS/HLR中，用于获取终端支持的特征和移动 性管理单元能力支持的特征中的至少一项；
(2)支持特征发送单元 1002， 用于向 M2M业务管理实体发送所述支持特征获取单元 1001所获取的终端支持的特征和移动性管理单元能力支持的特征中的至少一项；
例如， 相应的支持特征发送单元 1002 可以设置于 MME/SGSN 中， 也可以设置于 HSS/HLR中， 或者两者中分别设有不同的优化特征发送单元 3002;
设置于 MME/SGSN 中的支持特征发送单元 1002 可以向所述第一支持特征获取单元
10011所获取的终端支持的特征和移动性管理单元能力支持的特征中的至少一项；
设置于 HSS/HLR 中的支持特征发送单元 1002 可以向所述第二支持特征获取单元 10012所获取的终端支持的特征和移动性管理单元能力支持的特征中的至少一项。 可选地， 如图 16所示， 本发明实施例提供的 M2M业务优化装置具体还可以包括：
( 1 )不支持特征确定单元 1003， 用于根据所述支持特征获取单元 1001所获取的终端 支持的特征和移动性管理单元能力支持的特征， 以及用户签约的特征确定不可使用特征； 其中， 相应的不可使用特征是指在已经激活或正在激活的特征中， 终端不支持的特征 和 /或移动性管理单元能力不支持的特征；
例如， 相应的不支持特征确定单元 1003可以设置于 MME/SGSN 中， 也可以设置于
HSS/HLR中， 或者两者中分别设有不同的不支持特征确定单元 1003;
设置于 MME/SGSN中的不支持特征确定单元 1003可以根据所述第一支持特征获取单 元 10011 所获取的终端支持的特征和移动性管理单元能力支持的特征， 以及用户签约的特 征确定不可使用特征；
设置于 HSS/HLR中的不支持特征确定单元 1003可以根据所述第二支持特征获取单元
10012 所获取的终端支持的特征和移动性管理单元能力支持的特征， 以及用户签约的特征 确定不可使用特征；
(2)不支持特征发送单元 1004， 用于向所述 M2M业务管理实体发送所述不支持特征 确定单元 1003所确定的不可使用特征；
例如： 相应的不支持特征发送单元 1004可以设置于 MME/SGSN 中， 也可以设置于 HSS/HLR中， 或者两者中分别设有不同的不支持特征确定单元 1003;
设置于 MME/SGSN中的不支持特征发送单元 1004可以向所述 M2M业务管理实体发 送设置于 MME/SGSN中的不支持特征确定单元 1003所确定的不可使用特征；
设置于 HSS/HLR中的不支持特征发送单元 1004可以向所述 M2M业务管理实体发送 设置于 HSS/HLR中的不支持特征确定单元 1003所确定的不可使用特征； 具体地， 相应的不支持特征发送单元 1004可以与所述支持特征发送单元 1002同时执 行，即将支持特征获取单元 1001所获取的终端支持的特征和移动性管理单元能力支持的特 征中的至少一项， 以及所述不支持特征确定单元 1003所确定的不可使用特征同时发送给所 述 M2M业务管理实体。
可选地， 如图 20所示， 本发明实施例提供的 M2M业务优化装置具体还可以包括：
( 1 ) 第一特征接收处理单元 1005， 设置于 MME/SGSN中， 用于接收可激活特征和 / 或可去激活特征， 并将所述的可激活特征和 /或可去激活特征通知给 HSS或者 HLR; 所述 HSS或者 HLR再对所述可激活特征进行激活处理和 /或对所述可去激活特征进行去激活处 理；
其中， 所述的可激活特征是指在 M2M业务的用户签约的特征中， 除去已经激活或正在 激活的特征后， 终端和移动性管理单元能力均支持的特征；
其中， 所述的可去激活特征是指在 M2M业务的已经激活的特征中， 终端不支持的特征 和 /或移动性管理单元能力不支持的特征；
具体地， 如图 24所示， 相应的第一特征接收处理单元 1005可以包括：
第一特征接收判定处理单元 10051， 设置于 MME/SGSN 中， 用于接收可激活特征， 并根据 UE支持的特征和 MME/SGSN能力支持的特征中的至少一项确定接收到的可激活特 征是否能够被激活， 以获取可激活特征中能够被激活的特征和 /或不能够被激活的特征， 并 将所述不能够被激活的特征作为可去激活特征； 然后， MME/SGSN 将可激活特征和 /或可 去激活特征通知给 HSS或者 HLR; HSS或者 HLR再对可激活特征进行激活处理， 对可去 激活特征进行去激活处理；
或者，
(2)第二特征接收处理单元 1006， 设置于 HSS/HLR中， 用于直接接收可激活特征和
/或可去激活特征， 并对所述可激活特征进行激活处理和 /或对所述可去激活特征进行去激活 处理；
其中， 所述的可激活特征是指在 M2M业务的用户签约的特征中， 除去已经激活或正在 激活的特征后， 终端和移动性管理单元能力均支持的特征；
其中， 所述的可去激活特征是指在 M2M业务的已经激活的特征中， 终端不支持的特征 和 /或移动性管理单元能力不支持的特征；
具体地， 如图 24所示， 相应的第二特征接收处理单元 1006可以包括：
第二特征接收判定处理单元 10061， 设置于 HSS/HLR中， 用于接收可激活特征， 并根 据 HSS/HLR中所保存的 UE支持的特征和 MME/SGSN能力支持的特征中的至少一项确定 接收到的可激活特征是否能够被激活， 以获取可激活特征中能够被激活的特征和 /或不能够 被激活的特征， 并将所述不能够被激活的特征作为可去激活特征； 然后， HSS/HLR对可激 活特征进行激活处理， 对可去激活特征进行去激活处理。
(二） M2M业务管理实体 如图 17所示， 本发明实施例提供的 M2M业务优化装置， 相应的设置于 M2M业务管 理实体中的装置的具体结构可以包括：
( 1 ) 支持特征接收单元 2001， 用于接收终端支持的特征和移动性管理单元能力支持 的特征中的至少一项；
具体地， 如图 18所示， 本发明实施例提供的 M2M业务优化装置具体还可以包括： 第一支持特征接收单元 20011， 设置于 MTC Server/Web/OMC等中， 用于接收终端支 持的特征和移动性管理单元能力支持的特征中的至少一项；
(2)可激活特征确定单元 2002， 用于根据所述支持特征接收单元 2001所获取的终端 支持的特征和移动性管理单元能力支持的特征中的至少一项， 以及用户签约的特征和 /或运 营商的经营策略确定可激活特征， 并对所述可激活特征进行激活处理；
其中， 相应的可激活特征是指在 M2M业务的用户签约的特征中， 除去已经激活或正在 激活的特征后， 终端和移动性管理单元能力均支持的特征；
具体地，相应的可激活特征确定单元 2002也可以设置于 MTC Server/Web/OMC等中， 并根据第一支持特征接收单元 20011 所获取的终端支持的特征和移动性管理单元能力支持 的特征中的至少一项， 以及用户签约的特征和 /或运营商的经营策略确定可激活特征， 并对 所述可激活特征进行激活处理。 可选地， 如图 19所示， 本发明实施例提供的 M2M业务优化装置具体可以包括： 可去激活特征确定单元 2003， 用于根据所述支持特征接收单元 2001所获取终端支持 的特征和移动性管理单元能力支持的特征中的至少一项， 以及用户签约的特征和 /或运营商 的经营策略确定可去激活特征， 并对所述可去激活特征进行去激活处理；
其中， 相应的可去激活特征是指在 M2M业务的已经激活的特征中， 终端不支持的特征 和 /或移动性管理单元能力不支持的特征；
具体地，相应的可去激活特征确定单元 2003可以设置于 MTC Server/Web/OMC等中， 并可以与可激活特征确定单元 2002同时执行， 以便于同时确定出可去激活特征和可激活特 征。
可选地， 仍如图 19所示， 本发明实施例提供的 M2M业务优化装置具体可以包括： 不支持特征接收单元 2004， 用于接收不可使用特征， 并发送给可激活特征确定单元 2002进行可激活特征确定处理和 /或发送给可去激活特征确定单元 2003进行可去激活特征 确定处理；
其中， 相应的不可使用特征是指在已经激活或正在激活的特征中， 终端不支持的特征 和 /或移动性管理单元能力不支持的特征；
具体地， 相应的不支持特征接收单元 2004可以设置于 MTC Server/Web/OMC等中， 并与支持特征接收单元 2001 同时执行， 已分别接收 M2M业务通信实体所发送到的不支持 特征和支持特征。
可选地， 仍如图 20所示， 本发明实施例提供的 M2M业务优化装置具体还可以包括： 特征发送单元 2005， 设置于 MTC Server/Web/OMC等中， 用于发送所述可激活特征 确定单元 2002所确定的可激活特征和 /或所述可去激活特征确定单元 2003所确定的可去激 活特征；
例如， 相应的特征发送单元 2005可以设置于 MTC Server/Web/OMC等中， 用于向
M2M业务通信实体发送所述可激活特征确定单元 2002所确定的可激活特征和 /或所述可去 激活特征确定单元 2003所确定的可去激活特征。 除了上述技术方案外，本发明实施例提供的 M2M业务优化装置还包括另一种与之类似 的方案， 以便于使 M2M业务管理实体获知 UE和 /或 MME/SGSN所支持优化方案。下面将 分别说明另一种方案的相应 M2M业务通信实体和 M2M业务管理实体中所设装置的具体结 构。
(一） M2M业务通信实体
如图 21所示， 本发明实施例提供的 M2M业务优化装置， 相应的设置于 M2M业务通 信实体中的装置的具体结构可以包括：
( 1 ) 特征确定处理单元 3001， 用于根据终端支持的特征和移动性管理单元能力支持 的特征中的至少一项， 以及用户签约的特征和 /或运营商的经营策略确定可激活特征和 /或可 去激活特征，并对所述可激活特征进行激活处理和 /或对所述可去激活特征进行去激活处理; 其中， 相应的可激活特征是指在 M2M业务的用户签约的特征中， 除去已经激活或正在 激活的特征后， 终端和移动性管理单元能力均支持的特征；
其中， 相应的可去激活特征是指在 M2M业务的已经激活的特征中， 终端不支持的特征 和 /或移动性管理单元能力不支持的特征；
具体地， 如图 23所示， 本发明实施例提供的 M2M业务优化装置具体还可以包括： 第一特征确定单元 30011，设置于 MME/SGSN中，用于根据终端支持的特征和移动性 管理单元能力支持的特征中的至少一项， 以及用户签约的特征和 /或运营商的经营策略确定 可激活特征和 /或可去激活特征；
或者，
第二特征确定单元 30012， 设置于 HSS/HLR中，用于根据终端支持的特征和移动性管 理单元能力支持的特征中的至少一项， 以及用户签约的特征和 /或运营商的经营策略确定可 激活特征和 /或可去激活特征。
(2)优化特征发送单元 3002， 用于向 M2M业务处理实体发送所述特征确定处理单元
3001所确定的可激活特征和 /或可去激活特征；
例如， 相应的优化特征发送单元 3002 可以设置于 MME/SGSN 中， 也可以设置于 HSS/HLR中， 或者两者中分别设有不同的优化特征发送单元 3002;
设置于 MME/SGSN中的优化特征发送单元 3002可以向 M2M业务处理实体发送所述 第一特征确定单元 30011所确定的可激活特征和 /或可去激活特征；
设置于 HSS/HLR中的优化特征发送单元 3002可以向 M2M业务处理实体发送所述第 二特征确定单元 30012所确定的可激活特征和 /或可去激活特征。
(二） M2M业务管理实体
如图 22所示， 本发明实施例提供的 M2M业务优化装置， 相应的设置于 M2M业务管 理实体中的装置的具体结构可以包括：
( 1 ) 优化特征接收单元 4001， 用于接收可激活特征和 /或可去激活特征；
其中， 相应的可激活特征是指在 M2M业务的用户签约的特征中， 除去已经激活或正在 激活的特征后， 终端和移动性管理单元能力均支持的特征；
其中， 相应的可去激活特征是指在 M2M业务的已经激活的特征中， 终端不支持的特征 和 /或移动性管理单元能力不支持的特征；
具体地， 如图 23所示， 相应的优化特征接收单元 4001具体可以包括：
第一优化特征接收单元 40011， 设置于 MTC Server/Web/OMC等中， 用于接收可激活 特征和 /或可去激活特征；
例如， 相应的第一优化特征接收单元 40011的用途可以包括以下至少一项： 当 M2M业务通信实体发送可激活特征时， 设置于 MTC Server/Web/OMC等中的第一 优化特征接收单元 40011可以接收可激活特征；
当 M2M业务通信实体发送可去激活特征时， 设置于 MTC Server/Web/OMC等中的第 一优化特征接收单元 40011可以接收可去激活特征；
(2)优化特征处理单元 4002， 用于对所述优化特征接收单元 4001所接收的可激活特 征进行激活处理和 /或对所述可去激活特征进行去激活处理； 例如， 相应的优化特征处理单元 4002的用途可以包括以下至少一项：
当所述所述优化特征接收单元 4001 接收到可激活特征时， 相应的优化特征处理单元 4002对可激活特征进行激活处理；
当所述所述优化特征接收单元 4001接收到可去激活特征时，相应的优化特征处理单元 4002对可去激活特征进行去激活处理；
可见， 该装置实施例的实现使 M2M业务管理实体能够及时获知 UE和 /或 MME/SGSN 所支持的优化方案， 并且在用户签约的 Feature不可使用时， 能够根据 MME/SGSN能力支 持的 Feature和 /或 UE支持的 Feature确定出可激活特征和可去激活特征，从而使 M2M业 务得到优化。
本领域普通技术人员可以理解： 实现上述实施例方法中的全部或部分流程是可以通过 程序来指令相关的硬件来完成， 所述的程序可存储于一计算机可读取存储介质中， 该程序 在执行时， 可包括如上述各方法的实施例的流程。 其中， 所述的存储介质可为磁碟、 光盘、 只读存储记忆体 （Read-Only Memory , ROM ) 或随机存储记忆体 （Random Access Memory, RAM) 等。
以上所述， 仅为本发明较佳的具体实施方式， 但本发明的保护范围并不局限于此， 任 何熟悉本技术领域的技术人员在本发明揭露的技术范围内， 可轻易想到的变化或替换， 都 应涵盖在本发明的保护范围之内。 因此， 本发明的保护范围应该以权利要求书的保护范围 为准。

Claims

权 利 要 求 书
1、 一种 M2M业务的优化方法， 其特征在于， 包括：
获取终端支持的特征和移动性管理单元能力支持的特征中的至少一项；
向 M2M 业务管理实体发送所述终端支持的特征和移动性管理单元能力支持的特征中 的至少一项。
2、 根据权利要求 1所述的方法， 其特征在于， 该方法还包括：
根据终端支持的特征、 移动性管理单元能力支持的特征和用户签约的特征确定不可使 用特征； 所述的不可使用特征是指在已经激活或正在激活的特征中， 终端不支持的特征和 / 或移动性管理单元能力不支持的特征；
向所述 M2M业务管理实体发送所述不可使用特征。
3、 根据权利要求 1所述的方法， 其特征在于， 所述的获取终端支持的特征和移动性管 理单元能力支持的特征中的至少一项包括：
移动管理实体 MME或者服务通用分组无线服务技术支持节点 SGSN获取终端支持的 特征和移动性管理单元能力支持的特征中的至少一项；
或者，
归属用户服务器 HSS或者归属位置寄存器 HLR获取终端支持的特征和移动性管理单 元能力支持的特征中的至少一项。
4、 根据权利要求 3所述的方法， 其特征在于， 该方法还包括：
MME或者 SGSN接收可激活特征和 /或可去激活特征， 并将所述的可激活特征和 /或可 去激活特征通知给 HSS或者 HLR;所述 HSS或者 HLR再对所述可激活特征进行激活处理 和 /或对所述可去激活特征进行去激活处理；
或者，
HSS或者 HLR直接接收可激活特征和 /或可去激活特征， 并对所述可激活特征进行激 活处理和 /或对所述可去激活特征进行去激活处理；
其中， 所述的可激活特征是指在 M2M业务的用户签约的特征中， 除去已经激活或正在 激活的特征后， 终端和移动性管理单元能力均支持的特征；
其中， 所述的可去激活特征是指在 M2M业务的已经激活的特征中， 终端不支持的特征 和 /或移动性管理单元能力不支持的特征。
5、 根据权利要求 4所述的方法， 其特征在于， 该方法还包括： MME或者 SGSN接收可激活特征，并根据终端支持的特征和移动性管理单元能力支持 的特征中的至少一项确定接收到的可激活特征是否能够被激活， 以获取可激活特征中能够 被激活的特征和 /或不能够被激活的特征，并将所述不能够被激活的特征作为可去激活特征； 或者，
HSS或者 HLR接收可激活特征，并根据终端支持的特征中所保存的终端支持的特征和 移动性管理单元能力支持的特征中的至少一项确定接收到的可激活特征是否能够被激活， 以获取可激活特征中能够被激活的特征和 /或不能够被激活的特征， 并将所述不能够被激活 的特征作为可去激活特征。
6、 一种 M2M业务的优化方法， 其特征在于， 包括：
接收终端支持的特征和移动性管理单元能力支持的特征中的至少一项；
根据所述终端支持的特征和移动性管理单元能力支持的特征中的至少一项， 以及用户 签约的特征和 /或运营商的经营策略确定可激活特征， 并对所述可激活特征进行激活处理； 所述的可激活特征是指在 M2M业务的用户签约的特征中，除去已经激活或正在激活的特征 后， 终端和移动性管理单元能力均支持的特征。
7、 根据权利要求 6所述的方法， 其特征在于， 该方法还包括：
根据所述终端支持的特征和移动性管理单元能力支持的特征中的至少一项， 以及用户 签约的特征和 /或运营商的经营策略确定可去激活特征， 并对所述可去激活特征进行去激活 处理； 所述的可去激活特征是指在 M2M 业务的已经激活的特征中， 终端不支持的特征和 / 或移动性管理单元能力不支持的特征。
8、 根据权利要求 6或 7所述的方法， 其特征在于， 该方法还包括：
接收不可使用特征， 并根据所述不可使用特征确定可激活特征和 /或可去激活特征； 所 述的不可使用特征是指在已经激活或正在激活的特征中， 终端不支持的特征和 /或移动性管 理单元能力不支持的特征。
9、 根据权利要求 6所述的方法， 其特征在于， 所述的接收终端支持的特征和移动性管 理单元能力支持的特征中的至少一项包括：
机器通信业务服务器 MTC Server或者互联网 Web或者操作维护中心 OMC接收终端 支持的特征和移动性管理单元能力支持的特征中的至少一项。
10、 根据权利要求 9所述的方法， 其特征在于， 该方法还包括：
MTC Server或者 Web或者 OMC发送所述可激活特征和 /或所述可去激活特征。
11、 一种 M2M业务的优化方法， 其特征在于， 包括：
根据终端支持的特征和移动性管理单元能力支持的特征中的至少一项， 以及用户签约 的特征和 /或运营商的经营策略确定可激活特征和 /或可去激活特征， 并对所述可激活特征进 行激活处理和 /或对所述可去激活特征进行去激活处理； 所述的可激活特征是指在 M2M 业 务的用户签约的特征中， 除去已经激活或正在激活的特征后， 终端和移动性管理单元能力 均支持的特征； 所述的可去激活特征是指在 M2M业务的已经激活的特征中， 终端不支持的 特征和 /或移动性管理单元能力不支持的特征；
向 M2M业务处理实体发送可激活特征和 /或可去激活特征。
12、 根据权利要求 11所述的方法， 其特征在于， 所述的根据终端支持的特征和移动性 管理单元能力支持的特征中的至少一项， 以及用户签约的特征和 /或运营商的经营策略确定 可激活特征和 /或可去激活特征包括：
MME或者 SGSN根据终端支持的特征和移动性管理单元能力支持的特征中的至少一 项， 以及用户签约的特征和 /或运营商的经营策略确定可激活特征和 /或可去激活特征； 或者，
HSS或者 HLR根据终端支持的特征和移动性管理单元能力支持的特征中的至少一项， 以及用户签约的特征和 /或运营商的经营策略确定可激活特征和 /或可去激活特征。
13、 一种 M2M业务的优化方法， 其特征在于， 包括：
接收可激活特征和 /或可去激活特征； 所述的可激活特征是指在 M2M 业务的用户签约 的特征中， 除去已经激活或正在激活的特征后， 终端和移动性管理单元能力均支持的特征; 所述的可去激活特征是指在 M2M 业务的已经激活的特征中， 终端不支持的特征和 /或移动 性管理单元能力不支持的特征；
对所述可激活特征进行激活处理和 /或对所述可去激活特征进行去激活处理。
14、 根据权利要求 13 所述的方法， 其特征在于， 所述的接收可激活特征和 /或可去激 活特征包括： MTC Server或者 Web或者 OMC接收可激活特征和 /或可去激活特征。
15、 一种 M2M业务的优化装置， 其特征在于， 包括：
支持特征获取单元， 用于获取终端支持的特征和移动性管理单元能力支持的特征中的 至少一项；
支持特征发送单元，用于向 M2M业务管理实体发送所述支持特征获取单元所获取的终 端支持的特征和移动性管理单元能力支持的特征中的至少一项。
16、 根据权利要求 15所述的装置， 其特征在于， 该装置还包括：
不支持特征确定单元， 用于根据所述支持特征获取单元所获取的终端支持的特征和移 动性管理单元能力支持的特征， 以及用户签约的特征确定不可使用特征； 所述的不可使用 特征是指在已经激活或正在激活的特征中， 终端不支持的特征和 /或移动性管理单元能力不 支持的特征；
不支持特征发送单元，用于向所述 M2M业务管理实体发送所述不支持特征确定单元所 确定的不可使用特征。
17、 根据权利要求 15所述的装置， 其特征在于， 所述的支持特征获取单元包括： 第一支持特征获取单元， 设置于 MME或者 SGSN中， 用于获取终端支持的特征和移 动性管理单元能力支持的特征中的至少一项；
或者，
第二支持特征获取单元， 设置于 HSS或者 HLR中， 用于获取终端支持的特征和移动 性管理单元能力支持的特征中的至少一项。
18、 根据权利要求 17所述的装置， 其特征在于， 该装置还包括：
第一特征接收处理单元， 设置于 MME或者 SGSN中， 用于接收可激活特征和 /或可去 激活特征， 并将所述的可激活特征和 /或可去激活特征通知给 HSS或者 HLR; 所述 HSS或 者 HLR再对所述可激活特征进行激活处理和 /或对所述可去激活特征进行去激活处理； 或者，
第二特征接收处理单元， 设置于 HSS或者 HLR中， 用于直接接收可激活特征和 /或可 去激活特征，并对所述可激活特征进行激活处理和 /或对所述可去激活特征进行去激活处理； 其中， 所述的可激活特征是指在 M2M业务的用户签约的特征中， 除去已经激活或正在 激活的特征后， 终端和移动性管理单元能力均支持的特征；
其中， 所述的可去激活特征是指在 M2M业务的已经激活的特征中， 终端不支持的特征 和 /或移动性管理单元能力不支持的特征。
19、 根据权利要求 18所述的装置， 其特征在于，
第一特征接收判定处理单元， 设置于 MME或者 SGSN中， 用于接收可激活特征和， 并根据终端支持的特征和移动性管理单元能力支持的特征中的至少一项确定接收到的可激 活特征是否能够被激活，以获取可激活特征中能够被激活的特征和 /或不能够被激活的特征， 并将所述不能够被激活的特征作为可去激活特征；
或者，
第二特征接收判定处理单元， 设置于 HSS或者 HLR中， 用于接收可激活特征， 并根 据 HSS或者 HLR中所保存的终端支持的特征和移动性管理单元能力支持的特征中的至少 一项确定接收到的可激活特征是否能够被激活， 以获取可激活特征中能够被激活的特征和 / 或不能够被激活的特征， 并将所述不能够被激活的特征作为可去激活特征。
20、 一种 M2M业务的优化装置， 其特征在于， 包括： 支持特征接收单元， 用于接收终端支持的特征和移动性管理单元能力支持的特征中的 至少一项；
可激活特征确定单元， 用于根据所述支持特征接收单元所获取的终端支持的特征和移 动性管理单元能力支持的特征中的至少一项， 以及用户签约的特征和 /或运营商的经营策略 确定可激活特征， 并对所述可激活特征进行激活处理； 所述的可激活特征是指在 M2M业务 的用户签约的特征中， 除去已经激活或正在激活的特征后， 终端和移动性管理单元能力均 支持的特征。
21、 根据权利要求 20所述的装置， 其特征在于， 该装置还包括：
可去激活特征确定单元， 用于根据所述支持特征接收单元所获取终端支持的特征和移 动性管理单元能力支持的特征中的至少一项， 以及用户签约的特征和 /或运营商的经营策略 确定可去激活特征， 并对所述可去激活特征进行去激活处理； 所述的可去激活特征是指在
M2M 业务的已经激活的特征中， 终端不支持的特征和 /或移动性管理单元能力不支持的特 征。
22、 根据权利要求 20或 21所述的装置， 其特征在于， 该装置还包括：
不支持特征接收单元， 用于接收不可使用特征， 并发送给可激活特征确定单元进行可 激活特征确定处理和 /或发送给可去激活特征确定单元进行可去激活特征确定处理； 所述的 不可使用特征是指在已经激活或正在激活的特征中， 终端不支持的特征和 /或移动性管理单 元能力不支持的特征。
23、 根据权利要求 20所述的方法， 其特征在于， 所述的支持特征接收单元包括： 第一支持特征接收单元， 设置于 MTC Server或者 Web或者 OMC中， 用于接收终端 支持的特征和移动性管理单元能力支持的特征中的至少一项。
24、 根据权利要求 23所述的装置， 其特征在于， 该装置还包括：
特征发送单元， 设置于 MTC Server或者 Web或者 OMC中， 用于发送所述可激活特 征确定单元所确定的可激活特征和 /或所述可去激活特征确定单元所确定的可去激活特征。
25、 一种 M2M业务的优化装置， 其特征在于， 包括：
特征确定处理单元， 用于根据终端支持的特征和移动性管理单元能力支持的特征中的 至少一项， 以及用户签约的特征和 /或运营商的经营策略确定可激活特征和 /或可去激活特 征， 并对所述可激活特征进行激活处理和 /或对所述可去激活特征进行去激活处理； 所述的 可激活特征是指在 M2M业务的用户签约的特征中， 除去已经激活或正在激活的特征后， 终 端和移动性管理单元能力均支持的特征；所述的可去激活特征是指在 M2M业务的已经激活 的特征中， 终端不支持的特征和 /或移动性管理单元能力不支持的特征； 优化特征发送单元，用于向 M2M业务处理实体发送所述特征确定处理单元所确定的可 激活特征和 /或可去激活特征。
26、 根据权利要求 25所述的装置， 其特征在于， 所述的特征确定处理单元包括： 第一特征确定单元， 设置于 MME或者 SGSN中， 用于根据终端支持的特征和移动性 管理单元能力支持的特征中的至少一项， 以及用户签约的特征和 /或运营商的经营策略确定 可激活特征和 /或可去激活特征；
或者，
第二特征确定单元， 设置于 HSS或者 HLR中， 用于根据终端支持的特征和移动性管 理单元能力支持的特征中的至少一项， 以及用户签约的特征和 /或运营商的经营策略确定可 激活特征和 /或可去激活特征。
27、 一种 M2M业务的优化装置， 其特征在于， 包括：
优化特征接收单元， 用于接收可激活特征和 /或可去激活特征； 所述的可激活特征是指 在 M2M业务的用户签约的特征中， 除去已经激活或正在激活的特征后， 终端和移动性管理 单元能力均支持的特征； 所述的可去激活特征是指在 M2M业务的已经激活的特征中， 终端 不支持的特征和 /或移动性管理单元能力不支持的特征；
优化特征处理单元， 用于对所述优化特征接收单元所接收的可激活特征进行激活处理 和 /或对所述可去激活特征进行去激活处理。
28、 根据权利要求 27所述的装置， 其特征在于， 所述的优化特征接收单元包括： 第一优化特征接收单元， 设置于 MTC Server或者 Web或者 OMC中， 用于接收可激 活特征和 /或可去激活特征。
PCT/CN2011/073735 2010-08-26 2011-05-06 一种m2m业务的优化方法及装置 Ceased WO2012024941A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010264528.1A CN102378226B (zh) 2010-08-26 2010-08-26 一种m2m业务的优化方法及装置
CN201010264528.1 2010-08-26

Publications (1)

Publication Number Publication Date
WO2012024941A1 true WO2012024941A1 (zh) 2012-03-01

Family

ID=45722855

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/073735 Ceased WO2012024941A1 (zh) 2010-08-26 2011-05-06 一种m2m业务的优化方法及装置

Country Status (2)

Country Link
CN (1) CN102378226B (zh)
WO (1) WO2012024941A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103716822A (zh) * 2012-10-09 2014-04-09 中兴通讯股份有限公司 监控方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1351452A (zh) * 2000-10-30 2002-05-29 Lg电子株式会社 用于在移动通信系统中报告特性服务的激活状态的方法
CN1976523A (zh) * 2006-12-14 2007-06-06 华为技术有限公司 呼叫禁止的方法
CN101682832A (zh) * 2007-02-21 2010-03-24 株式会社克尔盖特 利用短消息服务提供3g业务的方法和系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1351452A (zh) * 2000-10-30 2002-05-29 Lg电子株式会社 用于在移动通信系统中报告特性服务的激活状态的方法
CN1976523A (zh) * 2006-12-14 2007-06-06 华为技术有限公司 呼叫禁止的方法
CN101682832A (zh) * 2007-02-21 2010-03-24 株式会社克尔盖特 利用短消息服务提供3g业务的方法和系统

Also Published As

Publication number Publication date
CN102378226A (zh) 2012-03-14
CN102378226B (zh) 2014-07-30

Similar Documents

Publication Publication Date Title
CN114009073B (zh) 用于在无线通信系统中提供服务的方法和装置
CN110249667B (zh) 非3gpp接入上的终端接入5g网络的注册管理方法
US9241254B2 (en) Method and system for determining reachability of terminal group
US20120096154A1 (en) Information Processing Method and System, and Mobility Management Network Element
WO2011054299A1 (zh) 机器类通讯终端信息的获取方法和系统
WO2011082538A1 (zh) 机器型通信中基于组的移动性优化方法和设备
WO2014110927A1 (zh) 触发消息发送的方法、设备及系统
WO2012097757A2 (zh) 一种单卡双待用户设备驻留网络的方法及用户设备
WO2011050689A1 (zh) 机器类通讯终端的接入控制方法和系统
WO2014067466A1 (zh) 下行传输数据的方法和设备
WO2010108352A1 (zh) 接入网策略发送方法、归属接入网络发现和选择功能单元
CN114424634A (zh) 使用多个sim的服务提供方法和设备
KR101782650B1 (ko) 이동통신 시스템에서의 ｍｔｃ 서비스 네트워크 오버로드의 제어 방법 및 그 장치
WO2012113178A1 (zh) 检测终端连接丢失的方法及装置
JP7100123B6 (ja) サービスアクティブ化及び非アクティブ化の方法、装置、コンピュータ記憶媒体
WO2013163945A1 (zh) 一种机器类通信事件的上报方法及相应装置
WO2012122902A1 (zh) 位置信息处理方法及接入网设备
CN101765089B (zh) 一种移动用户漫游方法和装置、移动终端及用户卡
WO2013143218A1 (zh) 触发消息计数器的更新方法、机器类型通信服务器和终端
CN103228025A (zh) 机器类通信终端的接入方法、装置及系统
EP2696619B1 (en) System and method for processing trigger messages of a terminal
WO2012024941A1 (zh) 一种m2m业务的优化方法及装置
CN103188728B (zh) 一种网络拥塞控制方法及系统
CN102868995B (zh) 终端接入方法及系统
CN103108305A (zh) 一种终端触发消息有效时间控制方法及系统

Legal Events

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

Ref document number: 11819316

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11819316

Country of ref document: EP

Kind code of ref document: A1