Service-based incombination of personal IoT networks

Abstract

The present disclosure relates to a 5G, 6G or personal IoT network communication system for supporting a higher data transmission rate. The method of PEMC includes transmitting a first message including information related to an individual Internet of Things network (PIN); receiving a first join request message from a first Internet of Things network element (PINE), the first join request message including information related to a support service of the first PINE; determining whether to add the first PINE to the PIN based on the information related to the support service; and transmitting a first join accept message to the first PINE based on determining that the first PINE has been added to the PIN, the first join accept message comprising at least one identifier (ID) of at least one PINE in the PIN.

Description

Technical Field

[0001] The present disclosure relates to a method and system for joining a personal IoT network element (PINE) into a personal IoT network (PIN) based on a service request. Background Art

[0002] The fifth generation (5G) mobile communication technology defines a wide frequency band, making high transmission rates and new services possible, and can be realized not only in "sub-6Ghz" frequency bands such as 3.5Ghz, but also in "above 6Ghz" frequency bands (including 28Ghz and 39GHz) called millimeter waves. In addition, it has been considered to implement 6G mobile communication technology (called super 5G system) in terahertz frequency bands (such as 95GHz to 3THz bands) in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency that is one-tenth of 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet the performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC) and massive machine type communication (mMTC), standardization on beamforming and massive MIMO is underway to reduce radio wave path loss in millimeter waves and increase radio wave transmission distance, thereby supporting parameter sets for dynamic operation of millimeter wave resources and time slot formats for efficient utilization (for example, operating multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods (such as LDPC (low-density parity check) codes for large-scale data transmission and polarization codes for high-reliability transmission of control information), L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, in view of the services supported by 5G mobile communication technology, discussions on the improvement and performance enhancement of initial 5G mobile communication technology are underway, and there is already physical layer standardization on the following technologies, for example, V2X (Vehicle-to-Everything) for assisting driving decisions by autonomous vehicles based on information about the location and status of the vehicle transmitted by the vehicle and for improving user convenience, NR-U (New Radio Unlicensed) for system operation designed to comply with various regulatory requirements in unlicensed bands, NR UE energy saving, and non-terrestrial network (NTN) for UE-satellite direct communication for providing coverage and positioning in areas where terrestrial network communications are not available.

[0005] In addition, the air interface architecture / protocols for the following technologies are being standardized, such as the Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area extension by supporting wireless backhaul links and access links in an integrated manner, mobility enhancement including conditional switching and DAPS (Dual Active Protocol Stack) switching, and two-step random access (2-step RACH for NR) for simplifying the random access process. The system architecture / services for the following technologies are also being standardized: 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and mobile edge computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, the number of connected devices, which has been growing exponentially, will be connected to the communication network, and it is therefore expected that there will be a need to enhance the functions and performance of the 5G mobile communication systems and the integrated operations of the connected devices. To this end, new research is planned related to the following technologies: Extended Reality (XR) for effectively supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality), etc., as well as 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, virtual world service support, and drone communication.

[0007] In addition, such developments in 5G mobile communication systems will serve as a foundation for developing new waveforms for providing coverage in the terahertz band for 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and large antennas, metamaterial-based lenses and antennas for improving the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum), RIS (reconfigurable smart surface), full-duplex technology for increasing the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for achieving system optimization by utilizing satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at a complexity level that exceeds the limits of UE operating capabilities by utilizing ultra-high-performance communication and computing resources.

[0008] With all the technical activities around the world for various candidate technologies from industry and academia, the momentum for 5th Generation (5G) or New Radio (NR) mobile communications has been increasing recently. Candidate drivers for 5G / NR mobile communications include massive antenna technology from traditional cellular bands to high frequencies to provide beamforming gain and support increased capacity, new waveforms (e.g., new radio access technologies (RATs)) for flexibly adapting to various services / applications with different requirements, new multiple access schemes for supporting large-scale connections, and so on. Summary of the invention

[0009] Technical issues

[0010] In an environment supported by one or more PIN elements with gateway functions (PEGC) and PIN elements with management capabilities (PEMC), there are multiple PINs. A first PINE wants to receive a specific service, such as a printer service, and the service may be supported by another PINE (i.e., a second PINE) that has not yet joined the PIN. The details of how to set up communication between the first PINE and the second PINE so that the first PINE accesses the services of the second PINE are not defined in the existing methods or systems.

[0011] Furthermore, there is no procedure for how a PINE needs to be released from a PIN, which is not defined in existing methods or systems. In other words, there is no procedure in the prior art that defines how a PINE needs to be released from a PIN.

[0012] It would therefore be desirable to address the above-mentioned or other disadvantages or at least provide a useful alternative.

[0013] The technical subject matter pursued in the present disclosure may not be limited to the above-mentioned technical subject matter, and other technical subject matter not mentioned may be clearly understood by those skilled in the art to which the present disclosure relates through the following description.

[0014] Technical Solutions

[0015] The main purpose of the embodiments herein is to provide a method and system for adding a PINE to a PIN based on a service request.

[0016] Another object of embodiments herein is to release a PINE from a PIN.

[0017] Another object of the embodiments herein is to provide a PIN network device (e.g., PEMC, PIN network function (PINNF), PIN application function (PINAF), PEGC, etc.) to announce or broadcast PIN information to available PINEs. When a PINE wants to join a PIN, the PINE sends a PIN join request. The PINE provides a list of services provided by the PINE and a list of services required by the PINE.

[0018] Another object of the embodiments herein is to provide a PIN network device to broadcast or announce a request to find a PINE that provides the requested service. If the PINE receiving the announcement provides the requested service, the PINE sends a PIN join request or any signal to join the PIN and provide the requested service to the requesting PINE.

[0019] Another object of the embodiments herein is to define a mechanism whereby a PINE provides information of required / requested services to a PIN network device, and the PIN network device finds a PINE that can provide the requested service and includes the requested service into the PIN to provide the service to the requesting PINE.

[0020] Therefore, embodiments of the present invention provide a method for adding a PINE to a PIN based on services. The method includes broadcasting PIN information to a plurality of PINEs by a PIN network device. In addition, the method includes receiving a first message by the PIN network device to add a first PINE from a plurality of PINEs to the PIN based on the PIN information. The first message includes the security credentials of the first PINE, the services provided by the first PINE, and the services requested by the first PINE in the PIN. In addition, the method includes determining, by the PIN network device, a second PINE from a plurality of PINEs that supports the services requested by the first PINE in the PIN. In addition, the method includes adding the first PINE to the PIN based on the security credentials and PIN information of the first PINE by the PIN network device. In addition, the method includes sending a second message by the PIN network device to the first PINE, thereby indicating that the first PINE is added to the PIN. The second message includes a PIN identifier of the second PINE that supports the services requested by the first PINE in the PIN.

