WO2015074177A1

WO2015074177A1 - Machine-to-machine (m2m) system and application, general service entity, and method for setting event priority

Info

Publication number: WO2015074177A1
Application number: PCT/CN2013/087406
Authority: WO
Inventors: 陶源; 于琦; 甄斌
Original assignee: 华为技术有限公司
Priority date: 2013-11-19
Filing date: 2013-11-19
Publication date: 2015-05-28

Abstract

Disclosed in the present invention are a machine-to-machine (M2M) system and application, a general service entity and a method for setting an event priority, wherein the method for setting an event priority is applicable to a machine-to-machine system and comprises: the general service entity receives data information from an application, wherein the data information includes an application strategy or an event priority, the event priority represents a priority of the data information, and the application strategy represents a strategy in which an application sets an event application; the general service entity sets a processing priority of the event represented by the data information according to strategy information, wherein the strategy information includes an event priority or an application strategy, the strategy information also includes application priority information, and the application priority information represents the prioritization of the applications registered in the general service entity performed by the general service entity according to the type of the application. A processing priority of an event is set according to the event priority, the application strategy and the application priority information, so that the general service entity may process events of different applications orderly.

Description

M2M system and application, general service entity, event priority setting method

Technical field

The present invention relates to the field of communications technologies, and in particular, to an M2M system and application, a general service entity, and an event priority setting method.

Say

Background technique

Machine-to-Machine Communications (Μ2Μ) communication is a book

Networked applications and services centered on machine intelligence interaction. By embedding a wireless communication module or a wired communication module and an application processing logic module inside the machine, data communication without manual intervention is realized, and the information needs of the user for monitoring, command scheduling, data acquisition, and measurement are met. The overall goal of the oneM2M standards organization for machine communication is to create open standards for the business layer of M2M communication to facilitate the establishment of a future network that integrates various devices and services, enabling M2M communication services to interoperate and enabling M2M devices to be independent. Realize the sharing of basic services on the network. The M2M system architecture defined by the oneM2M standard mainly includes an Application Entity (AE), a Common Service Entity (CSE), and an Underlying Network Service Entity (NSE). On the M2M communication device specified by the oneM2M standard, the AE and the CSE communicate through the Mca reference point, the CSE communicates through the Mcc reference point, and the CSE communicates with the NSE through the Men reference point. An AE may contain one or more applications. In M2M communication, it is necessary to distinguish the event type for each data in the M2M application, and the priority of the event processing for the receiving CSE. Generally, in each data information sent by the M2M application, an identifier indicating the priority of the event processing is carried, so that the CSE can know the priority of processing the event. However, there is currently no uniform identification standard for the priority of different M2M applications. For example, different types of M2M applications differ in the way they are set and the way they are divided. This In addition, CSE has its own set priorities for different M2M applications. These all result in the CSE not being able to process the information in an orderly manner based on the priority. Summary of the invention

technical problem

In view of the above, the technical problem to be solved by the present invention is that the CSE cannot process the information in an orderly manner according to the priority because the priorities of different M2M applications do not have a unified identification standard.

solution

In order to solve the above technical problem, in a first aspect, the present invention provides a general service entity, including:

a receiving unit, configured to receive data information from an application, where the data information includes an application policy or an event priority, the event priority indicates a priority of the data information, and the application policy indicates the application setting a policy for prioritizing events;

a setting unit, configured to be connected to the receiving unit, configured to set a processing priority of an event represented by the data information according to the policy information, where the policy information includes the event priority or the application policy, The policy information further includes application priority information indicating that the general service entity prioritizes the application that has been registered on the universal service entity according to an application type.

With reference to the first aspect, in a first possible implementation, the general service entity further includes: an analyzing unit, connected to the setting unit, configured to analyze historical data and/or the data information, Obtain analytical information;

The policy information also includes the analysis information.

With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner, the method further includes: The processing unit is connected to the setting unit, and is configured to process the event in an orderly manner according to the processing priority.

In combination with the first aspect or the first or second possible implementation manner of the first aspect, in a third possible implementation manner, the method further includes:

And a sending unit, configured to be configured to send, to the other general service entity, a processing message according to the processing priority, where the processing message includes an event represented by the data information and the processing priority.

With reference to the first aspect, or any one of the first to the third possible implementation manners of the first aspect, the fourth possible implementation manner further includes an update unit,

The receiving unit is further configured to receive a service policy from another general service entity, wherein the other general service entity has been registered on the universal service entity, the service policy indicating the other general service entity setting The strategy used to prioritize the application;

The update unit is connected to the receiving unit and the setting unit, and is configured to update the policy information according to the service policy.

With reference to the first aspect, or any one of the possible implementation manners of the first to fourth possible implementation manners of the first aspect, in a fifth possible implementation, the method further includes a registration unit and a determining unit, where the receiving The unit is further configured to receive creation request information from the application;

The registration unit is connected to the receiving unit, and configured to complete registration of the application in the universal service entity according to the creation request information;

The determining unit is connected to the registration unit, and configured to determine, according to registration information of the application, a type of the application;

The determining unit is further configured to: obtain the application priority information according to the type of the application;

The sending unit is further configured to send response information to the application, where the response information includes the application priority information. In a second aspect, the present invention provides an application comprising:

a first sending unit, configured to send, to the universal service entity, creation request information, where the creation request information includes an identifier of the request acquisition policy;

a receiving unit, configured to receive, by the first sending unit, a response information, where the response information includes application priority information, where the application priority information indicates that the universal service entity is used according to an application. a type prioritization of the application that has been registered on the generic service entity;

a setting unit, configured to be connected to the receiving unit, configured to set a processing priority of the event for an event according to the policy information, where the policy information includes the response information, and the policy information further includes the An event priority or an application policy of the application, the event priority indicating a priority set by the application for the event, the application policy indicating a policy for the application to set the event priority.

