Methods and systems for discovering personal internet of things network (PIN) element in a network

Abstract

Embodiments disclose methods for discovering at least one personal Internet of Things (IoT) network (PIN) element. The method includes sending a request to a second entity (104) to discover at least one PIN element Method includes receiving a response from second entity (104), wherein response comprises at least one of: a list of at least one discovered PIN element, at least one identifier of PIN client (106) and at least one PIN client profile for each discovered PIN element; and failure message indicating unsuccessful discovery of PIN element. Embodiments disclose receiving request from first entity to discover PIN element. Method includes authorizing based on identifier of first entity (102) and security credential. Method includes discovering, if there is PIN element, based on parameters provided in request, on successfully authorizing first entity; and sending, response to first entity.

Description

METHODS AND SYSTEMS FOR DISCOVERING PERSONAL INTERNET OF THINGS NETWORK (PIN) ELEMENT IN A NETWORK

[0001] Embodiments disclosed herein relate to wireless communication networks, and more particularly to methods and systems for discovering at least one personal Internet of Things (IoT) network (PIN) element.

[0002] The metaverse is a virtual environment where users are represented by avatars, to navigate a virtual world that maintains strong connections with its physical counterpart. The metaverse is expected to revolutionize the traditional Internet and influence every aspect of our lives. It has promising applications in areas such as virtual education, virtual workplaces, and real estate, among others. However, to fulfill the potential of a massive virtual universe, metaverse applications must address requirements, such as ultra-low latency, high resource demands, interoperability between applications, and security and privacy concerns.

[0003] Further, the current development of the metaverse is primarily focused on centralized data control. Various service providers maintain their exclusive, centralized metaverses, which are accessible only to their respective user bases. Most of the recent metaverse implementations are independent and fragmented, relying on diverse hardware and software technologies. The isolated implementations hinder integration and make it extremely challenging to interconnect the independent metaverse to form a universal metaverse.

[0004] To address the above-mentioned challenges, computational tasks can be distributed across a cloud servers, edge servers, and a personal IoT network (PIN) server. In an example, for each avatar in the metaverse, the user’s edge devices can handle computation tasks related to the avatar’s physical movement, such as momentum, mass, and the physical forces exerted by surrounding entities. Such distributed architecture requires a reliable, independent infrastructure that manages the virtual world, while synchronizing and updating events across all relevant end devices. The cloud servers are dedicated to simulating the virtual universe, the edge servers manage computational tasks for specific regions of the virtual world grid. Finally, PIN elements handle computational tasks near end users in smart home environments.

[0005] To support the edge servers, Third Generation Partnership Project (3GPP) has defined an architecture for enabling edge applications in Technical specification (TS) 23.558. To support PINs, the 3GPP has defined application layer support for personal IoT networks in TS 23.542.

[0006] However, the current application layer support for PINs does not enable a user equipment (UE) to discover nearby elements within the same PIN or across different PINs for offloading computational task(s).

[0007] Hence, there is a need in the art for solutions which will overcome the above-mentioned drawback(s), among others.

[0008] The principal object of the embodiments herein is to disclose methods and systems for a user equipment (UE) / personal Internet of Things (IoT) network (PIN) element to discover a node / PIN element, wherein the other nodes / PIN elements can be used to offload one or more computational tasks.

[0009] Further object of embodiments herein is to discover PIN element, to enable a first entity within a network to discover one or more PIN elements by sending a request to a second entity and receiving a response with information about discovered PIN elements or a failure message.

[0010] Further object of embodiments herein is to receive the response from the second entity based on the request, the response comprises a list of discovered PIN element(s), at least one identifier of the PIN client and at least one PIN client profile for each discovered PIN element.

[0011] Further object of embodiments herein is to receive the response to a failure message indicating an unsuccessful discovery of the PIN element.

[0012] Another object of embodiments herein is to allow the discovery request to include parameters such as a PIN element identifier, a security credential, a location information, service requirements, capability requirements, and a specified time duration for the required service.

[0013] Another object of embodiments herein is to identify PIN client profiles for each discovered PIN element comprises at least one of a capability, and an operational status.

[0014] Another object of embodiments herein is to authorize the first entity by the second entity based on an identifier of the first entity and a security credentials.