[0021] In one embodiment, determining, by a PIN network device, a second PINE that supports a service requested by a first PINE in a PIN includes: detecting, by a network device, that the second PINE that supports the service requested by the first PINE has not joined the PIN; sending, by the PIN network device, a service request message to a plurality of PINEs to detect the second PINE that supports the service requested by the first PINE in the PIN; receiving, by the PIN network device, a first message from the second PINE to join the PIN. The first message includes security credentials of the second PINE, services provided by the second PINE, adding the second PINE to the PIN by the PIN network device based on security information and PIN information of the second PINE, and sending, by the PIN network device, a second message to the second PINE to indicate that the second PINE is to be joined to the PIN that supports the service requested by the first PINE in the PIN.

[0022] In one embodiment, the method includes starting a timer by a network device after sending a service request message to a plurality of PINEs to detect a second PINE that supports a service requested by a first PINE in a PIN. The timer includes a timer window within which the network device expects a join request from a second PINE in the plurality of PINEs. In addition, the method includes determining by the network device whether a join request is received from the second PINE before expiration of the timer. In one embodiment, the method includes adding the second PINE to the PIN by the PIN network device when a join request is received from the second PINE before expiration of the timer. In another embodiment, the method includes sending a PIN reject request message to the first PINE when a join request is not received from the second PINE before expiration of the timer, thereby indicating that the service is not available in the PIN.

[0023] In one embodiment, adding the second PINE to the PIN by the PIN network device based on the security credentials and PIN information of the second PINE includes verifying the second PINE by the PIN network device based on the security credentials and PIN information of the second PINE, and after successfully verifying the second PINE, adding the second PINE to the PIN by the PIN network device.

[0024] In one embodiment, the PIN information includes supported services or device types indicating specific services supported by the PINE available in the PIN, requested services or device types indicating the requested services that the PINE can support, a group ID or PIN identifier, a time window in which the network device expects a join request from a PINE in multiple PINEs, and a user-defined name indicating in which PIN the PINE is to be added.

[0025] In one embodiment, adding the first PIN to the PIN based on the security credentials and PIN information of the first PINE by the PIN network device includes verifying the first PINE based on the security credentials and PIN information of the first PINE by the PIN network device, and upon successful verification of the first PINE, adding the first PIN to the PIN by the PIN network device.

[0026] Therefore, embodiments of the present invention provide a method for adding a PINE to a PIN based on services. The method includes receiving, by a first PINE from a plurality of PINEs, PIN information broadcasted by a PIN network device. In addition, the method includes determining, by the first PINE, whether to send a first message to the PIN network device based on a local configuration and at least one of the PIN information received from the PIN network device. In addition, the method includes sending, by the first PINE, a first message to join the PIN based on the PIN information. The first message includes security credentials for verifying the first PINE, services provided by the first PINE, and services requested by the first PINE in the PIN. In addition, the method includes receiving, by the first PINE, a second message from the PIN network device, indicating that the first PINE is added to the PIN. The second message includes a PIN identifier of a second PINE that supports the service requested by the first PINE in the PIN. In addition, the method includes performing PIN-PIN communication with the second PINE based on the PIN identifier of the second PINE by the first PINE. In addition, the method includes receiving, by the first PINE, services from the second PIN.

[0027] Therefore, embodiments of the present invention provide a method for adding a PINE to a PIN based on services. The method includes receiving, by a second PINE from a plurality of PINEs, PIN information broadcast by a PIN network device. In addition, the method includes receiving, by a second PINE from a plurality of PINEs, a service request message to support a service requested by a first PINE from a PIN network device. In addition, the method includes determining, by a second PINE, whether to send a first message to a network device based on at least one local configuration and PIN information received from a PIN network device. In addition, the method includes sending, by a second PINE, a first message to join a PIN based on the PIN information and the service request message. The first message includes a security credential for verifying the second PINE, a service provided by the second PINE, and a service requested by the second PINE in the PIN. In addition, the method includes receiving, by a second PINE, a second message from a network device, indicating that the second PINE is added to a PIN supporting a service requested by the first PINE in the PIN. In addition, the method includes receiving, by a second PINE, a PIN-PIN communication including a PIN identifier of the second PINE from the first PINE. In addition, the method includes sending, by a second PINE, a service from a second PIN.

[0028] Therefore, embodiments of the present invention provide a PIN network device for adding a PINE to a PIN based on a service. The PIN network device includes a service-based PINE controller connected to a memory and a processor. The service-based PINE controller broadcasts PIN information to multiple PINEs. In addition, the service-based PINE controller receives a first message from a first PINE among the multiple PINEs to join the PIN based on the PIN information. The first message includes a security credential of the first PINE, a service provided by the first PINE, and a service requested by the first PINE in the PIN. In addition, the service-based PINE controller determines a second PINE from the multiple PINEs that supports the service requested by the first PINE in the PIN. In addition, the service-based PINE controller adds the first PINE to the PIN based on the security credential and the PIN information of the first PINE. In addition, the service-based PINE controller sends a second message to the first PINE, thereby indicating that the first PINE is added to the PIN. The second message includes a PIN identifier of the second PINE that supports the service requested by the first PINE in the PIN.

[0029] Therefore, embodiments of the present invention provide a method for joining a first PINE in a PIN based on a service. The first PINE includes a service-based PINE controller connected to a memory and a processor. The service-based PINE controller receives PIN information broadcast by a network device. In addition, the service-based PINE controller determines whether to send a first message to the network device based on a local configuration and at least one of the PIN information received from the network device. In addition, the service-based PINE controller sends a first message based on the PIN information to join the PIN. The first message includes security credentials for verifying the first PINE, services provided by the first PINE, and services requested by the first PINE in the PIN. In addition, the service-based PINE controller receives a second message from the network device, thereby indicating that the first PINE is to be added to the PIN. The second message includes a PIN identifier of a second PINE that supports the service requested by the first PINE in the PIN. In addition, the service-based PINE controller performs PIN-PIN communication with the second PINE based on the PIN identifier of the second PINE. In addition, the service-based PINE controller receives services from the second PIN.

[0030] Therefore, embodiments of the present invention provide for joining a second PINE in a PIN based on services. The second PINE includes a service-based PINE controller connected to a memory and a processor. The service-based PINE controller receives PIN information broadcast by a network device. In addition, the service-based PINE controller receives a service request message to support a service requested by a first PINE from the network device. In addition, the service-based PINE controller determines whether to send a first message to the network device based on at least one local configuration and the PIN information received from the network device. In addition, the service-based PINE controller sends a first message to join the PIN based on the PIN information and the service request message. The first message includes a security credential for verifying the second PINE, a service provided by the second PINE, and a service requested by the second PINE in the PIN. In addition, the service-based PINE controller receives a second message from the network device, thereby indicating that the second PINE is joined to the PIN supporting the service requested by the first PINE in the PIN. In addition, the service-based PINE controller receives a PIN-PIN communication including a PIN identifier of the second PINE from the first PINE. In addition, the service-based PINE controller sends a service from the second PIN.

