Switching communication paths in communication between nodes

Abstract

Methods, apparatuses, and systems for communicating between nodes are disclosed. The method includes communicating from a first node to a second node on a first communication path, where the first communication path is one of a device-to-device communication path, a device-to-network communication path, or a global navigation satellite system-to-network path; automatically switching, by the first node, from the first communication path to a second communication path, where the second communication path is the other of a device-to-device communication path, a device-to-network communication path, or a global navigation satellite system-to-network path, where the second communication path is different from the first communication path, and the switching is performed based on one or more triggers; and communicating from the first node to the second node on the second communication path.

Description

Cross-referencing of related patent applications

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 457,200, filed April 5, 2023, entitled “ACTIVATION, SWITCHING AND COMBINATION OF SYSTEMS AND REFERENCE POINTS,” the entire contents of which are incorporated herein by reference. Technical Field

[0002] The apparatuses and methods consistent with this disclosure generally relate to communication, and more specifically, to methods, systems and devices for communication between nodes on a communication path and for switching communication paths based on one or more triggers. Background Technology

[0003] Network-to-device communication is used when nodes (as used herein, including (and also referred to as) devices, handsets, user equipment (UE), mobile devices, roadside units, or network infrastructure equipment) are within the coverage of a network. Nodes utilize network infrastructure, network-to-device interfaces, and device-to-network interfaces. Interfaces can be physical (e.g., wired) or wireless interfaces within the network, or radio interfaces between the network and devices. As used herein, the term "network-to-device" makes no restrictive assumptions about the direction of communication (i.e., the transmitting and receiving parties in the communication) and covers communication from network to device and / or from device to network.

[0004] Device-to-device communication can be used for direct communication between devices (or UEs) without requiring any UE to be within network coverage. For example, this is used for vehicle-to-vehicle communication.

[0005] Global Navigation Satellite System (GNSS) is a general term used to describe any satellite system that provides positioning. Examples of GNSS include the Global Positioning System (GPS), China's BeiDou Satellite Navigation System (BDS), Europe's Galileo, Russia's GLONASS, India's Indian Regional Navigation Satellite System (IRNSS) / Navigation Indian Constellation (NavIC), or Japan's Quasi-Zenith Satellite System (QZSS). Neither the terms "GNSS to device" nor "GNSS to network" make any restrictive assumptions about the direction of communication used and cover both directions. Summary of the Invention

[0006] According to some embodiments of this disclosure, a method for communication between nodes is provided. The method includes: performing communication from a first node to a second node on a first communication path, wherein the first communication path is one of a device-to-device communication path, a device-to-network communication path, or a GNSS-to-network path; automatically switching from the first communication path by the first node to a second communication path, wherein the second communication path is another of the device-to-device communication path, the device-to-network communication path, or the GNSS-to-network path, wherein the second communication path is different from the first communication path, and the switching is based on one or more triggers; and performing communication from the first node to the second node on the second communication path.

[0007] According to some embodiments of this disclosure, a first node is provided. The first node includes: a memory configured to store instructions; and a processor configured to execute the instructions stored in the memory to: perform communication from the first node to a second node on a first communication path, wherein the first communication path is one of a device-to-device communication path, a device-to-network communication path, or a GNSS-to-network path; automatically switch from the first communication path to a second communication path by the first node, wherein the second communication path is another of the device-to-device communication path, the device-to-network communication path, or the GNSS-to-network path, the second communication path being different from the first communication path, and the switching is based on one or more triggers; and perform communication from the first node to the second node on the second communication path.

[0008] According to some embodiments of this disclosure, a non-transitory computer-readable medium is provided that stores instructions executable by one or more processors of a first node in a communication network to perform a method. The method includes: performing communication from the first node to a second node on a first communication path, wherein the first communication path is one of a device-to-device communication path, a device-to-network communication path, or a GNSS-to-network path; automatically switching from the first communication path by the first node to a second communication path, wherein the second communication path is another of the device-to-device communication path, the device-to-network communication path, or the GNSS-to-network path, wherein the second communication path is different from the first communication path, and the switching is based on one or more triggers; and performing communication from the first node to the second node on the second communication path. Attached Figure Description

[0009] [ Figure 1 ] Figure 1 This is a block diagram of a user plane protocol stack for a 5G access layer, consistent with some embodiments of this disclosure. [ Figure 2 ] Figure 2 This is a block diagram of a control plane protocol stack for 5G that is consistent with some embodiments of this disclosure. [ Figure 3 ] Figure 3 This is a block diagram of a core network interface for 5G that is consistent with some embodiments of this disclosure. [ Figure 4 ] Figure 4 This is a block diagram of a user plane protocol stack for the LTE access layer, consistent with some embodiments of this disclosure. [ Figure 5 ] Figure 5This is a block diagram of a control plane protocol stack for the LTE access layer, consistent with some embodiments of this disclosure. [ Figure 6 ] Figure 6 This is a block diagram of a core network interface for LTE that is consistent with some embodiments of this disclosure. [ Figure 7 ] Figure 7 This is a diagram of 3GPP New Radio (NR) side link mode 2 resource allocation consistent with some embodiments of this disclosure. [ Figure 8 ] Figure 8 This is a diagram of 3GPP NR-side walkway mode 1 resource allocation consistent with some embodiments of this disclosure. [ Figure 9 ] Figure 9 This is a diagram of an LTE positioning protocol, consistent with some embodiments of this disclosure, as used in LTE or NR. [ Figure 10 ] Figure 10 This is a diagram of a first example of switching between communication paths, consistent with some embodiments of this disclosure. [ Figure 11 ] Figure 11 This is a diagram of a second example of switching between communication paths, consistent with some embodiments of this disclosure. [ Figure 12 ] Figure 12 This is a flowchart of a method for evaluating and switching communication paths or transmitting associated received one or more triggers on a combination of communication paths, consistent with some embodiments of this disclosure. [ Figure 13 ] Figure 13 This is a flowchart of a method for communication between nodes that is consistent with some embodiments of this disclosure. [ Figure 14 ] Figure 14 This is a block diagram of a UE conforming to some embodiments of this disclosure. Detailed Implementation

[0010] Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. The following description refers to the accompanying drawings, in which, unless otherwise stated, the same reference numerals in different figures denote the same or similar elements. The implementations set forth in the following description of the exemplary embodiments do not represent all implementations consistent with this disclosure. Rather, they are merely examples of systems, apparatuses, and methods consistent with aspects related to this disclosure as set forth in the appended claims.

[0011] Network-to-device communication and network-to-device interface

[0012] For the 3GPP example, one interface used for the access layer (or radio interface) is the Uu interface. For the 3GPP 5G example, this is referred to as the New Radio (NR) interface for the access layer, or the 5G N1 interface for non-access layer interfaces. Figure 1 and Figure 2 This paper summarizes some 5G-specific layers for the network-device interface between the UE and the base station (e.g., gNB, which is a 5G Node B, a radio access network node for 5G NR).

[0013] Figure 1 This is a block diagram of the user plane protocol stack 100 used in the 5G access layer, showing the communication layers between UE 102 and gNB 104. These layers include Physical (PHY) layers 110a and 110b; Medium Access Control (MAC) layers 112a and 112b; Radio Link Control (RLC) layers 114a and 114b; Packet Data Convergence Protocol (PDCP) layers 116a and 116b; and Service Data Adaptation Protocol (SDAP) layers 118a and 118b.

[0014] Figure 2 This is a block diagram of the control plane protocol stack 200 for 5G, showing the communication layers between UE 202, gNB 204, and the Access and Mobility Management Function (AMF) 206. These layers include PHY layers 210a and 210b; MAC layers 212a and 212b; RLC layers 214a and 214b; PDCP layers 216a and 216b; Radio Resource Control (RRC) layers 218a and 218b; and Non-Access Stratum (NAS) layers 220a and 220b.

