CN102378226A

CN102378226A - Optimization method and device for M2M (Machine-to-Machine) service

Info

Publication number: CN102378226A
Application number: CN2010102645281A
Authority: CN
Inventors: 闫学霞; 时书锋; 陈中平
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2010-08-26
Filing date: 2010-08-26
Publication date: 2012-03-14
Anticipated expiration: 2030-08-26
Also published as: CN102378226B; WO2012024941A1

Abstract

The invention relates to an optimization method and device for an M2M (Machine-to-Machine) service. The method comprises the following steps of: obtaining at least one of the feature supported by a terminal and the feature supported by the capacity of a mobility management unit; and sending at least one of the feature supported by the terminal and the feature supported by the capacity of the mobility management unit to an M2M service management entity. The method and the device have the advantages that: by the application of the embodiment of the invention, the M2M management entity can learn the optimization scheme supported by the UE (User Equipment) and/or the MME (Mobility Management Entity)/the SGSN (Service GPRS (General Packet Radio Service) Supporting Node) in time, thus the M2M service can be optimized.

Description

Method and device for optimizing M2M service

Technical Field

The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for optimizing an M2M service.

Background

With the development of technology, the types of communication services are more and more, and M2M (Machine to Machine communication) service is one of the most representative communication services. In existing networks, M2M traffic is mostly carried over CS/PS domain (i.e., circuit-carrying domain/data domain) networks. For the network, the users of the M2M service are the same as the users of the ordinary network service, and there is no explicit distinction. With the development of network services, the number of users of the M2M service is increasing, and when the number of users reaches a certain degree, a huge impact is brought to the network.

In order to reduce the impact on the network, 3GPP (3rd Generation Partnership Project) classifies M2M traffic according to the characteristics of M2M terminals, and defines different features for each type of M2M traffic; these features and their activation status identifiers are stored in an HSS (Home subscriber server)/HLR (Home Location Register).

The user of the M2M service can contract different features, and different optimization can be carried out aiming at the different Feature networks; specifically, the network may determine which features should be adopted according to features supported by the mobility management unit capability, features supported by the terminal, and features subscribed by the user, and execute a network optimization policy and an M2M service; an industry user or an operator can also activate and deactivate the M2M service or different features through interfaces such as WEB (internet), OMC (Operations & Maintenance Center), and the like.

Currently, as shown in fig. 1, an existing method for optimizing M2M service roughly includes the following steps:

step 1, a UE (User Equipment, terminal) sends an NAS (network access service message between a network and a terminal for interaction between the terminal and the network) message to an MME (Mobility Management Entity)/SGSN (serving GPRS Support Node), where the message may carry information such as Feature supported by the UE, IMSI (International Mobile Subscriber Identity) of the UE, and the like;

step 2, after receiving the NAS message, the MME/SGSN routes to HSS/HLR to which the UE belongs according to the information of the UE such as IMSI and the like;

step 3, MME/SGSN sends ULR (location update request) message to HSS/HLR, where the message may carry MME/SGSN capability (mobility management unit capability);

step 4, after receiving the ULR, the HSS/HLR determines the activated Feature supported by the MME/SGSN capability in the user signed Feature according to the MME/SGSN capability, and takes the Feature as the user signed Feature which can be issued;

step 5, HSS/HLR sends the Feature which can be sent down to the corresponding MME/SGSN;

step 6, the MME/SGSN detects whether the Feature issued by the HSS/HLR is matched with the Feature supported by the MME/SGSN capability;

step 7, the MME/SGSN informs the HSS/HLR of the Feature which is not supported by the MME/SGSN operation capability but activated by the user through a NOR (notify request) message;

step 8, HSS/HLR returns a response message to MME/SGSN;

step 9, the HSS/HLR notifies the Feature activated by the user, which is not supported by the MME/SGSN capability, to an MTC Server (Machine Type Communications Server)/Web (internet)/OMC (Operations & Maintenance Center), and the like;

and step 10, the MTC Server/Web/OMC and the like deactivate the Feature which is not supported by the MME/SGSN capability but activated by the user, and simultaneously the MME/SGSN informs the UE of successful connection.

The inventor finds that the above treatment process provided by the prior art has at least the following problems:

the M2M service management entity cannot know the optimization schemes supported by the UE and/or MME/SGSN, which may cause M2M services to be un-optimized and even cause M2M services to be inefficiently executed.

Disclosure of Invention

The embodiment of the invention provides an optimization method and device of an M2M service, so that an M2M service management entity can timely acquire an optimization scheme supported by UE and/or MME/SGSN, and the M2M service is optimized.

A method of optimizing M2M (machine-to-machine communication) traffic, comprising:

acquiring at least one of a feature supported by a terminal and a feature supported by the capability of a mobility management unit;

sending at least one of the terminal supported features and the mobility management unit capability supported features to an M2M traffic management entity.

A method for optimizing M2M service includes:

receiving at least one of a feature supported by the terminal and a feature supported by the mobility management unit capability;

determining an activatable feature according to at least one of the features supported by the terminal and the features supported by the mobile management unit capability, the features signed by the user and/or the operation strategy of the operator, and activating the activatable feature; the activatable feature refers to a feature supported by both the terminal and the mobility management unit after removing the activated or activating feature from the features subscribed by the M2M service.

A method for optimizing M2M service includes:

determining an activatable feature and/or a deactivatable feature according to at least one of a feature supported by a terminal and a feature supported by the capability of a mobility management unit, and a feature signed by a user and/or an operating policy of an operator, and activating the activatable feature and/or deactivating the deactivatable feature; the activatable feature refers to a feature supported by both the terminal and the mobility management unit after the activated or currently activated feature is removed from the features subscribed by the M2M service; the deactivatable features refer to features not supported by the terminal and/or features not supported by the mobility management unit capability among the already activated features of the M2M service;

the activatable feature and/or the deactivatable feature is sent to an M2M traffic processing entity.

A method for optimizing M2M service includes:

receiving an activatable feature and/or a deactivatable feature; the activatable feature refers to a feature supported by both the terminal and the mobility management unit after the activated or currently activated feature is removed from the features subscribed by the M2M service; the deactivatable features refer to features not supported by the terminal and/or features not supported by the mobility management unit capability among the already activated features of the M2M service;

activating the activatable feature and/or deactivating the deactivatable feature.

An apparatus for optimizing M2M service, comprising:

a supported feature obtaining unit, configured to obtain at least one of a feature supported by the terminal and a feature supported by the capability of the mobility management unit;

a supported feature sending unit, configured to send, to the M2M service management entity, at least one of the feature supported by the terminal and the feature supported by the mobility management unit, which are acquired by the supported feature acquiring unit.

An apparatus for optimizing M2M service, comprising:

a supported 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 capability;

an activatable feature determining unit, configured to determine an activatable feature according to at least one of the features supported by the terminal and the features supported by the mobility management unit, which are acquired by the supported feature receiving unit, and a feature signed by a user and/or an operation policy of an operator, and activate the activatable feature; the activatable feature refers to a feature supported by both the terminal and the mobility management unit after removing the activated or activating feature from the features subscribed by the M2M service.

An apparatus for optimizing M2M service, comprising:

the mobile terminal comprises a feature determination processing unit, a feature activation processing unit and a feature deactivation processing unit, wherein the feature determination processing unit is used for determining an activatable feature and/or a deactivatable feature according to at least one of a feature supported by the terminal and a feature supported by the capability of the mobile management unit, and a user signed feature and/or an operation strategy of an operator, and activating the activatable feature and/or deactivating the deactivatable feature; the activatable feature refers to a feature supported by both the terminal and the mobility management unit after the activated or currently activated feature is removed from the features subscribed by the M2M service; the deactivatable features refer to features not supported by the terminal and/or features not supported by the mobility management unit capability among the already activated features of the M2M service;

and the optimized feature sending unit is used for sending the activatable features and/or the deactivatable features determined by the feature determination processing unit to the M2M service processing entity.

An apparatus for optimizing M2M service, comprising:

an optimized feature receiving unit for receiving an activatable feature and/or a deactivatable feature; the activatable feature refers to a feature supported by both the terminal and the mobility management unit after the activated or currently activated feature is removed from the features subscribed by the M2M service; the deactivatable features refer to features not supported by the terminal and/or features not supported by the mobility management unit capability among the already activated features of the M2M service;

an optimized feature processing unit, configured to perform activation processing on the activatable feature received by the optimized feature receiving unit and/or perform deactivation processing on the deactivatable feature.

It can be seen from the foregoing technical solutions that, in the method and apparatus for optimizing M2M services provided in the embodiments of the present invention, at least one of a Feature supported by a UE and a Feature supported by an MME/SGSN capability is sent to an M2M service management entity (an M2M service management entity refers to an entity that manages an M2M service, and a corresponding M2M service management entity may include, but is not limited to, an MTC Server/Web/OMC, etc.), so that the M2M service management entity can timely know an optimization scheme supported by the UE and/or the MME/SGSN, thereby optimizing the M2M service.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

Fig. 1 is a schematic processing flow diagram of a conventional M2M service optimization method according to an embodiment of the present invention;

fig. 2 is a first schematic processing flow diagram of a method for optimizing M2M service according to an embodiment of the present invention;

fig. 3 is a schematic processing flow diagram of a M2M service optimization method according to an embodiment of the present invention;

fig. 4 is a schematic processing flow diagram three of a method for optimizing M2M service according to an embodiment of the present invention;

fig. 5 is a fourth schematic processing flow diagram of a M2M service optimization method according to an embodiment of the present invention;

fig. 6 is a schematic processing flow diagram five of a method for optimizing M2M service according to an embodiment of the present invention;

fig. 7 is a sixth schematic processing flow diagram of a method for optimizing M2M service according to an embodiment of the present invention;

fig. 8 is a seventh processing flow diagram of the M2M service optimization method according to the embodiment of the present invention;

fig. 9 is an eighth schematic processing flow diagram of a method for optimizing M2M service according to an embodiment of the present invention;

fig. 10 is a processing flow diagram nine of an M2M service optimization method according to an embodiment of the present invention;

fig. 11 is a schematic processing flow diagram ten of a method for optimizing M2M service according to an embodiment of the present invention;

fig. 12 is an eleventh schematic processing flow diagram of a method for optimizing M2M service according to an embodiment of the present invention;

fig. 13 is a process flow diagram twelve illustrating an M2M service optimization method according to an embodiment of the present invention;

fig. 14 is a first schematic structural diagram of an M2M service optimization apparatus according to an embodiment of the present invention;

fig. 15 is a schematic structural diagram ii of an M2M service optimization apparatus according to an embodiment of the present invention;

fig. 16 is a schematic structural diagram three of an M2M service optimization apparatus according to an embodiment of the present invention;

fig. 17 is a fourth schematic structural diagram of an M2M service optimization apparatus according to an embodiment of the present invention;

fig. 18 is a schematic structural diagram five of an M2M service optimization apparatus according to an embodiment of the present invention;

fig. 19 is a schematic structural diagram six of an M2M service optimization apparatus according to an embodiment of the present invention;

fig. 20 is a seventh schematic structural diagram of an M2M service optimization apparatus according to an embodiment of the present invention;

fig. 21 is a schematic structural diagram eight of an M2M service optimization apparatus according to an embodiment of the present invention;

fig. 22 is a schematic structural diagram nine of an M2M service optimization apparatus according to an embodiment of the present invention;

fig. 23 is a schematic structural diagram ten of an M2M service optimization apparatus according to an embodiment of the present invention;

fig. 24 is an eleventh structural schematic diagram of an M2M service optimization apparatus according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Existing MME/SGSN or HSS/HLR do not send the Feature supported by UE and/or the Feature supported by MME/SGSN capability to the M2M service management entity, so that the M2M service management entity cannot know the optimization scheme supported by UE and/or MME/SGSN, and thus the M2M service cannot be optimized, and even the M2M service cannot be effectively executed.

Embodiments of the present invention will be described in further detail below with reference to the accompanying drawings.

The specific implementation process of the M2M service optimization method provided in the embodiment of the present invention relates to an M2M service communication entity (the corresponding M2M service communication entity may include an MME/SGSN or an HSS/HLR, but is not limited to these network elements), and an M2M service management entity (the corresponding M2M service management entity may include an MTC Server/Web/OMC, but is not limited to these network elements). It should be noted that the terminal described in the embodiment of the present invention may include communication electronic devices such as a mobile phone, a PDA (personal digital assistant), various smart phones, and the like, and may also include other electrical devices equipped with an M2M service terminal, such as a notebook computer, a desktop computer, a camera, a washing machine, an air conditioner, an electric cooker, and the like. The terminal in the embodiment of the present invention includes, but is not limited to, the above-mentioned devices, and the following description only exemplifies some examples, but this does not limit the present invention.

The following will respectively describe the specific processing procedures that the corresponding M2M service communication entity and M2M service management entity need to perform in the embodiment of the present invention.

M2M service communication entity

As shown in fig. 2, in a specific implementation process of the M2M service optimization method provided in the embodiment of the present invention, an operation performed by a corresponding M2M service communication entity may specifically include the following steps:

step 21, acquiring at least one of Feature supported by UE and Feature supported by MME/SGSN capability;

for example, the corresponding acquiring at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability may include:

(1) the MME/SGSN acquires at least one of Feature supported by the UE and Feature supported by the MME/SGSN capability;

specifically, for the MME/SGSN, features supported by the MME/SGSN capability (for example, features supported by the corresponding MME/SGSN capability may include features for SMS (Short Messaging Service), PS only (Packet Switch only) features, features for theft prevention, features for group management, features for time control, features for low mobility, features for monitoring, features for online data transmission, features for offline data transmission, and the like defined by M2M) are obvious and do not need to be acquired; as for the Feature supported by the UE, the MME/SGSN can acquire the Feature supported by the UE carried in the message only by receiving the NAS message sent by the UE (for example, the corresponding UE-supported Feature may include features defined by M2M, such as a SMS Feature, a PS only Feature, a security Feature, a group management Feature, a time control Feature, a low mobility Feature, and a monitoring Feature);