[0031] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and accompanying drawings. However, it should be understood that the following description is given as an illustration and not as a limitation, although preferred embodiments and many of their specific details are indicated. Many changes and modifications may be made within the scope of the embodiments herein, and the embodiments herein include all such modifications.

[0032] Beneficial Effects

[0033] The present disclosure provides an effective and efficient method for adding PINE to a personal IOT network. The advantageous effects that can be obtained from the present disclosure may not be limited to the above effects, and other effects not mentioned can be clearly understood by those skilled in the art to which the present disclosure relates through the following description.

[0034] It may be helpful to set forth definitions of certain words and phrases used throughout this patent document: the term "including" and its derivatives mean including, but not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean including, included within, interconnected with, including, included within, connected to or connected with, coupled to or coupled with, capable of communicating with, cooperating with, interleaved, juxtaposed, proximate to, bound to or bound with, having, having the property of, and the like; and the term "controller" means any device, system, or portion thereof that controls at least one operation, which device may be implemented in hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0035] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a part thereof suitable for implementation with a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disc (CD), a digital video disc (DVD) or any other type of memory. "Non-transitory" computer-readable media excludes wired, wireless, optical or other communication links that transmit instantaneous electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data, and media that can store data and then rewrite data, such as rewritable optical discs or erasable memory devices.

[0036] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The present disclosure is illustrated in the accompanying drawings, in which the same reference letters indicate corresponding parts in the various figures. The embodiments of the present invention will be better understood from the following description with reference to the accompanying drawings, in which:

[0038] Figure 1 A method of establishing communication between a PINE and a PIN based on service requirements according to an embodiment as disclosed herein is shown;

[0039] Figure 2 shows a release / delete operation initiated by a PINE according to an embodiment as disclosed herein;

[0040] Figure 3 shows a PINE release / deletion initiated by PEMC / PEGC / PINNF / PINAF according to an embodiment as disclosed herein;

[0041] Figure 4 A PIN network device according to an embodiment as disclosed herein is shown;

[0042] Figure 5 shows a PINE according to an embodiment as disclosed herein;

[0043] Figure 6 A flow chart showing a method implemented by a PIN network device for adding a PINE to a PIN based on service according to an embodiment as disclosed herein;

[0044] Figure 7 A flow chart showing a method implemented by a first PINE for adding a PINE to a PIN on a service-based basis according to an embodiment as disclosed herein; and

[0045] Figure 8 A flow chart of a method implemented by a second PINE for service-based joining of a PINE to a PIN according to an embodiment as disclosed herein is shown.

[0046] It may be noted that, to the extent possible, the same reference numerals have been used to represent the same elements in the figures. In addition, it will be appreciated by those of ordinary skill in the art that the elements in the figures are shown for simplicity and may not necessarily be drawn to scale. For example, the dimensions of some elements in the figures may be exaggerated relative to other elements to help improve understanding of aspects of the present disclosure. In addition, one or more elements may have been represented in the figures by conventional symbols, and the drawings may only show specific details relevant to understanding the embodiments of the present disclosure, so as not to obscure the drawings with details that would be apparent to those of ordinary skill in the art having the benefit of this specification. DETAILED DESCRIPTION

[0047] The following patent document discusses Figures 1 to 8 The various embodiments used to describe the principles of the present disclosure are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. It will be understood by those skilled in the art that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0048] The embodiments of the present invention and their various features and advantageous details are more fully described with reference to the non-limiting embodiments shown in the accompanying drawings and described in detail in the following description. The description of well-known components and processing techniques is omitted so as not to unnecessarily obscure the embodiments of the present invention. In addition, the various embodiments described herein are not necessarily mutually exclusive, because some embodiments can be combined with one or more other embodiments to form new embodiments. The term "or" used herein refers to non-exclusive, or unless otherwise specified. The examples used herein are only for the convenience of understanding the way in which the embodiments of the present invention can be practiced, and further enable those skilled in the art to practice the embodiments of the present invention. Therefore, these examples should not be interpreted as limiting the scope of the embodiments of the present invention.

[0049] As conventional in the art, each embodiment can be described and illustrated according to a block that performs one or more functions described. These blocks, which may be referred to herein as managers, units, modules, hardware components, etc., 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, hard-wired circuits, etc.), and may optionally be driven by firmware. For example, the circuit may be embodied in one or more semiconductor chips, or embodied on a substrate support such as a printed circuit board. The circuits constituting the blocks may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuits), or by a combination of dedicated hardware for executing some functions of the blocks and processors and processors for executing other functions of the blocks. Without departing from the scope of the present disclosure, each block of the embodiment may be physically divided into two or more interactive and discrete blocks. Similarly, without departing from the scope of the present disclosure, the blocks of the embodiment may be physically combined into more complex blocks.

[0050] 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. Therefore, the present disclosure should be interpreted as extending to any changes, equivalents and substitutes other than those specifically listed in the accompanying drawings. Although the terms "first", "second" etc. can be used to describe various elements in this article, these elements should not be limited by these terms. These terms are usually only used to distinguish one element from another element.

[0051] Expansions of abbreviations used in patent disclosures are as follows:

[0052] a)3GPP Third Generation Participation Plan;

[0053] b)5GC 5G core network;

[0054] c) D2D device to device;

[0055] d) FQDN fully qualified domain name;

[0056] e) PEGC PIN has gateway functional elements;

[0057] f) Elements of PEMC PIN with management capabilities;

[0058] g) PIN personal IoT network;

[0059] h) PIN-E PIN element;

[0060] i) ProSe short-range service;

[0061] j) QoS quality of service; and / or

[0062] k)UE user equipment.

[0063] The expansions and definitions of abbreviations used in the patent disclosure are as follows:

[0064] a) PIN (Personal IoT Network): A Personal IoT Network (PIN) provides local connectivity between UEs and / or non-3GPP devices. A Personal IoT Network (PIN) consists of PIN elements (PINEs) that communicate using PIN direct connections or direct network connections and are managed locally (using PIN elements with management capabilities);

[0065] b) PINE (PIN Element): A PIN element is a UE and / or non-3GPP device that forms part of the PIN;

[0066] c) PEMC (PIN Element with Management Capabilities): a PIN element with the capability to provide a means for authorized administrators to configure and manage PINs;

[0067] d) PEGC (PIN element with gateway function): PIN element with gateway function provides a means for PIN elements to register and access 5G network services. PEGC can also help communicate between two PIN elements that are not in range using direct communication;

[0068] e) ProSe: ProSe (Proximity Service) is a D2D (Device to Device) technology that allows LTE devices to detect each other and communicate directly;

[0069] f) PIN-ID: a unique identifier associated with the PIN;

[0070] g) PINNF (PIN Network Function): The PIN Network Function is the 5GC NF responsible for creating and managing PINs; and / or