With reference to the second aspect, in a first possible implementation, the application further includes: a second sending unit, connected to the setting unit, configured to send a processing message to the universal service entity or another universal service entity, The processing message includes the processing priority to enable the general service entity or other general service entity to process the event in an orderly manner according to the processing priority.

In a third aspect, the present invention provides a machine to machine system comprising:

At least one application as described in any one of the second aspect and the second aspect; and

At least one general service entity as described in any one of the third aspect and the third aspect.

In a fourth aspect, the present invention provides an event priority setting method for a machine-to-machine system, including:

The universal service entity receives data information from the application, where the data information includes an application policy Or an event priority, the event priority indicates a priority of the data information, and the application policy indicates a policy that the application sets the event priority;

The general service entity sets the processing priority of the event represented by the data information according to the policy information, where the policy information includes the event priority or the application policy, and the policy information further includes an application priority. Information, the application priority information indicating that the general service entity prioritizes the application that has been registered on the universal service entity according to an application type.

With reference to the fourth aspect, in a first possible implementation, before the common service entity sets the processing priority of the event represented by the data information according to the policy information, the method further includes: The historical data and/or the data information are analyzed to obtain analytical information;

The policy information also includes the analysis information.

With reference to the fourth aspect, in a second possible implementation, after the general service entity sets the processing priority of the event indicated by the data information according to the policy information, the method further includes: the universal service entity according to the The processing priority processes the events in an orderly manner.

With reference to the fourth aspect or any one of the possible implementation manners of the first or the second possible implementation manner of the fourth aspect, in a third possible implementation manner, the universal service entity is configured according to the policy information After the processing priority of the event represented by the data information, the method further includes:

The universal service entity sends a processing message to other general service entities in accordance with the processing priority, wherein the processing message includes an event represented by the data information and the processing priority.

With reference to the fourth aspect or any one of the first to third possible implementation manners of the fourth aspect, in a fourth possible implementation manner, the universal service entity is configured according to the policy information Before the processing priority of the event represented by the data information, the method further includes:

The universal service entity receives a service policy from another general service entity, wherein the universal service entity has been registered with the other general service entity, the service policy indicating the other communication The policy used by the service entity to set the priority of the application;

The universal service entity updates the policy information according to the service policy.

In a fifth aspect, the present invention provides an event priority setting method for a machine-to-machine system, including:

The application sends the creation request information to the general service entity, where the creation request information includes an identifier of the request acquisition policy;

The application receives response information from the universal service entity, where the response information includes application priority information, and the application priority information indicates that the universal service entity has registered on the universal service entity according to an application type. Prioritization of the application;

The application sets the processing priority of the event for an event according to the policy information, where the policy information includes the response information, and the policy information further includes an event priority or an application policy, where the event takes precedence. The level indicates a priority set by the application for the event, and the application policy indicates a policy for the application to set the event priority.

With reference to the fifth aspect, in a first possible implementation, after the application sends the creation request information to the universal service entity, the method further includes:

The universal service entity completes registration of the application in the universal service entity according to the creation request information;

The general service entity determines the type of the application according to the registration information of the application; the universal service entity acquires the application priority information according to the type of the application. With reference to the fifth aspect, or the first possible implementation manner of the fifth aspect, in a second possible implementation manner, before the application sends the creation request information to the universal service entity, the method further includes: the universal service entity The other general service entity receives the service policy, wherein the general service entity has been registered on the other general service entity, and the service policy indicates the other With reference to the fifth aspect or any one of the possible implementation manners of the first or the second possible implementation manner of the fifth aspect, in a third possible implementation manner, the application is based on the policy information After the event sets the processing priority of the event, it also includes:

The application sends a processing message to the universal service entity, wherein the processing message includes the processing priority to enable the universal service entity to process the event in an orderly manner according to the processing priority.

Beneficial effect

The event priority setting in the embodiment of the present invention, for events of different applications, comprehensively considering the event priority, the application policy, and the application priority information, setting the processing priority of the event, so that the general service entity can process the orderly Events for different applications.

Further features and aspects of the present invention will become apparent from the Detailed Description of the Drawing. DRAWINGS

The accompanying drawings, which are incorporated in FIG

Figure la shows the architecture of the M2M system;

Figure lb shows a deployment scenario diagram supported by M2M;

Figure 1c is a block diagram showing the structure of a general service entity according to the first embodiment of the present invention;

2 is a block diagram showing the structure of a general service entity according to Embodiment 2 of the present invention;

3 is a block diagram showing the structure of an application according to Embodiment 3 of the present invention;

4 is a block diagram showing the structure of a machine-to-machine system according to Embodiment 4 of the present invention;

5 is a block diagram showing the structure of an event priority setting apparatus according to Embodiment 5 of the present invention; FIG. 6 is a flowchart showing an event priority setting method according to Embodiment 6 of the present invention; A flowchart of the event priority setting method of Example 7; FIG. 8 is a flowchart showing an event priority setting method according to Embodiment 8 of the present invention; FIG.

FIG. 9 is a flow chart showing an event priority setting method according to Embodiment 9 of the present invention. detailed description

Various exemplary embodiments, features, and aspects of the invention are described in detail below with reference to the drawings. The same reference numerals in the drawings denote the same or similar elements. The various aspects of the embodiments are shown in the drawings, and the drawings are not necessarily drawn to scale unless otherwise indicated.

The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustrative." Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous.

Further, in order to better illustrate the invention, numerous specific details are set forth in the Detailed Description. Those skilled in the art will appreciate that the invention may be practiced without some specific details. In other instances, well-known methods, means, components, and circuits are not described in detail to facilitate the invention.

Figure la shows an architecture diagram of the M2M system. As shown in Figure la, on the M2M device node, it may include an Application Entity (AE), a Common Services Entity (CSE), and an underlying network service entity. (Underlying Network Service Entity, NSE). Communication between the AE and the CSE can be made through the Mca reference point; communication between the CSE can be made through the Mcc reference point; communication between the CSE and the NSE can be made through the Men reference point. In each M2M device node, a CSE can be represented as a collection of Common Services Function (CSF) modules such as a Session Management module, a Registration module, and a Device Management module.