the first embodiment is as follows: assuming that an M2M service terminal M1 supports features for theft prevention and group management features, an MME/SGSN serving the M2M service terminal M1 supports features for theft prevention and time control features, and the features subscribed by the M2M service terminal M1 may include features for theft prevention and group management features; the MME/SGSN providing the service for the M2M service terminal M1 may receive the NAS message sent by the M2M service terminal M1, and acquire the Feature supported by the M2M service terminal M1 from the message (the Feature supported by the M2M service terminal M1 may include a Feature for theft prevention and a Feature for group management);

or,

(2) the HSS/HLR acquires at least one item of Feature supported by the UE and Feature supported by the MME/SGSN capability;

for example, the HSS/HLR may obtain at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability by receiving the ULR message sent by the MME/SGSN, and the Feature supported by the corresponding UE may be the same as the Feature supported by the corresponding MME/SGSN capability; specifically, the corresponding MME/SGSN may receive an NAS message sent by the UE, and obtain the Feature supported by the UE from the NAS message, and then send the Feature supported by the UE and the Feature supported by the self MME/SGSN capability carried in the ULR message to the HSS/HLR; HSS/HLR can receive the ULR message and obtain Feature supported by UE and Feature supported by MME/SGSN capability;

example two: assuming that a certain M2M service terminal M2 supports monitoring Feature and PS only Feature, an MME/SGSN serving the M2M service terminal M2 can support monitoring Feature and time control Feature, and the Feature subscribed by the M2M service terminal M1 may include monitoring Feature and PS only Feature; the MME/SGSN serving the M2M service terminal M2 may receive the NAS message sent by the M2M service terminal M2, and obtain the Feature supported by the M2M service terminal M2 from the NAS message, and then send the Feature supported by the M2M service terminal M2 and the Feature supported by the self MME/SGSN capability in the ULR message to the HSS/HLR to which the M2M service terminal M2 belongs; the HSS/HLR to which the M2M service terminal M2 belongs may receive the ULR message, and obtain the Feature supported by the M2M service terminal M2 from the ULR message (the Feature supported by the M2M service terminal M2 may include a monitoring Feature and a PS only Feature) and the 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);

step 22, sending at least one of Feature supported by the UE and Feature supported by MME/SGSN capability to an M2M service management entity;

wherein, the corresponding M2M service management entity may include MTC Server/Web/OMC, etc.;

specifically, for different M2M service communication entities in step 21, the step may specifically include:

(1) for the occasion that the MME/SGSN is an M2M service communication entity, the MME/SGSN sends at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability to an MTCServer/Web/OMC and the like;

further, for the occasion that the MME/SGSN is the M2M service communication entity, mainly means that the MME/SGSN acquires at least one of a Feature supported by the UE and a Feature supported by the MME/SGSN capability, the MME/SGSN sends the at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN to the mtserver/Web/OMC or the like;

the first corresponding embodiment: when the MME/SGSN providing services for the M2M service terminal M1 acquires the Feature supported by the M2M service terminal M1 and the Feature supported by the self MME/SGSN capability, the MME/SGSN may send the Feature supported by the M2M service terminal M1 (the Feature supported by the M2M service terminal M1 may include a Feature for theft prevention and a Feature for group management) and the Feature supported by the corresponding MME/SGSN capability (the Feature for theft prevention and the Feature for time control supported by the corresponding MME/SGSN capability) to the MTC Server/Web/OMC and the like currently providing services for the M2M service terminal M1

Or,

(2) for the occasion that the HSS/HLR is an M2M service communication entity, the HSS/HLR sends at least one item of Feature supported by the UE and Feature supported by the MME/SGSN capability to MTC Server/Web/OMC and the like;

further, for the occasion that the HSS/HLR is the M2M service communication entity, mainly means that the HSS/HLR acquires at least one of a Feature supported by the UE and a Feature supported by the MME/SGSN capability, the HSS/HLR sends the at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability to the mtserver/Web/OMC or the like;

corresponding example two: when the HSS/HLR to which the M2M service terminal M2 belongs acquires the Feature supported by the M2M service terminal M2 and the Feature supported by the self MME/SGSN capability, the HSS/HLR may send the Feature supported by the M2M service terminal M2 (the Feature supported by the M2M service terminal M2 may include a monitoring Feature and a PS only Feature) and at least one of the features supported by the corresponding MME/SGSN capability (the features supported by the corresponding MME/SGSN capability may include a monitoring Feature and a time control Feature) to the MTC Server/Web/OMC and the like that currently provides services for the M2M service terminal M2.

On the basis of the technical solution described in the above step 21, as shown in fig. 3, in a specific implementation process of the corresponding M2M service communication entity, the following operation steps may also be included:

step 31: acquiring at least one of Feature supported by UE and Feature supported by MME/SGSN capability;

specifically, the technical solution of this step is completely the same as the technical solution described in step 21, and is not described herein again;

step 32: determining that the Feature cannot be used according to the Feature supported by the UE, the Feature supported by the MME/SGSN capability and the Feature signed by the user;

wherein, the corresponding unavailable Feature refers to a Feature which is not supported by the UE and/or a Feature which is not supported by the MME/SGSN capability in the activated or activating features;

specifically, for different M2M service communication entities in step 31, the step may specifically include:

(1) after step 31, for the situation that the MME/SGSN is an M2M service communication entity, the MME/SGSN determines that the Feature cannot be used according to the Feature supported by the UE and the Feature supported by the MME/SGSN capability acquired in step 31, and the Feature signed by the user and stored by the MME/SGSN or issued by the HSS/HLR;

the first corresponding embodiment: after step 31 is performed, for the case that the MME/SGSN is the M2M service communication entity, the MME/SGSN providing services for the M2M service terminal M1 determines that the Feature is unavailable (the Feature subscribed by the M2M service terminal M1 may include the Feature for theft prevention and the Feature for time control) according to the Feature supported by the M2M service terminal M1 (the Feature supported by the M2M service terminal M1 may include the Feature for theft prevention and the Feature for group management) acquired in step 31 and the Feature supported by the corresponding MME/SGSN capability (the Feature supported by the corresponding MME/SGSN capability may include the Feature for theft prevention and the Feature for time control), and the Feature subscribed by the user and stored by the MME/SGSN or issued by the HSS/HLR (the Feature subscribed by the M2M service terminal M1 may include the Feature for theft prevention and the Feature for group management);

or,

(2) after step 31, for the situation that the HSS/HLR is the M2M service communication entity, the HSS/HLR determines that the Feature is unavailable according to the Feature supported by the UE and the Feature supported by the MME/SGSN capability obtained in step 31, and the activated Feature stored in the HSS/HLR;

corresponding example two: after step 31 is performed, for the case that the HSS/HLR is an M2M service communication entity, the HSS/HLR to which the M2M service terminal M2 belongs determines that the Feature is unavailable (the Feature subscribed by the M2M service terminal M1 may include a PS only Feature and a time control Feature) according to the Feature supported by the M2M service terminal M2 (the Feature supported by the M2M service terminal M2 may include a monitoring Feature and a PS only Feature) and the 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), which are acquired in step 31;

step 33: sending the unavailable Feature to an M2M service management entity;

specifically, the processing of this step is basically similar to step 22, and the unavailable Feature in this step and at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability in step 22 may be simultaneously sent to the MTC Server/Web/OMC, and the like, and the specific implementation thereof may include:

(1) for the occasion that MME/SGSN is an M2M service communication entity, MME/SGSN sends at least one of Feature supported by UE and Feature supported by MME/SGSN capability and the unavailable Feature to MTCServer/Web/OMC and the like;

the first corresponding embodiment: for the case that the MME/SGSN serves an M2M service communication entity, sending, by the MME/SGSN serving the M2M service terminal M1, a Feature supported by the M2M service terminal M1 (the Feature supported by the M2M service terminal M1 may include a Feature for theft prevention 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 a Feature for theft prevention and a time control Feature), to the mtserver/Web/OMC or the like currently serving the M2M service terminal M2, and the Feature not available (the corresponding Feature not available includes a group management Feature and a time control Feature);

or,

(2) for the occasion that the HSS/HLR is an M2M service communication entity, the HSS/HLR sends at least one of Feature supported by UE and Feature supported by MME/SGSN capability and the unavailable Feature to MTCServer/Web/OMC and the like;

corresponding example two: for the case that the HSS/HLR is an M2M service communication entity, the HSS/HLR to which the M2M service terminal M2 belongs sends, to an MTC Server/Web/OMC or the like currently providing services for the M2M service terminal M2, a Feature supported by the M2M service terminal M2 (the Feature supported by the M2M service terminal M2 may include a monitoring Feature and a PS only Feature) and a Feature supported by a corresponding MME/SGSN capability (the Feature supported by the corresponding MME/SGSN capability may include a monitoring Feature and a time control Feature), and the Feature is unavailable (the corresponding unavailable Feature includes a PS only Feature and a time control Feature).

In addition, for the case that the M2M service management entity returns a message, the specific operation steps of the corresponding M2M service communication entity may further include:

(1) the MME/SGSN receives the activatable Feature and/or the deactivatable Feature and informs the activatable Feature and/or the deactivatable Feature to the HSS/HLR; the HSS/HLR then carries out activation processing on the activatable Feature and/or deactivation processing on the deactivatable Feature;

the activatable Feature refers to a Feature supported by both the UE and the MME/SGSN capability after the activated or activating Feature is removed from the features subscribed by the user of the M2M service;

the Feature which can be deactivated refers to a Feature which is not supported by the UE and/or a Feature which is not supported by the MME/SGSN capability in the activated features of the M2M service;

optionally, the MME/SGSN may first receive an activatable Feature and/or a deactivatable Feature, and then determine whether the received activatable Feature can be activated according to at least one of a Feature supported by the UE and a Feature supported by the capability of the MME/SGSN, which are stored in the MME/SGSN, and if the activatable Feature can be activated, notify the activatable Feature to the HSS/HLR, and the HSS/HLR then performs activation processing on the activatable Feature; if the file can not be activated, the activated Feature is also used as a deactivatable Feature to be notified to the HSS/HLR, and the HSS/HLR then carries out deactivation processing on the deactivatable Feature; for the deactivatable Feature received by MME/SGSN, it can be directly notified to HSS/HLR, and the said HSS/HLR then carries out deactivation treatment to the said deactivatable Feature;

the first corresponding embodiment: an MME/SGSN providing a service for the M2M service terminal M1 may first receive an activatable Feature (the corresponding activatable Feature may include a Feature for theft prevention) and/or a deactivatable Feature (the corresponding deactivatable Feature may include a group management Feature and a time control Feature) returned by an MTC Server/Web/OMC or the like currently providing a service for the M2M service terminal M1, and then determine whether the received activatable Feature (the corresponding activatable Feature may include a Feature for theft prevention) can be activated according to at least one of a Feature supported by a UE and a Feature supported by the MME/SGSN capability, because the activatable Feature can be activated, notify the activatable Feature to an HSS/HLR, which then performs activation processing on the activatable Feature (the corresponding activatable Feature may include a Feature for theft prevention); for the deactivatable features received by the MME/SGSN, the deactivatable features may be directly notified to the HSS/HLR, and the HSS/HLR then deactivates the deactivatable features (the corresponding deactivatable features may include group management features and time control features);

or,

(2) the HSS/HLR directly receives the activatable features and/or the deactivatable features, and performs activation processing on the activatable features and/or deactivation processing on the deactivatable features;

optionally, the HSS/HLR may first receive an activatable Feature and/or a deactivatable Feature, and then determine whether the received activatable Feature can be activated according to at least one of a Feature supported by the UE and a Feature supported by the MME/SGSN capability stored in the HSS/HLR, and if the activatable Feature can be activated, perform activation processing on the activatable Feature; if the file cannot be activated, the activatable Feature is also used as a deactivatable Feature, and the deactivatable Feature is deactivated; deactivation processing can be directly carried out on the deactivatable Feature received by the HSS/HLR;

corresponding example two: the HSS/HLR to which the M2M service terminal M2 belongs may first receive an activatable Feature (the corresponding activatable Feature may include a monitoring Feature) and/or a deactivatable Feature (the corresponding deactivatable Feature may include a PS only Feature and a time control Feature) returned by an MTC Server/Web/OMC or the like currently providing services for the M2M service terminal M2, and then determine whether the received activatable Feature (the corresponding activatable Feature may include a monitoring Feature) can be activated according to at least one of a Feature supported by the UE and a Feature supported by the MME/SGSN capability stored in the HSS/HLR, because the activatable Feature can be activated, activate the activatable Feature (the corresponding activatable Feature may include a monitoring Feature); deactivation processing can be directly carried out on the deactivatable features (the corresponding deactivatable features can comprise PS only features and time control features) received by the HSS/HLR.

(II) M2M service management entity

As shown in fig. 4, in a specific implementation process of the M2M service optimization method provided in the embodiment of the present invention, an operation performed by an M2M service management entity corresponding to the M2M service communication entity may specifically include the following steps:

step 41, receiving at least one of Feature supported by UE and Feature supported by MME/SGSN capability;

specifically, the MTC Server/Web/OMC and the like receive at least one of Feature supported by UE and Feature supported by MME/SGSN capability;

the first corresponding embodiment: the MTC Server/Web/OMC or the like currently providing services for the M2M service terminal M1 receives at least one of features supported by the M2M service terminal M1 (the features supported by the M2M service terminal M1 may include features for theft prevention and group management features) and features supported by a corresponding MME/SGSN capability (the features supported by a corresponding MME/SGSN capability may include features for theft prevention and time control features) sent by the MME/SGSN providing services for the M2M service terminal M2;

corresponding example two: the MTC Server/Web/OMC, etc. currently providing services for the M2M service terminal M2 receives at least one of the Feature supported by the M2M service terminal M2 (the Feature supported by the M2M service terminal M2 may include a monitoring Feature and a PS only Feature) and the 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) sent by the HSS/HLR to which the M2M service terminal M2 belongs;