[0071] h) PINAF (PIN Application Function): PIN Application Function is a network function connected to the 5G core network via NEF (Network Exposure Function). PINAF is responsible for the policy configuration and provisioning of PIN and its elements in 5GC and PEGC / PEMC / PINE.

[0072] Information (or PIN information) in this disclosure is defined by at least one of the following:

[0073] a) Service type (IoT, hospital IoT equipment);

[0074] b) Type of device (e.g. printer, thermostat);

[0075] c) characteristics;

[0076] d) Group ID (the type of PIN-ID it wants to join);

[0077] e) functionality (e.g. printer, etc.); and / or

[0078] f) A normal string configured by the user or 5GC in PEMC or PEGC. When PINE sends this normal string, PEMC or PEGC will identify which PIN PINE can add. The normal string can be any configurable text, for example, the normal string can be an ID or PIN_NAME or PIN_DISCOVERY name, a user-readable format, etc.

[0079] "Service Type" can be one or any combination of the following, and it should be noted that this is not an exhaustive list:

[0080] a) eMBB: enhanced mobile broadband;

[0081] b) URLLC: Ultra-Reliable Low Latency Communication;

[0082] c) MIoT: Massive IoT or IOT;

[0083] d) V2X services; and / or

[0084] e) High performance machine type communication.

[0085] The type of device is for devices such as printers, thermostats, and can support the above "service types". The characteristics of the device that can handle the above "service types". The group ID is a kind of PIN-ID that it wants to join. Capabilities (such as printers, etc.) or capabilities of devices that can support the above "service types" or "device types".

[0086] Therefore, embodiments of the present invention provide a method for adding a PINE to a PIN based on services. The method includes broadcasting PIN information to a plurality of PINEs by a PIN network device. In addition, the method includes receiving a first message by the PIN network device to add a first PINE from a plurality of PINEs to the PIN based on the PIN information. The first message includes the security credentials of the first PINE, the services provided by the first PINE, and the services requested by the first PINE in the PIN. In addition, the method includes determining, by the PIN network device, a second PINE from a plurality of PINEs that supports the services requested by the first PINE in the PIN. In addition, the method includes adding the first PINE to the PIN based on the security credentials and PIN information of the first PINE by the PIN network device. In addition, the method includes sending a second message by the PIN network device to the first PINE, thereby indicating that the first PINE is added to the PIN. The second message includes a PIN identifier of the second PINE that supports the services requested by the first PINE in the PIN.

[0087] The method can be used to join a PINE to a PIN based on a service request. In an example, a first PINE requests to join a PIN that provides a specific service "s", and the entity responsible for creating or managing the PIN can broadcast or search for a second PINE that can provide the specific service "s". If the target second PINE joins the PIN, the first PINE will be informed of the details of the second PINE after including the information in the same PIN. Later, the first PINE can communicate with the second PINE and receive the required service.

[0088] This method can be used to release a PINE from a Personal IoT Network (PIN).

[0089] In one embodiment, PINE can request PEMC / PINNF / PINAF through PEGC or directly connect to 5GC to release / delete itself from PIN. In another embodiment, PEMC / PEGC / PINNF / PINAF can request to release / delete PINE from PIN.

[0090] Now referring to the drawings, more particularly Figures 1 to 8 , in which a preferred embodiment is shown.

[0091] Figure 1A method of establishing communication between a PINE (100) and a PIN (1000) based on service requirements according to an embodiment as disclosed herein is shown. In one embodiment, information (or PIN information) is defined by at least one of a service type (e.g., IOT, hospital IOT device), a device type (e.g., printer, thermostat, etc.), a characteristic, a group ID (the type of PIN-ID it wants to join), and a function (functions such as printers). A normal string configured by a user (user readable format) or a 5GC in a PEMC (200A) or PEGC (200B), when a PINE (100) sends the normal string, the PEMC (200A) or PEGC (200B) identifies which PIN (1000) the PINE (100) can add. The normal string can be any configurable text, for example, the normal string can be an ID or a PIN_NAME or a PIN_DISCOVERY name, etc.

[0092] At step 1, PEMC (200A) and PEGC (200B) are part of a plurality of PINs. PEMC (200A) (or any other entity responsible for managing PINs) maintains a list of available PINs, each of which has available services. PEMC (200A) is used as an example only in this embodiment, and it can be any entity that manages PIN (1000), such as PEMC (200A) / PEGC (200B) / PINNF (300) / PINAF (400) / user) maintains a list of available PINs based on any information (also referred to as PIN information in the embodiment).

[0093] At step 2, the first PINE (100a) wants to receive a specific service "S", such as a printer. At step 3, the first PINE (100a) requests the PEGC (200B) / PEMC (200A) to join the PIN (1000) that can provide the specific service "S" (based on at least one PIN information (i.e., type of device / characteristics / type of service, etc.)), or the first PINE (100a) is already part of the PIN (1000) but the first PINE (100a) requests the target PINE details that can provide the specific service "S", or the first PINE (100a) only indicates that the first PINE (100a) wants to receive the service "S".

[0094] At step 4, the PEMC (200A) / PINMF identifies that the PINE (100) (or any PINE) providing the service "S" has not yet joined any PIN or PIN (1000) to which the PINE (100) currently belongs. At step 5, the PEMC (200A) / PINMF / PINNF (300) / PEGC (200B) / PINAF (400) / user announces a request to join the PINE (100) supporting the service "S". When the PEMC (200A) / PINMF / PINNF (300) / PEGC (200B) / PINAF (400) broadcasts or announces the request, all PINEs (100) are able to receive the following information: the PEMC (200A) / PEGC (200B) is looking for a PINE (100) that can support the service "S" and this is a request for the corresponding PINE (100) to join the PIN.

[0095] The PEMC (200A) / PINMF / PINNF (300) / PEGC (200B) / PINAF (400) / user starts a timer, waiting for a trigger from the PINE (100) to join the PIN (1000) supporting service "S". If the timer expires, the PEMC (200A) / PINMF / PINNF (300) / PEGC (200B) / PINAF (400) / user indicates a rejection message to the first PINE and indicates that the requested service is not provided. At step 6, the second PINE (100b) supporting service "S" sends a signal (e.g., a join request) to the PEMC (200A) / PEGC (200B) / PINNF (300) / PEGC (200B) / PINAF (400) / user to join the PIN (1000), or if the second PINE (100b) is already part of the PIN (1000), indicates that it can provide the required service "S".

[0096] At step 7, PEGC (200B) / PEMC (200A) / PINNF (300) / PEGC (200B) / PINAF (400) / user includes the second PINE (100b) to the first PIN. At step 8, PEGC (200B) / PEMC (200A) includes the first PINE (100a) to the first PIN. PEGC (200B) / PEMC (200A) also provides the second PINE information, such as FQDN / IP address or any other identifier used during communication, to the first PINE, and identifies the second PINE (100b). At step 9, the first PINE (100a) may perform PIN-PIN communication via 5GC, PEGC (200B) or direct communication, and receive the desired service "S" provided by the second PINE (100b).