Figure lb shows a deployment scenario diagram supported by M2M. As shown in Figure lb, it includes an Application Dedicated Node, an Application Service Node, an Middle Node, and an Infrastructure Node. Infrastructure Node) Four functional entities, for each node, it can be a functional entity containing one or more M2M applications. It can also be a functional entity that contains one CSE and any number of M2M applications (including 0). As shown in Figure lb, instances 1 and 2 contain only application, called Application Dedicated Node; and instance 3 and instance 4 contain both application and CSE, called Application Service Node. In this scenario, the Application Dedicated Node and the Application Service Node can communicate with the Middle Node, or communicate with the Infrastructure Node through the Middle Node (Example 2, Example 3), or directly with the Infrastructure without the Middle Node. Node communicates (Example 1, Example 4).

Example 1

Figure 1c shows a block diagram of a general service entity according to a first embodiment of the present invention. As shown in FIG. 1c, the universal service entity 100 can mainly include:

The receiving unit 110 is configured to receive data information from an application, where the data information is related to the application, where the data information includes an application policy or an event priority, and the event priority indicates a priority of the data information, The application policy represents a policy in which the application sets the event priority.

Specifically, as shown in FIG. 1a and FIG. 1b, the receiving unit 110 of the universal service entity 100 can communicate with an application through an Mca reference point, where each application entity can include one or more applications, and different applications can generate different The event requires the generic service entity 100 to process according to the corresponding processing priority. When there is an event in the application that needs to be processed, the receiving unit 110 may receive data information from the application through the Mca reference point, and the data information may include an application policy or an event priority. The event priority indicates the prioritization of the data information by the application itself, and the application policy indicates the policy used by the application to set the event priority.

The setting unit 130 is connected to the receiving unit 110, and is configured to set a processing priority of an event represented by the data information according to policy information,

The policy information includes the event priority or the application policy, and the policy information further includes application priority information, where the application priority information indicates that the universal service entity is based on The application type prioritizes the applications that have been registered on the generic service entity.

Specifically, after receiving the data information by the receiving unit 110, the setting unit 130 may set the processing priority of the event according to the policy information, that is, the priority used when processing the event, for subsequent priority according to the processing. Levels handle events of different applications in an orderly manner. The policy information may include an event priority or an application policy in the received data information, and may also include application priority information. In the general service entity 100, the type of the application that has been registered to it is recognized, and the applications registered to it can be prioritized according to the types of different applications, that is, the application priority information, and the application priority information can be It is saved in the generic service entity 100.

In a possible implementation, the universal service entity 100 may further include an analyzing unit 150, connected to the setting unit 130, for analyzing the historical data and/or the data information to obtain the analysis information. .

Specifically, the general service entity 100 may analyze the historical data processed by the analysis unit 150 and the data currently needed to be processed, or analyze the data information that needs to be processed to obtain the analysis information. The analysis information may also be included in the above policy information, so that the processing priority of the event setting event may be combined with the historical data and the data currently to be processed, so that the event can be processed more accurately according to the processing priority.

For example, in a tire pressure detection system, the sensor can detect tire pressure values at different times. For this application, the generic service entity itself sets a low-voltage warning message with a high priority when the sensor for tire pressure detection detects a low air pressure, and a periodic air pressure report information has a low priority. However, when the application sets its own air pressure value less than M, the priority of issuing the low-voltage warning information is lower than the priority when the air pressure value is less than N, and the low-voltage warning information is issued, where M is greater than N. If the general service entity analyzes the historical barometric pressure value and the current barometric pressure value and finds that the obtained tire pressure value shows a rapid decline trend, or the general service entity analyzes the current barometric pressure value and finds that the value is close to the low air pressure threshold value, It sets a higher processing priority.

In a possible implementation manner, the universal service entity 100 may further include: The processing unit 170 is connected to the setting unit 130, and is configured to process the event in an orderly manner according to the processing priority.

Specifically, as shown in Figure lb, the application can communicate with the target generic service entity directly through the Mca reference point. When the general service entity 100 is the target general service entity that processes the event, the universal service entity 100 may further include a processing unit 170. After the receiving unit 110 receives the data information, the setting unit 130 sets the processing of the event according to the policy information. Priority, processing unit 170 can process the event in an orderly manner according to processing priority.

In a possible implementation manner, the universal service entity 100 may be a local general entity, in which case the local general service entity may sequentially send the processing priority and data information to the processing priority according to the processing priority through the Mcc reference point to The target general service entity, such that the target general service entity can process events of different applications in an orderly manner according to the processing priority.

The general service entity of the embodiment, for events of different applications, comprehensively considers the event priority, the application policy, the application priority information, and the analysis information, and sets the processing priority of the event by setting the unit, so that the target general service entity can Ordering events of different applications in an orderly manner avoids the problem that the target general service entity cannot process events in an orderly manner because the priorities of different applications are not uniformly identified.

Example 2

2 is a block diagram showing the structure of a general service entity according to Embodiment 2 of the present invention. The components in Fig. 2 having the same reference numerals as those of Fig. 1 have the same functions, and a detailed description of these components will be omitted for the sake of brevity.

As shown in FIG. 2, the main difference between the generic service entity 200 shown in FIG. 2 and the generic service entity 100 shown in FIG. 2 is that the universal service entity 200 may further include:

The sending unit 210 is connected to the setting unit 130, and is configured to send a processing message to other general service entities according to the processing priority, wherein the processing message includes an event represented by the data information and the processing priority.

Specifically, as shown in FIG. 1b, the application can be performed by the intermediate node and the target general service entity. Communication. When the general service entity 200 is a local general service entity, the universal service entity 200 may further include a sending unit 210. After the receiving unit 110 receives the data information, the setting unit 130 sets the processing priority of the event according to the policy information, and sends the The unit 210 may sequentially send the processing message to other general service entities according to the processing priority, and the processing message may include an event and a processing priority represented by the data information. The other general service entities mentioned above may be local general service entities or target general service entities. If it is a local general service entity, it can be combined with the policy information of the local general service entity itself to set a new processing priority for the target general service entity to process the event in an orderly manner; if it is a target general service entity, the target general service can be The processing unit of the entity processes the event in an orderly manner according to the processing priority.