step 42, determining the activatable Feature according to at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability, the Feature signed by the user and/or the operation strategy of the operator, and activating the activatable Feature;

the corresponding activatable Feature refers to a Feature supported by both the UE and the MME/SGSN capability after the activated or currently activated Feature is removed from the features subscribed by the user of the M2M service;

specifically, the MTC Server/Web/OMC and the like determine the activatable 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 operation strategy of the operator, and activate the activatable Feature;

the first corresponding embodiment: the MTC Server/Web/OMC and the like currently providing services for the M2M service terminal M1 determines an activatable Feature (the corresponding activatable Feature may include an anti-theft Feature and a group management Feature) according to a Feature supported by the M2M service terminal M1 (the Feature supported by the M2M service terminal M1 may include at least one of an anti-theft Feature and a group management Feature) and a Feature supported by a corresponding MME/SGSN capability (the Feature supported by a corresponding MME/SGSN capability may include an anti-theft Feature and a time control Feature), and/or a user-subscribed Feature (the Feature subscribed to a corresponding user may include an anti-theft Feature and a group management Feature) and/or an operator operation policy (the operation policy of a corresponding operator may include that it is no longer determined whether the activated Feature is a certain activatable Feature for the already activated Feature), and activates the activatable Feature;

corresponding example two: the MTC Server/Web/OMC or the like currently providing services for the M2M service terminal M2 determines an activatable Feature (the corresponding activatable Feature may include the monitoring Feature) according to a Feature supported by the M2M service terminal M2 (the Feature supported by the M2M service terminal M2 may include at least one of the monitoring Feature and the PS only Feature) and a Feature supported by a corresponding MME/SGSN capability (the Feature supported by a corresponding MME/SGSN capability may include the monitoring Feature and the time control Feature), and/or a user-subscribed Feature (the Feature subscribed to a corresponding user may include the monitoring Feature and the PS only Feature) and/or an operator operation policy (the operation policy of a corresponding operator may include that it is no longer determined whether the activated Feature is a certain activatable Feature for the already activated Feature), and activates the Feature;

similarly to the above process of determining that Feature can be activated, this step may further include a process of determining that Feature can be deactivated, and the specific processing contents thereof are as follows: determining the activateable Feature according to at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability, the Feature signed by the user and/or the operation strategy of the operator, and deactivating the activateable Feature;

the corresponding deactivatable Feature refers to a Feature which is not supported by the UE and/or a Feature which is not supported by the MME/SGSN capability in the activated features of the M2M service;

specifically, the MTC Server/Web/OMC and 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 signed by the user and/or the operation policy of the operator, and deactivates the deactivatable Feature;

the first corresponding embodiment: the MTC Server/Web/OMC and the like currently providing services for the M2M service terminal M1 determine that the Feature can be deactivated (the corresponding deactivatable Feature may include the time control Feature and the group management Feature) according to at least one of the features supported by the M2M service terminal M1 (the features supported by the M2M service terminal M1 may include the theft prevention Feature and the group management Feature) and the features supported by the corresponding MME/SGSN capabilities (the features supported by the corresponding MME/SGSN capabilities may include the theft prevention Feature and the time control Feature), and the user-subscribed features (the features subscribed to the corresponding user may include the theft prevention Feature and the group management Feature) and/or the operation policy of the operator (the operation policy of the corresponding operator may include determining whether the activated features are fixed deactivatable features or not), and may deactivate the Feature;

corresponding example two: the MTC Server/Web/OMC and the like currently providing services for the M2M service terminal M2 may determine that a Feature may be deactivated (a corresponding deactivatable Feature may include a PS only Feature) according to a Feature supported by the M2M service terminal M2 (a Feature supported by the M2M service terminal M2 may include a monitoring Feature and a PS only Feature) and/or a Feature supported by a user subscription (a Feature supported by a corresponding MME/SGSN capability may include a monitoring Feature and a time control Feature) and/or an operation policy of an operator (an operation policy of a corresponding operator may include only determining whether an already activated Feature is a fixed deactivatable Feature), and may deactivate the Feature.

In addition, as shown in fig. 5, in the implementation process, the corresponding M2M service communication entity may further include the following operation steps:

step 51: receiving at least one of a Feature supported by the UE and a Feature supported by the MME/SGSN capability, and the Feature is unavailable;

specifically, at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability may be received while receiving the unavailable Feature, and the specific processing of this step is similar to that in step 41 and is not described in detail;

step 52: determining an activatable Feature according to at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability, at least one of the Feature signed by the user and the operation strategy of the operator, and the unavailable Feature, and activating the activatable Feature;

specifically, on the basis of the technical solution in step 42, the unavailable Feature is used as an auxiliary condition for determining that the Feature can be activated and/or deactivated; for example, a Feature may be determined to be deactivatable if it is not available;

the first corresponding embodiment: the MTC Server/Web/OMC or the like currently providing services for the M2M service terminal M1 receives at least one of Feature supported by the M2M service terminal M1 and Feature supported by corresponding MME/SGSN capability, which are sent by the MME/SGSN providing services for the M2M service terminal M2, and cannot use the Feature; the corresponding MTCServer/Web/OMC and the like determine the activatable Feature (the corresponding activatable Feature may comprise the anti-theft Feature) and/or the deactivatable Feature (the corresponding deactivatable Feature may comprise the time control Feature and the group management Feature) according to at least one of the Feature supported by the M1 of the M2M service terminal and the Feature supported by the corresponding MME/SGSN capability and the non-usable Feature (the corresponding non-usable Feature may comprise the time control Feature and the group management Feature), and the user subscribed Feature and/or the operator operating policy (the corresponding operator operating policy may comprise directly judging that the deactivation Feature is possible if the deactivation Feature is not usable), activate the activatable Feature (the corresponding deactivatable Feature may comprise the time control Feature and the group management Feature), activate the activatable Feature, and deactivate the deactivatable Feature;

corresponding example two: the MTC Server/Web/OMC, etc. currently providing services for the M2M service terminal M2 receives at least one of Feature supported by the M2M service terminal M2 and Feature supported by corresponding MME/SGSN capability, which are sent by the HSS/HLR to which the M2M service terminal M2 belongs, and cannot use the Feature; the corresponding mtserver/Web/OMC and the like determine the deactivatable Feature (the corresponding activatable Feature may include the monitoring Feature) and/or the deactivatable Feature (the corresponding deactivatable Feature may include the PS only Feature and the time control Feature) according to at least one of the Feature supported by the M2M service terminal M2 and the Feature supported by the corresponding MME/SGSN capability and the non-usable Feature (the corresponding non-usable Feature may include the PS only Feature and the time control Feature), and the user-subscribed Feature and/or the operator's operating policy (the corresponding operator's operating policy may include directly determining the deactivatable Feature if the non-usable Feature is present), and perform an activation process on the activatable Feature, and perform a deactivation process on the deactivatable Feature.

In addition, after the M2M service management entity determines that Feature can be activated and/or deactivated, the corresponding M2M service management entity may further perform the following operation steps: the MTC Server/Web/OMC and the like send the activatable Feature and/or the deactivatable Feature;

the first corresponding embodiment: the MTC Server/Web/OMC, etc. currently providing services for the M2M service terminal M1 sends the activatable Feature (the corresponding activatable Feature may include a tamper-resistant Feature) and/or the deactivatable Feature (the corresponding deactivatable Feature may include a time control Feature and a group management Feature) to the corresponding MME/SGSN or HSS/HLR;

corresponding example two: the MTC Server/Web/OMC or the like currently serving the M2M service terminal M2 sends the activatable Feature (the corresponding activatable Feature may include a monitoring Feature) and/or the deactivatable Feature (the corresponding deactivatable Feature may include a PS only Feature and a time control Feature) to the corresponding MME/SGSN or HSS/HLR.

In addition to the foregoing technical solutions, the M2M service optimization method provided in the embodiment of the present invention further includes another similar solution, so that the M2M service management entity knows the optimization solution supported by the UE and/or the MME/SGSN. In the following, a specific processing procedure that needs to be performed by the corresponding M2M service communication entity and M2M service management entity in another scheme will be described respectively.

M2M service communication entity

As shown in fig. 6, in a specific implementation process of the M2M service optimization method provided in the embodiment of the present invention, an operation performed by a corresponding M2M service communication entity may specifically include the following steps:

step 61, determining that the Feature can be activated and/or 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 signed by the user and/or the operation policy of the operator, and performing activation processing on the activated Feature and/or deactivation processing on the deactivated Feature;

correspondingly, determining that the Feature can be activated and/or 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 subscribed by the user and/or the operation policy of the operator may include:

(1) the MME/SGSN determines that the Feature can be activated and/or 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 signed by the user and/or the operation strategy of the operator;

example three: assuming that an M2M service terminal M3 supports features for theft prevention and features for group management, an MME/SGSN serving the M2M service terminal M3 supports features for theft prevention and features for time control, and the features subscribed by the M2M service terminal M3 may include features for theft prevention and features for time control; an MME/SGSN serving the M2M service terminal M3 determines an activatable Feature (the corresponding activatable Feature may include an anti-theft Feature) and/or a deactivatable Feature (the corresponding deactivatable Feature may include a group management Feature) according to at least one of features supported by the M2M service terminal M3 (features supported by the M2M service terminal M3 may include anti-theft features and group management features) and features supported by corresponding MME/SGSN capabilities (features supported by corresponding MME/SGSN capabilities may include anti-theft features and time control features) and/or user-subscribed features (the corresponding user-subscribed features may include anti-theft features and time control features) and/or operator's operating policy (the corresponding operator's operating policy may include no longer determining whether a particular activatable Feature for an already activated Feature) and/or a deactivatable Feature (the corresponding activatable Feature may include an anti-theft Feature and a time control Feature);

or,

(2) and the HSS/HLR determines that the Feature can be activated and/or 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 subscribed by the user and/or the operation strategy of the operator:

example four: assuming that a certain M2M service terminal M4 supports time control Feature and PS only Feature, an MME/SGSN serving the M2M service terminal M4 can support monitoring Feature and time control Feature, and the Feature subscribed by the M2M service terminal M4 may include monitoring Feature and time control Feature; the HSS/HLR to which the M2M service terminal M4 belongs determines an activatable Feature (the corresponding activatable Feature may include a time control Feature) and/or a deactivatable Feature (the corresponding deactivatable Feature may include a monitoring Feature and a PS only Feature) according to a 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 Feature supported by a corresponding MME/SGSN capability (the Feature supported by a corresponding MME/SGSN capability may include a monitoring Feature and a time control Feature), and a user-subscribed Feature (the corresponding user-subscribed Feature may include a monitoring Feature and a time control Feature) and/or an operator's administration policy (the corresponding operator's administration policy may include a monitoring Feature that no longer determines whether the activatable Feature is a fixed activatable Feature for an already activated Feature);

further, the corresponding activating treatment of the activatable Feature and/or deactivating treatment of the deactivatable Feature may include:

(1) for the occasion that the MME/SGSN is an M2M service communication entity, after the MME/SGSN determines that the Feature can be activated and/or deactivated, the MME/SGSN sends the activated and/or deactivated Feature to the HSS/HLR; the HSS/HLR carries out activation processing on the activatable Feature and/or carries out deactivation processing on the deactivatable Feature;

corresponding example three: for the case that the MME/SGSN is an M2M service communication entity, after determining that an activatable Feature (the corresponding activatable Feature may include a security-use Feature) and/or a deactivatable Feature (the corresponding deactivatable Feature may include a group management Feature and a time control Feature), the MME/SGSN serving the M2M service terminal M3 sends the activatable Feature and/or the deactivatable Feature to the HSS/HLR to which the M2M service terminal M3 belongs; then the HSS/HLR which the M2M service terminal M3 belongs to carries out activation processing on the activatable Feature and/or deactivation processing on the deactivatable Feature;

or,

(2) for the occasion that the HSS/HLR is the M2M service communication entity, after the HSS/HLR determines that the Feature can be activated and/or deactivated, the HSS/HLR directly activates the activatable Feature and/or deactivates the deactivatable Feature

Corresponding example four: for the case that the HSS/HLR is an M2M service communication entity, after the HSS/HLR to which the M2M service terminal M4 belongs determines an activatable Feature (the corresponding activatable Feature may include a time control Feature) and/or a deactivatable Feature (the corresponding deactivatable Feature may include a PS only Feature and a monitoring Feature), the HSS/HLR directly activates the activatable Feature and/or deactivates the deactivatable Feature;

step 62, sending an activatable Feature and/or a deactivatable Feature to the M2M service processing entity;

the corresponding M2M service management entity may include an MTC Server/Web/OMC, but is not limited to these network elements and the like;

specifically, for different M2M service communication entities in step 61, the step may specifically include:

(1) for the occasion that the MME/SGSN is an M2M service communication entity, the MME/SGSN sends an activatable Feature and/or an deactivatable Feature to the M2M service processing entity;

further, for the occasion that the MME/SGSN is the M2M service communication entity, the MME/SGSN may send an activatable Feature and/or a deactivatable Feature to the MTC Server/Web/OMC or the like while sending the activatable Feature and/or the deactivatable Feature to the HSS/HLR;

corresponding example three: for the case that the MME/SGSN is an M2M service communication entity, the MME/SGSN serving the M2M service terminal M3 may send an activatable Feature (the corresponding activatable Feature may include a theft-prevention Feature) and/or a deactivatable Feature (the corresponding deactivatable Feature may include a group management Feature and a time control Feature) to the mtserver/Web/OMC or the like currently serving the M2M service terminal M3, while sending the activatable Feature and/or the deactivatable Feature to the HSS/HLR to which the M2M service terminal M3 belongs;

or,

(1) for the occasion that the HSS/HLR is an M2M service communication entity, the HSS/HLR sends an activatable Feature and/or a deactivatable Feature to an MTC Server/Web/OMC and the like;