[0097] In one embodiment, the first PINE (100a) indicates the requested service, as one service is only for illustration. The service may be one or more services. In one embodiment, the PEMC (200A) is only a representative entity, and the PEMC (200A) may be any entity part of the PIN (1000), or any entity part in the 5GC, or any entity part in the application layer, such as PINNF (300) / PEGC (200B) / PINAF (400) / user (also known as upper layer). The PEMC (200A) may be a single entity or network function, or the PEMC (200A) may be multiple network functions / entities interacting with each other.

[0098] In one embodiment, when the PEMC (200A) or any other entity announces the need for a particular service, the PEMC (200A) or any other entity may also provide detailed information about the first PINE (100a) that wants to receive the service based on the discoverability criteria of the target PINE (i.e., the second PINE (100b) in this embodiment), and the second PINE (100b) may decide whether to join the PIN (1000) and provide the service to the first PINE (100a). If the second PINE (100b) decides that the second PINE (100b) cannot provide the service to the first PINE (100a), the second PINE (100b) may indicate this to the PEMC (200A) or not respond to the PEMC (200A) announcement request.

[0099] Figure 2 A release / delete operation initiated by a PINE (100) is shown according to embodiments as disclosed herein.

[0100] PINE (100) can request PEMC (200A) / PINNF (300) / PINAF (400) through PEGC (200B) or directly connect to 5GC to release / delete itself from PIN (1000). PINE (100) can request to be released / deleted from PIN (1000) based on one of the following conditions (but not limited to):

[0101] 1) When the validity period has expired or is about to expire

[0102] I.5GC / PEMC(200A) / PINNF(300) / PINAF(400) can allocate a valid timer for PINE(100).

[0103] II. When PINE (100) registers / joins PIN (1000), or based on instructions from PEMC (200A) / PEGC (200B) / PINNF (300) / PINAF (400) / user, PINE (100) may start the PINE validity timer.

[0104] III. After the validity timer expires, the PINE (100) can request to be released / deleted from the PIN (1000).

[0105] 2) When the user has indicated to remove the PIN (1000), for example on the user interface of the PINE (100).

[0106] I. The PINE (100) may have a user interface, and the user may use the user interface to initiate the release / deletion of the PINE (100) from the PIN (1000).

[0107] 3) If PINE(100) is about to reach the maximum possible PIN.

[0108] I.5GC / PEMC(200A) / PINNF(300) / PINAF(400) / User can assign a maximum PIN value for PINE(100).

[0109] II. When the PINE (100) has joined the maximum possible PIN, and if the UE decides to join a new PIN, the PINE (100) can request to be released from any existing PIN (1000).

[0110] III. In addition, upon receiving a release request from the PINE (100), the PEMC (200A) / PINNF (300) / 5GC / PINAF (400) may trigger a PIN release based on policy considerations, such as operator policy, priority of PINs, priority of PINEs (100) within each PIN (1000), etc.

[0111] 4) After performing the required services

[0112] I. A PINE (100) can be dynamically added to a PIN (1000) based on the services required. Thus, after completing a particular service, the PINE (100) can request to be released / deleted from the PIN (1000).

[0113] 5) Based on operator policies or subscriptions pushed into PINE (100).

[0114] I. The PINE (100) can release / delete the PIN (1000) based on operator policy or subscription request, ie for example the subscription has expired, which can be based on data consumption or time validity of the subscription.

[0115] 6) When the PINE (100) moves out of this position, the PINE (100) is expected to operate and receive PIN services.

[0116] I. If the PINE (100) detects that the PINE (100) is moving out of the location (using any location estimation technology, such as geolocation tracking, explicit messages from PEMC (200A) / PEGC (200B) / PINNF (300) / 5GC), the PINE (100) can trigger a release request for the PIN (1000).

[0117] II. In addition, if the PINE (100) exceeds the PIN location area, the PINE (100) can also implicitly release itself from the PIN (1000).

[0118] The following various embodiments disclose PINE release / deletion initiated by PEMC (200A) / PEGC (200B) / PIN-NF (300) / PINAF (400).

[0119] Figure 3 A PINE release / deletion operation initiated by PEMC (200A) / PEGC (200B) / PIN-NF (300) / PINAF (400) is shown according to embodiments as disclosed herein.

[0120] The PEMC (200A) / PEGC (200B) / PINNF (300) / PINAF (400) may request to release / delete the PINE (100) from the PIN (1000) based on at least one of the following conditions (but not limited to):

[0121] 1) When the validity period has expired or is about to expire

[0122] I.5GC / PEMC(200A) / PINNF(300) / PINAF(400) can allocate a valid timer for PINE(100).

[0123] II. When PINE (100) registers / joins PIN (1000), or based on instructions from PEMC (200A) / PEGC (200B) / PINNF (300) / PINAF (400) / user, PINE (100) may start the PINE validity timer.

[0124] III. After the validity timer expires, the PINE (100) can request to be released / deleted from the PIN (1000).

[0125] 2) When the user has instructed to release the PINE (100) from the PEMC (200A) / PEGC (200B) / or from the user interface of the PINAF (400).

[0126] The PINE (100) may have a user interface, and the user may initiate release / deletion of the PINE (100) from the PIN (1000) using the user interface or from the user interface of the PEMC (200A) / PEGC (200B) / PINNF (300) / PINAF (400).

[0127] 1) If PINE(100) is about to be added to the maximum possible PIN.

[0128] I.5GC / PEMC(200A) / PINNF(300) / PINAF(400) / User can assign a maximum PIN value to PINE.

[0129] II. When a PINE (100) has joined the maximum possible PINs, the PEMC (200A) / PEGC (200B) / PIN-NF (300) / PINAF (400) may request to be released from any existing PIN (1000). The PEMC (200A) / PINNF (300) / 5GC / PINAF (400) may trigger the PIN (1000) release based on policy considerations such as operator policy, priority of PINs, priority of PINE (100) within each PIN.

[0130] 2) After performing the required service

[0131] I. PINE (100) can be dynamically added to PIN (1000) based on the required services. Therefore, after completing a specific service, PEMC (200A) / PEGC (200B) / PIN-NF (300) / PINAF (400) can request to be released / deleted from PIN (1000).

[0132] 3) Based on operator policies or subscriptions pushed into PINE.

[0133] The PEMC (200A) / PEGC (200B) / PIN-NF (300) / PINAF (400) may release / delete the PIN (1000) based on operator policy or subscription request, ie, for example, the subscription has expired, which may be based on the amount of data consumed or the time validity of the subscription.

[0134] 4) Based on the determination by PEMC (200A) / PEGC (200B) / PINNF (300) / PINAF (400), a maximum number of PINEs have been added to PIN (1000).

[0135] I. Depending on subscription or operator policy, a PIN (1000) can have a maximum number of PINE standards.

