WO2020048194A1 - 用于在通用服务实体上进行任务处理的方法、通用服务实体、进行任务处理的装置和介质 - Google Patents

用于在通用服务实体上进行任务处理的方法、通用服务实体、进行任务处理的装置和介质 Download PDF

Info

Publication number
WO2020048194A1
WO2020048194A1 PCT/CN2019/093084 CN2019093084W WO2020048194A1 WO 2020048194 A1 WO2020048194 A1 WO 2020048194A1 CN 2019093084 W CN2019093084 W CN 2019093084W WO 2020048194 A1 WO2020048194 A1 WO 2020048194A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
entity
service entity
resource list
task processing
Prior art date
Application number
PCT/CN2019/093084
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 US17/272,539 priority Critical patent/US11700189B2/en
Publication of WO2020048194A1 publication Critical patent/WO2020048194A1/zh

Links

Images

Classifications

    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/08—Allotting numbers to messages; Counting characters, words or messages
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5058—Service discovery by the service manager
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • 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/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • 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
    • 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
    • H04L67/63—Routing a service request depending on the request content or context
    • 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/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H04L41/5022—Ensuring fulfilment of SLA by giving priorities, e.g. assigning classes of service

Definitions

  • the present disclosure relates to the field of the Internet of Things, and in particular, to a method for performing task processing on a general service entity, a general service entity, a device and a medium for performing task processing.
  • the Internet of Things uses local networks or communication technologies such as the Internet to connect sensors, controllers, machines, people, and objects in new ways, forming a connection between people and things, and between things.
  • the Internet of Things technology in various application fields, more and more devices are connected to the Internet of Things.
  • the task processing may be requesting authentication, notification, update, deletion, etc. to complete the authentication between the Internet of Things entities. , Scheduling, security management and other functions.
  • a method for performing task processing on a general service entity including: receiving a request for task processing, determining whether the general service entity itself performs the task processing request, and determining itself If the task processing request is not executed, the request is forwarded to another general service entity, where the general service entity has an association relationship with the other general service entity; when it is determined that the task processing request is performed by itself Next, the general service entity executes the request processed by the task.
  • a first resource list is stored in the universal service entity, and the first resource list includes information of all universal service entities associated with the universal service entity.
  • the universal service entity determines whether other universal service entities in the first resource list meet the first standard, and moves the universal service entities that do not meet the first standard out of the first resource list, thereby updating the first List of resources.
  • the general service entity determines whether the general service entity itself performs the task processing request based on at least one of its own computing capability, storage capability, and security level.
  • the universal service entity stores the received request processed by the task into a request queue: when the number of requests included in the request queue is less than a first threshold, it determines that the request to perform the task processing itself, in When the number of requests included in the request queue is greater than or equal to the first threshold, it is determined that the request does not execute the task processing itself.
  • the task processing request includes an authentication request: determining whether an entity sending the authentication request meets a second criterion, and storing information of the authenticated entity in a second resource list to update the second resource A list, sending an updated second resource list to a universal service entity in the first resource list, and sending an authentication identifier to an entity in the second resource list.
  • the method for performing task processing on a universal service entity further includes removing entity information from the second resource list to update the second resource list; moving the second resource toward The list entity sends a notification message; and sends an updated second resource list to the universal service entity in the first resource list.
  • the first standard and the second standard are determined based on at least one of a computing capability, a storage capability, and a security level.
  • the universal service entity is configured to be able to manage entities in the first resource list and the second resource list.
  • the task processing request further includes at least one of a creation request, an update request, an acquisition request, a notification request, and a deletion request.
  • the method further includes: receiving a response corresponding to the request by the another general service entity, receiving data corresponding to the request from the requester, and The data is forwarded to the other general service entity, and the requester is sent the processing result corresponding to the request received from the other service subject.
  • a universal service entity including: a receiving unit configured to receive a request for task processing; and a processing unit configured to determine whether the universal service entity itself performs the task processing request: When it is determined that it does not execute the task processing request, it forwards the request to another general service entity; when it determines that it performs the task processing request, the general service entity executes the task processing request, where , The universal service entity has an associated relationship with the other universal service entity.
  • a first resource list is stored in the universal service entity, and the first resource list includes information of all universal service entities associated with the universal service entity, and the processing unit is further configured to determine the first Whether other general service entities in the resource list meet the first standard, and the general service entities that do not meet the first standard are removed from the first resource list, thereby updating the first resource list.
  • the universal service entity determines whether to perform the task processing request based on at least one of its own computing capability, storage capability, and security level.
  • the processing unit is further configured to store the received request for processing the task into a request queue, and when the number of requests included in the request queue is less than a first threshold, determine that it has performed the task processing itself. Requests; when the number of requests included in the request queue is greater than or equal to the first threshold, it is determined that it does not execute requests processed by the task.
  • the task processing request includes an authentication request
  • the processing unit is further configured to determine whether an entity sending the authentication request meets a second criterion, and store information of the authenticated entity in a second resource list, To update the second resource list; send an updated second resource list to a universal service entity in the first resource list; and send an authentication identifier to an entity in the second resource list.
  • the processing unit is further configured to remove the information of the entity from the second resource list to update the second resource list; send a notification message to the entity removed from the second resource list; and The general service entity in the first resource list sends the updated second resource list.
  • the processing unit is further configured to: in a case where it is determined that the processing is not performed, receive a response corresponding to the request by the other general service entity; and receive data corresponding to the request from the requester, The data is forwarded to the other general service entity; and the requester is sent the processing result corresponding to the request received from the other service subject.
  • an apparatus for performing task processing including: one or more processors; and one or more memories in which computer-readable code is stored, where the computer-readable code is in The method for performing task processing on a general service entity as described above is performed when executed by the one or more processors.
  • a computer storage medium in which computer-readable code is stored, which when executed by the one or more processors performs the above-mentioned method for Method for performing task processing on a general service entity.
  • FIG. 1A shows a schematic diagram of a centralized block framework according to an embodiment of the present disclosure
  • FIG. 1B shows a flowchart of a method for performing task processing on a universal service entity according to an embodiment of the present disclosure
  • FIG. 2 illustrates a schematic diagram of a centralized block according to an embodiment of the present disclosure
  • 3A and 3B illustrate a flowchart of task processing performed by a centralized block according to an embodiment of the present disclosure
  • FIG. 5 illustrates a schematic diagram of an apparatus for performing task processing according to an embodiment of the present disclosure
  • FIG. 6 shows a schematic block diagram of a universal service entity according to an embodiment of the present disclosure.
  • a flowchart is used in this application to illustrate the steps of a method according to an embodiment of the application. It should be understood that the preceding or following steps are not necessarily performed in order. Instead, the steps can be processed in reverse order or simultaneously. At the same time, other actions can be added to or removed from these processes.
  • the Internet of Things can be used as an extension of the Internet. It includes the Internet and all resources on the Internet and is compatible with all Internet applications. With the application of the Internet of Things technology in various fields, various new application fields such as smart home, intelligent transportation, and smart health have appeared.
  • oneM2M entities are required to have certain computing and storage capabilities.
  • different oneM2M entities have differences in their operational capabilities.
  • the operating capability of the general service entity CSE may be strong, while the operating capability of some application entities AE may be weak.
  • the operating capability of the CSE as a general service entity may be stronger than the physical AE such as a smart speaker, a rice cooker, and the like.
  • entity described in this article may be an IoT terminal device, or may be a software module in the device.
  • an entity with a stronger operational capability such as CSE
  • an entity with a weaker operational capability such as AE
  • the strong entity has a stronger running capability than the weak entity.
  • an entity's ability to run can be judged based on its computing resources, network resources, storage resources, and security functions to determine whether the entity is a strong entity or a weak entity.
  • an entity with a storage space of more than 10M can be implemented as a strong entity, and the remaining entities with a storage capacity of less than 10M can also be implemented as weak entities.
  • 800M CPU which can support IPV6 (Internet Protocol Version 6)
  • IPV6 Internet Protocol Version 6
  • CSE functions can be efficiently run, and it can be used as a common general service entity CSE to perform the weak connection to it.
  • the entity's task processing operations such as resource operations.
  • the weak entity does not have the function to complete all resource management operations.
  • these weak entities are simply used as common entities AE and connected to a common common service entity CSE, and all tasks related to them are implemented with the common CSE, the weak entity's own capacity will be wasted.
  • the CSE function is completely run on such a weak entity, the implementation of the CSE function will also be limited by its own operating capabilities, resulting in slowing down the overall work efficiency of the system.
  • the weak entity may be unable to complete operations on some sensitive data, or the speed of generating its own key is too slow, which will affect the operating efficiency of the weak entity itself and the operating efficiency of the overall system including the weak entity.
  • the present disclosure provides a method for performing task processing on a general service entity.
  • the common service entity CSE may be implemented by the strong entity described above.
  • the centralized block may include a core block and a non-core block, the core block includes the strong entity, and the non-core block includes the weak entity.
  • the strong entities in the core block can be managed by creating a first resource list, and the weak entities in the non-core block can be managed by creating a second resource list.
  • the first resource list and the second resource list The entities in the resource list together form a centralized block.
  • the centralized block may be a collection of entities within a certain range.
  • FIG. 1A A schematic diagram of a centralized block according to an embodiment of the present disclosure is shown in FIG. 1A.
  • a centralized block it can include strong entities with strong operating capabilities and weak entities with weak operating capabilities.
  • general service entities can implement management functions for all entities in the centralized block.
  • the universal service entity may be implemented by a strong entity with a strong computing capability in a core block.
  • several strong entities can be simultaneously implemented as general service entities to achieve management functions for all entities.
  • a first entity list and a second resource list are stored in a strong entity implemented as a general service entity CSE, and an association relationship between entities in the centralized block is established through the list.
  • the first resource list has information of all strong entities included in the core block in the centralized block, for example, the strong entity 1CSE1 and the strong entity 2CSE2 shown in FIG. 1A.
  • the universal service entity can implement task scheduling request scheduling. For example, upon receiving a request that it does not execute itself, the general service entity may forward the request to other strong entities (such as CSE1) in the first resource list to execute the request.
  • the second resource list has information on weak entities included in non-core blocks in the centralized block, for example, weak entity 1AE1 and weak entity 2AE2 shown in FIG. 1A.
  • the universal service entity can implement security management of entities within the centralized block.
  • entities such as gateways, smart speakers, lamps, and rice cookers can be included.
  • gateways and smart speakers with strong operating capabilities can be used as core block members, that is, as strong entities.
  • the information of the gateway and the smart speaker may be stored in the first resource list to be associated with each other.
  • the entities such as lamps and rice cookers in the smart home have weaker operating capabilities, they cannot complete the operation of some sensitive data, or the speed of generating their own keys is too slow.
  • the operating capabilities of entities such as a capable gateway can complete the above processing tasks.
  • Weak entities such as lamps and rice cookers in a smart home scene may be used as non-core block members, and information of the weak entities may be stored in a second resource list.
  • the strong entity in the core block can be used as a general service entity for the weak entity in the non-core block to complete processing tasks related to the weak entity.
  • the strong entity in the core block can also implement management of other strong entities in the core block, such as security authentication. Therefore, in this centralized block, the management and resource scheduling of all entities in the entire centralized block by the entities in the core block can be achieved, thereby improving the overall operating efficiency of the centralized block.
  • FIG. 1B shows a flowchart of a method for performing task processing on a general service entity according to an embodiment of the present disclosure. The task processing method according to the embodiment of the present disclosure will be described in detail below with reference to FIG. 1B.
  • the general service entity receives a request for task processing.
  • the task processing request may include an authentication request, a creation request, an update request, an acquisition request, a notification request, a deletion request, and the like.
  • the universal service entity may be any strong entity in the core block, such as CSE1.
  • the task processing request may be issued by a weak entity in a non-core block in the same centralized block as the strong entity. For example, in the scenario of a smart home, when a weak entity needs to perform security authentication, it can send a security authentication request to a strong entity, which requests to use the strong entity to generate the authentication key of the weak entity, thereby obtaining Access to related data in the centralized block of the smart home.
  • the general service entity CSE1 may determine whether it executes the request for task processing itself. For example, the general service entity CSE1 may determine whether it executes the received task processing request based on its own computing capability, storage capability, and security level. For example, in the centralized block of the smart home scenario, when the gateway receives an authentication request issued by a rice cooker that is a weak entity, the gateway may be processing a processing task requested by another weak entity, or the gateway It can judge the running capability required for this authentication request, and can determine whether it executes the authentication request itself according to its current computing capacity and storage capacity. For example, when the gateway determines that it takes a long time to complete the authentication request itself, it may affect the operating efficiency of the overall system.
  • the gateway may determine that it does not execute the authentication request itself.
  • the relationship between the running time and the running efficiency may be set artificially. For example, the gateway may be set. When it takes more than 1 minute to execute a processing task, it is determined that it does not perform the task itself. This time setting is only exemplary, and can be adjusted accordingly according to the specific scene in which the centralized block is located.
  • the general service entity CSE1 forwards the request to another general service entity, such as CSE2.
  • the general service entity CSE 1 has an association relationship with the other general service entity CSE 2.
  • the common service entity CSE1 may store a resource list, and determine other common service entities CSEs associated with the resource list through the resource list.
  • a strong entity 1 in the core block may forward the task request to other strong entities in the core block, such as strong entity 2, to request that the strong entity 2 process the task request.
  • the information of the strong entity 1 and the strong entity 2 may be recorded together in the first resource list, and the strong entities in the centralized block all store the first resource list.
  • the strong entity 1 may determine other strong entities that have an association relationship with the strong resource 1 by querying the first resource list, so as to forward the task request to the strong entity 2.
  • Both the strong entity 1 and the strong entity 2 in the core block shown can be implemented as a common service entity CSE due to their strong operational capabilities.
  • step S104 the general service entity CSE1 executes the task processing request.
  • the request processed by the task is a resource operation, and the general service entity CSE1 judges that it is capable of performing the task processing request based on its remaining storage capacity and computing capacity, and then executes the request corresponding to the request Processing operations without forwarding requests for processing of this task to other general service entities such as CSE2.
  • the present disclosure provides a method for managing the functions of an entity and a task processing mode based on the operating capabilities of the entity (including a general service entity and an application entity).
  • a plurality of entities belonging to the same network may be divided into a centralized block, wherein the running capabilities of the plurality of entities are different, such as that the plurality of entities may include one or more Strong entities and one or more weak entities, etc.
  • a strong entity capable of running all functions of the oneM2M architecture may be used as a core block entity member, for example, a common service entity CSE may be used as a core block entity.
  • a weak entity with a weaker running capability can be represented as a non-core block member, for example, a general AE can be used as a non-core block entity.
  • the core block may be implemented by means of group resources.
  • information of entities in the core block may be stored in, for example, a member ID sequence of the ⁇ group> resource, thereby establishing associations between core block members.
  • entities within the core block can also establish associations between core block members in the form of resource indexes.
  • a gateway, a smart speaker, a lamp, a rice cooker, and the like belonging to the same network constitute a centralized block.
  • a strong entity capable of running as a general service entity is represented as a core block member, and other entities with weaker operating capability than the strong entity are represented as non-core block members.
  • Members in the core block are managed by a first resource list, and members in the non-core block are managed by a second resource list.
  • the members in the core block all store the first resource list and the second resource list to receive requests for processing tasks of weak entities in the second resource list, and to determine that they do not perform the task processing requests themselves , The request is forwarded to other strong entities in the first resource list to complete the task processing.
  • a strong entity in a centralized block can be implemented as a CSE to manage the task processing of the entire centralized block.
  • the core block and non-core block members cooperate with each other to improve the operation efficiency of the entire centralized block and ensure the concentration. Stability and security within the block.
  • FIG. 2 illustrates a schematic diagram of a centralized block according to an embodiment of the present disclosure.
  • the OneM2M device group may include one or more centralized blocks, such as centralized block 1 and centralized block 2. Entities may be divided into core block or non-core block members in the centralized block.
  • the common service entity CSE may serve as a core block member
  • the weak entity may serve as a non-core block member.
  • the core block in centralized block 1 may include the three general service entities represented by circles in the left dotted box
  • the non-core block may include the three weak entities represented by triangles in the right dotted box. .
  • the number of entities in the core block and the non-core block in the centralized block 2 may be the same as or different from the centralized block 1.
  • the core block in the centralized block 2 may include the two general service entities represented by circles in the dotted box on the left, and the non-core block may include the triangles represented in the dotted box on the right. 4 weak entities.
  • the weak entities in the centralized block can request the common service entity CSE in the core block to perform the corresponding task processing.
  • the task processing may include entity authentication, entity authorization, and the like.
  • the management positions of the universal service entities in the core block are equal, and other universal service entities belonging to the same core block can be managed.
  • the universal service entity in the core block may store a first resource list, and the first resource list includes information of all universal service entities associated with the universal service entity.
  • the first resource list stored in the general service entity CSE 1 includes information of the general service entity CSE 2.
  • CSE1 can forward the request processed by this task to the general service entity CSE2.
  • the information in the first resource list may include an identity of the general service entity, an operation capability, and the like, and may further include other information of the general service entity.
  • the universal service entity in the core block not only needs to have strong computing power and storage capacity, etc., but also needs to have a high security level.
  • the information in the first resource list corresponds to the information of the universal service entity included in the core block. After running for a period of time, each universal service entity in the resource list can update the information in the first resource list.
  • the universal service entity may manage other entities in the first resource list.
  • the management may, for example, periodically update information of entities in the first resource list.
  • the management may further include an adding operation, such as assigning an authentication identifier to a new strong entity that has passed security verification, and adding the information of the entity to the first resource list.
  • the management may further include a removal operation, for example, information of a strong entity that does not meet the security level may be removed from the first resource list.
  • the universal service entity in the core block may determine whether other universal service entities in the first resource list meet the first standard, and move the universal service entities that do not meet the first standard out of the first resource. List, thereby updating the first resource list.
  • the first criterion is used as a criterion for judging whether an entity has strong entity capabilities.
  • the first criterion may be determined based on at least one of an entity's computing capability, storage capability, and security level. For example, the ability of an entity can be judged based on computing resources, network resources, storage resources, and security functions.
  • an 800M CPU with strong storage capacity can be implemented as a strong entity in a centralized block.
  • the general service entity in the core block not only needs to have strong computing power and storage capacity, etc., but also needs to have a higher security level.
  • each universal service entity in the resource list may update the information in the first resource list, for example, removing information of universal service entities that do not meet the core block entity security standards from the first resource list.
  • the time interval may be set based on the security requirements of the centralized block. For example, if the core block has higher security requirements for a strong entity therein, the time interval may be shortened .
  • the time interval can also be set based on the business needs of the manager of the centralized block, and it changes as the demand changes, and there is no limitation on the time interval here.
  • FIG. 3A and FIG. 3B show a flowchart of task processing performed by a centralized block according to an embodiment of the present disclosure.
  • the strong entity in the core block can be implemented as a general service entity CSE1.
  • CSE1 first determines whether it performs the task processing itself. For example, CSE1 may determine whether to execute the processing task based on its current status. For example, CSE1 can determine whether to execute the processing task based on its own CPU occupancy rate, bandwidth occupancy rate, and free storage space. If CSE1 determines that it has the ability to perform the task processing, it executes the task processing directly; if it determines that it does not perform the task processing, CSE1 sends the task to other common service entities CSE2 that belong to the core block. The request processed by the task. For example, as shown in FIG.
  • the weak entity may send a task processing request to the general service entity CSE1.
  • the request processed by the task may be a request using a CSE function.
  • the request for using the CSE function may be a request sent by a weak entity to the CSE1 to request the CSE1 to perform the corresponding data processing, and the weak entity cannot perform the CSE function due to a limitation of its own running capability.
  • the CSE1 can determine whether it processes the request processed by the task itself. According to the embodiment of the present disclosure, when the general service entity CSE1 receives a request for using the CSE function from an entity in a non-core block, it may store the received request in a request queue.
  • the CSE1 can automatically adjust the assignment of task processing, for example, it can determine whether to process the request itself based on the number of requests in the request queue. For example, when the number of requests included in the request queue is less than the first threshold, it determines that the request itself performs the task processing; when the number of requests included in the request queue is greater than or equal to the first threshold, it determines itself The request processed by this task is not executed.
  • the first threshold may be set based on the requirement of the centralized block for task processing efficiency. For example, if the centralized block has a higher requirement for the efficiency of task processing, a first threshold with a smaller value may be set.
  • the first threshold value can be set to 3 (only for example). That is, when the gateway serving as CSE1 receives an authentication request, if it determines that the number of requests in its own request queue is greater than or equal to 3, for example, 5 (only exemplary), the CSE1 determines that it completes the The authentication processing request takes a long time, because the CSE1 still needs to process 5 outstanding requests in its own request queue before executing the authentication processing request. In this case, the CSE1 may determine that it does not execute the authentication request, and forward the authentication request to other general service entities CSE2, such as smart speakers, that belong to the same core block as the CSE1.
  • CSE2 general service entities
  • the universal service entity may also determine whether to execute the request according to the content of the request processed by the task. For example, if it is an authentication request, it is executed by itself, and if it is a request about updating data, it is forwarded.
  • the general service entity in the core block can perform operation management and allocation according to the content of the request processed by the task. For example, in the centralized block of the smart home scene, it can be set that the gateway performs requests for authentication, addition, etc., and the smart speaker performs requests for data processing, etc. Therefore, after the gateway receives the data update request sent by the rice cooker, it can determine that it does not execute the request itself, and forward the request to the smart speaker. Similarly, when the smart speaker receives the request for authentication, it can determine that it does not execute the request itself and forward the request to the gateway.
  • step S2 the CSE 1 determines that it can process the currently received request. Then in step S3, the CSE1 may send a response request to the weak entity, allowing it to use the CSE function. After receiving the response message, in step S4, the weak entity can put data into the message and use the CSE function of CSE1. In step S5, the CSE 1 performs a CSE function operation corresponding to the request. Finally, in step S6, the CSE1 processing is completed, and the processing result is returned to the weak entity.
  • step S7 the weak entity requests the CSE 1 to use the CSE function.
  • step S8 the CSE 1 may store the request in a message queue and determine the number of unprocessed requests in the message queue. For example, if the number of unprocessed requests exceeds the first threshold, the system may confirm the request. CSE1 does not execute the request itself. In order to avoid congestion of requests in CSE1, it is necessary to forward the request to other general service entities in the core block, for example, CSE2.
  • CSE1 can forward the request to CSE2.
  • the CSE1 may further determine a request to be forwarded based on the priority of the request in the request queue. For example, a request sent by an entity in a non-core block to the CSE has a priority attribute, such as a QOS (quality of service) parameter, which is used to identify the priority of the current request.
  • the CSE1 can determine the order of processing each message according to the priority of these requests. For example, when CSE1 determines that the number of requests in the request queue exceeds the first threshold, it may forward the highest priority request in the request queue to the idle CSE2.
  • CSE1 and CSE2 belong to the same core block. For example, CSE1 can confirm the member CSE2 that belongs to the same core block through the first resource list.
  • step S10 CSE2 determines that it can handle the request, and responds to CSE1 with a request to allow the use of the CSE function at step S11.
  • the CSE 1 may send the information that the CSE 2 allows the CSE function to be used to the weak entity as the requester.
  • step S13 the weak entity puts data into the message to use the CSE function.
  • step S14 CSE1 forwards the data to CSE2 after receiving it.
  • step S15 CSE2 allows the weak entity to use its CSE function to perform CSE function operations, and sends the processing result to CSE1 in step S16.
  • step S17 CSE1 forwards the processing result to the weak entity of the requester.
  • the centralized block includes a core block and a non-core block.
  • the core block may include a strong entity with strong processing capability, and the strong entity may be implemented as a general service entity to provide CSE functions to other entities.
  • the non-core blocks may include weak entities with weaker processing capabilities.
  • the entities in the core block can manage all entities in the centralized block and process task requests that cannot be processed by the weak entities in the non-core block or are time-consuming.
  • the core block and the non-core block cooperate with each other to complete the tasks in the centralized block, and the task scheduling is performed automatically by the request shown in FIG. 3B above, so that the task requirements of the entire centralized block do not pile up, thereby improving the concentration Block processing power and efficiency.
  • each communication between the initiator and receiver requires registration of the corresponding resource and the declared version of the OneM2M resource on both sides, and then these resources will be synchronized to the remote resource declaration after the local change Version to implement data submission. Therefore, during these message passing processes, an identity authentication process is performed first, and a data encryption and decryption process may also be included.
  • the task processing request may further include an authentication request, that is, an entity in a non-core block sends an authentication request to a general service entity in the core block to obtain an authentication identifier, and the authentication identifier is passed.
  • the entity can communicate with other entities in the centralized block without having to authenticate again.
  • FIG. 4 shows a flowchart of performing an authentication request according to an embodiment of the present disclosure.
  • the entities in the core block may include gateways and smart speakers, and the entities in the non-core blocks may include lamps and rice cookers.
  • a rice cooker may send a request for authentication to a smart speaker, which determines that it can perform an authentication request for a rice cooker by itself based on its own computing space, and then it directly processes the authentication request.
  • the smart speaker determines whether the entity that sent the authentication request, that is, the rice cooker, meets the second criterion. If so, it can be considered that the rice cooker has passed the safety certification, and the information of the certified rice cooker is stored in the second resource list. Updating the second resource list.
  • the second resource list may also be referred to as a white list, in which information about entities that have passed security authentication in a non-core block is stored. Then, the smart speaker may send the updated second resource list to other universal service entities in the first resource list, and send an authentication identifier to the rice cooker.
  • the rice cooker can communicate with other entities in the centralized block according to the authentication ID. Specifically, a "token resource" can be created in the rice cooker to identify that it has passed the authentication, which means that it meets the security standards.
  • the second standard is used as a criterion for judging whether an entity is secure, and the universal service entity may determine the second standard based on a security level of a weak entity.
  • the second resource list may have information about all authenticated entities in the centralized block, that is, it may include both strong entities in the core block and weak entities in non-core blocks. Information. In this way, a strong entity that is a general service entity can manage all the security entities in the centralized block through the second resource list.
  • information of the core block entity may exist in the second resource list by default. In other words, in the centralized block of the smart home, the strong entity in the core block associated with the first resource list defaults to a security certification standard (such as a second standard) that complies with the second resource list.
  • the smart speaker determines that it does not execute the authentication request based on its insufficient computing space.
  • the smart speaker can then forward the authentication request to a gateway that belongs to the same core block as the smart speaker.
  • the smart speaker may optionally forward a higher priority request in its request queue to the gateway for processing.
  • the gateway may process the authentication request, and if it is determined that the lamp meets the second criterion, the information of the lamp is added to the second resource list.
  • the smart speaker forwards the authentication identification to the lamp to identify that it has passed the authentication.
  • the smart speaker or gateway may determine the second standard based on at least one of a computing capability, a storage capability, and a security level. For example, in the authentication request, the security level of a non-core entity can be evaluated, and an authentication mark is only sent to the entity that meets the security level standard to maintain the overall security of the system.
  • the universal service entity in the core block can also manage the entity in the second resource list.
  • the information of the rice cooker may be periodically removed from the second resource list to Updating the second resource list. For example, after a period of time, the rice cooker will again verify whether the rice cooker meets the second standard, and if it does not, then remove it from the second resource list. Then, the smart speaker may send a notification message to the entity that has moved out of the second resource list, that is, the rice cooker, and send an updated second resource list to the universal service entity in the first resource list. For example, in a centralized block of a smart home, a smart speaker as a general service entity may implement a regular update process of information in the second resource list.
  • the weak entity passed the security authentication by sending an authentication request to the smart speaker, and has a token resource for communicating with other entities. After 10 days (only for example), the smart speaker can automatically send the weak speaker The entity's information is removed from the second resource list and the validity of the token resource is released.
  • an entity in the non-core block may receive a notification message from a smart speaker to move its information out of the second resource list. After receiving the notification message, the rice cooker may send an authentication request to the universal service entity in the first resource list to obtain the authentication identifier again.
  • the weak entity needs to send a security authentication request to the smart speaker again. If the smart speaker determines that the weak entity does not meet the second criterion at this time, it does not pass the entity's authentication request. In this way, the security management function in the centralized block can be implemented to prevent leakage of sensitive data, thereby ensuring the security and stability of the entire centralized block.
  • the universal service entity in the core block may also change the second standard according to changes in the management requirements of the centralized block.
  • the cooperation between core blocks and non-core blocks can effectively improve the efficiency of system operation, and give full play to the operating capabilities of weak entities. Strong entities to perform tasks that they cannot achieve or take a long time (such as the operation of sensitive data or too slow to generate their own keys).
  • the general service entities in the core block can also cooperate with each other to automatically schedule tasks to effectively avoid problems such as task request blocking. In this way, the individual's operating speed and the overall system's operating efficiency are greatly improved.
  • FIG. 5 shows a schematic diagram of an apparatus for performing task processing according to an embodiment of the present disclosure.
  • the apparatus 500 may include one or more processors 501 and one or more memories 502. Wherein, the processor 501 stores computer-readable code, which, when executed by the one or more processors, can perform the task processing on the general service entity as described above. The method is not repeated here.
  • FIG. 6 shows a schematic block diagram of the universal service entity 600 according to an embodiment of the present disclosure.
  • the universal service entity may include a receiving unit 601 and a processing unit 602.
  • the receiving unit 601 may be configured to receive a request for task processing.
  • the processing unit 602 may be configured to determine whether the general service entity itself performs the task processing request: if it determines that it does not perform the task processing request, forward the request to another general service entity; after determining itself
  • the universal service entity executes the task processing request, wherein the universal service entity has an association relationship with the other universal service entity. For example, an association relationship between the universal service entity and another universal service entity may be established through a resource list.
  • the universal service entity 600 stores a first resource list, and the first resource list includes information of all universal service entities associated with the universal service entity.
  • the processing unit 602 may be further configured to determine whether other general service entities in the first resource list meet the first standard, and move general service entities that do not meet the first standard out of the first resource list, thereby updating the first resource. List.
  • the universal service entity 600 determines whether to perform the task processing request based on at least one of its own computing capability, storage capability, and security level. For example, in the centralized block of the smart home scenario, when the gateway receives an authentication request issued by a rice cooker that is a weak entity, the gateway may be processing a processing task requested by another weak entity, or the gateway It can judge the running capability required for this authentication request, and can determine whether it executes the authentication request itself according to its current computing capacity and storage capacity.
  • the processing unit 602 may be further configured to store the received request processed by the task into a request queue, and determine that it executes the task when the number of requests included in the request queue is less than the first threshold. Requests processed; when the number of requests included in the request queue is greater than or equal to the first threshold, it is determined that it does not execute requests processed by the task.
  • the first threshold may be set based on the requirements of the centralized block for task processing efficiency, and details are not described herein again.
  • the request for task processing may include an authentication request.
  • the processing unit 602 may be further configured to determine whether the entity sending the authentication request meets the second criterion, and store the information of the authenticated entity in the second resource list, To update the second resource list; send an updated second resource list to a universal service entity in the first resource list; and send an authentication identifier to an entity in the second resource list.
  • the processing unit 602 may be further configured to remove the information of the entity from the second resource list to update the second resource list; send a notification message to the entity removed from the second resource list; and Sending the updated second resource list to the universal service entity in the first resource list.
  • the strong entities in the core block can be managed by creating a first resource list
  • the weak entities in the non-core block can be managed by creating a second resource list.
  • the resource list and the entities in the second resource list together form a centralized block.
  • the centralized block is a collection of entities within a certain range.
  • the processing unit 602 may be further configured to: receive a response corresponding to the request from the other general service entity when it is determined that the processing is not performed by itself; and receive a response corresponding to the request from the requester Data, which is forwarded to the other general service entity; and sends to the requesting party the processing result corresponding to the request received from the other service subject.
  • a centralized block-type task processing method can be realized, and the cooperation between core blocks and non-core blocks can effectively improve the operating efficiency in the centralized block, and give full play to the weak entity's own operating capabilities
  • a strong entity such as a general service entity
  • it can achieve tasks that it cannot achieve or take a long time (such as the operation of sensitive data or the speed of generating its own key is too slow).
  • the general service entities in the core block can also cooperate with each other to automatically schedule tasks to effectively avoid problems such as task request blocking. In this way, the individual's operating speed and the overall system's operating efficiency are greatly improved.
  • a computer storage medium stores computer readable code, and when the computer readable code is executed by one or more processors, the method for performing task processing on a general service entity as described above can be performed. , Will not repeat them here.
  • the present disclosure provides a method for managing a large-scale oneM2M architecture in a centralized block manner.
  • the centralized block may include a core block and a non-core block.
  • the core block may include a strong entity with a strong running capability.
  • the strong entity may be implemented as a general service entity that performs a task request of other entities.
  • the non-core block May include weak entities with weaker operational capabilities.
  • a method for task processing on a general service entity is proposed, which includes: the general service entity may receive a request for task processing from a non-core block entity; and determine whether the general service entity itself performs the task processing.
  • Request if it is determined that it does not execute the task processing request, it forwards the request to another universal service entity that has an association relationship with the universal service entity; in the case of determining itself request to perform the task processing, the request The general service entity itself executes the request processed by the task.
  • the universal service entity performs the task processing method described above, and the core block entity and the non-core block cooperate with each other to efficiently run task management in the entire centralized block.
  • the core block may include a strong entity with a strong operating capability
  • the strong entity may be implemented as a general service entity to provide CSE functions to other entities
  • the non-core block may include a weaker processing capability. Weak entities, the strong entities have stronger operation capabilities than the weak entities.
  • the weak entity in the non-core block may send a task request to a strong entity implemented as a general service entity in the core block, and use the strong processing capability of the general service entity to solve task processing that the weak entity does not perform, such as the weak
  • the computing power of the entity cannot process or take a long task request.
  • the general service entity may also determine whether to perform processing corresponding to the request based on its current capabilities. To avoid request congestion or optimize task processing flow, the general service entity may The received request is forwarded to other idle general service entities in the core block to implement task scheduling between core block members.
  • the core block members can also manage the entities in the entire centralized block. For example, they can send authentication identifiers to non-core block entities to improve the security level of the centralized block. Utilizing the method for task processing according to the present disclosure can greatly improve the operating efficiency of the overall system and the operating speed of each entity.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Power Engineering (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开提供了一种用于在通用服务实体上进行任务处理的方法、通用服务实体、进行任务处理的装置和介质。所述方法包括：接收进行任务处理的请求(S101)，确定该通用服务实体自身是否执行该任务处理的请求(S102)，在确定自身不执行该任务处理的请求的情况下，将该请求转发给另一通用服务实体(S103)，其中，该通用服务实体与该另一通用服务实体具有关联关系；在确定自身执行该任务处理的请求的情况下，该通用服务实体执行该任务处理的请求(S104)。

Description

用于在通用服务实体上进行任务处理的方法、通用服务实体、进行任务处理的装置和介质 技术领域
本公开涉及物联网领域，具体的涉及一种用于在通用服务实体上进行任务处理的方法、通用服务实体、进行任务处理的装置和介质。
背景技术
随着信息技术尤其是互联网技术的发展，用于实现信息化、远程管理控制和智能化的物联网技术逐渐成熟。物联网利用局部网络或互联网等通信技术把传感器、控制器、机器、人员和物品等通过新的方式联接在一起，形成人与物、物与物之间的连接。随着物联网技术在各个应用领域的快速发展，越来越多的设备连接至物联网。在物联网中，具有联系的各个实体之间存在着相互配合以完成任务处理的需求，例如，所述任务处理可以是请求认证，通知、更新、删除等，以完成物联网实体之间的认证、调度、安全管理等功能。
发明内容
根据本公开的一方面，提供了一种用于在通用服务实体上进行任务处理的方法，包括：接收进行任务处理的请求，确定该通用服务实体自身是否执行该任务处理的请求，在确定自身不执行该任务处理的请求的情况下，将该请求转发给另一通用服务实体，其中，该通用服务实体与该另一通用服务实体具有关联关系；在确定自身执行该任务处理的请求的情况下，该通用服务实体执行该任务处理的请求。
根据本公开实施例，在该通用服务实体中存储有第一资源名单，该第一资源名单中包含与该通用服务实体相关联的所有通用服务实体的信息。
根据本公开实施例，该通用服务实体确定第一资源名单中的其他通用服务实体是否满足第一标准，并且将不满足第一标准的通用服务实体移出所述第一资源名单，从而更新第一资源名单。
根据本公开实施例，该通用服务实体基于自身的运算能力、存储能力和安全等级中的至少一种来确定该通用服务实体自身是否执行该任务处理的请求。
根据本公开实施例，该通用服务实体将接收到的该任务处理的请求存入请求队列：在请求队列中包括的请求的数目小于第一阈值时，确定其自身执行该任务处理的请求，在请求队列中包括的请求的数目大于或等于该第一阈值时，确定其自身不执行该任务处理的请求。
根据本公开实施例，所述任务处理的请求包括认证请求：确定发送该认证请求的实体是否满足第二标准，将通过认证的实体的信息存入第二资源名单，以更新所述第二资源名单，向所述第一资源名单中的通用服务实体发送更新的第二资源名单，向第二资源名单中的实体发送认证标识。
根据本公开实施例，所述用于在通用服务实体上进行任务处理的方法还包括，从所述第二资源名单中移出实体的信息，以更新所述第二资源名单；向移出第二资源名单的实体发送通知消息；和向所述第一资源名单中的通用服务实体发送更新的第二资源名单。
根据本公开实施例，基于运算能力、存储能力和安全等级中的至少一种来确定所述第一标准和第二标准。
根据本公开实施例，所述通用服务实体配置成能够对所述第一资源名单和第二资源名单中的实体进行管理。
根据本公开实施例，所述任务处理的请求还包括创建请求、更新请求、获取请求、通知请求、删除请求中的至少一种。
根据本公开实施例，在确定自身不执行该处理的情况下，所述方法还包括：接收该另一通用服务实体对应于该请求的回应，从请求方接收对应于该请求的数据，将该数据转发给该另一通用服务实体，向请求方发送从该另一服务主体接收的对应于该请求的处理结果。
根据本公开的另一方面，还提供了一种通用服务实体，包括：接收单元，配置成接收进行任务处理的请求；处理单元，配置成确定该通用服务实体自身是否执行该任务处理的请求：在确定自身不执行该任务处理的请求的情况下，将该请求转发给另一通用服务实体；在确定自身执行该任务处理的请求的情况下，该通用服务实体执行该任务处理的请求，其中，该通用服务实体 与该另一通用服务实体具有关联关系。
根据本公开实施例，该通用服务实体中存储有第一资源名单，该第一资源名单中包含与该通用服务实体相关联的所有通用服务实体的信息，所述处理单元还配置成确定第一资源名单中的其他通用服务实体是否满足第一标准，并且将不满足第一标准的通用服务实体移出所述第一资源名单，从而更新第一资源名单。
根据本公开实施例，该通用服务实体基于自身的运算能力、存储能力和安全等级中的至少一种来确定其自身是否执行该任务处理的请求。
根据本公开实施例，所述处理单元还配置成将接收到的该任务处理的请求存入请求队列，在请求队列中包括的请求的数目小于第一阈值时，确定其自身执行该任务处理的请求；在请求队列中包括的请求的数目大于或等于该第一阈值时，确定其自身不执行该任务处理的请求。
根据本公开实施例，所述任务处理的请求包括认证请求，所述处理单元还配置成确定发送该认证请求的实体是否满足第二标准，将通过认证的实体的信息存入第二资源名单，以更新所述第二资源名单；向所述第一资源名单中的通用服务实体发送更新的第二资源名单；以及向第二资源名单中的实体发送认证标识。
根据本公开实施例，所述处理单元还配置成从所述第二资源名单中移出实体的信息，以更新所述第二资源名单；向移出第二资源名单的实体发送通知消息；和向所述第一资源名单中的通用服务实体发送更新的第二资源名单。
根据本公开实施例，所述处理单元还配置成：在确定自身不执行该处理的情况下，接收该另一通用服务实体对应于该请求的回应；从请求方接收对应于该请求的数据，将该数据转发给该另一通用服务实体；向请求方发送从该另一服务主体接收的对应于该请求的处理结果。
根据本公开的又一方面，提供了一种用于进行任务处理的装置，包括：一个或多个处理器；一个或多个存储器，其中存储了计算机可读代码，所述计算机可读代码在由所述一个或多个处理器执行时进行如上所述的用于在通用服务实体上进行任务处理的方法。
根据本公开的又一方面，提供了一种计算机存储介质，其中存储有计算机可读代码，所述计算机可读代码在由所述一个或多个处理器执行时进行如 上所述的用于在通用服务实体上进行任务处理的方法。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1A示出了根据本公开实施例的集中块框架的示意图；
图1B示出了根据本公开实施例的在通用服务实体上进行任务处理的方法的流程图；
图2示出了根据本公开实施例的集中块的示意图；
图3A和图3B示出了根据本公开实施例的集中块进行任务处理的流程图；
图4示出了根据本公开实施例的进行认证请求的流程图；
图5示出了根据本公开实施例的用于进行任务处理的装置的示意图；
图6示出了根据本公开实施例的通用服务实体的示意性框图。
具体实施方式
下面将结合本公开实施例中的附图，对本公开实施例中的技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本公开一部分的实施例，而不是全部的实施例。基于本公开中的实施例，本领域普通技术人员在无需创造性劳动的前提下所获得的所有其他实施例，都属于本公开保护的范围。
本公开中使用的“第一”、“第二”以及类似的词语并不表示任何顺序、数量或者重要性，而只是用来区分不同的组成部分。同样，“包括”或者“包含”等类似的词语意指出现该词前面的元件或者物件涵盖出现在该词后面列举的元件或者物件及其等同，而不排除其他元件或者物件。“连接”或者“相连”等类似的词语并非限定于物理的或者机械的连接，而是可以包括电性的连接，不管是直接的还是间接的。
本申请中使用了流程图用来说明根据本申请的实施例的方法的步骤。应当理解的是，前面或后面的步骤不一定按照顺序来精确的进行。相反，可以 按照倒序或同时处理各种步骤。同时，也可以将其他操作添加到这些过程中，或从这些过程移除某一步或数步。
物联网可以作为互联网的一种延伸，它包括互联网及互联网上所有的资源，兼容互联网所有的应用。随着物联网技术在各个领域的应用，出现了诸如智能家居、智能交通、智慧健康等各种新的应用领域。
在与物联网相关的各种应用不断发展的过程中，以及随着物联网技术研发及市场推广的不断深入，为了促进国际物联网标准化活动的协调统一，减少重复的工作，保障各行业的物联网功能一致，成立了物联网领域国际标准化组织“oneM2M”，并输出了关于oneM2M的技术规范和技术报告。
在oneM2M架构中，需要oneM2M实体拥有一定的计算能力与存储能力。然而，不同的oneM2M实体在运行能力等方面存在着差异。例如，在各种oneM2M实体中，通用服务实体CSE的运行能力可能较强，而一些应用实体AE的运行能力可能较弱。例如在智能家居场景中，作为通用服务实体CSE的网关的运行能力可能强于诸如智能音响、电饭煲等的实体AE。
需要注意的是，本文中所描述的实体可以是物联网终端设备，或者可以是设备中的软件模块等。
在本文中，作为示例性的，可以将运行能力较强的实体(诸如CSE)表示为强实体，将运行能力较弱的实体的(诸如AE)表示为弱实体。所述强实体的运行能力强于所述弱实体。例如，可以依据实体的计算资源、网络资源、存储资源以及安全功能等方面来对实体的运行能力进行判断，从而确定该实体属于强实体或者弱实体。举例来说，存储空间大于10M的实体可以实施为强实体，还可以将存储能力小于10M的其余实体实施为弱实体。例如，800M CPU，其可以支持IPV6(Internet Protocol Version 6)，其可以实施为强实体，在其上可以高效的运行CSE功能，并可以作为共用的通用服务实体CSE来执行与其连接的所述弱实体的任务处理操作，例如，资源操作等。
在物联网中，对于上述运行能力较弱的弱实体而言，其具有一定的运行能力来运行oneM2M架构中的某些处理任务，但其自身的运行能力又不足以实现完整地运行oneM2M架构中的所有处理任务，换句话说，所述弱实体不具备完成所有资源管理操作的功能。在实际应用中，如果将这些弱实体单纯地作为通用实体AE，连接至共用的通用服务实体CSE，借助共用的CSE来 实现与其相关的所有的任务处理，将导致该弱实体自身能力的浪费。然而，如果将CSE功能完整地运行在这样的弱实体上，CSE功能的实现也将受到其自身运行能力的限制，导致拖慢系统整体的工作效率。这很有可能导致安全问题，也对运行速度造成很大影响。例如，所述弱实体可能无法完成对部分敏感数据的操作，或者生成自身的密钥速度过慢，这将影响该弱实体本身的运行效率以及包括该弱实体在内的整体系统的运行效率。
为了解决上述OneM2M实体由于其运行能力的差异对于OneM2M整体系统的运行速度以及安全方面等的影响的问题，本公开提供了一种用于在通用服务实体上进行任务处理的方法。所述通用服务实体CSE可以由上文所描述的强实体实施。
根据本公开实施例，提出一种集中块式的概念。所述集中块中可以包括核心块和非核心块，所述核心块内包括所述强实体，所述非核心块内包括所述弱实体。所述核心块内的强实体可以通过创建第一资源名单的方式进行管理，所述非核心块内的弱实体可以通过创建第二资源名单的方式进行管理，所述第一资源名单与第二资源名单内的实体共同组成一个集中块。所述集中块可以是一定范围内的实体的集合。
图1A中示出了根据本公开实施例的集中块的示意图。在一个集中块内，可以包括具有较强运行能力的强实体，以及运行能力较弱的弱实体，其中，在集中块内，可以由通用服务实体来实施对于集中块内的所有实体的管理功能。所述通用服务实体可以由核心块内的、具有较强运算能力的强实体来实施。在一个集中块内，可以将几个强实体同时实施为通用服务实体，以实现对于所有实体的管理功能。也可以仅将一个强实体实施为通用服务实体，例如，在所述集中块内仅包括3个(示例性的)实体的情况下，一个通用服务实体即可以实现对于该集中块的管理功能。
在图1A所示的集中块内，实施为通用服务实体CSE的强实体内存储有第一资源名单和第二资源名单，并通过所述名单建立集中块内的实体的关联关系。例如，第一资源名单内具有集中块内的核心块中包括的所有的强实体的信息，例如，图1A中示出的强实体1CSE1和强实体2CSE2。通过该第一资源名单，通用服务实体可以实现任务处理请求的调度。例如，在接收到其自身不执行的请求时，该通用服务实体可以将该请求转发给第一资源名单 内的其他强实体(诸如CSE1)以执行该请求。
所述第二资源名单内具有集中块内的非核心块中包括的弱实体的信息，例如，图1A中示出的弱实体1AE1和弱实体2AE2。通过该第二资源名单，通用服务实体可以实现集中块内的实体的安全管理。
例如，在智能家居场景的集中块中可以诸如包括网关、智能音响、灯和电饭煲等的实体，其中，具有较强运行能力的网关和智能音响可以作为核心块成员，即，作为强实体。所述网关和智能音响的信息可以存储在第一资源名单中以彼此关联。相比于所述网关和智能音响，智能家居中的灯、电饭煲等实体具有较弱的运行能力，其无法完成对部分敏感数据的操作，或者生成自身的密钥速度过慢，而需要借助运行能力较强的网关等实体的运行能力来完成上述处理任务。可以将智能家居场景中的所述灯、电饭煲等弱实体作为非核心块成员，所述弱实体的信息可以存储在第二资源名单中。
所述由网关和智能音响组成的核心块与由灯和电饭煲组成的非核心块共同构成此智能家居场景的一个集中块。在此集中块内，核心块内的强实体可以作为非核心块内的弱实体的通用服务实体，完成与所述弱实体相关的处理任务。此外，所述核心块内的强实体也可以实现对于核心块内的其他强实体的管理，例如安全认证等。由此，在此集中块内，可以实现由核心块内的实体对于整个集中块内的所有实体的管理以及资源调度，从而提高集中块整体的运行效率。
在根据本公开的上述集中块的基础上，提出一种在通用服务实体上进行任务处理的方法，所述通用服务实体可以为核心块内的强实体。图1B示出了根据本公开实施例的在通用服务实体上进行任务处理的方法的流程图。以下将结合图1B对根据本公开实施例的任务处理方法进行详细介绍。
如图1B所示，在步骤S101，通用服务实体接收进行任务处理的请求。例如，所述任务处理的请求可以包括认证请求、创建请求、更新请求、获取请求、通知请求、删除请求等。所述通用服务实体可以为核心块内的任意的一个强实体，诸如，CSE 1。所述任务处理的请求可以由与该强实体处于同一集中块的、非核心块中的一个弱实体发出。例如，在智能家居的场景中，所述弱实体在需要进行安全认证时，可以向强实体发出安全认证的请求，其请求借助该强实体来生成该弱实体的认证秘钥，从而获得在该智能家居的集 中块内获取相关数据的权限。
接着，在步骤S102，在接收到任务处理的请求后，所述通用服务实体CSE 1可以确定其自身是否执行该任务处理的请求。例如，所述通用服务实体CSE 1可以基于自身的运算能力、存储能力以及安全等级等来判断其是否执行接收的任务处理请求。例如，在所述智能家居场景的集中块内，所述网关在接收到由作为弱实体的电饭煲发出的认证请求时，所述网关可能正在处理其他的弱实体请求的处理任务，或者所述网关可以对此认证请求所需的运行能力进行判断，并可以根据自身当前的运算能力、存储能力来确定其自身是否执行该认证请求。例如，当所述网关确定，如果其自身执行此认证请求需要花费较长的时间完成，可能影响整体系统的运行效率。此时，所述网关可以确定其自身不执行该认证请求。所述运行时间与运行效率的关系可以进行人为地设定，例如，可以对所述网关进行设置，当执行某一处理任务需要花费的时间长于1分钟时，则确定其自身不执行该任务，此时间设置仅为示例性的，可以根据集中块所处的具体场景进行相应的调整。
如果确定其自身不执行该任务处理的请求，则在步骤S103，所述通用服务实体CSE 1将该请求转发给另一通用服务实体，诸如，CSE 2。根据本公开实施例，所述通用服务实体CSE 1与该另一通用服务实体CSE 2具有关联关系。例如，所述通用服务实体CSE 1中可以存储有资源名单，并通过该资源名单来确定与其关联的其他的通用服务实体CSE。
举例来说，在智能家居场景的集中块内，如果核心块内的某一强实体1接收到任务处理的请求，而基于其自身当前的运行能力而确定不执行该任务处理，所述强实体1可以将该任务请求转发给该核心块内的其他强实体，诸如强实体2，以请求由该强实体2来处理该任务请求。所述强实体1与强实体2的信息可以共同记录于第一资源名单内，集中块内的所述强实体均保存有该第一资源名单。例如，强实体1可以通过查询第一资源名单的方式来确定与其具有关联关系的其他强实体，诸如强实体2，从而将该任务请求转发给该强实体2。所示核心块内的强实体1和强实体2由于具有较强的运行能力而均可以实施为通用服务实体CSE。
如果确定其自身执行该任务处理的请求，例如，所述通用服务实体CSE1确定其自身可以执行该任务处理的请求，则在步骤S104，所述通用服务实 体CSE 1执行该任务处理的请求。例如，该任务处理的请求为资源操作，所述通用服务实体CSE 1基于其自身的剩余的存储能力和运算能力判断其有能力执行该任务处理的请求，则由其自身来执行与该请求对应的处理操作，而不将该任务处理的请求转发给诸如CSE 2的其他通用服务实体。
由此，本公开提供了一种基于实体(包括通用服务实体和应用实体)的运行能力来对实体的功能以及任务处理模式进行管理的方法。
在根据本公开的实施例中，可以将属于同一网络的多个实体划分为一个集中块，其中，所述多个实体的运行能力存在差异，诸如，所述多个实体可以包括一个或多个强实体和一个或多个弱实体等。在所述集中块中，可以将有能力运行oneM2M架构的全部功能的强实体作为核心块实体成员，例如通用服务实体CSE可以作为核心块实体。此外，还可以将运行能力较弱的弱实体表示为非核心块成员，例如通用AE可以作为非核心块实体。
所述核心块可以通过组资源的方式来实现，例如，核心块内的实体的信息可以存储在例如<group>资源的成员ID序列中，由此建立核心块成员之间的关联。另外，核心块内的实体还可以通过资源索引的形式建立核心块成员之间的关联。例如，在上述智能家居的场景中，属于同一网络内的网关、智能音响、灯、电饭煲等构成一个集中块。在所述集中块内，将运行能力较强的、可以作为通用服务实体运行的强实体表示为核心块成员，将运行能力弱于所述强实体的其他实体表示为非核心块成员，所述核心块内的成员通过第一资源名单进行管理，所述非核心块内的成员通过第二资源名单进行管理。所述核心块内的成员均存储有所述第一资源名单和第二资源名单，以接收第二资源名单内的弱实体的任务处理的请求，以及在确定其自身不执行该任务处理的请求时，将该请求转发给第一资源名单中的其他强实体以完成该任务处理。
由此，根据本公开实施例，可以实现集中块内的强实体作为CSE来管理整个集中块的任务处理，核心块与非核心块成员之间相互配合以提高整个集中块的运行效率，保证集中块内的稳定性和安全性。
图2示出了根据本公开实施例的集中块的示意图。如图2所示，OneM2M设备群可以包括一个或多个集中块，诸如集中块1和集中块2。在所述集中块中可以将实体分为核心块或非核心块成员。根据本公开的实施例，在上述 集中块中，通用服务实体CSE可以作为核心块成员，而弱实体可以作为非核心块成员。例如，在集中块1中的核心块可以包括左侧虚线方框内由圆形所表示3个通用服务实体，而非核心块可以包括右侧虚线方框内由三角形所表示的3个弱实体。
可选地，对于所述设备群中的其他的集中块，例如，集中块2中的核心块和非核心块内的实体的数目可以与集中块1相同，也可以不同。如图2所示出的，集中块2中的核心块可以包括左侧虚线方框内由圆形所表示的2个通用服务实体，非核心块可以包括右侧虚线方框内由三角形所表示的4个弱实体。
在系统运行过程中，集中块内的弱实体可以请求核心块内的通用服务实体CSE来执行相应任务处理。例如，所述任务处理可以包括实体认证、实体授权等。
根据本公开实施例，核心块内的通用服务实体的管理地位是平等的，并能对属于同一核心块内的其他的通用服务实体进行管理。
在根据本公开的实施例中，核心块内的通用服务实体中可以存储有第一资源名单，该第一资源名单中包含有与该通用服务实体相关联的所有通用服务实体的信息。例如，上述通用服务实体CSE 1中存储的第一资源名单中包括通用服务实体CSE 2的信息。在通用服务实体CSE 1接收到任务处理的请求，并确定其自身暂时不执行该的任务处理的请求时(例如，通用服务实体CSE 1在短时间内接收到多个处理请求，超出其任务处理能力，执行所有的请求可能会导致请求拥塞)，CSE 1可以将该任务处理的请求转发给通用服务实体CSE 2。所述第一资源名单中的信息可以包括通用服务实体的身份标识、运行能力等，还可以包括通用服务实体的其他信息。
根据本公开的一个实施例，所述核心块内的通用服务实体不仅需要具有较强的计算能力与存储能力等，还需要具有较高的安全等级。所述第一资源名单中的信息对应于该核心块内包括的通用服务实体的信息，运行一段时间后，该资源名单中的各个通用服务实体可以更新该第一资源名单中的信息。
所述通用服务实体可以对所述第一资源名单中的其他实体进行管理。所述管理，例如，可以是定期地更新第一资源名单中的实体的信息。此外，所述管理还可以包括添加操作，例如向通过安全验证的新的强实体分配认证标 识，并将该实体的信息添加到该第一资源名单中。所述管理还可以包括移出操作，例如可以将不符合安全等级的强实体的信息从第一资源名单中移出。
根据本公开实施例，所述核心块内的通用服务实体可以确定第一资源名单中的其他通用服务实体是否满足第一标准，并且将不满足第一标准的通用服务实体移出所述第一资源名单，从而更新该第一资源名单。所述第一标准作为判断实体是否具备强实体能力的标准，可以基于实体的运算能力、存储能力和安全等级中的至少一种来确定所述第一标准。例如，可以基于计算资源、网络资源、存储资源以及安全功能等方面对实体的能力进行判断，如上所述的，具有较强存储能力的800M CPU在集中块中可以实施为强实体。
例如，所述核心块内的通用服务实体不仅需要具有较强的计算能力与存储能力等，还需要具有较高的安全等级。每隔一段时间间隔，该资源名单中的各个通用服务实体可以更新该第一资源名单中的信息，例如，将不符合核心块实体安全性标准的通用服务实体的信息从所述第一资源名单中移出。根据本公开的一个实施例，所述时间间隔可以基于集中块对安全性的要求来设定，例如，所述核心块对于其中的强实体的安全性要求较高，则可以缩短所述时间间隔。此外，还可以基于集中块的管理方的业务需求来对所述时间间隔进行设置，并随需求的改变而改变，在此不对时间间隔进行限制。
在所述集中块内，所述核心块内的强实体可以对所有成员进行管理，还可以向非核心块内的实体提供其请求的CSE功能，所述核心块内的实体与非核心块内的实体彼此配合，以共同地、高效地完成整个集中块的功能。其中，图3A和图3B示出了根据本公开实施例的集中块进行任务处理的流程图。
下面，将结合图3A和图3B来对根据本公开的用于在通用服务实体上进行任务处理的方法及其实施例进行详细的描述。
核心块内的强实体可以实施为通用服务实体CSE1，在需要进行某项任务处理时，CSE1首先确定其自身是否执行该任务处理。例如，CSE1可以基于自身当前的状态来确定是否执行该处理任务。举例来说，CSE1可以依据自身的CPU占有率、带宽占有率、空闲存储空间等方面来确定自身是否执行该处理任务。在CSE1确定其自身有能力执行该任务处理的情况下，则直接执行该任务处理；在确定其自身不执行该任务处理的情况下，则CSE1向与其属于核心块的其他通用服务实体CSE2发送该任务处理的请求。例如，如 图3A所示，在步骤S1，弱实体可以向通用服务实体CSE 1发送任务处理的请求。例如，所述任务处理的请求可以是使用CSE功能的请求。所述使用CSE功能的请求可以是由弱实体发送给CSE 1、以请求CSE 1执行相应的数据处理的请求，所述弱实体由于其自身运行能力的限制而无法执行所述CSE功能。
该CSE 1可以判断其自身是否处理该任务处理的请求。根据本公开实施例，该通用服务实体CSE 1在接收到非核心块内的实体发出的使用CSE功能的请求时，可以将接收到的请求存入请求队列中。
该CSE 1可以自动地调节任务处理的分配，例如，可以基于请求队列内的请求的数目来确定其自身是否处理该请求。例如，在请求队列中包括的请求的数目小于第一阈值时，则确定其自身执行该任务处理的请求；在请求队列中包括的请求的数目大于或等于该第一阈值时，则确定其自身不执行该任务处理的请求。例如，可以基于集中块对于任务处理效率的要求来设定该第一阈值，例如，如果集中块对于任务处理的效率要求较高，则可以设定数值较小的第一阈值。
例如，在智能家居的场景的集中块内，可以认为其对于有关认证请求的任务处理的效率要求较高，当需要有新的实体加入到此集中块内时，希望能快速的进行安全认证以完成新实体的添加处理。此时，可以设置该第一阈值为3(仅为示例性的)。即，作为CSE1的网关在接收到认证请求时，如果判断其自身的请求队列中的请求的数目大于或等于3时，例如为5时(仅为示例性的)，则该CSE1确定其完成该认证处理的请求需要较长的时间，因为在执行该认证处理的请求之前，该CSE1仍需处理其自身请求队列内的5个未处理的请求。在此中情形下，该CSE1可以确定其自身不执行该认证请求，并将该认证请求转发给与该CSE1属于同一核心块内的其他通用服务实体CSE2，例如，智能音响。
根据本公开的另一个实施例，通用服务实体也可以依据任务处理的请求的内容来确定其是否执行该请求，例如，如果是认证请求则由自身执行，如果是关于更新数据的请求的则转发给其他的通用服务实体。在此实施例中，核心块内的通用服务实体可以依据任务处理的请求的内容来进行运行管理与分配。例如，在智能家居的场景的集中块内，可以设定由网关来执行关于认 证、添加等的请求，由智能音响来执行关于数据处理等的请求。由此，在网关接收到电饭煲发送的关于数据更新的请求后，可以确定其自身不执行该请求，并将该请求转发给智能音响。类似地，当智能音响接收到关于认证的请求后，可以确定其自身不执行该请求，并将该请求转发给网关。
在步骤S2，该CSE 1确定其可以处理当前接收的请求。则在步骤S3，该CSE 1可以向该弱实体发送回应请求，允许其使用CSE功能。在收到回应消息后，在步骤S4，该弱实体可以将数据放入消息，并使用CSE 1的CSE功能。在步骤S5，该CSE 1进行与该请求对应的CSE功能操作。最后，在步骤S6，所述CSE 1处理完成，并将处理结果返回给该弱实体。
如图3B所示，步骤S7，弱实体向CSE 1请求使用CSE功能。接着，步骤S8，该CSE 1可以将该请求存入消息队列，并判断该消息队列中的未处理的请求的数目，例如，未处理的请求的数目超过了所述第一阈值，则确认该CSE 1自身不执行该请求，为了避免CSE 1中的请求拥塞，需要将请求转发给核心块内的其他的通用服务实体，例如，CSE 2。
在步骤S9，CSE 1可以将该请求转发给CSE 2。此外，根据本公开的一个实施例，CSE 1还可以基于请求队列内的请求的优先级来确定要转发的请求。例如，非核心块内的实体向CSE发送的请求具有优先级属性，例如，QOS(quality of service)参数，其用来标识当前请求的优先级。此时该CSE1可以根据这些请求的优先级来确定处理各个消息的顺序。例如，在CSE 1确定请求队列中的请求的数目超出了第一阈值时，则其可以将请求队列中优先级最高的请求转发给空闲的CSE 2。其中，CSE 1与CSE 2属于同一个核心块。例如，CSE 1可以通过第一资源名单来确认与其属于同一核心块的成员CSE 2。
接着，在步骤S10，CSE 2确定其能处理该请求，并在步骤S11向CSE 1回应允许使用CSE功能的请求。在步骤S12，CSE 1可以将CSE 2允许使用CSE功能的信息发送给作为请求方的弱实体。在步骤S13，弱实体将数据放入消息，以使用CSE功能。在步骤S14，CSE 1在接收到数据后将其转发给CSE 2。接着，在步骤S15，CSE 2允许弱实体使用其CSE功能来进行CSE功能操作，并在步骤S16将处理结果发送给CSE 1。然后，在步骤S17，CSE1将处理结果转发给请求方的弱实体。
根据以上结合图3A和图3B的描述，可以理解利用本公开提出的任务处理方法的运行过程。其中，所述集中块内包括核心块和非核心块，核心块可以包括具有较强处理能力的强实体，所述强实体可以实施为通用服务实体，以向其他实体提供CSE功能。所述非核心块可以包括具有较弱处理能力的弱实体。所述核心块内的实体可以对集中块内的所有实体进行管理，并处理非核心块内的弱实体无法处理或者耗时的任务请求。核心块与非核心块相互配合地来完成集中块内的任务，并且，通过上述图3B中示出的自动地对请求进行任务调度，使得整个集中块的任务需求不会发生堆积，从而提高集中块的处理能力与效率。
对于oneM2M架构中的实体来说，每一次发起者与接收者之间的通信需要在双方注册相应的资源以及OneM2M资源的声明版本，然后这些资源会通过在本地改动后同步至远程的资源的声明版本来实现数据递交。由此，在这些消息传递过程中首先会进行一个身份认证的过程，还可以包括数据加解密的过程。
在根据本公开的实施例中，所述任务处理的请求还可以包括认证请求，即非核心块内的实体向核心块内的通用服务实体发送认证的请求，以获得认证标识，通过该认证标识，该实体可以与集中块内的其他实体进行通信，而无需再次进行认证。图4示出了根据本公开实施例的进行认证请求的流程图。
如图4所示，在以智能家居场景为例的集中块中，其中，核心块内的实体可以包括网关和智能音响，非核心块内的实体可以包括灯和电饭煲。例如，电饭煲可以向智能音响发送认证的请求，该智能音响基于自身的计算空间确定可以通过其自身来执行电饭煲的认证请求，则其直接地处理该认证请求。智能音响然后确定发送该认证请求的实体，即电饭煲，是否满足第二标准，如果满足，则可以认为该电饭煲通过了安全认证，并将该通过认证的电饭煲的信息存入第二资源名单，以更新所述第二资源名单。其中，所述第二资源名单也可以称为白名单，其中存储有非核心块内通过了安全认证的实体的信息。然后，智能音响可以向上述第一资源名单中的其他的通用服务实体发送该更新的第二资源名单，并向该电饭煲发送认证标识。电饭煲可以依据该认证标识来与集中块内的其他实体进行通信，具体的，可以在电饭煲内创建一个“令牌资源”来标识其已通过认证，即表示其符合安全标准。
所述第二标准作为判断实体是否安全的标准，所述通用服务实体可以基于弱实体的安全等级来确定所述第二标准。根据本公开的另一实施例，所述第二资源名单中可以具有集中块中所有通过认证的实体的信息，即，其既可以包括核心块内的强实体也可以包括非核心块的弱实体的信息。如此，作为通用服务实体的强实体可以通过所述第二资源名单对集中块内的所有的安全实体进行管理。根据本公开的一个实施例，核心块实体的信息可以默认地存在于所述第二资源名单中。换句话说，在该智能家居的集中块中，由第一资源名单关联的核心块内的强实体默认为符合第二资源名单的安全认证标准(诸如第二标准)。
此外，如图4所示，在作为非核心块实体的灯向智能音响发送认证请求之后，智能音响基于其计算空间不足，确定其自身不执行该认证请求。然后，智能音响可以将该认证请求转发给与智能音响属于同一核心块的网关。或者，根据本公开的另一实施例，智能音响也可以可选择地将其请求队列中优先级较高的请求转发给网关处理。
接着，所述网关可以处理该认证请求，如果确定灯满足第二标准，则将灯的信息加入所述第二资源名单。所述智能音响向灯转发认证标识，以标识其通过了认证。
根据本公开实施例，所述智能音响或者网关可以基于运算能力、存储能力和安全等级中的至少一种来确定所述第二标准。例如，在认证请求中，可以评估非核心实体的安全等级，只对安全等级达标的实体发送认证标识，以维持系统整体的安全性。
根据本公开实施例，所述核心块中的通用服务实体还能够对所述第二资源名单中的实体进行管理。
例如，如图4所示的智能音响在向电饭煲发送了认证标识，并将电饭煲的信息存入第二资源名单之后，还可以定期地从所述第二资源名单中移出该电饭煲的信息，以更新所述第二资源名单。例如，经过一段时间间隔后，电饭煲会再次验证电饭煲是否符合所述第二标准，如果不符合，则将其移出第二资源名单。接着，智能音响可以向移出第二资源名单的实体，即电饭煲发送通知消息，并向所述第一资源名单中的通用服务实体发送更新的第二资源名单。例如，在智能家居的集中块内，作为通用服务实体的智能音响可以实 施第二资源名单内的信息的定期更新处理。弱实体通过向智能音响发送认证请求而通过了安全认证，并具有用于与其他实体进行通信的令牌资源，经过10天后(仅为示例性的)，所述智能音响可以自动地将该弱实体的信息移出该第二资源名单，并解除该令牌资源的有效性。
根据本公开的实施例，所述非核心块内的实体可以从智能音响处接收将将其信息移出第二资源名单的通知消息。在接收到该通知消息之后，该电饭煲可以向所述第一资源名单中的通用服务实体发送认证请求，以重新获得认证标识。
在此种情况下，该弱实体需要再次向智能音响发送安全认证请求，如果此时智能音响确定该弱实体不满足第二标准，则不通过该实体的认证请求。由此，可以实现集中块内的安全管理功能，防止敏感数据泄露，从而保证整个集中块的安全性与稳定性。
此外，所述核心块内的通用服务实体还可以根据集中块的管理需求的改变而改变所述第二标准。
利用本公开提出的上述集中块式的任务处理方法，通过核心块与非核心块之间的配合能有效的提高系统运行的效率，充分发挥弱实体自身的运行能力，同时借助诸如通用服务实体的强实体来实现其自身无法实现或耗时较长的任务(诸如，敏感数据的操作或者生成自身的密钥速度过慢等)。核心块内的通用服务实体之间也能相互配合，自动地进行任务调度，有效避免任务请求阻塞等问题。这样一来，大大提高了个体的运行速度以及整体系统的运行效率。
图5示出了根据本公开实施例的用于进行任务处理的装置的示意图。所述装置500可以包括一个或多个处理器501以及一个或多个存储器502。其中，所述处理器501中存储有计算机可读代码，所述计算机可读代码当由所述一个或多个处理器执行时可以进行如上所述的用于在通用服务实体上进行任务处理的方法，在此不再赘述。
根据本公开的另一方面，还提供了一种通用服务实体，图6示出了根据本公开赛实施例的通用服务实体600的示意性框图。
如图6所示，所述通用服务实体可以包括接收单元601和处理单元602。所述接收单元601可以配置成接收进行任务处理的请求。所述处理单元602 可以配置成确定该通用服务实体自身是否执行该任务处理的请求：在确定自身不执行该任务处理的请求的情况下，将该请求转发给另一通用服务实体；在确定自身执行该任务处理的请求的情况下，该通用服务实体执行该任务处理的请求，其中，该通用服务实体与该另一通用服务实体具有关联关系。例如，可以通过资源名单的方式来建立所述通用服务实体与另一通用服务实体之间的关联关系。
根据本公开实施例，该通用服务实体600中存储有第一资源名单，该第一资源名单中包含与该通用服务实体相关联的所有通用服务实体的信息。所述处理单元602还可以配置成确定第一资源名单中的其他通用服务实体是否满足第一标准，并且将不满足第一标准的通用服务实体移出所述第一资源名单，从而更新第一资源名单。
根据本公开实施例，该通用服务实体600基于自身的运算能力、存储能力和安全等级中的至少一种来确定其自身是否执行该任务处理的请求。例如，在所述智能家居场景的集中块内，所述网关在接收到由作为弱实体的电饭煲发出的认证请求时，所述网关可能正在处理其他的弱实体请求的处理任务，或者所述网关可以对此认证请求所需的运行能力进行判断，并可以根据自身当前的运算能力、存储能力来确定其自身是否执行该认证请求。
根据本公开实施例，所述处理单元602还可以配置成将接收到的该任务处理的请求存入请求队列，在请求队列中包括的请求的数目小于第一阈值时，确定其自身执行该任务处理的请求；在请求队列中包括的请求的数目大于或等于该第一阈值时，确定其自身不执行该任务处理的请求。例如，如上所述的，可以基于集中块对于任务处理效率的要求来设定该第一阈值，在此不再赘述。
根据本公开实施例，所述任务处理的请求可以包括认证请求。在所述任务处理的请求是认证请的情况下，所述处理单元602还可以配置成确定发送该认证请求的实体是否满足第二标准，将通过认证的实体的信息存入第二资源名单，以更新所述第二资源名单；向所述第一资源名单中的通用服务实体发送更新的第二资源名单；以及向第二资源名单中的实体发送认证标识。
根据本公开实施例，所述处理单元602还可以配置成从所述第二资源名单中移出实体的信息，以更新所述第二资源名单；向移出第二资源名单的实 体发送通知消息；和向所述第一资源名单中的通用服务实体发送更新的第二资源名单。
如上所述的，所述核心块内的强实体可以通过创建第一资源名单的方式进行管理，所述非核心块内的弱实体可以通过创建第二资源名单的方式进行管理，所述第一资源名单与第二资源名单内的实体共同组成一个集中块。所述集中块是一定范围内的实体的集合。
根据本公开实施例，所述处理单元602还可以配置成：在确定自身不执行该处理的情况下，接收该另一通用服务实体对应于该请求的回应；从请求方接收对应于该请求的数据，将该数据转发给该另一通用服务实体；向请求方发送从该另一服务主体接收的对应于该请求的处理结果。利用本公开提出的上述通用服务实体，能实现集中块式的任务处理方法，通过核心块与非核心块之间的配合来有效地提高集中块内的运行效率，充分发挥弱实体自身的运行能力，同时借助诸如通用服务实体的强实体来实现其自身无法实现或耗时较长的任务(诸如，敏感数据的操作或者生成自身的密钥速度过慢等)。核心块内的通用服务实体之间也能相互配合，自动地进行任务调度，有效避免任务请求阻塞等问题。这样一来，大大提高了个体的运行速度以及整体系统的运行效率。
根据本公开实施例，还提供了一种计算机存储介质。其中，所述计算机存储介质中存储有计算机可读代码，所述计算机可读代码在由一个或多个处理器执行时进行可以进行如上所述的用于在通用服务实体上进行任务处理的方法，在此不再赘述。
本公开提供了一种采用集中块的方式管理大规模的oneM2M架构的方法。所述集中块可以包括核心块和非核心块，所述核心块可以包含具有较强运行能力的强实体，所述强实体可以实施为执行其他实体任务请求的通用服务实体，所述非核心块可以包含具有较弱运行能力的弱实体。提出了一种用于在通用服务实体上进行任务处理的方法，包括：所述通用服务实体可以接收来自非核心块实体的进行任务处理的请求；确定该通用服务实体自身是否执行该任务处理的请求，在确定自身不执行该任务处理的请求的情况下，将该请求转发给与该通用服务实体具有关联关系的另一通用服务实体；在确定自身执行该任务处理的请求的情况下，该通用服务实体自身执行该任务处理 的请求。
通用服务实体通过上述进行任务处理的方法，核心块实体与非核心块相互配合以高效的运行整个集中块内的任务管理。其中，所述核心块内可以包括具有较强运行能力的强实体，所述强实体可以实施为通用服务实体以向其他实体提供CSE功能，所述非核心块内可以包括具有较弱处理能力的弱实体，所述强实体的运行能力强于所述弱实体。
所述非核心块内的弱实体可以向核心块内的实施为通用服务实体的强实体发送任务请求，借助通用服务实体较强的处理能力来解决弱实体自身不执行的任务处理，例如该弱实体的运算能力无法处理或耗时较长的任务请求。所述通用服务实体在接收到任务处理的请求后，也可以基于自身当前的能力来确定其是否执行与该请求对应的处理，为避免请求拥塞或者优化任务处理流程，所述通用服务实体可以将接收到的请求转发给核心块内的其他的空闲的通用服务实体，以实现核心块成员之间的任务调度。此外，核心块成员还可以实现对于整个集中块内的实体的管理，例如，可以向非核心块实体发送认证标识，以提高集中块的安全等级。利用根据本公开的上述任务处理的方法可以大大提高整体系统的运行效率与各个实体的运行速度。
除非另有定义，这里使用的所有术语(包括技术和科学术语)具有与本发明所属领域的普通技术人员共同理解的相同含义。还应当理解，诸如在通常字典里定义的那些术语应当被解释为具有与它们在相关技术的上下文中的含义相一致的含义，而不应用理想化或极度形式化的意义来解释，除非这里明确地这样定义。
以上是对本发明的说明，而不应被认为是对其的限制。尽管描述了本发明的若干示例性实施例，但本领域技术人员将容易地理解，在不背离本发明的新颖教学和优点的前提下可以对示例性实施例进行许多修改。因此，所有这些修改都意图包含在权利要求书所限定的本发明范围内。应当理解，上面是对本发明的说明，而不应被认为是限于所公开的特定实施例，并且对所公开的实施例以及其他实施例的修改意图包含在所附权利要求书的范围内。本发明由权利要求书及其等效物限定。
本申请要求于2018年09月04日提交的中国专利申请第201811022263.7的优先权，该中国专利申请的全文通过引用的方式结合于此以作为本申请的 一部分。

Claims (20)

  1. 一种用于在通用服务实体上进行任务处理的方法，包括：
    接收进行任务处理的请求，
    确定该通用服务实体自身是否执行该任务处理的请求，
    在确定自身不执行该任务处理的请求的情况下，将该请求转发给另一通用服务实体，其中，该通用服务实体与该另一通用服务实体具有关联关系；
    在确定自身执行该任务处理的请求的情况下，该通用服务实体执行该任务处理的请求。
  2. 根据权利要求1所述的方法，其中，在该通用服务实体中存储有第一资源名单，该第一资源名单中包含与该通用服务实体相关联的所有通用服务实体的信息。
  3. 根据权利要求1或2所述的方法，其中，该通用服务实体确定第一资源名单中的其他通用服务实体是否满足第一标准，并且将不满足第一标准的通用服务实体移出所述第一资源名单，从而更新第一资源名单。
  4. 根据权利要求1-3中任一项所述的方法，其中，该通用服务实体基于自身的运算能力、存储能力和安全等级中的至少一种来确定该通用服务实体自身是否执行该任务处理的请求。
  5. 根据权利要求1-4中任一项所述的方法，还包括：该通用服务实体将接收到的该任务处理的请求存入请求队列：
    在请求队列中包括的请求的数目小于第一阈值时，确定其自身执行该任务处理的请求，
    在请求队列中包括的请求的数目大于或等于该第一阈值时，确定其自身不执行该任务处理的请求。
  6. 根据权利要求2所述的方法，其中，所述任务处理的请求包括认证请求，所述方法还包括：
    确定发送该认证请求的实体是否满足第二标准，
    将通过认证的实体的信息存入第二资源名单，以更新所述第二资源名单，
    向所述第一资源名单中的通用服务实体发送更新的第二资源名单，
    向第二资源名单中的实体发送认证标识。
  7. 根据权利要求6所述的方法，还包括，从所述第二资源名单中移出实体的信息，以更新所述第二资源名单；
    向移出第二资源名单的实体发送通知消息；和
    向所述第一资源名单中的通用服务实体发送更新的第二资源名单。
  8. 根据权利要求3或6所述的方法，其中，基于运算能力、存储能力和安全等级中的至少一种来确定所述第一标准或第二标准。
  9. 根据权利要求1-8中任一项所述的方法，其中，所述通用服务实体配置成能够对所述第一资源名单或第二资源名单中的实体进行管理。
  10. 根据权利要求6所述的方法，其中，所述任务处理的请求还包括创建请求、更新请求、获取请求、通知请求、删除请求中的至少一种。
  11. 根据权利要求1-10中任一项所述的方法，其中，在确定自身不执行该处理的情况下，所述方法还包括：
    接收该另一通用服务实体对应于该请求的回应，
    从请求方接收对应于该请求的数据，将该数据转发给该另一通用服务实体，
    向请求方发送从该另一服务主体接收的对应于该请求的处理结果。
  12. 一种通用服务实体，包括：
    接收单元，配置成接收进行任务处理的请求；
    处理单元，配置成确定该通用服务实体自身是否执行该任务处理的请求：
    在确定自身不执行该任务处理的请求的情况下，将该请求转发给另一通用服务实体；
    在确定自身执行该任务处理的请求的情况下，该通用服务实体执行该任务处理的请求，
    其中，该通用服务实体与该另一通用服务实体具有关联关系。
  13. 根据权利要求12所述的通用服务实体，其中，该通用服务实体中存储有第一资源名单，该第一资源名单中包含与该通用服务实体相关联的所有通用服务实体的信息，
    所述处理单元还配置成确定第一资源名单中的其他通用服务实体是否满足第一标准，并且将不满足第一标准的通用服务实体移出所述第一资源名单，从而更新第一资源名单。
  14. 根据权利要求12或13所述的通用服务实体，其中，该通用服务实体基于自身的运算能力、存储能力和安全等级中的至少一种来确定其自身是否执行该任务处理的请求。
  15. 根据权利要求12-14中任一项所述的通用服务实体，所述处理单元还配置成将接收到的该任务处理的请求存入请求队列，
    在请求队列中包括的请求的数目小于第一阈值时，确定其自身执行该任务处理的请求；
    在请求队列中包括的请求的数目大于或等于该第一阈值时，确定其自身不执行该任务处理的请求。
  16. 根据权利要求12-15中任一项所述的通用服务实体，其中，所述任务处理的请求包括认证请求，
    所述处理单元还配置成确定发送该认证请求的实体是否满足第二标准，将通过认证的实体的信息存入第二资源名单，以更新所述第二资源名单；
    向所述第一资源名单中的通用服务实体发送更新的第二资源名单；以及
    向第二资源名单中的实体发送认证标识。
  17. 根据权利要求16所述的通用服务实体，所述处理单元还配置成从所述第二资源名单中移出实体的信息，以更新所述第二资源名单；向移出第二资源名单的实体发送通知消息；和向所述第一资源名单中的通用服务实体发送更新的第二资源名单。
  18. 根据权利要求12-17中任一项所述的通用服务实体，其中，所述处理单元还配置成：在确定自身不执行该处理的情况下，接收该另一通用服务实体对应于该请求的回应；
    从请求方接收对应于该请求的数据，将该数据转发给该另一通用服务实体；
    向请求方发送从该另一服务主体接收的对应于该请求的处理结果。
  19. 一种用于进行任务处理的装置，包括：
    一个或多个处理器；
    一个或多个存储器，其中存储了计算机可读代码，所述计算机可读代码在由所述一个或多个处理器执行时进行如权利要求1-11中任一项所述的方法。
  20. 一种计算机存储介质，其中存储有计算机可读代码，所述计算机可读代码在由一个或多个处理器执行时进行如权利要求1-11中任一项所述的方法。
PCT/CN2019/093084 2018-09-04 2019-06-26 用于在通用服务实体上进行任务处理的方法、通用服务实体、进行任务处理的装置和介质 WO2020048194A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/272,539 US11700189B2 (en) 2018-09-04 2019-06-26 Method for performing task processing on common service entity, common service entity, apparatus and medium for task processing

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811022263.7 2018-09-04
CN201811022263.7A CN110875945B (zh) 2018-09-04 2018-09-04 用于在通用服务实体上进行任务处理的方法、装置和介质

Publications (1)

Publication Number Publication Date
WO2020048194A1 true WO2020048194A1 (zh) 2020-03-12

Family

ID=69716770

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/093084 WO2020048194A1 (zh) 2018-09-04 2019-06-26 用于在通用服务实体上进行任务处理的方法、通用服务实体、进行任务处理的装置和介质

Country Status (3)

Country Link
US (1) US11700189B2 (zh)
CN (1) CN110875945B (zh)
WO (1) WO2020048194A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110971533B (zh) * 2018-09-30 2023-02-03 京东方科技集团股份有限公司 用于数据通信的方法、服务器装置、客户端装置和介质
CN116250219A (zh) * 2020-08-04 2023-06-09 北京大学深圳研究生院 一种面向网内算力或资源服务的通信方法
CN114417870B (zh) * 2021-11-30 2024-06-21 北京天融信网络安全技术有限公司 一种安全实体的检测方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015096012A1 (zh) * 2013-12-23 2015-07-02 华为终端有限公司 一种会话处理方法及设备
WO2015106382A1 (zh) * 2014-01-14 2015-07-23 华为技术有限公司 一种服务质量的协商方法、设备及系统
CN105516271A (zh) * 2015-11-30 2016-04-20 电子科技大学 业务处理系统、业务处理方法及装置
CN108075908A (zh) * 2016-11-11 2018-05-25 京东方科技集团股份有限公司 处理操作请求的方法及装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2110732A3 (en) * 1995-02-13 2009-12-09 Intertrust Technologies Corporation Systems and methods for secure transaction management and electronic rights protection
CN101009640B (zh) * 2005-11-05 2011-04-06 华为技术有限公司 服务网络中网关间业务转发的方法及其服务网关
CN103023935B (zh) * 2011-09-23 2018-06-26 中兴通讯股份有限公司 M2m平台云系统及其处理m2m服务的方法
CN103516744A (zh) * 2012-06-20 2014-01-15 阿里巴巴集团控股有限公司 一种数据处理的方法和应用服务器及集群
KR20150063906A (ko) * 2013-11-29 2015-06-10 주식회사 케이티 M2m 환경에서 사용 가능한 장치를 검색하는 방법 및 장치
CN107567006A (zh) * 2016-06-30 2018-01-09 中兴通讯股份有限公司 M2m应用的信息方法、cse及ae

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015096012A1 (zh) * 2013-12-23 2015-07-02 华为终端有限公司 一种会话处理方法及设备
WO2015106382A1 (zh) * 2014-01-14 2015-07-23 华为技术有限公司 一种服务质量的协商方法、设备及系统
CN105516271A (zh) * 2015-11-30 2016-04-20 电子科技大学 业务处理系统、业务处理方法及装置
CN108075908A (zh) * 2016-11-11 2018-05-25 京东方科技集团股份有限公司 处理操作请求的方法及装置

Also Published As

Publication number Publication date
CN110875945A (zh) 2020-03-10
US11700189B2 (en) 2023-07-11
CN110875945B (zh) 2023-05-09
US20210328887A1 (en) 2021-10-21

Similar Documents

Publication Publication Date Title
CN108769150B (zh) 区块链网络的数据处理方法、装置、集群节点和存储介质
JP7432686B2 (ja) ブロックチェーンネットワークにおける効率的な伝播のための確率的リレー
US20160072843A1 (en) Policy-Based Control Layer in a Communication Fabric
WO2020048194A1 (zh) 用于在通用服务实体上进行任务处理的方法、通用服务实体、进行任务处理的装置和介质
US11252196B2 (en) Method for managing data traffic within a network
US20200177473A1 (en) Network component management method and network device
JP2018509827A (ja) アクセスポイントステアリング
US9960998B2 (en) Forwarding packet in stacking system
WO2018219148A1 (zh) 一种管理传输网切片的方法、装置及系统
WO2019196451A1 (zh) 无线多联机系统的组网方法和装置
CN111953655B (zh) 一种通信系统中服务器响应请求消息的方法及设备
WO2021115270A1 (zh) 一种边缘应用的管理方法及装置
US10511494B2 (en) Network control method and apparatus
CN109981462B (zh) 一种报文处理方法及装置
WO2023197529A1 (zh) 针对输电线路的在线监测系统、方法、装置和主站
WO2020258099A1 (zh) 配置物联网设备的方法和物联网设备
WO2016139911A1 (ja) 情報処理装置、情報処理方法及びプログラムを格納した非一時的なコンピュータ可読媒体
US8730811B2 (en) Managing network traffic
CN107959584B (zh) 信息配置方法及装置
US11546251B2 (en) System and method for securing communication between devices on a network with multiple access points
CN111917683B (zh) 安全交互方法、计算节点、控制中心、云平台及存储介质
CN110933591B (zh) 认证方法、设备及系统
WO2024093640A1 (zh) 配置网络方法和设备
WO2023080278A1 (en) Whitelisting security method and system for iot-based multi-framework smart lighting system
CN114616564A (zh) 用于保护虚拟无线基站的网络的基于区块链的方法和系统

Legal Events

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

Ref document number: 19857413

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19857413

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 19857413

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 18/06/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19857413

Country of ref document: EP

Kind code of ref document: A1