corresponding example four: for the case that the HSS/HLR is an M2M service communication entity, the HSS/HLR to which the M2M service terminal M4 belongs sends an activatable Feature (the corresponding activatable Feature may include a time control Feature) and/or a deactivatable Feature (the corresponding deactivatable Feature may include a PS only Feature and a monitor Feature) to an MTC Server/Web/OMC or the like that currently provides services for the M2M service terminal M4.

(II) M2M service management entity

As shown in fig. 7, in a specific implementation process of the M2M service optimization method provided in the embodiment of the present invention, an operation performed by an M2M service management entity corresponding to the M2M service communication entity may specifically include the following steps:

step 71, receiving an activatable Feature and/or a deactivatable Feature;

specifically, the MTC Server/Web/OMC and the like can receive the activatable Feature and/or the deactivatable Feature;

corresponding example three: the MTC Server/Web/OMC or the like currently providing services for the M2M service terminal M3 may receive an activatable Feature (the corresponding activatable Feature may include a security Feature) and/or a deactivatable Feature (the corresponding deactivatable Feature may include a group management Feature and a time control Feature);

corresponding example four: the MTC Server/Web/OMC or the like currently providing services for the M2M service terminal M4 may receive an activatable Feature (the corresponding activatable Feature may include a time control Feature) and/or may deactivate a Feature (the corresponding deactivatable Feature may include a PS only Feature and a monitoring Feature);

step 72, performing activation processing on the activatable Feature and/or performing deactivation processing on the deactivatable Feature;

specifically, the MTC Server/Web/OMC and the like performs activation processing on the activatable Feature and/or performs deactivation processing on the deactivatable Feature;

corresponding example three: the MTC Server/Web/OMC and the like currently providing services for the M2M service terminal M3 perform activation processing on the activatable Feature (the corresponding activatable Feature may include a Feature for theft prevention) and/or perform deactivation processing on the deactivatable Feature (the corresponding deactivatable Feature may include a group management Feature and a time control Feature);

corresponding example four: the MTC Server/Web/OMC or the like currently providing services for the M2M service terminal M4 performs activation processing on the activatable features (the corresponding activatable features may include time control features) and/or deactivation processing on the deactivatable features (the corresponding deactivatable features may include PS only features and monitoring features).

In order to make the objects, technical solutions and advantages of the present invention clearer, the following describes in detail an overall interaction process between an M2M service communication entity and an M2M service management entity provided in the embodiments of the present invention by referring to the embodiments and the accompanying drawings.

EXAMPLE five

As shown in fig. 8, a M2M service terminal M5 is taken as an example to explain an M2M service optimization method provided by the embodiment of the present invention. Assuming that the M2M service terminal M5 supports Feature for theft prevention and time control Feature, and the MME/SGSN providing service to the M2M service terminal M5 supports Feature for theft prevention, time control Feature and PS only Feature, the Feature subscribed to the M2M service terminal M5 includes Feature for theft prevention, time control Feature and PS only Feature, when the Feature subscribed to the user and stored in the HSS/HLR to which the M2M service terminal M5 belongs is already partially activated (the corresponding Feature that has been partially activated may include time control Feature and PS only Feature), and when the Feature subscribed to the user and stored in the HSS/HLR to which the M2 5 belongs is not stored in the MME/SGSN serving the M5 to which the M2M service terminal M5 is related to the M2 service terminal M5, the M2 4642 may implement a specific registration method from the M4673784 provided by the present invention to the MME/SGSN:

step 101, UE sends NAS message to MME/SGSN, and the message can carry the IMSI of UE, and the Feature information supported by UE;

for example, the corresponding M2M service terminal M5 sends an 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 information such as Feature supported by the M2M service terminal M5.

Step 102, after receiving the NAS message, the MME/SGSN stores 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;

for example, after receiving the NAS message, the corresponding MME/SGSN stores Feature supported by the M2M service terminal M5, and determines the ULR of the HSS/HLR to which the M2M service terminal M5 belongs according to the IMSI of the M2M service terminal M5;

step 103, the MME/SGSN routes to the HSS/HLR to which the UE belongs according to the ULR, and the corresponding ULR can carry the Feature supported by the UE and the Feature supported by the MME/SGSN capability;

for example, the corresponding MME/SGSN may route to the HSS/HLR to which the M2M service terminal M5 belongs according to the corresponding ULR; wherein, the corresponding ULR may carry Feature supported by the M5 of the corresponding M2M service terminal and Feature supported by the corresponding MME/SGSN capability;

step 104, after receiving the ULR, the HSS/HLR may determine whether the Feature activated in the features subscribed by the user may be used according to the Feature supported by the UE and/or the Feature supported by the MME/SGSN, uploaded by the MME/SGSN;

specifically, the determining whether the Feature subscribed by the user can use the Feature supported by the UE and/or the Feature supported by the MME/SGSN capability includes: judging whether the Feature supported by the UE and/or the Feature supported by the MME/SGSN capability are matched with the Feature signed by the user, if the Feature supported by the UE and/or the Feature supported by the MME/SGSN capability are matched with the Feature signed by the user, the Feature signed by the user can be used; if the Feature supported by the UE is not matched with the Feature subscribed by the user and/or the Feature supported by the MME/SGSN capability is not matched with the Feature subscribed by the user, the Feature subscribed by the user is unavailable;

for example, after receiving the ULR, the corresponding HSS/HLR may determine, 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, whether the Feature supported by the M2M service terminal M5 (the Feature supported by the corresponding M2M service terminal M5 may include a Feature for theft prevention and a time control Feature) and the Feature supported by the MME/SGSN capability (the Feature supported by the corresponding MME/SGSN capability may include a Feature for theft prevention, a time control Feature and a PS only Feature) match with the features already activated in the features subscribed to the user (the features already activated in the features subscribed to the user may include a time control Feature and a PS only Feature), so as to determine whether the features already activated in the features subscribed to the user may be used;

in a step 105, the process is carried out,

(1) for the Feature which can be used in the activated Feature, the HSS/HLR sends the Feature which can be used to the MME/SGSN;

for example: for the features already activated in the features subscribed by the user (the features already activated in the corresponding features subscribed by the user may include a time control Feature and a PS only Feature), if there are features matching with both the features supported by the M2M service terminal M5 (the features supported by the corresponding M2M service terminal M5 may include a tamper-resistant Feature and a time control Feature) and the features supported by the corresponding MME/SGSN capability (the features supported by the corresponding MME/SGSN capability may include a tamper-resistant Feature, a time control Feature and a PS only Feature), the corresponding HSS/HLR issues the available features (the corresponding features available may include a time control Feature) to the MME/MME;

(2) for features that cannot be used in features that have been activated, there may be two processing schemes for this step:

scheme 1: the HSS/HLR determines the activatable Feature and the deactivatable Feature according to at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability, the Feature subscribed by the user and the operator operation strategy;

for example: for an activated Feature among the features subscribed by the user (the activated Feature among the corresponding features subscribed by the user may include a time control Feature and a PS only Feature), if there is a Feature that cannot be matched with the Feature supported by the M2M service terminal M5 (the Feature supported by the corresponding M2M service terminal M5 may include a tamper-resistant Feature and a time control Feature, and does not include a PS only Feature) or a Feature supported by MME/SGSN capability (the Feature supported by the corresponding MME/SGSN capability may include a tamper-resistant Feature, a time control Feature, and a PS only Feature), the activated Feature (the corresponding activated Feature may include a PS only Feature) may not be used; then, the corresponding HSS/HLR responds to the Feature supported by the M2M service terminal M5 (the corresponding Feature supported by the M2M service terminal M5 may include a Feature for anti-theft and a Feature for time control) and the corresponding Feature supported by MME/SGSN capability (the corresponding Feature supported by MME/SGSN capability may include a Feature for anti-theft, a Feature for time control and a Feature for PS only), and user-subscribed features (the features subscribed to by the respective user may comprise anti-theft features, temporal control features and PS only features) and operator operating policies (the respective operator operating policies may comprise that no more activatable features are determined for already activated features) determining activatable features (the respective activatable features may comprise anti-theft features because temporal control features are already activated and may be used) and deactivatable features (the respective deactivatable features may comprise PS only features);

scheme 2: the HSS/HLR can send at least one item of Feature supported by MME/SGSN capability, Feature supported by UE, Feature unsupported by MME/SGSN capability in the activated Feature and/or Feature unsupported by UE to MTC Server/Web/OMC and the like;

for example: for an activated Feature among the features subscribed by the user (the activated Feature among the corresponding features subscribed by the user may include a time control Feature and a PS only Feature), if there is a Feature that cannot be matched with the Feature supported by the M2M service terminal M5 (the Feature supported by the corresponding M2M service terminal M5 may include a tamper-resistant Feature and a time control Feature, and does not include a PS only Feature) or a Feature supported by MME/SGSN capability (the Feature supported by the corresponding MME/SGSN capability may include a tamper-resistant Feature, a time control Feature, and a PS only Feature), the activated Feature (the corresponding activated Feature may include a PS only Feature) may not be used; then, the corresponding HSS/HLR may send the 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 supported by the M2M service terminal M5 (the Feature supported by the corresponding M2M service terminal M5 may include an anti-theft Feature and a time control Feature), and the Feature not supported by the M2M service terminal M5 in the already activated features (the Feature not supported by the corresponding M2M service terminal M5 may include a PS only Feature) to the mtserver/Web/OMC or the like currently serving the M2M service terminal M5;

in a step 106 of the method, the step of the method,

(1) for Feature that can be used in Feature that has been activated, then the step is: the MME/SGSN informs the UE that the registration is successful, namely the processing of the Feature which can be used is finished;

for example: the corresponding ME/SGSN informs the M2M that the registration of the service terminal M5 is successful, namely the process for the available Feature is ended;

(2) for Feature that cannot be used in Feature that has been activated, the step is:

scheme 1: the HSS/HLR sets the activation state identification update of the activatable feature as activated, and sets the activation state identification update of the deactivatable feature as deactivated;

for example: the corresponding HSS/HLR sets the activation status identity update of the activatable Feature (the corresponding activatable Feature may comprise a tamper-resistant Feature) to active, and the activation status identity update of the deactivatable Feature (the corresponding deactivatable Feature may comprise a PS only Feature) to deactivate;

scheme 2: the MTC Server/Web/OMC and the like determine the activatable Feature and the deactivatable 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 operation strategy;

for example: corresponding MTC Server/Web/OMC and the like can be based on the Feature supported by the M2M service terminal M5 (the Feature supported by the M2M service terminal M5 can include anti-theft Feature and time control Feature) and the Feature supported by the corresponding MME/SGSN capability (the Feature supported by the corresponding MME/SGSN capability can include anti-theft Feature, time control Feature and PS only Feature), and user-subscribed features (the features subscribed to by the respective user may comprise anti-theft features, temporal control features and PS only features) and operator operating policies (the respective operator operating policies may comprise that no activatable Feature is determined anymore for already activated features) determining activatable features (the respective activatable features may comprise anti-theft features because temporal control features are already activated and may be used) and deactivatable features (the respective deactivatable features may comprise PS only features);

in a step 107, the step of,

for Feature that cannot be used in Feature that has been activated, the step is:

scheme 1: the HSS/HLR sends the activatable and deactivatable features to the MTC Server/Web/OMC and the like;

for example: the corresponding HSS/HLR may send the activatable Feature (the corresponding activatable Feature may comprise the Feature for theft prevention) and the deactivatable Feature (the Feature of the corresponding deactivatable Feature may comprise the PS only Feature) to the MTC Server/Web/OMC or the like currently serving the M2M service terminal M5;

scheme 2: the MTC Server/Web/OMC and the like perform activation processing on the activatable features and perform deactivation processing on the deactivatable features; and transmitting the activatable and/or deactivatable features to the HSS/HLR for activation;

for example: the corresponding MTC Server/Web/OMC and the like carry out activation processing on the activatable Feature (the corresponding activatable Feature can comprise a security Feature), and carry out deactivation processing on the deactivatable Feature (the corresponding deactivatable Feature can comprise a PSonly Feature); and transmitting the activatable and deactivatable features to the HSS/HLR for activation;

in a step 108, the step of,

scheme 1: the HSS/HLR may issue the activatable feature to the MME/SGSN; meanwhile, the MTC Server/Web/OMC and the like perform activation processing on the activatable features and perform deactivation processing on the deactivatable features;

for example: the corresponding HSS/HLR may issue Feature (the corresponding activatable Feature may include Feature for anti-theft) of the activatable Feature to the corresponding MME/SGSN; meanwhile, a corresponding MTC Server/Web/OMC or the like performs activation processing on the activatable Feature (the corresponding activatable Feature may include a tamper-resistant Feature), and performs deactivation processing on the deactivatable Feature (the corresponding deactivatable Feature may include a PS only Feature);

scheme 2: for the activatable Feature, the HSS/HLR checks whether the activatable Feature can be activated or not according to the Feature supported by the MME/SGSN capability and the Feature supported by the UE, if so, the activation state identifier of the activatable Feature is updated to be activated, otherwise, the activation failure information of the activatable Feature is notified to the corresponding MTC Server/Web/OMC and the like, and the corresponding MTC Server/Web/OMC and the like deactivate the activatable Feature which is failed to be activated; for the feature which can be deactivated, the HSS/HLR directly sets the activation state identification of the feature which can be deactivated as deactivation;

for example: for an activatable Feature (the corresponding activatable Feature may include a Feature for theft prevention), 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 so, sets an activation status identifier update of the activatable Feature (the corresponding activatable Feature may include the Feature for theft prevention) to be activated, otherwise, notifies an activatable Feature activation failure message to a corresponding MTC Server/Web/OMC, etc., and the corresponding MTC Server/Web/OMC, etc. deactivates the activatable Feature that fails to be activated; for deactivatable features (the corresponding deactivatable features may comprise PS only features), the corresponding HSS/HLR directly sets the activation status identity update of the deactivatable features to deactivated;

in a step 109 of the method, the step of the method,