[0136] II. During PIN creation or PIN management, the maximum number of PINEs that can be added to the PIN (1000) can be updated in the PIN entity (PEMC (200A) / PEGC (200B) / PINAF (400) / PINNF (300)).

[0137] III. Once PIN (1000) has the maximum number of PINEs, PEMC (200A) / PEGC (200B) / 5GC / PINAF (400) can release a PINE from PIN (1000).

[0138] When the PINE (100) moves out of the location, the PINE (100) is expected to operate and receive PIN services. If the PEMC (200A) / PEGC (200B) / PINNF (300) / 5GC / PINAF (400) detects that the PINE (100) has moved out of the location (using any location estimation technology, such as geolocation tracking or location-based services defined in 3GPP, etc.), the PEMC (200A) / PEGC (200B) / PINNF (300) / 5GC / PINAF (400) may initiate the release of the corresponding PINE (100) from the PIN procedure.

[0139] If PEMC (200A) / PEGC (200B) / PINNF (300) / 5GC / PINAF (400) detects that the service provided by PINE (100) is prohibited or restricted by at least one of 5GC / PINAF (400) / PINNF (300) / PEGC (200B) / PEMC (200A), at least one of them initiates a PINE release procedure to release PINE (100) from PIN (1000).

[0140] If PEMC (200A) / PEGC (200B) / PINNF (300) / 5GC / PINAF (400) detects that PIN (1000) is prohibited or restricted by at least one of 5GC / PINAF (400) / PINNF (300) / PEGC (200B) / PEMC (200A), at least one of them initiates a PINE release procedure to release all PINEs from PIN (1000). That is, PEMC (200A) / PEGC (200B) / PINNF (300) / 5GC / PINAF (400) can trigger the PIN release procedure.

[0141] Release / delete / remove are terms used in this embodiment to indicate a process for removing PINE (100) from PIN (1000), i.e., after executing the procedure, PINE (100) may no longer be a part of PIN (1000).

[0142] Figure 4 A PIN network device (200) according to an embodiment as disclosed herein is shown. The PIN network device (200) may be, for example, but not limited to, a PEMC (200A), a PINMF, a PINNF (300), a PEGC (200B), and a PINAF (400). In one embodiment, the PIN network device (200) includes a processor (210), a communicator (220), a memory (230), and a service-based PINE controller (240). The processor (210) is connected to the communicator (220), the memory (230), and the service-based PINE controller (240).

[0143] The service-based PINE controller (240) broadcasts PIN information to the plurality of PINEs. The PIN information includes: supported services or device types indicating a particular service supported by the PINE (100) available in the PIN (1000), requested services or device types indicating at least one requested service that the PINE (100) can support, a group ID or PIN identifier, a time window during which the network device (200) expects a join request from the PINE (100) in the plurality of PINEs, and a user-defined name indicating the PINE (100) is to be added to the PIN (1000).

[0144] In addition, the service-based PINE controller (240) receives a first message to join the PIN (1000) from a first PINE (100a) of the plurality of PINEs based on the PIN information. The first message includes security credentials of the first PINE (100a), services provided by the first PINE (100a), and services requested by the first PINE (100a) of the PIN (1000). In addition, the service-based PINE controller (240) determines a second PINE (100b) from the plurality of PINEs that supports the service requested by the first PINE (100a) of the PIN (1000).

[0145] In one embodiment, a service-based PINE controller (240) detects that a second PINE (100b) supporting a service requested by a first PINE (100a) is not added to a PIN (1000). In addition, the service-based PINE controller (240) sends a service request message to a plurality of PINEs to detect a second PINE (100b) supporting a service requested by a first PINE (100a) in a PIN (1000). In addition, the service-based PINE controller (240) receives a first message from the second PINE (100b) to join the PIN (1000). The first message includes a security credential of the second PINE (100b), a service provided by the second PINE (100b). In addition, the service-based PINE controller (240) adds the second PINE (100b) to the PIN (1000) based on security information and PIN information of the second PINE (100b) by verifying the second PINE (100b) based on the security credential and PIN information of the second PINE (100b). In addition, the service-based PINE controller (240) sends a second message to the second PINE (100b), thereby instructing the second PINE (100b) to be added to the PIN (1000) supporting the service requested by the first PINE (100a) in the PIN (1000).

[0146] In addition, the service-based PINE controller (240) starts a timer after sending a service request message to the plurality of PINEs to detect a second PINE (100b) that supports the service requested by the first PINE (100a) in the PIN (1000). The timer includes a timer window within which the network device (200) expects a join request from at least one second PINE (100b) in the plurality of PINEs. In addition, the service-based PINE controller (240) determines whether a join request is received from the second PINE (100b) before the timer expires. In one embodiment, when a join request is received from the second PINE (100b) before the timer expires, the service-based PINE controller (240) adds the second PINE (100b) to the PIN (1000). In another embodiment, when a join request is not received from the second PINE (100b) before the timer expires, the service-based PINE controller (240) sends a PIN reject request message to the first PINE (100a), thereby indicating that no service is available in the PIN.

[0147] In addition, the service-based PINE controller (240) adds the first PINE (100a) to the PIN (1000) based on the security credentials and PIN information of the first PINE (100a) by verifying the first PINE (100a) based on the security credentials and PIN information of the first PINE (100a). In addition, the service-based PINE controller (240) sends a second message to the first PINE (100a) to indicate that the first PINE (100a) is added to the PIN (1000). The second message includes a PIN identifier of a second PINE (100b) that supports the service requested by the first PINE (100a) in the PIN (1000).

[0148] The service-based PINE controller (240) 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, hard-wired circuits, etc., and can optionally be driven by firmware.

[0149] In addition, the processor (210) is configured to execute instructions stored in the memory (230) and perform various processes. The communicator (220) is configured to communicate internally between internal hardware components and communicate with external devices via one or more networks. The memory (230) also stores instructions to be executed by the processor (210). The memory (230) may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or various forms of electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM). In addition, in some examples, the memory (230) may be considered to be a non-transitory storage medium. The term "non-transitory" may mean that the storage medium is not specifically implemented in a carrier or propagation signal. However, the term "non-transitory" should not be interpreted as the memory (230) being non-removable. In some examples, a non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or a cache).

[0150] although Figure 4 Various hardware components of the PIN network device (200) are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, the PIN network device (200) may include fewer or greater numbers of components. In addition, the labels or names of the components are for illustrative purposes only and do not limit the scope of the present disclosure. One or more components may be combined together to perform the same or substantially similar functions in the PIN network device (200).

[0151] Figure 5 A PINE (100) according to an embodiment as disclosed herein is shown. In one embodiment, the PINE (100) includes a processor (110), a communicator (120), a memory (130), and a service-based PINE controller (140). The processor (110) is connected to the communicator (120), the memory (130), and the service-based PINE controller (140).