[0015] One example of an interface used for 5G core network-device interfaces is the N1 interface, such as... Figure 3 As shown. Figure 3 This is block diagram 300 for the core network interface used in 5G. Figure 3The diagram illustrates various network interfaces between entities in the core network, including AMF 302, Network Slice Selection Function (NSSF) 304, Authentication Server Function (AUSF) 306, Network Slice-Specific Authentication and Authorization Function (NSSAAF) 308, Unified Data Management (UDM) Function 310, Session Management Function (SMF) 312, Policy Control Function (PCF) 314, Application Function (AF) 316, UE 318, Radio Access Network (RAN) 320, User Plane Function (UPF) 322, and Data Network (DN) 324.

[0016] An example of transitioning to 3GPP LTE (Long Term Evolution) is that, for the access layer / radio, the network interface used is either the LTE-Uu interface or the E-UTRA (Evolved Universal Terrestrial Radio Access) interface. Figure 4 and Figure 5 This paper summarizes some layers used for the LTE-Uu interface in network-device scenarios between UE and eNB (Evolved Node B, a radio access network node for LTE).

[0017] Figure 4 This is a block diagram of the user plane protocol stack 400 used in the LTE access layer, showing the communication layers between UE 402 and eNB 404. These layers include PHY layers 410a and 410b; MAC layers 412a and 412b; RLC layers 414a and 414b; and PDCP layers 416a and 416b.

[0018] Figure 5This is a block diagram of the control plane protocol stack 500 used for the LTE access layer. It shows the communication layer between the UE 502, eNB 504, and Mobility Management Entity (MME) 506, which is part of the LTE core network (or Evolved Packet Core (EPC)). These layers include PHY layers 510a and 510b; MAC layers 512a and 512b; RLC layers 514a and 514b; PDCP layers 516a and 516b; RRC layers 518a and 518b; and NAS layers 520a and 520b.

[0019] like Figure 6 As shown, some of the interfaces used for the LTE core network-device interface are the S1-MME and S1-U interfaces. Figure 6 This is block diagram 600 for the core interface used in LTE. Figure 6 The diagram illustrates various network interfaces between entities in the core network, including the Universal Terrestrial Radio Access Network (UTRAN) 602, the Global System for Mobile Communication (GSM) Enhanced Data for GSM Evolution (EDGE) Radio Access Network (GERAN) 604, the Serving GPRS Support Node (SGSN) 606, the MME 608, the Home Subscriber Server (HSS) 610, the UE 612, the Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN) 614, the Serving Gateway 616, the Packet Data Network (PDN) Gateway 618, and the Policy and Charging Rules function. Function (PCRF) 620, and Carrier IP Service 622.

[0020] Device-to-device communication and device-to-device interface

[0021] In the 3GPP example, device-to-device communication uses the PC5 interface for 5G and LTE, which includes a direct radio interface and protocols between UEs. For this purpose, LTE and NR technologies are reused (with some modifications) without traversing any network nodes.

[0022] For an example of 3GPP NR, direct device-to-device communication is used via side link communication with mode 2, such as... Figure 7 As shown. Figure 7 This is a diagram of 3GPP NR-side walkway mode 2 resource allocation 700, illustrating communication between network 702, transmitting (Tx) UE 704, and receiving (Rx) UE 706. In mode 2, network 702 can, for example, provide some general configuration information about some (one or more) resource pools for use by sending RRC configuration from network 702 to Tx UE 704. In some embodiments, this can be accomplished via pre-configuration in the Tx UE. During transmission, Tx UE 704 is not connected to the network (nor is Rx UE 706). Tx UE 704 performs some autonomous sensing and resource selection to find time and frequency resources to be used for transmission to Rx UE 706. The equivalent of NR-side walkway mode 2 for LTE-side walkway is LTE-side walkway mode 4.

[0023] Alternatively, 3GPP NR-side walkway device-to-device communication can be used, with scheduling controlled by a network with dynamic licensing and / or configuration licensing. In this case, the Tx UE needs to be within network coverage. This can be accomplished via NR-side walkway mode 1 resource allocation, such as... Figure 8 As shown. Figure 8 This is a diagram of 3GPP NR side link mode 1 resource allocation 800, which illustrates the communication between network 802, Tx UE 804, and Rx UE 806. In mode 1, the scheduling mandate provided by network 802 to Tx UE 804 informs Tx UE 804 of the time and frequency resources used for transmission to Rx UE 806.

[0024] GNSS to device communication and GNSS to device interface

[0025] GNSS-to-device communication is used to derive information such as timing, which in turn allows for the determination of geographic location. Although this relies on GNSS-to-device signals, it can utilize network signaling via the LTE Positioning Protocol (LPP), such as... Figure 9 As shown. Figure 9 This is a diagram of the LPP protocol 900 used in LTE or NR, illustrating communication between the target device 902, the location server 904, the first reference source 906, and the second reference source 908. The term "GNSS to device interface" includes GNSS to UE signals.

[0026] Target device 902 may include a UE. Location server 904 may include an Evolved Serving Mobile Location Center (E-SMLC), a Location Management Function (LMF), or a Secure User Plane Location (SUPL) Location Platform (SLP). First reference source 906 may include an eNodeB or a Next Generation Radio Access Network (NG-RAN). Second reference source 908 may include one or more satellites.

[0027] The first reference source 906 can provide LTE or NR radio signals to the target device 902. The second reference source 908 can provide GNSS signals to the target device 902. The target device 902 can provide the location server 904 with measurements of the LTE or NR radio signals, GNSS signals, a combination of these two signals, or additional location information. The location server 904 can provide auxiliary data to the target device 902 to assist the target device in determining its location.

[0028] Communication path

[0029] Some existing communication standards involve different communication interfaces (also referred to as communication paths in this paper), but none of these standards address switching between different communication interfaces / paths.

[0030] For example, ETSI Technical Specification (TS) 103 831 (Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Decentralized Environmental Notification Service)) is source-agnostic and specifies in its scope that "DEN basic services can be implemented in vehicle ITS-S, roadside ITS-S, personal ITS-S, or central ITS-S".

[0031] For example, ETSI TS103 301 (Intelligent Transport Systems (ITS); Vehicular Communications; Basic Set of Applications; Facilities layer protocols and communication requirements for infrastructure services) focuses on a path / interface that, within its scope, indicates that it is "for supporting communication between infrastructure ITS equipment and traffic participants (e.g., vehicles, pedestrians) using ITS equipment".

[0032] For example, 3GPP TS23.285 (Architecture enhancements for V2X services) mentions the procedures for V2X (Vehicle-to-Everything) communication via the PC5 reference point and the procedures for V2X communication via the LTE-Uu reference point, but does not provide details on which reference point to choose.

[0033] For example, 3GPP TS24.386 (UE to V2X control function; protocol aspect) mentions the procedures for V2X communication via the PC5 reference point and the procedures for V2X communication via the LTE-Uu reference point, but does not provide details on which reference point to select.

[0034] For example, 3GPP TS24.587 (Vehicle-to-Everything (V2X) services in 5G System (5GS); Phase 3) mentions procedures for V2X communication via PC5 reference points and procedures for V2X communication via LTE-Uu reference points, but does not provide details on which reference point to choose.

[0035] For example, 3GPP TS23.122 (Non-Access-Stratum (NAS) Functions Related to Mobile Stations (MS) in Idle Mode) mentions that “communication via PC5 V2X can be performed on a selected PLMN in a limited service state”, but does not provide further details on whether V2X services are performed via the PC5 interface or the Uu interface.

[0036] For example, 5GAA TS S-180175 (Brief Profile of C-ITS Communication Systems Using Cellular Uu Interfaces), as its title suggests, focuses on scenarios “when long-range cellular Uu communication is used.”

[0037] This disclosure relates to switching between systems or communication interfaces / paths. Some embodiments can provide communication across multiple interfaces simultaneously. Some different systems and interfaces that can be used as examples are network-to-device interfaces, device-to-device interfaces, or GNSS-to-device interfaces. In some embodiments, triggers can be defined and used in decisions associated with switching between interfaces and / or transmission across multiple interfaces. Switching between communication paths allows the selection of the “best” system, interface, or reference point based on various criteria such as cost; availability of one or more systems, interfaces, or reference points; etc.