[0015] Another object of embodiments herein is to discover if there is at least one PIN element, based on parameters provided in the request on successfully authorizing the first entity.

[0016] The embodiment discloses a method for discovering at least one personal Internet of Things (IoT) network (PIN) element in a network. The method includes sending, by a first entity, a request to a second entity to discover at least one PIN element. The method includes receiving, by the first entity, a response from the second entity based on the request, wherein the response comprises at least one of: a list of at least one discovered PIN element, at least one identifier of the PIN client, a validity duration of the at least one discovered PIN element and at least one PIN client profile for each discovered PIN element; and a failure message indicating an unsuccessful discovery of at least one PIN element.

[0017] The embodiments disclose a method for discovering at least one personal Internet of Things (IoT) network (PIN) element in a network. The method includes receiving, by a second entity, a request from a first entity to discover at least one PIN element; authorizing, by the second entity, the first entity based on an identifier of the first entity and a security credential. The method includes discovering, by the second entity, if there is at least one PIN element, based on parameters provided in the request, on successfully authorizing the first entity. The method includes sending, by the second entity, a response to the first entity, wherein the response comprises at least one of: a list of at least one discovered PIN element, at least one identifier of the PIN client, a validity duration of the at least one discovered PIN element and at least one PIN client profile for each discovered PIN element; and a failure message indicating an unsuccessful discovery of at least one PIN element.

[0018] The embodiments disclose a first entity, comprising: a processor; a memory; and a PINE managing controller, coupled with the processor and the memory. The PINE managing controller sends a request to a second entity to discover at least one PIN element. The PINE managing controller receives a response from the second entity based on the request, wherein the response comprises at least one of: a list of at least one discovered PIN element, at least one identifier of the PIN client, a validity duration of the at least one discovered PIN element and at least one PIN client profile for each discovered PIN element; and a failure message indicating an unsuccessful discovery of at least one PIN element.

[0019] The embodiments disclose a second entity, comprising: a processor; a memory; and a PEMC managing controller, coupled with the processor and the memory. The PEMC managing controller is configured to receive a request from a first entity to discover at least one PIN element. The PEMC managing controller authorizes the first entity based on an identifier of the first entity and a security credential. The PEMC managing controller discovers if there is at least one PIN element, based on parameters provided in the request, on successfully authorizing the first entity. The PEMC managing controller sends a response to the first entity, wherein the response comprises at least one of: a list of at least one discovered PIN element, at least one identifier of the PIN client, a validity duration of the at least one discovered PIN element and at least one PIN client profile for each discovered PIN element; and a failure message indicating an unsuccessful discovery of at least one PIN element.

[0020] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the scope thereof, and the embodiments herein include all such modifications.

[0021] FIG. 1 is an example diagram depicting the communication of a first entity and a second entity for discovering at least one personal Internet of Things (IoT) network (PIN) element in a network, according to embodiments as disclosed herein;

[0022] FIG. 2 is an example diagram depicting the authorization of a PEMC by receiving a PIN management PIN element discovery request from a PINE, according to embodiments as disclosed herein;

[0023] FIG. 3 shows various hardware components of the first entity, according to embodiments as disclosed herein;

[0024] FIG. 4 shows various hardware components of the second entity, according to embodiments as disclosed herein;

[0025] FIG. 5 is a flow chart depicting a method for discovering at least one PIN element in the network, according to embodiments as disclosed herein; and

[0026] FIG. 6 is a flow chart depicting the method for authorizing the first entity and discovering the PIN element in the network, according to embodiments as disclosed herein.

[0027] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0028] For the purposes of interpreting this specification, the definitions (as defined herein) will apply and whenever appropriate the terms used in singular will also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms “comprising”, “having” and “including” are to be construed as open-ended terms unless otherwise noted.

[0029] The words / phrases "exemplary", “example”, “illustration”, “in an instance”, “and the like”, “and so on”, “etc.”, “etcetera”, “e.g.,” , “i.e.,” are merely used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein using the words / phrases "exemplary", “example”, “illustration”, “in an instance”, “and the like”, “and so on”, “etc.”, “etcetera”, “e.g.,”, “i.e.,” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0030] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0031] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts / sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components / modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0032] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the present disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components / elements / steps is for the purposes of this description and should not be construed as sequential ordering / placement / occurrence unless specified otherwise.