scheme 1: MME/SGSN sends response message to HSS/HLR, namely scheme one finishes processing activated Feature;

for example: the corresponding MME/SGSN sends a response message to the corresponding HSS/HLR, namely the activated Feature processing of the scheme one is ended;

scheme 2: the HSS/HLR may issue the activatable feature to the MME/SGSN;

for example: the corresponding HSS/HLR may issue an activatable Feature (the corresponding activatable Feature may include a tamper Feature) to the corresponding MME/SGSN;

in a step 110, the method further comprises the steps of,

scheme 2: MME/SGSN sends response message to HSS/HLR, namely scheme two finishes processing activated Feature;

for example: the corresponding MME/SGSN sends a response message to the corresponding HSS/HLR, namely the scheme II finishes the activated Feature processing;

therefore, the implementation of the embodiment of the invention enables the M2M service management entity to timely know the optimization scheme supported by the UE and/or the MME/SGSN, and when the Feature subscribed by the user is unavailable, the activatable Feature and the deactivatable Feature can be determined according to the Feature supported by the MME/SGSN capability and/or the Feature supported by the UE, so that the M2M service is optimized.

EXAMPLE six

As shown in fig. 9, a M2M service terminal M6 is taken as an example to explain an M2M service optimization method provided by the embodiment of the present invention. If the M2M service terminal M6 has been registered to a corresponding MME/SGSN, and a Feature supported by the M2M service terminal M6 and a Feature supported by a corresponding MME/SGSN capability, which are registered by the M2M service terminal M6, have been stored in the HSS/HLR to which the M2M service terminal M6 belongs, when an mtserver/Web/OMC or the like currently serving the M2M service terminal M6 needs to activate a new Feature of the M2M service terminal M6 (the new Feature of the M2M service terminal M6 can be an anti-theft Feature) by using the M2M service optimization method provided by the present invention, the specific implementation steps may include:

step 201, MTC Server/Web/OMC sends Feature to be activated to HSS/HLR;

for example: the MTC Server/Web/OMC and the like which currently serve the M6 service terminal M2M send the Feature for theft prevention to be activated to the HSS/HLR to which the M6 service terminal M2M belongs;

step 202, the HSS/HLR judges whether the Feature required to be activated can be activated or not according to the Feature supported by the UE registered by the UE and/or the Feature supported by the capability of the MME/SGSN;

for example: the corresponding HSS/HLR can judge whether the Feature for anti-theft which needs to be activated can be activated or not according to the Feature supported by the M6 of the M2M service terminal and the Feature supported by the corresponding MME/SGSN capability;

in the step 203, the process is carried out,

assume that 1: if the HSS/HLR judges that the Feature which needs to be activated can be activated, the HSS/HLR can update the activation state identifier of the Feature which can be activated into activation, and sends the newly activated Feature to a corresponding MME/SGSN through an IDR message (a user inserting message which is used for notifying the MME/SGSN serving the user terminal at present after the user signed Feature in the HSS/HLR is changed);

for example: if both the Feature supported by the M2M service terminal M6 and the Feature supported by the corresponding MME/SGSN capability can support the Feature for anti-theft, the corresponding HSS/HLR may determine that the Feature for anti-theft can be activated; then, the corresponding HSS/HLR sets the activation status identifier update of the Feature for theft prevention to be active, and sends the Feature for theft prevention to the MME/SGSN serving the M2M service terminal M6 through an IDR message;

assume 2: if the HSS/HLR judges that the Feature which needs to be activated can not be activated, the HSS/HLR can send the activation failure information of the Feature which can not be activated, the Feature supported by the MME/SGSN capability registered by the UE and/or the Feature supported by the UE to the MTC Server/Web/OMC and the like;

for example: if at least one of the Feature supported by the M2M service terminal M6 and the Feature supported by the corresponding MME/SGSN capability does not support the anti-tamper Feature, the corresponding HSS/HLR may determine that the anti-tamper Feature cannot be activated; then, the corresponding HSS/HLR may send the activation failure information of the Feature for theft prevention, the Feature supported by the M2M service terminal M6 and the Feature supported by the corresponding MME/SGSN capability to the MTC Server/Web/OMC or the like currently serving the M2M service terminal M6;

in a step 204, the process is carried out,

for hypothesis 1, the step is: MME/SGSN returns response information to HSS/HLR, then the activation process is finished;

for example: the corresponding MME/SGSN returns response information to the corresponding HSS/HLR, and the activation flow of the anti-theft Feature is ended;

for hypothesis 2, the step is: judging whether an activatable Feature exists according to a Feature supported by the MME/SGSN capability uploaded by the HSS/HLR and/or a Feature supported by the UE by the MTC Server/Web/OMC and the like, if so, executing the step 201 again, otherwise, exiting the activation process;

for example: corresponding MTC Server/Web/OMC and the like judge whether the activatable Feature exists according to the Feature supported by the M2M service terminal M6 and the Feature supported by the corresponding MME/SGSN capability uploaded by the HSS/HLR, if the activatable Feature exists, the step 201 is executed again, and the activation flow of the activatable Feature is entered; and if the activatable Feature does not exist, exiting the activation process of the Feature for preventing burglary.

EXAMPLE seven

As shown in fig. 10, a M2M service terminal M7 is taken as an example to explain an M2M service optimization method provided by the embodiment of the present invention. If the M2M service terminal M7 supports the Feature for theft prevention and the time control Feature, the MME/SGSN serving the M2M service terminal M7 supports the Feature for theft prevention, the time control Feature, and the PS only Feature, and the Feature subscribed by the M2M service terminal M7 includes the Feature for theft prevention, the time control Feature, and the PS only Feature; if the M2M service terminal M7 was successfully registered to the MME/SGSN, but the registration is not performed in the normal exit manner due to power exhaustion, and the like, so the Feature signed by the user issued by the HSS/HLR when the registration is successfully performed is stored in the MME/SGSN (the Feature stored in the corresponding MME/SGSN may include a time control Feature and a PS only Feature), then the specific implementation step of the M2M service terminal M7 registering again to the MME/SGSN by using the M2M service optimization method provided by the present invention may include:

step 301, the UE sends an NAS message to the MME/SGSN, and the message may carry information such as IMSI of the UE and Feature supported by the UE;

for example, the corresponding M2M service terminal M7 sends an NAS message to the MME/SGSN, and the NAS message may carry the IMSI of the M2M service terminal M7 and information such as Feature supported by the M2M service terminal M7;

step 302, the MME/SGSN can determine whether the Feature signed by the user and stored in the MME/SGSN can be used according to the Feature supported by the UE and the Feature supported by the MME/SGSN capability;

for example: the features of the user subscription stored in the MME/SGSN are all in an active state since they were stored when the M2M service terminal M7 successfully registered last time; then, determining whether the Feature supported by the M2M service terminal M7 and the Feature supported by the corresponding MME/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) match the Feature stored in the MME/SGSN (the Feature stored in the corresponding MME/SGSN may include the time control Feature and the PS only Feature) according to the Feature supported by the M2M service terminal M7 (the Feature supported by the corresponding M2M service terminal M7 may include the anti-theft Feature and the time control Feature) and the Feature supported by the corresponding MME/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), so as to determine whether the Feature stored in the MME/SGSN subscribed by the user can be used;

in a step 303, the process is executed,

(1) for the features which can be used in the features stored by the MME/SGSN, the MME/SGSN informs the HSS/HLR of all the available features;

for example: for the available features in the features saved by the corresponding MME/SGSN (the corresponding available features may include time control features), the MME/SGSN informs the HSS/HLR of the available features:

(2) for the Feature which can not be used in the features stored by the MME/SGSN, the MME/SGSN informs the HSS/HLR of the features supported by the UE, the features supported by the MME/SGSN capability, and the features which are not supported by the MME/SGSN capability and/or the features which are not supported by the UE (namely the features which can not be used) in the features stored by the MME/SGSN;

for example: for features that cannot be used in features stored by a corresponding MME/SGSN (the corresponding features that cannot be used may include PS only features), the MME/SGSN notifies a HSS/HLR to which the M2M service terminal M7 belongs of features supported by the M2M service terminal M7 (the features supported by the M2M service terminal M7 may include anti-theft features and time control features), features supported by a corresponding MME/SGSN capability (the features supported by the corresponding MME/SGSN capability may include anti-theft features, time control features and PS only features), and the features that cannot be used;

in a step 304, the process is carried out,

(1) for the Feature that can be used in the features stored by the MME/SGSN, the step is as follows:

the HSS/HLR returns a response message to the MME/SGSN;

for example: the corresponding HSS/HLR returns a response message to the MME/SGSN which provides service for the M2M service terminal M7;

(2) for features that cannot be used in features saved by the MME/SGSN, there may be two following processing schemes in this step:

scheme 1: the HSS/HLR deactivates the Feature which can not be used and informs the deactivated Feature to an MTC Server/Web/OMC and the like;

for example: the corresponding HSS/HLR deactivates the unavailable Feature (the corresponding unavailable Feature may comprise a PS only Feature), and notifies the deactivated Feature to an MTC Server/Web/OMC and the like which currently provide services for the M2M service terminal M7;

scheme 2: the HSS/HLR deactivates the Feature which cannot be used and informs at least one of the deactivated Feature and the Feature supported by the UE and the Feature supported by the MME/SGSN capability to MTCServer/Web/OMC and the like;

for example: the corresponding HSS/HLR deactivates the unusable Feature (the corresponding unusable Feature may include a PS only Feature), and notifies at least one of the deactivated Feature, a Feature supported by the M2M service terminal M7 (the Feature supported by the corresponding M2M service terminal M7 may include an anti-theft 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 an anti-theft Feature, a time control Feature and a PS only Feature) to an MTC Server/Web/OMC or the like currently serving the M2M service terminal M7;

in a step 305 of the method, the step is described,

the MME/SGSN informs the UE that the registration is successful, and the processing flow can be exited;

for example: the corresponding MME/SGSN informs the M2M that the registration of the service terminal M7 is successful, and the processing flow can be exited;

scheme 1: the MTC Server/Web/OMC and the like deactivate the deactivated Feature, and meanwhile, the HSS/HLR determines the Feature suitable for activation according to the Feature supported by the UE and the Feature supported by the MME/SGSN capability;

for example: deactivating the deactivated Feature (the deactivated Feature may include a PS only Feature) by the corresponding MTC Server/Web/OMC, etc., and determining, by the corresponding HSS/HLR, a Feature suitable for activation (the corresponding Feature suitable for activation may include a theft-prevention Feature, a time-controlled Feature, and a PS only Feature) according to the Feature supported by the M2M service terminal M7 (the Feature supported by the corresponding M2M service terminal M7 may include a theft-prevention Feature and a time-controlled Feature) and the Feature supported by the corresponding MME/SGSN capability (the Feature supported by the corresponding MME/SGSN capability may include a theft-prevention Feature, a time-controlled Feature, and a PS only Feature);

scheme 2: the MTC Server/Web/OMC and the like carry out deactivation processing on the deactivated Feature, and meanwhile, the Feature suitable for activation is determined according to the Feature supported by the UE and the Feature supported by the MME/SGSN capability and is activated;

for example: the corresponding MTC Server/Web/OMC and the like perform deactivation processing on the deactivated Feature (the deactivation may include PS only Feature), and at the same time, determine a Feature suitable for activation (the corresponding Feature suitable for activation may include anti-theft Feature, time control Feature and PS only Feature) according to the features supported by the M2M service terminal M7 (the features supported by the M2M service terminal M7 may include anti-theft Feature and time control Feature) and the features supported by the corresponding MME/SGSN capability (the features supported by the corresponding MME/SGSN capability may include anti-theft Feature, time control Feature and PS only Feature), and perform activation processing;

in a step 306 of the method, the step of the method,

for features that cannot be used in features saved by the MME/SGSN, there may be two following processing schemes in this step:

scheme 1: the HSS/HLR sets the activation state identification update of Feature suitable for activation as activation;

for example: the corresponding HSS/HLR sets the activation state identification update of the Feature suitable for activation (the corresponding Feature suitable for activation can comprise the anti-theft Feature) to be activated;

scheme 2: the MTC Server/Web/OMC and the like inform the Feature suitable for activation to the HSS/HLR;

for example: the corresponding MTC Server/Web/OMC and the like inform the proper activated Feature (the corresponding proper activated Feature can comprise the anti-theft Feature) to the corresponding HSS/HLR;

in a step 307, the process is executed,

scheme 1: the HSS/HLR informs the Feature suitable for activation to an MTC Server/Web/OMC and the like;

for example: the corresponding HSS/HLR informs the Feature suitable for activation (the corresponding Feature suitable for activation can comprise anti-theft Feature) to the MTC Server/Web/OMC and the like which currently provides services for the M2M service terminal M7;

scheme 2: the HSS/HLR sets the activation state identification update of the Feature suitable for activation as activation;

in a step 308, the process is executed,

scheme 1: the HSS/HLR transmits the Feature suitable for activation to a corresponding MME/SGSN, and meanwhile, MTCServer/Web/OMC and the like perform activation processing on the Feature suitable for activation;

for example: the corresponding HSS/HLR sends the Feature suitable for activation (the corresponding Feature suitable for activation can comprise the Feature for anti-theft) to the corresponding MME/SGSN, and meanwhile, the corresponding MTC Server/Web/OMC and the like carry out activation processing on the Feature suitable for activation (the corresponding Feature suitable for activation can comprise the Feature for anti-theft);

scheme 2: the HSS/HLR sends the Feature suitable for activation to a corresponding MME/SGSN;

for example: the corresponding HSS/HLR sends the Feature suitable for activation (the corresponding Feature suitable for activation can comprise the Feature for anti-theft) to the corresponding MME/SGSN;

step 309, for features that cannot be used in the features stored by the MME/SGSN, the step is:

MME/SGSN sends response message to corresponding HSS/HLR;

for example: the corresponding MME/SGSN sends a response message to the corresponding HSS/HLR;

Example eight