In a possible implementation manner, the universal service entity may include a local universal service entity and a target general service entity, and the target general service entity may directly communicate with the application through the Mca reference point, or may pass the Mcc reference point and the local universal service entity. Communication is performed, and the local general service entity communicates with the application through the Mca reference point, that is, indirectly communicates with the application through at least one local general service entity.

As shown in FIG. 2, in the case that the universal service entity 200 is a local universal service entity, the receiving unit 110 may be further configured to receive a service policy from other general service entities, where the other general service entities are already in the Registered on a generic service entity that represents the policy employed by the other generic service entity to set the priority of the application. Further, the generic service entity 200 may further include:

The updating unit 230 is connected to the receiving unit 110 and the setting unit 130, and is configured to update the policy information according to the service policy.

Specifically, the universal service entity 200 shown in FIG. 2a may be a local universal service entity. In this case, the receiving unit 110 of the universal service entity 200 may also receive a service policy from other general service entities, where other common service entities have Registered on the generic service entity 200, the business policy indicates that other general service entities themselves set policies for the priority of the application. Update unit 230 The policy information can be updated in conjunction with the above business policy. In this way, when the general service entity 200 subsequently sets the processing priority, the service policy can be taken into consideration, and the common service entity cannot be unified because the priority set and the processing priority set by the other general service entities are not unified. The problem of ordering the event.

In a possible implementation manner, the universal service entity 200 may further include: a registration unit 240 and a determining unit 250,

The receiving unit 110 may be further configured to receive creation request information from the application; the registration unit 240 is connected to the receiving unit 110, and configured to complete the application in the universal service according to the creation request information. Registration in the entity;

The determining unit 250 is connected to the registration unit 240, and configured to determine a type of the application according to the registration information of the application;

The determining unit 250 is further configured to acquire the application priority information according to the type of the application;

The sending unit 210 is further configured to send response information to the application, where the response information includes the application priority information.

Specifically, in the M2M system, the application can be registered in the general service entity 200 before communicating with the general service entity 200. By the creation request information of the application received by the receiving unit 110, the general service entity 200 can be instructed to complete the registration of the application in the general service entity 200 through the registration unit 240. After the registration is completed, the determining unit 250 may determine the type of the application according to the registration information of the application, and further determine the application priority information according to the type of the application. The sending unit 210 can transmit the application priority information to the application in response information for setting the processing priority of a certain event of the application.

The general service entity of the embodiment sets the event priority, the application policy, the application priority information, and the analysis information for the events of different applications, and sets the processing priority of the event according to the setting unit, according to different deployment scenarios of the M2M. The processing message can be sent to the other by the sending unit a general service entity for orderly processing events of different application entities; for a local general service entity, the receiving unit can also receive a service policy, and further consider the impact of the business policy when setting the processing priority to ensure the general service Entities can process events of different applications in an orderly manner.

Example 3

FIG. 3 is a block diagram showing the structure of an application according to Embodiment 3 of the present invention. In an M2M system, each application entity may include one or more applications, and different applications may generate different events that need to be processed by the general service entity according to the corresponding processing priority. As shown in FIG. 3, the application 300 can mainly include:

The first sending unit 310 is configured to send creation request information to the general service entity, where the creation request information includes an identifier of the request acquisition policy.

Specifically, the first sending unit 310 of the application 300 may send the creation request information to the general service entity for the application 300 to complete the registration in the general service entity. After the registration is completed, the application 300 may obtain the general service entity from the general service entity. A policy in which the priority of the application is set for the subsequent processing priority of the event. The creation request information may include an identifier of the request acquisition policy.

The receiving unit 330 is connected to the first sending unit 310, and is configured to receive response information from the universal service entity, where the response information includes application priority information, where the application priority information indicates the universal service entity The prioritization of the applications that have been registered on the generic service entity is based on the type of application.

Specifically, after the first sending unit 310 sends the creation request information, the universal service entity confirms that the application 300 has been authenticated in the universal service entity, may create a registration resource for the application 300, and identify the type of the application 300 according to the registration information of the application 300. Get the corresponding application priority information to reply. The receiving unit 330 of the application 300 can receive the response information returned by the general service entity, and the application priority information can be included in the response information.

Since the application 300 and the generic service entity have not yet started processing an event, they are ringing The analysis information is not included in the information, but in one possible implementation, the general service entity may save the historical data of the previous application 300 or the general service entity may share the analysis information of the other general service entity for the application 300, such that The above analysis information may be included in the response information. The application 300 may also consider the analysis information when setting the processing priority of the event.

The setting unit 350 is connected to the receiving unit 330, and is configured to set a processing priority of the event for an event according to the policy information, where the policy information includes the response information, and the policy information further includes An event priority or an application policy of the application, the event priority indicating a priority set by the application for the event, and the application policy indicating a policy for the application to set the event priority.

Specifically, the setting unit 350 may set the processing priority of the event according to the policy information, where the policy information may include the response information and the event priority or the application policy of the application 300. For the application priority information, if the application 300 has been authenticated in the general service entity, the application 300 can obtain application priority information from the general service entity; for the application policy and event priority, the application 300 itself can be known.

Further, the application 300 may further include:

a second sending unit 370, connected to the setting unit 350, configured to send a processing message to the universal service entity or other general service entity, where the processing message includes the processing priority, so that the universal service entity Or other general service entity can process the event in an orderly manner according to the processing priority.

Specifically, after the event priority setting of the event, if the application has an event to be processed, the information and processing priority of the event may be directly sent to the general service entity, so that the general service entity can process the event in an orderly manner.