[0033] Embodiments herein disclose methods and systems for discovering at least one personal Internet of Things (IoT) network (PIN) element in a network.

[0034] The proposed method allows a user equipment (UE) / PIN element to discover other node / PIN elements, wherein the other node / PIN elements can be used to offload one or more computational tasks.

[0035] The proposed method allows to discover another PIN elements based on discovery filters like required services and required time, etc. The proposed method enables a metaverse capable device to discover nearby device for offloading computational task rather than depending on single device. The proposed method can be used to create universal metaverse by enabling different metaverse services to integrate with each other.

[0036] Referring now to the drawings, and more particularly to FIGs. 1 through 6, where similar reference characters denote corresponding features consistently throughout the figures, there are shown at least one embodiment.

[0037] FIG. 1 is an example diagram depicting the communication of a first entity 102 and a second entity 104 for discovering at least one personal Internet of Things (IoT) network (PIN) element in a wireless communication network 100. As illustrated in FIG. 1, the wireless communication network 100 comprises the first entity 102 and the second entity 104. The first entity 102 communicates with the second entity 104.

[0038] The first entity 102 referred to herein may be an electronic device / user device that is used by the user to connect, interact, and / or control the operations of the plurality of other devices using a 3GPP network. Examples of the first entity 102 may include, but are not limited to, a smartphone, a mobile phone, a video phone, a computer, a tablet personal computer (PC), a laptop, a wearable device, television, a personal digital assistant (PDA), an IoT device, or any other device that may use a 3GPP network or non-3GPP network. ‘First entity’ 102 referred to herein may be interchangeably used with the ‘PIN element’, ‘PIN client’ and ‘Entity 1’.

[0039] The second entity 104 referred to herein may be the electronic device / user device that is used by the user to connect, interact, and / or control the operations of the plurality of other devices using a 3GPP network. Examples of the second entity 104 may include, but are not limited to, a smartphone, a mobile phone, a video phone, a computer, a tablet personal computer (PC), a laptop, a wearable device, television, a personal digital assistant (PDA), an IoT device, or any other device that may use a 3GPP network or non-3GPP network. ‘Second entity’ 104 referred to herein may be interchangeably used with the ‘PEMC’, and ‘Entity 2’.

[0040] As illustrated in FIG. 1, the first entity 102 (Entity-1) acts as the requester and can be the PIN element, the PIN Management Client (PEMC), a PIN Element with Gateway Capability (PEGC), or a PIN server. Essentially, the PIN element represents any authorized entity that seeks to discover other PIN elements. Second entity 104 (Entity-2), serves as the responder and can be the PEMC, a PIN server, or another authorized entity facilitating the discovery.

[0041] As illustrated in FIG. 1, in the first step the first entity 102 sends a discovery request to the second entity 104(S101). The request includes several pieces of critical information, such as the identifier of the first entity 102, the identifier(s) of the PIN element(s) to be discovered, the application identity, the duration for which the PIN element is required, the services and capabilities that first entity 102 requires, and any relevant security credentials or additional parameters necessary for authorization or discovery.

[0042] As illustrated in FIG. 1, in the second step, the second entity 104 processes the request by authorizing the first entity 102 based on the provided identifiers and credentials. Upon successful authorization, the second entity 104 discovers the list of nearby PIN elements by analyzing the parameters specified in the request (the identifier(s) of the PIN element(s) to be discovered, the application identity, the duration for which the PIN element is required, the services and capabilities that first entity 102 requires). The second entity 104 sends a response back to the first entity 102(S102). If the process is successful, the response includes a list of discovered PIN elements along with their identifier of the PIN client, a validity duration and respective PIN client profiles, which detail the capabilities and operational status of each PIN element. In case of failure, the response includes a failure message specifying the reason for the unsuccessful discovery.

