[go: up one dir, main page]

WO2025174156A1 - Améliorations apportées et se rapportant à des procédés de basculement d'états de dispositif ido - Google Patents

Améliorations apportées et se rapportant à des procédés de basculement d'états de dispositif ido

Info

Publication number
WO2025174156A1
WO2025174156A1 PCT/KR2025/002297 KR2025002297W WO2025174156A1 WO 2025174156 A1 WO2025174156 A1 WO 2025174156A1 KR 2025002297 W KR2025002297 W KR 2025002297W WO 2025174156 A1 WO2025174156 A1 WO 2025174156A1
Authority
WO
WIPO (PCT)
Prior art keywords
state
aiot
aiot device
network
mode
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.)
Pending
Application number
PCT/KR2025/002297
Other languages
English (en)
Inventor
Mahmoud Watfa
Chadi KHIRALLAH
David Gutierrez Estevez
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
Publication of WO2025174156A1 publication Critical patent/WO2025174156A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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/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
    • 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
    • H04L67/125—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
    • 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
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security

Definitions

  • 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
  • multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.
  • FD-MIMO Full Dimensional MIMO
  • OAM Organic Angular Momentum
  • RIS Reconfigurable Intelligent Surface
  • the present disclosure relates to providing a method for defining and managing AIoT device states and modes, enabling network-controlled and application function-triggered transitions without relying on traditional RRC states.
  • a method performed by an ambient internet of things (AIoT) device in a wireless communication system comprises: receiving, from a network, a request message indicating a target state of the AIoT device, wherein the target state indicating mode of operation for the AIoT device; transitioning a current state of the AIoT device to the target state of the AIoT device, based on the request message, in case that the current state of the AIoT device is different from the target state of the AIoT device; and transmitting, to the network, a response message indicating a result of an operation performed based on the request message.
  • AIoT ambient internet of things
  • an ambient internet of things (AIoT) device in a wireless communication system comprises: memory; transceiver; and at least one processor, coupled to the transceiver, configured to: receive, from a network, a request message indicating a target state of the AIoT device, wherein the target state indicating mode of operation for the AIoT device; transition a current state of the AIoT device to the target state of the AIoT device, based on the request message, in case that the current state of the AIoT device is different from the target state of the AIoT device; and transmit, to the network, a response message indicating a result of an operation performed based on the request message.
  • a request message indicating a target state of the AIoT device
  • the target state indicating mode of operation for the AIoT device transition a current state of the AIoT device to the target state of the AIoT device, based on the request message, in case that the current state of the AIoT device is different from the target state of the AIoT device.
  • the present disclosure relates to providing a method for defining and managing AIoT device states and modes, enabling network-controlled and application function-triggered transitions without relying on traditional RRC states.
  • Figure 1 shows an illustration of states or modes of operation according to an embodiment of the disclosure
  • Figure 2 shows a message flow illustrating an embodiment of the disclosure
  • Figure 3 is a block diagram illustrating a structure of a UE according to an embodiment of the disclosure.
  • the RAN SID reference is to be updated to RAN TR when available, and the meaning of no mobility is to be clarified by RAN.
  • Ambient IoT devices are a new type of reduced capabilities devices
  • the existing subscription model may not be suitable.
  • the UE which has not registered yet to the system is in a DEREGISTERED state, whereas after registration the UE is deemed to be in a REGISTERED state, noting that both of these states have substates and hence the UE can transition between substates accordingly as known.
  • the AIoT device may operate using different assumptions which is one of the main issues addresses by embodiments of the invention.
  • a problem in the art is that there is no current solutions available related to UE sates and how to switch between them. As indicated earlier, there have not been any state definitions and/or mode definitions for the AIoT device, and how the device transitions between them. However, it is clear that there may not be RRC states for use in an AIoT device.
  • UE User Equipment
  • AIoT Ambient Internet of Things
  • AF Application Function
  • the UE is operable in a VALIDATED mode comprising a plurality of sub-modes comprising REPORT-ONLY, RECEIVE-ONLY, REPORT-and-RECEIVE and RECEIVE-and-EVENT-REPORT.
  • the VALIDATE mode is entered following a security or validation procedure.
  • the UE enters an INVALIDATED mode after completing an AIoT procedure.
  • the UE enters a VOID state if instructed by the telecommunication network to stop operations.
  • the UE is only permitted to enter a particular mode of operation a predefined number of times, to change mode of operation a predefined number of times or to remain in a particular mode of operation for a predetermined duration, before entering a different defined mode of operation.
  • the different defined mode of operation is a VOID or SUSPEND mode.
  • the UE indicates to the network its supported modes of operation.
  • apparatus arranged to perform the method of the first aspect.
  • Embodiments herein do not rely on a particular message format especially on the interface between the RAN (e.g. gNB, eNB or NG-RAN, etc.) and the AIoT device, or between a UE and the AIoT device, or between the AIoT device and another AIoT device, or between multiple UEs, RAN entities and/or AIoT devices.
  • the RAN e.g. gNB, eNB or NG-RAN, etc.
  • the network may verify the capability of a given UE to be AIoT capable device.
  • new subscription information may be defined to indicate if the UE and/or the network can behave as set out. Furthermore, the UE may exchange any related capability indication to signal that the node in question can operate as described.
  • a UE state may also refer to a UE mode of operation or to a service operation that the UE can take.
  • the term state is not to be considered as a restriction that binds a UE to a particular state but rather as an example of how the UE may perform or behave in certain modes or conditions or based on service operations or expectations.
  • Embodiments set out new states and substates and/or modes for AIoT devices.
  • the name of the state and/or mode should not be regarded as a limitation but rather as an example and hence any name may be used. In other words, "mode” and “state” should not be interpreted in an overly strict manner.
  • the UE may report data either due to the UE needing to report data e.g. periodically, or based on a solicitation (or command, trigger, and/or indication, etc.) from the network.
  • this data reporting may not necessarily be due to a threshold being crossed (e.g. the data reporting may not necessarily be due to occurrence of an event).
  • ⁇ WRITE-ONLY in this substate, the UE may only be allowed (or permitted) to store data, e.g. data received from the network when the UE was previously in a READ-ONLY or READ-and/or-REPORT substate.
  • the UE in READ-ONLY substate may switch to WRITE-ONLY substate to store the received data.
  • the network may command the UE to perform this substate switch.
  • a new SUSPEND (sub-)state may be defined, where this may be a state on its own or a sub-state of any of the previous states.
  • the UE may enter this state when the network is revalidating or re-authorizing the UE or performing security procedures with the UE.
  • the UE should not perform any operation (e.g. read, write, transmit, receive, report, etc.) until the procedure is completed. If successful, the UE enters any of the above states (except the INVALIDATED state). If not successful, the UE enters the INVALIDATED state.
  • the UE may reset and/or delete all configurations and/or all (or part of) stored data, as a result of transition between different states defined above. For example, after performing a READ-ONLY or REPORT-ONLY the UE flushes (or deletes) or releases its stored information (e.g. data, configuration, etc.) and moves (or transit) to VOID state (and/or any other state). This UE behavior may be decided based on network configurations (or commands) and/or UE.
  • the UE may wait for the new configuration (or commands) from the network to transit between different states (or substates).
  • the network may configure the UE to only operate or exist in one state or operation modes, mentioned herein in this invention, e.g. READ-ONLY, WRITE-ONLY, etc.
  • the UE is only allowed to be read (or in READ-ONLY state) or to REPORT-ONLY state, a given number of times (e.g. X times, X is integer value, preconfigured by the network) before moving to VOID or SUSPEND state.
  • the UE may only be a WRITE-ONLY state a given number of times before it is moved to VOID or SUSPEND.
  • the UE is only allowed to be in (or enter) a given state (and/or mode), for a given time T (e.g. T is an integer value, preconfigured by the network). In another example, to be in a given state for a given time T before moving to another state or to be moved to VOID or SUSPEND.
  • the UE may be moved to another state or moved to VOID or SUSPEND.
  • the UE may be moved between two states, state A and state B, where state A and B may be different.
  • state A and B may be the same state.
  • the UE may only be allowed to toggle its state (or operation mode), mentioned herein, a given number of times (e.g. X times, X is an integer value, preconfigured by the network) before moving to VOID or SUSPEND state. Additionally, the UE may not be able to change (or toggle) its state after an X state changes.
  • the network may only allow the UE certain number of transitions of states, e.g. READ-ONLY to WRITE-ONLY.
  • state transition frequency can be defined or used e.g. the UE can only toggle its state K number of times (where K is an integer) within a certain time period T (where T represents any time unit).
  • Figure 1 shows an illustration of states or modes of operation according to an embodiment of the invention.
  • the dashed rectangle may indicate that the states REPORT-ONLY, RECEIVE-ONLY, RECEIVE-and/or-EVENT-REPORT, REPORT-and/or-RECEIVE are optionally sub-states of the VALIDATED state.
  • the UE can transition between these as shown with the double-ended arrows.
  • the UE may enter the SUSPEND state from any other state except the VOID state. Note that the SUSPEND state may be implemented as a sub-state of any other state.
  • the UE may transition between the NON-VALIDATED and the VALIDATED state (and optionally any of its sub-states) as shown by the double-ended arrows.
  • the network may request (or command) the AIoT device to enter the SUSPEND (or VOID or any other naming) state and terminate communication with this network (and/or other devices or UEs).
  • the network may be configured to inform the UE which state to start with, where this may be based on local policies or based on subscription information. As such, after validation of the UE, the network may send a message, which may be part of the validation process or the registration process, to inform the UE which state the UE should start operating with (or in).
  • the UE indicates the desired state, and the network may verify whether the UE can operate in that state or not based on the details above.
  • the UE may signal its preference to the network to change (or modify) its state, using (or through) UEAssistanceInformation (or a similar procedure or a procedure modified to be suitable for communication between the AIoT device and the network).
  • UEAssistanceInformation or a similar procedure or a procedure modified to be suitable for communication between the AIoT device and the network.
  • the AIoT device when configured to do so, it may signal to the network one or more of the following (e.g. through UEAssistanceInformation and/or another existing or newly defined procedure):
  • the network may have a corresponding state for each UE or for each UE context. Similar transitions can occur at the network side.
  • the establishment, modification and/or release of SRBs and/or DRB(s) between a AIoT device and gNB may be similar to existing methods for other type of UEs or different.
  • new type of SRBs and/or DRBs maybe introduced to carry the information between AIoT device and gNB.
  • AS security may not be applied to all SRBs and/or DRBs of the AIoT device.
  • encryption and/or integrity protection methods may not apply to AIoT SRBs and/or DRBs.
  • the UE may indicate that it is able to operate in accordance with the above, or the UE can operate in a set of states where a state may be associated with a well-known behavior.
  • the UE may indicate it supports receiving commands from the network to toggle its state.
  • the allowed states for an AIoT device and/or UE depend on the AIoT services and/or use cases that such AIoT device and/or UE is configured to support.
  • the potential states of an AIoT device and/or UE supporting an Inventory service only may include RECEIVE-and/or-EVENT-REPORT state but not necessarily READ-and WRITE related states
  • the potential states of an AIoT device or UE supporting a Command service may include READ-only, WRITE-only, and READ-and/or-WRITE.
  • the toggling of the state(s) of an AIoT device or UE may be also bound to the services it is configured to support.
  • the UE may operate in any of the states indicated above and/or in any state (or substate) which may not have been listed above. Regardless of the state name, embodiments provide a method by which the network can toggle the device state by issuing a command such that the UE will transition from one state to another.
  • the AF may negotiate or discover the NEF exposure services or capabilities for the 5GS (or any other system), where the NEF may indicate the support of toggling the states of IoT devices.
  • a network function (e.g. AMF, SMF, MME, etc.), which may be any function that is either existing or new, may subscribe to the UDM for getting events related to a requirement to toggle a UE state or mode of operation. Note that this may be done by a new NF that is potentially dedicated to handle or service AIoT devices. However, the details set out herein would still apply regardless of the NF. As such, the NF may be assumed to be an AMF for the purpose of describing embodiments.
  • step 7a the UE transitions into a new state based on the request received from the network. Note that step 7a may occur before the UE reports the result of the operation to the network in step 7. Note that this step assumes that the UE has successfully toggled its state or that it can successfully do so. Otherwise, if this is not possible then the UE does not change its state.
  • the NF e.g. AMF, RAN
  • the source NF e.g. the UDM.
  • the result may be that the UE has changed its state or not, or may report the UE's current state (which may be a new state e.g. in the case that the UE has changed its state, or any other state such as the state that the UE is in and that may not have changed based on the request from the network).
  • step 8a the NF (e.g. AMF, RAN) updates the UE's state or context to reflect the new UE state, based on the operation or result indicated by the UE. If the operation or result is successful, then the AMF and/or RAN can update the UE's state, otherwise the UE state is not updated and optionally a "failure to update" indication may be stored.
  • the NF e.g. AMF, RAN
  • the request may be to query the current state of the UE or group of UEs. As such all the steps can still be applied however the UE will reply to indicate its current state.
  • a NF may have this information and provide it to the AF via the NEF. This information may reside in the AMF, MME, UDM, or NEF, or SMF, etc.
  • the NEF may be configured to store the UE state or mode of operation and when queried the NEF can provide this information to the AF.
  • the NEF may either query the UDM or communicate directly (or via the UDM) with another NF (e.g. the AMF) in order to get this information and then reply.
  • any NF e.g. AMF
  • AMF may store this information and when queried the NF can provide it in a response.
  • the request may be to query resource availability in the UE, and hence the UE may respond to provide indications about its resources, where resources may be memory, power, etc
  • modes of operation may also be defined, although the corresponding states have not been listed earlier.
  • modes may include:
  • ⁇ Mobile Originated / Mobile Only mode in this mode, the UE is only expected/allowed to initiate communication for sending data and hence the UE is not expected to receive data. However, the UE may receive commands that may be needed to control the UE behavior.
  • ⁇ Device triggered device terminated mode in this mode the UE is triggered by the network to send or receive data and/or signaling.
  • the baseband processor 320 performs the function of converting between baseband signals and bit strings according to the physical layer protocol of the system. For example, the baseband processor 320 performs coding and modulation on the transmission bit string to generate complex symbols when transmitting data. In addition, when receiving data, the baseband processor 320 performs demodulation and decoding on the baseband signal provided from the RF processor 310 to recover the received bit string.
  • the baseband processor 320 performs coding and modulation on the transmission bit string to generate complex symbols, maps the complex symbols to subcarriers, performs inverse fast Fourier transform (IFFT) computation on the subcarriers, and inserts cyclic prefix (CP) to generate OFDM symbols when transmitting data.
  • IFFT inverse fast Fourier transform
  • CP cyclic prefix
  • the baseband processor 320 separates the baseband signal provided from the RF processor 310 into OFDM symbols, restores the signal mapped to the subcarriers by the fast Fourier transform (FFT) computation, and performs demodulation and decoding to restore the bit string.
  • FFT fast Fourier transform
  • the storage 330 stores basic programs for the operation of the UE, application programs, and data, such as configuration information. More particularly, the storage 330 may store information about the secondary access node with which the UE performs radio communication using the secondary radio access technology. Further, the storage 330 provides stored data in response to a request from the controller 340.
  • the controller 340 may include a multi-connection processor 342.
  • Figure 4 is a block diagram illustrating a constitution of a network entity according to an embodiment of the disclosure.
  • the baseband processor 420 performs the function of converting between baseband signals and bit strings according to the physical layer protocol of a first radio access technology. For example, the baseband processor 420 performs coding and modulation on the transmission bit string to generate complex symbols when transmitting data. The baseband processor 420 also performs demodulation and decoding on the baseband signals provided from the RF processor 410 to recover the received bit string when receiving data. For example, in the case of following an OFDM scheme, the baseband processor 420 performs coding and modulation on a transmission bit string to generate complex symbols, maps the complex symbols to subcarriers, performs IFFT computation on the subcarriers, and insert CP to generate OFDM symbols when transmitting data.
  • the baseband processor 420 separates the baseband signals provided from the RF processor 410 into OFDM symbols, recovers the signals mapped to the subcarriers by the FFT computation, and performs demodulation and decoding to recover the receiving bit strings when receiving data.
  • the baseband processor 420 and RF processor 410 are responsible for transmitting and receiving signals.
  • the baseband processor 420 and RF processor 410 may be referred to as a transmitter, a receiver, a transceiver, a communicator, or a wireless communicator.
  • the backhaul communicator 430 provides interfaces for communicating with other nodes in a network.
  • the backhaul communicator 430 converts a bit string to be transmitted from the main network entity to another node, for example, an auxiliary network entity, a core network, or the like into a physical signal, and converts a physical signal received from another node into a bit string.
  • the storage 440 stores basic programs, application programs, and data, such as configuration information for the operation of the main network entity. More particularly, the storage 440 may store information about bearers allocated to the connected UE, measurement results reported by the connected UE, and the like. The storage 440 may also store information as criteria for determining whether to enable or disable multi-connectivity of the UE. In addition, the storage 440 provides stored data in response to requests from the controller 450.
  • the controller 450 may include a multi-connection processor 452.
  • the controller 450 controls the overall operations of the network entity. For example, the controller 450 transmits and receives signals through the baseband processor 420 and RF processor 410, or through the backhaul communicator 430. The controller 450 also writes data to the storage 440 and reads data from the storage 440. To achieve this, the controller 450 may include at least one processor.
  • At least some of the example embodiments described herein may be constructed, partially or wholly, using dedicated special-purpose hardware.
  • Terms such as 'component', 'module' or 'unit' used herein may include, but are not limited to, a hardware device, such as circuitry in the form of discrete or integrated components, a Field Programmable Gate Array (FPGA) or Application Specific Integrated Circuit (ASIC), which performs certain tasks or provides the associated functionality.
  • FPGA Field Programmable Gate Array
  • ASIC Application Specific Integrated Circuit
  • the described elements may be configured to reside on a tangible, persistent, addressable storage medium and may be configured to execute on one or more processors.
  • These functional elements may in some embodiments include, by way of example, components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
  • components such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
  • components such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.

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)
  • Data Exchanges In Wide-Area Networks (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. La présente divulgation concerne un procédé mis en œuvre par un dispositif de l'Internet des objets (AIoT) ambiant dans un système de communication sans fil. Le procédé consiste à : recevoir, en provenance d'un réseau, un message de demande indiquant un état cible du dispositif AIoT, l'état cible indiquant un mode de fonctionnement pour le dispositif AIoT; effectuer la transition d'un état actuel du dispositif AIoT vers l'état cible du dispositif AIoT, sur la base du message de demande, dans le cas où l'état actuel du dispositif AIoT est différent de l'état cible du dispositif AIoT; et transmettre, au réseau, un message de réponse indiquant un résultat d'une opération effectuée sur la base du message de demande.
PCT/KR2025/002297 2024-02-16 2025-02-17 Améliorations apportées et se rapportant à des procédés de basculement d'états de dispositif ido Pending WO2025174156A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
GB2402248.5 2024-02-16
GB202402248 2024-02-16
GB2500605.7A GB2639746A (en) 2024-02-16 2025-01-16 Improvements in and relating to methods to toggling IoT device states
GB2500605.7 2025-01-16

Publications (1)

Publication Number Publication Date
WO2025174156A1 true WO2025174156A1 (fr) 2025-08-21

Family

ID=95559420

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2025/002297 Pending WO2025174156A1 (fr) 2024-02-16 2025-02-17 Améliorations apportées et se rapportant à des procédés de basculement d'états de dispositif ido

Country Status (2)

Country Link
GB (1) GB2639746A (fr)
WO (1) WO2025174156A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10826684B1 (en) * 2019-06-06 2020-11-03 Syniverse Technologies, Llc System and method of validating Internet of Things (IOT) devices
WO2021080035A1 (fr) * 2019-10-24 2021-04-29 엘지전자 주식회사 Dispositif ido et système de communication comprenant un dispositif ido
CN114449625A (zh) * 2020-10-31 2022-05-06 华为技术有限公司 模式切换方法及相关装置
US20230300199A1 (en) * 2017-09-06 2023-09-21 Convida Wireless, Llc Internet of things configurable event and action sequencing framework
US20230300753A1 (en) * 2020-11-18 2023-09-21 Samsung Electronics Co., Ltd. Electronic device and operating method therefor

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116056028A (zh) * 2021-10-28 2023-05-02 华为技术有限公司 通信方法和装置
CN116918318A (zh) * 2023-05-30 2023-10-20 北京小米移动软件有限公司 通信方法、装置、介质、通信设备及通信系统
WO2025054782A1 (fr) * 2023-09-11 2025-03-20 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Appareils et procédés d'enregistrement pour dispositif iot ambiant

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230300199A1 (en) * 2017-09-06 2023-09-21 Convida Wireless, Llc Internet of things configurable event and action sequencing framework
US10826684B1 (en) * 2019-06-06 2020-11-03 Syniverse Technologies, Llc System and method of validating Internet of Things (IOT) devices
WO2021080035A1 (fr) * 2019-10-24 2021-04-29 엘지전자 주식회사 Dispositif ido et système de communication comprenant un dispositif ido
CN114449625A (zh) * 2020-10-31 2022-05-06 华为技术有限公司 模式切换方法及相关装置
US20230300753A1 (en) * 2020-11-18 2023-09-21 Samsung Electronics Co., Ltd. Electronic device and operating method therefor

Also Published As

Publication number Publication date
GB2639746A (en) 2025-10-01
GB202500605D0 (en) 2025-03-05

Similar Documents

Publication Publication Date Title
WO2021215794A1 (fr) Procédé et système pour traiter une procédure de transfert dans un système à points d'émission et de réception multiples
AU2019355645A1 (en) Method and apparatus for providing information for vehicle communication services
WO2022235117A1 (fr) Procédé et appareil de prise en charge d'acquisition d'informations de système par un terminal distant de liaison latérale sur un relais de liaison latérale
WO2024029943A1 (fr) Procédé et appareil de mise à jour de politique d'ue sur la base d'un découpage en tranches de réseau
WO2022158807A1 (fr) Procédé et dispositif de gestion de la mobilité d'un mode de connexion d'un terminal distant par l'intermédiaire d'un terminal de relais dans un système de communication sans fil
WO2024091089A1 (fr) Procédés permettant d'effectuer une mobilité déclenchée par une couche inférieure dans un réseau sans fil
WO2023219344A1 (fr) Procédé et appareil permettant d'optimiser un ajout et un changement de cellule pscell conditionnelle dans des systèmes de communication sans fil
WO2025174156A1 (fr) Améliorations apportées et se rapportant à des procédés de basculement d'états de dispositif ido
WO2024101949A1 (fr) Connexion de nœud répéteur à un réseau
WO2023191438A1 (fr) Opérations pc5 de prose 5g sur la base de procédures de réseau
WO2023080748A1 (fr) Procédé et dispositif de prise en charge de découpage de réseau efficace dans un système de communication sans fil
WO2022245093A1 (fr) Procédé pour des améliorations apportées et se rapportant à des services de proximité
WO2023214773A1 (fr) Procédé et dispositif de prise en charge d'authentification de terminal dans un système de communication sans fil
WO2023090970A1 (fr) Procédé et appareil pour prendre en charge une pluralité de sim dans un système de communication mobile de prochaine génération
WO2023080751A1 (fr) Améliorations dans et relatives à prose
WO2022240191A1 (fr) Procédé et appareil de services de proximité dans un réseau de télécommunication
WO2025244429A1 (fr) Procédé et appareil destinés à des améliorations associées à un découpage en tranches dans un système de communication
WO2023229314A1 (fr) Procédé et appareil pour optimiser un accès aléatoire dans un système de communication sans fil
WO2024035135A1 (fr) Procédé et appareil de gestion de session de service informatique périphérique dans un système de communication sans fil
WO2024147661A1 (fr) Procédé et dispositif pour prendre en charge un changement de tranche de réseau en tenant compte d'un quota de tranches de réseau
WO2024210577A1 (fr) Procédé et appareil permettant de gérer des clés dans une double connectivité dans un système de communication sans fil
WO2024147642A1 (fr) Procédés et appareil pour mettre en œuvre une mobilité déclenchée par une couche inférieure dans un système de communication sans fil
WO2025014277A1 (fr) Procédé et appareil pour configurer et prendre en charge diverses versions pdcp dans une architecture ran divisée dans un système de communication
WO2025239665A1 (fr) Améliorations apportées à une attribution d'identité dans un réseau de télécommunications et se rapportant à celle-ci
WO2024101895A1 (fr) Procédé et dispositif d'autorisation basés sur une upf dans un système de communication sans fil

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: 25755298

Country of ref document: EP

Kind code of ref document: A1