In a possible implementation manner, if the foregoing general service entity is a local general service entity, after receiving the event information and processing priority of the application 300, the second sending unit 370 may send the event information and the processing priority to the target. General service entity, target general service entity The processing priority processes the event in an orderly manner; the event information and processing priority may also be sent to other local general service entities, which are sent to the target general service entity in an orderly manner by other local general service entities. If the general service entity is a target general service entity, the second sending unit 370 can reply the event information and the processing priority to the target general service entity, and the target general service entity processes the event in an orderly manner according to the processing priority.

In a possible implementation manner, if the foregoing universal service entity is a local universal service entity, the local universal service entity may receive the service policy of the other general service entity before receiving the creation request information, and update the policy information according to the service policy. In this way, when the application 300 sets the processing priority through the setting unit 350, the service policy can be taken into consideration, and the common service entity is avoided because the priority set by the other general service entities and the processing priority are not unified. The problem of the event could not be processed in an orderly manner.

In the application of the embodiment, the application priority information of the application is obtained from the general service entity by using the first sending unit and the receiving unit, and the setting unit sets the processing priority according to the policy information, so that the target general service entity can have the processing priority according to the processing priority. Sequentially handling events of different applications avoids the problem that the target general service entity cannot process the events in an orderly manner because the priorities of different applications are not uniformly identified.

Example 4

4 is a block diagram showing the structure of a machine-to-machine system according to a fourth embodiment of the present invention. As shown in Figure 4, the machine-to-machine system 400 can primarily include:

At least one application 410 as described in the third embodiment above;

At least one general service entity 430 as described in the first embodiment and the second embodiment above.

Specifically, in a machine-to-machine (M2M) system, each application entity may include one or more applications, and different applications may generate different events that require the general service entity to process according to the corresponding processing priority. When the generic service entity 430 processes an event of an application 410, it needs to obtain the processing priority of the event in order to process the event in an orderly manner. On the one hand, due to the M2M system There are many types of applications, and different types of applications use different policies and division methods when setting event priorities. Thus, there is no uniform standard for the receiving general service entities to identify. For example, in tire pressure detection, the sensor will issue a high-priority low-pressure warning message when low air pressure is detected, and the periodic air pressure report information is low-priority information, but the application of different tire pressure detection sensors to the low-pressure door The limits may be set differently so that the generic service entity does not recognize the priority of the event after receiving the data message. On the other hand, the generic service entity itself has different priorities for different applications, so that after the general service entity receives the data information, it cannot determine which priority to handle the event.

In response to the above problem, it is necessary to determine the processing priority of the event before processing the events of different applications.

In a possible implementation manner, referring to the related description in the foregoing Embodiment 3, the application 410 may send the creation request information to the universal service entity 430, requesting to obtain the application in the universal service entity 430 from the universal service entity 430. Applying the priority information, after receiving the response information of the universal service entity 430 including the application priority information, the application 410 may set the processing priority of the event according to the policy information, for the subsequent general service entity to orderly according to the processing priority. Handle events. For a specific example of the policy information, refer to the related description in the third embodiment.

In a possible implementation manner, referring to the related description in Embodiment 1 and Embodiment 2, the universal service entity 430 can receive the data information sent by the application 410. If the application 410 is already registered in the universal service entity 430, the universal service entity 430 can set the processing priority of the event according to the policy information, so that the subsequent general service entity processes the event in an orderly manner according to the processing priority. For a specific example of the policy information, refer to the related description in the first embodiment.

Further, in a case where the general service entity 430 is a local general service entity, the universal service entity 430 may receive the service policy of other general service entities and update the policy information in conjunction with the service policy. Other common service entities have their own prioritization methods and policies for different application events. Combining business policies to update policy information and setting processing priorities can further avoid The priority set by other common service entities themselves causes problems that cannot handle events in an orderly manner.

The machine-to-machine system, the application, and the general service entity of the embodiment can set the processing priority of the event according to the acquired policy information, so that the target general service entity can process the events of different applications in an orderly manner, thereby avoiding different applications. Priority does not have a problem with the target generic service entity that cannot be processed in an orderly manner.

Example 5

Fig. 5 is a block diagram showing the structure of an event priority setting device according to a fifth embodiment of the present invention. The event priority setting device 500 may be a host server having a computing capability, a personal computer PC, or a portable computer or terminal that can be carried. The specific embodiment of the present invention does not limit the specific implementation of the computing node.

The event priority setting means 500 includes a processor 510, a communications interface 520, a memory 530, and a bus 540. The processor 510, the communication interface 520, and the memory 530 complete communication with each other via the bus 540.

Communication interface 520 is for communicating with network devices, such as virtual machine management centers, shared storage, and the like.

The processor 510 is for executing a program. The processor 510 may be a central processing unit CPU, or an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention.

The memory 530 is used to store files. Memory 530 may include high speed RAM memory and may also include non-volatile memory, such as at least one disk memory. Memory 530 can also be a memory array. Memory 530 may also be partitioned, and the blocks may be combined into a virtual volume according to certain rules.

In a possible implementation, the above program may be a program code including computer operating instructions. This program can be used to:

In a possible implementation, before the general service entity sets the processing priority of the event represented by the data information according to the policy information, the method further includes:

The general service entity analyzes historical data and/or the data information to obtain analysis information;

The policy information also includes the analysis information.

In a possible implementation, after the general service entity sets the processing priority of the event represented by the data information according to the policy information, the method further includes:

The generic service entity processes the event in an orderly manner according to the processing priority.

The universal service entity receives a service policy from another general service entity, wherein the universal service entity has been registered with the other general service entity, the service policy indicating the other communication In a possible implementation manner, the program is specifically used to:

In a possible implementation, after the application sends the creation request information to the universal service entity, the method further includes:

The general service entity determines the type of the application according to the registration information of the application; the universal service entity acquires the application priority information according to the type of the application. In a possible implementation, before the application sends the creation request information to the universal service entity, the method further includes:

