Method for performing task processing on common service entity, common service entity, apparatus and medium for task processing

Patent metadata

Field	Value
Publication number	US-11700189-B2
Application number	US-201917272539-A
Country	US
Kind code	B2
Filing date	Jun 26, 2019
Priority date	Sep 4, 2018
Publication date	Jul 11, 2023
Grant date	Jul 11, 2023

Abstract

Provided are a method for performing task processing on a common service entity, a common service entity, an apparatus and a medium for performing task processing. The method includes: receiving a task processing request; determining whether the common service entity itself performs the processing request; forwarding the request to another common service entity in a case where it is determined that the common service entity itself does not perform the task processing request, wherein the common service entity is associated with the another common service entity; performing, by the common service entity, the task processing request in a case where it is determined that the common service entity itself performs the task processing request.

First claim

What is claimed is:

1. A method for performing task processing on a common service entity, the common service entity being a strong entity within a core block in an centralized block, the method comprising the following steps performed by the common service entity:
receiving a task processing request sent by a weak entity in a non-core block in the same centralized block as the strong entity;
determining whether the common service entity itself performs the task processing request;
forwarding the request to another common service entity which is a strong entity within another core block in the same centralized block, in a case where it is determined that the common service entity itself does not perform the task processing request, wherein the common service entity is associated with said another common service entity;
performing, by the common service entity, the task processing request in a case where it is determined that the common service entity itself performs the task processing request, wherein a first resource list is stored in the common service entity, and the first resource list contains information of all common service entities associated with the common service entity.

2. The method according to claim 1 , wherein the common service entity determines whether other common service entities in the first resource list meet the first criterion, and removes a common service entity which does not meet the first criterion from the first resource list, so as to update the first resource list.

3. The method according to claim 1 , wherein the common service entity determines whether the common service entity itself performs the task processing request based on at least one of its own computing capability, storage capacity, and security level.

4. The method according to claim 1 , further comprising: storing, by the common service entity, the task processing request in a request queue, wherein, said determining whether the common service entity itself performs the task processing request includes:
determining that the common service entity itself performs the task processing request in a case where the number of requests comprised in the request queue is less than a first threshold;
determining that the common service entity itself does not perform the request in a case where the number of requests comprised in the request queue is more than or equal to the first threshold.

5. The method of claim 1 , wherein the task processing request comprises a certification request, and the method further comprises: determining whether the entity sending the certification request meets a second criterion; storing the information of the entity passing certification in a second resource list to update the second resource list; sending the updated second resource list to the common service entities in the first resource list; sending a certification identifier to the entity passing the certification.

6. The method of claim 5 , further comprising:
removing information of an entity from the second resource list to update the second resource list;
sending a notification message to the entity which is removed from the second resource list; and
sending an updated second resource list to the common service entities in the first resource list.

7. The method according to claim 2 , wherein the first criterion or the second criterion is determined based on at least one of computing capability, storage capacity, and security level.

8. The method according to claim 1 , wherein the common service entity is configured to manage entities in the first resource list or the second resource list.

9. The method of claim 5 , wherein the task processing request further comprises at least one of a creation request, an update request, an acquisition request, a notification request, and a deletion request.

10. The method according to claim 1 , wherein, in the case where it is determined that the common service entity itself does not perform the processing, the method further comprises:
receiving a response corresponding to the request from said another common service entity,
receiving data corresponding to the request from the entity sending the request, and forwarding the data to said another common service entity,
sending processing results corresponding to the request received from said another service entity to the entity sending the request.

11. A common service entity which is a strong entity within a core block in an centralized block, the common service entity comprising:
a receiver configured to receive a task processing request sent by a weak entity in a non-core block in the same centralized block as the strong entity;
a processor configured to:
determine whether the common service entity itself performs the task processing request:
forward the request to another common service entity which is a strong entity within another core block in the same centralized block in a case where it is determined that the common service entity itself does not perform the task processing request;
perform, by the common service entity, the task processing request in a case where it is determined that the common service entity itself performs the task processing request,
wherein, the common service entity is associated with said another common service entity,
wherein a first resource list is stored in the common service entity, and the first resource list contains information of all common service entities associated with the common service entity.

12. The common service entity according to claim 11 , the processor is further configured to determine whether other common service entities in the first resource list meet the first criterion, and remove a common service entity which does not meet the first criterion from the first resource list, so as to update the first resource list.

13. The common service entity according to claim 11 , wherein the common service entity determines whether the common service entity itself performs the task processing request based on at least one of its own computing capability, storage capacity, and security level.

14. The common service entity according to claim 11 , the processor is further configured to store the received task processing request in a request queue, wherein,
it is determined that the common service entity itself performs the task processing request in a case where the number of requests comprised in the request queue is less than a first threshold;
it is determined that the common service entity itself does not perform the request in a case where the number of requests comprised in the request queue is more than or equal to the first threshold.

15. The common service entity according to claim 11 , wherein the task processing request comprises a certification request,
the processor is further configured to determine whether an entity sending the certification request meets a second criterion, and store the information of the entity passing certification in a second resource list to update the second resource list;
send the updated second resource list to the common service entities in the first resource list; and
send a certification identifier to the entity passing the certification.

16. The common service entity according to claim 15 , wherein the processor is further configured to:
remove information of an entity from the second resource list to update the second resource list;
send a notification message to the entity which is removed from the second resource list; and
send an updated second resource list to the common service entities in the first resource list.

Assignees

• Boe Technology Group Co Ltd

Inventors

• Zhao Junjie

Classifications

• H04L67/63

  Routing a service request depending on the request content or context · CPC title

• H04L41/5019

  Ensuring fulfilment of SLA · CPC title

• H04L41/5058 Primary

  Service discovery by the service manager · CPC title

• H04L41/5051 Primary

  Service on demand, e.g. definition and deployment of services in real time · CPC title

• H04L67/51

  Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title