[0152] The PINE (100) is considered to be a first PINE (100a). The service-based PINE controller (140) receives PIN information broadcasted by the PIN network device (200). In addition, the service-based PINE controller (140) determines whether to send a first message to the PIN network device (200) based on a local configuration and the PIN information received from the PIN network device (200).

[0153] In addition, the service-based PINE controller (140) sends a first message based on the PIN information to join the PIN. The first message includes security credentials for verifying the first PINE (100a), services provided by the first PINE (100a), and services requested by the first PINE (100a) in the PIN (1000). In addition, the service-based PINE controller (140) receives a second message from the network device (200) to indicate joining the first PINE (100a) to the PIN (1000). The second message includes a PIN identifier of a second PINE (100b) that supports the service requested by the first PINE (100a) in the PIN (1000). In addition, the service-based PINE controller (140) performs PIN-PIN communication with the second PINE (100b) based on the PIN identifier of the second PINE (100b). In addition, the service-based PINE controller (140) receives services from another PIN (e.g., a second PIN).

[0154] The PINE (100) is considered to be a second PINE (100b). The service-based PINE controller (140) receives PIN information broadcasted by the PIN network device (200). In addition, the service-based PINE controller (140) receives a service request message for supporting a service requested by the first PINE (100a) from the network device (200). In addition, the service-based PINE controller (140) determines whether to send a first message to the network device (200) based on a local configuration and the PIN information received from the PIN network device (200).

[0155] In addition, the service-based PINE controller (140) sends a first message to join the PIN (1000) based on the PIN information and the service request message. The first message includes security credentials for verifying the second PINE (100b), services provided by the second PINE (100b), and services requested by the second PINE (100b) in the PIN (1000).

[0156] In addition, the service-based PINE controller (140) receives a second message from the PIN network device (200) indicating the addition of a second PINE (100b) to the PIN (1000) that supports the service requested by the first PINE (100a) in the PIN (1000). In addition, the service-based PINE controller (140) receives a PIN-PIN communication including a PIN identifier of the second PINE (100b) from the first PINE (100a). In addition, the service-based PINE controller (140) sends a service from the second PIN.

[0157] The service-based PINE controller (140) 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, hard-wired circuits, etc., and can optionally be driven by firmware.

[0158] In addition, the processor (110) is configured to execute instructions stored in the memory (130) and perform various processes. The communicator (120) is configured to communicate internally between internal hardware components and to communicate with external devices via one or more networks. The memory (130) also stores instructions to be executed by the processor (110). The memory (130) may include a non-volatile storage element. Examples of such non-volatile storage elements may include a magnetic hard disk, an optical disk, a floppy disk, a flash memory, or various forms of electrically programmable memory (EPROM) or electrically erasable programmable memory (EEPROM). In addition, in some examples, the memory (130) may be considered to be a non-transitory storage medium. The term "non-transitory" may mean that the storage medium is not specifically implemented in a carrier or propagation signal. However, the term "non-transitory" should not be interpreted as the memory (130) being non-removable. In some examples, a non-transitory storage medium may store data that may change over time (e.g., in a random access memory (RAM) or a cache).

[0159] although Figure 5 Various hardware components of PINE (100) are shown, but it should be understood that other embodiments are not limited thereto. In other embodiments, PINE (100) may include fewer or greater numbers of components. In addition, the labels or names of the components are for illustrative purposes only and do not limit the scope of the present disclosure. One or more components may be combined together to perform the same or substantially similar functions in PINE (100).

[0160] Figure 6 A flow chart (S600) is shown of a method for service-based addition of a PINE (100) to a PIN (1000) implemented by a PIN network device (200) according to an embodiment as disclosed herein. Operations (S602 to S610) are processed by a service-based PINE controller (240).

[0161] At step S602, the method includes broadcasting PIN information to a plurality of PINEs (100a to 100b). At step S604, the method includes receiving a first message to join a PIN (1000) from a first PINE (100a) of the plurality of PINEs based on the PIN information. The first message includes security credentials of the first PINE (100a), services provided by the first PINE (100a), and services requested by the first PINE (100a) of the PIN (1000). At step S606, the method includes determining a second PINE (100b) from the plurality of PINEs that supports the service requested by the first PINE of the PIN (1000).

[0162] At step S608, the method includes adding the first PINE (100a) to the PIN (1000) based on the security credentials and PIN information of the first PINE (100a). At step S610, the method includes sending a second message to the first PINE (100a) indicating the addition of the first PINE (100a) to the PIN (1000). The second message includes a PIN identifier of a second PINE (100b) that supports the service requested by the first PINE (100a) in the PIN (1000).

[0163] Figure 7 A flow chart (S700) of a method implemented by a first PINE (100a) for service-based addition of a PINE to a PIN (1000) according to an embodiment as disclosed herein is shown. Operations (S702 to S712) are processed by a service-based PINE controller (140).

[0164] At step S702, the method includes receiving PIN information broadcasted by the PIN network device (200). At step S704, the method includes determining whether to send a first message to the PIN network device (200) based on at least one local configuration and the PIN information received from the PIN network device (200).

[0165] At step S706, the method includes sending a first message based on the PIN information to join the PIN (1000). The first message includes security credentials for verifying the first PINE (100a), services provided by the first PINE (100a), and services requested by the first PINE (100a) in the PIN (1000). At step S708, the method includes receiving a second message from the PIN network device (200) indicating the joining of the first PINE (100a) to the PIN (1000). The second message includes a PIN identifier of a second PINE (100b) that supports the service requested by the first PINE (100a) in the PIN (1000).

[0166] At step S710, the method includes performing PIN-PIN communication with a second PINE (100b) based on a PIN identifier of the second PINE (100b).At step S712, the method includes receiving a service from the second PIN.

[0167] Figure 8 A flow chart (S800) is shown of a method implemented by a second PINE (100b) for service-based joining of a PINE (100) to a PIN (1000) according to an embodiment as disclosed herein. Operations (S802 to S814) are processed by a service-based PINE controller (140).

[0168] At step S802, the method includes receiving PIN information broadcasted by a PIN network device (200). At step S804, the method includes receiving a service request message for supporting a service requested by a first PINE (100a) from the PIN network device (200). At step S806, the method includes determining whether to send a first message to a network device (200) based on at least one local configuration and the PIN information received from the PIN network device (200).

[0169] At step S808, the method includes sending a first message to join the PIN (1000) based on the PIN information and the service request message. The first message includes security credentials for verifying the second PINE (100b), services provided by the second PINE (100b), and services requested by the second PINE (100b) in the PIN (1000). At step S810, the method includes receiving a second message from the network device (200) indicating that the second PINE (100b) is joined to the PIN (1000), which supports the service requested by the first PINE (100a) in the PIN (1000). At step S812, the method includes receiving a PIN-PIN communication including a PIN identifier of the second PINE (100b) from the first PINE (100a). At step S814, the method includes sending the service from the second PIN.