The universal service entity receives a service policy from other general service entities, wherein the universal service entity has been registered with the other general service entity, the service policy indicating that the other general service entity sets the application priority The strategy adopted by the level;

The general service entity updates the application priority information according to the service policy.

In a possible implementation, after the application sets the processing priority of the event for an event according to the policy information, the method further includes:

The application sends a processing message to the universal service entity, wherein the processing message includes The processing priority is such that the generic service entity can process the event in an orderly manner according to the processing priority.

One of ordinary skill in the art will appreciate that the various exemplary units and algorithm steps in the embodiments described herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can select different methods for a particular application to achieve the described functionality, but such implementation should not be considered to be beyond the scope of the present invention.

If the function is implemented in the form of computer software and sold or used as a stand-alone product, it may be considered to some extent that all or part of the technical solution of the present invention (for example, a part contributing to the prior art) is It is embodied in the form of computer software products. The computer software product is typically stored in a computer readable non-volatile storage medium, including instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform all of the methods of various embodiments of the present invention. Or part of the steps. The foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Example 6

FIG. 6 is a flow chart showing an event priority setting method according to Embodiment 6 of the present invention. As shown in FIG. 6, the event priority setting method may mainly include:

Step S610: The universal service entity receives the data information from the application, where the data information includes an application policy or an event priority, the event priority indicates a priority of the data information, and the application policy indicates the application setting The policy of the event priority.

Specifically, as shown in FIG. 1a and FIG. 1b, the general service entity can communicate with the application through the Mca reference point, where each application entity can include one or more applications, and different applications can generate different events and require common services. The entity 100 processes according to the corresponding processing priority. When there is an event in the application that needs to be processed, the generic service entity can use the Mca reference point from the application. Receiving data information, which may include an application policy or an event priority. The event priority indicates the prioritization of the data information by the application itself, and the application policy indicates the strategy used when the application sets the event priority.

Step S630: The universal service entity sets a processing priority of the event represented by the data information according to the policy information.

The policy information includes the event priority or the application policy, and the policy information further includes application priority information.

The application priority information indicates that the general service entity prioritizes the applications that have been registered on the universal service entity according to an application type.

Specifically, after receiving the data information, the general service entity may set a processing priority of the event according to the policy information, that is, a priority used when processing the event, for subsequent orderly according to the processing priority. Handle events for different applications. The policy information may include an event priority or an application policy in the received data information, and may also include application priority information. In a generic service entity, it has a type of awareness of the application that has been registered to it, and has its own prioritization for each application registered to it, through the recognition of the application type and its own priority to the application of the type. The division is the application priority information of the application, and the application priority information can be saved in the general service entity.

In a possible implementation, before the step S630, the event priority setting method may further include:

Step S620: The general service entity analyzes the historical data and/or the data information to obtain analysis information, where the policy information further includes the analysis information.

Specifically, the general service entity may analyze the historical data processed and the data that needs to be processed, and may also analyze the current data information that needs to be processed to obtain the analysis information. The analysis information may also be included in the foregoing policy information, so that the processing priority of the event may be set in combination with the historical data and the data currently needed to be processed, so that the processing priority may be more accurately determined according to the processing priority. Handle events.

In a possible implementation, after the step S630, the event priority setting method may further include:

Step S650: The universal service entity processes the event in an orderly manner according to the processing priority. Specifically, as shown in Figure lb, the application can communicate with the target generic service entity directly through the Mca reference point. When the general service entity is the target general service entity that processes the event, after receiving the data information, the universal service entity may set the processing priority of the event according to the policy information, and process the order according to the processing priority. event.

In a possible implementation manner, the general service entity may be a local general entity, in which case the local general service entity may sequentially send the processing priority and data information to the target according to the processing priority through the Mcc reference point. A generic service entity, such that the target generic service entity can process events of different applications in an orderly manner according to processing priorities.

In the event priority setting method of the embodiment, the event priority, the application policy, the application priority information, and the analysis information are comprehensively considered for events of different applications, and the processing priority of the event is set by the policy information, so that the target is universally used. The service entity can process the events of different applications in an orderly manner, and avoids the problem that the target general service entity cannot process the events in an orderly manner because the priorities of different applications are not uniformly identified. Example 7

FIG. 7 is a flow chart showing an event priority setting method according to Embodiment 7 of the present invention. The same steps in Fig. 7 as those in Fig. 6 have the same functions, and detailed descriptions of these steps are omitted for the sake of brevity.

As shown in FIG. 7, the main difference between the event priority setting method shown in FIG. 7 and the event priority setting method shown in FIG. 6 is that, before step S630, the event priority setting method may further include: S710. The universal service entity sends a processing message to other general service entities according to the processing priority, where the processing message includes an event represented by the data information and the processing priority.

Specifically, as shown in FIG. 1b, the application can communicate with the target general service entity through the intermediate node. When the general service entity is a local general service entity, after receiving the data information, the general service entity may set the processing priority of the event according to the policy information, and may send the processing message to the other order according to the processing priority. The general service entity, the processing message may include the event and processing priority represented by the data information. The other general service entities mentioned above may be local general service entities or target general service entities. If it is a local general service entity, it can be combined with the policy information of the local general service entity itself to set a new processing priority for the target general service entity to process the event in an orderly manner; if it is a target general service entity, the target general service can be The processing unit of the entity processes the event in an orderly manner according to the processing priority.

In a possible implementation manner, the universal service entity may include a local universal service entity and a target general service entity, and the target general service entity may directly communicate with the application through the Mca reference point, or may pass the Mcc reference point and the local universal service entity. Communicate, and then the local general service entity communicates with the application through the Mca reference point, that is, through at least one local universal service. The universal service entity has been registered with the other general service entity, the service policy indicating a policy employed by the other general service entity to set the priority of the application.

Specifically, the general service entity may be a local general service entity, in which case the general service entity may also receive service policies from other general service entities, where other general service entities have been registered on the general service entity, and the service policy indicates other The generic service entity itself sets the policy adopted by the priority of the application entity.