[0043] FIG. 2 is an example diagram depicting the authorization of a PEMC 104a by receiving the PIN management PIN element discovery request from the PIN element 102a. As illustrated in FIG. 2, a PIN client 106 of a PIN element 102a sends a discovery request to the PIN Management Client (PEMC) 104a to locate or discover other PIN elements(S201). The request sent by the PINE 102a includes key information such as the identifier of the PIN element 102a making the request, the security credentials of the PIN client 106 obtained during the authorization procedure, and optionally the UE identifier (such as GPSI), the PIN client ID, the UE location, the PIN ID representing the PIN element 102a, the identifier(s) of the PIN element(s) to be discovered, the application identity, the specific services or capabilities required, and the time duration for which the PIN element is needed.

[0044] Upon receiving the request, the PEMC 104a begins the authorization process for the PIN client 106(S202). The authorization process involves verifying the provided parameters and checking against the registered information of PIN elements within the PIN. The registered PIN elements 102a may already be available within the PIN Management Client 104a, for instance, in the PIN dynamic profile, or this information may be fetched from the PIN Server by the PIN Management Client. Upon successful authorization, the PEMC 104a discovers the list of nearby PIN elements by analyzing the parameters specified in the request (the identifier(s) of the PIN element(s) to be discovered, the application identity, the duration for which the PIN element is required, the services and capabilities that PIN client 106 requires).

[0045] After successfully authorizing the PIN client 106 and discovering the requested PIN elements, the PIN Management Client 104a sends a response back to the PIN client 106(S203). If the discovery is successful, the response contains a list of discovered PIN elements along with their identifier of the PIN client 106, a validity duration and respective PIN client profiles, which detail their capabilities and status. In the event of failure, the response includes a failure message specifying the reason for the unsuccessful discovery.

[0046] In another embodiment, the PIN client profiles for each discovered PIN element comprise at least one of PIN element identifier, a service, a capability, an operational status, a location information, and a validity duration for the discovered PIN element.

[0047]

[0048] Table 1 shows the request sent by the PIN client 106 of the PIN element 102a to the PEMC 104a for the PIN element discovery request.

[0049]

[0050] Table 2 shows the response sent by the PEMC 104a to the request for the PIN element discovery response.

[0051] FIG. 3 shows various hardware components of a first entity (102), according to embodiments as disclosed herein. In an embodiment, the first entity (102) comprises a processor (310), a communicator (320), a memory (330), and a PINE managing controller (340). The processor (310) is coupled with the communicator (320), the memory (330), and the PINE managing controller (340).

[0052] The PINE managing controller (340) comprises the processor (310) responsible for executing commands related to the discovery request and response. The memory (330) stores essential data, such as PIN element identifiers, security credentials, and the operational profiles of other PIN elements. The PINE managing controller (340) coordinates the entire discovery process, managing the interaction between the first entity (102) and the second entity (104).

[0053] When a PIN element acts as the first entity (102) in the discovery process, the PINE managing controller (340) generates and sends a discovery request to the second entity (104). The request comprises parameters, may include, but not limited to a PIN element identifier requesting to discover other PINs, a security credential, a first entity identifier, a PIN client identifier, first entity location information, a PIN identifier (ID) as an identifier of the PIN, a service required by the first entity, capability required by the first entity, and a time duration specifying the period for which the first entity requires the service from the PIN element.

[0054] Upon receiving a response from the second entity (104), the processor (310) interprets the response, which may include a list of discovered PIN elements, identifier of the PIN client 106, a validity duration and their associated client profiles. The profiles include the capabilities and operational statuses of the discovered elements, providing actionable information for the requesting PIN element 102a. If the response indicates a failure, the processor 310 analyzes the failure message to determine the cause. The first entity (102) comprises one of: a first PIN element, a PIN Management Client (PEMC), a PIN Element with Gateway Capability (PEGC), and a PIN server, and the second entity comprises one of a PEMC and a PIN server. Hence, the request comprises a PIN management PIN element discovery request, and the response comprises a PIN management PIN element discovery response.

[0055] The PINE managing controller (340) is implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.

[0056] The processor (310) may include one or a plurality of processors. The one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-dedicated processor such as a neural processing unit (NPU). The processor (210) may include multiple cores and is configured to execute the instructions stored in the memory (230).