[0170] In the embodiment, the service term is used as an example, but it can be any parameter of the PIN information discussed in this embodiment. The term service can be replaced by these parameters, and the same solution applies.

[0171] The various actions, behaviors, modules, steps, etc. in the flow chart (S600 to S800) can be performed in the order presented, in a different order, or simultaneously. In addition, in some embodiments, some actions, behaviors, modules, steps, etc. can be omitted, added, modified, skipped, etc. without departing from the scope of the present disclosure.

[0172] The foregoing description of specific embodiments will fully reveal the general nature of the embodiments herein, so that others can easily modify and / or adapt such specific embodiments to various applications without departing from the general concepts by applying current knowledge, and therefore, such adaptations and modifications should and are intended to be understood as belonging to the meaning and scope of the equivalents of the disclosed embodiments. It should be understood that the wording or terminology used herein is for descriptive purposes and not for limitation. Therefore, although the embodiments herein have been described according to preferred embodiments, those skilled in the art will recognize that the embodiments herein can be modified to practice within the scope of the embodiments described herein.

[0173] Although the present disclosure has been described with various embodiments, various changes and modifications may occur to those skilled in the art. It is intended that the present disclosure encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method for a personal Internet of Things network element PEMC with management capabilities, the method include: Transmitting a first message, wherein the first message includes information related to a personal Internet of Things network PIN; receiving a first join request message from a first Personal Internet of Things network element PINE, wherein the first join request message includes information related to supported services of the first PINE; determining whether to add the first PINE to the PIN based on the information related to the supported service; as well as Based on determining that the first PINE has been added to the PIN, a first joining acceptance message is transmitted to the first PINE, the first joining acceptance message including at least one identifier (ID) of at least one PINE in the PIN.

2. The method of claim 1, wherein transmitting the first message include: receiving a second message from the first PINE to query services in the PIN; as well as The first message including information related to the PIN is transmitted.

3. The method according to claim 1, further comprising: include: receiving a second join request message from a second PINE, the second join request message including information related to a requested service of the second PINE; transmitting a third message including information related to the requested service of the second PINE in a case where the PIN does not provide the requested service of the second PINE; receiving a third join request message from a third PINE providing the requested service of the second PINE; transmitting a second join acceptance message to the third PINE; determining whether to add the second PINE to the PIN based on information related to the requested service of the second PINE; based on determining that the second PINE has been added to the PIN, transmitting a third join acceptance message to the second PINE; as well as In case there is no reply to the third message within a certain period of time, a join reject message is transmitted to the second PINE.

4. The method of claim 1, wherein the first message further includes at least one of supported PIN services, requested PIN services, information of a timer, an identifier ID, or a group ID, and The first join request message also includes security credentials that enable the PEMC to verify the first PINE.

5. A method for a personal Internet of Things network element PINE, the method include: receiving a first message from a personal Internet of Things network element PEMC with management capabilities, the first message including information related to the personal Internet of Things network PIN; transmitting a first join request message to the PEMC, the first join request message including information related to supported services of the PINE; as well as In case the PINE is added to the PIN based on the information related to the supported service, a first join accept message is received from the PEMC, the first join accept message including at least one identifier ID of at least one PINE in the PIN.

6. The method of claim 5, wherein receiving the first message include: transmitting a second message to the PEMC to query services in the PIN; as well as The first message including information related to the PIN is received from the PEMC.

7. The method according to claim 5, further comprising: include: transmitting a second join request message to the PEMC, the second join request message including information related to a requested service of the PINE; in a case where the PIN does not provide the requested service of the PINE, adding another PINE that provides the requested service of the PINE to the PIN, and when the PINE is added to the PIN, receiving a second joining acceptance message from the PEMC; as well as In case the PIN does not provide the requested service of the PINE and the another PINE is not joined to the PIN, a join rejection message is received from the PEMC.

8. The method of claim 5, wherein the first message further includes at least one of supported PIN services, requested PIN services, information of a timer, an identifier ID, or a group ID, and The first join request message also includes security credentials that enable the PEMC to verify the PINE.

9. A personal Internet of Things network element PEMC with management capability, the PEMC include: Transceiver; as well as A controller is connected to the transceiver and is configured to: transmitting a first message, wherein the first message includes information related to a personal Internet of Things network PIN, receiving a first join request message from a first Personal Internet of Things network element PINE, wherein the first join request message includes information related to a supported service of the first PINE, determining whether to add the first PINE to the PIN based on the information related to the supported service, and Based on determining that the first PINE has been added to the PIN, a first joining acceptance message is transmitted to the first PINE, the first joining acceptance message including at least one identifier (ID) of at least one PINE in the PIN.

10. The PEMC of claim 9, wherein the controller is further configured to: receiving a second message from the first PINE to query services in the PIN, and The first message including information related to the PIN is transmitted.

11. The PEMC of claim 9, wherein the controller is further configured to: receiving a second join request message from a second PINE, the second join request message including information related to a requested service of the second PINE, transmitting a third message including information related to the requested service of the second PINE in the event that the PIN does not provide the requested service of the second PINE, receiving a third join request message from a third PINE providing the requested service of the second PINE, transmitting a second join accept message to the third PINE, determining whether to add the second PINE to the PIN based on information related to the requested service of the second PINE, based on determining that the second PINE has been added to the PIN, transmitting a third join accept message to the second PINE, and In case there is no reply to the third message within a certain period of time, a join reject message is transmitted to the second PINE.

12. The PEMC of claim 9, wherein the first message further includes at least one of supported PIN services, requested PIN services, information of a timer, an identifier ID, or a group ID, and The first join request message also includes security credentials that enable the PEMC to verify the first PINE.

13. A personal Internet of Things network element PINE, the PINE include: Transceiver; as well as A controller is connected to the transceiver and is configured to: receiving a first message from a personal Internet of Things network element PEMC with management capabilities, the first message including information related to the personal Internet of Things network PIN, transmitting a first join request message to the PEMC, the first join request message including information related to supported services of the PINE, and In case the PINE is added to the PIN based on the information related to the supported service, a first join accept message is received from the PEMC, the first join accept message including at least one identifier ID of at least one PINE in the PIN.

14. The PINE of claim 13, wherein the controller is further configured to: transmitting a second message to the PEMC to query the services in the PIN, and receiving, from the PEMC, the first message including information related to the PIN, The first message further includes at least one of supported PIN services, requested PIN services, timer information, an identifier ID or a group ID, and The first join request message also includes security credentials that enable the PEMC to verify the PINE.

15. The PINE of claim 13, wherein the controller is further configured to: transmitting a second join request message to the PEMC, the second join request message including information related to the requested service of the PINE, adding another PINE that provides the requested service of the PINE to the PIN if the PIN does not provide the requested service of the PINE, and receiving a second joining acceptance message from the PEMC when the PINE is added to the PIN, and In case the PIN does not provide the requested service of the PINE and the another PINE is not joined to the PIN, a join rejection message is received from the PEMC.

Images