Step S750: The universal service entity updates the policy information according to the service policy. Specifically, the general service entity may update the policy information in combination with the foregoing service policy. In this way, when the general service entity subsequently sets the processing priority, the service policy can be taken into consideration, and the common service entity cannot be in an orderly manner because the priority set by the general service entity itself and the processing priority are not unified. Handle the problem with this event.

The event priority setting method of the embodiment, for the events of different applications, comprehensively considering the event priority, the application policy, the application priority information, and the analysis information, setting the processing priority of the event, according to different deployment scenarios of the M2M, The service entity may send the processing message to other general service entities in an orderly manner to process the events of different applications in an orderly manner; for the local general service entity, it may also receive the service policy, and further consider the service when setting the processing priority. The impact of the policy to ensure that the generic service entity can process events of different application entities in an orderly manner.

Example 8

FIG. 8 is a flow chart showing an event priority setting method according to Embodiment 8 of the present invention. As shown in FIG. 8, the event priority setting method may mainly include:

Step S810: The application sends the creation request information to the universal service entity, where the creation request information includes an identifier of the request acquisition policy.

Specifically, the application may send the creation request information to the universal service entity by using the Mca reference point, and obtain the application priority information of the application of the type in the general service entity from the universal service entity, and the processing for the subsequent setting event is prioritized. level. The request information may include a request Get the ID of the policy.

Step S850: The application receives response information from the universal service entity, where the response information includes application priority information, where the application priority information indicates that the universal service entity is already in the universal service according to an application type. The prioritization of the application registered on the entity.

In a possible implementation, after step S810, the method may further include:

Step S820: The universal service entity completes registration of the application in the universal service entity according to the creation request information.

Step S830: The universal service entity determines the type of the application according to the registration information of the application.

Step S840: The universal service entity acquires the application priority information according to the type of the application.

Specifically, after the application sends the creation request information, after confirming that the application has been authenticated in the universal service entity, the universal service entity may complete registration of the application in the universal service entity according to the creation request information, and create a registration resource for the application, the universal service. The entity may also identify the type of the application according to the registration information of the application, and obtain the corresponding application priority information according to the above type to reply. The application can receive the response information returned by the general service entity, and the application priority information can be included in the response information.

Since the application and the general service entity have not started processing of an event, the analysis information is not included in the response information, but in one possible implementation, the general service entity may save historical data or general service of the previous application. The entity may share the analysis information of the other general service entity for the application, such that the analysis information may be included in the response information. The analysis information can also be considered when applying the processing priority of the event.

Step S870: The application sets a processing priority of the event for an event according to the policy information, where the policy information includes the response information and an event priority or an application policy of the application, where the event The priority indicates the priority set by the application for the event, and the response A policy is used to indicate that the application sets the priority of the event.

Specifically, the application may set the processing priority of the event according to the policy information. For the policy information, refer to the related description of the event priority setting method in the foregoing sixth embodiment. For the application priority information, if the application has been authenticated in the general service entity, the application may obtain the priority division information of the application of the generic service entity from the general service entity, that is, the application priority information; Priority, the application itself can know; for analyzing information, can pass

The Mca reference point is obtained from the generic service entity. After the event priority setting of the event, if the application has an event to be processed, the information and processing priority of the event may be directly sent to the general service entity, so that the general service entity can process the event in an orderly manner.

In a possible implementation, before the step 810, the event priority setting method may further include:

Step S880, the application sends a processing message to the universal service entity or other general service entity, where the processing message includes the processing priority, so that the general service entity or other general service entity can be processed according to the The events are processed in order of priority.

Specifically, after the event priority setting of the event, if the application has an event to be processed, the information and processing priority of the event may be directly sent to the general service entity, so that the general service entity can process the event in an orderly manner. If the general service entity is a local general service entity, after receiving the event information and processing priority of the application, the event information and the processing priority may be sent to the target general service entity, and the target general service entity is ordered according to the processing priority. The event is processed; event information and processing priority may also be sent to other local general service entities for transmission by other local general service entities to the target general service entity. If the generic service entity is a target general service entity, the application can reply the event information and processing priority to the target generic service entity, which processes the event in an orderly manner according to the processing priority.

In the event priority setting method of the embodiment, the application priority information of the application is obtained from the general service entity, and the application sets the processing priority according to the policy information, so that the target general service entity is obtained. The events of different applications can be processed in an orderly manner according to the processing priority, and the problem that the target general service entity cannot process the events in order due to the lack of unified identification of different applications is avoided.

Example 9

FIG. 9 is a flow chart showing an event priority setting method according to Embodiment 9 of the present invention. The same steps in Fig. 9 as those in Fig. 8 have the same functions, and detailed descriptions of these steps are omitted for the sake of brevity.

As shown in FIG. 9, the main difference between the event priority setting method shown in FIG. 9 and the event priority setting method shown in FIG. 8 is that the event priority setting method may further include:

Step S910: The universal service entity receives a service policy from another general service entity, where the universal service entity has been registered on the other general service entity, and the service policy indicates that the other universal service entity sets the The strategy used by the priority of the application entity;

Step S930: The universal service entity updates the application priority information according to the service policy.

Specifically, if the general service entity is a local general service entity, the service policy of other general service entities may be received through the Mcc reference point. The other general service entity is already registered on the local general service entity, and may be a local general service entity or a target general service entity. The strategy used by a business policy to prioritize applications for other common service entities. The local general service entity can update the application priority information in combination with the above business policy. In this way, when the general service entity subsequently sets the processing priority, the service policy can be taken into consideration, and the common service entity cannot be identified because the priority and the processing priority set by the other general service entities are not unified. Order the problem of the event.

The event priority setting method in this embodiment receives the service policy and updates the policy information according to the service policy, and is used to set the processing priority of the event. The business policy can be taken into consideration, so that the target general service entity can process the events of different applications in an orderly manner, and the target common service entity is avoided because the priority set and the processing priority set by the universal service entity are not unified. The problem of the event could not be processed in an orderly manner.