As shown in fig. 11, an M2M service terminal M8 is taken as an example to explain an M2M service optimization method provided by the embodiment of the present invention. Assuming that the M2M service terminal M8 supports features for theft prevention, and features for time control, and the MME/SGSN serving the M2M service terminal M8 supports features for theft prevention, features for time control, and PS only features, the Feature subscribed to the M2M service terminal M8 includes features for theft prevention, features for time control, and PS only features, when the Feature subscribed to the user and stored in the HSS/HLR to which the M2M service terminal M8 belongs is already partially activated (the corresponding activated Feature may include features for time control and PS only features), and when the Feature subscribed to the M2M service terminal M8 is not stored in the MME/SGSN serving the M2M service terminal M8, the M2M service terminal M8 may implement a specific registration method to the MME by using the M2 SGSN 2M provided by the present invention, which may include:

step 401, the UE sends an NAS message to the MME/SGSN, and the message may carry the IMSI of the UE and information such as Feature supported by the UE;

for example, the corresponding M2M service terminal M8 sends an NAS message to the MME/SGSN, and the NAS message may carry the IMSI of the M2M service terminal M8 and information such as Feature supported by the M2M service terminal M8;

step 402, after receiving the NAS message, the MME/SGSN stores Feature supported by the corresponding UE, and then determines the ULR of the HSS/HLR to which the UE belongs according to the IMSI of the UE;

for example, after receiving the NAS message, the MME/SGSN serving the M2M service terminal M8 stores Feature supported by the M2M service terminal M8, and determines the ULR of the HSS/HLR to which the M2M service terminal M8 belongs according to information such as IMSI of the M2M service terminal M8;

step 405, MME/SGSN routes to HSS/HLR to which UE belongs according to ULR;

for example, the corresponding MME/SGSN routes 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 in the user subscribed features stored in the HSS/HLR to the MME/SGSN;

for example: after receiving the ULR, the HSS/HLR to which the M2M service terminal M8 belongs sends the activated Feature (the activated Feature may include a time control Feature and a PS only Feature) in the features subscribed by the company stored in the HSS/HLR to the corresponding MME/SGSN;

step 405, the MME/SGSN determines whether the activated Feature issued by the HSS/HLR can be used according to at least one of the Feature supported by the UE and the Feature supported by the MME/SGSN capability;

for example: the corresponding HSS/HLR determines whether the activated Feature issued by the HSS/HLR (the corresponding activated Feature may include a time control Feature and a PS only Feature) can be used according to the Feature supported by the M2M service terminal M8 (the Feature supported by the corresponding M2M service terminal M8 may include a Feature for anti-theft and a time control Feature) and the Feature supported by the corresponding MME/SGSN capability (the Feature supported by the corresponding MME/SGSN capability may include a Feature for time control, a Feature for PS only and a Feature for anti-theft);

in a step 406, the process is executed,

(1) for the Feature which can be used in the activated Feature, the MME/SGSN informs the UE that the registration is successful, namely the processing flow of the Feature which can be used is completed;

for example: for features that can be used in the activated features (when the corresponding features that can be used can include time control features), the MME/SGSN notifies the M2M that the registration of the service terminal M8 is successful, that is, the processing flow of the features that can be used is completed;

scheme 1: the MME/SGSN determines the Feature suitable for activation according to at least one of the Feature supported by the MME/SGSN capability and the Feature supported by the UE, and the Feature signed by the user and/or the operator operation strategy;

for example: for features that are not available in the already activated features (the corresponding features that are not available may include PS only features), the corresponding MME/SGSN determines features that are suitable for activation (the corresponding features that are supported by MME/SGSN capabilities may include anti-theft features, time-controlled features, and PS only features) and features that are supported by the M2M service terminal M8 (the corresponding features that are supported by the M2M service terminal M8 may include anti-theft features and time-controlled features), and user-subscribed features (the corresponding user-subscribed features may include anti-theft features, time-controlled features, and PS only features) and operator operation policies (the corresponding operator operation policies may include operator operation policies that do not determine whether or not the already activated features are suitable for activation);

scheme 2: the MME/SGSN can send at least one of the Feature supported by the MME/SGSN capability, the Feature supported by the UE, the Feature not supported by the MME/SGSN capability in the activated features and/or the Feature not supported by the UE (namely the Feature which can not be used) to the MTC Server/Web/OMC and the like;

for example: for features that cannot be used in the features that have been activated (corresponding features that cannot be used may include PS only features), the MME/SGSN may send at least one of features supported by the MME/SGSN capability (features supported by the corresponding MME/SGSN capability may include anti-theft features, time control features, and PS only features), features supported by the M2M service terminal M8 (features supported by the corresponding M2M service terminal M8 may include anti-theft features and time control features), features supported by the non-usable features may include PS only features), MTC servers/Web/OMCs that currently provide services for the M2M service terminal M8, and the like;

in a step 407 of the method,

for features that cannot be used in features that have been activated, there may be two processing schemes for this step:

scheme 1: MME/SGSN transmits the Feature suitable for activation to HSS/HLR and MTCServer/Web/OMC, etc. respectively;

for example: the corresponding MME/SGSN transmits the Feature suitable for activation (the corresponding Feature suitable for activation can comprise the Feature for anti-theft) to the corresponding HSS/HLR and the MTC Server/Web/OMC and the like respectively;

scheme 2: the MTC Server/Web/OMC and the like determine the Feature suitable for activation according to at least one of the Feature supported by the MME/SGSN capability uploaded by the MME/SGSN and the Feature supported by the UE, the Feature signed by the user and the operator operation strategy;

for example: corresponding MTC Server/Web/OMC and the like determine the Feature suitable for activation according to the Feature supported by the MME/SGSN (the Feature supported by the corresponding MME/SGSN capability can comprise the anti-theft Feature, the time control Feature and the PS only Feature) uploaded by the MME/SGSN and the Feature supported by the M2M service terminal M8 (the Feature supported by the corresponding M2M service terminal M8 can comprise the anti-theft Feature and the time control Feature), and the Feature signed by the user (the Feature signed by the user can comprise the anti-theft Feature, the time control Feature and the PS only Feature) and the operator operation policy (the corresponding operator operation policy can comprise the Feature not determined by the activated Feature as the Feature suitable for activation or not);

in a step 408, the process is executed,

scheme 1: the MTC Server/Web/OMC and the like activate the Feature suitable for activation; meanwhile, the HSS/HLR sets the activation state identification update of the Feature suitable for activation as activation, and sends a response message to the MME/SGSN;

for example: the corresponding MTC Server/Web/OMC and the like activate the Feature suitable for activation (the corresponding Feature suitable for activation can comprise the Feature for anti-theft); meanwhile, the corresponding HSS/HLR sets the activation status identification update of the Feature suitable for activation (the corresponding Feature suitable for activation may include the anti-theft Feature) to be active, and sends a response message to the MME/SGSN;

scheme 2: the MTC Server/Web/OMC and the like activate the Feature suitable for activation and transmit the Feature to the MME/SGSN;

for example: the corresponding MTC Server/Web/OMC and the like activate the Feature suitable for activation (the corresponding Feature suitable for activation can comprise the Feature for anti-theft) and transmit the Feature to the MME/SGSN;

in a step 409, the process is executed,

for features that are not available in features that have already been activated, the following processing scheme may exist for this step:

scheme 2: MME/SGSN transmits the Feature suitable for activation to HSS/HLR;

for example: the corresponding MME/SGSN transmits the Feature suitable for activation (the corresponding Feature suitable for activation may comprise the anti-theft Feature) to the HSS/HLR;

in a step 410, the process is executed,

scheme 2: the HSS/HLR sets the activation state identification update of the Feature suitable for activation as activation, and sends a response message to the MME/SGSN;

for example: the corresponding HSS/HLR sets the activation status identification update of the suitable activated Feature (the corresponding suitable activated Feature can comprise the anti-theft Feature) to be activated, and sends a response message to the corresponding MME/SGSN;

therefore, the implementation of the embodiment of the invention enables the M2M service management entity to timely know the optimization scheme supported by the UE and/or the MME/SGSN, and when the Feature signed by the user is unavailable, the activatable Feature can be determined according to the Feature supported by the MME/SGSN capability and/or the Feature supported by the UE, so that the M2M service is optimized.

Example nine

As shown in fig. 12, an M2M service terminal M9 is taken as an example to explain an M2M service optimization method provided by the embodiment of the present invention. Assuming that the M2M service terminal M5 supports a Feature for theft prevention and a time control Feature, an MME/SGSN serving the M2M service terminal M9 supports a Feature for theft prevention, a time control Feature, and a PS only Feature, and the Feature subscribed by the M2M service terminal M9 includes a Feature for theft prevention, a time control Feature, and a PS only Feature; if the M2M service terminal M9 was successfully registered to the MME/SGSN, but the registration is not performed in the normal exit manner due to power exhaustion, and the like, so the Feature signed by the user issued by the HSS/HLR at the time of successful registration is stored in the MME/SGSN (the Feature stored in the corresponding MME/SGSN may include a time control Feature and a PS only Feature), the specific implementation step of the M2M service terminal M9 registering to the MME/SGSN again by using the M2M service optimization method provided by the present invention may include:

step 501, the UE sends an NAS message to the MME/SGSN, and the message may carry the IMSI of the UE and information such as Feature supported by the UE;

for example, the corresponding M2M service terminal M9 sends an NAS message to the MME/SGSN, and the NAS message may carry the IMSI of the M2M service terminal M9 and information such as Feature supported by the M2M service terminal M9;

step 502, the MME/SGSN can determine whether the Feature signed by the user and stored in the MME/SGSN can be used according to the Feature supported by the UE and the Feature supported by the capability of the MME/SGSN;

for example: the features of the user subscription stored in the MME/SGSN are all in an active state since they were stored when the M2M service terminal M9 successfully registered last time; then, determining whether the Feature supported by the M2M service terminal M9 (the Feature supported by the corresponding M2M service terminal M9 may include a Feature for theft prevention and a Feature for time control) and the Feature supported by the corresponding MME/SGSN capability (the Feature supported by the corresponding MME/SGSN capability may include a Feature for theft prevention, a Feature for time control and a Feature for PS only) match the Feature stored in the MME/SGSN (the Feature stored in the corresponding MME/SGSN may include a Feature for time control and a Feature for PS only), so as to determine whether the Feature signed by the user and stored in the MME/SGSN can be used;

in a step 503 of the method,

(1) for the Feature which can be used in the features stored by the MME/SGSN, the MME/SGSN informs the UE that the registration is successful, namely the processing flow of the Feature which can be used is completed;

for example: for features that can be used in the features stored by the MME/SGSN (the corresponding features that can be used may include a time control Feature), the corresponding MME/SGSN notifies the M2M that the service terminal M9 is successfully registered, that is, completes the processing flow of the features that can be used;

scheme 1: the MME/SGSN determines the Feature suitable for activation according to at least one of the Feature supported by the MME/SGSN capability and the Feature supported by the UE, the Feature stored in the MME/SGSN and the operator operation strategy;

for example: for features that are not available in the features saved by the MME/SGSN (the corresponding non-available features may include PS only features), the corresponding MME/SGSN according to the Feature supported by the M2M service terminal M9 (the Feature supported by the corresponding M2M service terminal M9 may include a Feature for anti-theft and a Feature for time control) and the Feature supported by the corresponding MME/SGSN capability (the Feature supported by the corresponding MME/SGSN capability may include a Feature for anti-theft, a Feature for time control and a Feature for PS only), and the user-subscribed features (the corresponding user-subscribed features may include the anti-theft features, the time-controlled features, and the PS only features) and the operator operating policy (the corresponding operator operating policy may include the already activated features not being determined to be the features suitable for activation) determine the features suitable for activation (the corresponding features suitable for activation may include the anti-theft features);

scheme 2: the MME/SGSN informs MTCServer/Web/OMC and the like of at least one of the Feature supported by the UE, the Feature supported by the MME/SGSN capability and the Feature not supported by the UE and/or the Feature not supported by the MME/SGSN capability in the features saved by the MME/SGSN;

for example: for features that cannot be used in the features stored by the MME/SGSN (corresponding features that cannot be used may include PS only features), the MME/SGSN notifies features supported by the M2M service terminal M9 (features supported by the M2M service terminal M9 may include anti-theft features and time control features), features supported by the MME/SGSN capabilities (features supported by the corresponding MME/SGSN capabilities may include anti-theft features, time control features, and PS only features), and features that cannot be used (corresponding features that cannot be used may include PS only features) to the MTC Server/Web/OMC, etc. currently serving the M2M service terminal M9;

in a step 504 of the method, the step of the method,

for example: the corresponding MME/SGSN transmits the Feature suitable for activation (the corresponding Feature suitable for activation can comprise the Feature for anti-theft) to the HSS/HLR and the MTC Server/Web/OMC and the like respectively;

for example: corresponding MTC Server/Web/OMC etc. determining a suitable activated Feature (corresponding suitable activated Feature may include a tamper-proof Feature) from features supported by the M2M service terminal M9 (corresponding features supported by the M2M service terminal M9 may include a tamper-proof Feature and a time-controlled Feature) and corresponding MME/SGSN capabilities (corresponding MME/SGSN capabilities supported features may include a tamper-proof Feature, a time-controlled Feature and a PS only Feature), and a user subscribed Feature (corresponding user subscribed Feature may include a tamper-proof Feature, a time-controlled Feature and a PS only Feature) and an operator administration policy (corresponding operator administration policy may include that an already activated Feature is not determined to be a suitable activated Feature);

in the step 505, the process is executed,

scheme 1: the MTC Server/Web/OMC and the like carry out activation processing on the Feature suitable for activation, and meanwhile, the HSS/HLR updates and sets the activation state identification of the Feature suitable for activation as activation and sends a response message to the MME/SGSN;

for example: the corresponding MTC Server/Web/OMC and the like perform activation processing on the Feature suitable for activation (the corresponding Feature suitable for activation can comprise a Feature for theft prevention), and meanwhile, the corresponding HSS/HLR sets the activation state identification update of the Feature suitable for activation as activation and sends a response message to the MME/SGSN;

