WO2024237655A1 - Procédé et appareil de gestion d'un internet des objets personnel - Google Patents

Procédé et appareil de gestion d'un internet des objets personnel Download PDF

Info

Publication number
WO2024237655A1
WO2024237655A1 PCT/KR2024/006526 KR2024006526W WO2024237655A1 WO 2024237655 A1 WO2024237655 A1 WO 2024237655A1 KR 2024006526 W KR2024006526 W KR 2024006526W WO 2024237655 A1 WO2024237655 A1 WO 2024237655A1
Authority
WO
WIPO (PCT)
Prior art keywords
pine
pin
registration
request
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2024/006526
Other languages
English (en)
Inventor
Aman Agarwal
Lalith KUMAR
Sidhant JAIN
Arunprasath Ramamoorthy
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Priority to KR1020257038319A priority Critical patent/KR20260010394A/ko
Publication of WO2024237655A1 publication Critical patent/WO2024237655A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/009—Security arrangements; Authentication; Protecting privacy or anonymity specially adapted for networks, e.g. wireless sensor networks, ad-hoc networks, RFID networks or cloud networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/71—Hardware identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/72—Subscriber identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services

Definitions

  • the embodiments disclosed herein generally relate to the field of network, and more particularly, to a Personal IOT Network (PIN) Element Context and Validity/Lifetime Handling.
  • PIN Personal IOT Network
  • Wireless communication has been one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services exceeded five billion and continues to grow quickly.
  • the demand of wireless data traffic is rapidly increasing due to the growing popularity among consumers and businesses of smart phones and other mobile data devices, such as tablets, "note pad” computers, net books, eBook readers, and machine type of devices.
  • improvements in radio interface efficiency and coverage are of paramount importance.
  • 5G communication systems have been developed and are currently being deployed.
  • 5th generation (5G) or new radio (NR) mobile communications is recently gathering increased momentum with all the worldwide technical activities on the various candidate technologies from industry and academia.
  • the candidate enablers for the 5G/NR mobile communications include massive antenna technologies, from legacy cellular frequency bands up to high frequencies, to provide beamforming gain and support increased capacity, new waveform (e.g., a new radio access technology (RAT)) to flexibly accommodate various services/applications with different requirements, new multiple access schemes to support massive connections, and so on.
  • RAT new radio access technology
  • 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz.
  • 6G mobile communication technologies referred to as Beyond 5G systems
  • terahertz bands for example, 95GHz to 3THz bands
  • IIoT Industrial Internet of Things
  • IAB Integrated Access and Backhaul
  • DAPS Dual Active Protocol Stack
  • 5G baseline architecture for example, service based architecture or service based interface
  • NFV Network Functions Virtualization
  • SDN Software-Defined Networking
  • MEC Mobile Edge Computing
  • the principal object of the embodiments herein is to provide a method for handling Personal IOT Network (PIN) element (PINE) context and validity of a PIN element.
  • PIN Personal IOT Network
  • PINE Personal IOT Network
  • Another object of the embodiments herein is to handle a de-registration procedure.
  • Another object of the embodiments herein is to handle an update -registration procedure.
  • a method performed by a personal internet of things (IoT) network element (PINE) in a wireless communication system comprising: transmitting, to a PIN server, a request for a de-registration, the request including a security credential of the PINE received during authorization procedure with the PIN server; and receiving, from the PIN server, a response for the de-registration, the response including a status of the request for the de-registration.
  • IoT internet of things
  • PINE personal internet of things network element
  • a method performed by a personal internet of things (IoT) network (PIN) server in a wireless communication system comprising: receiving, from a PIN element (PINE), a request for a de-registration, the request including a security credential of the PINE received during authorization procedure with the PIN server; and transmitting, to the PINE, a response for the de-registration, the response including a status of the request for the de-registration.
  • IoT internet of things
  • PIN personal internet of things
  • a personal internet of things (IoT) network element (PINE) in a wireless communication system comprising: a transceiver; and a controller coupled with the transceiver and configured to: transmit, to a PIN server, a request for a de-registration, the request including a security credential of the PINE received during authorization procedure with the PIN server, receive, from the PIN server, a response for the de-registration, the response including a status of the request for the de-registration.
  • IoT internet of things
  • a personal internet of things (IoT) network (PIN) server in a wireless communication system comprising: a transceiver; and a controller coupled with the transceiver and configured to: receive, from a PIN element (PINE), a request for a de-registration, the request including a security credential of the PINE received during authorization procedure with the PIN server; and transmit, to the PINE, a response for the de-registration, the response including a status of the request for the de-registration.
  • IoT internet of things
  • FIG. 1 is sequence diagram illustrating a PINE/PEGC/PEMC gets disconnected/de-registered/deleted/loses authorization/released from PIN or PIN Server or 5GC/5GS, according to a prior art
  • FIG. 2 is a sequence diagram illustrating a 5GC and the PIN Server remove a PINE information from a context, according to the embodiments disclosed herein;
  • FIG. 3 is a sequence diagram illustrating the 5GC and the PIN Server remove the PINE information from the context when a PINE context timer is expired, according to the embodiments disclosed herein;
  • FIG. 4 is a sequence diagram illustrating the 5GC/5GS are stop the PINE context timer when a 5GC periodic update timer is expired, according to the embodiments disclosed herein;
  • FIG. 5 is a sequence diagram illustrating the PIN Server starts a PIN Element Context Periodic Update timer and periodically receive periodic updates from the 5GS/5GC about the PINE/PEGC/PEMC, according to the embodiments disclosed herein;
  • FIG. 6 is a sequence diagram illustrating a PINE sending de-registration request to PIN Server.
  • PIN server then indicates to 5GS/5GC to remove the PINE information from a context, according to the embodiments disclosed herein;
  • FIG. 7 is a sequence diagram illustration the PINE sending a PINE De-registration request to PIN Server directly, according to the embodiments disclosed herein;
  • FIG. 8 is a sequence diagram illustration the PINE sending a PINE De-registration request to PIN Server indirectly via PEMC, according to the embodiments disclosed herein;
  • FIG. 9 is a sequence diagram illustration the PINE sending a PINE De-registration request to PIN Server indirectly via PEMC along with the PIN Leave Request, according to the embodiments disclosed herein;
  • FIG. 10 is a sequence diagram illustration the PINE sending a PINE update registration request to PIN Server directly, according to the embodiments disclosed herein;
  • FIG. 11 shows various hardware components of the PINE, according to the embodiments as disclosed herein;
  • FIG. 12 shows various hardware components of the PIN server, according to the embodiments as disclosed herein;
  • FIG. 13 is a flow chart illustrating method, implemented by the PINE, for handling PINE context and validity of a PIN element based on a PINE de-registration request, according to the embodiments as disclosed herein;
  • FIG. 14 is a flow chart illustrating method, implemented by the PINE, for handling PINE context and validity of a PIN element based on a PINE update registration request, according to the embodiments as disclosed herein;
  • FIG. 15 is a flow chart illustrating method, implemented by the PIN server, for handling PINE context and validity of a PIN element based on the PINE de-registration request, according to the embodiments as disclosed herein;
  • FIG. 16 is a flow chart illustrating method, implemented by the PIN server, for handling PINE context and validity of a PIN element based on a PINE update registration request, according to the embodiments as disclosed herein.
  • FIG. 1 is sequence diagram illustrating a PINE (100A)/PEGC (100B)/PEMC (100C) gets disconnected/de-registered/deleted/loses authorization/released from PIN or PIN server (300) or 5GC/5GS (200), according to a prior art.
  • the PINE (100A) or a PEMC (100C) or a PEGC (100B) can be part of multiple PINs.
  • the PINE (100A)/PEGC (100B)/PEMC (100C) may register with the PIN server (300) via the PEGC (100B) or may register directly.
  • the PIN server (300) maintains a PIN profile or a PIN Client profile and the PINE (100A) profile with it for the PIN and PINE (100A)/PEGC (100B)/PEMC (100C) and optionally also maintain a PINE (100A)/PEGC (100B)/PEMC context in the PIN server (300).
  • the PINE (100A) which are part of the PIN may optionally get authorized/registered to access 5G (5GC or 5GS) by the PIN server (300) or 5GC/5GS (200) and register/authorize with 5GC/5GS (200) to get 5GC/5GS (200) services.
  • step 1-At step 3 when the PINE (100A) or PEMC (100C) or PEGC (100B), which is registered with 5GC/5GS (200), gets de-registered/loses authorization that is no more authorized to access the 5GS/5GC or the PIN server (300) from the 5GC/5GS (200), what should be the behaviour for that PINE (100A)/PEGC (100B)/PEMC (100C) at the PIN server (300) is not defined in the current conventional systems and needs to be handled.
  • PIN server (300) and/or 5GC/5GS (200) remove the PINE (100A)/PEGC (100B)/PEMC (100C) information from the PINE (100A)/UE/PIN context or from the PIN Profile or from the PIN client profile/information/context is not defined in the conventional system and needs to be handled.
  • Embodiments disclosed herein provide a method for handling Personal IOT Network (PIN) element (PINE) context and validity of a PIN element.
  • the method includes sending, by a PINE, a PINE de-registration request to a PIN server.
  • the PINE de-registration request includes a security credential and information.
  • the method includes receiving, by the PINE, a PINE de-registration response with a status of the PINE de-registration request from the PIN server based on the PINE de-registration request.
  • the PINE de-registration response indicates at least one of: the PINE is successfully de-registered, and the PINE is not successfully de-registered.
  • the PINE de-registration response indicates a failure response with cause of de-registration failure from the PIN server, when the PINE de-registration response indicates the PINE is not successfully de-registered.
  • the PINE sends the PINE de-registration request to the PIN server directly or via at least one of: a PIN Element with Management Capability (PEMC) and PIN Element with Gateway Capability (PEGC).
  • PEMC PIN Element with Management Capability
  • PEGC PIN Element with Gateway Capability
  • the PINE receives the PINE de-registration response with the status of the PINE de-registration request from the PIN server directly or via at least one of: a PEMC and a PEGC.
  • the PINE includes at least one of: a User Equipment (UE) that communicates within a PIN, a non-3GPP device that communicates within a PIN, a PEMC and a PEGC.
  • UE User Equipment
  • the information includes at least one of: a Generic Public Subscription Identifier (GPSI), a Medium Access Control (MAC) address, vendor name, a device description, a PIN element identifier (ID), a PIN client ID and a PINE address.
  • GPSI Generic Public Subscription Identifier
  • MAC Medium Access Control
  • ID PIN element identifier
  • PIN client ID PIN client ID
  • PINE address PINE address
  • Embodiments disclosed herein provide a method for handling PINE context and validity of a PIN element.
  • the method includes receiving, by a PIN server, a PINE de-registration request from at least one of a PINE, a PEMC and a PEGC entity.
  • the PINE de-registration request includes a security credential and information.
  • the method includes validating, by the PIN server, the PINE based on the PINE de-registration request.
  • the method includes determining, by the PIN server, that the PINE has an active registration with the PIN server.
  • the method includes sending, by the PIN server, a PINE de-registration response with a status of the PINE de-registration request to the PINE based on the determination.
  • the PINE de-registration response indicates at least one of: the PINE is successfully de-registered, and the PINE is not successfully de-registered.
  • the method includes sending, by the PIN server, a PINE de-registration response with a failure response with cause of de-registration failure to the PINE, when the PINE de-registration response indicates the PINE is not successfully de-registered.
  • the method includes deleting, by the PIN server, all configuration for the PINE, when the PINE de-registration response indicates the PINE is successfully de-registered.
  • Embodiments disclosed herein provide a method for handling PINE context and validity of the PIN element.
  • the method includes sending, by a PINE, a PINE update registration request to a PIN server.
  • the PINE update registration request includes a security credential and information.
  • the method includes receiving, by the PINE, a PINE update registration response with a status of the PINE update registration request from the PIN server based on the PINE update registration request.
  • the PINE update registration response indicates at least one of : the PINE update registration request is successful and the PINE update registration request is failed.
  • the PIN server provides a failure response with cause of update registration failure to the PINE, when the PINE update registration request is failed.
  • the PINE sends the PINE update registration request to the PIN server directly or via at least one of: a PEMC and a PEGC.
  • the PINE receives the PINE update registration response with the status of the PINE update registration request from the PIN server directly or via at least one of: a PEMC and a PEGC.
  • Embodiments disclosed herein provide a method for handling PINE context and validity of the PIN element.
  • the method includes receiving, by a PIN server, a PINE update registration request from a PINE.
  • the PINE update registration request includes a security credential and information.
  • the method includes validating, by the PIN server, the PINE based on the PINE update registration request.
  • the method includes determining, by the PIN server, that the PINE has an active registration with the PIN server.
  • the method includes sending, by the PIN server, a PINE update registration response with a status of the PINE update registration request to the PINE based on the determination.
  • the PINE update registration response indicates at least one of : the PINE update registration request is successful and the PINE update registration request is failed.
  • Embodiments disclosed herein provide a PINE for handling a PINE context and validity of the PIN element.
  • the PINE includes a PINE context and validity controller communicatively coupled to a memory and a processor.
  • the PINE context and validity controller is configured to send a PINE de-registration request to a PIN server.
  • the PINE de-registration request includes a security credential and information.
  • the PINE context and validity controller is configured to receive a PINE de-registration response with a status of the PINE de-registration request from the PIN server based on the PINE de-registration request.
  • the PINE de-registration response indicates at least one of: the PINE is successfully de-registered, and the PINE is not successfully de-registered.
  • the PINE context and validity controller is configured to receive a PINE de-registration response with a failure response with cause of de-registration failure from the PIN server, when the PINE de-registration response indicates the PINE is not successfully de-
  • Embodiments disclosed herein provide a PINE for handling a PINE context and validity of the PIN element.
  • the PINE includes a PINE context and validity controller communicatively coupled to a memory and a processor.
  • the PINE context and validity controller is configured to send a PINE update registration request to a PIN server.
  • the PINE update registration request includes a security credential and information.
  • the PINE context and validity controller is configured to receive a PINE update registration response with a status of the PINE update registration request from the PIN server based on the PINE update registration request.
  • the PINE update registration response indicates at least one of : the PINE update registration request is successful and the PINE update registration request is failed.
  • Embodiments disclosed herein provide a PIN server for handling PINE context and validity of the PIN element.
  • the PIN server includes a PINE context and validity controller communicatively coupled to a memory and a processor.
  • the PINE context and validity controller is configured to receive a PINE de-registration request from at least one of a PINE, a PEMC and a PEGC.
  • the PINE de-registration request includes a security credential and information.
  • the PINE context and validity controller is configured to validate the PINE based on the PINE de-registration request.
  • the PINE context and validity controller is configured to determine that the PINE has an active registration with the PIN server.
  • the PINE context and validity controller is configured to send a PINE de-registration response with a status of the PINE de-registration request to the PINE based on the determination.
  • the PINE de-registration response indicates at least one of: the PINE is successfully de-registered, and the PINE is not successfully de-registered.
  • the PINE context and validity controller is configured to send a PINE de-registration response with a failure response with cause of de-registration failure to the PINE, when the PINE de-registration response indicates the PINE is not successfully de-registered.
  • the PINE context and validity controller is configured to delete all configuration for the PINE, when the PINE de-registration response indicates the PINE is successfully de-registered
  • Embodiments disclosed herein provide a PIN server for handling PINE context and validity of the PIN element.
  • the PIN server includes a PINE context and validity controller communicatively coupled to a memory and a processor.
  • the PINE context and validity controller is configured to receive a PINE update registration request from a PINE.
  • the PINE update registration request includes a security credential and information.
  • the PINE context and validity controller is configured to validate the PINE based on the PINE update registration request.
  • the PINE context and validity controller is configured to determine that the PINE has an active registration with the PIN server.
  • the PINE context and validity controller is configured to send a PINE update registration response with a status of the PINE update registration request to the PINE based on the determination.
  • the PINE update registration response indicates at least one of : the PINE update registration request is successful and the PINE update registration request is failed.
  • circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.
  • circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block.
  • a processor e.g., one or more programmed microprocessors and associated circuitry
  • Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.
  • the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.
  • Embodiments disclosed herein provide a method for handling PINE context and validity of a PIN element.
  • the method includes sending, by a PINE, a PINE de-registration request to a PIN server.
  • the PINE de-registration request includes a security credential and information.
  • the method includes receiving, by the PINE, a PINE de-registration response with a status of the PINE de-registration request from the PIN server based on the PINE de-registration request.
  • the PINE de-registration response indicates at least one of: the PIN server deletes all configuration for the PINE when the PINE is successfully de-registered, and the PIN server gives failure response with cause of de-registration failure to the PINE, when the PINE is not successfully de-registered.
  • 5GS supports Personal IOT Network
  • PIN Personal IOT Network
  • 5GC Personal IOT Network
  • NB Narrow Band
  • WB Wide Band
  • WB-IOT WideBand Internet Of Things
  • LTE Long Term Evolution
  • AMF Access and Mobility Management Function
  • MME Mobility Management Entity
  • gnodeB Next generation Node-B
  • e-nodeB evolved-nodeB
  • HSS HSS
  • An example list of NAS messages can be, but not limited to, REGISTRATION REQUEST message; DEREGISTRATION REQUEST message; SERVICE REQUEST message; CONTROL PLANE SERVICE REQUEST; IDENTITY REQUEST; AUTHENTICATION REQUEST; AUTHENTICATION RESULT; AUTHENTICATION REJECT; REGISTRATION REJECT; DEREGISTRATION ACCEPT; SERVICE REJECT; SERVICE ACCEPT, and so on.
  • a Network (NW) used in the embodiment is explained using any 5G Core Network Function for e.g. AMF.
  • the network could be any 5G/EUTRAN Core Network Entities like AMF/SMF/ MME/UPF or the Network could be any 5G/EUTRAN RAN Entity like eNodeB (eNB) or gNodeB (gNB) or NG-RAN etc.
  • the messages used or indicated in the embodiment are shown as an example.
  • the messages could be any signalling messages between a UE and the Network Functions/Entities or between different Network functions/entities.
  • area/location/geographical area may refer to any of cell/cell ID, Tracking Area Code (TAC)/ Tracking Area Identity (TAI), Public Land Mobile Network (PLMN), Mobile Country Code (MCC)/ Mobile Network Code (MNC), Latitude/longitude, CAG cell or any geographical location/coordinate.
  • TAC Tracking Area Code
  • TAI Tracking Area Identity
  • PLMN Public Land Mobile Network
  • MCC Mobile Country Code
  • MNC Mobile Network Code
  • Latitude/longitude CAG cell or any geographical location/coordinate.
  • camp and register are used interchangeably and have the same meaning.
  • PINE, PIN Element and PIN-E are used interchangeably and have the same meaning.
  • the procedures and solutions defined in this embodiment can apply to any of the PINE or PEGC or PEMC or any PIN Element or Entity.
  • the examples explained in this embodiment are just used as an illustration.
  • the terms PIN profile, PIN context, PIN information are used interchangeably and have the same meaning.
  • PINE profile, PINE context, PINE information, PIN Client Profile, PIN client information, PIN client context are used interchangeably and have the same meaning.
  • Validity or lifetime or duration are used interchangeably and have the same meaning.
  • 5GC and 5GS are used interchangeably and have the same meaning.
  • NAS messages For the list of possible NAS messages please refer to 3GPP TS 24.501 or 3GPP TS 24.301, for list of AS messages please refer to 3GPP TS 38.331 or 3GPP TS 36.331.
  • the cause names in this embodiment are for illustration purpose and it can have any name.
  • the non-access stratum (NAS) messages and access stratum(AS) messages described in this embodiment is only for illustration purpose it can be any NAS or AS messages as per defined protocol between UE and AMF/MME or UE and gNB (NG-RAN/any RAN node)/ eNB.
  • Embodiments disclosed herein provide a PIN element context and validity/lifetime handling.
  • a PINE/PEMC/PEGC is a part of a PIN and optionally registered with a 5GC/5GS and a PIN server serving that the PIN.
  • PINE/PEGC/PEMC gets disconnected/de-registered/deleted/loses authorization/released from the PIN or PIN Server or if the complete PIN is deleted, PIN profile or PIN Client profile is updated/removed at PIN server accordingly.
  • the PIN server informs/indicates to the 5GC/5GS via any indication or message or any signalling that the PINE /PEGC/ PEMC has been disconnected/de-registered/deleted/loses authorization/released from the PIN or PIN Server, and 5GC/5GS (e.g. AMF) updates the PINE/PEGC/PEMC (UE) context with this information and may even delete the PINE/PEGC/PEMC (UE) context.
  • the PEGC/PEMC or the PINE itself informs the 5GC/5GS about leaving/ disconnected/de-registered/deleted/loses authorization/released from the PIN or the PIN Server, this indication can be sent directly by PEMC/PEGC or PINE or indirectly via PEGC/PEMC.
  • the PINE may, Deregister with 5GC (due to local reasons such as subscription over/expired or scheduled maintenance or scheduled Switch Off etc. or based on indication from PIN SERVER or 5GS) directly or via PEMC/PEGC.
  • the PINE leaving, deregistering the PIN may or may not include PIN IDs in the indication.
  • the events such as leaving/ disconnected/de-registered/deleted/loses authorization/released from the PIN/PIN Server is just shown as an example and it could be any event triggered by the PINE/PEMC/PEGC or by the PIN Server (such as Join/Delete/Create etc.).
  • the PINE/PEGC/PEMC may send deregistration request directly or via PEGC/PEMC to all the PIN servers which are handling the PINs which the said PINE is part of, when it gets disconnected/de-registered/deleted/loses authorization/released from 5GC or PIN server.
  • the PINE may include de-registration request in the PIN leave request itself.
  • the PEMC on receiving the PIN leave request may determine if the PINE needs to be de-registered as well. If the PINE has included a PINE de-registration request in the PIN leave request, the PEMC shall remove the PINE from the PIN and send the PINE de-registration request to the PIN server.
  • the PIN server on receiving PINE de-registration request from PINE directly or via PEGC/PEMC deregisters the PINE and indicates to 5GC/other PINs (PEGC/PEMC) including the same PINE, other PIN servers serving the PINs which have the said PINE as member.
  • the PINE may send de-registration request to PIN server with PIN leave request or before or after sending the PIN leave request.
  • the PEMC/PEGC handle the de-registration request received from PINE and forward the request to PIN server/5GC accordingly.
  • the PEGC/PEMC must remove the PINE from all the PINs when it receives de-registration indication for that PINE from the any of the PIN servers or 5GC.
  • the PEGC/PEMC shall include PIN IDs for PINs from which it wants to leave in the de-registration/leave request sent to the PIN server, if the PEGC/PEMC was acting as primary PEMC or optionally secondary PEMC or default PEGC or optionally backup PEGC so that the PIN server can assign other PEGC/PEMC as primary/secondary PEMC or default/backup PEGC for that PIN.
  • the PEGC/PEMC may or may not include PIN IDs for PINs from which it wants to leave in the de-registration/leave request sent to the PIN server, if the PEGC/PEMC was acting as primary PEMC or optionally secondary PEMC or default PEGC or optionally backup PEGC so that the PIN server can assign other PEGC/PEMC as primary/secondary PEMC or default/backup PEGC for that PIN.
  • the PEGC/PEMC may or may not include PIN IDs for PINs from which it wants to leave in the de-registration/leave request sent to the PIN server so that the PIN server can assign other PEGC/PEMC for that PIN.
  • the PIN server itself determines the PINs for which the requesting PEGC/PEMC was acting as PEGC (default PEGC or backup PEGC) or PEMC (either primary or secondary PEMC) for, and starts procedure to assign new PEGC/PEMC for the respective PINs.
  • the 5GC/5GS updates the PINE/PEGC/PEMC (UE) context/profile/information based on any event or trigger from the PIN Server or PINE/PEGC/PEMC (events such as, but not limited to, PINE/PEGC/PEMC Join/Delete/Leave/Register with/to the PIN or PIN server or such as PIN create/delete etc. or PINE subscription expiry at 5GC).
  • PINE/PEGC/PEMC UE context/profile/information based on any event or trigger from the PIN Server or PINE/PEGC/PEMC (events such as, but not limited to, PINE/PEGC/PEMC Join/Delete/Leave/Register with/to the PIN or PIN server or such as PIN create/delete etc. or PINE subscription expiry at 5GC).
  • the PIN server indicates to all PINs (PEGC/PEMC), served by this PIN Server and for which the PINE is part of, to remove the PINE from the PINs, when the PINE directly deregisters from the PIN Server, or such deregistration results from any indication from 5GC/PEMC/PEGC. If there is any signalling or procedure(For example: PINE management procedures like PIN Join/ PIN Leave or any service is requested) or request generated from this PINE towards the PIN or PEGC/PEMC or other PINEs, then the signalling or procedure or request or requested service shall be rejected with appropriate reject cause to indicate that the PINE is already de-registered and not a part of/not available in this Pin anymore.
  • the PIN server may indicate to other PIN servers serving any PIN which has the PINE about deregistration of PINE, so the other PIN servers may deregister the PINE from them.
  • the other PIN server may still keep the PINE registered even if the PINE is deregistered from a PIN Server (e.g. first PIN Server)
  • a PIN Server e.g. first PIN Server
  • the 5GC/5GS deletes the PINE/PEGC/PEMC (UE) context/profile/information based on any event (such as Subscription is expired at 5GC) or trigger from the PIN Server or PINE/PEGC/PEMC (events such as, but not limited to, PINE/PEGC/PEMC Join/Delete/Leave/Register with/to the PIN or PIN server or such as PIN create/delete etc.) if the PINE/PEGC/PEMC is not a part of any of the PIN anymore.
  • any event such as Subscription is expired at 5GC
  • PINE/PEGC/PEMC events such as, but not limited to, PINE/PEGC/PEMC Join/Delete/Leave/Register with/to the PIN or PIN server or such as PIN create/delete etc.
  • the 5GC/5GS may start a timer (such as PINE/PEGC/PEMC context delete wait timer) and wait for the timer to expire before deleting the PINE/PEGC/PEMC (UE) context/profile/information.
  • a timer such as PINE/PEGC/PEMC context delete wait timer
  • the timer would be stopped and PINE/PEGC/PEMC (UE) context/profile/information would not be deleted and would still be maintained at 5GC/5GS.
  • the 5GC/5GS maintains a validity or duration or lifetime of the PINE/PEGC/PEMC (UE) context/profile/information, which may be optionally different from the 5GC/5GS context of that PINE/PEGC/PEMC (UE). If the validity or duration or lifetime of the PINE/PEGC/PEMC (UE) context/profile/information expires, the 5GC/5GS (e.g. AMF) deletes the PINE/PEGC/PEMC (UE) context/profile/information.
  • the 5GC/5GS e.g. AMF
  • the timer related to the validity or duration or lifetime of the PINE/PEGC/PEMC (UE) context/profile/information is started/re-started/refreshed/reset when the PINE/PEGC/PEMC (UE) context/profile/information is first stored or optionally updated at the 5GC/5GS, during any of events (for example, during registration/authorization of PINE/PEGC/PEMC with the PIN Server or during any PINE/PEGC/PEMC joins/registers/becomes a part of a PIN/PIN Server etc. or due to any indication/signalling/message from the PIN server/PINE/PEMC/PEGC to update/store the context or reset/refresh/restart the timer).
  • MS Mobile Station The present document makes no distinction between MS and UE.
  • Satellite Constellation Group of satellites placed in orbit round the earth or moon or another planet in order to collect information or for communication.
  • Visited Public Land Mobile Network This is a Public Land Mobile Network (PLMN) different from a HPLMN (if the EHPLMN list is not present or is empty) or different from an EHPLMN (if the EHPLMN list is present).
  • PLMN Public Land Mobile Network
  • Allowable PLMN In case of a Mobile Station (MS) operating in a MS operation mode A or B, this is the PLMN which is not in a list of "forbidden PLMNs" in the MS. In the case of the MS operating in a MS operation mode C or an MS not supporting A/Gb mode and not supporting Iu mode, this is the PLMN which is not in the list of "forbidden PLMNs” and not in the list of "forbidden PLMNs for General Packet Radio Service (GPRS)" in the MS.
  • GPRS General Packet Radio Service
  • PLMN(s) in the given area which is/are broadcasting capability to provide wireless communication services to a User Equipment (UE).
  • UE User Equipment
  • the MS (ME if there is no SIM) has completed the cell selection/reselection process and has chosen a cell from which it plans to receive all available services. Note that the services may be limited, and that the PLMN or a Standalone Non-Public Networks (SNPN) may not be aware of existence of the MS (ME) within the chosen cell.
  • SNPN Standalone Non-Public Networks
  • EHPLMN Any of the PLMN entries contained in the Equivalent HPLMN list.
  • Equivalent HPLMN list To allow provision for multiple HPLMN codes, PLMN codes that are present within this list shall replace the HPLMN code derived from the IMSI for PLMN selection purposes. This list is stored on a Universal Subscriber Identification Module (USIM) and is known as the EHPLMN list. The EHPLMN list may also contain the HPLMN code derived from the IMSI. If the HPLMN code derived from the IMSI is not present in the EHPLMN list then it shall be treated as a Visited PLMN for PLMN selection purposes.
  • USIM Universal Subscriber Identification Module
  • MCC Mobile Country Code
  • MNC Mobile Network Code
  • Registered PLMN This is the PLMN on which certain LR (location registration which is also called as registration procedure) outcomes have occurred.
  • the RPLMN is the PLMN defined by the PLMN identity of the CN operator that has accepted the LR.
  • UPLMN PLMN/access technology combination in the "User Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order);
  • OPLMN PLMN/access technology combination in the "Operator Controlled PLMN Selector with Access Technology" data file in the SIM (in priority order) or stored in the ME (in priority order)
  • PIN Personal IoT Networks
  • PINs provide local connectivity between UEs and/or non-3GPP devices.
  • a Personal IoT Network (PIN) consists of PIN Elements(PINE) that communicate using PIN Direct Connection or direct network connection and is managed locally (using a PIN Element with Management Capability).
  • PIN Elements are UEs and/or non-3GPP devices which form part of the PIN.
  • PEMC PIN Element with Management Capability: PIN Element which have the capability to provide means for an authorised administrator to configure and manage the PIN.
  • PEGC PIN Element with Gateway Capability
  • PIN Elements with Gateway Capability provide means to PIN elements to register and access Fifth Generation (5G) network services. It can also help in communication between 2 PIN elements that are not within the range to use direct communication.
  • 5G Fifth Generation
  • ProSe ProSe (Proximity Services) is a D2D (Device-to-Device) technology that allows LTE devices to detect each other and to communicate directly.
  • D2D Device-to-Device
  • PIN-ID A unique identifier is associated with a PIN.
  • PINNF PIN Network Function
  • the PIN Network function is a core network entity responsible for assignment and management of PIN-ID.
  • PINAF PIN Application Function
  • the PIN Application function is a Network Function connected to 5G Core network via NEF (Network Exposure Function).
  • NEF Network Exposure Function
  • the PINAF is responsible for policy configuration and provisioning of PIN and its elements.
  • Access Control Information A set of information that assists the authorized PINE in a PIN to access 5GS network via PEGC, for example, the username or password.
  • a PIN enabler refers to overall functionality provided by the entities such as a PIN Client, a PIN Gateway Client, a PIN Management Client, and a PIN server in support of applications as per a PIN architecture.
  • a PIN management refers to the set of operations related to creation, modification, maintenance and removal of PIN.
  • PIN Profile A set of data and information about the PIN and PIN elements resides in the PIN.
  • Service Switch A mechanism to switch a service traffic flow between an Application server (AS) and the PINE to the application server and other PINE.
  • Example list of NAS messages which is not limited to:
  • 5GMM sublayer states in this embodiment is at least one of the below:
  • EMM sublayer states are at least one of the below:
  • RAT as defined in this embodiment is one of the following:-
  • PLMN selection as per 23.122 without RPLMN The MS selects and attempts registration on any PLMN/access technology combinations, if available and allowable, in the following order:
  • PLMN selection as per 23.122 with RPLMN The MS selects and attempts registration on any PLMN/access technology combinations, if available and allowable, in the following order:
  • FIGS. 2 through 16 where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.
  • FIG. 2 is a sequence diagram illustrating a 5GC and the PIN server (300) remove a PINE (100A) information from a context, according to the embodiments disclosed herein.
  • the PINE (100A)/PEGC (100B)/PEMC (100C) may de-register/lose connection/performs Periodic TAU/updates capabilities/de-authorizes with 5GC/5GS (200).
  • the PINE (100A)/PEGC (100B)/PEMC (100C) gets de-registered/loses connection from the 5GC/5GS (200)
  • the PINE (100A)/PEGC (100B)/PEMC (100C) informs the PEGC (100B)/PIN server (300)/PEMC (100C) about de-registering/losing connection from the 5GC/5GS (200).
  • the 5GC/5GS (200) may inform the PIN server (300)/PEGC (100B)/PEMC (100C) or any PIN entity whenever the registration/authorization status (for example, 5GC registration/authorization status changes from Registered/Authorized to De-registered/Unauthorized or the PINE (100A)/PEGC (100B)/PEMC (100C) is deregistered from the 5GS/5GC) of the PINE (100A)/PEMC (100C)/PEGC (100B) changes.
  • the registration/authorization status for example, 5GC registration/authorization status changes from Registered/Authorized to De-registered/Unauthorized or the PINE (100A)/PEGC (100B)/PEMC (100C) is deregistered from the 5GS/5GC) of the PINE (100A)/PEMC (100C)/PEGC (100B) changes.
  • the PIN server (300)/Other PIN elements may decide to either keep or remove the indicated or respective PINE (100A)/PEMC (100C)/PEGC (100B) in the PIN even though the PINE (100A)/PEGC (100B)/PEMC (100C) is deregistered/de-authorized from the 5GC/5GS (200).
  • the PIN server (300) may trigger de-registration of PINE (100A)/PEGC (100B)/PEMC (100C) based on local data timers/subscription/periodic update/lifetime/authorization expiry etc.) Or based on PINE (100A) data/indication (indication received from PINE (100A)) or based on 5GC indication.
  • PINE (100A) Profile Information or context or capabilities or PIN client profile information or PIN Profile Information changes due to change in 5GC/5GS (200) registration/authorization/capabilities status change of the PINE (100A)/PEGC (100B)/PEMC (100C)
  • PINE (100A) Profile Information or context or capabilities or PIN client profile information or PIN Profile Information is updated at PEGC (100B)/PEMC (100C) and/or PIN server (300).
  • the PINE (100A)/PEGC (100B)/PEMC (100C) which is part of multiple PINs may optionally have single registration with 5GC/5GS (200). If the PINE (100A)/PEMC (100C)/PEGC (100B) gets disconnected/de-registered/deleted/loses authorization/released from the PIN or PIN server (300) or if the complete PIN is deleted, the PINE (100A) Profile Information or context or capabilities or PIN client profile information or PIN Profile Information is updated at PEGC (100B)/PEMC (100C) and/or PIN server (300).
  • the PIN server (300) may delete the PINE (100A)/PEGC (100B)/PEMC (100C) (UE) context/profile/information based on any event or trigger from the PINE (100A)/PEGC (100B)/PEMC (100C) or 5GC/5GS (200) (events such as, but not limited to, PINE (100A)/PEGC (100B)/PEMC (100C) Join/Delete/Leave/Register with/to the PIN or PIN server (300) or such as PIN create/delete etc.) if the PINE (100A)/PEGC (100B)/PEMC (100C) is not a part of any of the PIN anymore.
  • the PINE/PEGC/PEMC is a part of a PIN, where the PINE/PEGC/PEMC is optionally, registered with 5GC/5GS and PIN Server.
  • the PINE/PEMC/PEGC de-registers with the 5GC.
  • 5GC / 5GS 200 sends the PINE disconnection indication to the PIN server 300.
  • the 5GC and the PIN Server remove the PINE information from context.
  • FIG. 3 is a sequence diagram illustrating the 5GC and the PIN server (300) remove the PINE (100A) information from the context when a PINE context timer is expired, according to the embodiments disclosed herein.
  • the PINE/PEGC/PEMC is a part of a PIN, where the PINE/PEGC/PEMC is optionally, registered with 5GC/5GS and PIN Server.
  • the PINE/PEMC/PEGC de-registers with the 5GC.
  • the PINE (100A)/PEGC (100B)/PEMC (100C) may perform periodic updates at PIN server (300) and/or 5GC/5GS (200) based on periodic timer assigned to it by PIN server (300)/5GC to indicate it is still part of PIN and maintain context at 5GC/5GS (200) and PIN server (300).
  • the PINE (100A) maintains a timer, say 'PIN server (300) periodic update timer' or it may be any other name. PINE (100A) starts/resets this timer after every message/signal sent to PIN server (300). The PINE (100A) performs a periodic update procedure, in which it sends a periodic update message (it may be any other name) to the PIN server (300) on expiry of this timer.
  • a timer say 'PIN server (300) periodic update timer' or it may be any other name.
  • the PIN server (300) also maintains a Timer, say 'PINE context timer' or it may be any other name (whose value is just greater than the PIN server (300) periodic update timer maintained at PINE (100A)) to maintain the context for PINE (100A) at PIN server (300). If the PIN server (300) does not receive Periodic update from the PINE (100A) before the expiry of PINE Context timer for that PINE (100A), it deletes the PINE context from the PIN profile and updates the 5GC and/or PEGC (100B)/PEMC (100C) with same information. Say Periodic timer (PIN server (300) periodic update timer or 5GC periodic update timer) was of 30 minutes.
  • a Timer say 'PINE context timer' or it may be any other name (whose value is just greater than the PIN server (300) periodic update timer maintained at PINE (100A)) to maintain the context for PINE (100A) at PIN server (300). If the PIN
  • PIN server (300)/PEMC (100C) can determine after 30 minutes that PINE (100A) is not available, or PIN sever/PEMC (100C) can start a new timer of duration "x" after which PIN server (300)/5GC determines PINE (100A) is not available.
  • FIG. 4 is a sequence diagram illustrating the 5GC/5GS (200) are stop the PINE context timer when a 5GC periodic update timer is expired, according to the embodiments disclosed herein.
  • the PINE (100A) maintains a timer, say '5GC periodic update timer' or it may be any other name. PINE (100A) starts/resets this timer after every message/signal sent to the 5GC. The PINE (100A) performs the periodic update procedure, in which it sends a periodic update message (it may be any other name) to the 5GC on expiry of this timer.
  • the 5GC also maintains a Timer, say 'PINE context timer' or it may be any other name (whose value is just greater than the 5GC periodic update timer maintained at PINE (100A)) to maintain the context for PINE (100A) at 5GC.
  • the 5GC does not receive Periodic update from the PINE (100A) before the expiry of PINE Context timer for that PINE (100A), it deletes the PINE context from the PIN profile and updates the PIN server (300) and/or PEGC (100B)/PEMC (100C) with same information.
  • FIG. 5 is a sequence diagram illustrating the PIN server (300) starts a PIN Element Context Periodic Update timer and periodically receive periodic updates from the 5GS/5GC about the PINE (100A)/PEGC (100B)/PEMC (100C), according to the embodiments disclosed herein.
  • the PIN server (300) can periodically update the 5GC with the PINE (100A)/PEGC (100B)/PEMC (100C) information indicating the PINE (100A)'s availability/current context/current registration/authorization/availability status.
  • the 5GC periodically updates the PIN server (300) with PINE (100A) information indicating the PINE (100A)'s availability/current context/current registration/authorization/availability status.
  • the PIN server (300) and/or 5GC/5GS (200) may start a timer, say a 'PIN Element Context Periodic Update timer' or it may be any other name.
  • PIN server (300) and/or 5GC/5GS (200) starts/resets/re-starts/refreshes this timer after every message/signal sent to PIN server (300) or 5GS/5GC.
  • the PIN server (300) and/or 5GC/5GS (200) performs the periodic update procedure, in which it sends a periodic update message(it may be any other name) to the PIN server (300) and/or 5GC/5GS (200) on expiry of this timer.
  • the PIN server (300) and/or 5GC/5GS (200) also maintains a Timer, say a 'PINE context delete wait timer' or it may be any other name (whose value is just greater than the PIN Element Context Periodic Update timer maintained at PIN server (300) and/or 5GC/5GS (200)) to maintain the context for PINE (100A) at PIN server (300) and/or 5GC/5GS (200).
  • a Timer say a 'PINE context delete wait timer' or it may be any other name (whose value is just greater than the PIN Element Context Periodic Update timer maintained at PIN server (300) and/or 5GC/5GS (200) to maintain the context for PINE (100A) at PIN server (300) and/or 5GC/5GS (200).
  • PINE Context delete wait timer for that PINE (100A)
  • PINE deletes the PINE (100A)/PEGC (100B)/PEMC (100C) (UE) context/profile/information from the PIN or PIN Client profile and updates the PIN server (300) and/or 5GC/5GS (200) and/or PEGC (100B)/PEMC (100C) with same information.
  • the PIN server (300) or 5GC respectively deletes the PINE (100A)/PEGC (100B)/PEMC (100C) (UE) context/profile/information for the PINE (100A) if they do not receive the periodic update from the 5GC or the PIN server (300) respectively for the respective timer duration (for example, the '5GC periodic update timer' or the 'PIN server (300) periodic update timer' or any other timer started between the 5GC/5GS (200) and the PIN server (300).
  • timer duration for example, the '5GC periodic update timer' or the 'PIN server (300) periodic update timer' or any other timer started between the 5GC/5GS (200) and the PIN server (300).
  • PIN server (300)/PEMC (100C) on determining by any of the methods explained earlier that PINE (100A) is deregistered/not available/unauthorized, PIN server (300)/PEMC (100C) triggers PINE (100A) removal from all the PINs the PINE (100A) is part of.
  • the PIN server (300) can start PIN Element Context Periodic Update timer and periodically receive periodic updates from the 5GS/5GC about the PINE (100A)/PEGC (100B)/PEMC (100C).
  • FIG. 6 is a sequence diagram illustrating the PINE (100A) sending de-registration request to the PIN server (300).
  • the PIN server (300) then indicates to the 5GS/5GC (200) to remove the PINE (100A) information from the context, according to the embodiments disclosed herein.
  • the PINE (100A)/PEGC (100B)/PEMC (100C) may de-register/lose connection/performs Periodic update/updates capabilities/de-authorizes with PIN server (300).
  • PINE (100A)/PEGC (100B)/PEMC (100C) gets de-registered/loses connection from the PIN server (300)
  • the PINE (100A)/PEGC (100B)/PEMC (100C) informs the PEGC (100B)/PIN server (300)/PEMC (100C) about de-registering/losing connection from the PIN server (300).
  • the PIN server (300) may inform the PEGC (100B)/PEMC (100C)/5GC or any PIN entity whenever the registration/authorization status (for example, registration/authorization status changes from Registered/Authorized to De-registered/Unauthorized) of the PINE (100A)/PEMC (100C)/PEGC (100B) changes.
  • the PIN server (300) may trigger de-registration of PINE (100A)/PEGC (100B)/PEMC (100C) based on local data timers/subscription/periodic update/lifetime/authorization expiry etc.) Based on PINE (100A) data/indication (indication received from PINE (100A)) or based on 5GC indication.
  • the PINE context is updated at the 5GC/5GS (200).
  • the PINE 100a/ the PEGC 100b/ the PEMC 100c is a part of the PIN, where the PINE 100a/ the PEGC 100b/ the PEMC 100c is, optionally, registered with the 5GC/5GS (200) and the PIN server (300).
  • the PINE (100a)/ PEGC (100b)/ PEMC (100c) de-registers with the PIN server (300).
  • the PIN server (300) sends the PINE disconnection indication to the 5GC/5GS (200).
  • the 5GC / 5GS (200) / PIN server (300) removes the PINE information from the context.
  • FIG. 7 is a sequence diagram illustration the PINE (100A) sending the PINE de-registration request to the PIN server (300) directly.
  • the PINE (100A) (including PINE (100A)/PEMC (100C)/PEGC (100B)) sends the PINE de-registration request to the PIN server (300).
  • the PINE de-registration request includes the security credentials of the PINE (100A) received during authorization procedure and also the request may include the GPSI, MAC address, vendor name, device description, PIN element ID/PIN client ID, PIN ID, PINE Address.
  • the PIN server (300) checks whether the UE identified by the GPSI has active registration with the PIN server (300).
  • the PIN server (300) responds to the PINE (100A) with PINE de-registration response which contains the status of the PINE de-registration request.
  • De-registration status indicates whether the PINE de-registration request was successful or not. Includes the cause of the failure if the de-registration fails. If the PINE (100A) is successfully de-registered, the PIN server (300) deletes all the configuration information it has related to the PIN element that is being de-registered. If the de-registration procedure fails, the PIN server (300) should give the failure response to indicates that indicates the cause of de-registration request failure.
  • FIG. 8 is a sequence diagram illustration the PINE (100A) sending a PINE de-registration request to PIN server (300) indirectly via the PEMC (100C) or the PEGC (100B).
  • the PINE (100A) (including PINE (100A)/PEMC (100C)/PEGC (100B)) sends the PINE de-registration Request to the PEMC (100C)/PEGC (100B).
  • the request may include the security credentials of the PINE (100A) received during authorization procedure and also the request may include the GPSI, MAC address, vendor name, device description, PIN element ID/PIN client ID, PIN ID, PINE Address.
  • the PEMC (100C)/PEGC (100B) sends the PINE de-registration request to PIN server (300).
  • the PIN server (300) checks whether the UE identified by the GPSI has active registration with the PIN server (300).
  • the PIN server (300) responds to the PEMC (100C)/PEGC (100B) with PINE de-registration response which contains the status of the PINE de-registration request. If the PINE (100A) is successfully de-registered, the PIN server (300) deletes all the configuration information it has related to the PIN element that is being de-registered. If the de-registration procedure fails, the PIN server (300) should give the failure response to indicates that indicates the cause of de-registration request failure.
  • the PEMC (100C)/PEGC (100B) sends the response received from PIN server (300) to the respective PIN, and updates the PIN Profile and PIN Client Profile accordingly.
  • Table 1 indicates the PINE de-registration request.
  • Table 1 describes information elements in the PINE de-registration request from the PINE (including PEMC, PEGC, PINEs) to the PIN server.
  • Table 2 indicates the PINE de-registration response.
  • Table 2 describes information elements in the PINE de-registration response from the PIN server to the PINE (including PEMC, PEGC, PINEs).
  • FIG. 9 is a sequence diagram illustration the PINE (100A) sending a PINE de-registration request to PIN server (300) indirectly via PEMC (100C) along with the PIN Leave Request ( or it can be any PINE (100A) initiated procedure or request.
  • the PINE (100A) (including PINE (100A)/PEMC (100C)/PEGC (100B)) sends a PINE leave and de-registration Request to the PEMC (100C)/PEGC (100B).
  • the request may include the security credentials of the PINE (100A) received during authorization procedure and also the request may include the GPSI, MAC address, vendor name, device description, PIN element ID/PIN client ID, PIN ID, PINE Address.
  • the PEMC (100C) authorizes the request sent by PINE (100A) and decides to de-register/not de-register the PINE (100A).
  • the PEMC (100C)/PEGC (100B) after successful authorization sends the PINE (100A) deregistration response to the requesting PINE (100A).
  • the PEMC (100C)/PEGC (100B) sends the PIN status update (or any other message) including PINE de-registration request to PIN server (300), indicating that the PINE (100A) has de-registered.
  • the PIN server (300) deletes all the configuration information it has related to the PIN element that is being de-registered.
  • the PEMC (100C) notifies all other PINE (100A)/PEGC (100B) about the PINE de-registration in the PIN Status notify message.
  • the PEMC (100C)/PEGC (100B)/PINE (100A)/PIN server (300) update the PIN Profile and PIN Client Profile accordingly.
  • FIG. 10 is a sequence diagram illustration the PINE (100A) sending a PINE update registration request to PIN server (300) directly.
  • the PINE (100A) (including PINE (100A)/PEMC (100C)/PEGC (100B)) sends the PINE update registration request to the PIN server (300).
  • the request includes the security credentials of the PINE (100A) received during authorization procedure and also the request may include the GPSI, MAC address, vendor name, device description, PIN element ID/PIN client ID, PINE Address.
  • the PIN server (300) checks whether the UE identified by the GPSI has active registration with the PIN server (300).
  • the PIN server (300) responds to the PINE (100A) with PINE update registration response which contains the status of the PINE update registration request. If the update registration procedure fails, the PIN server (300) should give the failure response to indicates that indicates the cause of update registration request failure.
  • the PINE (100A) may send a PINE update registration request to PIN server (300) indirectly via PEGC (100B) or PEMC (100C).
  • the PINE (100A) (including PINE (100A)/PEMC (100C)/PEGC (100B)) sends a PINE update registration request to the PEGC (100B)/PEMC (100C).
  • the request includes the security credentials of the PINE (100A) received during authorization procedure and also the request may include the GPSI, MAC address, vendor name, device description, PIN element ID/PIN client ID, PINE Address.
  • the PEGC (100B)/PEMC (100C) forwards the PINE update registration request to the PIN server (300).
  • the PIN server (300) checks whether the UE identified by the GPSI has active registration with the PIN server (300). The PIN server (300) responds to the PEGC (100B)/PEMC (100C) with PINE update registration response which contains the status of the PINE update registration request. If the update registration procedure fails, the PIN server (300) should give the failure response to indicates that indicates the cause of update registration request failure. The PEMC (100C)/PEGC (100B) forwards the PINE update registration response to the PINE (100A).
  • Table 3 indicates the PINE update registration request.
  • Table 3 describes information elements in the PINE update registration request from the PINE (including PEMC, PEGC, PINEs) to the PIN server.
  • Table 4 describes the PINE update registration response.
  • Table 4 describes information elements in the PINE de-registration response from the PIN server to the PINE (including PEMC, PEGC, PINEs).
  • FIG. 11 shows various hardware components of the PINE (100A), according to the embodiments as disclosed herein.
  • the PINE (100A) can be, for example, but not limited to the UE that communicates within the PIN, the non-3GPP device that communicates within the PIN, the PEMC (100C) and the PEGC (100B).
  • the PINE (100A) (100) includes a processor (110), a communicator (120), a memory (130) and a PINE context and validity controller (140).
  • the processor (110) is coupled with the communicator (120), the memory (130) and the PINE context and validity controller (140).
  • the PINE context and validity controller (140) sends the PINE de-registration request to the PIN server (300).
  • the PINE de-registration request includes the security credential and information.
  • the information comprises at least one of: the GPSI, the MAC address, the vendor's name, the device description, the PINE element ID, the PIN client ID and the PINE address.
  • the PINE context and validity controller (140) sends the PINE de-registration request to the PIN server (300) directly or via at least one of: the PEMC (100C) and the PEGC (100B).
  • the PINE context and validity controller (140) receives the PINE de-registration response with a status of the PINE de-registration request from the PIN server (300) directly or via at least one of: the PEMC (100C) and the PEGC (100B) based on the PINE de-registration request.
  • the PINE de-registration response indicates at least one of: the PIN server (300) deletes all configuration for the PINE (100A) when the PINE (100A) is successfully de-registered, and the PIN server (300) gives failure response with cause of de-registration failure to the PINE (100A), when the PINE (100A) is not successfully de-registered.
  • the PINE context and validity controller (140) sends the PINE update registration request to the PIN server (300).
  • the PINE update registration request includes the security credential and the information.
  • the PINE context and validity controller (140) receives the PINE update registration response with the status of the PINE update registration request from the PIN server (300) based on the PINE update registration request.
  • the PIN server (300) provides the failure response with cause of update registration failure to the PINE (100A), when the PINE update registration request is failed.
  • the PINE context and validity 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, hardwired circuits and the like, and may optionally be driven by firmware.
  • the processor (110) may include one or a plurality of processors.
  • the one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an AI-dedicated processor such as a neural processing unit (NPU).
  • the processor (110) may include multiple cores and is configured to execute the instructions stored in the memory (130).
  • the processor (110) is configured to execute instructions stored in the memory (130) and to perform various processes.
  • the communicator (120) is configured for communicating internally between internal hardware components and 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 non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.
  • EPROM electrically programmable memories
  • EEPROM electrically erasable and programmable
  • the memory (130) may, in some examples, be considered a non-transitory storage medium.
  • non-transitory may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted that the memory (130) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).
  • RAM Random Access Memory
  • the communicator (120) includes an electronic circuit specific to a standard that enables wired or wireless communication.
  • the communicator (120) is configured to communicate internally between internal hardware components of the UE and with external devices via one or more networks.
  • FIG. 11 shows various hardware components of the PINE (100A) but it is to be understood that other embodiments are not limited thereon.
  • the PINE (100A) may include less or more number of components.
  • the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention.
  • One or more components can be combined together to perform same or substantially similar function in the PINE (100A).
  • the solutions discussed in this embodiment is being illustrated by showing request (for e.g. de-registration request or update registration request) being triggered by PINE directly or indirectly via PEGC or PEMC to the PIN server as an example.
  • the request (for e.g. de-registration request or update registration request) can be initiated or exchanged between any set of entities in any order or combinations.
  • the entities include but not restricted to PINE, PEGC, PEMC, PIN Server, 5GC/5GC or any Network or Server Entity either directly or indirectly via any other entity.
  • FIG. 12 shows various hardware components of the PIN server (300), according to the embodiments as disclosed herein.
  • the PIN server (300) includes a processor (310), a communicator (320), a memory (330) and a PINE context and validity controller (340).
  • the processor (310) is coupled with the communicator (320), the memory (330) and the PINE context and validity controller (340).
  • the PINE context and validity controller (340) receives the PINE de-registration request from at least one of the PINE (100A), the PEMC (100C) and the PEGC (100B).
  • the PINE de-registration request includes the security credential and the information.
  • the PINE context and validity controller (340) validates the PINE (100A) based on the PINE de-registration request. Further, the PINE context and validity controller (340) determines that the PINE (100A) has the active registration with the PIN server (300). Further, the PINE context and validity controller (340) sends the PINE de-registration response with the status of the PINE de-registration request to the PINE (100A) based on the determination.
  • the PINE de-registration response indicates at least one of: the PIN server (300) deletes all configuration for the PINE (100A), when the PINE (100A) is successfully de-registered, and the PIN server (300) gives failure response with cause of de-registration failure to the PINE (100A), when the PINE (100A) is not successfully de-registered.
  • the PINE context and validity controller (340) receives the PINE update registration request from the PINE (100A).
  • the PINE update registration request includes the security credential and the information.
  • the PINE context and validity controller (340) validates the PINE (100A) based on the PINE update registration request.
  • the PINE context and validity controller (340) determines that the PINE (100A) has the active registration with the PIN server (300).
  • the PINE context and validity controller (340) sends the PINE update registration response with the status of the PINE update registration request to the PINE (100A) based on the determination.
  • the PINE context and validity controller (340) is implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.
  • the processor (310) may include one or a plurality of processors.
  • the one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and/or an AI-dedicated processor such as a neural processing unit (NPU).
  • the processor (310) may include multiple cores and is configured to execute the instructions stored in the memory (330).
  • the processor (310) is configured to execute instructions stored in the memory (330) and to perform various processes.
  • the communicator (320) is configured for communicating internally between internal hardware components and with external devices via one or more networks.
  • the memory (330) also stores instructions to be executed by the processor (310).
  • the memory (330) may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories.
  • EPROM electrically programmable memories
  • EEPROM electrically erasable and programmable
  • the memory (330) may, in some examples, be considered a non-transitory storage medium.
  • non-transitory may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term “non-transitory” should not be interpreted that the memory (330) is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache).
  • RAM Random Access Memory
  • the communicator (320) includes an electronic circuit specific to a standard that enables wired or wireless communication.
  • the communicator (330) is configured to communicate internally between internal hardware components of the UE and with external devices via one or more networks.
  • FIG. 12 shows various hardware components of the PIN server (300) but it is to be understood that other embodiments are not limited thereon.
  • the PIN server (300) may include less or more number of components.
  • the labels or names of the components are used only for illustrative purpose and does not limit the scope of the invention.
  • One or more components can be combined together to perform same or substantially similar function in the PIN server (300).
  • FIG. 13 is a flow chart (S1300) illustrating method, implemented by the PINE (100A), for handling PINE context and validity of the PIN element based on the PINE de-registration request, according to the embodiments as disclosed herein.
  • the operations (S1302 and S1304) are handled by the PINE context and validity controller (140).
  • the method includes sending the PINE de-registration request to the PIN server (300).
  • the PINE de-registration request includes the security credential and information.
  • the method includes receiving the PINE de-registration response with the status of the PINE de-registration request from the PIN server (300) based on the PINE de-registration request.
  • the PINE de-registration response indicates at least one of: the PINE (100A) is successfully de-registered, and t the PINE (100A) is not successfully de-registered.
  • the method includes receive a PINE de-registration response with a failure response with cause of de-registration failure from the PIN server, when the PINE de-registration response indicates the PINE is not successfully de-registered
  • FIG. 14 is a flow chart (S1400) illustrating method, implemented by the PINE (100A), for handling PINE context and validity of the PIN element based on the PINE update registration request, according to the embodiments as disclosed herein.
  • the operations (S1402 and S1404) are handled by the PINE context and validity controller (140).
  • the method includes sending the PINE update registration request to the PIN server (300).
  • the PINE update registration request includes the security credential and information.
  • the method includes receiving the PINE update registration response with the status of the PINE update registration request from the PIN server (300) based on the PINE update registration request where the PINE update registration response indicates at least one of : the PINE update registration request is successful and the PINE update registration request is failed.
  • FIG. 15 is a flow chart (S1500) illustrating method, implemented by the PIN server (300), for handling PINE context and validity of the PIN element based on the PINE de-registration request, according to the embodiments as disclosed herein.
  • the operations (S1502-S1512) are handled by the PINE context and validity controller (340).
  • the method includes receiving the PINE de-registration request from at least one of the PINE (100A), the PEMC (100C) and the PEGC (100B).
  • the PINE de-registration request includes the security credential and information.
  • the method includes validating the PINE (100A) based on the PINE de-registration request.
  • the method includes determining that the PINE (100A) has the active registration with the PIN server (300).
  • the method includes sending the PINE de-registration response with a status of the PINE de-registration request to the PINE (100A) based on the determination.
  • the PINE de-registration response indicates at least one of: the PINE (100A) is successfully de-registered, and the PINE (100A) is not successfully de-registered.
  • the method includes sending a PINE de-registration response with a PINE de-registration response with a failure response with cause of de-registration failure to the PINE, when the PINE de-registration response indicates the PINE is not successfully de-registered.
  • the method includes deleting all configuration for the PINE when the PINE de-registration response indicates the PINE is successfully de-registered.
  • FIG. 16 is a flow chart (S1600) illustrating method, implemented by the PIN server (300), for handling PINE context and validity of the PIN element based on the PINE update registration request, according to the embodiments as disclosed herein.
  • the operations (S1602-S1608) are handled by the PINE context and validity controller (340).
  • the method includes receiving the PINE update registration request from the PINE (100A).
  • the PINE update registration request includes the security credential and the information.
  • the method includes validating the PINE (100A) based on the PINE update registration request.
  • the method includes determining that the PINE (100A) has the active registration with the PIN server (300).
  • the method includes sending the PINE update registration response with a status of the PINE update registration request to the PINE (100A) based on the determination.
  • the PINE update registration response indicates at least one of : the PINE update registration request is successful and the PINE update registration request is failed.
  • a method for handling Personal IOT Network (PIN) element (PINE) context and validity of a PIN element comprising: sending, by a PINE (100A), a PINE de-registration request to a PIN server (300), wherein the PINE de-registration request comprises a security credential and information; receiving, by the PINE (100A), a PINE de-registration response with a status of the PINE de-registration request from the PIN server (300) based on the PINE de-registration request, wherein the PINE de-registration response indicates at least one of: the PINE (100A) is successfully de-registered, and the PINE (100A) is not successfully de-registered; and receiving, by the PINE (100A), a PINE de-registration response with a failure response with cause of de-registration failure from the PIN server (300), when the PINE de-registration response indicates the PINE (100A) is not successfully de-registered.
  • PIN Personal IOT Network
  • the PINE (100A) sends the PINE de-registration request to the PIN server (300) directly or via at least one of: a PIN Element with Management Capability (PEMC) (100C) and a PIN Element with Gateway Capability (PEGC) (100B).
  • PEMC PIN Element with Management Capability
  • PEGC PIN Element with Gateway Capability
  • the PINE (100A) receives the PINE de-registration response with the status of the PINE de-registration request from the PIN server (300) directly or via at least one of: a PEMC (100C) and a PEGC (100B).
  • the PINE (100A) comprises at least one of: a User Equipment (UE) that communicates within a PIN, a non-3GPP device that communicates within a PIN, a PEMC (100C) and a PEGC (100B), and wherein the information comprises at least one of: a Generic Public Subscription Identifier (GPSI), a Medium Access Control (MAC) address, vendor name, a device description, a PIN element identifier (ID), a PIN client ID and a PINE address.
  • GPSI Generic Public Subscription Identifier
  • MAC Medium Access Control
  • ID PIN element identifier
  • a method for handling Personal IOT Network (PIN) element (PINE) context and validity of a PIN element comprising: receiving, by a PIN server (300), a PINE de-registration request from at least one of a PINE (100A), a PEMC (100C) and a PEGC (100B), wherein the PINE de-registration request comprises a security credential and information; validating, by the PIN server (300), the PINE (100A) based on the PINE de-registration request; determining, by the PIN server (300), that the PINE (100A) has an active registration with the PIN server (300); sending, by the PIN server (300), a PINE de-registration response with a status of the PINE de-registration request to the PINE (100A) based on the determination, wherein the PINE de-registration response indicates at least one of: the PINE (100A) is successfully de-registered, and the PINE (100A) is not
  • the PIN server (300) receives the PINE de-registration request from the PINE (100A) directly or via at least one of: a PIN Element with Management Capability (PEMC) (100C)and a PIN Element with Gateway Capability (PEGC) (100B).
  • PEMC PIN Element with Management Capability
  • PEGC PIN Element with Gateway Capability
  • the PIN server (300) sends the PINE de-registration response with the status of the PINE de-registration request to the PINE (100A) directly or via at least one of: a PEMC (100C) and a PEGC (100B).
  • the PINE (100A) comprises at least one of: a UE that communicates within a PIN, a non-3GPP device that communicates within a PIN, a PEMC (100C) and a PEGC (100B), and wherein the information comprises at least one of: a GPSI, MAC Address, vendor Name, Device Description, PIN Element ID, PIN Client ID and a PINE address.
  • a method for handling Personal IOT Network (PIN) element (PINE) context and validity of the PIN element comprising: sending, by a PINE (100A), a PINE update registration request to a PIN server (300), wherein the PINE update registration request comprises a security credential and information; and receiving, by the PINE (100A), a PINE update registration response with a status of the PINE update registration request from the PIN server (300) based on the PINE update registration request, wherein the PINE update registration response indicates at least one of : the PINE (100A) update registration request is successful and the PINE (100A) update registration request is failed.
  • PIN Personal IOT Network
  • PIN server (300) provides a failure response with cause of update registration failure to the PINE (100A), when the PINE update registration request is failed.
  • the PINE (100A) sends the PINE update registration request to the PIN server (300) directly or via at least one of: a PIN Element with Management Capability (PEMC) (100C) and PIN Element with Gateway Capability (PEGC) (100B).
  • PEMC PIN Element with Management Capability
  • PEGC PIN Element with Gateway Capability
  • the PINE (100A) receives the PINE update registration response with the status of the PINE update registration request from the PIN server (300) directly or via at least one of: a PEMC (100C) and a PEGC (100B).
  • the PINE (100A) comprises at least one of: a UE that communicates within a PIN, a non-3GPP device that communicates within a PIN, a PEMC (100C) and a PEGC (100B), and wherein the information comprises at least one of: a GPSI, MAC Address, vendor Name, Device Description, PIN Element ID, PIN Client ID and a PINE address.
  • a method for handling Personal IOT Network (PIN) element (PINE) context and validity of the PIN element comprising: receiving, by a PIN server (300), a PINE update registration request from a PINE (100A), wherein the PINE update registration request comprises a security credential and information; validating, by the PIN server (300), the PINE (100A) based on the PINE update registration request; determining, by the PIN server (300), that the PINE (100A) has an active registration with the PIN server (300); and sending, by the PIN server (300), a PINE update registration response with a status of the PINE update registration request to the PINE (100A) based on the determination, wherein the PINE update registration response indicates at least one of : the PINE (100A) update registration request is successful and the PINE (100A) update registration request is failed.
  • PINE Personal IOT Network
  • the PIN server (300) provides a failure response with cause of update registration failure to the PINE (100A), when the PINE update registration request is failed.
  • the PIN server (300) receives the PINE update registration request from the PINE (100A) directly or via at least one of: a PIN Element with Management Capability (PEMC) (100C) and a PIN Element with Gateway Capability (PEGC) (100B).
  • PEMC PIN Element with Management Capability
  • PEGC PIN Element with Gateway Capability
  • the PIN server (300) sends the PINE update registration response with the status of the PINE update registration request to the PINE (100A) directly or via at least one of: a PEMC (100C) and a PEGC (100B).
  • the PINE (100A) comprises at least one of: a UE that communicates within a PIN, a non-3GPP device that communicates within a PIN, a PEMC (100C) and a PEGC (100B), and wherein the information comprises at least one of: a GPSI, MAC Address, vendor Name, Device Description, PIN Element ID, PIN Client ID and a PINE address.
  • a PINE (100A) for handling a PINE context and validity of the PIN element comprising: a memory (130); a processor (110); and a PINE context and validity controller (140), communicatively coupled to the memory (130) and the processor (110), configured to: send a PINE de-registration request to a PIN server (300), wherein the PINE de-registration request comprises a security credential and information; receive a PINE de-registration response with a status of the PINE de-registration request from the PIN server (300) based on the PINE de-registration request, wherein the PINE de-registration response indicates at least one of: the PINE (100A) is successfully de-registered, and the PINE (100A) is not successfully de-registered; and receive a PINE de-registration response with a failure response with cause of de-registration failure from the PIN server (300), when the PINE de-registration response indicates the PINE (100A)
  • a PINE (100A) for handling a PINE context and validity of the PIN element comprising: a memory (130); a processor (110); and a PINE context and validity controller (140), communicatively coupled to the memory (130) and the processor (110), configured to: send a PINE update registration request to a PIN server (300), wherein the PINE update registration request comprises a security credential and information; and receive a PINE update registration response with a status of the PINE update registration request from the PIN server (300) based on the PINE update registration request, wherein the PINE update registration response indicates at least one of : the PINE (100A) update registration request is successful and the PINE (100A) update registration request is failed.
  • a PIN server (300) for handling PINE context and validity of the PIN element comprising: a memory (330); a processor (310); and a PINE context and validity controller (340), communicatively coupled to the memory (330) and the processor (310), configured to: receive a PINE de-registration request from at least one of a PINE (100A), a PEMC (100C) and a PEGC (100B), wherein the PINE de-registration request comprises a security credential and information; validate the PINE (100A) based on the PINE de-registration request; determine that the PINE (100A) has an active registration with the PIN server (300); send a PINE de-registration response with a status of the PINE de-registration request to the PINE (100A) based on the determination, wherein the PINE de-registration response indicates at least one of: t the PINE (100A) is successfully de-registered, and the PINE (100A) is not
  • a PIN server (300) for handling PINE context and validity of the PIN element comprising: a memory (330); a processor (310); and a PINE context and validity controller (340), communicatively coupled to the memory (330) and the processor (310), configured to: receive a PINE update registration request from a PINE (100A), wherein the PINE update registration request comprises a security credential and information; validate the PINE (100A) based on the PINE update registration request; determine that the PINE (100A) has an active registration with the PIN server (300); and send a PINE update registration response with a status of the PINE update registration request to the PINE (100A) based on the determination, wherein the PINE update registration response indicates at least one of : the PINE (100A) update registration request is successful and the PINE (100A) update registration request is failed.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La divulgation concerne un système de communication 5G ou 6G destiné à prendre en charge un débit supérieur de transmission de données. L'invention concerne un procédé mis en œuvre par un élément de réseau de l'Internet des Objets (IdO) personnel (PINE) dans un système de communication sans fil, le procédé consistant à : émettre, vers un serveur PIN, une requête pour un désenregistrement, la requête comprenant un justificatif de sécurité du PINE reçu pendant une procédure d'autorisation avec le serveur PIN ; et recevoir, en provenance du serveur PIN, une réponse pour le désenregistrement, la réponse comprenant un état de la requête pour le désenregistrement.