[0038] In the example of device positioning, when a mobile device is outside network coverage, it can benefit from using sidelink positioning so that the device may still be able to determine its geographic location. When there is no GNSS coverage (e.g., no GPS coverage), the device may still be able to obtain its location via network positioning. If one system is more accurate than others (and is likely to be so if that accuracy is required), the device can use that system or interface as the starting or default mode. Other criteria can influence the default mode used, such as the relative cost of using each system or interface, for example, which one is the cheapest (or potentially free).

[0039] In another example, when network problems occur, the mobile device can switch to sidelink communication. Another potential advantage is, for example, avoiding a situation where the UE remains "stuck in mode 1" (i.e., sidelink mode 1) if the device is configured or pre-configured to use mode 1 and a series of radio link failures with the network occur.

[0040] Figure 10 This is a diagram of a first example 1000 of switching between communication paths / interfaces, consistent with some embodiments of this disclosure. Figure 10 An example of aggregation of three systems is shown, such as Uu interface 1002, Sidelink (SL) interface 1004, and GNSS interface 1006. The operating principles described herein can be switched between more or fewer systems than those described herein without changing how the embodiments operate. Triggers for switching between interfaces 1002, 1004, and 1006 can be defined.

[0041] Some potential triggers that can be used during handover include, but are not limited to: Uu coverage (e.g., the UE is outside or within network coverage), GNSS coverage, Uu radio link failure, sidelink radio link failure, network cell ban, sidelink congestion level, Uu congestion level, number of surrounding UEs supporting sidelinks, number of surrounding UEs with sidelink connections to the UE, the required or supported accuracy for each system or interface, or the required or supported latency for each system or interface.

[0042] The one or more triggers used do not need to be the same for every switching path. In some embodiments, triggers can be selected symmetrically. For example, switching a communication path from the Uu interface to the side link interface can use a trigger outside the network coverage area, while symmetrically switching a communication path from the side link interface to the Uu interface can use a symmetrical trigger within the network coverage area.

[0043] For triggers where a threshold can be applied, each potential trigger can also use a threshold. For example, a threshold can be applied to a trigger based on the Uu congestion level, because a handover is triggered if the Uu congestion level is higher than a predetermined threshold. As another example, a threshold will not be applied to triggers that are binary (e.g., yes or no) conditions, such as whether the UE is outside network coverage.

[0044] As an example, handover can be used to provide information about road accidents. In one embodiment, the default or initial system or interface for this type of signaling could be the Uu interface. For example, it might be more resource-efficient for a UE to use the Uu interface instead of the sidelink interface for this type of signaling because the Uu interface only uses one hop to the network and does not involve transmissions across many UEs (e.g., vehicles) communicating via the sidelink if the information is intended to be provided to UEs located several miles away (e.g., requiring multiple hops from the initially communicating UE to the target UE). When there is no network coverage, if a network problem is detected (e.g., a radio link failure is detected) and / or the cell becomes disabled, the UE will switch to the sidelink interface. When one or more problems disappear or under one or more other specific triggers (e.g., reflecting the opposite condition), the UE can switch to the Uu interface.

[0045] In some embodiments, handover criteria may include a hysteresis dimension to avoid the frequent ping-pong effect of handovers between systems or interfaces. Instead of or appended to this criterion, timers may also be used to avoid overly frequent handovers. For example, a timer may be started when a communication path is switched, and if the timer has not expired, the UE does not perform another handover (or does not switch back to the previous path). In one embodiment, triggering conditions are evaluated only if the required accuracy of the existing communication connection is not achieved (e.g., for location information or for the Quality of Service (QoS) of the communication path in use) to avoid unnecessary handovers.

[0046] In some embodiments, a combination of communication interfaces can be used to send messages or packets. For example, a UE in a vehicle might use both the Uu interface and the sidelink interface to provide information about a recent car accident. Using a combination of communication interfaces may be desirable because some surrounding UEs might be equipped with the Uu interface instead of the sidelink interface. Using direct sidelink communication takes advantage of its lower latency. After a duration (e.g., a few seconds), the UE could switch to only the Uu interface to provide, for example, more detailed information about the car accident. In other embodiments, other combinations of interfaces are possible, including switching between interfaces.

[0047] In one embodiment, to preserve session continuity—that is, to deliver the most accurate location information to the original requesting node (e.g., the target UE, AMF, or LocationService (LCS) client of the Location Management Function) under the same session identifier (ID) independent of the location technology (e.g., legacy Uu positioning, GNSS, PC5-only positioning)—a subordinate location request can be triggered to feed into the original (independent) session. For example, for a Network Induced Location Request (NI-LR) or a Mobile Terminated Location Request (MT-LR), the target UE can be instructed to trigger its own Mobile Originated Location Request (MO-LR) to its own GNSS interface, and then use this information to provide location information to the LMF within the original NI-LR or MT-LR session. The LMF can then compare the location information from the two sessions and use the more accurate result. In the case of MO-LR, the target UE will be the management node and will compare the GNSS input with the input provided from the LMF.

[0048] Add examples of transformations and combinations Figure 10 In the embodiments shown This will lead to Figure 11 The example shown. Figure 11 This is a diagram of a second example 1100 of switching between communication paths, consistent with some embodiments of this disclosure. Figure 11 An aggregation example of different systems is shown, such as Uu interface 1102, sidelink (SL) interface 1104, GNSS interface 1106, and a combination of Uu and SL interfaces 1108. Triggers for switching between interfaces 1102-1108 can be defined.

[0049] Other embodiments include switching to and from the sidelink UE autonomous resource selection mode and sidelink network resource allocation mode. For the example of a sidelink NR, this reflects switching to and from sidelink UE autonomous resource selection mode and sidelink network resource allocation mode 1 described elsewhere in this disclosure and from sidelink resource allocation mode 2 and sidelink resource allocation mode 1 described elsewhere in this disclosure (see, for example...). Figure 7 and Figure 8 ).

[0050] One advantage of switching from Mode 1 to Mode 2 is that service is allowed if there are network problems. In Mode 1, since scheduling is performed by the network, if a network problem occurs (e.g., outside network coverage), the UE can remain trapped in Mode 1 (because scheduling is performed by the network) and be blocked from communicating with other UEs until it falls back to the abnormal resource pool.

