WO2018086413A1 - 处理操作请求的方法及装置 - Google Patents

处理操作请求的方法及装置 Download PDF

Info

Publication number
WO2018086413A1
WO2018086413A1 PCT/CN2017/102214 CN2017102214W WO2018086413A1 WO 2018086413 A1 WO2018086413 A1 WO 2018086413A1 CN 2017102214 W CN2017102214 W CN 2017102214W WO 2018086413 A1 WO2018086413 A1 WO 2018086413A1
Authority
WO
WIPO (PCT)
Prior art keywords
group
operation request
entity group
entity
processing
Prior art date
Application number
PCT/CN2017/102214
Other languages
English (en)
French (fr)
Inventor
赵君杰
Original Assignee
京东方科技集团股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 京东方科技集团股份有限公司 filed Critical 京东方科技集团股份有限公司
Priority to EP17870069.6A priority Critical patent/EP3541013A4/en
Priority to US16/347,649 priority patent/US11362856B2/en
Publication of WO2018086413A1 publication Critical patent/WO2018086413A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2838—Distribution of signals within a home automation network, e.g. involving splitting/multiplexing signals to/from different paths
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2807—Exchanging configuration information on appliance services in a home automation network
    • H04L12/2814—Exchanging control software or macros for controlling appliance services in a home automation network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2823—Reporting information sensed by appliance or service execution status of appliance services in a home automation network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0876—Aspects of the degree of configuration automation

