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 registrant that communicates with a network node hosting a service layer, the method comprising:
transmitting to the network node, by a registrant node, a discovery request for one or more services, wherein the one or more services is a set of software functionalities that are accessed via a supported interface,
the discovery request for the one or more services including a parameter that specifies one or more operations that the registrant intends to perform on discovered services, wherein the parameter comprises an indication of permission-based filter criteria; and
receiving, by the registrant node, a discovery response from the network node based on the parameter,
wherein the discovery response includes a list of identifiers of one or more discovered services that the registrant has privileges to perform the one or more operations upon at the service layer.
2. The method of claim 1 , wherein the parameter comprises an indication of at least one of an operation that the registrant intends to perform on the one or more services, a role that the registrant intends to assume if the registrant accesses the one or more services, a location at which the registrant intends to access the one or more services, and a subscription plan that the registrant intends to use if the registrant accesses the one or more services.
3. The method of claim 1 , the method further comprising:
when the one or more services do not satisfy the discovery request, receiving at least one service from the network node such that the registrant can obtain permission to access the at least one service.
4. The method of claim 1 , the method further comprising:
when the one or more services satisfy the discovery request, receiving the one or more services from the network node.
5. The method of claim 1 , wherein one of a plurality of permission-based discovery response parameters indicates that select one of the one or more services: 1) satisfies permission-based filter criteria and 2) cannot be accessed by the registrant due to a lack of permissions.
6. The method of claim 5 , wherein one of the permission-based discovery response parameters indicates an operation that the registrant is permitted to perform on the selected one of the one or more services.
7. The method of 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 services.
8. The method of claim 1 , wherein the registrant is an application entity or a common services entity.
9. A device for a registrant, the device comprising communication circuitry such that the registrant communicates with a network node with a network via its communication circuitry, wherein the device further comprises:
a processor and a memory, the memory comprising computer-executable instructions that when executed by the processor, cause the processor to perform operations comprising:
transmitting, by a registrant device, a discovery request, to the network node, for one or more services, wherein the one or more services is a set of software functionalities that are accessed via a supported interface, the discovery request for the one or more services including a parameter that specifies one or more operations that the registrant intends to perform on discovered services, wherein the parameter comprises an indication of permission-based filter criteria; and
receiving, by the registrant device, a discovery response from the network node based on the parameter, wherein the discovery response includes a list of identifiers of one or more discovered services that the registrant has privileges to perform the one or more operations upon at a service layer.
10. The device of claim 9 , wherein the registrant is an application entity or a common services entity.
11. The device of claim 9 , wherein the service layer is a common services entity.
12. A method performed by a network node that hosts a service layer and that communicates with a registrant, the method comprising:
receiving, by the network node, a discovery request, from the registrant, for one or more services, wherein the one or more services is a set of software functionalities that are accessed via a supported interface, the discovery request including a parameter that specifies one or more operations that the registrant intends to perform on the discovered services, wherein the parameter comprises an indication of permission-based filter criteria;
based on the intended operations specified in the discovery request, determining, by the network node, whether one or more services at the service layer have privileges defined that permit the registrant to perform the intended operations; and
sending, by the network node, a discovery response to the registrant, wherein the discovery response includes a list of identifiers of one or more discovered services that the registrant has privileges to perform the intended operations upon.
13. The method of claim 12 , wherein the parameter comprises an indication of at least one of an operation that the registrant intends to perform on the one or more services, a role that the registrant intends to assume if the registrant accesses the one or more services, a location at which the registrant intends to access the one or more services, and a subscription plan that the registrant intends to use if the registrant accesses the one or more services.
14. The method of claim 12 , the method further comprising:
when the one or more services do not satisfy the discovery request, sending at least one service to the registrant such that the registrant can obtain permission to access the at least one service.
15. The method of claim 12 , the method further comprising:
when the one or more services satisfy the discovery request, providing the one or more services to the registrant.
16. The method of claim 12 , wherein one of a plurality of permission-based discovery response parameters indicates that the select one of the one or more services 1) satisfies the permission based filter criteria and 2) cannot be accessed by the registrant due to a lack of permissions.
17. The method of claim 16 , 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 services.
18. The method of claim 16 , 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 services.
19. The method of claim 12 , wherein the registrant is an application entity or a common services entity.
20. The method of claim 12 , wherein the service layer is a common services entity.