[0051] Another reason for switching between Mode 1 and Mode 2 may be to conserve battery power in certain situations, such as in battery-powered devices (e.g., pedestrian mobile devices or electric vehicles). Therefore, the fact that the UE is a pedestrian device, an electric vehicle, or more generally a UE requiring power conservation can be used as a trigger to switch from Mode 1 to Mode 2 or vice versa (or, for example, its equivalent mode for LTE or 6G). This can be performed autonomously within the device, or the network can indicate a mode change (e.g., to Mode 1 and / or to Mode 2) based on information received from the device by the network (e.g., UE capabilities or the UE's battery level).

[0052] Another trigger used in handover (in lieu of or attached to other conditions or triggers) is that, in addition to another trigger (e.g., network problem), the UE is in the process of receiving resource allocation information from the network, such as receiving a Physical Downlink Control Channel (PDCCH) allocation for example, for sidelink NR.

[0053] If the UE is in sidelink autonomous mode (resource allocation mode 2 for the NR example) and, in addition to another trigger (e.g., a network problem), is in the process of receiving Radio Resource Control (RRC) configuration from the network, another handover can occur. In this example, the UE can remain in sidelink autonomous mode (resource allocation mode 2 for the NR example) and switch to using the previous RRC configuration. This will allow the UE to perform sidelink communication.

[0054] Other triggers that can be used include existing criteria that have been used for other purposes. For example, in 3GPP TS 38.331, in order for a UE to move from RRC connected mode to RRC idle mode, the UE performs an RRC rebuild, or is reconfigured to hand over to a new cell or node. Triggers in this scenario may include, but are not limited to: RadioLink Failure, detection of physical layer problems, reconfiguration with synchronization failure, upon receiving a series of consecutive "out of sync" indications, upon receiving a series of consecutive "synchronization" indications, random access problems received from the Medium Access Control (MAC) layer or entity (e.g., indications), several RLC retransmissions have been reached, consistent uplink Listen Before Talk (LBT) failure from the MAC layer or entity (e.g., indications), the expiration of a timer that started upon receiving a series of consecutive "out of sync" indications (e.g., the timer could be T310 from 3GPP TS 38.331), or the expiration of a timer that started upon triggering a measurement report and stopped upon receiving a series of consecutive "synchronization" indications (e.g., the timer could be T312 from 3GPP TS 38.331).

[0055] In other embodiments, device history can be used as a criterion and can be combined with one or more other criteria. For example, if the UE has experienced a certain number of problems within a predetermined duration, this can be considered a valid criterion for the activation, handover, and / or combination of communication paths. The problem or trigger can be the same as those described elsewhere in this disclosure.

[0056] In another embodiment, the UE's location, its speed, and / or its orientation can be used as a trigger for handover. In another embodiment, the knowledge about the UE's location can be contextual, for example, the UE is on a highway. In another embodiment, the predicted location of the UE at a specific subsequent moment can be the trigger. For example, a UE leaving an urban environment and entering a highway can switch from Uu positioning to GNSS positioning. In another example, a UE entering a tunnel on a highway can switch from GNSS positioning to lateral link positioning.

[0057] In other embodiments, whether the assistance information is available from a location server (see, for example, see...) Figure 9 This can be used as a potential trigger. In other embodiments, the quantity and / or frequency of auxiliary information from the location server can be used as a trigger (and potentially a threshold).

[0058] In another embodiment, a request for service from another UE can be used as a trigger. For example, in a scenario outside network coverage, a UE might receive a request from another UE to act as an anchor in a sidelink absolute positioning session. In another variation of this embodiment, a UE with an active positioning session might experience a radio link failure that results in a loss of connection with the LMF. This can be used as a trigger for the UE to switch to GNSS positioning to obtain location information. In yet another embodiment, one or more conditions for using the system or interface can be defined without requiring a conversion.

[0059] In another embodiment, a priority can be defined for each of the systems or interfaces used. The system or interface with the highest priority will be used when it becomes available or when its corresponding criteria are met. One or more criteria may be associated with the use of each system or interface. If criteria are valid for more than one system or interface, the system or interface with the highest priority can be used.

[0060] Information (e.g., priorities or criteria) for configuring this behavior can be provided to the UE via signaling. This signaling can be provided from the network or from another UE. For example, this information can be provided via the Uu interface or via the side link interface. This can be done using the RRC protocol and / or MAC-CE (control element) information as an example. Any predefined constants and timers for Radio Link Failure (RLF) or Handover Failure can be directly used and extended by the UE to switch between using a 3GPP network (e.g., gNB), a GNSS node, or another UE (e.g., within or outside the coverage of the gNB and / or GNSS). In one embodiment, for a 3GPP NR example, constants and timers can be configured and can use the RRC protocol. In another embodiment, configuration information can be transmitted to the UE via the LTE positioning protocol.

[0061] Configuration information can be provided to the UE through pre-configuration in the mobile equipment (ME) or USIM. For example, configuration information can be uploaded from the home PLMN to the USIM over the air via the SIM toolkit.

[0062] To distinguish different messages (potentially originating from different sources, such as an LPP from the network and a sidelink LPP from another UE) referring to the same application and thus able to be considered during handover, an application identifier (ID) can be provided in the signaling. In the case of nested (parallel) sessions, one embodiment also provides a session ID. Ideally, the dependencies between individual sessions are explicitly indicated (e.g., through hierarchical session IDs) or implicitly managed (e.g., at the LMF). When the root session terminates, any dependent sub-sessions also terminate, and all resources are released. The termination of a sub-session does not imply the termination of any parent session. Input from sub-sessions can also be shared between parent sessions.

[0063] In one example, switching and / or combining can be applied to positioning methods from different systems, e.g., between network-to-device and GNSS-to-device. In another example, switching and / or combining can be applied to positioning methods within the same system, e.g., within GNSS-to-device (e.g., between a Round-Trip-Time (RTT) method and an Observed-Time-Difference-Of-Arrival (OTDOA) method). In the case of multiple positioning processes within 3GPP Radio Access Technology (RAT), Positioning Reference Signal (PRS) resources and measurement reports can be shared, for example, by tagging individual PRS measurements with sub-sessions and / or session IDs associated with that resource. In this way, PRS usage and reporting overhead are reduced. Alternatively, if each measurement report (legacy behavior) allows only a single session ID, duplicate measurement reports can provide pointers or links to some other previous measurement to indicate the duplicate nature of the report.

[0064] In other embodiments, another UE or network (e.g., gNB) may provide the UE with information that will allow the UE to decide whether a handover, activation, or combination is useful. This may involve some of the triggers described above, or it may involve more straightforward information about which system to activate, switch to, and / or combine. For example, the UE may broadcast such information to surrounding UEs. This will allow another UE receiving the information to anticipate activation, handover, or combination. For example, a UE experiencing an outage or degradation may notify its surrounding UEs of the outage or degradation so that other UEs are aware of the problem before they experience it. For example, a vehicle approaching a tunnel may switch from Uu positioning to lateral link positioning. If the UE has determined the problem itself or received information about the problem from another UE or network (e.g., gNB), the UE may notify the LMF about the problem or the anticipated problem. The LMF, in turn, may provide this information to other UEs. The speed, location, and / or orientation of these other UEs may be used in the decision-making process. Therefore, other UEs that receive this information can proactively establish the necessary procedures to switch their location and / or communication interfaces, thus allowing their ongoing services to gracefully degrade before experiencing any anticipated interruption, or thus avoid degradation altogether.

[0065] Figure 12 This is a flowchart of a method 1200 for evaluating and transmitting one or more triggers associated with switching communication paths or a combination of communication paths, consistent with some embodiments of this disclosure. In some embodiments, method 1200 may be performed by a first node communicating with a second node.

[0066] Method 1200 includes: step 1202, whereby the first node communicates with the second node on a first communication path. For example, the first node may communicate with the second node via a Uu interface.

[0067] Method 1200 includes: step 1204, receiving at least one trigger at a first node. The at least one trigger may include any one or more of the triggers described elsewhere in this disclosure. Step 1204 is optional. The at least one trigger may be known at the first node without needing to be explicitly received. For example, the at least one trigger may be hardcoded according to 3GPP specifications. Therefore, other variations of step 1204 may include evaluating the at least one trigger instead of receiving it. In another embodiment, step 1204 may be omitted.

[0068] Method 1200 includes: step 1206, determining whether the at least one trigger indicates a switch to a second communication path. If the at least one trigger indicates a switch to a second communication path (step 1206, "Yes" branch), then method 1200 includes: step 1208, whereby the first node switches the communication path between the first node and the second node from the first communication path to the second communication path. For example, the first node may switch from the first communication path on the Uu interface to the second communication path on the side link interface. In some embodiments, the first node may automatically switch the communication path from the first communication path to the second communication path (e.g., using any additional input such as from an individual or another device). After step 1208, method 1200 may return to step 1202 (in some embodiments) or may proceed to step 1210 (in other embodiments). Options for the next step to be performed after step 1208 are shown by dashed lines to indicate that either option is possible.

[0069] If at least one trigger does not indicate a switch to the second communication path (step 1206, "No" branch), then method 1200 includes: step 1210, determining whether the at least one trigger indicates that a transmission should occur on the combined communication path. If at least one trigger indicates that a transmission should occur on the combined communication path (step 1210, "Yes" branch), then method 1200 includes: step 1212, performing communication from the first node to the second node on both the first and second communication paths. For example, the first node can currently communicate with the second node via the first communication path (e.g., Uu interface) and can also communicate with the second node via the second communication path (e.g., sidelink interface). If at least one trigger does not indicate that a transmission should occur on the combined communication path (step 1210, "No" branch), then method 1200 returns to step 1202 as described above.

[0070] Figure 12 The method 1200 shown is one possible example embodiment. In another example embodiment, method 1200 may be modified such that step 1210 is performed before step 1206. In yet another example embodiment, all criteria are evaluated in no particular order between switching or combining.

[0071] In another embodiment, the above method can also be applied to non-terrestrial networks (e.g., High-Altitude Platform Stations (HAPS), Uncrewed Aerial Vehicles (UAVs), Low-Earth Orbit (LEO), Medium-Earth Orbit (MEO), Geostationary Earth Orbit (GEO) satellites, etc.) in addition to or in place of GNSS satellites and terrestrial networks.

[0072] Any of the embodiments described in this document (two or more) may be used in combination. For such combinations, any logical elements such as "OR", "AND", and / or "XOR" may be used.

[0073] Although the examples described in this document involve 3GPP LTE, 3GPP NR, 3GPP LTE sidelink, and 3GPP NR sidelink, other technologies are also possible, such as 3GPP 6G or IEEE 802.11.

[0074] This disclosure considers at least three types of devices (Type A, Type B, and Type C). Type A devices include modules for first-side hop link communication and modules for second-side hop link communication. Type B devices include only modules for first-side hop link communication. Type C devices include only modules for second-side hop link communication. For example, in one embodiment, a Type A device includes both an LTE-side hop link module and an NR-side hop link module; a Type B device includes only an NR-side hop link module; and a Type C device includes only an LTE-side hop link module.

[0075] In some embodiments, method 1200 may be performed by a type A device, a type B device, or a type C device.

[0076] Figure 13 This is a flowchart of a method 1300 for communication between nodes, consistent with some embodiments of this disclosure.

[0077] Method 1300 includes: step 1302, performing communication from a first node to a second node on a first communication path, wherein the first communication path is one of a device-to-device communication path, a device-to-network communication path, or a GNSS-to-network path. The first node and the second node may each be a mobile device, a user equipment, a roadside unit, or a network infrastructure device.

[0078] In some embodiments, one or more triggers include one or more of the following: the first node is within network coverage; the first node is outside network coverage; the first node is within GNSS coverage; the first node is outside GNSS coverage; radio link failure; under conditions where the network cell is disabled; under conditions where the network fails; under conditions where the radio interface congestion level exceeds, reaches, or falls below one or more of the congestion thresholds; several surrounding nodes supporting sidelink communication; several surrounding nodes having sidelink communication connections to the first node; the accuracy of one or more radio interfaces, including the accuracy of positioning information received via one or more radio interfaces or the quality of service of one or more radio interfaces; the latency of one or more radio interfaces; the battery level of the first node; detection of physical layer problems; reconfiguration due to synchronization failure; under conditions where the first node receives several consecutive asynchronous indications. The following conditions apply: When the first node receives several consecutive synchronization indications; when the first node receives a random access problem indication from the media access control layer; when several radio link control retransmissions have been completed; when a consistent uplink listen-before-speak failure indication is received from the media access control layer; when a timer expires; the position of the first node; the speed of the first node; the direction of movement of the first node; when a request for services to be provided by the first node is received from another node; the first node needs to conserve power; the first node is in the process of receiving configuration via the radio interface; the first node is in the process of receiving resource allocation via the radio interface; or the type of the first node, such as a pedestrian-carried type node, a fixed type node in a vehicle (e.g., an electric vehicle (e.g., a pure electric vehicle, a hybrid electric vehicle, a plug-in hybrid electric vehicle, or a fuel cell electric vehicle) or a non-electric vehicle), or other types of nodes.

[0079] In some embodiments, some or all of the one or more triggers are related to sidelink communication. In some embodiments, the one or more triggers are received by a first node.

[0080] In some embodiments, the first node is any of the following: a mobile device, a user equipment, a roadside unit, or a network infrastructure device, such as an evolved NodeB (eNB), a Next Generation NodeB (gNB), a Mobility Management Entity (MME), an Access and Mobility Management Function (AMF), or other network infrastructure devices.

[0081] Method 1300 includes: step 1304, whereby a first node automatically switches from a first communication path to a second communication path, wherein the second communication path is another of a device-to-device communication path, a device-to-network communication path, or a GNSS-to-network path, the second communication path being different from the first communication path, and the switching is based on one or more triggers. These triggers may include various states or conditions, as described elsewhere in this disclosure. In some embodiments, the trigger may have an associated threshold, and the switching is performed when a criterion associated with the trigger exceeds, reaches, or falls below the associated threshold.

[0082] In some embodiments, the handover is performed only if the required quality of service associated with the first communication path is not achieved. In some embodiments, some or all of the one or more triggers have associated thresholds, and the handover is performed if a criterion associated with one or more of the one or more triggers exceeds, reaches, or falls below the associated threshold.

[0083] In some embodiments, the first communication path and the second communication path are used for device positioning.

[0084] In some embodiments, the switch is performed only if the required positioning accuracy associated with the first communication path is not achieved.

[0085] In some embodiments, the switching is also based on the device history of the first node, and the device history includes a number of triggers that have become valid within a predetermined time period. In some embodiments, the number of triggers that have become valid also includes one or more of the following: exceeding one or more predetermined values, reaching one or more predetermined values, or falling below one or more predetermined values.

[0086] In some embodiments, the switching is performed if a plurality of triggers become valid within a predetermined time period. In some embodiments, the plurality of triggers that become valid further include one or more of the following: exceeding one or more predetermined values, reaching one or more predetermined values, or falling below one or more predetermined values.

[0087] Method 1300 includes: step 1306, performing communication from the first node to the second node on the second communication path.

[0088] In some embodiments, the switching further includes: switching the first node from a first communication path to a second communication path based on a first set of triggers. In some embodiments, the switching further includes: switching the first node from a second communication path to a first communication path based on a second set of triggers. In some embodiments, the first set of triggers and the second set of triggers may be symmetrical depending on the direction of the switching. In some embodiments, the first set of triggers and the second set of triggers may be asymmetrical depending on the direction of the switching. In some embodiments, the first set of triggers and the second set of triggers may include a hysteresis between values ​​associated with the direction of the switching.

[0089] In some embodiments, method 1300 further includes: setting a timer after the switch from the first communication path to the second communication path is completed, and preventing the first node from switching to the other communication path until the timer expires. In one example, the other communication path may be the first communication path. In another example, the other communication path may be the second communication path.

[0090] In some embodiments, method 1300 further includes: activating a second communication path based on the one or more triggers. In some embodiments, method 1300 further includes: performing communication from a first node to a second node on both the first communication path and the second communication path based on the one or more triggers.

[0091] Figure 14 A block diagram of a UE 1400 conforming to some embodiments of this disclosure is shown. The UE 1400 can be type A, type B, type C, or any other type of UE. The UE 1400 can be installed in a mobile vehicle or in a fixed location. The UE 1400 can take any form, including but not limited to, a vehicle, a component installed in a vehicle, a roadside unit, a laptop computer, a wireless terminal including a mobile phone, a wireless handheld device, or a wireless personal device, or any other form. See also Figure 14UE1400 may include antenna 1402, which can be used to transmit electromagnetic signals to or from a base station or other UE, or to receive electromagnetic signals from or from a base station or other UE. Antenna 1402 may include one or more antenna elements and may enable different input / output antenna configurations, such as Multiple Input Multiple Output (MIMO), Multiple Input Single Output (MISO), and Single Input Multiple Output (SIMO). In some embodiments, antenna 1402 may include multiple (e.g., dozens or hundreds) antenna elements and may enable multi-antenna functions such as beamforming. In some embodiments, antenna 1402 is a single antenna.

[0092] UE 1400 may include a transceiver 1404 coupled to antenna 1402. Transceiver 1404 may be a radio transceiver at UE 1400 and may communicate bidirectionally with a base station or other UEs. For example, transceiver 1404 may receive / transmit radio signals from / to a base station via downlink / uplink communication. Transceiver 1404 may also receive / transmit radio signals from / to other UEs or RSUs via sidelink communication. Transceiver 1404 may include a modem for modulating packets and providing the modulated packets to antenna 1402 for transmission, and for demodulating packets received from antenna 1402.

[0093] UE 1400 may include memory 1406. Memory 1406 may be any type of computer-readable storage medium, including volatile or non-volatile memory devices, or combinations thereof. Computer-readable storage media include, but are not limited to, non-transitory computer storage media. Non-transitory storage media can be accessed by a general-purpose or special-purpose computer. Examples of non-transitory storage media include, but are not limited to, portable computer floppy disks, hard disks, random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), digital versatile disk (DVD), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, etc. Non-transitory media can be used to carry or store desired program code means (e.g., instructions and / or data structures) and can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. In some examples, software / program code may be transmitted from a remote source (e.g., a website, server, etc.) using coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave. In such examples, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are within the scope of the defined medium. Combinations of the above examples are also within the scope of computer-readable media.