Definitions

  • the present disclosure relates to the field of information technology, and in particular, to a method and apparatus for processing an operation request by using an association group.
  • a group is a combination of multiple individuals of the same or different types.
  • Batch operations can be implemented through groups, such as reading information, storing information, subscribing information, making notifications, device management, and the like.
  • the group receives the operation request, the group forwards the request to each member of the group, and can aggregate the results sent by each member.
  • the present disclosure proposes a method and apparatus for processing an operation request using an association group.
  • a method of processing an operation request including:
  • the operation request is sent to the at least one second entity group for processing.
  • another method of processing an operation request including:
  • the operation request is sent to at least one second entity group associated with the first entity group for processing.
  • a control apparatus comprising:
  • a transceiver receiving an operation request of an entity and transmitting the operation request to the first entity group for processing
  • the processor determines at least one second entity group associated with the first entity group and instructs the transceiver to send the operation request to the at least one second entity group for processing.
  • a communication apparatus including:
  • transceiver that sends an operation request to initiate a first entity group to process the operation request
  • the processor instructs the transceiver to send the operation request to the at least one second entity group associated with the first entity group for processing.
  • a method and apparatus for processing an operation request are disclosed. By associating a plurality of groups and processing the operation request with the associated groups, batch processing of the operation request can be realized, and the automation level and management efficiency are improved.
  • FIG. 1 is a schematic network to which the principles of the present disclosure may be applied.
  • 2A-2B are schematic diagrams of processing an operation request using a group.
  • 3A-3D are schematic diagrams of processing an operation request based on an association relationship between groups, in accordance with an embodiment of the present disclosure.
  • FIG. 4 is a schematic diagram of adding an association identifier and associated attribute values in a resource of a group, in accordance with an embodiment of the present disclosure.
  • FIG. 5 illustrates an illustrative process for processing an operation request with an association group in accordance with an embodiment of the present disclosure.
  • FIG. 6 illustrates another schematic process for processing an operation request with an association group in accordance with an embodiment of the present disclosure.
  • FIG. 7 illustrates yet another illustrative process for processing an operation request with an association group in accordance with an embodiment of the present disclosure.
  • FIG. 8 illustrates an illustrative process for processing an operation request with the created association group, in accordance with an embodiment of the present disclosure.
  • FIG. 9 illustrates an illustrative process for processing an operation request with the created association group, in accordance with an embodiment of the present disclosure.
  • FIG. 10 is a schematic flowchart of a method of processing an operation request using an association group, according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic flow diagram of a method of processing an operation request using an association group, in accordance with an embodiment of the present disclosure.
  • FIG. 12 is a schematic block diagram of a control device in accordance with an embodiment of the present disclosure.
  • FIG. 13 is a schematic block diagram of a communication device in accordance with an embodiment of the present disclosure.
  • FIG. 1 shows a schematic diagram of a network to which the principles of the present disclosure may be applied.
  • a user can connect to a home gateway via a server via a mobile phone, so that a home device (eg, a lighting device) can be controlled through a home gateway.
  • the home devices may be divided into groups, an association relationship between the groups is established, and an operation request of the user is processed using an association relationship between the groups.
  • FIG. 2A-2B show schematic diagrams of processing an operation request using a group, where the group includes one or more members that can perform an operation request.
  • the established group sends the operation request to each member of the group, and the member of the group processes and executes the operation request; then, As shown in FIG. 2B, when the processing of the operation request is completed, each member feeds back the processing result as a response to assemble the respective processing results and return the processing result to the requesting party of the operation request.
  • the backup relationship is a pointer to the same operation request
  • there is a backup relationship between the at least two groups as shown in FIG. 3A, when the member of one of the groups fails to successfully execute the operation request, the operation request is Forwarding to another group belonging to the backup relationship, starting the member of the other group to perform the operation request; in other words, for the operation request, the two groups are in a backup relationship to ensure that at least one group of members can The operation request was successfully executed.
  • the progressive relationship is a pointer to the same operation request, and there is a progressive relationship between the at least two groups, as shown in FIG. 3B, when a member of one of the groups has successfully executed the operation request, The operation request is forwarded to another group belonging to the progressive relationship, and the member that starts the other group also performs the operation request; in other words, for the operation request, the two groups are in a progressive relationship to achieve In the case where a group of members successfully executes the operation request, starting at least another group of members also performs the operation request.
  • a side-by-side relationship is a pointer to the same operation
  • the request has a parallel relationship between the at least two groups. As shown in FIG.
  • the association identifier and the associated attribute value under the resource corresponding to the first group are queried to determine
  • the first group belongs to another group of the side-by-side relationship; thus, when the members of the first group are started to execute the operation request, members of another group belonging to the first group in a side-by-side relationship are also started to process the operation request.
  • the two groups are in a side-by-side relationship to implement the operation request in the members of the first group and the members of the second group, respectively.
  • the operation request can be processed in parallel using a plurality of groups.
  • association relationships may also be established between groups, for example, an association relationship such as an interlock relationship.
  • an association relationship such as an interlock relationship.
  • the interlock refers to an interlock relationship between at least two groups. When a group successfully performs an operation request, it is prohibited to start another group that has an interlocking relationship with the group.
  • the two groups are in an interlocking relationship, so that the members of the first group or the members of the second group separately perform the operation request instead of the members of the first group and the second
  • the members of the group mix and execute the operation request.
  • the embodiments of the present disclosure are merely illustrative and not exhaustive. Therefore, the principles of the present disclosure can also be applied to groups having other related relationships to produce new embodiments, and such embodiments do not depart from the present invention. The scope.
  • FIG. 4 is a schematic diagram of adding an association identifier and associated attribute values in a resource of a group, in accordance with an embodiment of the present disclosure. As shown in FIG. 4, under the resource type group, two attributes are added, which are the association identifier relatedGroup and the associated attribute value relationshipofGroups.
  • the association identifier relatedGroup may indicate an identifier of a resource (for example, another entity group) associated with an entity group
  • the association attribute value relationshipofGroups may indicate an association relationship between the entity group and other resources (for example, other entity groups), for example, , backup relationships, progressive relationships, side-by-side relationships, interlocking relationships, and more.
  • an identifier of another resource that is associated with an entity group is set in the association identifier relatedGroup, for example, a resource identification ID of another entity group associated with the entity group, or a resource name may be set.
  • the query can be queried according to the association identifier and the associated attribute value set under the entity group resource.
  • the operation instruction corresponding to the request improves the automation level and management efficiency of the device management.
  • the attributes of the group may be set on the general service entity CSE under the management server, for example, under the framework of the M2M protocol, for example, setting the association identifier relatedGroup and the associated attribute corresponding to the group resource of the first group.
  • the value of relationshipofGroups For the sake of simplicity, in the embodiment illustrated in FIG. 5, two groups, namely a first group A and a second group B, are illustrated, wherein each group includes at least one member that can perform an operation request of the requesting party.
  • the association identifier relatedGroup under the group resource corresponding to the first group A is set to point to the identifier of the second group B, and the association attribute value relationshipofGroups can be set as the backup relationship.
  • the first group A and the second group B are associated, and the relationship between them is set as the backup relationship.
  • an entity issues an operation request to the management server, for example, the application entity AE issues an operation request to the general service entity CSE.
  • the CSE processes the request, obtains the group that executed the operation request, and the information of the group member, and forwards the operation request to all members of the group.
  • the CSE obtains information about the members of the first group A and the first group A, and forwards the operation request to all members in the first group A.
  • the requestor of the operation request may be first authenticated, and after successfully passing the identity verification, the group for executing the operation request is selected.
  • the group for executing the operation request is selected.
  • the CSE upon receiving an operation request sent from the CSE, all members included in the first group A are activated to execute the operation request, and the result of the execution is returned as feedback to the CSE.
  • the CSE receives the execution results returned by all members in the first group A, and analyzes the results to assemble whether the operation request is successfully executed.
  • various policies can be set to determine if the operational request was successfully executed.
  • the following policy can be set: only when all the members in the first group A have successfully executed the operation request, it is determined that the operation request has been successfully executed by the first group A. Alternatively, it can be set that as long as more than half of the members in the first group A have successfully executed the operation request, it is determined that the operation request has been Successful execution by group A.
  • the specific judgment strategy can be determined according to the business requirements, and is not limited herein. Alternatively, it may be determined based on the associated attribute value whether the operation request was successfully executed. For example, the association relationship indicated by the associated attribute value is subdivided.
  • the member of the group B is started to process the operation request after all members in the group A fail to process the operation request.
  • the group B can be started to process the operation request after the partial member processing operation request fails in the group A, and other relationships can be analogized, and details are not described herein again.
  • the CSE determines that the operation request is not successfully executed by the first group A, in other words, the first group A performs the operation request is determined.
  • the backup group of the first group A can be determined by querying the association identifier and the associated attribute value under the group resource of the first group A set. For example, if the association identifier relatedGroup corresponding to the group resource of the first group A points to the identifier of the second group B, and the association attribute value relationshipofGroups is set as the backup relationship, it may be determined that the second group B is the first group A Backup group.
  • the operation request can be executed by triggering the second group B as the backup group. Specifically, the CSE obtains information about the members of the second group B and the second group B, and forwards the operation request to all members in the group B. As shown in FIG.
  • all members included in the second group B are activated to execute the operation request, and the result of the execution is returned as feedback to the CSE.
  • the CSE receives the execution results returned by all members in the second group B, and analyzes the results to assemble whether the operation request is successfully executed.
  • various policies can be set to determine if the operation request was successfully executed.
  • the CSE can then return to the requesting party feedback information to perform the operation request. For example, when the operation request is successfully executed by either the first group A or the second group B, the CSE returns a response to the requester to successfully execute the operation request. Conversely, only if the first group A and the second group B fail to perform the operation request, the CSE returns to the requester information that the operation request failed.
  • the user's mobile phone can access the home gateway in the home through the wireless network, and an application that can remotely control the home device through the application of the home gateway is installed in the mobile phone, for example, Control the lighting facilities in the user's home through the application of the home gateway (for example, lights in each room), temperature control facilities (for example, air conditioning or heating facilities in the room), or bathroom facilities (such as electric water heaters), Cooking facilities (such as rice cookers) and more.
  • the application in the mobile phone can be used as the requesting party for sending the operation request in FIG.
  • the requesting entity, and the corresponding application in the home gateway can be used as the management server or the general service entity CSE, and can be created corresponding to An application entity group of different types of facilities in the home, for example, respectively corresponding to a lighting facility, a temperature control facility, or a bathroom facility, the group including members who can perform an operation request (for example, perform an operation request to turn on the corresponding facility).
  • the facilities of one room may also be set as a group, and the specific manner is not limited.
  • a group may include different types of application entities, and each entity in the room is received when the startup operation is received. Was started.
  • a user may set a corresponding group in an application of a home gateway in advance and associate each group.
  • a user may set a function associated with an access control system of a user's home in an application of the mobile phone.
  • the access control system authenticates the user's identity. After passing the verification, the access control system is turned on, and at the same time, an operation request to turn on the lights of the hall is issued to the home gateway.
  • the lights in the foyer can be divided into two sets of lights that are in a backup relationship, and two groups corresponding to the first set of lights and the second set of lights are established and associated.
  • the CSE in the home gateway first issues a start command to the first set of lights to turn on the first set of lights and receive a response from the first set of lights.
  • the CSE determines that the first group of lights fails and fails to be turned on
  • the CSE queries the association identifier and the associated attribute value of the group resource corresponding to the first group, thereby starting the backup relationship.
  • the second set of lights In this way, even if the first group of lamps fails to open due to some kind of failure, the second group of lamps can be turned on in time to realize redundant control of the lamps, so that when the user enters the hall through the access control system, a group of lights in the hall has been Turn on, avoiding the inconvenience of users turning on the lights.
  • the member since the backup relationship between the two entity groups is established and associated, thereby implementing the redundancy control, the member can be started in time when the member of one of the entity groups fails to perform the operation request.
  • the members of another entity group perform operational requests, improving the level of automation and management efficiency.
  • the first group A and the second group B are also described, wherein each group includes at least one member who can perform an operation request of the requesting party.
  • the association identifier relatedGroup under the group resource corresponding to the first group A is set to point to the identifier of the second group B, and the association attribute value relationshipofGroups can be set as the progressive relationship.
  • the first group A and the second group B are associated, and the relationship between them is set as a progressive relationship.
  • the first group A may subscribe an application entity request to a management server (for example, a general service entity CSE), so that the first group can be notified in time when the CSE receives an operation request from the application entity.
  • a management server for example, a general service entity CSE
  • an entity issues an operation request to the management server, for example, the application entity AE issues an operation request to the general service entity CSE.
  • the CSE processes the request, obtains the group that executed the operation request, and the information of the group member, and forwards the operation request to all members of the group.
  • the CSE obtains information about the members of the first group A and the first group A, and forwards the operation request to all members in the first group A.
  • the requestor of the operation request may be first authenticated, and after successfully verifying the identity, the first group A subscribed to the application entity is notified to notify the operation request. .
  • the first group A subscribed to the application entity is notified to notify the operation request.
  • the requestor of the operation request may be first authenticated, and after successfully verifying the identity, the first group A subscribed to the application entity is notified to notify the operation request.
  • the requestor of the operation request may be first authenticated, and after successfully verifying the identity, the first group A subscribed to the application entity is notified to notify the operation request. .
  • the CSE upon receiving an operation request from the CSE transmission, all members included in the first group A are activated to execute the operation request, and the result of the execution is returned as feedback to the CSE.
  • the CSE receives the execution results returned by all members in the first group A, and analyzes the results to assemble whether the operation request is successfully executed.
  • various policies may be set or determined based on the associated attribute values to determine whether the operation
  • the query may be performed by querying the group resources of the first group A set.
  • the association identifier and the associated attribute value determine a group that is in a progressive relationship with the first group A. For example, if the association identifier relatedGroup corresponding to the group resource of the first group A points to the identifier of the second group B, and the association attribute value relationshipofGroups is set to the progressive relationship, it may be determined that the second group B is the first group A group of progressive relationships. At this time, the second group B, which is a progressive relationship, can also be triggered to execute the operation request. Specifically, the CSE obtains information about the members of the second group B and the second group B, and forwards the operation request to all members in the group B. As shown in FIG.
  • the user's mobile phone can access the home gateway in the home through the wireless network, and an application that can remotely control the home device through the home gateway is installed in the mobile phone, for example, Control the lighting facilities in the user's home (for example, the lights of each room), the temperature control facilities (for example, the air conditioning or heating facilities of the room), or the bathroom facilities (such as electric water heaters) through the application of the home gateway (as the management server CSE) and many more.
  • the application in the mobile phone can be used as the requesting party for sending the operation request in FIG.
  • the requesting entity, and the corresponding application in the home gateway can be used as the management server or the general service entity CSE, and can be created corresponding to An application entity group of different types of facilities in the home, for example, respectively corresponding to a lighting facility, a temperature control facility, or a bathroom facility, the group including members who can perform an operation request (for example, perform an operation request to turn on the corresponding facility).
  • the facilities of one room may also be set as a group, and the specific manner is not limited.
  • the group may include different types of application entities, and when receiving the startup operation, each entity in the room is Was started.
  • a user may set a corresponding group in an application of a home gateway in advance and associate each group.
  • a user may create two groups in an application of a home gateway as a management server, using the air conditioner of the living room as an application entity of the first group of facilities, and using the electric water heater of the bathroom as a second group of facilities.
  • Application entity and the two as a progressive The groups of the association are associated.
  • a subscription application entity request is set on the application of the home gateway (for example, CSE).
  • CSE receives a request from the corresponding application entity
  • a notification can be sent to the first group A, thereby triggering the members of the first group A to perform the corresponding operation request.
  • the user uses the mobile phone's application on the way home to issue an operation request to the home gateway to open the facility, such as the start command "ON".
  • an application eg, application entity AE
  • the CSE on the home gateway sends a notification request to the first group A subscribed to the application entity request, thereby initiating the first group A
  • the member performs the corresponding operation request.
  • the members of the first group A ie, the air conditioner of the living room, are turned on to control the appropriate room temperature.
  • the first group A then returns a notification response message to the CSE.
  • the CSE After receiving the notification response message from the first group A, the CSE aggregates and analyzes the notification response message to determine whether the first group A successfully executed the operation request. After determining that the air conditioner of the living room has been successfully turned on, the CSE queries the association identifier and the associated attribute value corresponding to the group resource of the first group A, and queries that the group associated with the first group A is the second group, and they are The relationship between the two is a progressive relationship. Thus, the CSE sends an operation request to the second group B, thereby starting the second group B as a progressive relationship.
  • the member of the second group B that is, the application entity AE corresponding to the electric water heater of the toilet, upon receiving an operation request from the CSE, activates the electric water heater of the toilet, starts heating, and maintains the water temperature when heated to a predetermined water temperature.
  • the user only needs to send an operation request to the home gateway through the application on the mobile phone, and according to the setting of the relevant application entity group in the application of the home gateway, the facility corresponding to the application entity group as the progressive relationship can be automatically started, and the device is omitted.
  • the cumbersome steps of the user separately sending an operation request to each entity group save data communication traffic and improve the management efficiency of the facility.
  • first group A and the second group B respectively include only one member
  • first group and the second group may include more than one member as needed.
  • principles of the present disclosure are not limited to two groups, and members of the group are not limited to the same type as long as members of the group can handle the same operation request.
  • the first group is set to subscribe to the application entity request to the CSE, so that when the CSE receives the operation request from the application entity, the member of the first group is triggered to process the operation request.
  • the CSE automatically triggers the first group when receiving the application entity request sent by the requesting party, for example, when the CSE receives the operation request from the requesting party, directly forwards the member to the first group; or The CSE periodically forwards the operation request from the requesting party to the first group of members, which is not limited in this disclosure.
  • the first group A and the second group B are also described, wherein each group includes at least one member who can perform an operation request of the requesting party.
  • the association identifier relatedGroup under the group resource corresponding to the first group A is set to point to the identifier of the second group B, and the association attribute value relationshipofGroups can be set to the side-by-side relationship.
  • the first group A and the second group B are associated, and the relationship between them is set to a side-by-side relationship.
  • the first group A may subscribe to an application entity request (for example, a general service entity CSE) to send the operation request when the CSE receives an operation request from the requesting party. Give the first group A.
  • an application entity request for example, a general service entity CSE
  • an entity issues an operation request to the management server, for example, the application entity AE issues an operation request to the general service entity CSE.
  • the CSE processes the request, obtains the group that executed the operation request, and the information of the group member, and forwards the operation request to all members of the group.
  • the CSE obtains information about the members of the first group A and the first group A, and forwards the operation request to all members in the first group A.
  • the requester of the operation request may be first authenticated, and after the identity verification is successfully performed, the operation request is notified to the first group A that subscribes to the application entity request. As shown in FIG.
  • the CSE determines a group that is in a side-by-side relationship with the first group A by querying the association identifier and the associated attribute value under the group resource of the first group A set. For example, if the association identifier relatedGroup corresponding to the group resource of the first group A points to the identifier of the second group B, and the association attribute value relationshipofGroups is set to the side-by-side relationship, it may be determined that the second group B is the first group A The group of side-by-side relationships.
  • the members of the second group B of the side-by-side relationship also perform the operation request.
  • the CSE obtains information about the members of the second group B and the second group B, and forwards the operation request to all members in the group B.
  • all members included in the second group B are activated to execute the operation request, and the result of the execution is returned as feedback to the CSE.
  • the CSE receives the execution results returned by all members in the first group A and the second group B, and analyzes the results to determine whether the operation request is successfully executed.
  • various policies may be set or determined according to the associated attribute values to determine whether the operation request is successfully executed by the first group A.
  • the specific judgment strategy can be determined according to the business requirements, and is not limited herein.
  • various policies can also be set to determine whether the operation request was successfully executed by the second group B.
  • the CSE returns an operation response to the requesting party, that is, returns the execution result of the first group A and the execution result of the second group B to the requesting party, so that the requesting party can decide the next action based on the received operation response.
  • a group that responds to an operation that failed to perform an operation can trigger its backup group to perform an operation request.
  • the first group is set to be associated with the second group by using the first group, and the first group is set to be associated with the second group, and the association relationship is set to a side-by-side relationship, so that the operation from the application entity can be received at the CSE.
  • the notification message is automatically sent to the first group subscribed to the application entity request, thereby triggering the members of the first group to perform the operation request; meanwhile, since the second group is associated with the first group, the query can be set by the query.
  • the second group B is found by the association identifier and the associated attribute value under the group resource of the first group A, and the member triggering the second group B also performs the operation request.
  • the user's mobile phone can access the home gateway in the home through the wireless network, and an application that can remotely control the home device through the home gateway is installed in the mobile phone, for example,
  • the home gateway application (as the management server CSE) controls various facilities in the user's home, such as lighting facilities, temperature control facilities, bathroom facilities or cooking facilities, and the like.
  • the application in the phone can be sent as Figure 7.
  • the requesting party that sends the operation request can serve as the management server or the general service entity CSE, and can create an application entity group respectively corresponding to different types of facilities in the home, for example, Corresponding to a lighting facility, a temperature control facility, a bathroom facility, or a cooking group, respectively, the group includes members who can perform an operation request (for example, perform an operation request to turn on the corresponding facility).
  • the facilities of one room may also be set as a group, and the specific manner is not limited.
  • the group may include different types of application entities, and when receiving the startup operation, each entity in the room is Was started.
  • a user may set a corresponding group in an application of a home gateway in advance and associate each group.
  • a user may create two groups in an application as a home gateway of a management server, using the rice cooker of the kitchen as an application entity of the first group of facilities, and the washing machine of the bathroom as a second group.
  • the application entity of the facility and associates the two as a group of side-by-side relationships.
  • the user Before going out to work in the morning, the user can put rice and water into the rice cooker, put the laundry to be put into the washing machine, and set the length of time for cooking and washing.
  • a subscription application entity request is set on the application of the home gateway (for example, CSE).
  • a notification can be sent to the first group A, thereby triggering the members of the first group A to perform the corresponding operation request.
  • the user can use the mobile phone's application to send an operation request to open the facility to the home gateway before leaving work, such as the start command "ON".
  • an operation request eg, "ON”
  • an application eg, application entity AE
  • the CSE on the home gateway sends a notification request to the first group A subscribed to the application entity request,
  • the members of the first group A are started to perform corresponding operation requests.
  • the members of the first group A are activated, ie, the rice cooker is activated to start cooking.
  • the CSE can find the second group B by querying the association identifier and the associated attribute value under the group resource of the first group A set, and trigger the second group.
  • the member of B also performs the operation request.
  • the washing machine can be started to start the laundry.
  • the first group A returns a notification response message to the CSE
  • the second group B feeds back an operational response to the CSE.
  • the CSE analysis aggregates the responses of the first group A and the second group B, and feeds back the responses of the two to the requesting party, for example, the application on the user's mobile phone, so that the user can obtain the execution result of the operation request in time, and can Take the appropriate next step.
  • the application entity request is subscribed on the CSE and will
  • the second group B is associated with the first group A in parallel, thereby preventing the user from separately transmitting operation requests for the first group and the second group to the home gateway, that is, in this example, the user is not required to use the mobile phone
  • the home gateway separately sends operation instructions for controlling the rice cooker and the washing machine, which saves data communication traffic, improves the automation level and manages the efficiency of the facility.
  • first group A and the second group B respectively include only one member, but it should be understood that the first group and the second group may include more than one member, in the group, as needed.
  • Members are not limited to the same type, as long as members of the group can handle the same operational request (for example, a request to start or close).
  • two attributes of the association identifier relatedGroup and the association attribute value relationOfGroups as shown in FIG. 4 are added to the group resource group on the general service entity CSE.
  • an application entity wants to create a group resource on the CSE, it sends a request to the CSE to create a group.
  • the CSE Upon receiving the request to create a group, the CSE creates a corresponding group after passing the verification, for example, creating group 1 and group 2, wherein each group may include multiple application entities; then, the CSE to the application entity as the requesting party Returns the response that the group was created.
  • the application entity may request to set the attributes of the group as needed, for example, setting the attribute of the group 1, wherein the association identifier relatedGroup under the group resource of the group 1 is set to the group 2
  • the identifier, and set the associated attribute value relationOfGroups to, for example, a backup.
  • the CSE returns a group attribute setting response to the application entity, thereby completing a setting request for the group of the application entity.
  • the CSE When the application entity sends an operation request to the CSE (for example, the application entity can be implemented by setting an associated resource attribute value of the group 1 by an update request), the CSE first goes to the group 1 The member sends an instruction to execute the operation request, and the member of group 1 executes the operation request upon receiving the instruction, and returns the result of the execution to the CSE as a response.
  • the CSE receives the execution response from the members of group 1, and determines whether the member of group 1 successfully executed the operation request. If the execution is not successful, the CSE sends an instruction to execute the operation request to the associated member of the group 2 as the backup group by querying the association identifier relatedGroup and the association attribute value relationOfGroups under the group resource of the group 1.
  • the members of group 2 return an execution response to the CSE.
  • the CSE aggregates the execution response of the member of the analysis group 2
  • the application entity that is the requesting party sends a response to perform the operation request; for example, if the member of the group 2 successfully performs the operation response, the CSE acts as the requesting party.
  • the application entity sends a response to successfully execute the operation request.
  • FIG. 9 illustrates an example in which a request to create a group is separately issued by a different application entity and an operation request is performed using the created group.
  • two attributes of the association identifier relatedGroup and the association attribute value relationOfGroups as shown in FIG. 4 are added to the group resource group on the general service entity CSE.
  • an operation request may be sent to the CSE by another entity, such as the application entity B, for example, the request may be implemented by an update request to set the resources associated with the group 1.
  • the CSE Upon receiving an operation request from the application entity B, the CSE sends an instruction to the member of the group 1 to execute the operation request, and accordingly, each member of the group 1 executes the operation request, and returns a result of executing the operation request to the CSE as a response. .
  • the CSE collects the execution result returned by the member of the analysis group 1, and returns an execution operation request to the application entity B. the response to. At this point, the CSE can analyze whether the member of the group 1 successfully executed the operation request and return the final judgment result to the application entity B.
  • the CSE may also directly forward the execution response of the group 1 to the application entity B, and the application entity B itself determines whether the member of the group 1 successfully executes the operation request.
  • the group associated with the group 1 can be queried by the CSE or the application entity B, and the group associated with the group 1 is determined to be the group 2
  • the application entity B may send an operation request to the general service entity CSE, and the CSE sends the operation request to the member of the group 2 as the backup of the group 1 to execute the operation request. Accordingly, the CSE receives the result of the execution of the operation request sent by the member in the group 2 as a response, and returns a response to the execution of the operation request to the application entity B.
  • the application entities that set the association group and the entities that use the association group to perform the operation request are different entities.
  • an application entity that sets an association group and an entity that uses an association group to perform an operation request may also be located on different hardware terminals.
  • a mobile phone can be used as a host to send a request for setting an association group to a home gateway, thereby setting an association group for each home facility, and other mobile phones acting as slaves can
  • the home gateway sends an operation request to perform an operation request using an association group set as a host's mobile phone.
  • FIG. 10 illustrates a method of processing an operation request according to an embodiment of the present disclosure, including the steps of: S1010, receiving an operation request of an entity; S1020, transmitting the operation request to a first entity group for processing; S1030, determining and At least one second entity group associated with the first entity group; and S1040, the operation request is sent to the at least one second entity group to process the operation request.
  • the method further includes associating the first entity group with the at least one second entity group.
  • each of the entity groups includes at least one member for processing an operation request.
  • the method further includes: adding an association identifier and an association attribute value to the resource corresponding to the first entity group, wherein the association identifier indicates an identifier of the entity group associated with the first entity group, and the associated attribute value Indicates the association relationship between the first entity group and the entity group.
  • the associating the first entity group with the at least one second entity group comprises: setting a value of the association identifier to an identifier of the second entity group, and setting the associated attribute value to the indicator genus An association relationship of at least one of a backup relationship, a progressive relationship, or a parallel relationship.
  • the method further includes: querying the association identifier and the associated attribute value included in the resource corresponding to the first entity group, to determine the second entity group and the second entity group associated with the first entity group The relationship between the first entity groups.
  • sending the operation request to the first entity group for processing comprises: sending an operation request to each member of the first entity group to process the operation request, and receiving the processing returned by each member of the first entity group result.
  • the method further includes: when the returned processing result indicates that the operation request is not successfully processed, starting a member included in the second entity group that belongs to the backup relationship with the first entity group to process the operation request.
  • the method further includes: determining an association relationship between the first entity group and the at least one second entity group as a backup relationship; wherein, when the returned processing result indicates that the operation request is failed When processing, the operation request is sent to the at least one second entity group for processing.
  • the method further includes: when the returned processing result indicates that the operation request has been successfully processed, starting a member included in the second entity group that belongs to the first entity group in a progressive relationship to process the operation request.
  • the method further includes: determining an association relationship between the first entity group and the at least one second entity group as a progressive relationship;
  • the operation request is sent to the at least one second entity group for processing.
  • the method further includes: starting a member included in the first entity group to process the operation request, and initiating a member included in the second entity group that is in a side-by-side relationship with the first entity group to process the operation request. Specifically, determining that the association relationship between the first entity group and the at least one second entity group is a parallel relationship; wherein, after sending the operation request to the first entity group, sending the operation request to The at least one second entity group performs processing without waiting for the first entity group to return a processing result.
  • the method further includes: assembling the processing result returned by the member of the entity group that processes the operation request, and feeding back the processing result to the entity that issues the operation request.
  • the method further includes: receiving a request to create an entity group, creating a first entity group and at least one second entity group.
  • the request and operation requests to create an entity group are from the same or different entities.
  • the method further includes: collecting processing results returned by the entity group that processes the operation request, And feeding back the processing result to the entity that issues the operation request, including:
  • the identifier of the entity group includes: a resource identifier or a resource name of the resource corresponding to the entity group.
  • the method further includes: receiving a request from the subscription entity of the first entity group; and automatically receiving a notification to the first entity group to initiate the member of the first entity group upon receiving the operation request from the application entity To handle the operation request.
  • FIG. 11 illustrates another method of processing an operation request according to an embodiment of the present disclosure, including the steps of: S1110, transmitting an operation request to start a first entity group to process the operation request; and S1120, processing according to the first entity group As a result, the operation request is sent to at least one second entity group associated with the first entity group for processing.
  • the resource corresponding to the first entity group includes an association identifier and an associated attribute value, where the association identifier indicates an identifier of the at least one second entity group associated with the first entity group, and the associated attribute value indicates the first entity group An association relationship with the at least one second entity group; wherein a value of an association identifier in a resource corresponding to the first entity group is set as an identifier of the at least one second entity group, and the associated attribute value indicates the first entity group The relationship with the second entity group.
  • association relationship is: a backup relationship, a progressive relationship, a parallel relationship, or an interlock relationship.
  • the method further includes determining an association relationship between the first entity group and the at least one second entity group as a backup relationship;
  • the operation request is sent to the at least one second entity group for processing.
  • the method further includes determining that the association relationship between the first entity group and the at least one second entity group is a progressive relationship
  • the operation request is sent And sending to the at least one second entity group for processing.
  • the method further includes: determining an association relationship between the first entity group and the at least one second entity group as a parallel relationship;
  • the operation request is sent to the first entity group
  • the operation request is sent to the at least one second entity group for processing.
  • the method further includes determining, according to the resource corresponding to the first entity group, the at least one second entity group associated with the first entity group.
  • the resource corresponding to the first entity group includes an association identifier and an associated attribute value, the association identifier indicating an identifier of the at least one second entity group associated with the first entity group, the associated attribute value indicating the first An association relationship between the entity group and the at least one second entity group.
  • the identifier of the at least one second entity group includes: a resource identifier or a resource name of a resource corresponding to the at least one second entity group.
  • the value of the association identifier in the resource corresponding to the first entity group is set as the identifier of the at least one second entity group, and the associated attribute value is set to indicate that it belongs to the backup relationship, the progressive relationship, or the parallel An association of at least one of the relationships.
  • the method further includes: receiving a processing result returned by a member of the first entity group; and when the returned processing result indicates that the operation request is not successfully processed, starting a second backup relationship with the first entity group
  • the entity group includes members to handle the operation request.
  • the method further includes: receiving a processing result returned by a member of the first entity group; and when the returned processing result indicates that the operation request has been successfully processed, starting a second belonging to the first entity group to be a progressive relationship
  • the entity group includes members to handle the operation request.
  • the method further includes: initiating a member included in the second entity group that is in a side-by-side relationship with the first entity group to process the operation request.
  • a control device is also provided. As shown in FIG. 12, the method includes: a transceiver 1200, receiving an operation request of an entity, and transmitting the operation request to a first entity group for processing; and a processor 1220, determining at least one associated with the first entity group And the second entity group instructs the transceiver to send the operation request to the at least one second entity group for processing.
  • a communication device includes: a transceiver 1300, sending an operation request to start a first entity group to process the operation request; and a processor 1320, instructing the transceiver to send the operation request according to a processing result of the first entity group Processing is performed on at least one second entity group associated with the first entity group.
  • a control device comprising a processor, a memory coupled to the processor, and a transceiver, wherein the memory stores instructions that are configured to execute the instructions stored in the memory And performing the following steps: instructing the transceiver to receive an operation request of an entity, and sending the operation request to the first entity group for processing; the processor determining the at least one second entity group associated with the first entity group, and starting The at least one second entity group processes the operation request.
  • the communication device is a user terminal, including but not limited to at least one of the following: a smart phone, a PDA, a tablet, and a navigator.
  • control device includes, but is not limited to, at least one of the following: a server, a gateway, and a set top box.
  • any flow diagrams, flowcharts, state transition diagrams, pseudocode, etc. represent various processes that can be substantially represented in a computer readable medium and executed by a computer or processor, whether such computers or processors Whether it is clearly displayed.
  • a computer that can perform writing in transient states (signals) and non-transient states (eg, on tangible media such as CD-ROM, DVD, Blu-ray, hard disk drives, flash memory cards, or other types of tangible storage media) Readable media and code.
  • processor capable of executing software in conjunction with suitable software.
  • this functionality may be provided by a single dedicated processor or a single shared processor or a plurality of independent processors in which some may be shared.
  • DSP digital signal processor
  • ROM Read-only memory
  • RAM random access memory
  • non-volatile memory for storing software.
  • any of the switches shown in the figures are conceptual only. Their function can be performed by operating program logic, dedicated logic, program control and special purpose logic or even manually, and the implementer can select a particular technique based on a more detailed understanding of the context.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Automation & Control Theory (AREA)
  • Multimedia (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种利用关联组来处理操作请求的方法及装置。具体地，本公开的处理操作请求的方法包括：接收操作请求(S1010)；将该操作请求发送给第一实体组进行处理(S1020)；确定与第一实体组相关联的至少一个第二实体组(S1030)；将该操作请求发送给所述至少一个第二实体组进行处理(S1040)。由此，通过将多个组进行关联并且利用关联的各个组对操作请求进行处理，能够实现对操作请求的批量处理，提升自动化水平和管理效率。

Description

处理操作请求的方法及装置 技术领域
本公开涉及信息技术领域，具体涉及一种利用关联组来处理操作请求的方法及装置。
背景技术
目前，随着网络技术的发展，接入网络的设备越来越多。为了简化设备的管理和控制，可以将多个设备或者应用实体分为一组。组是将多个相同或不同类型的个体组合起来，通过组可以实现批量操作，如读取信息，存储信息，订阅信息，进行通知，设备管理等等。当组接收到操作请求后，组将请求转发给组中的每个成员，并且可以将每个成员发送的结果汇集起来。
发明内容
本公开提出了一种利用关联组来处理操作请求的方法及装置。
根据本公开的一方面，提供了一种处理操作请求的方法，包括：
接收操作请求；
将该操作请求发送给第一实体组进行处理；
确定与第一实体组相关联的至少一个第二实体组；
将该操作请求发送给所述至少一个第二实体组进行处理。
根据本公开的另一方面，提供了另一种处理操作请求的方法，包括：
发送操作请求以启动第一实体组来处理该操作请求；以及
根据第一实体组的处理结果，将该操作请求发送给与该第一实体组相关联的至少一个第二实体组进行处理。
根据本公开的另一方面，提供了一种控制装置，其包括：
收发器，接收一实体的操作请求，并且将该操作请求发送给第一实体组进行处理；以及
处理器，确定与第一实体组相关联的至少一个第二实体组，并且指示收发器将该操作请求发送给所述至少一个第二实体组进行处理。
根据本公开的又一方面，还提供了一种通信装置，包括：
收发器，发送操作请求以启动第一实体组来处理该操作请求；以及
处理器，根据第一实体组的处理结果，指示收发器将该操作请求发送给与该第一实体组相关联的至少一个第二实体组进行处理。
根据本公开实施例公开处理操作请求的方法和装置，通过将多个组进行关联并且利用关联的各个组对操作请求进行处理，能够实现对操作请求的批量处理，提升自动化水平和管理效率。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对实施例的附图作简单地介绍，显而易见地，下面描述中的附图仅仅涉及本公开的一些实施例，而非对本发明的限制。
图1是一种可以应用本公开的原理的示意性网络。
图2A-2B是利用组来处理操作请求的示意图。
图3A-3D是根据本公开的实施例的基于各个组之间的关联关系来处理操作请求的示意图。
图4是根据本公开的实施例的在组的资源中添加关联标识符和关联属性值的示意图。
图5图示了一种根据本公开的实施例利用关联组来处理操作请求的示意性过程。
图6图示了另一种根据本公开的实施例利用关联组来处理操作请求的示意性过程。
图7图示了又一种根据本公开的实施例利用关联组来处理操作请求的示意性过程。
图8图示了一种根据本公开的实施例的利用所创建的关联组来处理操作请求的示意性过程。
图9图示了一种根据本公开的实施例的在利用所创建的关联组来处理操作请求的示意性过程。
图10是根据本公开的一实施例的一种利用关联组来处理操作请求的方法的示意性流程图。
图11是根据本公开的一实施例的一种利用关联组来处理操作请求的方法的示意性流程图。
图12是根据本公开的一实施例的一种控制装置的示意性框图。
图13是根据本公开的一实施例的一种通信装置的示意性框图。
具体实施方式
下面将结合附图对本公开实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本公开一部分实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，也属于本发明保护的范围。
图1示出了可以应用本公开的原理的一种网络的示意图。如图1所示，例如，用户可以通过手机经由服务器连接到家庭网关，从而可以通过家庭网关来控制家用设备(例如，照明设备)。根据本公开的实施例，可以将家用设备分为若干组，建立各组之间的关联关系，并且利用各组之间的关联关系来处理用户的操作请求。
图2A-2B示出了利用组来处理操作请求的示意图，其中，组包括一个或者多个可以执行操作请求的成员。如图2A所示，当接收到来自请求方的操作请求时，所建立的组将该操作请求发送给组中的每个成员，由组中的成员来处理并且执行该操作请求；然后，如图2B所示，当完成对该操作请求的处理时，各个成员将处理结果作为响应进行反馈，以便对各个处理结果进行汇集并且向操作请求的请求方返回处理结果。
根据本公开的实施例，可以针对同一操作请求，建立若干组来处理该操作请求。其中，可以在各组之间建立各种关联关系，例如，备份关系，递进关系或者并列关系等等。可选地，例如，备份关系是指针对同一操作请求，至少两个组之间存在备份关系，如图3A所示，当其中一个组的成员未能成功执行该操作请求时，将该操作请求转发给属于备份关系的另一组，启动该另一组的成员来执行该操作请求；换句话说，针对该操作请求，这两个组之间是备份关系，以保证至少一组的成员能够成功执行该操作请求。可选地，例如，递进关系是指针对同一操作请求，至少两个组之间存在递进关系，如图3B所示，当其中一个组的成员已成功执行该操作请求时，再将该操作请求转发给属于递进关系的另一组，启动该另一组的成员也执行该操作请求；换句话说，针对该操作请求，这两个组之间是递进关系，以实现在第一组的成员成功执行该操作请求的情况下，启动至少另一组的成员也执行该操作请求。可选地，例如，并列关系是指针对同一操作 请求，至少两个组之间存在并列关系，如图3C所示，当将操作请求发送给第一组时，通过查询与第一组对应的资源下的关联标识符和关联属性值，确定与第一组属于并列关系的另一组；由此，在启动第一组的成员来执行该操作请求时，也启动与第一组属于并列关系的另一组的成员来处理该操作请求。换句话说，针对该操作请求，这两个组之间是并列关系，以实现在第一组的成员和第二组的成员分别执行该操作请求。在这种情况下，可以利用多个组并行地对操作请求进行处理。
尽管在以上针对组之间的关联关系进行了描述，然而，应理解，上述的备份关系、递进关系以及并列关系仅仅是为了解释本公开的原理所作的示例性说明。对于本领域技术人员而言，根据业务需求，还可以在组之间建立其它的关联关系，例如，互锁关系等关联关系。可选地，如图3D所示，互锁是指至少两个组之间存在互锁关系，当一个组成功执行操作请求时，禁止启动与该组存在互锁关系的另一组。换句话说，针对该操作请求，这两个组之间是互锁关系，以实现在第一组的成员或者第二组的成员单独执行该操作请求，而不是第一组的成员和第二组的成员混合执行该操作请求。本公开的实施例仅仅是例示性的而不是穷举性的，因此，本公开的原理也能够应用到具有其它的关联关系的组而产生新的实施方式，这样的实施方式也未脱离本发明的范围。
以下将结合物联网M2M架构下的组管理场景来说明本公开的原理。然而，应理解，本公开的原理不限于这种具体情形。实际上，在采用其它网络架构协议的情况下，也可以实现本公开的原理。图4是根据本公开的实施例的在组的资源中添加关联标识符和关联属性值的示意图。如图4所示，在资源类型的组下，增加了两个属性，分别是关联标识符relatedGroup和关联属性值relationshipofGroups。其中，关联标识符relatedGroup可以指示与一实体组关联的资源(例如，其它实体组)的标识符，关联属性值relationshipofGroups可以指示该实体组与其它资源(例如，其它实体组)的关联关系，例如，备份关系、递进关系、并列关系、互锁关系等等。可选地，在关联标识符relatedGroup中设置与一实体组存在关联关系的其它资源的标识符，例如，可以设置与该实体组关联的其它实体组的资源标识ID，或者资源名称。
由此，可以根据实体组资源下设置的关联标识符和关联属性值，查询 到与该实体组相关联的其它资源(例如其它实体组)的标识以及它们之间的关联关系，从而可以利用多个实体组的成员来处理来自请求方的操作请求，在批量成员中实施操作请求所对应的操作指令，提升了设备管理的自动化水平和管理效率。
以下结合图5来描述根据本公开一实施例的利用添加的关联标识符relatedGroup和关联属性值relationshipofGroups来实现多个组对来自请求方的操作请求进行处理的过程。
根据本公开的原理，可以在管理服务器，例如在M2M协议框架下，可以在通用服务实体CSE上设置组的属性，例如，设置对应于第一组的group资源下的关联标识符relatedGroup和关联属性值relationshipofGroups。为简便起见，在图5图示的实施例中，采用两个组，即第一组A和第二组B进行说明，其中每个组包括至少一个可以执行请求方的操作请求的成员。例如，设置对应于第一组A的group资源下的关联标识符relatedGroup指向第二组B的标识符，并且可以将关联属性值relationshipofGroups设置为备份关系。由此，将第一组A和第二组B进行了关联，并且将它们之间的关联关系设置为备份关系。如图5所示，一实体向管理服务器发出操作请求，例如应用实体AE向通用服务实体CSE发出操作请求。在接收到该操作请求时，CSE对该请求进行处理，取得执行该操作请求的组以及该组成员的信息，并且将该操作请求转发给该组的所有成员。在图5所示的示例中，CSE取得有关第一组A以及第一组A的成员的信息，并且将该操作请求转发给第一组A中的所有成员。可选地，在CSE对该操作请求进行处理时，可以首先对该操作请求的请求方进行身份验证，待成功通过身份验证之后，再选择用于执行该操作请求的组。如图5所示，在接收到来自CSE发送的操作请求时，第一组A所包括的所有成员都被启动来执行该操作请求，并且将执行的结果作为反馈返回给CSE。CSE接收第一组A内的所有成员返回的执行结果，并且对结果进行分析汇集以判断该操作请求是否被成功执行。在第一组A包括不止一个成员时，可以设定各种策略来确定该操作请求是否被成功执行。例如，可以设定如下策略：只有第一组A中所有成员均已成功执行了该操作请求时，才确定该操作请求已被第一组A成功执行。或者，可以设定：只要第一组A中的一半以上成员均已成功执行了该操作请求时，就确定该操作请求已 被组A成功执行。具体的判断策略可以根据业务需求来确定，在此不作限制。或者，可以根据关联属性值来确定操作请求是否被成功执行。例如，对关联属性值指示的关联关系进行细分，例如，如果关联属性值指示的备份关系属于完全备份关系，则当组A中所有成员处理操作请求失败后启动组B的成员处理该操作请求，而当备份关系属于部分备份关系时，则当组A中部分成员处理操作请求失败后就可启动组B处理该操作请求，其他关系可以类推，在此不再赘述。如图5所示，如果经过分析汇集来自第一组A的成员的响应后，CSE确定该操作请求未能被第一组A成功执行，换句话说，第一组A执行该操作请求被判定为失败，则可以通过查询所设置的第一组A的group资源下的关联标识符和关联属性值来确定第一组A的备份组。例如，如果对应于第一组A的group资源下的关联标识符relatedGroup指向第二组B的标识符，并且关联属性值relationshipofGroups被设置为备份关系，则可以确定第二组B是第一组A的备份组。此时，可以触发作为备份组的第二组B来执行该操作请求。具体地，CSE取得有关第二组B以及第二组B的成员的信息，并且将该操作请求转发给组B中的所有成员。如图5所示，在接收到来自CSE发送的操作请求时，第二组B所包括的所有成员都被启动来执行该操作请求，并且将执行的结果作为反馈返回给CSE。CSE接收第二组B内的所有成员返回的执行结果，并且对结果进行分析汇集以判断该操作请求是否被成功执行。同样地，在第二组B包括不止一个成员时，可以设定各种策略来确定该操作请求是否被成功执行。随后，CSE可以向请求方返回执行该操作请求的反馈信息。例如，当无论是第一组A还是第二组B成功执行了该操作请求时，CSE向请求方返回成功执行该操作请求的响应。相反，只有在第一组A和第二组B执行该操作请求均失败的情况下，CSE才向请求方返回执行该操作请求失败的信息。
为使得本公开的上述实施例更加直观，以下以一个具体应用示例来对该实施例的方案进行说明。例如，在以上图1的图示的情境下，用户的手机可以通过无线网络访问家中的家用网关，在该手机内安装了可以通过家用网关的应用程序来远程控制家用设备的应用程序，例如可以通过家用网关的应用程序来控制用户家中的照明设施(例如，各个房间的灯)、调温设施(例如，房间的空调或者取暖设施)，或者卫浴设施(例如电热水器)、 烹饪设施(例如电饭锅)等等。在此，手机中的应用程序可以作为图5中发送操作请求的请求方，即发出请求的实体，而家用网关中对应的应用程序可以作为管理服务器或者通用服务实体CSE，并且可以创建分别对应于家中的不同类型的设施的应用实体组，例如，分别对应于照明设施、调温设施、或者卫浴设施的组，组中包括可以执行操作请求(例如，执行开启相应设施的操作请求)的成员。例如，在接收到启动操作请求时，打开房间中的灯、开启空调或者采暖器、启动电热水器而进行加热，从而使得用户到家时，各种设施均已准备好。可选地，也可以将一个房间的设施设置为一个组，具体方式不作限定，在这种情况下，一个组可以包括不同类型的应用实体，在接收到启动操作时，房间中的各个实体均被启动。作为示例，用户可以预先在家用网关的应用程序中设置相应的组，并且将各个组相关联。
作为另一示例，用户可以在手机的应用程序中设置与用户住宅的门禁系统相关的功能。当用户的手机接近门禁系统时，门禁系统对用户身份进行验证。在通过验证之后，门禁系统开启，并且同时向家用网关发出开启门厅的灯的操作请求。例如，门厅的灯可以被分为互为备份关系的两组灯，建立对应于第一组灯和第二组灯的两个组，并将其相关联。家用网关中的CSE首先向第一组灯发出启动命令以便开启第一组灯，并且接收来自第一组灯的响应。如果接收到第一组灯返回的响应，CSE判断第一组灯出现故障而未能开启，则CSE查询与第一组对应的group资源下的关联标识符和关联属性值，从而启动作为备份关系的第二组灯。这样以来，即便第一组灯出现某种故障而无法打开时，也能够及时开启第二组灯，实现对灯的冗余控制，从而在用户通过门禁系统进入门厅时，门厅的一组灯已经开启，避免了用户摸黑开灯的不便。
在上述示例中，由于建立了两个实体组之间的备份关系，并且将其相关联，从而实现了冗余控制，可以在其中一个实体组的成员出现故障未能执行操作请求时，及时启动另一实体组的成员来执行操作请求，提高了自动化的水平和管理效率。
以下结合图6来描述根据本公开另一实施例的利用添加的关联标识符relatedGroup和关联属性值relationshipofGroups来实现多个组对来自请求方的操作请求进行处理的过程。
在本实施例中，也采用第一组A和第二组B进行说明，其中每个组包括至少一个可以执行请求方的操作请求的成员。例如，设置对应于第一组A的group资源下的关联标识符relatedGroup指向第二组B的标识符，并且可以将关联属性值relationshipofGroups设置为递进关系。由此，将第一组A和第二组B进行了关联，并且将它们之间的关联关系设置为递进关系。如图6所示，可选地，第一组A可以向管理服务器(例如，通用服务实体CSE)订阅应用实体请求，以便在CSE接收到来自应用实体的操作请求时，可以及时通知第一组，以便触发第一组A的成员处理该操作请求。如图6所示，一实体向管理服务器发出操作请求，例如应用实体AE向通用服务实体CSE发出操作请求。在接收到该操作请求时，CSE对该请求进行处理，取得执行该操作请求的组以及该组成员的信息，并且将该操作请求转发给该组的所有成员。在图6所示的示例中，CSE取得有关第一组A以及第一组A的成员的信息，并且将该操作请求转发给第一组A中的所有成员。可选地，在CSE对该操作请求进行处理时，可以首先对该操作请求的请求方进行身份验证，待成功通过身份验证之后，再向订阅了应用实体请求的第一组A通知该操作请求。如图6所示，在接收到来自CSE发送的操作请求时，第一组A所包括的所有成员都被启动来执行该操作请求，并且将执行的结果作为反馈返回给CSE。CSE接收第一组A内的所有成员返回的执行结果，并且对结果进行分析汇集以判断该操作请求是否被成功执行。在第一组A包括不止一个成员时，可以设定各种策略或根据关联属性值来确定该操作请求是否被成功执行。例如，可以设定：只有第一组A中所有成员均已成功执行了该操作请求时，才确定该操作请求已被第一组A成功执行。或者，可以设定：只要第一组A中的一半以上成员均已成功执行了该操作请求时，就确定该操作请求已被第一组A成功执行。具体的判断策略可以根据业务需求来确定，在此不作限制。如图6所示，如果经过分析汇集来自第一组A的成员的响应后，CSE确定该操作请求已经被第一组A成功执行，则可以通过查询所设置的第一组A的group资源下的关联标识符和关联属性值来确定与第一组A属于递进关系的组。例如，如果对应于第一组A的group资源下的关联标识符relatedGroup指向第二组B的标识符，并且关联属性值relationshipofGroups被设置为递进关系，则可以确定第二组B是第一组A的递进关系的组。 此时，可以触发作为递进关系的第二组B也来执行该操作请求。具体地，CSE取得有关第二组B以及第二组B的成员的信息，并且将该操作请求转发给组B中的所有成员。如图6所示，在接收到来自CSE发送的操作请求时，第二组B所包括的所有成员都被启动来执行该操作请求，并且将执行的结果作为反馈返回给CSE。CSE接收第二组B内的所有成员返回的执行结果，并且对结果进行分析汇集以判断该操作请求是否被成功执行。同样地，在第二组B包括不止一个成员时，可以设定各种策略来确定该操作请求是否被成功执行。随后，CSE可以向请求方返回执行该操作请求的反馈信息。在递进关系下，例如，只有当第一组A和第二组B均成功执行了该操作请求时，CSE才向请求方返回成功执行该操作请求的响应。换句话说，只要有一个组未能成功执行该操作请求，则CSE会向请求方返回执行该操作请求失败的信息。
作为示例，例如，在以上图1的图示的情境下，用户的手机可以通过无线网络访问家中的家用网关，在该手机内安装了可以通过家用网关来远程控制家用设备的应用程序，例如可以通过家用网关的应用程序(作为管理服务器CSE)来控制用户家中的照明设施(例如，各个房间的灯)、调温设施(例如，房间的空调或者取暖设施)，或者卫浴设施(例如电热水器)等等。在此，手机中的应用程序可以作为图6中发送操作请求的请求方，即发出请求的实体，而家用网关中对应的应用程序可以作为管理服务器或者通用服务实体CSE，并且可以创建分别对应于家中的不同类型的设施的应用实体组，例如，分别对应于照明设施、调温设施、或者卫浴设施的组，组中包括可以执行操作请求(例如，执行开启相应设施的操作请求)的成员。例如，在接收到启动操作请求时，打开房间中的灯、开启空调或者采暖器、启动电热水器而进行加热，从而使得用户到家时，各种设施均已准备好。可选地，也可以将一个房间的设施设置为一个组，具体方式不作限定，在这种情况下，组中可以包括不同类型的应用实体，在接收到启动操作时，房间中的各个实体均被启动。作为示例，用户可以预先在家用网关的应用程序中设置相应的组，并且将各个组相关联。
作为另一具体应用示例，例如，用户可以在作为管理服务器的家用网关的应用程序中创建两个组，将客厅的空调作为第一组设施的应用实体，将卫生间的电热水器作为第二组设施的应用实体，并且将二者作为递进关 系的组进行关联。此外，针对与客厅的空调对应的第一组A，在家用网关的应用程序上(例如，CSE)上设置了订阅应用实体请求。由此，在CSE接收到来自相应的应用实体的请求时，可以向第一组A发送通知，从而触发第一组A的成员来执行相应的操作请求。例如，用户在回家的路上利用手机的应用程序向家用网关发出开启设施的操作请求，例如启动命令“ON”。在接收到来自用户的手机的应用程序(例如应用实体AE)的操作请求并且通过验证之后，家用网关上的CSE向订阅了应用实体请求的第一组A发送通知请求，从而启动第一组A的成员执行对应的操作请求。在本示例中，第一组A中的成员，即，客厅的空调被开启，控制合适的室温。然后，第一组A向CSE返回通知响应消息。在接收到来自第一组A的通知响应消息之后，CSE汇集并分析该通知响应消息，判断第一组A是否成功执行了该操作请求。在判断客厅的空调已被成功开启之后，CSE查询对应于第一组A的group资源下的关联标识符和关联属性值，查询到与第一组A关联的组是第二组，并且它们之间的关联关系是递进关系。由此，CSE向第二组B发送操作请求，从而启动作为递进关系的第二组B。第二组B的成员，即与卫生间的电热水器对应的应用实体AE在接收到来自CSE的操作请求时，启动卫生间的电热水器，开始加热，并且在加热到预定水温时保持水温。用户通过手机上的应用程序只需向家用网关发出一个操作请求，根据家用网关的应用程序中的有关应用实体组的设置，可以自动启动与作为递进关系的应用实体组对应的设施，免去了用户分别向各个实体组发送操作请求的繁琐的步骤，节省了数据通信流量，提升了设施的管理效率。
在上述示例中，由于建立了两个实体组之间的递进关系，并且将其相关联，从而实现了利用简单的操作指令对相关联的多组设施进行控制，在其中与一组设施对应的一组实体成功执行了操作请求之后，及时启动与另一组设施对应的实体组的成员来执行操作请求，提高了自动化的水平和管理效率。
尽管在本公开的上述实施例中，作为示例，第一组A和第二组B分别仅仅包括一个成员，但是应理解，根据需要，第一组和第二组可以包括不止一个成员。此外，本公开的原理也不限于两个组，组中的成员也不限于同一类型，只要组中的成员可以处理同一操作请求即可。
另外，在上述实施例中，设置了第一组向CSE订阅应用实体请求，从而可以在CSE接收到来自应用实体的操作请求时，触发第一组的成员对操作请求进行处理。然而，还可以存在CSE在接收到请求方发送的应用实体请求时自动触发第一组的其它方式，例如，在CSE接收到来自请求方的操作请求时，直接转发给第一组的成员；或者，CSE定时向第一组成员转发来自请求方的操作请求，本公开对此不作限制。
以下结合图7来描述根据本公开又一实施例的利用添加的关联标识符relatedGroup和关联属性值relationshipofGroups来实现多个组对来自请求方的操作请求进行处理的过程。
在本实施例中，也采用第一组A和第二组B进行说明，其中每个组包括至少一个可以执行请求方的操作请求的成员。例如，设置对应于第一组A的group资源下的关联标识符relatedGroup指向第二组B的标识符，并且可以将关联属性值relationshipofGroups设置为并列关系。由此，将第一组A和第二组B进行了关联，并且将它们之间的关联关系设置为并列关系。如图7所示，可选地，第一组A可以向管理服务器(例如，通用服务实体CSE)订阅应用实体请求，以便在CSE接收到来自请求方的操作请求时，可以将该操作请求发送给第一组A。如图7所示，一实体向管理服务器发出操作请求，例如应用实体AE向通用服务实体CSE发出操作请求。在接收到该操作请求时，CSE对该请求进行处理，取得执行该操作请求的组以及该组成员的信息，并且将该操作请求转发给该组的所有成员。在图7所示的示例中，CSE取得有关第一组A以及第一组A的成员的信息，并且将该操作请求转发给第一组A中的所有成员。类似地，在CSE对该操作请求进行处理时，可以首先对该操作请求的请求方进行身份验证，待成功通过身份验证之后，再向订阅了应用实体请求的第一组A通知该操作请求。如图7所示，在接收到来自CSE发送的操作请求时，第一组A所包括的所有成员都被启动来执行该操作请求，并且将执行的结果作为反馈返回给CSE。此外，CSE通过查询所设置的第一组A的group资源下的关联标识符和关联属性值来确定与第一组A属于并列关系的组。例如，如果对应于第一组A的group资源下的关联标识符relatedGroup指向第二组B的标识符，并且关联属性值relationshipofGroups被设置为并列关系，则可以确定第二组B是第一组A的并列关系的组。此时，可以触发作为 并列关系的第二组B的成员也来执行该操作请求。具体地，CSE取得有关第二组B以及第二组B的成员的信息，并且将该操作请求转发给组B中的所有成员。如图7所示，在接收到来自CSE发送的操作请求时，第二组B所包括的所有成员都被启动来执行该操作请求，并且将执行的结果作为反馈返回给CSE。CSE接收第一组A以及第二组B内所有成员返回的执行结果，并且对结果进行分析汇集以判断该操作请求是否被成功执行。在第一组A包括不止一个成员时，可以设定各种策略或根据关联属性值来确定该操作请求是否被第一组A被成功执行，例如，可以设定：只有第一组A中所有成员均已成功执行了该操作请求时，才确定该操作请求已被第一组A成功执行。或者，可以设定：只要第一组A中的一半以上成员均已成功执行了该操作请求时，就确定该操作请求已被第一组A成功执行。具体的判断策略可以根据业务需求来确定，在此不作限制。类似地，在第二组B包括不止一个成员时，也可以设定各种策略来确定该操作请求是否被第二组B被成功执行。然后，CSE向请求方返回操作响应，即，将第一组A的执行结果和第二组B的执行结果均返回给请求方，使得请求方可以基于接收到的操作响应，决定下一步的动作。例如，可以对返回执行失败的操作响应的组触发其备份组来执行操作请求。
在上述实施例中，利用第一组向CSE订阅应用实体请求，将第一组设置为与第二组相关联，并且将关联关系设置为并列关系，从而可以在CSE接收到来自应用实体的操作请求时，自动地向订阅了应用实体请求的第一组发送通知消息，从而触发第一组的成员执行该操作请求；同时，由于第二组和第一组相关联，可以通过查询所设置的第一组A的group资源下的关联标识符和关联属性值而找到第二组B，并且触发第二组B的成员也执行该操作请求。由此，可以避免用户端分别向各个组发送操作请求的繁琐的步骤，节省了数据通信流量，提升了自动化水平和针对组的管理效率。
作为示例，例如，在以上图1的图示的情境下，用户的手机可以通过无线网络访问家中的家用网关，在该手机内安装了可以通过家用网关来远程控制家用设备的应用程序，例如可以通过家用网关的应用程序(作为管理服务器CSE)来控制用户家中的各个设施，例如照明设施、调温设施、卫浴设施或者烹饪设施等等。在此，手机中的应用程序可以作为图7中发 送操作请求的请求方，即发出请求的实体，而家用网关中对应的应用程序可以作为管理服务器或者通用服务实体CSE，并且可以创建分别对应于家中的不同类型的设施的应用实体组，例如，分别对应于照明设施、调温设施、卫浴设施或者烹饪的组，组中包括可以执行操作请求(例如，执行开启相应设施的操作请求)的成员。可选地，也可以将一个房间的设施设置为一个组，具体方式不作限定，在这种情况下，组中可以包括不同类型的应用实体，在接收到启动操作时，房间中的各个实体均被启动。作为示例，用户可以预先在家用网关的应用程序中设置相应的组，并且将各个组相关联。
作为另一具体应用示例，例如，用户可以在作为管理服务器的家用网关的应用程序中创建两个组，将厨房的电饭锅作为第一组设施的应用实体，将卫生间的洗衣机作为第二组设施的应用实体，并且将二者作为并列关系的组进行关联。用户在早上出门上班之前，可以将米和水放入电饭锅，并且将须洗的衣物放入洗衣机，并且设置好煮饭和洗衣的时长。此外，针对与洗衣机对应的第一组A，在家用网关的应用程序上(例如，CSE)上设置了订阅应用实体请求。由此，在CSE接收到来自相应的应用实体的请求时，可以向第一组A发送通知，从而触发第一组A的成员来执行相应的操作请求。例如，用户在下班前可以利用手机的应用程序向家用网关发出开启设施的操作请求，例如启动命令“ON”。在接收到来自用户的手机的应用程序(例如应用实体AE)的操作请求(例如“ON”)并且通过验证之后，家用网关上的CSE向订阅了应用实体请求的第一组A发送通知请求，从而启动第一组A的成员执行对应的操作请求。在本示例中，启动第一组A中的成员，即，启动电饭锅开始煮饭。同时，由于第一组A与第二组B相关联，CSE可以通过查询所设置的第一组A的group资源下的关联标识符和关联属性值而找到第二组B，并且触发第二组B的成员也执行该操作请求。在本示例中，可以启动洗衣机开始洗衣。
随后，第一组A向CSE返回通知响应消息，而第二组B向CSE反馈操作响应。CSE分析汇集第一组A和第二组B的响应，并且将二者的响应均反馈给请求方，例如，用户的手机上的应用程序，使得用户可以及时得到操作请求的执行结果，并且可以采取相应的下一步动作。
在上述示例中，针对第一组A，在CSE上订阅应用实体请求，并且将 第二组B与第一组A进行并列关联，由此，可以避免用户向家用网关分别发送针对第一组和第二组的操作请求，也就是说，在本示例中，无需用户通过手机向家用网关分别发送控制电饭锅和洗衣机的操作指令，节省了数据通信流量，提升了自动化水平和对设施的管理效率。
在上述示例中，由于建立了两个实体组之间的并列关系，并且将其相关联，从而实现了利用简单的操作指令对相关联的多组设施进行控制，只需向其中的一组设施对应的实体发送操作请求，就可以启动彼此相关联的多组设施来执行操作请求，提高了自动化的水平和管理效率。
类似地，在上述实施例中，为便于说明，第一组A和第二组B分别仅仅包括一个成员，但是应理解，根据需要，第一组和第二组可以包括不止一个成员，组中的成员也不限于同一类型，只要组中的成员可以处理同一操作请求(例如，启动或者关闭的请求)即可。
以上结合具体示例对本公开一些实施例进行说明，并且分别针对关联组的备份关系、递进关系和并列关系详细说明了本原理的主要实施过程。应注意，尽管在上述实施例中主要针对智能家居的情境进行了描述，然而，本公开的原理还可以应用到众多领域，例如，工业控制、安保消防、智能交通等等领域，在此不作限制。注意到，上述实施例针对于已经建立了想要进行关联的组的情况。在以下实施例中，将结合组的建立过程来进一步描述本公开的原理。
如图8所示，在通用服务实体CSE上为组资源group添加如图4所示的关联标识符relatedGroup和关联属性值relationOfGroups两个属性。当某个应用实体想要在CSE上创建组资源时，其向CSE发送创建组的请求。在接收到创建组的请求时，CSE在通过验证之后，创建相应的组，例如创建组1和组2，其中，每个组可以包括多个应用实体；然后，CSE向作为请求方的应用实体返回组创建完成的响应。在接收到组已经创建完成的响应时，该应用实体可以根据需要请求设置组的属性，例如，设置组1的属性，其中，将组1的group资源下的关联标识符relatedGroup设置为组2的标识符，并且将关联属性值relationOfGroups设置为例如备份。相应地，CSE向该应用实体返回组属性设置响应，从而完成针对该应用实体的组的设置请求。在该应用实体向CSE发送操作请求(例如，该应用实体可以通过update请求设置组1的相关资源属性值来实现)时，CSE首先向组1 的成员发送执行该操作请求的指令，组1的成员在接收到该指令时，执行该操作请求，并且向CSE返回执行的结果作为响应。CSE接收来自组1的成员的执行响应，并且判断组1的成员是否成功执行了该操作请求。如果未能成功执行，则CSE通过查询组1的group资源下的关联标识符relatedGroup和关联属性值relationOfGroups，从而向所关联的作为备份组的组2的成员发送执行该操作请求的指令。类似地，在对该操作请求执行后，组2的成员向CSE返回执行响应。CSE在汇集分析组2的成员的执行响应后，向作为请求方的该应用实体发送执行该操作请求的响应；例如，如果组2的成员成功地执行了该操作响应，则CSE向作为请求方的应用实体发送成功执行操作请求的响应。
以上结合图8例示了本公开的原理针对一应用实体的请求，从创建相关联的各组到利用相关联的各组来处理来自于该应用实体的操作请求的过程。应注意，以上以备份关系为例，然而，针对于递进关系、并列关系，或者例如互锁关系等等关联关系，也完全能够应用本公开的原理，在此不再赘述。
与图8所示的过程稍有不同，图9图示了由不同的应用实体来分别发出创建组的请求和利用所创建的组来执行操作请求的示例。如图9所示，在通用服务实体CSE上为组资源group添加如图4所示的关联标识符relatedGroup和关联属性值relationOfGroups两个属性。当接收到来自应用实体A发送的创建组请求时，CSE创建例如两个组，组1和组2，每个组包括多个应用实体；然后，CSE向应用实体A发送成功创建组的响应；随后，应用实体A向CSE发送设置组的属性的请求，相应地，CSE将组1的关联标识符设置为组2的标识符，例如，组2的ID或者名称，即，relatedGroup＝group2，并且将关联属性值设置为例如备份，即，relationshipOfGroups＝backup，随后CSE向应用实体A发送设置组属性的响应，从而完成对组的关联设置。如上所述，与图8不同，可以由另一实体，例如应用实体B向CSE发送操作请求，例如，该请求可以通过update请求设置组1相关的资源来实现。当接收到来自应用实体B的操作请求时，CSE向组1的成员发送执行该操作请求的指令，相应地，组1的各成员执行该操作请求，并且向CSE返回执行操作请求的结果作为响应。CSE汇集分析组1的成员返回的执行结果，并且向应用实体B返回执行操作请求 的响应。在这一点上，CSE可以分析判断组1的成员是否成功执行了该操作请求，并且向应用实体B返回最终的判断结果。或者，CSE也可以将组1的执行响应直接转发给应用实体B，由应用实体B自身来判断组1的成员是否成功执行了该操作请求。无论采用何种方式，在判断组1的成员未能成功执行该操作请求时，可以通过CSE或者应用实体B来查询与组1相关联的组，在确定与组1相关联的组是组2，并且二者之间的关联关系为备份时，应用实体B可以向通用服务实体CSE发送操作请求，由CSE将所述操作请求发送给作为组1的备份的组2的成员来执行该操作请求；相应地，CSE接收组2中的成员发送的作为响应的执行操作请求的结果，并且向应用实体B返回执行操作请求的响应。
在以上结合图9描述的实施例中，设置关联组的应用实体和利用关联组来执行操作请求的实体是不同的实体。在实际应用中，设置关联组的应用实体和利用关联组来执行操作请求的实体也可以位于不同的硬件终端上。例如，在以上利用手机来控制家用设施的情境下，可以由一部手机作为主机，发送设置关联组的请求给家用网关，从而为各个家用设施设置关联组，而其它手机作为从机，可以向家用网关发送有关操作请求，以便利用作为主机的手机所设置的关联组来执行操作请求。
图10图示了根据本公开实施例的一种处理操作请求的方法，包括步骤：S1010，接收一实体的操作请求；S1020,将该操作请求发送给第一实体组进行处理；S1030，确定与第一实体组相关联的至少一个第二实体组；以及S1040，将所述操作请求发送给所述至少一个第二实体组对该操作请求进行处理。
将所述操作请求发送给所述至少一个第二实体组对该操作请求进行处理，即，将所述操作请求发送给每一个确定出的所述第二实体组。
可选地，该方法还包括：将第一实体组与所述至少一个第二实体组关联。
其中，所述的每个实体组包括至少一个用于处理操作请求的成员。
可选地，该方法还包括：在与第一实体组对应的资源中增加关联标识符和关联属性值，其中，关联标识符指示与第一实体组关联的实体组的标识符，关联属性值指示第一实体组与该实体组的关联关系。
可选地，其中，将第一实体组与至少一个第二实体组相关联包括：将关联标识符的值设置为第二实体组的标识符，并且将关联属性值设置为指示属 于备份关系、递进关系或者并列关系中的至少一种的关联关系。
可选地，该方法还包括：查询与第一实体组对应的资源中所包括的关联标识符和关联属性值，来确定与第一实体组相关联的第二实体组以及第二实体组与第一实体组之间的关联关系。
可选地，其中，将该操作请求发送给第一实体组进行处理包括：将操作请求发送给第一实体组的各成员来处理该操作请求，并且接收第一实体组的各成员返回的处理结果。
可选地，该方法还包括：当返回的处理结果指示该操作请求未能被成功处理时，启动与该第一实体组属于备份关系的第二实体组包括的成员来处理该操作请求。换句话说，所述方法还包括：确定所述第一实体组和所述至少一个第二实体组之间的关联关系为备份关系；其中，当返回的处理结果指示该操作请求未能被成功处理时，将该操作请求发送给所述至少一个第二实体组进行处理。
可选地，该方法还包括：当返回的处理结果指示该操作请求已经被成功处理时，启动与该第一实体组属于递进关系的第二实体组包括的成员来处理该操作请求。换句话说，所述方法还包括：确定所述第一实体组和所述至少一个第二实体组之间的关联关系为递进关系；
其中，当返回的处理结果指示该操作请求已经被成功处理时，将该操作请求发送给所述至少一个第二实体组进行处理。
可选地，该方法还包括：启动第一实体组包括的成员来处理该操作请求，并且启动与第一实体组属于并列关系的第二实体组包括的成员来处理该操作请求。具体的，确定所述第一实体组和所述至少一个第二实体组之间的关联关系为并列关系；其中，将所述操作请求发送给第一实体组后，将所述操作请求发送给所述至少一个第二实体组进行处理，而无需等待第一实体组返回处理结果。
可选地，该方法还包括：汇集处理操作请求的实体组的成员返回的处理结果，并且将所述处理结果反馈给发出操作请求的实体。
可选地，该方法还包括：接收创建实体组的请求，创建第一实体组和至少一个第二实体组。
可选地，创建实体组的请求和操作请求来自于相同或者不同的实体。
可选地，该方法还包括：汇集处理操作请求的实体组返回的处理结果， 并且将所述处理结果反馈给发出操作请求的实体，包括：
汇集第一实体组的所有成员的处理结果作为第一实体组的处理结果；以及在该至少一个第二实体组对该操作请求进行处理的情况下，汇集该至少一个第二实体组的所有成员的处理结果作为第二实体组的处理结果；对第一实体组的处理结果和至少一个第二实体组的处理结果进行逻辑运算来获得最终的处理结果，并且将其反馈给发出该操作请求的实体。
可选地，实体组的标识符包括：与该实体组对应的资源的资源标识或者资源名称。
可选地，该方法还包括：接收来自第一实体组的订阅应用实体的请求；以及在接收到来自应用实体的操作请求时，自动向第一实体组发送通知从而启动第一实体组的成员来处理该操作请求。
图11图示了根据本公开实施例的另一种处理操作请求的方法，包括步骤：S1110，发送操作请求以启动第一实体组来处理该操作请求；以及S1120,根据第一实体组的处理结果，将该操作请求发送给与该第一实体组相关联的至少一个第二实体组进行处理。
其中，与第一实体组对应的资源包括关联标识符和关联属性值，关联标识符指示与第一实体组相关联的该至少一个第二实体组的标识符，关联属性值指示第一实体组与该至少一个第二实体组的关联关系；其中第一实体组对应的资源中的关联标识符的值被设置为该至少一个第二实体组的标识符，并且关联属性值指示第一实体组与第二实体组存在的关联关系。
可选地，所述关联关系为：备份关系、递进关系、并列关系或者互锁关系。
在一种实施方式中，所述方法还包括确定所述第一实体组和所述至少一个第二实体组之间的关联关系为备份关系；
其中，
当返回的处理结果指示该操作请求未能被成功处理时，将该操作请求发送给所述至少一个第二实体组进行处理。
在一种实施方式中，所述方法还包括确定所述第一实体组和所述至少一个第二实体组之间的关联关系为递进关系；
其中，
当返回的处理结果指示该操作请求已经被成功处理时，将该操作请求发 送给所述至少一个第二实体组进行处理。
在一种实施方式中，所述方法还包括：确定所述第一实体组和所述至少一个第二实体组之间的关联关系为并列关系；其中，
将所述操作请求发送给第一实体组后，将所述操作请求发送给所述至少一个第二实体组进行处理。
可选地，该方法还包括：根据与第一实体组对应的资源，确定与第一实体组相关联的该至少一个第二实体组。
可选地，与第一实体组对应的资源包括关联标识符和关联属性值，关联标识符指示与第一实体组相关联的该至少一个第二实体组的标识符，关联属性值指示第一实体组与该至少一个第二实体组的关联关系。
可选地，该至少一个第二实体组的标识符包括：与该至少一个第二实体组对应的资源的资源标识或者资源名称。
可选地，其中第一实体组对应的资源中的关联标识符的值被设置为该至少一个第二实体组的标识符，并且关联属性值被设置为指示属于备份关系、递进关系或者并列关系中的至少一种的关联关系。
可选地，该方法还包括：接收第一实体组的成员返回的处理结果；当返回的处理结果指示该操作请求未能被成功处理时，启动与该第一实体组属于备份关系的第二实体组包括的成员来处理该操作请求。
可选地，该方法还包括：接收第一实体组的成员返回的处理结果；当返回的处理结果指示该操作请求已经被成功处理时，启动与该第一实体组属于递进关系的第二实体组包括的成员来处理该操作请求。
可选地，该方法还包括：启动与第一实体组属于并列关系的第二实体组包括的成员来处理该操作请求。
根据本公开的一方面，还提供了一种控制装置。如图12所示，其包括：收发器1200，接收一实体的操作请求，并且将该操作请求发送给第一实体组进行处理；以及处理器1220，确定与第一实体组相关联的至少一个第二实体组，并指示收发器将该操作请求发送给所述至少一个第二实体组进行处理。
根据本公开的另一方面，还提供了一种通信装置。如图13所示，其包括：收发器1300，发送操作请求以启动第一实体组来处理该操作请求；以及处理器1320，根据第一实体组的处理结果，指示收发器将该操作请求发送给与该第一实体组相关联的至少一个第二实体组进行处理。
根据本公开的又一方面，还提供了一种控制装置，该控制装置包括处理器、与处理器连接的存储器以及收发器，其中，存储器存储指令，处理器被配置为在运行存储器存储的指令时，执行以下步骤：指示收发器接收一实体的操作请求，并且将该操作请求发送给第一实体组进行处理；处理器确定与第一实体组相关联的至少一个第二实体组，并且启动该至少一个第二实体组来处理该操作请求。
可选地，上述通信装置是用户终端，包括但不限于以下中的至少一种：智能手机、PDA、平板电脑、导航仪。
可选地，上述控制装置包括但不限于以下中的至少一种：服务器、网关、机顶盒。
然而，本领域技术人员应理解，本说明书中出现的框图表示实施本公开的原理的说明性电路的概念图。类似地，应理解，任何流程表、流程图、状态转移图、伪代码等表示可在计算机可读介质中被实质性表示并由计算机或处理器执行的各种过程，不论这些计算机或处理器是否明确地显示出来。可在短暂性状态(信号)和非短暂性状态(例如，在诸如CD-ROM、DVD、蓝光、硬盘驱动器、闪存卡、或其他类型的有形存储介质的有形介质上)中实现写入的计算机可读介质和代码。
图中所示的各种元件的功能可以通过使用专用硬件和能够联合合适的软件执行软件的硬件来提供。当由处理器提供时，该功能可由单个专用处理器或单个共用处理器或其中有一些可以共用的多个独立的处理器提供。并且，明确的使用术语“处理器”或“控制器”不应该被解读为排他性地专指能够执行软件的硬件，而可以没有限制地、隐含地包括数字信号处理器(“DSP”)硬件、用于存储软件的只读存储器(“ROM”)、随机存取存储器(“RAM”)和非易失性存储器。
其他的硬件，常规和/或定制的也可以包括在内。相似地，图中所示的任何开关仅仅是概念性的。它们的功能可以通过操作程序逻辑、专用逻辑、程序控制和专用逻辑交互或者甚至手动进行，实施者可以根据对上下文更加详细的理解来选择特定的技术。
虽然在此处已经示出并详细描述了包含本公开的教导的实施例，本领域技术人员可以容易地设计出许多其他仍然包含这些教导的各种实施例。注意，本领域技术人员可以根据上述教导做出修改和变型。
上面已经描述了一些具体实施例。但是应该了解可以对这些实施例作出修改。例如，不同的实施例的元素可以进行组合、补充、修改和删除，从而获得其他的实施例。此外，本领域的普通技术人员应该了解可以使用其他的结构和处理流程来替换上面已经公开的结构和处理流程，从而获得其它实施例。该其它实施例至少以实质上相同的方式，实现实质上相同的功能，达到本发明公开的实施例提供的实质上相同的效果。相应地，这些以及其他的实施例应该属于本发明的范围。
本申请要求于2016年11月11日递交的中国专利申请第201610994874.2号的优先权，在此全文引用上述中国专利申请公开的内容以作为本申请的一部分。

Claims (21)

  1. 一种处理操作请求的方法，包括：
    接收操作请求；
    将该操作请求发送给第一实体组进行处理；
    确定与第一实体组相关联的至少一个第二实体组；
    将该操作请求发送给所述至少一个第二实体组进行处理。
  2. 根据权利要求1所述的方法，还包括：确定所述至少一个第二实体组与所述第一实体组之间的关联关系。
  3. 根据权利要求2所述的方法，还包括：
    在与第一实体组对应的资源中增加关联标识符和关联属性值，其中，关联标识符指示与第一实体组关联的实体组的标识符，关联属性值指示第一实体组与所述实体组的关联关系；
    将所述关联标识符的值设置为所述至少一个第二实体组的标识符，将所述关联属性值设置为指示第一实体组与所述至少一个第二实体组存在的关联关系。
  4. 根据权利要求2或3所述的方法，其中所述关联关系为备份关系、递进关系、并列关系或者互锁关系。
  5. 根据权利要求4所述的方法，其中，将该操作请求发送给第一实体组进行处理包括：
    启动第一实体组的成员来处理该操作请求，并且接收第一实体组的成员返回的处理结果。
  6. 根据权利要求5所述的方法，还包括：确定所述第一实体组和所述至少一个第二实体组之间的关联关系为备份关系；
    其中，当返回的处理结果指示该操作请求未能被成功处理时，将该操作请求发送给所述至少一个第二实体组进行处理。
  7. 根据权利要求5所述的方法，还包括：确定所述第一实体组和所述至少一个第二实体组之间的关联关系为递进关系；
    其中，当返回的处理结果指示该操作请求已经被成功处理时，将该操作请求发送给所述至少一个第二实体组进行处理。
  8. 根据权利要求5所述的方法，还包括：确定所述第一实体组和所述至少一个第二实体组之间的关联关系为并列关系；
    其中，将所述操作请求发送给第一实体组后，将所述操作请求发送给所述至少一个第二实体组进行处理。
  9. 根据权利要求6-8任一项所述的方法，还包括：
    汇集处理操作请求的实体组返回的处理结果，并且将所述处理结果反馈给发出操作请求的实体。
  10. 根据权利要求9所述的方法，汇集处理操作请求的实体组返回的处理结果，并且将所述处理结果反馈给发出操作请求的实体，包括：
    汇集第一实体组的所有成员的处理结果作为第一实体组的处理结果；以及
    在该至少一个第二实体组对该操作请求进行处理的情况下，汇集该至少一个第二实体组的所有成员的处理结果作为第二实体组的处理结果；
    对第一实体组的处理结果和至少一个第二实体组的处理结果进行逻辑运算来获得最终的处理结果，并且将其反馈给发出该操作请求的实体。
  11. 根据权利要求3-10任一项所述的方法，其中，实体组的标识符包括：与该实体组对应的资源的资源标识或者资源名称。
  12. 根据权利要求1-11任一项所述的方法，该方法还包括：
    接收来自第一实体组的订阅应用实体的请求；以及
    在接收到来自应用实体的操作请求时，向第一实体组发送通知从而启动第一实体组来处理该操作请求。
  13. 一种处理操作请求的方法，包括：
    发送操作请求以启动第一实体组来处理该操作请求；以及
    根据第一实体组的处理结果，将该操作请求发送给与该第一实体组相关联的至少一个第二实体组进行处理。
  14. 根据权利要求13所述的方法，还包括：
    根据与第一实体组对应的资源，确定与第一实体组相关联的该至少一个第二实体组。
  15. 根据权利要求14所述的方法，其中，与第一实体组对应的资源包括关联标识符和关联属性值，关联标识符指示与第一实体组相关联的该至少一个第二实体组的标识符，关联属性值指示第一实体组与该至少一个第二实体 组的关联关系；其中第一实体组对应的资源中的关联标识符的值被设置为该至少一个第二实体组的标识符，并且关联属性值指示第一实体组与第二实体组存在的关联关系。
  16. 根据权利要求15所述的方法，其中所述关联关系为：备份关系、递进关系、并列关系或者互锁关系。
  17. 根据权利要求16所述的方法，还包括确定所述第一实体组和所述至少一个第二实体组之间的关联关系为备份关系；
    其中，
    当返回的处理结果指示该操作请求未能被成功处理时，将该操作请求发送给所述至少一个第二实体组进行处理。
  18. 根据权利要求16所述的方法，还包括确定所述第一实体组和所述至少一个第二实体组之间的关联关系为递进关系；
    其中，
    当返回的处理结果指示该操作请求已经被成功处理时，将该操作请求发送给所述至少一个第二实体组进行处理。
  19. 根据权利要求16所述的方法，还包括：确定所述第一实体组和所述至少一个第二实体组之间的关联关系为并列关系；其中，
    将所述操作请求发送给第一实体组后，将所述操作请求发送给所述至少一个第二实体组进行处理。
  20. 一种控制装置，包括：
    收发器，接收一实体的操作请求，并且将该操作请求发送给第一实体组进行处理；以及
    处理器，确定与第一实体组相关联的至少一个第二实体组，并且指示收发器将该操作请求发送给所述至少一个第二实体组进行处理。
  21. 一种通信装置，包括：
    收发器，发送操作请求以启动第一实体组来处理该操作请求；以及
    处理器，根据第一实体组的处理结果，指示收发器将该操作请求发送给与该第一实体组相关联的至少一个第二实体组进行处理。
PCT/CN2017/102214 2016-11-11 2017-09-19 处理操作请求的方法及装置 WO2018086413A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17870069.6A EP3541013A4 (en) 2016-11-11 2017-09-19 METHOD AND DEVICE FOR REQUESTING A PROCESSING OPERATION
US16/347,649 US11362856B2 (en) 2016-11-11 2017-09-19 Processing operation requesting method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610994874.2 2016-11-11
CN201610994874.2A CN108075908B (zh) 2016-11-11 2016-11-11 处理操作请求的方法及装置

Publications (1)

Publication Number Publication Date
WO2018086413A1 true WO2018086413A1 (zh) 2018-05-17

Family

ID=62109098

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/102214 WO2018086413A1 (zh) 2016-11-11 2017-09-19 处理操作请求的方法及装置

Country Status (4)

Country Link
US (1) US11362856B2 (zh)
EP (1) EP3541013A4 (zh)
CN (1) CN108075908B (zh)
WO (1) WO2018086413A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109120446B (zh) * 2018-08-22 2022-02-15 迈普通信技术股份有限公司 一种零配置启动方法及设备
CN110875945B (zh) 2018-09-04 2023-05-09 京东方科技集团股份有限公司 用于在通用服务实体上进行任务处理的方法、装置和介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140369251A1 (en) * 2012-01-06 2014-12-18 Huawei Technologies Co., Ltd. Method, group server, and member device for accessing member resources
CN104869532A (zh) * 2015-04-28 2015-08-26 北京海尔广科数字技术有限公司 一种群组成员管理方法和装置
WO2016074455A1 (zh) * 2014-11-14 2016-05-19 中兴通讯股份有限公司 组资源更新处理方法、装置、系统及cse
CN105634989A (zh) * 2014-10-28 2016-06-01 中兴通讯股份有限公司 M2m群组及其通告资源创建和信息交互方法

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100347322B1 (ko) * 2000-04-27 2002-08-07 주식회사 하이닉스반도체 Ｉｍｔ-2000 비동기/동기 시스템에서의 제어국 및 기지국ｉｄ 할당방법
US7380008B2 (en) * 2000-12-22 2008-05-27 Oracle International Corporation Proxy system
US20030014533A1 (en) * 2001-07-11 2003-01-16 Greene David P. Method and apparatus for facilitating attention to a communication
US7512715B2 (en) * 2003-09-26 2009-03-31 Nokia Corporation System and method for requesting a resource over at least one network with reduced overhead
WO2011105780A2 (en) * 2010-02-23 2011-09-01 Lg Electronics Inc. A method and an apparatus for initiating a session in home network system
CN102130773B (zh) * 2011-02-25 2012-12-19 华为技术有限公司 群组通信的方法和用于群组通信的装置
WO2013029146A1 (en) * 2011-08-29 2013-03-07 Woznew Inc. System and method for identifying groups of entities
CN103297468B (zh) * 2012-02-29 2017-12-01 华为技术有限公司 针对群组资源的操作方法、群组服务器
EP3170284B1 (en) * 2014-07-18 2023-01-25 Convida Wireless, LLC Enhanced operations between service layer and management layer in an m2m system by allowing the execution of a plurality of commands on a plurality of devices
US9883320B2 (en) * 2014-07-21 2018-01-30 Lg Electronics Inc. Method for processing request message in wireless communication system and apparatus therefor
CN105681210A (zh) 2014-11-14 2016-06-15 中兴通讯股份有限公司 组资源更新处理方法、装置、系统及cse
CN105703979B (zh) * 2014-11-26 2019-02-22 海尔优家智能科技（北京）有限公司 设备联动的方法、用于设备联动的设备和网络设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140369251A1 (en) * 2012-01-06 2014-12-18 Huawei Technologies Co., Ltd. Method, group server, and member device for accessing member resources
CN105634989A (zh) * 2014-10-28 2016-06-01 中兴通讯股份有限公司 M2m群组及其通告资源创建和信息交互方法
WO2016074455A1 (zh) * 2014-11-14 2016-05-19 中兴通讯股份有限公司 组资源更新处理方法、装置、系统及cse
CN104869532A (zh) * 2015-04-28 2015-08-26 北京海尔广科数字技术有限公司 一种群组成员管理方法和装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3541013A4

Also Published As

Publication number Publication date
EP3541013A4 (en) 2020-04-15
CN108075908A (zh) 2018-05-25
EP3541013A1 (en) 2019-09-18
US20210288834A1 (en) 2021-09-16
US11362856B2 (en) 2022-06-14
CN108075908B (zh) 2023-01-17

Similar Documents

Publication Publication Date Title
WO2017129124A1 (zh) 智能家电控制方法及智能家电
WO2016065812A1 (zh) 基于设定场景模式的智能设备控制方法和装置
CN105471686B (zh) 终端控制方法、装置及系统
WO2017148308A1 (zh) 一种物联网设备接入网络的方法、装置及系统
AU2016335987B2 (en) Wireless provisioning and configuring of hardware elements of a home automation system
US8588990B2 (en) Communicating through a server between appliances and applications
EP3557339A1 (en) Linked control method for internet-of-things gateway and internet-of-things gateway
WO2016065813A1 (zh) 自定义智能设备场景模式的方法和装置
WO2020223854A1 (zh) 设备配网方法、装置、电子设备及存储介质
WO2016065825A1 (zh) 针对智能设备的场景模式推荐方法和装置
EP3675543B1 (en) Device control method and apparatus
CN111585771B (zh) 一种基于u2f物理令牌的物联网设备的集中式认证系统
EP3007385B1 (en) Terminal peripheral control method, m2m gateway, and communications system
WO2023138285A1 (zh) 一种智能家居设备的绑定方法和终端
JP2009135783A (ja) 通信アダプタ及びその接続情報設定方法
JP6564327B2 (ja) マルチコントローラネットワークにおける相互作用制御の設定
WO2018086413A1 (zh) 处理操作请求的方法及装置
WO2015123890A1 (zh) 一种m2m中信息处理的方法和装置
CN105281957B (zh) 一种在物联网中接入设备的方法及服务器
TWI684949B (zh) 用於參與及回應應用程式的邀約方法和裝置
WO2021027436A1 (zh) 一种控制设备的方法及服务器
US20200013246A1 (en) Secured tethering process between devices
CN113132958A (zh) 融合组网方法、设备、系统及计算机可读存储介质
JP4623073B2 (ja) リクエスタとプロバイダとの間の通信を管理するシステム、リクエスタとプロバイダとの間の通信を管理する方法、リクエスタとプロバイダとの間の電子通信を管理する方法を実現すべく構成された計算装置、及びリクエスタとプロバイダとの間の電子通信を管理する方法を実現する実行可能な命令を含むコンピュータ読取可能な媒体
WO2019241006A1 (en) Indoor comfort control system and method with multi-party access

Legal Events

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

Ref document number: 17870069

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017870069

Country of ref document: EP

Effective date: 20190611