Permission based resource and service discovery
Current discovery mechanisms lack capabilities, such as capabilities related to permissions associated with a given registrant for example. In an example embodiment, a registrant of a service layer can communicate with a network node that hosts the service layer. The network node may receive a discovery request for a resource from the registrant. The discovery may request include various context. For example, the context of the discovery request may be indicative of an operation that the registrant intends to perform on the resource, a role that the registrant intends to assume if the registrant accesses the resource, a location in which the registrant intends to access the resource, or a subscription plan that the registrant intends to use if the registrant accesses the resource. Based on the context of the discovery request, the network node may determine whether one or more resources at the service layer satisfy the discovery request.
1. A method performed by a network node that hosts a service layer and that communicates with a registrant, the method comprising:
receiving a discovery request, from the registrant, for one or more resources, the discovery request including a parameter that specifies one or more operations that the registrant intends to perform on the discovered resources, wherein the parameter comprises an indication of permission-based filter criteria;
based on the intended operations specified in the discovery request, determining whether one or more resources at the service layer have privileges defined that permit the registrant to perform the intended operations; and
sending a discovery response to the registrant, wherein the discovery response includes a list of identifiers of one or more discovered resources that the registrant has privileges to perform the intended operations upon.
2. The method as recited in claim 1 , wherein the parameter comprises an indication of at least one of an operation that the registrant intends to perform on the resource, a role that the registrant intends to assume if the registrant accesses the resource, a location at which the registrant intends to access the resource, and a subscription plan that the registrant intends to use if the registrant accesses the resource.
3. The method as recited in claim 1 , the method further comprising:
when the one or more resources do not satisfy the discovery request, sending at least one resource to the registrant such that the registrant can obtain permission to access the at least one resource.
4. The method as recited in claim 1 , the method further comprising:
when the one or more resources satisfy the discovery request, sending the one or more resources to the registrant.
5. The method as recited in claim 1 , wherein one of a plurality of permission-based discovery response parameters indicates that the select one of the one or more resources 1) satisfies the permission based filter criteria and 2) cannot be accessed by the registrant due to a lack of permissions.
6. The method as recited in claim 5 , wherein one of the permission-based discovery response parameters indicates an operation that the registrant is permitted to perform on the select one of the one or more resources.
7. The method as recited in claim 5 , wherein one of the permission-based discovery response parameters indicates a role that the registrant is permitted to assume to a select one of the one or more resources.
8. The method as recited in claim 5 , wherein one of the permission-based discovery response parameters indicates a location from which the registrant is permitted to access a select one of the one or more resources.
9. The method as recited in claim 5 , wherein one of the permission-based discovery response parameters indicates a subscription plan that is required in order to access a select one of the one or more resources.
10. The method as recited in claim 1 , wherein the registrant is an application entity or a common services entity.
11. The method as recited in claim 1 , wherein the service layer is a common services entity.
12. The method as recited in claim 1 , wherein the registrant is configured, via a user interface, such that the parameter is specified by a user of the registrant.
13. A network node that hosts a service layer, the network node comprising communication circuitry such that the node is coupled with a network via its communication circuitry, wherein the network node further comprises:
a processor and a memory, the memory containing computer-executable instructions that when executed by the processor, cause the processor to perform operations comprising:
receiving a discovery request, from a registrant, for one or more resources, the discovery request including a parameter that specifies one or more operations that the registrant intends to perform on the discovered resources, wherein the parameter comprises an indication of permission-based filter criteria;
based on the intended operations specified in the discovery request, determining whether one or more resources at the service layer have privileges defined that permit the registrant to perform the intended operations; and
sending a discovery response to the registrant, wherein the discovery response includes a list of identifiers of one or more discovered resources that the registrant has privileges to perform the intended operations upon.
14. The network node as recited in claim 13 , wherein the parameter comprises an indication of an operation that the registrant intends to perform on the resource, a role that the registrant intends to assume if the registrant accesses the resource, a location at which the registrant intends to access the resource, and a subscription plan that the registrant intends to use if the registrant accesses the resource.
15. The network node as recited in claim 13 the operations further comprising:
when the one or more resources do not satisfy the discovery request, sending at least one resource to the registrant such that the registrant can obtain permission to access the at least one resource.
16. The network node as recited in claim 13 , the operations further comprising:
when the one or more resources satisfy the discovery request, sending the one or more resources to the registrant.
17. The network node as recited in claim 13 , wherein one of a plurality of permission-based discovery response parameters indicates that a select one of the one or more resources 1) satisfies the permission-based filter criteria and 2) cannot be accessed by the registrant due to a lack of permissions.
18. The network node as recited in claim 17 , wherein one of the permission-based discovery response parameters indicates an operation that the registrant is permitted to perform on the select one of the one or more resources.
19. The network node as recited in claim 17 , wherein one of the permission-based discovery response parameters indicates a role that the registrant is permitted to assume to the select one of the one or more resources.
20. The network node as recited in claim 17 , wherein one of the permission-based discovery response parameters indicates a location from which the registrant is permitted access the select one of the one or more resources.
21. The network node as recited in claim 17 , wherein one of the permission-based discovery response parameters indicates a subscription plan that is required in order to access the select one of the one or more resources.