[0094] Memory 1406 may store information related to the identification of device 1400 and signals and / or data received by antenna 1402. Memory 1406 may also store post-processed signals and / or data. Memory 1406 may also store computer-readable program instructions, mathematical models, and algorithms used in signal processing in transceiver 1404 and calculations in processor 1408. Memory 1406 may also store computer-readable program instructions for execution by processor 1408 to operate UE 1400 to perform the various functions described in this disclosure. In some examples, memory 1406 may include a Basic Input / Output System (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices. In some embodiments, UE 1400 is a type AUE, and memory 1406 includes both an LTE SL module and an NR SL module. In some embodiments, UE 1400 is a type BUE, and memory 1406 includes only an NR SL module. In some embodiments, UE 1400 is a type C UE, and memory 1406 includes only an LTE SL module.

[0095] The computer-readable program instructions disclosed herein may be assembly instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages ​​(including object-oriented programming languages ​​and traditional procedural programming languages). The computer-readable program instructions may execute entirely on a computing device as a standalone software package, or may execute partly on a first computing device and partly on a second computing device located remotely from the first computing device. In the latter scenario, the remote second computing device may be connected to the first computing device via any type of network, including a local area network (LAN) or a wide area network (WAN).

[0096] UE 1400 may include processor 1408, which may include hardware devices with processing capabilities. Processor 1408 may include at least one of a general-purpose processor, a digital signal processor (DSP), a central processing unit (CPU), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or other programmable logic devices. Examples of general-purpose processors include, but are not limited to, microprocessors, any conventional processor, controllers, microcontrollers, or state machines. In some embodiments, processor 1408 may be implemented using a combination of devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration). Processor 1408 may receive downlink or sidelink signals from transceiver 1404 and further process the signals. Processor 1408 may also receive data packets from transceiver 1404 and further process these packets. In some embodiments, processor 1408 may be configured to operate memory using a memory controller. In some embodiments, the memory controller may be integrated into the processor 1408. The processor 1408 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1406) to cause the UE 1400 to perform various functions.