PCT/KR2024/006526 2023-05-16 2024-05-14 Procédé et appareil de gestion d'un internet des objets personnel Ceased WO2024237655A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020257038319A KR20260010394A (ko) 2023-05-16 2024-05-14 개인용 사물 인터넷을 처리하기 위한 방법 및 장치

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202341034400 2023-05-16
IN202341034400 2024-04-30

Publications (1)

Publication Number Publication Date
WO2024237655A1 true WO2024237655A1 (fr) 2024-11-21

Family

ID=93520122

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2024/006526 Ceased WO2024237655A1 (fr) 2023-05-16 2024-05-14 Procédé et appareil de gestion d'un internet des objets personnel

Country Status (2)

Country Link
KR (1) KR20260010394A (fr)
WO (1) WO2024237655A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022271957A1 (fr) * 2021-06-25 2022-12-29 Idac Holdings, Inc. Découverte d'un réseau de l'internet des objets

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022271957A1 (fr) * 2021-06-25 2022-12-29 Idac Holdings, Inc. Découverte d'un réseau de l'internet des objets

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3 Generation Partnership Project; Technical Specification Group Services and System Aspects; Application layer support for Personal IoT Network; (Release 18)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.542, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V0.3.0, 10 May 2023 (2023-05-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 95, XP052408926 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Application layer support for Personal IoT Network; (Release 18)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.700-78, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V18.1.0, 31 March 2023 (2023-03-31), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 90, XP052284162 *
ARUNPRASATH RAMAMOORTHY, SAMSUNG: "Minor corrections in PIN registration procedures", 3GPP DRAFT; S6-231233; TYPE PCR; PINAPP, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG6, no. Online; 20230417 - 20230426, 11 April 2023 (2023-04-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052287516 *
HUAZHANG LYU, VIVO: "Editorial changes of PINAPP", 3GPP DRAFT; S6-231155; TYPE PCR; PINAPP, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG6, no. Online; 20230417 - 20230426, 10 April 2023 (2023-04-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052287440 *

Also Published As

Publication number Publication date
KR20260010394A (ko) 2026-01-20

Similar Documents

Publication Publication Date Title
WO2023214858A1 (fr) Procédés et appareils de gestion d'une liste de plmn
WO2024155091A1 (fr) Procédés et appareil d'enregistrement et de retransmission dans des déploiements de ntn
WO2019194633A1 (fr) Dispositif et procédé de gestion de politique d'un équipement utilisateur dans un système de communication sans fil
WO2023182793A1 (fr) Procédé et appareil de commande de hplmn pour couverture discontinue dans un réseau d'accès par satellite
WO2023146168A1 (fr) Procédé et appareil conçus pour assurer une synchronisation temporelle dans un système de communication sans fil
WO2024172623A1 (fr) Procédé et appareil de gestion de temporisateur d'inactivité lorsque des nssai sont changées de nssai à la demande en nssai normales
WO2024210560A1 (fr) Appareil et procédé de gestion de contexte associé à un ue pendant un scénario de couverture discontinue dans un système de communication sans fil
WO2024035128A1 (fr) Procédés et systèmes de gestion de réseaux fplmn pour mint
WO2023075299A1 (fr) Dispositif et procédé pour fournir un service d'appel d'urgence dans un réseau de communication sans fil
WO2025028916A1 (fr) Procédé et appareil de signalisation de rétablissement dans un système de communication sans fil
WO2024072112A1 (fr) Gestion de service d'itinérance en cas de catastrophe dans un réseau sans fil
WO2023182728A1 (fr) Procédé d'enregistrement de réseau pour transmission de trafic et dispositif prenant en charge celui-ci
WO2025095726A1 (fr) Gestion de communications par satellite à l'aide d'un service de stockage et de transfert avec un nœud de réseau intégrant un satellite
WO2024172556A1 (fr) Procédé et appareil pour des améliorations de l'accès par satellite et se rapportant à lui dans un système de télécommunication
WO2025071340A1 (fr) Procédé et dispositif pour ue multi-sim pour gérer des espaces de collision dans un système de communication mobile de prochaine génération
WO2024096458A1 (fr) Procédé et dispositif de mesure de qoe dans un système de communication sans fil
WO2024025282A1 (fr) Appareil et procédé de prise en charge de continuité de service de communication dans système de communication sans fil
WO2024237655A1 (fr) Procédé et appareil de gestion d'un internet des objets personnel
WO2025037916A1 (fr) Gestion d'un ue et de temporisateurs associés à l'ue pendant une période d'indisponibilité
WO2025174045A1 (fr) Procédé et appareil de gestion de mwab
WO2026019158A1 (fr) Procédés et systèmes de gestion de paramètres de satellite dans un système de communication de prochaine génération
WO2025211893A1 (fr) Procédé et appareil pour déterminer des informations d'indisponibilité d'un ue dans un système de communication sans fil
WO2025150995A1 (fr) Procédés et systèmes de gestion d'enregistrement périodique pour des services de magasin et de transfert
WO2025165159A1 (fr) Transfert d'autorisation d'un mwab-ue dans un réseau sans fil
WO2025174214A1 (fr) Procédé et mwab-gnb pour créer une interface mobile entre premier gnb, et entité de réseau voisine

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24807526

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE