WO2024145802A1 - Systems and methods for notifying synchronization status - Google Patents
Systems and methods for notifying synchronization status Download PDFInfo
- Publication number
- WO2024145802A1 WO2024145802A1 PCT/CN2023/070284 CN2023070284W WO2024145802A1 WO 2024145802 A1 WO2024145802 A1 WO 2024145802A1 CN 2023070284 W CN2023070284 W CN 2023070284W WO 2024145802 A1 WO2024145802 A1 WO 2024145802A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- wireless communication
- time
- threshold value
- amf
- message
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
- H04W56/001—Synchronization between nodes
Definitions
- the disclosure relates generally to wireless communications, including but not limited to systems and methods for notifying synchronization status.
- the standardization organization Third Generation Partnership Project (3GPP) is currently in the process of specifying a new Radio Interface called 5G New Radio (5G NR) as well as a Next Generation Packet Core Network (NG-CN or NGC) .
- the 5G NR will have three main components: a 5G Access Network (5G-AN) , a 5G Core Network (5GC) , and a User Equipment (UE) .
- 5G-AN 5G Access Network
- 5GC 5G Core Network
- UE User Equipment
- the elements of the 5GC also called Network Functions, have been simplified with some of them being software based, and some being hardware based, so that they could be adapted according to need.
- example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings.
- example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.
- a wireless communication device may receive a first message including a time sync status threshold value.
- the wireless communication device may receive a second message including a time status value.
- the wireless communication device may determine whether to switch itself to a connection state based on the time status value and the time sync status threshold value.
- the wireless communication device may receive the first message from an Access &Mobility Management Function (AMF) or a wireless communication node (e.g., a NG-RAN) .
- AMF Access &Mobility Management Function
- a wireless communication node e.g., a NG-RAN
- the AMF can be configured to create the time sync status threshold value.
- the first message can be a Non-Access Stratum (NAS) message sent directly from the AMF.
- the first message can be a Radio Resource Control (RRC) message sent from the wireless communication node.
- RRC Radio Resource Control
- the second message can be a new Information Element of a System Information Block (SIB) or an existing Information Element of ReferenceTimeInfo.
- a Time Sensitive Communication Synchronization Function (TSCTSF) or a Time Sensitive Networking-Adaptation Function (TSN-AF) can be configured to create the time sync status threshold value.
- the TSCTSN or TSN AF can be configured to send the time sync status threshold value to the AMF.
- the wireless communication node can be configured to create the time sync status threshold value.
- the wireless communication node can be configured to send the time sync status threshold value to the AMF.
- a network entity may send a message including a time sync status threshold value to a wireless communication device.
- the wireless communication device can be configured to determine whether to switch itself to a connection state based on the time sync status threshold value and a received time status value.
- the network entity can be an Access &Mobility Management Function (AMF) or a wireless communication node.
- AMF Access &Mobility Management Function
- the time status value can be received from the wireless communication node through broadcast.
- the time sync status threshold value can be created by one of: the AMF, the wireless communication node, a Time Sensitive Communication Synchronization Function (TSCTSF) , or a Time Sensitive Networking-Adaptation Function (TSN-AF) .
- TSCTSF Time Sensitive Communication Synchronization Function
- TSN-AF Time Sensitive Networking-Adaptation Function
- the AMF may receive the time sync status threshold value from Time Sensitive Communication Synchronization Function (TSCTSF) , a Time Sensitive Networking-Adaptation Function (TSN-AF) , or the wireless communication node.
- TSCTSF Time Sensitive Communication Synchronization Function
- TSN-AF Time Sensitive Networking-Adaptation Function
- the wireless communication node can be a NG-RAN.
- FIG. 1 illustrates an example cellular communication network in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure
- FIG. 2 illustrates a block diagram of an example base station and a user equipment device, in accordance with some embodiments of the present disclosure
- FIG. 3 illustrates an example implementation of a 5GS architecture, in accordance with some embodiments of the present disclosure
- FIG. 4 illustrates a sequence diagram illustrating a time synchronization, in accordance with some embodiments of the present disclosure
- FIG. 5 illustrates a sequence diagram illustrating a time synchronization, in accordance with some embodiments of the present disclosure
- FIG. 6 illustrates a sequence diagram illustrating a time synchronization, in accordance with some embodiments of the present disclosure
- FIG. 8 illustrates a sequence diagram illustrating a time synchronization, in accordance with some embodiments of the present disclosure
- FIG. 9 illustrates a sequence diagram illustrating a time synchronization, in accordance with some embodiments of the present disclosure.
- FIG. 10 illustrates a flow diagram of an example method for notifying synchronization status, in accordance with an embodiment of the present disclosure.
- FIG. 1 illustrates an example wireless communication network, and/or system, 100 in which techniques disclosed herein may be implemented, in accordance with an embodiment of the present disclosure.
- the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of things (NB-IoT) network, and is herein referred to as “network 100.
- NB-IoT narrowband Internet of things
- Such an example network 100 includes a base station 102 (hereinafter “BS 102” ; also referred to as wireless communication node) and a user equipment device 104 (hereinafter “UE 104” ; also referred to as wireless communication device) that can communicate with each other via a communication link 110 (e.g., a wireless communication channel) , and a cluster of cells 126, 130, 132, 134, 136, 138 and 140 overlaying a geographical area 101.
- the BS 102 and UE 104 are contained within a respective geographic boundary of cell 126.
- Each of the other cells 130, 132, 134, 136, 138 and 140 may include at least one base station operating at its allocated bandwidth to provide adequate radio coverage to its intended users.
- the BS 102 may operate at an allocated channel transmission bandwidth to provide adequate coverage to the UE 104.
- the BS 102 and the UE 104 may communicate via a downlink radio frame 118, and an uplink radio frame 124 respectively.
- Each radio frame 118/124 may be further divided into sub-frames 120/127 which may include data symbols 122/128.
- the BS 102 and UE 104 are described herein as non-limiting examples of “communication nodes, ” generally, which can practice the methods disclosed herein. Such communication nodes may be capable of wireless and/or wired communications, in accordance with various embodiments of the present solution.
- FIG. 2 illustrates a block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM/OFDMA signals) in accordance with some embodiments of the present solution.
- the system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein.
- system 200 can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment 100 of Figure 1, as described above.
- the System 200 generally includes a base station 202 (hereinafter “BS 202” ) and a user equipment device 204 (hereinafter “UE 204” ) .
- the BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with one another as necessary via a data communication bus 220.
- the UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with one another as necessary via a data communication bus 240.
- the BS 202 communicates with the UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for transmission of data as described herein.
- system 200 may further include any number of modules other than the modules shown in Figure 2.
- modules other than the modules shown in Figure 2.
- Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein may be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, or software can depend upon the particular application and design constraints imposed on the overall system. Those familiar with the concepts described herein may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as limiting the scope of the present disclosure
- the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 that includes a radio frequency (RF) transmitter and a RF receiver each comprising circuitry that is coupled to the antenna 232.
- a duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in time duplex fashion.
- the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 that includes a RF transmitter and a RF receiver each comprising circuity that is coupled to the antenna 212.
- a downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in time duplex fashion.
- the operations of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna 232 for reception of transmissions over the wireless transmission link 250 at the same time that the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operations of the two transceivers 210 and 230 may be coordinated in time such that the downlink receiver is coupled to the downlink antenna 212 for reception of transmissions over the wireless transmission link 250 at the same time that the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is close time synchronization with a minimal guard time between changes in duplex direction.
- the UE transceiver 230 and the base station transceiver 210 are configured to communicate via the wireless data communication link 250, and cooperate with a suitably configured RF antenna arrangement 212/232 that can support a particular wireless communication protocol and modulation scheme.
- the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as the Long Term Evolution (LTE) and emerging 5G standards, and the like. It is understood, however, that the present disclosure is not necessarily limited in application to a particular standard and associated protocols. Rather, the UE transceiver 230 and the base station transceiver 210 may be configured to support alternate, or additional, wireless data communication protocols, including future standards or variations thereof.
- LTE Long Term Evolution
- 5G 5G
- the BS 202 may be an evolved node B (eNB) , a serving eNB, a target eNB, a femto station, or a pico station, for example.
- eNB evolved node B
- the UE 204 may be embodied in various types of user devices such as a mobile phone, a smart phone, a personal digital assistant (PDA) , tablet, laptop computer, wearable computing device, etc.
- PDA personal digital assistant
- the policy control function may include at least one of following functionalities: an unified policy framework to govern network behavior, policy rules to control plane function (s) to enforce the policy rules, or a front end to access subscription information relevant for policy decisions in a user data repository (UDR) .
- an unified policy framework to govern network behavior
- policy rules to control plane function to enforce the policy rules
- a front end to access subscription information relevant for policy decisions in a user data repository (UDR) .
- the network exposure function may be deployed optionally for exchanging information between 5G core (5GC) and an external application function (AF) .
- NEF/AF may present the NEF and the AF for brief.
- a NG-RAN can provide precise time information to a UE via a 5G AS signaling (e.g., 5G access stratum time distribution (ASTI) ) .
- 5G AS signaling e.g., 5G access stratum time distribution (ASTI)
- a NG-RAN may send ReferenceTimeInfo to a UE in a system information block 9 (SIB9) or radio resource control (RRC) message.
- SIB9 system information block 9
- RRC radio resource control
- step 402 there can be three information elements (IEs) in the ReferenceTimeInfo.
- IEs information elements
- an AMF may receive a service operation which carries a 5G access stratum time distribution requirement for a UE.
- the AMF may receive the request from a UDM or a PCF.
- the AMF may create a time synchronization status threshold value for the UE (e.g., according to a time synchronization error budget for the UE in step 701, or according to a local configuration) .
- step 808 according to the time synchronization status threshold value received in the step 804/804a and current time status value, the IDLE or RRC inactive UE may initiate a RRC connection establishment procedure with the NG-RAN. This step can be similar with step 608.
- the AMF may send the time synchronization status threshold value to the UE.
- the AMF may send the time synchronization status threshold value via a NAS message (same with step 603 in FIG. 6) , or send the time synchronization status threshold value to a NG-RAN.
- the NG-RAN may send the time synchronization status threshold value to the UE via an AS (e.g., RRC) message (same with step 703/704 in FIG. 7) .
- AS e.g., RRC
- Step 907 ⁇ 911 can be the same with the step 605 ⁇ 609.
- a time synchronization status threshold value and a time status value may be in the same dimension, or different dimensions.
- the UE may compare the time synchronization status threshold value and the 5G time status value directly.
- the time synchronization status threshold value and a time status value may be in the different dimensions.
- the UE may formulate a conversion on time synchronization status threshold value and 5G time status value. After formulating the conversion, the UE may compare the time synchronization status threshold value and the 5G time status value.
- the AMF can be configured to create the time sync status threshold value.
- the first message can be a Non-Access Stratum (NAS) message sent directly from the AMF.
- the first message can be a Radio Resource Control (RRC) message sent from the wireless communication node.
- RRC Radio Resource Control
- the second message can be a new Information Element of a System Information Block (SIB) or an existing Information Element of ReferenceTimeInfo.
- the wireless communication node can be configured to create the time sync status threshold value.
- the wireless communication node can be configured to send the time sync status threshold value to the AMF.
- the AMF may receive the time sync status threshold value from Time Sensitive Communication Synchronization Function (TSCTSF) , a Time Sensitive Networking-Adaptation Function (TSN-AF) , or the wireless communication node.
- TSCTSF Time Sensitive Communication Synchronization Function
- TSN-AF Time Sensitive Networking-Adaptation Function
- the wireless communication node can be a NG-RAN.
- any reference to an element herein using a designation such as “first, “ “second, “ and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
- any of the various illustrative logical blocks, modules, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software” or a "software module) , or any combination of these techniques.
- firmware e.g., a digital implementation, an analog implementation, or a combination of the two
- firmware various forms of program or design code incorporating instructions
- software or a “software module”
- IC integrated circuit
- DSP digital signal processor
- ASIC application specific integrated circuit
- FPGA field programmable gate array
- the logical blocks, modules, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
- a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
- module refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various modules are described as discrete modules; however, as would be apparent to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs the associated functions according embodiments of the present solution.
- memory or other storage may be employed in embodiments of the present solution.
- memory or other storage may be employed in embodiments of the present solution.
- any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present solution.
- functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller.
- references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (17)
- A wireless communication method, comprising:receiving, by a wireless communication device, a first message including a time sync status threshold value;receiving, by the wireless communication device, a second message including a time status value; anddetermining, by the wireless communication device, whether to switch itself to a connection state based on the time status value and the time sync status threshold value.
- The wireless communication method of claim 1, further comprising:receiving, by the wireless communication device from an Access &Mobility Management Function (AMF) or a wireless communication node, the first message; andreceiving, by the wireless communication device from the wireless communication node, the second message through broadcast.
- The wireless communication method of claim 2, wherein the AMF is configured to create the time sync status threshold value.
- The wireless communication method of claim 2, wherein the first message is a Non-Access Stratum (NAS) message sent directly from the AMF.
- The wireless communication method of claim 2, wherein the first message is a Radio Resource Control (RRC) message sent from the wireless communication node.
- The wireless communication method of claim 2, wherein the second message is a new Information Element of a System Information Block (SIB) or an existing Information Element of ReferenceTimeInfo.
- The wireless communication method of claim 2, wherein a Time Sensitive Communication Synchronization Function (TSCTSF) or a Time Sensitive Networking- Adaptation Function (TSN-AF) is configured to create the time sync status threshold value.
- The wireless communication method of claim 7, wherein the TSCTSN or TSN AF is configured to send the time sync status threshold value to the AMF.
- The wireless communication method of claim 2, wherein the wireless communication node is configured to create the time sync status threshold value.
- The wireless communication method of claim 9, wherein the wireless communication node is configured to send the time sync status threshold value to the AMF.
- A wireless communication method, comprising:sending, by a network entity to a wireless communication device, a message including a time sync status threshold value;wherein the wireless communication device is configured to determine whether to switch itself to a connection state based on the time sync status threshold value and a received time status value.
- The wireless communication method of claim 11, wherein the network entity is an Access &Mobility Management Function (AMF) or a wireless communication node, and wherein the time status value is received from the wireless communication node through broadcast.
- The wireless communication method of claim 12, wherein the time sync status threshold value is created by one of: the AMF, the wireless communication node, a Time Sensitive Communication Synchronization Function (TSCTSF) , or a Time Sensitive Networking-Adaptation Function (TSN-AF) .
- The wireless communication method of claim 12 or 13, wherein the AMF receives the time sync status threshold value from Time Sensitive Communication Synchronization Function (TSCTSF) , a Time Sensitive Networking-Adaptation Function (TSN-AF) , or the wireless communication node.
- The wireless communication method of claim 11, wherein the wireless communication node is a NG-RAN.
- A wireless communications apparatus comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement a method recited in any of claims 1 to 15.
- A computer program product comprising a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement a method recited in any of claims 1 to 15.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202380088892.2A CN120419148A (en) | 2023-01-04 | 2023-01-04 | System and method for notifying synchronization status |
| PCT/CN2023/070284 WO2024145802A1 (en) | 2023-01-04 | 2023-01-04 | Systems and methods for notifying synchronization status |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2023/070284 WO2024145802A1 (en) | 2023-01-04 | 2023-01-04 | Systems and methods for notifying synchronization status |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2024145802A1 true WO2024145802A1 (en) | 2024-07-11 |
Family
ID=91803461
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2023/070284 Ceased WO2024145802A1 (en) | 2023-01-04 | 2023-01-04 | Systems and methods for notifying synchronization status |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN120419148A (en) |
| WO (1) | WO2024145802A1 (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102948225A (en) * | 2010-06-23 | 2013-02-27 | 摩托罗拉移动有限责任公司 | A method and device with dynamic dormancy |
| US20210243797A1 (en) * | 2020-02-04 | 2021-08-05 | Altiostar Networks, Inc. | Status messaging protocol |
| CN113438143A (en) * | 2021-06-23 | 2021-09-24 | 中国航空无线电电子研究所 | Communication gateway controller based on SOC |
-
2023
- 2023-01-04 CN CN202380088892.2A patent/CN120419148A/en active Pending
- 2023-01-04 WO PCT/CN2023/070284 patent/WO2024145802A1/en not_active Ceased
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102948225A (en) * | 2010-06-23 | 2013-02-27 | 摩托罗拉移动有限责任公司 | A method and device with dynamic dormancy |
| US20210243797A1 (en) * | 2020-02-04 | 2021-08-05 | Altiostar Networks, Inc. | Status messaging protocol |
| CN113438143A (en) * | 2021-06-23 | 2021-09-24 | 中国航空无线电电子研究所 | Communication gateway controller based on SOC |
Non-Patent Citations (4)
| Title |
|---|
| "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on timing resiliency and TSC and URLLC enhancements (Release 18)", 3GPP STANDARD; TECHNICAL REPORT; 3GPP TR 23.700-25, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, no. V18.0.0, 21 December 2022 (2022-12-21), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 105, XP052234753 * |
| CHUNLI WU, NOKIA, NOKIA SHANGHAI BELL: "Discussion on SA2 LS on Time Synchronization Status notification towards UE(s)", 3GPP DRAFT; R2-2211777; TYPE DISCUSSION; FS_5TRS_URLLC, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 2, no. Toulouse, FR; 20221114 - 20221118, 4 November 2022 (2022-11-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052215881 * |
| TAO CAI, HUAWEI, HISILICON: "Discussion on Time Synchronization Status notification towards UE(s)", 3GPP DRAFT; R2-2211559; TYPE DISCUSSION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 2, no. Toulouse, FR; 20221114 - 20221118, 4 November 2022 (2022-11-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052215665 * |
| TING LU, ZTE CORPORATION, SANECHIPS, CHINA SOUTHERN POWER GRID CO., LTD: "Consideration on Time Synchronization Status notification towards UE(s)", 3GPP DRAFT; R2-2211994; TYPE DISCUSSION; NR_IIOT_URLLC_ENH-CORE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. 3GPP RAN 2, no. Toulouse, FR; 20221114 - 20221118, 4 November 2022 (2022-11-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052216082 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN120419148A (en) | 2025-08-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US12238607B2 (en) | Wireless communication method, terminal device, and network device | |
| JP7789053B2 (en) | Base Stations and Transmitting/Receiving Devices | |
| US12452822B2 (en) | Positioning procedures for user equipments in inactive state | |
| JP7796723B2 (en) | Transceiver device, network entity, and base station | |
| CN113261340A (en) | Information transmission method, terminal equipment, base station and core network equipment | |
| US20240188157A1 (en) | Systems and methods for establishing shared n3 tunnel | |
| WO2024145802A1 (en) | Systems and methods for notifying synchronization status | |
| CN119384840A (en) | System and method for configuring unmanned aerial vehicle (UAV) services between and within systems using cross-standard radio access technologies (RATs) | |
| CN116506837A (en) | A method and device for interoperability between systems | |
| WO2025156460A1 (en) | Systems and methods for energy state control | |
| WO2025156483A1 (en) | Systems and methods for performing mode 2 sidelink communication | |
| WO2026065018A1 (en) | Systems and methods for communication in ambient internet of things service | |
| WO2024230037A1 (en) | Systems and methods for session management | |
| RU2805981C1 (en) | Wireless communication method, terminal device and network device | |
| WO2025091480A1 (en) | Systems and methods for energy data collection | |
| US20260095966A1 (en) | Systems and methods for configuring unmanned aerial vehicle (uav) multi-rat dual connectivity (mrdc) | |
| JP7804078B2 (en) | Systems and methods for identifying subscription-based unmanned aerial vehicles (UAVs) | |
| WO2025091174A1 (en) | Systems and methods for device discovery control | |
| WO2024234520A1 (en) | Systems and methods for network slice information synchronization | |
| WO2025145441A1 (en) | Systems and methods for quality of experience support | |
| WO2024082207A1 (en) | Systems and methods for providing analytics identifier in subscription change notification | |
| WO2025236499A1 (en) | Systems and methods for authentication and key management for applications service disabling | |
| WO2025076714A1 (en) | Systems and methods for user equipment registration | |
| US20250126656A1 (en) | Wireless communication method and device thereof | |
| WO2024169004A1 (en) | Systems and methods for reactivation of a protocol data unit (pdu) session for data network name (dnn) replacement |
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: 23913961 Country of ref document: EP Kind code of ref document: A1 |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 202380088892.2 Country of ref document: CN |
|
| WWP | Wipo information: published in national office |
Ref document number: 202380088892.2 Country of ref document: CN |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 23913961 Country of ref document: EP Kind code of ref document: A1 |