[0097] UE 1400 may include a Global Positioning System (GPS) 1410. GPS 1410 may be used to enable location-based services or other services and / or synchronize based on the geographic location of UE 1400. GPS 1410 may receive Global Navigation Satellite Systems (GNSS) signals from a single satellite or multiple satellites via antenna 1402 and provide the geographic location of UE 1400 (e.g., the coordinates of UE 1400).

[0098] UE 1400 may include an input / output (I / O) device 1412, which can be used to communicate the results of signal processing and computation to a user or other devices. I / O device 1412 may include a user interface, including a display and input devices, for transmitting user commands to processor 1408. The display may be configured to display the status of signal reception at UE 1400, data stored in memory 1406, the status of signal processing, and the results of computation, etc. The display may include, but is not limited to, a cathode ray tube (CRT), a liquid crystal display (LCD), a light-emitting diode (LED), a plasma gas display, a touchscreen, or other image projection devices for displaying information to the user. The input device may be any type of computer hardware device for receiving data and control signals from the user. The input device may include, but is not limited to, a keyboard, mouse, scanner, digital camera, joystick, trackball, cursor arrow keys, touchscreen monitor, or audio / video command device, etc.

[0099] UE 1400 may also include machine interface 1414, such as an electrical bus connecting transceiver 1404, memory 1406, processor 1408, GPS 1410 and I / O device 1412.

[0100] In some embodiments, the UE 1400 may be configured or programmed for communication between nodes. The processor 1408 may be configured to execute instructions stored in memory 1406 to: perform communication from a first node to a second node on a first communication path, wherein the first communication path is one of a device-to-device communication path, a device-to-network communication path, or a GNSS-to-network path. The processor 1408 may be configured to execute instructions to: automatically switch from the first communication path by the first node to a second communication path, wherein the second communication path is another of a device-to-device communication path, a device-to-network communication path, or a GNSS-to-network path, the second communication path being different from the first communication path, and the switching is based on one or more triggers. The processor 1408 may be configured to execute instructions to: perform communication from the first node to the second node on the second communication path.

[0101] As used in this disclosure, the use of the term "or" in a list of items indicates a comprehensive list. A list of items may be prefixed with phrases such as "at least one" or "one or more." For example, a list of at least one of A, B, or C includes A or B or C or AB (i.e., A and B) or AC or BC or ABC (i.e., A and B and C). Furthermore, as used in this disclosure, a list of conditions prefixed with the phrase "based on" should not be interpreted as "based only on" the set of conditions, but rather as "at least partially based on" the set of conditions. For example, a result described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure.

[0102] In this specification, the terms "comprising," "containing," or "including" are used interchangeably and have the same meaning, and are interpreted as inclusive and open-ended. The terms "comprising," "containing," or "including" may precede a list of elements and indicate that at least all listed elements are present, but other elements not listed may also be present. For example, if A includes B and C, then {B, C} and {B, C, D} are both within the scope of A.

[0103] With reference to the accompanying drawings, this disclosure describes example configurations that do not represent all possible examples or all configurations within the scope of this disclosure. The term "exemplary" should not be construed as "preferred" or "advantageous compared to other examples," but rather as "illustration, instance, or example." By reading this disclosure, including the description of embodiments and accompanying drawings, those skilled in the art will understand that alternative embodiments can be used to implement the techniques disclosed herein. Those skilled in the art will appreciate that the embodiments described herein or certain features of the embodiments can be combined to obtain other embodiments for practicing the techniques described in this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the broadest scope consistent with the principles and novel features disclosed herein.

[0104] The flowcharts and block diagrams in the figures illustrate examples of the architecture, functionality, and operation of possible implementations of systems, methods, and apparatuses according to various embodiments. It should be noted that in some alternative implementations, the functions marked in the boxes may occur outside the order in which they are marked in the figures. For example, depending on the functions involved, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order. Similarly, in methods consistent with the various embodiments, such methods may include additional steps, and certain steps may be omitted or combined.

[0105] It should be understood that the described embodiments are not mutually exclusive. Elements, components, materials or steps described in conjunction with an exemplary embodiment may be combined with or eliminated from other embodiments in a suitable manner to achieve the desired design purpose.

[0106] References to “some embodiments” or “some exemplary embodiments” herein mean that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. The phrases “one embodiment,” “some embodiments,” or “another embodiment” appearing throughout this disclosure do not necessarily refer to the same embodiment, nor are they necessarily separate or alternative embodiments that must be mutually exclusive with other embodiments.

[0107] Furthermore, the articles “a” and “an” used in this disclosure and the appended claims should generally be understood to mean “one or more”, unless otherwise specified or clearly indicated by the context to be in the singular form.

[0108] Although the elements in the following method claims (if any) are recited in a particular order, these elements are not necessarily intended to be limited to being implemented in that particular order unless the claims otherwise imply a particular order for implementing some or all of these elements.

[0109] It should be understood that certain features of this disclosure described in the context of various separate embodiments for clarity may also be provided in combination in a single embodiment. Conversely, various features of this specification described in the context of a single embodiment for brevity may also be provided separately, or in any suitable sub-combination, or appropriately in any other described embodiment of this specification. Certain features described in the context of various embodiments are not essential features of those embodiments unless otherwise stated.

[0110] It will be further understood that those skilled in the art can make various modifications, substitutions, and alterations to the details, materials, and arrangements of the components described and illustrated for the purpose of explaining the nature of the described embodiments, without departing from the scope. Accordingly, the appended claims cover all such substitutions, modifications, and alterations falling on the aspects of the claims.