scheme 2: the MTC Server/Web/OMC and the like transmit the Feature suitable for activation to the MME/SGSN;

for example: the corresponding MTC Server/Web/OMC and the like transmit the Feature suitable for activation (the corresponding Feature suitable for activation can comprise a theft-prevention Feature) to the corresponding MME/SGSN;

in a step 506 of the method,

scheme 2: MME/SGSN transmits the Feature suitable for activation to HSS/HLR;

for example: the corresponding MME/SGSN transmits the appropriate active Feature (the corresponding appropriate active Feature may include a tamper-resistant Feature) to the corresponding HSS/HLR;

in the step 507, the operation is carried out,

for example: the corresponding HSS/HLR sets the activation status identification update of the Feature suitable for activation (the corresponding Feature suitable for activation may comprise the anti-theft Feature) to be active and sends a response message to the MME/SGSN;

Example ten

As shown in fig. 13, a M2M service terminal M10 is taken as an example to explain an M2M service optimization method provided by the embodiment of the present invention. If the M2M service terminal M10 has been registered to a corresponding MME/SGSN, and a Feature supported by the M2M service terminal M10 and a Feature supported by a corresponding MME/SGSN capability, which are registered by the M2M service terminal M10, have been stored in the HSS/HLR to which the M2M service terminal M10 belongs, when an MTC Server/Web/OMC or the like currently serving the M2M service terminal M10 needs to activate a new Feature of the M2M service terminal M10 (the new Feature of the M2M service terminal M10 may be an anti-theft Feature), using the M2M service optimization method provided by the present invention, the specific implementation steps may include:

601, inquiring information of MME/SGSN registered by UE in HSS/HLR by MTC Server/Web/OMC and the like;

for example: waiting for the MTC Server/Web/OMC currently serving the M2M service terminal M10 to query the HSS/HLR to which the M2M service terminal M10 belongs for the information of the MME/SGSN registered by the M2M service terminal M10 (the information of the corresponding MME/SGSN may include information for specifying the MME/SGSN registered by the M2M service terminal M10);

step 602, the HSS/HLR returns the information of MME/SGSN registered by the UE to MTC Server/Web/OMC and the like;

for example: the corresponding HSS/HLR returns the information of the MME/SGSN registered by the M2M service terminal M10 to the corresponding MTC Server/Web/OMC and the like;

step 603, MTC Server/Web/OMC and the like send Feature to be activated to MME/SGSN;

for example: corresponding MTC Server/Web/OMC and the like send the Feature for theft prevention to be activated to MME/SGSN registered by the M2M service terminal M10;

step 604, the MME/SGSN judges whether the Feature required to be activated issued by the MTC Server/Web/OMC and the like can be activated or not according to the Feature supported by the MME/SGSN and/or the Feature supported by the UE;

for example: because the corresponding MME/SGSN has stored the Feature supported by the M2M service terminal M10 registered by the M2M service terminal M10, the MME/SGSN can determine whether the Feature to be activated issued by the MTC Server/Web/OMC and the like can be activated according to the Feature supported by the MME/SGSN capability and the Feature supported by the M2M service terminal M10;

in a step 605 of the method, the step of the method,

assume that 1: if the MME/SGSN judges that the Feature which needs to be activated can be activated, the MME/SGSN can inform the activated Feature to HSS/HLR, MTC Server/Web/OMC and the like;

for example: if both the Feature supported by the MME/SGSN capability and the Feature supported by the M10 of the M2M service terminal can support the anti-theft Feature, the corresponding MME/SGSN can determine that the anti-theft Feature can be activated; then, the corresponding MME/SGSN can inform the anti-theft Feature to the corresponding HSS/HLR and MTCServer/Web/OMC, etc.;

assume 2: if the MME/SGSN judges that the Feature which needs to be activated can not be activated, the MME/SGSN can send the activation failure information of the Feature which can not be activated, the Feature supported by the MME/SGSN capability and/or the Feature supported by the UE, the Feature not supported by the MME/SGSN capability and/or the Feature not supported by the UE to the MTCCerver/Web/OMC and the like;

for example: if the corresponding MME/SGSN capability does not support anti-theft Feature and/or the M2M service terminal M10 does not support anti-theft Feature, the corresponding MME/SGSN can determine that the anti-theft Feature cannot be activated; then, the MME/SGSN may send the activation failure information of the tamper-resistant Feature, the Feature supported by the corresponding MME/SGSN capability and/or the Feature supported by the M2M service terminal M10, and the Feature unsupported by the MME/SGSN capability and/or the Feature unsupported by the UE to the MTC Server/Web/OMC, etc.;

in a step 606 of the method,

for hypothesis 1, the step is: the MTC Server/Web/OMC and the like carry out activation processing on the Feature to be activated, and meanwhile, the HSS/HLR updates and sets the activation state identification of the Feature to be activated as activation and returns a response message to the MME/SGSN;

for example: the corresponding MTC Server/Web/OMC and the like activate the anti-theft Feature, and simultaneously, the corresponding HSS/HLR updates and sets the activation state identification of the anti-theft Feature to be activated and returns a response message to the corresponding MME/SGSN;

for hypothesis 2, the step is: judging whether a Feature suitable for activation exists according to the Feature supported by the MME/SGSN capability uploaded by the MME/SGSN and/or the Feature supported by the UE by the MTC Server/Web/OMC and the like, if so, executing the step 603 again, otherwise, exiting the activation process;

for example: the corresponding MTC Server/Web/OMC and the like judge whether the Feature suitable for activation exists 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, if the Feature suitable for activation exists, the step 603 is executed again, namely, the activation process suitable for the activated Feature is entered; and if the Feature suitable for activation does not exist, the activation process of the Feature for anti-theft is exited.

Those of ordinary skill in the art will understand that: all or part of the processes of the methods for implementing the embodiments may be implemented by a program, which may be stored in a computer-readable storage medium, and when executed, may include the processes of the embodiments of the methods as described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), or the like.

The M2M service optimization apparatus provided in 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 (the corresponding M2M service management entity may include an MTC Server/Web/OMC, etc.).

The following describes specific structures of devices disposed in an M2M service communication entity or an M2M service management entity, respectively, according to embodiments of the present invention, with reference to the accompanying drawings.

M2M service communication entity

As shown in fig. 14, the specific structure of the M2M service optimization apparatus provided in the embodiment of the present invention, which is correspondingly disposed in the M2M service communication entity, may include:

(1) a supported feature acquiring unit 1001 configured to acquire at least one of a feature supported by a terminal and a feature supported by a mobility management unit capability;

specifically, as shown in fig. 15, the corresponding supported feature obtaining unit 1001 may specifically include:

a first supported feature acquiring unit 10011, configured in the MME/SGSN, configured to acquire at least one of a feature supported by the terminal and a feature supported by the mobility management unit capability;

or,

a second supported feature acquiring unit 10012, configured in the HSS/HLR, configured to acquire at least one of a feature supported by the terminal and a feature supported by the mobility management unit capability;

(2) a supported feature sending unit 1002, configured to send, to an M2M service management entity, at least one of a feature supported by the terminal and a feature supported by a mobility management unit capability, which are acquired by the supported feature acquiring unit 1001;

for example, the corresponding supported feature sending unit 1002 may be disposed in the MME/SGSN, or disposed in the HSS/HLR, or both of them are respectively disposed with different optimized feature sending units 3002;

the supported feature sending unit 1002 disposed in the MME/SGSN may send at least one of the feature supported by the terminal and the feature supported by the mobility management unit capability acquired by the first supported feature acquiring unit 10011;

the supported feature transmitting unit 1002 disposed in the HSS/HLR may transmit at least one of the terminal-supported feature acquired by the second supported feature acquiring unit 10012 and the mobility management unit capability-supported feature.

Optionally, as shown in fig. 16, the M2M service optimization apparatus provided in the embodiment of the present invention may further include:

(1) an unsupported feature determining unit 1003, configured to determine an unusable feature according to the feature supported by the terminal and the feature supported by the mobility management unit and the feature subscribed by the user, which are acquired by the supported feature acquiring unit 1001;

wherein, the corresponding unavailable feature refers to a feature not supported by the terminal and/or a feature not supported by the mobility management unit capability among the features already activated or being activated;

for example, the corresponding unsupported feature determining unit 1003 may be disposed in the MME/SGSN, or may be disposed in the HSS/HLR, or different unsupported feature determining units 1003 are disposed in both of them;

the unsupported feature determining unit 1003 disposed in the MME/SGSN may determine the unavailable feature according to the feature supported by the terminal and the feature supported by the mobility management unit acquired by the first supported feature acquiring unit 10011, and the feature subscribed by the user;

the unsupported feature determining unit 1003 disposed in the HSS/HLR may determine the unavailable feature according to the feature supported by the terminal and the feature supported by the mobility management unit acquired by the second supported feature acquiring unit 10012, and the feature subscribed by the user;

(2) an unsupported feature sending unit 1004, configured to send the unavailable feature determined by the unsupported feature determining unit 1003 to the M2M service management entity;

for example: the corresponding unsupported feature sending unit 1004 may be disposed in the MME/SGSN, or may be disposed in the HSS/HLR, or both of them are respectively disposed with different unsupported feature determining units 1003;

the unsupported feature sending unit 1004 disposed in the MME/SGSN may send the unavailable feature determined by the unsupported feature determining unit 1003 disposed in the MME/SGSN to the M2M service management entity;

the unsupported feature transmitting unit 1004 provided in the HSS/HLR may transmit the unavailable feature determined by the unsupported feature determining unit 1003 provided in the HSS/HLR to the M2M service management entity;

specifically, the corresponding unsupported feature sending unit 1004 may execute concurrently with the supported feature sending unit 1002, that is, concurrently send at least one of the features supported by the terminal and the features supported by the mobility management unit capability, which are acquired by the supported feature acquiring unit 1001, and the unavailable features determined by the unsupported feature determining unit 1003 to the M2M service management entity.

Optionally, as shown in fig. 20, the M2M service optimization apparatus provided in the embodiment of the present invention may further include:

(1) a first feature receiving and processing unit 1005, disposed in the MME/SGSN, configured to receive an activatable feature and/or a deactivatable feature, and notify the HSS or the HLR of the activatable feature and/or the deactivatable feature; the HSS or HLR then activates the activatable feature and/or deactivates the deactivatable feature;

the activatable feature refers to a feature supported by both the terminal and the mobility management unit after removing the activated or activating feature from the features subscribed by the M2M service;

wherein, the deactivatable feature refers to a feature not supported by the terminal and/or a feature not supported by the mobility management unit capability among the already activated features of the M2M service;

specifically, as shown in fig. 24, the corresponding first feature reception processing unit 1005 may include:

a first feature receiving and determining processing unit 10051, configured to receive the activatable feature, and determine whether the received activatable feature can be activated according to at least one of the features supported by the UE and the features supported by the MME/SGSN capability, so as to obtain a feature that can be activated and/or a feature that cannot be activated in the activatable feature, and use the feature that cannot be activated as a deactivatable feature; then, the MME/SGSN informs the HSS or the HLR of the activatable feature and/or the deactivatable feature; the HSS or the HLR then activates the activatable feature and deactivates the deactivatable feature;

or,

(2) a second feature receiving and processing unit 1006, disposed in the HSS/HLR, and configured to directly receive an activatable feature and/or a deactivatable feature, and activate the activatable feature and/or deactivate the deactivatable feature;

specifically, as shown in fig. 24, the corresponding second feature reception processing unit 1006 may include:

a second feature receiving and determining processing unit 10061, configured to receive the activatable feature, determine whether the received activatable feature can be activated according to at least one of the features supported by the UE and the features supported by the MME/SGSN, which are stored in the HSS/HLR, to obtain features that can be activated and/or features that cannot be activated in the activatable feature, and use the features that cannot be activated as the deactivatable feature; the HSS/HLR then activates the activatable feature and deactivates the deactivatable feature.

(II) M2M service management entity

As shown in fig. 17, in the M2M service optimization apparatus provided in the embodiment of the present invention, a specific structure of an apparatus correspondingly disposed in the M2M service management entity may include:

(1) a supported feature receiving unit 2001 for receiving at least one of a feature supported by the terminal and a feature supported by the mobility management unit capability;

specifically, as shown in fig. 18, the M2M service optimization apparatus provided in the embodiment of the present invention may further include:

a first supported feature receiving unit 20011, which is arranged in the MTC Server/Web/OMC and the like, and is configured to receive at least one of a feature supported by the terminal and a feature supported by the capability of the mobility management unit;

(2) an activatable feature determining unit 2002, configured to determine an activatable feature according to at least one of the features supported by the terminal and the features supported by the mobility management unit, which are acquired by the supported feature receiving unit 2001, and a feature signed by a user and/or an operation policy of an operator, and activate the activatable feature;

the corresponding activatable feature refers to a feature supported by both the terminal and the mobility management unit after the activated or activating feature is removed from the features subscribed by the user of the M2M service;

specifically, the corresponding activatable feature determining unit 2002 may also be disposed in the MTC Server/Web/OMC, and the like, and determine the activatable feature according to at least one of the features supported by the terminal and the features supported by the mobility management unit, which are acquired by the first supported feature receiving unit 20011, the feature signed by the user and/or the operation policy of the operator, and perform activation processing on the activatable feature.

Optionally, as shown in fig. 19, the M2M service optimization apparatus provided in the embodiment of the present invention may specifically include:

a deactivatable feature determining unit 2003, configured to determine a deactivatable feature according to at least one of the features supported by the terminal and the features supported by the mobility management unit acquired by the supported feature receiving unit 2001, and a user-subscribed feature and/or an operator operating policy, and deactivate the deactivatable feature;

wherein, the corresponding deactivatable feature refers to a feature not supported by the terminal and/or a feature not supported by the mobility management unit capability among the already activated features of the M2M service;