The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Claims

claims

1. A universal service entity, characterized by:

A receiving unit, configured to receive data information from an application, wherein the data information includes an application policy or an event priority, the event priority represents the priority of the data information, and the application policy represents the settings set by the application. Strategies for prioritizing events;

a setting unit, connected to the receiving unit, configured to set the processing priority of the event represented by the data information according to policy information, wherein the policy information includes the event priority or the application policy, The policy information also includes application priority information. The application priority information represents the priority classification of the applications registered on the universal service entity by the universal service entity according to the application type.

2. The universal service entity according to claim 1, further comprising: an analysis unit, connected to the setting unit, for analyzing historical data and/or the data information to obtain analysis information;

The policy information also includes the analysis information.

3. The universal service entity according to claim 1 or 2, further comprising: a processing unit, connected to the setting unit, and configured to process the events in an orderly manner according to the processing priority.

4. The universal service entity according to any one of claims 1 to 3, further comprising:

A sending unit, connected to the setting unit, is used to send a processing message to other general service entities according to the processing priority, where the processing message includes the event represented by the data information and the processing priority.

5. The universal service entity according to any one of claims 1 to 4, further comprising an update unit,

The receiving unit is further configured to receive a business policy from other general service entities, wherein the other general service entities have been registered on the general service entity, and the business policy represents the The strategy adopted by the other general service entities to set the priority of the application;

The update unit is connected to the receiving unit and the setting unit, and is used to update the policy information according to the service policy.

6. The universal service entity according to any one of claims 1 to 5, further comprising a registration unit and a determination unit,

The receiving unit is further configured to: receive creation request information from the application;

The registration unit is connected to the receiving unit and is used to complete the registration of the application in the universal service entity according to the creation request information;

The determining unit is connected to the registration unit and is used to determine the type of the application according to the registration information of the application;

The determining unit is further configured to obtain the application priority information according to the type of the application;

The sending unit is further configured to send response information to the application, where the response information includes the application priority information.

7. An application, characterized by including:

The first sending unit is configured to send creation request information to the general service entity, where the creation request information includes the identification of the requested acquisition strategy;

A receiving unit, connected to the first sending unit, configured to receive response information from the universal service entity, wherein the response information includes application priority information, and the application priority information indicates that the universal service entity Type prioritization of the applications registered on the universal service entity;

A setting unit, connected to the receiving unit, configured to set the processing priority of the event for a certain event according to policy information, where the policy information includes the response information, and the policy information also includes the The event priority or application policy of the application. The event priority indicates the priority set by the application for the event. The application policy indicates the priority set by the application for the event. level strategy.

8. The application according to claim 7, further comprising:

A second sending unit, connected to the setting unit, is used to send a processing message to the universal service entity or other universal service entities, wherein the processing message includes the processing priority, so that the universal service entity or other The general service entity can process the events in an orderly manner according to the processing priority.

9. A machine-to-machine system, characterized by including:

At least one application as claimed in claim 7 or 8; and

At least one universal service entity as described in any one of claims 1 to 6.

10. An event priority setting method, suitable for machine-to-machine systems, characterized by including:

The universal service entity receives data information from the application, wherein the data information includes an application policy or an event priority, the event priority indicates the priority of the data information, and the application policy indicates that the application sets the event priority strategy;

The general service entity sets the processing priority of the event represented by the data information according to the policy information, wherein the policy information includes the event priority or the application policy, and the policy information also includes the application priority. Information, the application priority information represents the priority classification by the universal service entity of the applications registered on the universal service entity according to application types.

11. The event priority setting method according to claim 10, characterized in that, before the universal service entity sets the processing priority of the event represented by the data information according to the policy information, it further includes:

The policy information also includes the analysis information.

12. The event priority setting method according to claim 10, characterized in that, in the After the universal service entity sets the processing priority of the event represented by the data information according to the policy information, it also includes:

The general service entity processes the events in an orderly manner according to the processing priority.

13. The event priority setting method according to any one of claims 10 to 12, characterized in that after the universal service entity sets the processing priority of the event represented by the data information according to the policy information , Also includes:

The universal service entity sends processing messages to other universal service entities according to the processing priority, where the processing message includes the event represented by the data information and the processing priority.

14. The event priority setting method according to any one of claims 10 to 13, characterized in that, before the universal service entity sets the processing priority of the event represented by the data information according to the policy information, , Also includes:

The universal service entity receives a business policy from other universal service entities, wherein the universal service entity has been registered on the other universal service entities, and the business policy indicates that the other universal service entities set the priority of the application. Strategies adopted by level;

The general service entity updates the policy information according to the business policy.

15. An event priority setting method, suitable for machine-to-machine systems, characterized by including:

The application sends creation request information to the general service entity, and the creation request information includes the identification of the requested acquisition strategy;

The application receives response information from the universal service entity, wherein the response information includes application priority information, and the application priority information indicates that the universal service entity has been registered on the universal service entity according to the application type. Prioritization of the applications;

The application sets the processing priority of the event for a certain event based on policy information, where the policy information includes the response information, and the policy information also includes event priority or application policy. Omitted, the event priority represents a priority set by the application for the event, and the application policy represents a policy for the application to set the event priority.

16. The event priority setting method according to claim 15, characterized in that, after the application sends the creation request information to the universal service entity, it further includes:

The universal service entity completes the registration of the application in the universal service entity according to the creation request information;

The general service entity determines the type of the application based on the registration information of the application; the general service entity obtains the application priority information based on the type of the application.

17. The event priority setting method according to claim 15 or 16, characterized in that, before the application sends the creation request information to the universal service entity, it also includes:

The universal service entity updates the application priority information according to the service policy.

18. The event priority setting method according to any one of claims 15 to 17, characterized in that, after the application sets the processing priority of the event for a certain event according to the policy information, include:

The application sends a processing message to the universal service entity, where the processing message includes the processing priority, so that the universal service entity can process the event in an orderly manner according to the processing priority.