[0111] Clause 1: Methods for communication between nodes, including: Communication from a first node to a second node is performed on a first communication path, wherein the first communication path is one of a device-to-device communication path, a device-to-network communication path, or a global navigation satellite system-to-network path; The first node automatically switches from the first communication path to a second communication path, wherein the second communication path is another of the device-to-device communication path, the device-to-network communication path, or the Global Navigation Satellite System-to-Network path, the second communication path is different from the first communication path, and the switching is based on one or more triggers; and Communication from the first node to the second node is performed on the second communication path.

[0112] Clause 2: The method described in Clause 1, wherein the one or more triggers include one or more of the following: The first node is within the network coverage area; The first node is outside the network coverage area; The first node is within the coverage area of ​​the Global Navigation Satellite System (GNSS); The first node is outside the GNSS coverage area; Radio link failure; Under the condition that network access is prohibited in residential areas; Under network failure conditions; Under the condition that the radio interface congestion level exceeds, reaches, or falls below one or more of the congestion thresholds; Several surrounding nodes that support sidelink communication; Several surrounding nodes having sidelink communication connections to the first node; The accuracy of one or more radio interfaces, including the accuracy of positioning information received via one or more radio interfaces or the quality of service of one or more radio interfaces; Delay of one or more radio interfaces; The battery level of the first node; Detection of physical layer problems; Reconfiguration after synchronization failure; Under the condition that the first node receives several consecutive asynchronous instructions; Under the condition that the first node receives several consecutive synchronization instructions; Under the condition that the first node receives a random access problem indication from the media access control layer; Under the condition that several radio link control retransmissions have been achieved; Under the condition that a consistent uplink listen-before-talk failure indication is received from the media access control layer; When the timer expires; The position of the first node; The speed of the first node; The direction of movement of the first node; When a request for a service to be provided by the first node is received from another node; The first node needs to conserve power; The first node is in the process of receiving configuration via the radio interface; The first node is in the process of receiving resource allocation via the radio interface; or The first node is a node of the type carried by pedestrians, a node of the type fixed in an electric vehicle, a node of the type fixed in a non-electric vehicle, or a node of other types.

[0113] Clause 3: The method described in Clause 2, wherein the first node is any of the following: mobile device, user equipment, roadside unit, evolved Node B (eNB), next-generation Node B (gNB), mobility management entity (MME), access and mobility management function (AMF), or other network infrastructure equipment.

[0114] Clause 4: The method described in Clause 2, wherein some or all of the one or more triggers are related to side link communication.

[0115] Clause 5: The method described in Clause 1, wherein: Some or all of the one or more triggers have associated thresholds; and The switching is performed when one or more of the criteria associated with the one or more triggers exceed, reach, or fall below the associated threshold.

[0116] Clause 6: The method described in Clause 1, wherein the switching is performed only if the required quality of service associated with the first communication path is not achieved.

[0117] Clause 7: The method according to Clause 1, wherein the first communication path and the second communication path are used for device positioning.

[0118] Clause 8: The method described in Clause 7, wherein the switching is performed only if the required positioning accuracy related to the first communication path is not achieved.

[0119] Clause 9: The method described in Clause 1, wherein the switching further comprises: Based on the first set of one or more triggers, the first node is switched from the first communication path to the second communication path; and Based on the second set of one or more triggers, the first node is switched from the second communication path to the first communication path.

[0120] Clause 10: The method according to Clause 9, wherein the one or more triggers of at least one of the first set or the second set are symmetrical depending on the direction of the switching.

[0121] Clause 11: The method according to Clause 9, wherein the one or more triggers of at least one of the first set or the second set are asymmetric depending on the direction of the switching.

[0122] Clause 12: The method according to Clause 9, wherein the one or more triggers of at least one of the first set or the second set include a hysteresis between two or more values ​​associated with the direction of the switching.

[0123] Clause 13: The method described in Clause 1, wherein: The switching is also based on the device history of the first node; and The device history includes several triggers that have become valid within a predetermined time period.

[0124] Clause 14: The method described in Clause 13, wherein the plurality of triggers that become effective further includes one or more of exceeding one or more predetermined values, reaching one or more predetermined values, or falling below one or more predetermined values.

[0125] Clause 15: The method described in Clause 1, wherein: The switching is performed under the condition that several triggers become effective within a predetermined time period.

[0126] Clause 16: The method according to Clause 15, wherein the plurality of triggers that become effective further includes one or more of exceeding one or more predetermined values, reaching one or more predetermined values, or falling below one or more predetermined values.

[0127] Clause 17: The method described in Clause 1, wherein the one or more triggers are received by the first node.

[0128] Clause 18: The method described pursuant to Clause 1 further includes: The second communication path is activated based on one or more of the aforementioned triggers.

[0129] Clause 19: The method described in Clause 1 further includes: Based on one or more triggers, communication from the first node to the second node is performed on both the first communication path and the second communication path.

[0130] Clause 20: The method described in Clause 1 further includes: After completing the switch from the first communication path to the second communication path, a timer is set; and To prevent the first node from switching to another communication path until the timer expires.

[0131] Clause 21: A first node for communicating with a second node, the first node comprising: Memory configured to store instructions; and A processor configured to execute the instructions stored in the memory to: Communication from the first node to the second node is carried out on a first communication path, wherein the first communication path is one of a device-to-device communication path, a device-to-network communication path, or a global navigation satellite system-to-network path; The first node automatically switches from the first communication path to a second communication path, wherein the second communication path is another of the device-to-device communication path, the device-to-network communication path, or the Global Navigation Satellite System-to-Network path, the second communication path is different from the first communication path, and the switching is based on one or more triggers; and Communication from the first node to the second node is performed on the second communication path.

[0132] Clause 22: The first node as described in Clause 21, wherein the one or more triggers include one or more of the following: The first node is within the network coverage area; The first node is outside the network coverage area; The first node is within the coverage area of ​​the Global Navigation Satellite System (GNSS); The first node is outside the GNSS coverage area; Radio link failure; Under the condition that network access is prohibited in residential areas; Under network failure conditions; Under the condition that the radio interface congestion level exceeds, reaches, or falls below one or more of the congestion thresholds; Several surrounding nodes that support sidelink communication; Several surrounding nodes having sidelink communication connections to the first node; The accuracy of one or more radio interfaces, including the accuracy of positioning information received via one or more radio interfaces or the quality of service of one or more radio interfaces; Delay of one or more radio interfaces; The battery level of the first node; Detection of physical layer problems; Reconfiguration after synchronization failure; Under the condition that the first node receives several consecutive asynchronous instructions; Under the condition that the first node receives several consecutive synchronization instructions; Under the condition that the first node receives a random access problem indication from the media access control layer; Under the condition that several radio link control retransmissions have been achieved; Under the condition that a consistent uplink listen-before-talk failure indication is received from the media access control layer; When the timer expires; The position of the first node; The speed of the first node; The direction of movement of the first node; When a request for a service to be provided by the first node is received from another node; The first node needs to conserve power; The first node is in the process of receiving configuration via the radio interface; The first node is in the process of receiving resource allocation via the radio interface; or The first node is a node of the type carried by pedestrians, a node of the type fixed in an electric vehicle, a node of the type fixed in a non-electric vehicle, or a node of other types.

[0133] Clause 23: The first node as described in Clause 22, wherein the first node is any of the following: mobile device, user equipment, roadside unit, evolved Node B (eNB), next-generation Node B (gNB), mobility management entity (MME), access and mobility management function (AMF), or other network infrastructure equipment.

[0134] Clause 24: The first node as described in Clause 22, wherein some or all of the one or more triggers are related to side link communication.

[0135] Clause 25: The first node as described in Clause 21, wherein: Some or all of the one or more triggers have associated thresholds; and The processor is further configured to perform the switching when one or more of the criteria associated with the one or more triggers exceed, reach, or fall below the associated threshold.

[0136] Clause 26: The first node as described in Clause 21, wherein the processor is further configured to perform the switching only if the required quality of service associated with the first communication path is not achieved.