[0057] Further, the processor (310) is configured to execute instructions stored in the memory (330) and to perform various processes. The communicator (320) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (330) also stores instructions to be executed by the processor (310). The memory (330) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (330) may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted that the memory (330) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0058] Although FIG. 3 shows various hardware components of the first entity (102) but it is to be understood that other embodiments are not limited thereon. In other embodiments, the first entity (102) may include less or more number of components. Further, the labels or names of the components are used only for illustrative purposes and does not limit the scope of the invention. One or more components can be combined together to perform the same or substantially similar function in the first entity (102).

[0059] FIG. 4 shows various hardware components of the second entity (104), according to embodiments as disclosed herein. In an embodiment, the second entity (104) comprises a processor (410), a communicator (420), a memory (430), and a PEMC managing controller (440). The processor (410) is coupled with the communicator (420), the memory (430), and the PEMC managing controller (440).

[0060] The processor (410) is the central computational component responsible for executing commands related to the authorization and discovery of PIN elements. The processor (410) processes incoming requests from the first entity (102), which can be the PIN element, the PEMC 104a, the PEGC, or the PIN server. The requests include parameters such as the PIN element identifier, security credentials, the identifier of the requesting entity, location information, services or capabilities required, and the duration for which the services are needed.

[0061] The memory (420) in the second entity (104) stores data required for managing the discovery process, including information about registered PIN elements, PIN client profiles, and security credentials. The information may either be preloaded in the PIN Management Client (e.g., in a dynamic profile) or fetched from the PIN Server as needed during the discovery process.

[0062] The PEMC managing controller (440) deals with handling the authorization of the first entity 102 by validating the provided PIN element identifier, security credentials, and other identifiers. Upon successful authorization, the controller (440) utilizes the parameters provided in the request to discover PIN elements within the network. Therefore, it involves retrieving information about available PIN elements and assessing their compatibility with the requesting entity's requirements.

[0063] Finally, the second entity (104) sends a response back to the first entity (102). The response includes a list of discovered PIN elements, identifier of the PIN client (106), a validity duration and their associated PIN client profiles if the discovery is successful. These profiles contain details about the capabilities and operational statuses of the discovered elements.

[0064] The PEMC managing controller (440) is implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.

[0065] The processor (410) may include one or a plurality of processors. The one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-dedicated processor such as a neural processing unit (NPU). The processor (410) may include multiple cores and is configured to execute the instructions stored in the memory (430).

[0066] Further, the processor (410) is configured to execute instructions stored in the memory (430) and to perform various processes. The communicator (420) is configured for communicating internally between internal hardware components and with external devices via one or more networks. The memory (430) also stores instructions to be executed by the processor (410). The memory (430) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory (430) may, in some examples, be considered a non-transitory storage medium. The term “non-transitory” may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted that the memory (430) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).

[0067] FIG. 5 is an example diagram S500 depicting the method for discovering at least one PIN element in the network. As illustrated in FIG. 5, in step S502, the first entity 102 may send the request to the second entity 104 to discover at least one PIN element. In step S504, the first entity 102 may receive the response from the second entity 104 based on the request. The response comprises at least one of: a list of at least one discovered PIN element, at least one identifier of the PIN client (106), a validity duration of the at least one discovered PIN element and at least one PIN client profile for each discovered PIN element; and a failure message indicating an unsuccessful discovery of at least one PIN element. The PIN client profiles for each discovered PIN element comprise at least one of PIN element identifier, a service, a capability, an operational status, a location information, and a validity duration for the discovered PIN element.

[0068] FIG. 6 is an example diagram S600 depicting the method for authorizing the first entity and discovering the PIN element in the network. As illustrated in FIG. 6, in step S602, the second entity 104 may receive the request from a first entity 102 to discover at least one PIN element. In step S604, the second entity 104 may authorize the first entity 102 based on an identifier of the first entity 102 and a security credential. In step S606, the second entity 104 may discover if there is at least one PIN element, based on parameters provided in the request, on successfully authorizing the first entity 102. In step S608, the second entity 104, may send a response to the first entity 102, wherein the response comprises at least one of: a list of at least one discovered PIN element, at least one identifier of the PIN client (106), a validity duration of the at least one discovered PIN element and at least one PIN client profile for each discovered PIN element; and a failure message indicating an unsuccessful discovery of at least one PIN element.

[0069] The various actions, acts, blocks, steps, or the like in the flow charts / diagrams (S500-S600) may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.

[0070] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The elements include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

