System and method for determining the availability status of an entity in a PIN

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting high data transmission rates. A method (300) and system for determining an availability status of a first entity associated with a personal Internet of Things (IoT) network (PIN) (210) is described. The method (300) may include determining (302) by a second entity associated with the PIN (210) whether a periodic update request is received from the first entity before a periodic update (PU) timer value expires. The method (300) may also include determining (304) by the second entity the availability status of the first entity based on the determination of whether the periodic update request is received from the first entity.

Description

Technical Field

[0001] The present invention relates generally to Internet of Things (IoT) environments, and more particularly to methods and systems for determining the availability status of entities within a Personal IoT Network (PIN) and assigning PIN-related functions to different entities within the PIN. Background Art

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

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communication (URLLC) and massive machine type communication (mMTC), standardization has been carried out on the following various technologies: beamforming and massive MIMO for mitigating radio wave path loss in millimeter waves and increasing radio wave transmission distance, support parameter sets for dynamic operation of efficient utilization of millimeter wave resources and time slot formats (for example, operation of multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of bandwidth parts (BWPs), new channel coding methods such as low-density parity-check (LDPC) codes for large-scale data transmission and polar codes for highly reliable transmission of control information, L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, in view of the services to be supported by 5G mobile communication technology, discussions are underway on improvements and performance enhancements to initial 5G mobile communication technology, and there is already physical layer standardization on various technologies such as: Vehicle-to-everything (V2X) for assisting driving determination of autonomous vehicles based on information about the location and status of vehicles sent by vehicles and for enhancing user convenience, New Radio Unlicensed (NR-U) for system operation designed to comply with various regulatory requirements in unlicensed bands, NR UE power saving, Non-Terrestrial Network (NTN) for UE-satellite direct communication to provide coverage in areas where communication with terrestrial networks is unavailable, and positioning.

[0005] In addition, standardization has been carried out on various technologies such as the following: Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, Integrated Access and Backhaul (IAB) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional handover and Dual Active Protocol Stack (DAPS) handover, and two-step random access (two-step RACH for NR) for simplifying the random access procedure. Standardization is also underway on various technologies such as the following: 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software-defined networking (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. Therefore, it is expected that enhanced functionality and performance of 5G mobile communication systems and the integrated operation of connected devices will become necessary. 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.; 5G performance improvement and complexity reduction through the use of artificial intelligence (AI) and machine learning (ML); AI service support; meta-space service support; and drone communication.

[0007] In addition, such development of 5G mobile communication systems will not only provide a basis for developing new waveforms for providing coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies (such as full-dimensional MIMO (FD-MIMO), array antennas and massive antennas), metamaterial-based lenses and antennas for improving the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using orbital angular momentum (OAM) and reconfigurable smart surfaces (RIS), but will also provide a basis for developing full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for achieving system optimization by utilizing satellites and artificial intelligence (AI) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for achieving services with a complexity level that exceeds the operational capability limits of UEs by utilizing ultra-high performance communication and computing resources. Summary of the Invention

[0008] Technical issues

[0009] The present disclosure relates to wireless communication systems, and more particularly, to availability status of entities within a Personal IoT Network (PIN) and PIN-related functionality of different entities within the PIN.

[0010] Solution to the problem

[0011] This summary is provided to introduce a selection of concepts in a simplified format that will be further described in the detailed description of the invention. This summary is not intended to identify key or essential inventive concepts of the invention nor is it intended to determine the scope of the invention.

[0012] According to one embodiment of the present disclosure, a method for determining the availability status of a first entity associated with a personal Internet of Things (IoT) network (PIN) is disclosed. The method includes determining, by a second entity associated with the PIN, whether a periodic update request is received from the first entity before a periodic update (PU) timer value expires. The method also includes determining, by the second entity, the availability status of the first entity based on whether the periodic update request is received from the first entity.

[0013] According to another embodiment of the present disclosure, a method for determining an availability status of a PIN element with gateway capability (PEGC) associated with a personal Internet of Things (IoT) network (PIN) is disclosed. The method includes determining, by a PIN element with management capability (PEMC) associated with the PIN, whether a periodic update request is received from the PEGC before a periodic update (PU) timer value expires. The method also includes determining, by the PEMC, the availability status of the PEGC based on the determination of whether the periodic update request is received from the PEGC.

[0014] According to yet another embodiment of the present disclosure, a method for determining the availability status of a PIN element (PINE) associated with a personal Internet of Things (IoT) network (PIN) is disclosed. The method includes determining, by a PIN element with management capabilities (PEMC) associated with the PIN, whether a periodic update request is received from the PINE before a periodic update (PU) timer value expires. Furthermore, the method includes determining, by the PEMC, the availability status of the PINE based on the determination of whether the periodic update request is received from the PINE.

[0015] According to yet another embodiment of the present disclosure, a method for determining the availability status of a personal Internet of Things (IoT) network (PIN) with management capabilities (PEMC) is disclosed. The method includes determining, by a PIN server associated with the PIN, whether a periodic update request is received from the PEMC before a periodic update (PU) timer value expires. Furthermore, the method includes determining, by the PIN server, the availability status of the PEMC based on the determination of whether the periodic update request is received from the PEMC.

[0016] According to another embodiment of the present disclosure, a method for allocating a new gateway-capable Personal Internet of Things (IoT) network (PIN) element (PEGC) for a PIN is disclosed. The PIN includes multiple PIN elements, a PIN management element (PEMC), and a PIN server. The method includes the PEMC determining, by the PEMC, that the availability status of a current PEGC within the PIN is unavailable. Furthermore, the method includes, upon determining that the availability status of the current PEGC is unavailable, selecting, by the PIN server, a first PINE from among the multiple PINEs as a new PEGC for the PIN.

[0017] According to another embodiment of the present disclosure, a system for determining an availability status of a first entity associated with a personal Internet of Things (IoT) network (PIN) is disclosed. The system includes a second entity configured to determine whether a periodic update request is received from the first entity before a periodic update (PU) timer value expires. The second entity is further configured to determine the availability status of the first entity based on the determination of whether the periodic update request is received from the first entity.

[0018] According to another embodiment of the present disclosure, a system for determining the availability status of a personal Internet of Things (IoT) network (PIN)-enabled gateway component (PEGC) is disclosed. The system includes a PIN management component (PEMC) associated with the PIN. The PEMC is configured to determine whether a periodic update request is received from the PEGC before a periodic update (PU) timer value expires. The PEMC is further configured to determine the availability status of the PEGC based on the determination of whether the periodic update request is received from the PEGC.

[0019] According to another embodiment of the present disclosure, a system for determining the availability status of a personal Internet of Things (IoT) network (PIN) element (PINE) associated with a personal Internet of Things (IoT) network (PIN) is disclosed. The system includes a PIN element (PEMC) associated with the PIN with management capabilities. The PEMC is configured to determine whether a periodic update request is received from the PINE before a periodic update (PU) timer value expires. The PEMC is further configured to determine the availability status of the PINE based on the determination of whether the periodic update request is received from the PINE.

[0020] According to another embodiment of the present disclosure, a system for determining the availability status of a personal Internet of Things (IoT) network (PIN) with management capabilities (PEMC) is disclosed. The system includes a PIN server associated with the PIN. The PIN server is configured to determine whether a periodic update request is received from the PEMC before a periodic update (PU) timer value expires. Furthermore, the PIN server is configured to determine the availability status of the PEMC based on the determination of whether the periodic update request is received from the PEMC.

[0021] According to another embodiment of the present disclosure, a system for allocating a new gateway-capable Personal Internet of Things (IoT) network (PIN) element (PEGC) for a PIN is disclosed. The PIN includes multiple PIN elements, a PIN management element (PEMC), and a PIN server. The system includes the PEMC configured to determine the availability status of the current PEGC within the PIN as unavailable. Furthermore, the system includes the PIN server configured to select a first PINE from a plurality of PINEs as a new PEGC for the PIN when the availability status of the current PEGC is determined to be unavailable.

[0022] To further illustrate the advantages and features of the present invention, a more detailed description of the present invention will be presented by reference to specific embodiments of the present invention shown in the accompanying drawings. It should be understood that these drawings depict only typical embodiments of the present invention and are not to be considered as limiting the scope thereof. The present invention will be described and explained with additional features and details in conjunction with the accompanying drawings.

[0023] Advantageous Effects of the Invention

[0024] According to embodiments of the present disclosure, the availability status of an entity can be effectively determined. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings, in which like reference numerals represent like parts throughout the several views, and in which:

[0026] Figure 1 A prior art operational flow chart depicting the process when any entity is disconnected from a personal Internet of Things (IoT) network (PIN) according to the prior art is shown.

[0027] Figure 2A A schematic block diagram illustrating an environment associated with a Personal Internet of Things (IoT) network (PIN) according to an embodiment of the present invention is shown;

[0028] Figure 2B shows a schematic block diagram of a system within an environment according to an embodiment of the present invention;

[0029] Figure 3 A flow chart including a method for determining an availability status of a first entity according to an embodiment of the present invention is shown;

[0030] Figure 4A A flow chart including a method for determining the availability status of a PEGC according to an embodiment of the present invention is shown;

[0031] Figure 4BA flow chart of a method including a new PEGC for allocating PINs according to an embodiment of the present invention is shown;

[0032] Figure 4C An operational flow diagram depicting a process for determining the availability status of a PEGC according to an embodiment of the present invention is shown;

[0033] Figure 4D shows an operational flow chart depicting a process for allocating a new PEGC for a PIN in accordance with an embodiment of the present invention;

[0034] Figure 5A A flow chart including a method for determining the availability status of a PINE according to an embodiment of the present invention is shown;

[0035] Figure 5B An operational flow chart depicting a process for determining the availability status of a PINE according to an embodiment of the present invention is shown;

[0036] Figure 5C An operational flow diagram depicting a process for pausing data transmission to a PINE in accordance with an embodiment of the present invention is shown;

[0037] Figure 6A A flow chart including a method for determining the availability status of a PEMC according to an embodiment of the present invention is shown;

[0038] Figure 6B 1. A flow chart of a method including a new PEMC for allocating PINs according to an embodiment of the present invention is shown;

[0039] Figure 6C An operational flow chart depicting a process for determining the availability status of a PEMC according to an embodiment of the present invention is shown; and

[0040] Figure 6D An operational flow diagram depicting a process for assigning a new PEMC for a PIN is shown, in accordance with an embodiment of the present invention.

[0041] Furthermore, those skilled in the art will appreciate that the elements in the drawings are illustrated for simplicity and may not necessarily be drawn to scale. For example, a flow chart illustrates the method in terms of the most prominent steps involved to help improve understanding of the various aspects of the present invention. Furthermore, with respect to 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 relevant to understanding the embodiments of the present invention so as not to obscure the drawings with details that would be apparent to one of ordinary skill in the art having the benefit of the description herein. DETAILED DESCRIPTION

[0042] A Personal Internet of Things (IoT) network (PIN) includes multiple entities that communicate with the core network and / or PIN server. These entities may include a PIN element (PINE), a PIN element with gateway capabilities (PEGC), and a PIN element with management capabilities (PEMC). The PEGC acts as a gateway for connections between different PINEs and between the PINE and the core network. The PEMC acts as the management entity for the PIN. A PINE can provide or receive various services within the PIN.

[0043] Figure 1 A prior art operational flow chart depicting the process when any entity is disconnected from a Personal Internet of Things (IoT) network (PIN) according to the prior art is shown. At block 102, the PIN is active, with the PINs connected to each other and to the core network via the PEGC. The PEMC is managing the PIN.

[0044] At block 104, any of the PEGC, PEMC, or PINEs may be disconnected or lost from the PIN. When the PEGC leaves the PIN, all PINEs served by the PEGC become disconnected from the PIN, and the PIN services they provide or require become unavailable to other PINEs. When the PEMC leaves the PIN, the PEGC and all PINEs managed by the PEMC are left without a service management entity. When any PINE becomes unavailable, it may be impossible to provide or receive PIN services from the unavailable PINE.

[0045] The core network and / or PIN server may be unable to determine the availability status of any of the disconnected PEGC, PEMC, or PINE at block 106. The core network and / or PIN server may be unable to take any necessary actions, such as assigning PIN-related functions, regarding any unavailability of the PEGC or PEMC or PINE.

[0046] Currently, no methods or systems are defined to detect the unavailability of entities within the PIN (PEGC / PEMC / PINE). The core network and / or PIN server may remain unaware of the availability of the entity. As a result, PIN functions and services may be impaired due to the unavailability of entities within the PIN.

[0047] Therefore, there is a need for an improved method and system to address the aforementioned issues. For example, there is a need for a system and method to determine the availability status of an entity within a PIN. Furthermore, there is a need for a system and method to facilitate the assignment of PIN-related functionality associated with an unavailable entity to other entities within the PIN.

[0048] For the purpose of promoting an understanding of the principles of the invention, reference will now be made to various embodiments, and specific language will be used to describe these embodiments. It will be understood, however, that no limitation of the scope of the invention is intended thereby, and that such alterations and further modifications in the illustrated systems, as well as such further applications of the principles of the invention as illustrated herein, will normally occur to those skilled in the art to which the invention relates.

[0049] Those skilled in the art will understand that both the foregoing general description and the following detailed description are illustrative of the present invention and are not intended to restrict the invention.

[0050] Reference throughout this specification to "one aspect," "another aspect," or similar language means that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases "in an embodiment," "in another embodiment," and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.

[0051] The terms "comprises," "includes," or any other variations thereof are intended to cover a non-exclusive inclusion such that a process or method that comprises a list of steps may include not only those steps but may also include other steps not expressly listed or inherent to such process or method. Similarly, without more constraints, one or more devices or subsystems or elements or structures or components preceded by "comprises..." does not preclude the presence of other devices or other subsystems or other elements or other structures or other components or additional devices or additional subsystems or additional elements or additional structures or additional components.

[0052] The present invention is directed to methods and systems for determining the availability status of one or more entities in a personal Internet of Things (IoT) network (PIN) and allocating PIN-related functions to different entities within the PIN. The one or more entities may include one or more PIN elements (PINEs), a PIN element with gateway capabilities (PEGCs), and a PIN element with management capabilities (PEMCs).

[0053] Figure 2AA schematic block diagram illustrates an environment 200 for determining the availability status of entities within a personal Internet of Things (IoT) network (PIN) and facilitating the assignment of PIN-related functionality associated with unavailable entities to other entities within the PIN, according to an embodiment of the present disclosure. The environment 200 may be associated with a PIN 210. The PIN 210 may include a plurality of entities 220. The plurality of entities 220 may include one or more PIN elements (PINEs) 222a-222n, a PIN element with gateway capabilities (PEGC) 224, and a PIN element with management capabilities (PEMC) 226. In some embodiments, each of the plurality of entities 220 may be associated with a corresponding PIN identifier (PIN-ID).

[0054] Environment 200 also includes a PIN server 230 and a core network entity 240 that communicates with PIN 210 via a communication network. In some embodiments, core network entity 240 may be a 5G core network entity. In some embodiments, core network entity 240 may include one or more of an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), a unified data management (UDM), and the like. In some embodiments, PIN server 230 may include a PIN network function (PINNF) and / or a PIN application function (PINAF). In some embodiments, PINNF may refer to a core network entity responsible for allocating and managing PIN identifiers (IDs) associated with multiple entities 220. In some embodiments, PINAF may refer to a network function connected to core network entity 240 via a network exposure function (NEF) and may be configured for policy configuration and provisioning of PIN 210 and multiple entities 220.

[0055] In some embodiments, the plurality of entities 220 may be communicatively coupled to each other via a direct network connection or a PIN direct connection. In some embodiments, the plurality of entities 220 may be communicatively coupled to each other via a proximity service (ProSe) that allows device-to-device (D2D) communication.

[0056] In some embodiments, each of the plurality of entities 220 comprises a user equipment (UE) and / or a non-3rd Generation Partnership Project (non-3GPP) device, such as, but not limited to, a smart phone, a smart watch, a tablet, a personal digital assistant (PDA), and / or a laptop.

[0057] In some embodiments, the PEGC 224 can be configured to provide connectivity to and from the core network entity 240 for multiple entities 220, including PINEs 222a-222n and PEMCs 226. In some embodiments, the PEGC 224 is configured to facilitate registration and access to a network (e.g., a 5G network) by the multiple entities 220 through the core network entity 240. In some embodiments, the PEGC 224 can be configured to facilitate communications among entities within the PIN 210 (such as PINEs that are not within range using direct communications). Thus, the PEGC 224 can act as a gateway for communications among different entities 220, between an entity 220 and a PIN server 230, and between an entity 220 and a core network entity 240.

[0058] In some embodiments, PEMC 226 may be configured to manage PIN 210. In some embodiments, PEMC 226 may be associated with an authorized administrator to facilitate configuration and management of PIN 210.

[0059] In some embodiments, PINEs 222a-222n may be configured to provide associated services within PIN 210. As non-limiting examples, PINEs may include printers, smart thermostats, smart sprinklers, smart blinds, smart garages, and other smart devices.

[0060] In some embodiments, the environment 200 includes one or more systems formed by a combination of multiple entities 220, such as Figure 2B Environment 200 may include system 260A, which includes PEGC 224 and PEMC 226. Environment 200 may include system 260B, which includes PINE 222n and PEMC 226. Environment 200 may include system 260C, which includes PIN server 230 and PEMC 226. Environment 200 may include system 260D, which includes PIN server 230, PEGC 224, PEMC 226, and one of multiple PINEs 222a-222n (here, 222a). Environment 200 may include system 260E, which includes PIN server 230, PEGC 224, PEMC 226, and one of multiple PINEs 222a-222n (here, 222b).

[0061] It should be understood that the environment 200 may include additional systems formed by various combinations of the plurality of entities 220. That is, the environment 200 may include a system formed by a first entity and a second entity in the plurality of entities 220. It should be understood that the term "system" as used in this disclosure refers to a system formed by a combination of the plurality of entities 220.

[0062] In some embodiments, each entity in the plurality of entities 220 may be associated with a memory and a processor communicatively coupled to the memory. Figure 2A As shown, entity 222n (i.e., PINE 222n) is shown as including a processor 270 and a memory 280. It should be understood that while one or more details may be provided for the processor 270 and the memory 280 of entity 222n / PINE 222n, the one or more details are equally applicable to the corresponding processor and memory of each of the plurality of entities 220. The functionality of the entity 220 may be provided by the corresponding processor 270 and the corresponding memory 280.

[0063] In some embodiments, the processor 270 and the memory 280 may be on-device units and may be integrated with the entity 222 n. In some embodiments, the functionality of the processor 270 and the memory 280 may be provided by a cloud-based unit in communication with the entity 222 n. In some embodiments, the functionality of the processor 270 and the memory 280 may be provided in a distributed manner, i.e., distributed across the cloud and the device.

[0064] In some embodiments, the processor 270 and the memory 280 may communicate with one or more modules (not shown). In some embodiments, one or more modules may be included in the memory 280. The memory 280 may be configured to store data and instructions that can be executed by the processor 270. The memory 280 may include a database configured to store data. The one or more modules may include a set of instructions that can be executed to cause the corresponding entity to perform any one or more of the methods disclosed herein, for example, using data stored in a database. In an embodiment, each of the one or more modules may be a hardware unit that may be external to the memory 280. In addition, the memory 280 may include an operating system for performing one or more tasks of the corresponding entity, such as performed by a generic operating system in the communication domain.

[0065] In some embodiments, the functions, actions, or tasks shown or described in the figures may be performed by a programmed processor 270 for executing instructions stored in memory 280. The functions, actions, or tasks performed by an entity may be performed by the entity's corresponding processor in conjunction with its corresponding memory. The functions, actions, or tasks are independent of a particular type of instruction set, storage medium, processor, or processing strategy and may be performed by software, hardware, integrated circuits, firmware, microcode, etc., operating alone or in combination. Similarly, processing strategies may include multi-processing, multi-tasking, parallel processing, etc.

[0066] The memory 280 may include, but is not limited to, non-transitory computer-readable storage media, such as various types of volatile and non-volatile storage media, including, but not limited to, random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media, etc. In one example, the memory 280 may include a cache or random access memory for the processor. In alternative examples, the memory 280 is separate from the processor / controller, such as a cache memory in the processor, system memory, or other memory.

[0067] In one embodiment, the processor 270 may include a dedicated processing unit, such as an integrated system (bus) controller, a memory management control unit, a floating point unit, a graphics processing unit, a digital signal processing unit, etc. In one embodiment, the processor 270 may include a central processing unit (CPU), a graphics processing unit (GPU), or both. The processor 270 may be one or more general-purpose processors, digital signal processors, application-specific integrated circuits, field programmable gate arrays, servers, networks, digital circuits, analog circuits, combinations thereof, or other devices now known or later developed for analyzing and processing data. The processor 270 may implement a software program, such as manually generated (i.e., programmed) code. In some embodiments, the processor 270 may include one or more of the processors. One or more of the processors may be a general-purpose processor (such as a central processing unit (CPU), an application processor (AP), etc.), a graphics processing unit (such as a graphics processing unit (GPU)), a visual processing unit (VPU), and / or an AI-specific processor (such as a neural processing unit (NPU)).

[0068] In some embodiments, each of the plurality of entities 220 may include a transceiver (not shown) and an I / O interface (not shown). The I / O interface may provide display functionality and one or more physical buttons on the corresponding entity. The I / O interface may utilize communication protocols such as Code Division Multiple Access (CDMA), High Speed ​​Packet Access (HSPA+), Global System for Mobile Communications (GSM), Long Term Evolution (LTE), WiMax, etc. In some embodiments, the processor 270 may be configured to communicate with a communication network via a network interface. The network interface may be an I / O interface of a corresponding entity of the processor 270. The network interface may connect to the communication network. The network interface may utilize connection protocols including, but not limited to, direct connection, Ethernet (e.g., twisted pair 10 / 100 / 1000Base T), Transmission Control Protocol / Internet Protocol (TCP / IP), Token Ring, IEEE 802.11a / b / g / n / x, etc. The communication network may include, but not limited to, direct interconnection, a local area network (LAN), a wide area network (WAN), a wireless network (e.g., using Wireless Application Protocol), the Internet, etc. The network interface may employ connection protocols including but not limited to direct connection, Ethernet (e.g., twisted pair 10 / 100 / 1000Base T), Transmission Control Protocol / Internet Protocol (TCP / IP), Token Ring, IEEE 802.11a / b / g / n / x, etc.

[0069] For the sake of brevity, the architecture and standard operation of the operating system, memory, database, processor, transceiver, and I / O interfaces are not discussed in detail.

[0070] In some embodiments, each of the plurality of entities 220 may be associated with a timer corresponding to a periodic update (PU) timer value. In some embodiments, each of the plurality of entities 220 may be configured to send a periodic update request to indicate availability within the PIN 210 before the PU timer value expires.

[0071] In some embodiments, considering a first entity and a second entity in the plurality of entities 220, an availability status of the first entity may be determined. The first entity and the second entity may form a corresponding system. The second entity may be configured to determine whether a periodic update request is received from the first entity before a PU timer value expires. The second entity may be configured to determine the availability status of the first entity based on the determination of whether a periodic update request is received from the first entity. In some embodiments, the PU timer value may define a periodicity of PU update requests to be sent by the first entity to the second entity to indicate the availability of the first entity.

[0072] In some embodiments, the second entity may be configured to determine the availability status of the first entity as unavailable within the PIN upon determining that no periodic update request is received from the first entity before expiration of the PU timer value. The second entity may be configured to determine the availability status of the first entity as available within the PIN upon determining that a periodic update request is received from the first entity before expiration of the PU timer value.

[0073] It should be understood that the term "before" as used in this disclosure is intended to mean "at or before."

[0074] In some embodiments, the first entity is PEGC 224 and the second entity is PEMC 226, thereby forming part of system 260A. In some embodiments, the first entity is PINE 222n of a plurality of PINEs 222a-222n and the second entity is PEMC 226, thereby forming part of system 260B. In some embodiments, the first entity is PEMC 226 and the second entity is PIN server 230, thereby forming part of system 260C. Thus, the availability status of the first entity within the PIN can be determined by the second entity.

[0075] refer to Figure 3 , illustrates an exemplary process including a method 300 for determining the availability status of a first entity according to one embodiment of the present disclosure. At step 302, the method 300 includes determining, by a second entity, whether a periodic update request is received from the first entity before the PU timer value expires. At step 304, the method 300 includes determining, by the second entity, the availability status of the first entity based on the determination of whether a periodic update request is received from the first entity.

[0076] PEGC Availability and Allocation of New PEGCs

[0077] Reference again Figure 2A-2B In some embodiments, the PEGC 224 is associated with a timer corresponding to a PU timer value. The PU timer value is assigned to the PEGC 224 by one of the PEMC 226 and the PIN server 230. In some embodiments, the PU timer value may be configured by a user associated with the entity 220 within the PIN 210. In some embodiments, the PEGC 224 may be configured to send periodic update requests prior to the expiration of the PU timer value to indicate availability within the PIN 210. In some embodiments, the PU timer value may define the periodicity of the PU update requests to be sent by the PEGC 224 to the PEMC 226 to indicate the availability of the PEGC 224.

[0078] In some embodiments, the availability status of the PEGC 224 within the PIN 210 may be determined. Figure 2B The system 260A shown in FIG may include a PEMC 226 configured to determine whether a periodic update request is received from the PEGC before the PU timer value expires. The PEMC 226 may be configured to determine an availability status of the PEGC 224 based on the determination of whether a periodic update request is received from the PEGC 224.

[0079] In some embodiments, the PEMC 226 may be configured to determine the availability status of the PEGC 224 as unavailable within the PIN 210 upon determining that no periodic update request is received from the PEGC 224 before the PU timer value expires. The PEMC 226 may be configured to determine the availability status of the PEGC 224 as available within the PIN upon determining that no periodic update request is received from the PEGC 224 before the PU timer value expires. Thus, the PEMC 226 may determine that the PEGC 224 is unavailable based on the PU timer value.

[0080] When PEGC 224 is unavailable, PEGC 224 cannot serve as a gateway for connections among the individual PINEs 222a-222n and between the PINEs 222a-222n and the core network entity 240. Consequently, all PINEs 222a-222n may become disconnected from PIN 210, and PIN services provided or required by the PINEs 222a-222n may become unavailable.

[0081] When PEGC 224 is unavailable, an entity may be assigned as a new PEGC to provide the functionality of PEGC 224. Figure 2B 2 may include a PEMC 226 configured to determine an availability status of a PEGC 224 (i.e., a current PEGC) as unavailable within the PIN 210, as described above. The system 260D may include a PIN server 230 configured to select a first PINE (e.g., PINE 222a) from a plurality of PINEs 222a-222n to serve as a new PEGC for the PIN 210. The PIN server 230 may select the first PINE when the PEMC 226 determines that the availability status of the PEGC 224 is unavailable within the PIN 210.

[0082] In some embodiments, PIN server 230 may be configured to select a first PINE based on corresponding PINE capability information associated with each of the plurality of PINEs 222a-222n. In some embodiments, the PINE capability information may be provided by the corresponding PINE 222a-222n when joining PIN 210, when registering with core network entity 240, and / or based on user input indicating the capabilities of the corresponding PINE 222a-222n. In some embodiments, the PINE capability information may be stored at PEMC 226 and / or PIN server 230.

[0083] In some embodiments, PEMC 226 may be configured to send a modification message to PIN server 230 indicating a request to select a new PEGC for PIN 210. PIN server 230 may be configured to select the first PIN upon receiving the modification message. In some embodiments, the modification message may be associated with a protocol data unit (PDU) session modification procedure.

[0084] In some embodiments, PIN server 230 may be configured to send an allocation request to a first PINE (e.g., PINE 222a). The allocation request may indicate that the first PINE is allocated to serve as the new PEGC for PIN 210. PIN server 230 may be configured to receive an allocation response from the first PINE. The allocation response may indicate that the first PINE is accepted to serve as the new PEGC for PIN 210. PIN server 230 or PEMC 226 may be configured to send a notification message to multiple PINEs 222a-222n within PIN 210, indicating that the first PINE is allocated as the new PEGC for PIN 210.

[0085] In some embodiments, the notification message may include information associated with the new PEGC (i.e., the first PINE), such as a fully qualified domain name (FQDN), an IP address, a port number, a PEGC ID, etc. The notification message may also instruct other PINEs (e.g., if the first PINE is 222a, the other PINEs are 222b-222n) to move from the old PEGC 224 and connect to the new PEGC.

[0086] In an alternative embodiment, the PEMC 226 and / or the PIN server 230 may broadcast or instruct UEs external to the PIN 210 to join the PIN 210 to act as a new PEGC for the PIN 210 .

[0087] In some embodiments, a notification message may additionally be sent to the core network entity 240 to indicate the allocation of the new PEGC. It should be understood that although the notification message is described as being sent by the PIN server 230 or the PEMC 226, in alternative embodiments, the notification message may be sent by the core network entity 240 to the PEMC 226, the PIN server 230, and the PINEs 222a-222n.

[0088] It should be understood that although the selection of the new PEGC is described as being performed by the PIN server 230 , in alternative embodiments, the selection of the new PEGC may be performed by the PEMC 226 .

[0089] refer to Figure 4A , according to one embodiment of the present disclosure, an exemplary process is shown including a method 400 for determining the availability status of a PEGC 224. The method 400 may be performed at the system 260A. At step 402, the method 400 includes determining, by the PEMC 226, whether a periodic update request is received from the PEGC 224 before the PU timer value expires. At step 404, the method 400 includes determining, by the PEMC 226, the availability status of the PEGC 224 based on the determination of whether a periodic update request is received from the PEGC 224.

[0090] refer to Figure 4B , illustrates an exemplary process including a method 410 for assigning a new PEGC for a PIN 210 according to one embodiment of the present disclosure. The method 410 may be executed at the system 260D. At step 412, the method 410 includes determining, by the PEMC 226, that the availability status of the current PEGC within the PIN is unavailable. At step 414, the method 410 includes selecting, by the PIN server 230, a first PINE from among a plurality of PINEs as the new PEGC for the PIN when the availability status of the current PEGC is determined to be unavailable.

[0091] In some embodiments, method 410 may be performed as a continuation of method 400, i.e., first the unavailability of PEGC 224 may be determined, and then a new PEGC may be allocated thereafter. Figure 4A-4B The detailed description of each step is given in Figure 2A-2B The related description is covered in , and is omitted in this article for the sake of brevity.

[0092] refer to Figure 4C, a flow chart depicting the operation of a process 420 for determining the availability status of a PEGC 224 according to one embodiment of the present disclosure is shown. At step 421, a PIN join request (join request) is sent by the PEGC 224 to the PEMC 226, the join request indicating a request to join the PIN 210. At step 422, the PEMC 226 adds the PEGC 224 to the PIN 210 and assigns a PU timer value to the PEGC 224.

[0093] At step 423, the PEMC 226 determines that there is no data or signaling exchanged between the PEGC 224 and the PEMC 226. For example, the PEMC 226 may not have received any data from the PEGC 224. When it is determined that there is no data or signaling exchanged between the PEGC 224 and the PEMC 226, an inactivity timer is started at the PEMC 226. At step 424, the inactivity timer expires at the PEMC 226.

[0094] When the inactivity timer expires, corresponding timers at PEMC 226 and PEGC 224 are started at steps 425A and 425B. For example, PEMC 226 may send a trigger signal to PEGC 224 to start the corresponding timers. At step 425A, a PEGC implicit deregistration timer is started at PEMC 226. At step 425B, a PU timer may be started at PEGC 224. Both the PEGC implicit deregistration timer and the PU timer may correspond to the PU timer value.

[0095] At step 426, PEGC 224 may be disconnected from PIN 210. For example, PEGC 224 may be experiencing a loss of coverage and / or a loss of signal. As an example, PEGC 224 may be outside the coverage area of ​​PIN 210. When PEGC 224 is disconnected from PIN 210, PEGC 224 cannot send a PU update request to PEMC 226, as described at step 427.

[0096] At step 428A, the PEGC implicit deregistration timer may expire at the PEMC 226, and at step 428B, the PU timer may expire at the PEGC 224. Since the PEMC 226 did not receive a PU update request from the PEGC 224 before the PU timer value expired (i.e., before the corresponding timer expired), the PEMC 226 determines the availability status of the PEGC 224 as unavailable within the PIN 210. In some embodiments, the PEMC 226 may notify other entities (such as the PIN server 230 and the PINEs 222a-222n) about the unavailability of the PEGC 224.

[0097] In some embodiments (not shown), if the PEGC 224 remains connected to the PIN 210 at step 426, the PEGC 224 may send a PU update request to the PEMC 226 before the PU timer value expires at step 427. The PEMC 226 may receive the PU update request from the PEGC 224 and determine that the availability status of the PEGC 224 is available within the PIN 210.

[0098] It should be understood that while the determination of the availability status of PEGC 224 is described as being determined by PEMC 226, in alternative embodiments, any one of PINEs 222a-222n may determine the availability status of PEGC 224 in the manner described above.

[0099] In an alternative embodiment, the core network entity 240 may determine the availability status of the PEGC 224. When the PEGC 224 is disconnected from the PIN 210, such as due to power outage, low battery, switching to disconnected mode, etc., the PEGC 224 may enter a deregistered state (e.g., "5GMM_DEREGISTERED state") and send a deregistration request to the core network entity 240. The core network entity 240 may receive the deregistration request and determine that the PEGC 224 is not available within the PIN 210.

[0100] In another alternative embodiment, the core network entity 240 may determine PEGC unavailability based on expiration of a mobility reachability timer and / or an implicit deregistration time.

[0101] In yet another alternative embodiment, the core network entity 240 may determine the availability status of the PEGC 224 as unavailable based on whether the single network slice selection assistance information (S-NSSAI) dedicated to the PIN 210 is part of the NSSAI list that is not allowed or denied.

[0102] In yet another alternative embodiment, if the PEGC 224 switches and / or reselects from a first radio access technology (RAT) to a second RAT, the core network entity 240 may determine the availability status of the PEGC 224 as unavailable. For example, the PEGC 224 may switch from a 5G network to a long-term evolution (LTE) or wideband code division multiple access (WCDMA). In another example, the PEGC 224 may be registered to a roaming PLMN. The PEGC 224 may perform an inter-system change, and the core network entity 240 (e.g., AMF, SMF, UDM) may determine that the PEGC 224 is unavailable.

[0103] refer to Figure 4D , shows an operational flow diagram depicting a process 430 for allocating a new PEGC for a PIN 210, according to one embodiment of the present disclosure. At step 431, the PEMC 226 may determine that the PEGC 224 (i.e., the current PEGC) is not available within the PIN 210. At step 432, the PEMC 226 may notify the PIN server 230 of the unavailability of the PEGC 224.

[0104] At step 433, PIN server 230 may select a first PINE, such as PINE 222a, from among the plurality of PINEs 222a-222n as the new PEGC for PIN 210. This selection may be based on the PIN capabilities associated with the plurality of PINEs 222a-222n. At step 434, PIN server 230 may send an allocation request to the new PEGC, i.e., the first PINE. At step 435, PIN server 230 may receive an allocation response from the new PEGC. At step 436, PIN server 230 may send information associated with the new PEGC to PEMC 226 and other PINEs, such as PINEs 222b-222n. In some embodiments, the information associated with the new PEGC may be sent as an indication or may be broadcast.

[0105] In an alternative embodiment, steps 433-436 may be performed by PEMC 226. In some embodiments, PEMC 226 may send information associated with the new PEGC to other PINEs.

[0106] At step 437, the other PINEs may send corresponding join requests to the new PEGC. In some embodiments, the corresponding join requests may include the corresponding PINE ID assigned by the old PEGC 224. In some embodiments, the join request may be of type "reconnect" to indicate that the other PINEs are moving from the old PEGC to the new PEGC.

[0107] At step 438, the new PEGC may request details associated with the other PINEs from the PEMC 226 based on their corresponding PINE IDs. At step 439, the PEMC 226 may send the details associated with the PINEs to the new PEGC. At step 440, the new PEGC may send a join response to the other PINEs, indicating acceptance of the corresponding join request. In some embodiments, the join response may include a new PINE ID for the other PINEs. In some embodiments, the new PEGC may utilize the PINE ID assigned by the old PEGC 224 rather than assigning a new PINE ID. In some embodiments, the new PEGC may update details associated with the other PINEs at one or more of the PEMC 226, the PIN server 230, and the core network entity 240, for example, using a PDU session modification procedure.

[0108] As shown in Figures 2 and Figures 4A-4D As described, the unavailability of the PEGC 224 within the PIN 210 can be detected in a reliable manner. Connections will not be lost among entities within the PIN 210 because a new PEGC can be allocated when the unavailability of the PEGC 224 is detected.

[0109] PINE availability and pausing data transfers

[0110] Reference again Figure 2A-2B In some embodiments, each of the PINEs 222a-222n is associated with a timer corresponding to a periodic update (PU) timer value. The PU timer value is assigned to the PINEs 222a-222n by one of the PEGC 224, the PEMC 226, and the PIN server 230. In some embodiments, the PU timer value may be configured by a user associated with the entity 220 within the PIN 210. In some embodiments, the PU timer value may be preconfigured within the PINEs 222a-222n.

[0111] In some embodiments, the availability status of PINEs 222a-222n within PIN 210 may be determined. It should be understood that while details may be explained with reference to PINE 222n, these details are equally applicable to other PINEs. Figure 2B The system 260B shown may include a PEMC 226 configured to determine whether a periodic update request is received from a PINE 222n before the PU timer value expires. The PEMC 226 may be configured to determine an availability status of the PINE 222n based on the determination of whether a periodic update request is received from the PINE 222n.

[0112] In some embodiments, the PEMC 226 may be configured to determine the availability status of the PINE 222n as unavailable within the PIN 210 upon determining that no periodic update request is received from the PINE 222n before the PU timer value expires. The PEMC 226 may be configured to determine the availability status of the PINE 222n as available within the PIN upon determining that a periodic update request is received from the PINE 222n before the PU timer value expires. Thus, the PEMC 226 may determine that the PINE 222n is unavailable based on the PU timer value.

[0113] In some embodiments, when PINE 222n is unavailable, PEMC 226 may establish a non-3GPP access connection with PINE 222n and request PINE 222n to send a PIN join request before PINE 222n deregisters from PIN 210. PEMC 226 may start a second timer and wait for PINE 222n to send a PU update request upon expiration of the second timer. If no PU update request is received from PINE 222n, PINE 222n may deregister from PIN 210.

[0114] In some embodiments, PINE 222n can join a PIN on a non-3GPP access. PINE 222n may experience link loss with PEMC 226 on the non-3GPP access. When link loss is detected, corresponding timers at PEMC 226 and PINE 222n may be started, corresponding timers corresponding to the PU timer value. If the link is restored, the corresponding timers at PEMC 226 and PINE 222n are stopped, and PINE 222n is able to send packets to PEMC 226. If the link is not restored, PINE 222n cannot send a PU update request to PEMC 226, and PINE 222n is determined to be unavailable.

[0115] In some embodiments, when PINE 222n is unavailable, data transmission to PINE 222n may be suspended. PINE 222n may be unable to receive downlink data due to a lost or unreachable link. Due to the unavailability of PINE 222n, PEGC 224 may be configured to send a signal to core network entity 240, such as through a PDU session modification procedure, indicating the unavailability of PINE 222n and / or release PINE 222n from PIN 210. PINE 222n may be released from PIN 210 via PEMC 226. In some embodiments, PEGC 224 may send a signal to PEMC 226 to release PINE 222n. Furthermore, one of PEMC 226 and PEGC 224 may be configured to indicate the release of PINE 222n to core network entity 240 and / or PIN server 230, and in response, core network entity 240 and / or PIN server 230 may suspend data transmission to PINE 222n.

[0116] refer to Figure 5A , illustrates an exemplary process including a method 500 for determining the availability status of a PINE 222n according to one embodiment of the present disclosure. Method 400 may be performed at system 260B. At step 502, method 500 includes determining, by the PEMC 226, whether a periodic update request is received from the PINE 222n before the PU timer value expires. At step 504, method 500 includes determining, by the PEMC 226, the availability status of the PINE 222n based on the determination of whether a periodic update request is received from the PINE 222n.

[0117] refer to Figure 5B , shows an operational flow diagram depicting a process 510 for determining the availability status of a PINE 222n, according to one embodiment of the present disclosure. At step 511, the PINE 222n sends a PIN join request to the PEMC 226, indicating a request to join the PIN 210. The PEMC 226 adds the PINE 222n to the PIN 210 and assigns a PU timer value to the PINE 222n. In some embodiments, the PU timer value may be assigned to the PINE 222n by the PEGC 224 or the PIN server 230.

[0118] At step 512, PEMC 226 determines that no data or signaling has been exchanged between PINE 222n and PEMC 226. For example, PEMC 226 may not have received any data from PINE 222n. Upon determining that no data or signaling has been exchanged between PINE 222n and PEMC 226, an inactivity timer is started at PEMC 226. At step 513, the inactivity timer expires at PEMC 226.

[0119] When the inactivity timer expires, corresponding timers at PEMC 226 and PINE 222n are started at steps 514A and 514B. For example, PEMC 226 may send a trigger signal to PINE 222n to start the corresponding timers. At step 514A, the PINE implicit deregistration timer is started at PEMC 226. At step 514B, the PU timer may be started at PINE 222n. Both the PINE 222n implicit deregistration timer and the PU timer may correspond to the PU timer value.

[0120] At step 515, PINE 222n may disconnect from PIN 210. For example, PINE 222n may experience loss of coverage and / or loss of signal. As an example, PINE 222n may be outside the coverage area of ​​PIN 210. As another example, PINE 222n may lose a non-3GPP access signal, such as Bluetooth or WiFi access. As another example, PINE 222n may enter idle mode on the non-3GPP access, or the signaling connection may be released. When PINE 222n is disconnected from PIN 210, PINE 222n cannot send a PU update request to PEMC 226, as depicted at step 516.

[0121] At step 517, the PINE implicit deregistration timer may expire at the PEMC 226. The PU timer may also expire at the PINE 222n. Since the PEMC 226 did not receive a PU update request from the PINE 222n before the PU timer value expired (i.e., before the corresponding timer expired), the PEMC 226 determines the availability status of the PINE 222n as unavailable within the PIN 210. In some embodiments, the PEMC 226 may notify other entities (such as the PIN server 230 and the PEGC 224) about the unavailability of the PINE 222n.

[0122] In some embodiments (not shown), if the PINE 222n remains connected to the PIN 210 at step 515, the PINE 222n may send a PU update request to the PEMC 226 before the PU timer value expires at step 516. The PEMC 226 may receive the PU update request from the PINE 222n and determine that the availability status of the PINE 222n is available within the PIN 210.

[0123] It should be understood that although the determination of the availability status of PINE 222n is described as being determined by PEMC 226, in alternative embodiments, PEGC 224 may determine the availability status of PINE 222n, PIN server 230, or core network entity 240 in the manner described above.

[0124] refer to Figure 5C , illustrates an operational flow diagram depicting a process 520 for pausing data transmission to a PINE 222n, according to one embodiment of the present disclosure. At step 521, a PDU session may be established for a PIN 210 communicating with a core network entity 240. At step 522, the PIN server 230 may add the PINE 222n to the PIN 210. At step 523, the PINE 222n may experience a link loss or may be unreachable. Consequently, the connection between the PINE 222n and the PEMC 226 / PEGC 224 is lost.

[0125] At step 524, downlink data to be sent to PINE 222n may be received at PEGC 224 from PIN server 230. In some embodiments, the downlink data may be received using one or more of an IP address, port number, FQDN, and PINE-ID associated with PINE 222n. At step 525, PEGC 224 may signal a core network entity 240 (such as an SMF) indicating link loss for PINE 222n. At step 526, PEGC 224 may signal PEMC 226 to release PINE 222n from PIN 210, and PINE 222n may be released by PEMC 226. At step 527, one of PEMC 226 and PEGC 224 may indicate the release of PINE 222n to core network entity 240 and / or PIN server 230, and in response, core network entity 240 and / or PIN server 230 may suspend data transmission to PINE 222n.

[0126] As shown in Figures 2 and Figures 5A-5CAs described, unavailability of a PINE 222n within a PIN 210 can be detected in a reliable manner, and in case of unavailability, data transmission can be suspended.

[0127] PEMC availability and allocating new PEMCs

[0128] Reference again Figure 2A-2B In some embodiments, the PEMC 226 is associated with a timer corresponding to a PU timer value. The PU timer value is assigned to the PEMC 226 by one of the PEGC 224 and the PIN server 230. In some embodiments, the PU timer value may be configured by a user associated with the entity 220 within the PIN 210. In some embodiments, the PEMC 226 may be configured to send periodic update requests prior to the expiration of the PU timer value to indicate availability within the PIN 210. In some embodiments, the PU timer value may define the periodicity of the PU update requests to be sent by the PEMC 226 to the PIN server 230 to indicate the availability of the PEMC 226.

[0129] In some embodiments, the availability status of the PEMC 226 within the PIN 210 may be determined. Figure 2B The illustrated system 260C may include a PIN server 230 configured to determine whether a periodic update request is received from the PEMC before the PU timer value expires. The PIN server 230 may be configured to determine an availability status of the PEMC 226 based on the determination of whether a periodic update request is received from the PEMC 226.

[0130] In some embodiments, the PIN server 230 may be configured to determine the availability status of the PEMC 226 as unavailable within the PIN 210 upon determining that no periodic update request is received from the PEMC 226 before the PU timer value expires. The PIN server 230 may be configured to determine the availability status of the PEMC 226 as available within the PIN upon determining that no periodic update request is received from the PEMC 226 before the PU timer value expires. Therefore, the PIN server 230 may determine that the PEMC 226 is unavailable based on the PU timer value.

[0131] When the PEMC 226 is unavailable, the PEMC 226 cannot serve as a management entity for the PIN 210 to manage the PEGC 224 and the PINEs 222a-222n. Therefore, the PIN 210 may not function properly due to the unavailability of the PEMC 226. For example, functions such as adding a new PINE or terminating a PIN may not be performed.

[0132] When PEMC 226 is unavailable, an entity may be assigned as a new PEMC to provide the functionality of PEMC 226. Figure 2B In the system 260E shown in FIG. 2 , one of the PEGC 224 and the PIN server 230 may be configured to determine the availability status of the PEMC 226 (i.e., the current PEMC) as unavailable within the PIN 210, as described above. One of the PEGC 224 and the PIN server 230 may be configured to select a first PINE (e.g., PINE 222b) from among the plurality of PINEs 222a-222n as a new PEMC for the PIN 210. Upon determining that the availability status of the PEMC 226 is unavailable within the PIN 210, the PEGC 224 or the PIN server 230 may select the first PINE.

[0133] In some embodiments, the PEGC 224 or the PIN server 230 may be configured to select a first PINE based on corresponding PINE capability information associated with each of the plurality of PINEs 222a-222n. In some embodiments, the PINE capability information may be provided by the corresponding PINE 222a-222n when joining the PIN 210, when registering with the core network entity 240, and / or based on user input indicating the capabilities of the corresponding PINE 222a-222n.

[0134] In some embodiments, PEGC 224 or PIN server 230 may be configured to send an assignment request to a first PINE (e.g., PINE 222b). The assignment request may indicate that the first PINE is assigned as the new PEMC for PIN 210. PEGC 224 or PIN server 230 may be configured to receive an assignment response from the first PINE. The assignment response may indicate that the first PINE is accepted as the new PEMC for PIN 210. PIN server 230 or PEGC 224 may be configured to send a notification message to multiple PINEs 222a-222n within PIN 210, indicating that the first PINE is assigned as the new PEMC for PIN 210.

[0135] In some embodiments, the notification message may include information associated with the new PEMC (i.e., the first PINE), such as a fully qualified domain name (FQDN), an IP address, a port address, a PEMC ID, etc. The notification message may also instruct other PINEs (e.g., if the first PINE is 222b, the other PINEs are 222a and 222c-222n) to move from the old PEMC 226 and connect to the new PEMC.

[0136] In an alternative embodiment, the PEGC 224 and / or the PIN server 230 may broadcast or instruct UEs external to the PIN 210 to join the PIN 210 to act as a new PEMC for the PIN 210 .

[0137] In some embodiments, a notification message may additionally be sent to the core network entity 240 to indicate the assignment of the new PEMC. It should be understood that although the notification message is described as being sent by the PIN server 230 or the PEGC 224, in alternative embodiments, the notification message may be sent by the core network entity 240 to the PEGC 224, the PIN server 230, and the PINEs 222a-222n.

[0138] It should be understood that while selection of a new PEMC is described as being performed by PIN server 230, in alternative embodiments selection of a new PEGC may be performed by PEGC 224, core network entity 240, or any of a plurality of PINEs.

[0139] refer to Figure 6A , illustrates an exemplary process including a method 600 for determining the availability status of the PEMC 226 according to one embodiment of the present disclosure. The method 600 may be performed at the system 260C. At step 602, the method 600 includes determining, by the PIN server 230, whether a periodic update request is received from the PEMC 226 before the PU timer value expires. At step 604, the method 600 includes determining, by the PIN server 230, the availability status of the PEMC 226 based on the determination of whether a periodic update request is received from the PEMC 226.

[0140] refer to Figure 6B, illustrates an exemplary process including a method 610 for assigning a new PEMC for a PIN 210 according to one embodiment of the present disclosure. Method 610 may be executed at system 260E. At step 611, method 610 includes, by one of PEGC 224 and PIN server 230, determining the availability status of a current PEMC (PEMC 226) within the PIN as unavailable. At step 613, method 610 includes, upon determining the availability status of the current PEMC as unavailable, selecting, by one of the PEGC and PIN server, a first PINE from among a plurality of PINEs as a new PEMC for the PIN. At step 615, method 610 includes, by one of PEGC 224 and PIN server 230, sending an allocation request to the first PINE, the allocation request instructing the first PINE to be assigned as the new PEMC for the PIN. At step 617, method 610 includes, by one of PEGC 224 and PIN server 230, receiving an allocation response from the first PINE, the allocation response instructing the first PINE to be accepted as the new PEMC for the PIN. At step 619 , method 610 includes sending, by one of PEGC 224 and PIN server 230 , a notification message to the plurality of PINEs within the PIN, the notification message indicating that the first PINE is assigned as a new PEMC for PIN 210 .

[0141] In some embodiments, method 610 may be performed as a continuation of method 600, i.e., first the unavailability of PEMC 226 may be determined, and then a new PEMC may be allocated thereafter. Figure 6A-Figure 6B The detailed description of each step is given in Figure 2A-2B The related description is covered in , and is omitted in this article for the sake of brevity.

[0142] refer to Figure 6C , a flowchart depicting a process 620 for determining the availability status of a PEMC 226 according to one embodiment of the present disclosure is shown. At step 621, a PIN join request is sent by the PEMC 226 to the PIN server 230, indicating a request to join the PIN 210. At step 622, the PEMC 226 is added to the PIN 210, and a PU timer value is assigned to the PEMC 226. The PU timer value may be assigned by the PIN server 230 or the PEGC 224.

[0143] At step 623, PIN server 230 determines that no data or signaling has been exchanged between PIN server 230 and PEMC 226. For example, PIN server 230 may not have received any data from PEMC 226. When it is determined that no data or signaling has been exchanged between PIN server 230 and PEMC 226, an inactivity timer is started at PIN server 230. At step 624, the inactivity timer expires at PIN server 230.

[0144] When the inactivity timer expires, corresponding timers at PIN server 230 and PEGC 224 are started at steps 625A and 625B. For example, PIN server 230 may send a trigger signal to PEMC 226 to start the corresponding timers. At step 625A, the PEMC implicit deregistration timer is started at PIN server 230. At step 625B, the PU timer may be started at PEMC 226. Both the PEMC implicit deregistration timer and the PU timer may correspond to the PU timer value.

[0145] At step 626, PEMC 226 may be disconnected from PIN 210. For example, PEMC 226 may be experiencing a loss of coverage and / or a loss of signal. As an example, PEMC 226 may be outside the coverage area of ​​PIN 210. When PEMC 226 is disconnected from PIN 210, PEMC 226 cannot send a PU update request to PIN server 230, as described at step 627.

[0146] At step 628A, the PEGC implicit deregistration timer may expire at the PIN server 230, and at step 628B, the PU timer may expire at the PEMC 226. Since the PIN server 230 did not receive a PU update request from the PEMC 226 before the PU timer value expired (i.e., before the corresponding timer expired), the PIN server 230 determines the availability status of the PEMC 226 as unavailable within the PIN 210. In some embodiments, the PIN server 230 may notify other entities (such as the PEGC 224 and the PINEs 222a-222n) about the unavailability of the PEMC 226.

[0147] In some embodiments (not shown), if the PEMC 226 remains connected to the PIN 210 at step 626, the PEMC 226 may send a PU update request to the PIN server 230 before the PU timer value expires at step 627. The PIN server 230 may receive the PU update request from the PEMC 226 and determine that the availability status of the PEMC 226 is available within the PIN 210.

[0148] It should be understood that while the determination of the availability status of PEMC 226 is described as being determined by PIN server 230, in alternative embodiments, PEGC 224 or any of PINEs 222a-222n may determine the availability status of PEMC 226 in the manner described above.

[0149] In an alternative embodiment, the core network entity 240 may determine the availability state of the PEMC 226. When the PEMC 226 is disconnected from the PIN 210, such as due to a power outage, low battery, switching to disconnected mode, etc., the PEMC 226 may enter a deregistered state (e.g., a "5GMM_DEREGISTERED state") and send a deregistration request to the core network entity 240. The core network entity 240 may receive the deregistration request and determine that the PEMC 226 is not available within the PIN 210.

[0150] In another alternative embodiment, the core network entity 240 may determine PEMC unavailability based on expiration of a mobility reachability timer and / or an implicit deregistration time.

[0151] In yet another alternative embodiment, the core network entity 240 may determine the availability status of the PEMC 226 as unavailable based on whether the single network slice selection assistance information (S-NSSAI) dedicated to the PIN 210 is part of the NSSAI list that is not allowed or denied.

[0152] In yet another alternative embodiment, if the PEMC 226 switches and / or reselects from a first radio access technology (RAT) to a second RAT, the core network entity 240 may determine the availability status of the PEMC 226 as unavailable. For example, the PEMC 226 may switch from a 5G network to Long Term Evolution (LTE) or Wideband Code Division Multiple Access (WCDMA). In another example, the PEMC 226 may be registered to a roaming PLMN. The PEMC 226 may perform an inter-system change, and the core network entity 240 (e.g., AMF, SMF, UDM) may determine that the PEMC 226 is unavailable.

[0153] refer to Figure 6D, a flowchart depicting a process 630 for assigning a new PEMC for a PIN 210 is shown, according to one embodiment of the present disclosure. The PIN 210 is active, and the PEMC 226 serves as the management entity. At step 631, the PIN server 230 may determine that the PEMC 226 (i.e., the current PEMC) is unavailable within the PIN 210. At step 632, the PIN server 230 may notify the PEGC 224 of the unavailability of the PEMC 226, such as through a PDU Session Modification procedure.

[0154] At step 633, PIN server 230 may select a first PINE, such as PINE 222b, from among the plurality of PINEs 222a-222n as the new PEMC for PIN 210. This selection may be based on the PIN capabilities associated with the plurality of PINEs 222a-222n. At step 634, PIN server 230 may send an allocation request to the new PEMC, i.e., the first PINE. At step 635, PIN server 230 may receive an allocation response and a PIN information request from the new PEMC. At step 636, PIN server 230 may send PIN information to the new PEMC. At step 637, PIN server 230 may send information associated with the new PEMC to PEGC 224. In some embodiments, the information associated with the new PEMC may include the new PEMC's FQDN and IP address. At step 638, PEGC 224 may send information associated with the new PEMC to the other PINEs, such as PINEs 222a and 222c-222n. In some embodiments, information associated with the new PEGC may be sent as an indication or may be broadcast. At step 639, the PEGC 224 and other PINEs may connect to the new PEMC. In some embodiments, the new PEMC may update the PIN information with the PIN server 230 and / or the core network entity 240, such as by using a PDU session modification procedure.

[0155] As shown in Figures 2 and Figures 6A-6D As described above, the unavailability of the PEMC 226 within the PIN 210 can be detected in a reliable manner. Errors related to management among entities within the PIN 210 will not exist because a new PEMC can be allocated when the unavailability of the PEMC 226 is detected.

[0156] The present invention provides various technical advances based on the key features described above. The present invention provides systems and methods that allow for reliable detection of the availability status of entities within a PIN, such as the availability status of PEGC, PEMC, and PINE. Furthermore, in the event that a PEGC and PEMC are unavailable, a new PEGC and a new PEMC can be allocated, respectively, to avoid interruption of PIN-related functions. Furthermore, in the event that a PINE is unavailable, data transmission can be suspended for the unavailable PINE. Furthermore, in the event that a PINE is unavailable, when the PINE is lost or disconnected from the PIN, a list of available services can be updated at the PEMC, PEGC, and PIN server.

[0157] Although specific language has been used to describe this subject, it is not intended that any limitation will therefore be generated. It will be apparent to those skilled in the art that various modifications to the method can be made in order to implement the inventive concept taught herein. The accompanying drawings and the foregoing description provide examples of embodiments. It will be understood by those skilled in the art that one or more of the elements described can be well combined into a single functional element. Alternatively, some elements can be divided into multiple functional elements. Elements from one embodiment can be added to another embodiment.

Claims

1. A method performed by a Personal Internet of Things (IoT) network PIN Element (PEMC) entity with management capabilities in a wireless communication system, the method comprising: Obtaining a periodic timer for a PIN element PINE to indicate availability of the PINE; identifying whether a request associated with updating the periodic timer is received from the PINE before expiration of the periodic timer; Upon receiving the request, determining the availability of the PINE; as well as In the event that the request is not received, when the periodic timer expires, it is determined that the PINE is unavailable.

2. The method according to claim 1, further comprising: in, The periodicity of the request is defined by the value of the periodic timer.

3. A method performed by a personal Internet of Things (IoT) network PIN element (PINE) in a wireless communication system, the method comprising: obtaining a periodic timer associated with a PIN element with management capabilities PEMC to indicate the availability of said PINE, wherein the availability of the PINE is determined based on sending a request associated with updating the periodic timer to the PEMC before the periodic timer expires, When the periodic timer expires, without sending the request, the PINE is determined to be unavailable.

4. The method according to claim 3, in, The periodicity of the request is defined by the value of the periodic timer.

5. A personal Internet of Things (IoT) network PIN element (PEMC) entity with management capabilities in a wireless communication system, the PEMC entity comprising: Memory, and A processor, coupled to the memory, the processor being configured to: Obtaining a periodic timer for a PIN element PINE to indicate availability of the PINE; identifying whether a request associated with updating the periodic timer is received from the PINE before expiration of the periodic timer; Upon receiving the request, determining the availability of the PINE; as well as In the event that the request is not received, when the periodic timer expires, it is determined that the PINE is unavailable.

6. The PEMC entity according to claim 5, wherein: The periodicity of the request is defined by the value of the periodic timer.

7. A personal Internet of Things (IoT) network PIN element (PINE) in a wireless communication system, the PINE comprising: a memory configured to store data; as well as A processor, coupled to the memory, the processor being configured to: obtaining a periodic timer associated with a PIN element with management capabilities PEMC to indicate the availability of said PINE, wherein the availability of the PINE is determined based on sending a request associated with updating the periodic timer to the PEMC before the periodic timer expires, When the periodic timer expires, without sending the request, the PINE is determined to be unavailable.

8. The PINE according to claim 7, in, The periodicity of the request is defined by the value of the periodic timer.

Images