[0137] Clause 27: The first node as described in Clause 21, wherein the first communication path and the second communication path are used for device positioning.

[0138] Clause 28: The first node as described in Clause 27, wherein the processor is further configured to perform the switching only if the required positioning accuracy associated with the first communication path is not achieved.

[0139] Clause 29: The first node as described in Clause 21, wherein the processor is further configured to: Based on the first set of one or more triggers, the first node is switched from the first communication path to the second communication path; and Based on the second set of one or more triggers, the first node is switched from the second communication path to the first communication path.

[0140] Clause 30: The first node as described in Clause 29, wherein the one or more triggers of at least one of the first set or the second set are symmetrical depending on the direction of the switching.

[0141] Clause 31: The first node as described in Clause 29, wherein the one or more triggers of at least one of the first set or the second set are asymmetric depending on the direction of the switching.

[0142] Clause 32: The first node as described in Clause 29, wherein the one or more triggers of at least one of the first set or the second set include a hysteresis between two or more values ​​associated with the direction of the switching.

[0143] Clause 33: The first node as described in Clause 21, wherein: The processor is further configured to perform the handover based on the device history of the first node; and The device history includes several triggers that have become valid within a predetermined time period.

[0144] Clause 34: The first node as described in Clause 33, wherein the plurality of triggers that become effective further include one or more of exceeding one or more predetermined values, reaching one or more predetermined values, or falling below one or more predetermined values.

[0145] Clause 35: The first node as described in Clause 21, wherein: The processor is further configured to perform the switching under the condition that the plurality of triggers become effective within a predetermined time period.

[0146] Clause 36: The first node as described in Clause 35, wherein the plurality of triggers that become effective further include one or more of exceeding one or more predetermined values, reaching one or more predetermined values, or falling below one or more predetermined values.

[0147] Clause 37: The first node as described in Clause 21, wherein the one or more triggers are received by the first node.

[0148] Clause 38: The first node as described in Clause 21, wherein the processor is further configured to: The second communication path is activated based on one or more of the aforementioned triggers.

[0149] Clause 39: The first node as described in Clause 21, wherein the processor is further configured to: Based on one or more triggers, communication from the first node to the second node is performed on both the first communication path and the second communication path.

[0150] Clause 40: The first node as described in Clause 21, wherein the processor is further configured to: After completing the switch from the first communication path to the second communication path, a timer is set; and To prevent the first node from switching to another communication path until the timer expires.

[0151] Clause 41: A non-transitory computer-readable medium storing instructions executable by one or more processors at a first node in a communication network to perform a method comprising: Communication from the first node to the second node is carried out on a first communication path, wherein the first communication path is one of a device-to-device communication path, a device-to-network communication path, or a global navigation satellite system-to-network path; The first node automatically switches from the first communication path to a second communication path, wherein the second communication path is another of the device-to-device communication path, the device-to-network communication path, or the Global Navigation Satellite System-to-Network path, the second communication path is different from the first communication path, and the switching is based on one or more triggers; and Communication from the first node to the second node is performed on the second communication path.

Claims

1. Methods for communication between nodes, including: Communication from a first node to a second node is performed on a first communication path, wherein the first communication path is one of a device-to-device communication path, a device-to-network communication path, or a global navigation satellite system-to-network path; The first node automatically switches from the first communication path to a second communication path, wherein the second communication path is another of the device-to-device communication path, the device-to-network communication path, or the Global Navigation Satellite System-to-Network path, wherein the second communication path is different from the first communication path, and the switching is based on one or more triggers; and Communication from the first node to the second node is performed on the second communication path.

2. The method according to claim 1, wherein, The one or more triggers include one or more of the following: The first node is within the network coverage area; The first node is outside the network coverage area; The first node is within the coverage area of ​​the Global Navigation Satellite System (GNSS); The first node is outside the GNSS coverage area; Radio link failure; Under the condition that network access is prohibited in residential areas; Under network failure conditions; Under the condition that the radio interface congestion level exceeds, reaches, or falls below one or more of the congestion thresholds; Several surrounding nodes that support sidelink communication; Several surrounding nodes having sidelink communication connections to the first node; The accuracy of one or more radio interfaces, including the accuracy of positioning information received via one or more radio interfaces or the quality of service of one or more radio interfaces; Delay of one or more radio interfaces; The battery level of the first node; Detection of physical layer problems; Reconfiguration after synchronization failure; Under the condition that the first node receives several consecutive asynchronous instructions; Under the condition that the first node receives several consecutive synchronization instructions; Under the condition that the first node receives a random access problem indication from the media access control layer; Under the condition that several radio link control retransmissions have been achieved; Under the condition that a consistent uplink listen-before-talk failure indication is received from the media access control layer; When the timer expires; The position of the first node; The speed of the first node; The direction of movement of the first node; When a request for a service to be provided by the first node is received from another node; The first node needs to conserve power; The first node is in the process of receiving configuration via the radio interface; The first node is in the process of receiving resource allocation via the radio interface; or The first node is a node of the type carried by pedestrians, a node of the type fixed in an electric vehicle, a node of the type fixed in a non-electric vehicle, or a node of other types.

3. The method according to claim 2, wherein, The first node is any of the following: mobile device, user equipment, roadside unit, evolved Node B (eNB), next-generation Node B (gNB), mobility management entity (MME), access and mobility management function (AMF), or other network infrastructure equipment.

4. The method according to claim 2, wherein, Some or all of the one or more triggers are related to side link communication.

5. The method according to claim 1, wherein: Some or all of the one or more triggers have associated thresholds; and The switching is performed when one or more of the criteria associated with the one or more triggers exceed, reach, or fall below the associated threshold.

6. The method according to claim 1, wherein, The switching is performed only if the required quality of service associated with the first communication path is not achieved.

7. The method according to claim 1, wherein, The first communication path and the second communication path are used for device positioning.

8. The method according to claim 7, wherein, The switching is performed only if the required positioning accuracy associated with the first communication path is not achieved.

9. The method according to claim 1, wherein, The switching also includes: Based on the first set of one or more triggers, the first node is switched from the first communication path to the second communication path; and Based on the second set of one or more triggers, the first node is switched from the second communication path to the first communication path.

10. The method according to claim 9, wherein, The one or more triggers of at least one of the first set or the second set depend on the direction of the switching being symmetrical.

11. The method according to claim 9, wherein, The one or more triggers of at least one of the first set or the second set are asymmetric depending on the direction of the switching.

12. The method according to claim 9, wherein, The one or more triggers of at least one of the first set or the second set include a hysteresis between two or more values ​​associated with the direction of the switching.

13. The method according to claim 1, wherein: The switching is also based on the device history of the first node; and The device history includes several triggers that have become valid within a predetermined time period.

14. The method according to claim 13, wherein, The triggers that become effective also include exceeding one or more predetermined values, reaching one or more predetermined values, or falling below one or more predetermined values.

15. The method according to claim 1, wherein: The switching is performed under the condition that several triggers become effective within a predetermined time period.

16. The method according to claim 1, wherein, The one or more triggers are received by the first node.

17. The method according to claim 1, further comprising: The second communication path is activated based on one or more of the aforementioned triggers.

18. The method according to claim 1, further comprising: Based on one or more triggers, communication from the first node to the second node is performed on both the first communication path and the second communication path.

19. The method according to claim 1, further comprising: After completing the switch from the first communication path to the second communication path, a timer is set; as well as To prevent the first node from switching to another communication path until the timer expires.

20. A first node for communicating with a second node, the first node comprising: Memory configured to store instructions; as well as A processor configured to execute the instructions stored in the memory to: Communication from the first node to the second node is carried out on a first communication path, wherein the first communication path is one of a device-to-device communication path, a device-to-network communication path, or a global navigation satellite system-to-network path; The first node automatically switches from the first communication path to a second communication path, wherein the second communication path is another of the device-to-device communication path, the device-to-network communication path, or the Global Navigation Satellite System-to-Network path, the second communication path is different from the first communication path, and the switching is based on one or more triggers; and Communication from the first node to the second node is performed on the second communication path.

Images