[0071] The embodiments disclosed herein describe a circuit for performing analog calibration for a scalable multi-voltage memory interface driver. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high-speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g., an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g., using a plurality of CPUs.

[0072] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

1.A method for discovering at least one personal Internet of Things (IoT) network (PIN) element in a network (100), comprising:sending, by a first entity (102), a request to a second entity (104) to discover at least one PIN element; andreceiving, by the first entity (102), a response from the second entity (104) based on the request, wherein the response comprises at least one of:a list of at least one discovered PIN element, at least one identifier of a PIN client (106), a validity duration of the discovered at least one PIN element and at least one PIN client profile for each discovered PIN element; anda failure message indicating an unsuccessful discovery of at least one PIN element.2.The method as claimed in claim 1, wherein the request comprises at least one of: a PIN element identifier requesting to discover other PINs, a security credential, a first entity identifier, a PIN client identifier, first entity location information, a PIN identifier (ID) as an identifier of the PIN, a service required by the first entity (102), capability required by the first entity (102), and a time duration specifying the period for which the first entity requires the service from the PIN element.3.The method as claimed in claim 1, wherein the PIN client profiles for each discovered PIN element comprise at least one of: a capability, and an operational status.4.The method as claimed in claim 1, wherein the first entity (102) comprises one of: a first PIN element, a PIN Management Client (PEMC) (104a), a PIN Element with Gateway Capability (PEGC), and a PIN server, and the second entity comprises one of: a PEMC and a PIN server.5.The method as claimed in claim 1, wherein the request comprises a PIN management PIN element discovery request, and the response comprises a PIN management PIN element discovery response.6.A method for discovering at least one personal Internet of Things (IoT) network (PIN) element in a network (100), comprising:receiving, by a second entity (104), a request from a first entity to discover at least one PIN element;authorizing, by the second entity (104), the first entity (102) based on an identifier of the first entity (102) and a security credential;discovering, by the second entity (104), if there is at least one PIN element, based on parameters provided in the request, on successfully authorizing the first entity; andsending, by the second entity (104), a response to the first entity (102), wherein the response comprises at least one of:a list of at least one discovered PIN element, and at least one PIN client profile for each discovered PIN element; anda failure message indicating an unsuccessful discovery of at least one PIN element.7.The method as claimed in claim 6, wherein the request comprises at least one of: a PIN element identifier requesting to discover other PINs, a security credential, a first entity identifier, a PIN client identifier, first entity location information, a PIN identifier (ID) as an identifier of the PIN, a service required by the first entity, capability required by the first entity, and a time duration specifying the period for which the first entity is required.8.The method as claimed in claim 6, wherein the first entity (102) comprises one of: a first PIN element, a PIN Management Client (PEMC) 104a, a PEGC, and a PIN server, and the second entity comprises one of: a PEMC and a PIN server.9.The method as claimed in claim 6, wherein the request comprises a PIN management PIN element discovery request, and the response comprises a PIN management PIN element discovery response.10.The method as claimed in claim 6, wherein the authorization is based on validating at least one of a PIN element identifier, a first entity identifier, and a PIN client identifier in the PIN element discovery request.11.A first entity (102), comprising:a processor (310);a memory (330); anda PINE managing controller (340), coupled with the processor (310) and the memory (330), configured to:send a request to a second entity (104) to discover at least one PIN element; andreceive a response from the second entity (104) based on the request, wherein the response comprises at least one of:a list of at least one discovered PIN element, at least one identifier of a PIN client (106), a validity duration of the discovered at least one PIN element and at least one PIN client profile for each discovered PIN element; anda failure message indicating an unsuccessful discovery of at least one PIN element.12.A second entity (104), comprising:a processor (410);a memory (430); anda PEMC managing controller (440), coupled with the processor (410) and the memory (430), configured to:receive a request from a first entity (102) to discover at least one PIN element;authorize the first entity based on an identifier of the first entity (102) and a security credential;discover if there is at least one PIN element, based on parameters provided in the request, on successfully authorizing the first entity (102); andsend a response to the first entity (102), wherein the response comprises at least one of:a list of at least one discovered PIN element, and at least one PIN client profile for each discovered PIN element; anda failure message indicating an unsuccessful discovery of at least one PIN element.

Images