specifically, the corresponding deactivatable feature determination unit 2003 may be provided in the MTC Server/Web/OMC or the like, and may be executed concurrently with the activatable feature determination unit 2002, so as to determine both the deactivatable feature and the activatable feature concurrently.

Optionally, as still shown in fig. 19, the M2M service optimization apparatus provided in the embodiment of the present invention may specifically include:

an unsupported feature receiving unit 2004, configured to receive an unavailable feature, and send the unavailable feature to the activatable feature determining unit 2002 for activatable feature determination processing and/or send the deactivatable feature determining unit 2003 for deactivatable feature determination processing;

specifically, the corresponding unsupported feature receiving unit 2004 may be disposed in the MTC Server/Web/OMC, etc., and executed simultaneously with the supported feature receiving unit 2001, having received the unsupported feature and the supported feature respectively sent by the M2M service communication entity.

Optionally, as still shown in fig. 20, the M2M service optimization apparatus provided in the embodiment of the present invention may further include:

a feature sending unit 2005, disposed in the MTC Server/Web/OMC, and the like, and configured to send the activatable feature determined by the activatable feature determining unit 2002 and/or the deactivatable feature determined by the deactivatable feature determining unit 2003;

for example, the corresponding feature sending unit 2005 may be disposed in an MTC Server/Web/OMC, etc., and is configured to send the activatable feature determined by the activatable feature determining unit 2002 and/or the deactivatable feature determined by the deactivatable feature determining unit 2003 to the M2M service communication entity.

In addition to the foregoing technical solutions, the M2M service optimization apparatus provided in the embodiment of the present invention further includes another similar solution, so that the M2M service management entity knows the optimization solution supported by the UE and/or the MME/SGSN. The specific structure of the devices provided in the respective M2M service communication entity and M2M service management entity of another scheme will be described below.

M2M service communication entity

As shown in fig. 21, the specific structure of the M2M service optimization apparatus provided in the embodiment of the present invention, which is correspondingly disposed in the M2M service communication entity, may include:

(1) a feature determination processing unit 3001, configured to determine, according to at least one of a feature supported by a terminal and a feature supported by a capability of a mobility management unit, and a feature subscribed by a user and/or an operation policy of an operator, an activatable feature and/or a deactivatable feature, and activate the activatable feature and/or deactivate the deactivatable feature;

specifically, as shown in fig. 23, the M2M service optimization apparatus provided in the embodiment of the present invention may further include:

a first feature determining unit 30011, configured in the MME/SGSN, configured to determine an activatable feature and/or an deactivatable feature according to at least one of a feature supported by the terminal and a feature supported by a capability of the mobility management unit, and a feature subscribed by the user and/or an operation policy of an operator;

or,

a second feature determination unit 30012, arranged in the HSS/HLR, is configured to determine an activatable feature and/or an deactivatable feature based on at least one of a feature supported by the terminal and a feature supported by the mobility management unit capability, and a feature subscribed to by the user and/or an operating policy of the operator.

(2) An optimized feature sending unit 3002, configured to send, to the M2M business processing entity, the activatable feature and/or the deactivatable feature determined by the feature determination processing unit 3001;

for example, the corresponding optimized feature sending unit 3002 may be disposed in the MME/SGSN, or disposed in the HSS/HLR, or both of them are respectively disposed 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 deactivatable feature determined by the first feature determining unit 30011 to the M2M service processing entity;

the optimized feature sending unit 3002 provided in the HSS/HLR may send the activatable and/or deactivatable features determined by the second feature determination unit 30012 to the M2M service processing entity.

(II) M2M service management entity

As shown in fig. 22, in the M2M service optimization apparatus provided in the embodiment of the present invention, a specific structure of an apparatus correspondingly disposed in the M2M service management entity may include:

(1) an optimized feature receiving unit 4001 for receiving activatable features and/or deactivatable features;

specifically, as shown in fig. 23, the corresponding optimized feature receiving unit 4001 may specifically include:

a first optimized feature receiving unit 40011, disposed in the MTC Server/Web/OMC, and configured to receive an activatable feature and/or a deactivatable feature;

for example, the usage of the respective first optimized feature receiving unit 40011 may include at least one of:

when the M2M service communication entity sends an activatable feature, the first optimized feature receiving unit 40011 disposed in the MTC Server/Web/OMC, etc. may receive the activatable feature;

when the M2M service communication entity sends the deactivatable feature, the first optimized feature receiving unit 40011 disposed in the MTC Server/Web/OMC, etc. may receive the deactivatable feature;

(2) an optimized feature processing unit 4002, configured to perform activation processing on the activatable feature received by the optimized feature receiving unit 4001 and/or perform deactivation processing on the deactivatable feature;

for example, the usage of the respective optimized feature processing unit 4002 may include at least one of:

when the optimized feature receiving unit 4001 receives an activatable feature, the corresponding optimized feature processing unit 4002 performs activation processing on the activatable feature;

when the optimized feature receiving unit 4001 receives a feature that can be deactivated, the corresponding optimized feature processing unit 4002 deactivates the feature that can be deactivated;

therefore, the implementation of the embodiment of the device enables the M2M service management entity to timely know the optimization scheme supported by the UE and/or the MME/SGSN, and when the Feature subscribed by the user is unavailable, the activatable Feature and the deactivatable Feature can be determined according to the Feature supported by the MME/SGSN capability and/or the Feature supported by the UE, so that the M2M service is optimized.

The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A method for optimizing M2M service is characterized by comprising the following steps:

2. The method of claim 1, further comprising:

determining the unavailable feature according to the feature supported by the terminal, the feature supported by the capability of the mobility management unit and the feature signed by the user; the non-usable feature refers to a feature not supported by the terminal and/or a feature not supported by the mobility management unit capability among the activated or activating features;

sending the unavailable feature to the M2M traffic management entity.

3. The method of claim 1, wherein the obtaining at least one of the terminal-supported features and the mobility management unit capability-supported features comprises:

a mobile management entity MME or a serving general packet radio service technology support node SGSN acquires at least one of a characteristic supported by a terminal and a characteristic supported by the capability of a mobile management unit;

or,

the home subscriber server HSS or the home location register HLR obtains at least one of the features supported by the terminal and the features supported by the mobility management unit capability.

4. The method of claim 3, further comprising:

the MME or the SGSN receives the activatable and/or deactivatable features and informs the HSS or the HLR of the activatable and/or deactivatable features; the HSS or HLR then activates the activatable feature and/or deactivates the deactivatable feature;

or,

the HSS or the HLR directly receives the activatable feature and/or the deactivatable feature and activates and/or deactivates the activatable feature;

wherein, the deactivatable feature refers to a feature not supported by the terminal and/or a feature not supported by the mobility management unit capability among the already activated features of the M2M service.

5. The method of claim 4, further comprising:

the MME or the SGSN receives the activatable features, determines whether the received activatable features can be activated or not according to at least one of the features supported by the terminal and the features supported by the mobility management unit capability, so as to obtain the features which can be activated and/or the features which cannot be activated in the activatable features, and takes the features which cannot be activated as the deactivatable features;

or,

the HSS or the HLR receives the activatable features and determines whether the received activatable features can be activated according to at least one of the features supported by the terminal and the features supported by the mobility management unit, wherein the features supported by the terminal are saved in the features supported by the terminal, so as to obtain the features which can be activated and/or the features which cannot be activated in the activatable features, and the features which cannot be activated are taken as the deactivatable features.

6. A method for optimizing M2M service is characterized by comprising the following steps:

7. The method of claim 6, further comprising:

determining a feature which can be deactivated according to at least one of the features supported by the terminal and the features supported by the mobile management unit capability, the features signed by the user and/or the operation strategy of the operator, and deactivating the feature which can be deactivated; the deactivatable feature refers to a feature not supported by the terminal and/or a feature not supported by the mobility management unit capability among the already activated features of the M2M service.

8. The method of claim 6 or 7, further comprising:

receiving an unavailable feature and determining an activatable feature and/or a deactivatable feature based on the unavailable feature; the non-available feature refers to a feature not supported by the terminal and/or a feature not supported by the mobility management unit capability among features already activated or being activated.

9. The method of claim 6, wherein at least one of the features supported by the receiving terminal and the features supported by the mobility management unit capability comprises:

and the machine communication service Server MTC Server or Internet Web or the operation and maintenance center OMC receives at least one of the characteristics supported by the terminal and the characteristics supported by the capability of the mobility management unit.

10. The method of claim 9, further comprising:

the MTC Server or the Web or the OMC sends the activatable feature and/or the deactivatable feature.

11. A method for optimizing M2M service is characterized by comprising the following steps:

12. The method of claim 11, wherein determining the activatable feature and/or the deactivatable feature 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 subscribed to by the user and/or an operator operating policy comprises:

the MME or the SGSN determines the activatable feature and/or the deactivatable feature according to at least one of the features supported by the terminal and the features supported by the capability of the mobility management unit, the features signed by the user and/or the operation strategy of the operator;

or,

the HSS or the HLR determines the activatable and/or deactivatable features depending on at least one of the features supported by the terminal and the features supported by the mobility management unit capabilities, as well as the features subscribed to by the user and/or the operating policy of the operator.

13. A method for optimizing M2M service is characterized by comprising the following steps:

14. The method of claim 13, wherein receiving the activatable and/or deactivatable feature comprises: the MTC Server or the Web or OMC receives the activatable feature and/or the deactivatable feature.

15. An apparatus for optimizing M2M service, comprising:

16. The apparatus of claim 15, further comprising:

a non-supported feature determining unit, configured to determine a non-usable feature according to the feature supported by the terminal and the feature supported by the mobility management unit acquired by the supported feature acquiring unit, and the feature subscribed by the user; the non-usable feature refers to a feature not supported by the terminal and/or a feature not supported by the mobility management unit capability among the activated or activating features;

an unsupported feature sending unit, configured to send the unavailable feature determined by the unsupported feature determining unit to the M2M service management entity.

17. The apparatus of claim 15, wherein the supported feature obtaining unit comprises:

a first supported feature obtaining unit, configured in the MME or SGSN, for obtaining at least one of a feature supported by the terminal and a feature supported by the mobility management unit capability;

or,

and the second supported feature acquiring unit is arranged in the HSS or the HLR and is used for acquiring at least one of the features supported by the terminal and the features supported by the capability of the mobility management unit.

18. The apparatus of claim 17, further comprising:

the first feature receiving and processing unit is arranged in the MME or the SGSN and used for receiving the activatable features and/or the deactivatable features and informing the HSS or the HLR of the activatable features and/or the deactivatable features; the HSS or HLR then activates the activatable feature and/or deactivates the deactivatable feature;

or,

the second feature receiving and processing unit is arranged in the HSS or the HLR and used for directly receiving the activatable features and/or the deactivatable features and carrying out activation processing on the activatable features and/or deactivation processing on the deactivatable features;

19. The apparatus of claim 18,

a first feature receiving and determining processing unit, disposed in the MME or the SGSN, configured to receive the activatable feature and determine whether the received activatable feature can be activated according to at least one of a feature supported by the terminal and a feature supported by a capability of the mobility management unit, so as to obtain a feature that can be activated and/or a feature that cannot be activated in the activatable feature, and use the feature that cannot be activated as a deactivatable feature;

or,

and the second feature receiving and judging processing unit is arranged in the HSS or the HLR and used for receiving the activatable features, determining whether the received activatable features can be activated according to at least one of the features supported by the terminal and the features supported by the mobility management unit, which are stored in the HSS or the HLR, so as to acquire the features which can be activated and/or the features which cannot be activated in the activatable features, and taking the features which cannot be activated as the deactivatable features.

20. An apparatus for optimizing M2M service, comprising:

21. The apparatus of claim 20, further comprising:

a deactivatable feature determining unit, configured to determine a deactivatable feature according to at least one of the features supported by the terminal and the features supported by the capability of the mobility management unit, which are acquired by the supported feature receiving unit, and a user-subscribed feature and/or an operator operating policy, and deactivate the deactivatable feature; the deactivatable feature refers to a feature not supported by the terminal and/or a feature not supported by the mobility management unit capability among the already activated features of the M2M service.

22. The apparatus of claim 20 or 21, further comprising:

the unsupported characteristic receiving unit is used for receiving the unavailable characteristic and sending the unavailable characteristic to the activatable characteristic determining unit for activatable characteristic determination processing and/or sending the activatable characteristic determining unit for deactivatable characteristic determination processing; the non-available feature refers to a feature not supported by the terminal and/or a feature not supported by the mobility management unit capability among features already activated or being activated.

23. The method of claim 20, wherein the feature enabled receiver unit comprises:

and the first supported feature receiving unit is arranged in the MTC Server or Web or OMC and is used for receiving at least one of the features supported by the terminal and the features supported by the capability of the mobility management unit.

24. The apparatus of claim 23, further comprising:

and the feature sending unit is arranged in the MTC Server or Web or OMC and is used for sending the activatable features determined by the activatable feature determining unit and/or the deactivatable features determined by the deactivatable feature determining unit.

25. An apparatus for optimizing M2M service, comprising:

26. The apparatus of claim 25, wherein the feature determination processing unit comprises:

a first feature determining unit, disposed in the MME or the SGSN, configured to determine an activatable feature and/or an deactivatable feature according to at least one of a feature supported by the terminal and a feature supported by a capability of the mobility management unit, and a feature subscribed by the user and/or an operation policy of an operator;

or,

and the second characteristic determining unit is arranged in the HSS or the HLR and is used for determining the activatable characteristic and/or the deactivatable characteristic according to at least one of the characteristic supported by the terminal and the characteristic supported by the capability of the mobility management unit, the characteristic signed by the user and/or the operation strategy of the operator.

27. An apparatus for optimizing M2M service, comprising:

28. The apparatus of claim 27, wherein the optimized feature receiving unit comprises:

the first optimization feature receiving unit is arranged in the MTC Server or the Web or the OMC and used for receiving the activatable feature and/or the deactivatable feature.