Active switching of V2X communication from SIDELINK connection to cell connection

Through the active switching mechanism of terminal devices, the connection switching from the SL interface to the Uu interface is solved, and the delay and interrupt time problems caused by interface switching in the prior art are achieved, and more efficient V2X communication is achieved.

CN114097277BActive Publication Date: 2024-12-06ALCATEL LUCENT SHANGHAI BELL CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980098147.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2019-07-04
Publication Date
2024-12-06
Estimated Expiration
2039-07-04

AI Technical Summary

Technical Problem

In the prior art, the delay and service interruption time caused by interface handover of V2X service are long, especially during the switching process of the SL interface to the Uu interface, which cannot effectively reduce the delay and interrupt time.

Method used

Through the active switching mechanism of the terminal device, the connection switches from the SL interface to the Uu interface. After the terminal device receives the switching instructions, it directly sends a request to the network device for switching, avoids waiting for the trigger of the network device, realizes parallel connection establishment, and reduces delays and Interrupt time.

Benefits of technology

It effectively reduces the delay and service interruption time during SL to Uu interface switching, and improves the reliability and efficiency of V2X communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114097277B_ABST
    Figure CN114097277B_ABST
Patent Text Reader

Abstract

Embodiments of the present disclosure relate to devices, methods, apparatuses, and computer-readable storage media for active switching of vehicle network communications from a device-to-device connection to a connection routed by one or more network devices. In an example embodiment, a first terminal device receives an indication of a decision to switch a device-to-device connection to a connection routed by at least one network device for communication with the second terminal device via a device-to-device connection. Based on the indication received from the second terminal device, the first terminal device then determines that an active switching of the device-to-device connection to the routed connection is to be performed. The first terminal device then sends a request to a first network device among at least one network device to establish a routed connection, the request indicating a reason for the determined active switching.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of communications, and in particular to devices, methods, apparatuses, and computer-readable storage media for active switching of vehicle-to-everything (V2X) communications from a sidelink (SL) connection to a cell connection. Background Art

[0002] Currently, in the 3rd Generation Partnership Project (3GPP) Release 16, the fifth generation (5G) vehicle-to-everything (V2X) technology is being developed based on 3GPP specifications such as 3GPP TR 38.885. The following design aspects are addressed: New Radio (NR) Sidelink (SL) design for V2X; Uu enhancements for advanced V2X use cases; Uu-based SL resource allocation or configuration for Long Term Evolution (LTE) and NR; Radio Access Technology (RAT) and interface selection; Quality of Service (QoS) management; and non-co-channel coexistence between NR and LTE SL. These designs are related to unlicensed Intelligent Transport System (ITS) bands and licensed bands in frequency range 1 (FR1) and frequency range 2 (FR2) up to 52.6 GHz.

[0003] As mentioned above, interface selection is one of the aspects to be addressed in 3GPP Release 16. For example, an upper layer entity at a V2X user equipment (UE) may select and switch the air interface between a Uu interface and a PC5 interface. According to the specifications of the relevant 3GPP TR38.885, the selection of the radio interface will be performed by the UE at an upper layer such as the access stratum (AS) layer above. The selection may be based on the candidate RAT(s) associated with the service type and the availability information of different interfaces received from the AS layer (e.g., Uu interface or SL interface such as PC5 interface).

[0004] Because the availability of the Uu and SL interfaces may change dynamically, for example due to the traffic load of each interface, available resources and / or radio link quality, the interface selected by the upper layers may change from one to another during the life cycle of the V2X service. For example, when a unicast SL link has been established between two vehicle UEs for a V2X service, the upper layers may trigger an interface reselection or switch to the Uu interface, for example due to congestion of SL resources or unsatisfied quality of service (QoS) of the V2X service.

[0005] The interface reselection or switching decision in each of the involved vehicle UEs may be made independently and may therefore not be synchronized between the involved vehicle UEs of the established unicast SL connection. For example, one UE may be configured to switch from SL to Uu for an ongoing V2X service, while another UE may still keep using SL for the same V2X service. In this example, the interruption time caused by the interface switching may be extended for the ongoing V2X session. Summary of the invention

[0006] Generally, embodiments of the present disclosure provide devices, methods, apparatus, and computer-readable storage media for active switching of vehicle-to-everything (V2X) communications from a device-to-device connection to a connection routed by one or more network devices.

[0007] In a first aspect, a first terminal device is provided, comprising: at least one processor, and at least one memory, including computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the first terminal device to receive an indication of a decision to switch a device-to-device connection from a second terminal device via a device-to-device connection to a connection routed by at least one network device for communication with the second terminal device. The first terminal device is then caused to determine, based on the indication received from the second terminal device, that an active switch from the device-to-device connection to the routed connection is to be performed. The first terminal device is also caused to send a request to a first network device among the at least one network device to establish a routed connection, the request indicating a reason for the determined active switch.

[0008] In a second aspect, a second terminal device is provided, comprising: at least one processor, and at least one memory, including computer program code. The at least one memory and the computer program code are configured to, together with the at least one processor, cause the second terminal device to determine that a device-to-device connection for communicating with at least one first terminal device is to be switched to a connection routed by at least one network device. The second terminal device is also caused to send an indication of the decision to switch from the device-to-device connection to the routed connection to the at least one first terminal device and then perform the switching from the device-to-device connection to the routed connection.

[0009] In a third aspect, a method is provided. In the method, a first terminal device receives an indication of a decision to switch the device-to-device connection to a connection routed by at least one network device for communication with the second terminal device from a second terminal device via a device-to-device connection. Based on the indication received from the second terminal device, the first terminal device determines that an active switch from the device-to-device connection to the routed connection is to be performed. The first terminal device then sends a request to a first network device of the at least one network device to establish the routed connection, the request indicating a reason for the determined active switch.

[0010] In a fourth aspect, a method is provided. In the method, a second terminal device determines that a device-to-device connection for communicating with at least one first terminal device is to be switched to a connection routed by at least one network device. The second terminal device then sends an indication of the decision to switch from the device-to-device connection to the routed connection to the at least one first terminal device. In addition, the second terminal device performs a switch from the device-to-device connection to the routed connection.

[0011] In a fifth aspect, an apparatus is provided, comprising means for performing the method according to the third aspect or the fourth aspect.

[0012] In a sixth aspect, a computer readable storage medium is provided, on which a computer program is stored. The computer program, when executed by a processor of a device, causes the device to perform the method according to the third aspect or the fourth aspect.

[0013] It should be understood that the present invention summary is neither intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0015] Figure 1 illustrates an example environment in which embodiments of the present disclosure may be implemented;

[0016] Figure 2 illustrates a flow chart of an example method according to some example embodiments of the present disclosure;

[0017] Figure 3 illustrates a flow chart of an example method according to some other example embodiments of the present disclosure;

[0018] Figure 4 illustrates example signal flows according to some example embodiments of the present disclosure;

[0019] Figure 5illustrates example signal flows according to some other example embodiments of the present disclosure; and

[0020] Figure 6 A simplified block diagram of a device suitable for implementing embodiments of the present disclosure is illustrated.

[0021] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0022] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described only for illustrative purposes and help those skilled in the art to understand and implement the present disclosure, without implying any limitation on the scope of the present disclosure. The present disclosure described herein can be implemented in various ways except the way described below.

[0023] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0024] As used herein, the term "network equipment" refers to a device via which services can be provided to a terminal device in a communication network. Network equipment may include access network equipment and core network equipment. Access network equipment may also be referred to as a base station (BS) and may include any appropriate device via which a terminal device or UE may access a communication network. Examples of access network equipment or BS include relays, access points (APs), transmission points (TRPs), node Bs (NodeBs or NBs), evolved NodeBs (eNodeBs or eNBs), new radio (NR) NodeBs (gNBs), remote radio modules (RRUs), radio heads (RHs), remote radio heads (RRHs), low power nodes (such as femto, micro, etc.).

[0025] As used herein, the term "core network equipment" refers to equipment that can communicate with access network equipment and provide services to terminal devices in the core network. Examples of core network equipment may include user layer functions (UPFs), application servers, mobile switching centers (MSCs), MMEs, operation and management (O&M) nodes, operation support system (OSS) nodes, self-organizing network (SON) nodes, positioning nodes such as enhanced service mobile positioning centers (E-SMLCs), mobile data terminals (MDTs), common control network functions (CCNFs), access and mobility management functions (AMFs), and / or network slice selection functions (NSSFs).

[0026] As used herein, the term "user plane function" (UPF) refers to a device, function or component for providing various functions in the user plane in the core network. The UPF can provide interconnection between the mobile infrastructure and the data network, packet routing and forwarding, etc.

[0027] As used herein, the term "terminal device" or "user equipment" (UE) refers to any terminal device capable of wireless communication with each other or with a base station. The communication may involve sending and / or receiving wireless signals using electromagnetic signals, radio waves, infrared signals, and / or other types of signals suitable for conveying information over the air. In some example embodiments, the UE may be configured to send and / or receive information without direct human interaction. For example, the UE may send information to a network device on a predetermined schedule, when triggered by an internal or external event, or in response to a request from a website side.

[0028] Examples of UE include, but are not limited to, user equipment (UE) such as a smart phone, a wireless-enabled tablet computer, a laptop embedded device (LEE), a laptop mounted device (LME), and / or a wireless customer premises equipment (CPE). For purposes of discussion, some example embodiments will be described with reference to a UE as an example of a terminal device, and the terms "terminal device" and "user equipment" (UE) may be used interchangeably in the context of the present disclosure.

[0029] As used herein, the term "circuitry" may refer to one or more or all of the following:

[0030] (a) hardware circuit implementation only (such as implementation with analog and / or digital circuitry only) and

[0031] (b) a combination of hardware circuitry and software, such as (where applicable): (i) a combination of analog and / or digital hardware circuitry(s) and software / firmware and (ii) any portion of hardware processor(s) and software (including digital signal processor(s), software and memory(s) that work together to enable a device such as a mobile phone or server to perform various functions), and

[0032] (c) Hardware circuits and or processor(s), such as microprocessor(s) or portions of microprocessor(s), that require software (e.g., firmware) for operation, but the software may not be present when it is not required for operation.

[0033] This definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term circuitry also covers only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware implementation. For example and where applicable, the term circuitry also covers a specific claimed element, a baseband integrated circuit or a processor integrated circuit for a mobile device or a similar integrated circuit in a server, cell network device, or other computing or network device.

[0034] As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "including" and variations thereof should be understood as open-ended terms meaning "including, but not limited to." The term "based on" should be understood as "based at least in part on." The terms "one embodiment" and "embodiment" should be understood as "at least one embodiment." The term "another embodiment" should be understood as "at least one other embodiment." Other definitions (explicit and implicit) may be included below.

[0035] As used herein, the terms "first", "second", etc. can be used to describe various elements in this article, and these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, the first element can be named as the second element, and similarly, the second element can be named as the first element, without departing from the scope of the exemplary embodiment. As used herein, the term "and / or" includes any and all combinations of one or more of the listed items.

[0036] Interface selection is one of the aspects to be addressed in 3GPP Release 16. For example, 3GPP TR 38.885 in Part 8 states the following:

[0037]

[0038]

[0039] According to the specifications of the relevant 3GPP TR 38.885, the selection of the radio interface will be performed by the UE at an upper layer (such as above the access stratum (AS) layer). Typically, the interface reselection or switching decision in each of the vehicle UEs involved can be made independently. Therefore, the interface reselection among the vehicle UEs involved may be asynchronous, which may extend the interruption time due to the interface switching initiated at one of the UEs involved for the ongoing V2X session. In addition, the UEs involved may be in an IDLE / INACTIVE or CONNECTED / ACTIVE state of one or more serving cells belonging to one or more public land mobile networks (PLMNs). Therefore, the end-to-end (E2E) connection via the Uu interface between the UEs involved can be enabled using different routes (or data forwarding paths). For example, when the UEs involved are served by one NR NodeB (e.g., gNB), the E2E connection can be routed via the gNB and not through the core network when the optimal data forwarding path is applied. In another example, when the involved UEs are served by different PLMNs, the E2E connection may be routed through the core network via some common server.

[0040] According to the connection and session management procedures defined in NR (e.g., in 3GPP TS 23.501 and 23.502), when one UE (denoted as UE#1) is configured to switch from the SL interface to the Uu interface for an ongoing V2X service, UE#1 needs to establish a new protocol data unit (PDU) session to the network (NW) or modify an existing PDU session to request the V2X service to be resumed from the V2X application server. The V2X application server can then request the NW to reach another UE (denoted as UE#2) and trigger UE#2 to establish or modify a corresponding PDU session to the NW for the same V2X service if the interface switch has not been triggered in UE#2. If UE#2 is in an idle state, the NW needs to page UE#2 first. Then, UE#2 needs to enter the connected state of the NW and initiate the PDU session establishment procedure. Only after the PDU session has been established by both UE#1 and UE#2, the communication for the ongoing V2X service can be resumed.

[0041] There is a need to reduce the latency in establishing an E2E connection via the Uu interface for ongoing unicast / multicast SL communication of the UEs when one of the UEs decides to reselect the Uu interface and thus switches from the SL interface to the Uu interface.

[0042] Embodiments of the present disclosure provide a mechanism for actively switching an E2E connection between two terminal devices (e.g., UE) to reduce latency and service interruption during interface reselection or switching from an SL interface to a Uu interface. According to the mechanism, when a terminal device determines that a device-to-device (D2D) connection (e.g., a sidelink connection) used to communicate with another terminal device is to be switched to a connection routed by one or more network devices, the terminal device sends an indication or request for switching to the other terminal device via the SL. Then, the other terminal device can actively initiate a switch from the D2D connection to the routed connection, instead of waiting for a trigger to initiate the switch from the network or (multiple) network devices.

[0043] In this way, the connection or interface switching from SL to Uu can be actively performed by the terminal device. Typically, the receiver UE will be triggered by the network to establish a connection via the Uu interface only after the sender UE has established its connection via the Uu interface. According to the mechanism of the present disclosure, the receiver UE can actively switch the connection or interface based on a request received from the sender UE via the SL. Therefore, the connection establishment for individual UEs via Uu can be performed in a parallel manner, which can reduce the delay for establishing an E2E connection via the Uu interface caused by the interface switching initiated by the sender UE.

[0044] Figure 1 An example environment 100 is shown in which embodiments of the present disclosure may be implemented. The environment 100, which is part of a communication network, includes two terminal devices 105 and 110, two base stations (BSs) 115 and 120, and two user layer functions (UPFs) 125 and 130, which will be referred to as the first terminal device 105, the second terminal device 110, the first base station 115, the second base station 120, the first UPF 125, and the second UPF 130, respectively, for the purpose of discussion.

[0045] It should be understood that the two terminal devices, base stations and / or UPFs are shown in FIG. Figure 1 Any suitable number of terminal devices, base stations and UPFs may be included in the environment 100. In addition, the environment 100 may include any suitable other devices, functions and elements such as a V2X application server.

[0046] The first terminal device 105 can communicate with the second terminal device 110 via a D2D connection. In this example, the D2D connection is implemented by a sidelink (SL) connection through a sidelink interface 135. Applications of D2D may include V2X, public safety, Internet of Things (IoT), proximity communications, and the like. The communication may be performed using unicast or multicast in any appropriate D2D transmission mode. The D2D transmission mode may include SL transmission mode 1 (with network-scheduled resource allocation) or SL transmission mode 2 (with UE-selected resource allocation). For example, the second terminal device 110 may multicast a signal to other terminal devices (not shown) other than the first terminal device 105. The first terminal device 105 and the second terminal device 110 may also communicate with the first BS 115 and the second BS 120 via Uu interfaces 140-1 and 140-2 (collectively or individually referred to as Uu interfaces 140). The first base station 115 and the second base station 120 may communicate via an X2 or Xn interface 145 or via a first UPF 125 and a second UPF 130.

[0047] Communications in environment 100 may follow any appropriate communication standards or protocols, such as Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), LTE Advanced (LTE-A), Fifth Generation (5G) NR, Wireless Fidelity (Wi-Fi), and Worldwide Interoperability for Microwave Access (WiMAX) standards, and employ any appropriate communication technology, including, for example, Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), Code Division Multiplexing (CDM), Bluetooth, ZigBee, Machine Type Communication (MTC), Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC), Ultra-Reliable Low Latency Communication (URLLC), Carrier Aggregation (CA), Dual Connectivity (DC), New Radio Unlicensed (NR-U), and V2X technology.

[0048] It should be understood that the two terminal devices 105 and 110 are shown as being served by different base stations 115 and 120 and different UPFs 125 and 130 for illustration purposes only and without implying any limitation. In some example embodiments, the two terminal devices 105 and 110 may be served by the same UPF or even by the same BS.

[0049] In the environment 100, the second terminal device 110 may send data to the first terminal device 105 via the SL connection through the SL interface 135. If the second terminal device 110 determines that the SL connection is to be switched to a Uu connection routed by network devices such as the BSs 115 and 120 and / or the UPFs 125 and 130, the second terminal device 110 will send an indication of the decision to switch the SL connection to the Uu connection to the first terminal device 105. The first terminal device 105 may then initiate the step of routing the Uu connection based on the received indication message.

[0050] Figure 2 FIG. 2 is a flow chart showing an example method 200 for connection switching according to some example embodiments of the present disclosure. The method 200 may be performed as follows: Figure 1 For the purpose of discussion, reference will be made to the second terminal device 110 shown in FIG. Figure 1 Method 200 is described.

[0051] As shown, at block 205 the second terminal device 110 determines that the D2D connection for communicating with the first terminal device 105 is to be switched to a connection routed by at least one network device, such as the first and second BSs 115 , 120 and even UPFs 125 and 130 .

[0052] This determination can be performed by the second terminal device 110 according to any appropriate rules. The rules can involve many events or reasons based on the network configuration. For example, if the second terminal device 110 receives one or more scheduling request rejections for communication via the D2D connection, the second terminal device 110 can determine that the connection switching is triggered. These rejections can be received (dis)continuously by the second terminal device 110 in a row. The number of rejections that trigger the switching can be configured by the network or depending on the specific implementation at the second terminal device 110.

[0053] As another example, if the second terminal device 110 may receive a scheduling request rejection indicating a handover, the second terminal device 110 may determine that a handover is to be triggered. The rejection may be received after the second terminal device 110 sends a request for transmission resources for D2D communication.

[0054] As a further example, if the traffic load via the D2D connection is too high, for example above a threshold load, the second terminal device 110 may determine that a handover is triggered. The traffic load may be determined or evaluated at the second terminal device 110. Alternatively or in addition, the second terminal device 110 may receive an indication from the network that the traffic load via the first connection is above a certain threshold load. The indication may be sent by the network in a broadcast manner via a system information block or in a dedicated manner by RRC signaling or downlink control information (DCI).

[0055] In some example embodiments, the second terminal device 110 may receive an indication from an upper layer above the access stratum (AS) layer (such as a V2X layer or an application layer) that the device-to-device connection is to be switched to a routed connection. Alternatively or in addition, the second terminal device 110 may receive an indication from the AS layer that a specific device-to-device transmission mode (such as SL Mode 1) is not available. In addition, the second terminal device 110 may make a decision for switching.

[0056] In some example embodiments, the second terminal device 110 may be configured by the network or by an upper layer (eg, above the AS layer) to switch the air interface from the SL interface 135 (such as the PC5 interface) to the Uu interface 140. Therefore, the second terminal device 110 may determine that a connection switch is to be performed.

[0057] After the switch is determined, at block 210, the second terminal device 110 sends an indication of the decision to switch from the D2D connection to the routed connection to the first terminal device 110. The indication is sent via the D2D connection. Using this indication, the second terminal device 110 can, for example, indicate or notify the first terminal device 105 via SL that the ongoing SL communication is to be switched to the Uu interface. With this indication, the first terminal device knows that it should start preparing for the connection via the Uu interface instead of waiting for an indication from the network or (multiple) network devices.

[0058] The indication may be sent via unicast or multicast in SL mode 1 or mode 2. In some example embodiments, the request may be sent in an application layer message. In some other example embodiments, the request may be sent in an AS layer message to further reduce the time of the handover.

[0059] In some example embodiments, the indication may include context information of the second terminal device 110, such as a cell identifier (ID) and a PLMN ID. The indication may include other UE assistance information, such as a cell access temporary identifier of the second terminal device 110. The cell access temporary identifier may be a non-access stratum (NAS) ID, such as a temporary mobile subscriber identity (TMSI), when the second terminal device 110 is in an idle state, or an AS ID, such as an inactive radio network temporary identifier (I-RNTI), when the second terminal device 110 is in an inactive state, or a cell radio network temporary identifier (C-RNTI) when the second terminal device 110 is in a connected state. These contexts may help the first terminal device 105 to perform a connection handover. Example embodiments in this regard will be described in detail in reference to Figure 3 In the following paragraphs.

[0060] The indication may be sent by the second terminal device 110 as early as possible, for example, immediately after the second terminal device 110 determines that a handover is to be performed, regardless of whether the second terminal device 110 is in a connected state. For example, if the network supports routing of V2X services via BSs 115 and 120 for an optimal data forwarding path, the second terminal device 110 may send the indication immediately.

[0061] In some example embodiments, the second terminal device 110 may send an indication after the handover is allowed by the network. For example, after the second terminal device 110 determines that the handover is to be triggered, the second terminal device 110 may first send a request for the handover to a network device, such as a second base station 120. For example, the request may be implicitly or explicitly carried by an RRC establishment request message. If a response indicating that the handover is allowed is received from the base station 120, the second terminal device 110 may send an indication to the first terminal device 105. For example, the response may be implicitly or explicitly carried by an RRC connection establishment message. In this way, the admission control of the requested handover by the network may be guaranteed to the second terminal device 110 before the first terminal device 105 is triggered by an indication for handover via SL to initiate a connection via a route via Uu.

[0062] At block 215, the second terminal device 110 performs a handover from the D2D connection to the routed connection. In some example embodiments, the second terminal device 110 may determine whether the communication via the routed connection requires a regular cell access PDU session. In the context of the present disclosure, a regular cell access PDU session refers to a PDU session that utilizes a regular path service routed via a core network (CN) or a network device in the CN (such as UPF 125 and / or 130).

[0063] For example, the second terminal device 110 may know the serving cell of the first terminal device 105 by exchanging information with the first terminal device 105. If the first terminal device 105 and the second terminal device 110 are served by different PLMNs, the second terminal device 110 may determine that a PDU session served by the CN is required. As another example, the second terminal device 110 may receive an indication from a network such as the second BS 120 indicating whether a PDU session is required.

[0064] The indication sent to the first terminal device 105 may indicate whether the second communication requires a PDU session served by the CN. For example, the second terminal device 110 may know the serving cell of the first terminal device 105 by exchanging information with the first terminal device 105. If the first terminal device 105 and the second terminal device 110 are served by different PLMNs, the second terminal device 110 may determine that a PDU session served by the CN is required and use the indication to indicate the requirement. As another example, the second terminal device 110 may determine the requirement for the PDU session according to the configuration by the network.

[0065] If a PDU session served by the CN is needed, then when the second terminal device 110 is in a connected state, the second terminal device 110 can determine a PDU session for communication via a connection routed, for example, through the Uu interface 140. The second terminal device 110 can determine whether an appropriate PDU session is available. For example, the second terminal device 110 can have multiple PDU sessions to different APNs. The second terminal device 110 can determine whether there is a PDU session connected to the APN for V2X services. If the PDU session is determined, the second terminal device 110 determines whether an appropriate QoS flow for the PDU session is available. For example, from multiple QoS flows, the second terminal device 110 determines a QoS flow that can support the QoS requirements of the ongoing V2X service.

[0066] If an appropriate PDU session is available but no appropriate QoS flow for the PDU session is available, the second terminal device 110 may add a new QoS flow to the PDU session used for communication. Alternatively, the second terminal device 110 may adjust the QoS flow of the PDU session used for communication. If no appropriate PDU session is available, the second terminal device 110 may initiate the establishment of a PDU session. If the second terminal device 110 is in an idle or inactive state, the second terminal device 110 may first establish an RRC connection.

[0067] In some example embodiments, the second terminal device 110 may send an indication to the first terminal device 105 after the second terminal device 110 has established an RRC connection and initiated a PDU session establishment. This may ensure that the second terminal device 110 may pass admission control to the network before it sends the indication. In this case, the indication may indicate to the first terminal device 105 whether a PDU session is required. The indication may help the first terminal device 105 to determine and immediately initiate an appropriate Uu connection establishment.

[0068] In some example embodiments, the final decision on the requirement for a PDU session may be obtained on the network side. Many aspects may be considered, including, for example, the capabilities and / or available capabilities of the use of the X2 or Xn interface between the base stations 115 and 120 serving the terminal devices 105 and 110. In this case, the indication may indicate to the first terminal device 105 to wait for an indication from the network whether further indication of the PDU session is required. Upon receiving the indication, the first terminal device 105 actively transitions to the RRC_Connection / Active state without waiting for a trigger from the network or (multiple) network devices.

[0069] This determination and establishment of the PDU session may be performed after the indication is sent to the first terminal device 105. Thus, the connection establishment may be initiated in parallel at both the first terminal device 105 and the second terminal device 110. Thus, latency or service interruption time may be reduced.

[0070] In some example embodiments, after sending the indication for switching to the first terminal device 105, the second terminal device 110 may temporarily continue D2D communication with the first terminal device 105 via the D2D connection, for example in SL mode 2, before the routed Uu connection is established. In this way, service interruption may be further reduced.

[0071] In some example embodiments, the second terminal device 110 may receive a confirmation for the handover from the first terminal device 105 via the D2D connection. Based on the confirmation, the second terminal device 110 may determine that the handover is confirmed or even completed by the first terminal device 105. The second terminal device 110 may then prepare for communication with the first terminal device 105 via a connection routed by one or more network devices, such as the first BS 115 and the second BS 120 and even the first UPF 125 and the second UPF 130.

[0072] Figure 3 FIG. 3 is a flow chart showing an example method 300 for connection switching according to some example embodiments of the present disclosure. The method 300 may be performed as follows: Figure 1 For the purpose of discussion, reference will be made to the first terminal device 105 shown in FIG. Figure 1 Method 300 is described.

[0073] At block 305, the first terminal device 105 receives an indication of a decision to switch the D2D connection to a connection routed by one or more network devices, such as BSs 115 and 120 and / or UPFs 125 and 130, from the second terminal device 110 via the D2D connection. At block 310, based on the indication received from the second terminal device 110, the first terminal device 105 determines that an active switch from the device-to-device connection to the routed connection is to be performed.

[0074] In some example embodiments, the first terminal device 105 may determine whether the second communication requires a PDU session served by the CN. For example, in an example embodiment in which the indication indicates that a PDU session is required, the first terminal device 105 may determine that the second communication requires a PDU session. As another example, if the first terminal device 105 receives an indication from the second terminal device 110 to wait for further indication from the network indicating whether a PDU session is required, and receives an indication from a network device such as the first base station 115 that a packet data unit session is required, then the first terminal device 105 may determine that the second communication requires a PDU session.

[0075] In some example embodiments, if the indication contains the context of the second terminal device 110, such as a cell ID and / or a PLMN ID, the first terminal device 105 may prioritize the reselection of the cell or PLMN serving the second terminal device 110. For example, the first terminal device 105 may determine whether it can be served by the same cell or in the same PLMN as the second terminal device 110. The first terminal device 105 may access the serving cell or PLMN of the second terminal device 110. If both terminal devices are served by the same cell or the same PLMN, the first terminal device 105 may send an indication of handover to the first BS 115. The indication contains the received UE context of the second terminal device 110, such as a radio class identifier for SL to Uu handover and some UE assistance information, so that the network can decide and select the optimal route for communication between the first terminal device 105 and the second terminal device 110.

[0076] If the connection can be routed by the network device, the first terminal device 105 can determine whether a PDU session served by the CN is required. As an example, if the 5G radio access network (5G-RAN) has the ability to reroute the uplink (UL) transmission of the second terminal device 110 to the downlink (DL) transmission of the first terminal device 105 and identifies that both the first terminal device 105 and the second terminal device 110 are connected to the same 5G-RAN node or different 5G-RAN nodes using the Xn interface, then the 5G-RAN can indicate to the first terminal device 105 that the 5G-RAN will be responsible for the second communication, which means that the ongoing V2X service does not require a PDU session.

[0077] In the case where a PDU session is required, if the first terminal device 105 is in a connected state, the first terminal device 105 can determine a PDU session for communication via a routed Uu connection. The first terminal device 105 can determine whether an appropriate PDU session is available and whether an appropriate QoS flow for the PDU session is available. If an appropriate PDU session is available but no appropriate QoS flow for the PDU session is available, the first terminal device 105 can add a new QoS flow to the PDU session for communication or adjust the QoS flow of the PDU session for communication. If no appropriate PDU session is available, the first terminal device 105 can initiate the establishment of a PDU session.

[0078] At block 315, the first terminal device 105 sends a request to the first network device (e.g., the first BS 115) in at least one network device to establish a routed connection. The request indicates the cause for the determined active handover. For example, if the first terminal device 105 is in the RRC IDLE or INACTIVE state, the first terminal device 105 can be triggered by the handover indication to initiate the RRC connection establishment / recovery process without waiting for the incoming call from the second terminal device 110 until the data of the second terminal device 110 arrives via the public application server. In some example embodiments, the first terminal device 105 may send a request for establishing or restoring an RRC connection after receiving the handover indication. The request may include the cause for the determined active handover. As an example, a new RRC connection establishment / recovery cause may be used to indicate an expected incoming call due to a connection handover. The first terminal device 105 may indicate the cause in the establishment / recovery request to indicate a connection handover. This can help the first terminal device 105 to obtain a connection with the 5G-RAN as quickly as possible. Therefore, the first terminal device 105 can be ready to send a PDU session-related request to the NW or receive a trigger to establish a PDU session with the second terminal device 110 or other requests for a target V2X service.

[0079] In some example embodiments, the active connection establishment for the first terminal device 105 may bypass or at least postpone a portion of the Authentication Authorization Accounting (AAA) process until the common application server attempts to reach the first terminal device 105. In this case, the serving network of the first terminal device 105 may configure some enforced deactivation / release timers for the established connection for the first terminal device 105. The configured timers start after the establishment of the PDU session for the first terminal device 105. If the network does not receive any actual data for the established PDU session or an explicit request to update the timer from the second terminal device 120, the PDU session is autonomously deactivated or released.

[0080] After both the first terminal device 105 and the second terminal device 110 establish a connection to the NW, V2X communications for the ongoing V2X service may be resumed via the connection, such as over the Uu interface 140. In some example embodiments, the first terminal device 105 may send a confirmation for the handover to the second terminal device 110 via the D2D connection to cause initiation of communications via the routed connection.

[0081] In conventional methods, the first terminal device 105 may react only after data from the second terminal device 110 arrives, which will trigger paging for the first terminal device 105 when the first terminal device 105 is in an inactive or idle state. The handover suffers from significant delays because the PDU session establishment for the second terminal device 110 may need to be completed, data from the second terminal device 110 to the first terminal device 105 via the server may be sent on the established PDU session, and the data triggers paging for the first terminal device 105 to initiate the PDU session establishment before the handover can be performed. According to an example embodiment of the present disclosure, the first terminal device 105 will actively switch the D2D connection to a connection routed by one or more network devices in response to receiving an indication from the second terminal device 110. Therefore, the connection or PDU establishment associated with the two terminal devices 105 and 110 can be performed in a parallel manner, which can reduce the delay for establishing an E2E connection via the Uu interface.

[0082] As mentioned above Figure 2 All operations and features described are equally applicable to method 300 and have similar effects. For the purpose of simplicity, details will be omitted.

[0083] Figure 4An example signal flow 400 between various devices according to some example embodiments of the present disclosure is shown. In this example, the network 405 may include different network entities, such as the first base station 115 and the second base station 120, the first UPF and the second UPF, a V2X application (APP) server, etc. The terminal devices 105 and 110 are implemented by UEs.

[0084] Initially, the second terminal device 110 performs (410) V2X transmission via SL transmission mode 1 or mode 2 to the first terminal device 105 using unicast or multicast. The second terminal device 110 determines (415) the selection of the Uu interface for switching the SL connection via the PC5 interface to the connection via the Uu interface by configuration via the network or via its upper layer. The event or reason for triggering the switching based on the network configuration may be as follows:

[0085] a) The second terminal device 110 receives one or more scheduling request rejection messages in a row. The number of rejection messages that trigger interface switching may be configured by the network or by UE implementation.

[0086] b) When the second terminal device 110 requests transmission resources for SL Mode 1, it receives a Scheduling Request Reject message containing an indication to trigger an interface switch to Uu.

[0087] c) The second terminal device 110 receives an indication from the network that the traffic load on the PC5 interface is above a certain threshold. The indication may be sent in a broadcast manner via a system information block, in a dedicated manner through RRC signaling or downlink control information (DCI).

[0088] The second terminal device 110 sends (420) an indication of the decision to switch from the SL connection to the Uu connection in SL mode 1 or mode 2 to the first terminal device 105 using unicast or multicast to trigger the interface switch from PC5 to Uu. In order to obtain a fast interface switch, the indication may be sent in the AS layer instead of in the application layer. The indication may indicate one of two options for the first terminal device 105, including:

[0089] a) The first terminal device 105 needs to prepare a PDU session to receive packets from the second terminal device 110 via Uu.

[0090] b) The first terminal device 105 shall establish an RRC connection and wait for further indication from the network whether a PDU session is required.

[0091] Additionally, the indication may contain some context information of the second terminal device 110, such as its detected cell ID, PLMN ID, UE assistance information and the like.

[0092] For example, according to the configuration of the network 405 or the UE upper layer, before the connection via the Uu interface is ready, the second terminal device 110 still performs (425) V2X communication with the first terminal device 105 in SL mode 2.

[0093] The second terminal device 110 performs (430) PDU session establishment or dedicated QoS flow establishment / modification. For example, the second terminal device 110 needs to check the following conditions:

[0094] a) whether a PDU session to the Access Point Name (APN) for V2X communication already exists, and

[0095] b) Whether the QoS flow involved in the PDU session can meet the QoS requirements of (multiple) V2X services.

[0096] Based on the above inspection:

[0097] i. If condition a) is met, that is, there is no PDU session to the APN for V2X communication, then the second terminal device 110 needs to establish a new PDU session.

[0098] ii. If condition a) is met but condition b) is not met, i.e., there is an appropriate PDU session but the QoS requirements of the (multiple) V2X services cannot be met via the (multiple) existing QoS flows, then additional QoS flows need to be established to meet the QoS requirements, or the current QoS flows need to be modified.

[0099] iii. If conditions a) and b) are met, the second terminal device 110 can utilize the current PDU session and the current QoS flow.

[0100] After receiving the indication, the first terminal device 105 needs to check whether it should establish a new PDU session or an additional QoS flow. In this example, the first terminal device 105 is in the RRC_Idle or RRC_Inactive state. Therefore, the first terminal device 105 needs to transition to the RRC_Connected state.

[0101] As shown, the first terminal device 105 first performs (435) a random access (RA) procedure. After the RA procedure, the first terminal device 105 sends (440) an RRC setup request message, in which a new cause of "expected incoming call" or "switching from SL to Uu" is indicated in the message. The new cause can help the first terminal device 105 to establish an RRC connection as quickly as possible. After receiving the RRC setup request message, the network sends (445) an RRC connection establishment message back to the first terminal device 105.

[0102] If the first terminal device 105 is already in the RRC_Connected state, the first terminal device 105 performs (450) a PDU session establishment or a dedicated QoS flow establishment / modification. For example, the first terminal device 105 may establish a new PDU session or add an additional QoS flow.

[0103] Once the PDU session is ready, the first terminal device 105 may send (455) confirmation of the switch to the second terminal device 110 in SL mode 1 or mode 2. The AS layer at the second terminal device 110 indicates the availability of the Uu interface and thus the upper layer may select the Uu interface from now on. The second terminal device 110 then performs (460) V2X communication via the Uu interface.

[0104] Figure 5 An example signal flow 500 between various devices according to some example embodiments of the present disclosure is shown.

[0105] In flow 500, the operations and actions at 510 to 525 are similar to the operations and actions at 410 to 425, and the details thereof will not be repeated for the purpose of simplicity.

[0106] In the case where both the first terminal device 105 and the second terminal device 110 are in the RRC_Inactive or RRC_Idle state, the two terminal devices 105 and 110 need to transition to the RRC_Connected state. As shown, the second terminal device 110 performs (530) RRC connection establishment. The first terminal device 105 also performs (535) RRC connection establishment. During this RRC connection establishment process, the first terminal device 105 sends a new cause of "expected incoming call" or "switching from SL to Uu" in its RRC establishment request message.

[0107] The second terminal device 110 sends (540) its own information with / without the information of the first terminal device 105 to the serving base station 120 to indicate that it wants to send V2X services to the first terminal device 105 via the Uu interface. The information of the first terminal device 105 may be collected before the decision to switch the connection or interface. Alternatively, the second terminal device 110 may query the first terminal device 105 for the required information once it decides to switch the interface. In addition, the information sent to the network 405 (such as the second base station 120) may include application layer and / or AS layer information to help the network determine the establishment of a Uu connection for the terminal device.

[0108] The network 405 makes (545) a decision whether a PDU session is needed. For example, the first base station 115 may interact with other network entities to decide whether the 5G RAN can locally route traffic from the second terminal device 110 to the first terminal device 105 without using a PDU session. The network 405 sends (550) the decision to the second terminal device 110 and also sends (555) the decision to the first terminal device 105.

[0109] For example, if the 5G RAN does not have the ability to locally route traffic from the second terminal device 110 to the first terminal device 105, the network 405 may send a message to the second terminal device 110 to indicate that the second terminal device 110 needs to establish a PDU session. If the first terminal device 105 and the second terminal device 110 are served by the same BS, a message with the same indication may be sent to the first terminal device 105. If the first terminal device 105 and the second terminal device 110 are served by two different BSs, the serving BS 120 of the second terminal device 110 may send the message to the first terminal device 105 via the serving BS 115 of the first terminal device 105.

[0110] The second terminal device 110 may then perform (560) a PDU session establishment or a dedicated QoS flow establishment / modification, and the first terminal device 105 may perform (565) a PDU session establishment or a dedicated QoS flow establishment / modification.

[0111] If the 5G RAN has the capability to locally route traffic from the second terminal device 110 to the first terminal device 105, the network 405 may send a message to the second terminal device 110 to indicate that the second terminal device 110 does not need to establish a PDU session. Therefore, the second terminal device 110 may rely on the 5G RAN to send its data to the first terminal device 105. If the first terminal device 105 and the second terminal device 110 are served by the same BS, a message with the same indication may be sent to the first terminal device 105. If the first terminal device 105 and the second terminal device 110 are served by two different BSs, the serving BS 120 of the second terminal device 110 may send a message to the first terminal device 105 through the serving BS 115 of the first terminal device 105. Afterwards, the second terminal device 110 and the first terminal device 105 skip the PDU session establishment or dedicated QoS flow establishment / modification.

[0112] The first terminal device 105 may send (570) confirmation for the switch to the second terminal device 110 in SL mode 1 or mode 2. Then, the second terminal device 110 performs (575) V2X communication to the first terminal device 105 via the Uu interface.

[0113] Figure 6 600 is a simplified block diagram of a device suitable for implementing an embodiment of the present disclosure. The device 600 may be implemented as Figure 6 At the second terminal device 110 or the first terminal device 105 shown in .

[0114] As shown, the device 600 includes a processor 610, a memory 620 coupled to the processor 610, a communication module 630 coupled to the processor 610, and a communication interface (not shown) coupled to the communication module 630. The memory 620 stores at least a program 640. The communication module is used for two-way communication, for example, via multiple antennas. The communication interface can represent any interface necessary for communication.

[0115] Program 640 is assumed to include a program that, when executed by associated processor 610, enables device 600 to operate in accordance with the procedures described herein. Figures 2 to 5 The embodiments of the present disclosure discussed operate as program instructions. The embodiments herein may be implemented by computer software executable by a processor 610 of the device 600, or by hardware, or by a combination of software and hardware. The processor 610 may be configured to implement various embodiments of the present disclosure.

[0116] The memory 620 may be of any type suitable for the local technology network and may be implemented using any appropriate data storage technology, such as, as non-limiting examples, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 620 is shown in the device 600, there may be several physically distinct memory modules in the device 600. The processor 610 may be of any type suitable for the local technology network and may include one or more of the following: as non-limiting examples, a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 600 may have multiple processors, such as a dedicated integrated circuit chip, which is time-slaved to the clock of a synchronized master processor.

[0117] When the device 600 is used as the second terminal device 110 or a part of the second terminal device 110, the processor 610 and the communication module 630 can cooperate to implement the above reference Figure 2 , Figure 4 and Figure 5 When the device 600 is used as the first terminal device 105 or a part of the first terminal device 105, the processor 610 and the communication module 630 can cooperate to implement the above reference Figures 3 to 5 The method 300 and the flows 400 and 500 described above are Figures 2 to 5All operations and features described are equally applicable to the device 600 and have similar effects. For the sake of simplicity, the details will be omitted.

[0118] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof as non-limiting examples.

[0119] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes a device executed on a target real or virtual processor to perform the above reference Figures 2 to 5 The computer executable instructions of the described methods 200 and 300 and streams 400 and 500 are such as those included in program modules. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functions of program modules can be combined or split between program modules as needed in various embodiments. The machine executable instructions for program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local storage media and remote storage media.

[0120] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, executed as an independent software group, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0121] In the context of the present disclosure, computer program codes or related data may be carried by any appropriate carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0122] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. More specific examples of computer readable storage media will include electrical connections with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disks-read-only memories (CD-ROM), digital versatile disks (DVD), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0123] In addition, although the operation is described in a specific order, this should not be understood as requiring such operation to be performed in the specific order shown or in a sequential order or the illustrated operation is performed to achieve the desired result. In some cases, multitasking and parallel processing can be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be interpreted as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Some features described in the context of the separated embodiment may also be combined and implemented in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments separately or with any suitable sub-combination.

[0124] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

[0125] Various embodiments of these techniques have been described. In addition to or as an alternative to the above, the following examples are described. Features described in any of the following examples may be utilized together with any of the other examples described herein.

[0126] In some aspects, a first terminal device comprises: at least one processor; and at least one memory comprising computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the first terminal device to: receive an indication of a decision to switch a device-to-device connection to a connection routed by at least one network device for communicating with the second terminal device from a second terminal device via a device-to-device connection; determine, based on the indication received from the second terminal device, that an active switch from the device-to-device connection to the routed connection is to be performed; and send a request to a first network device among the at least one network device to establish a routed connection, the request indicating a reason for the determined active switch.

[0127] In some example embodiments, the first terminal device is further caused to send a confirmation of the handover to the second terminal device via the device-to-device connection.

[0128] In some example embodiments, the first terminal device is further caused to: determine whether communication via the routed connection requires a packet data unit session serviced by the core network; and in response to determining that a packet data unit session is required, determine the packet data unit session.

[0129] In some example embodiments, the first terminal device is caused to determine whether the packet data unit session is required by: determining whether an indication indicates that a packet data unit session is required; and in response to indicating that a packet data unit session is required, determining that a packet data unit session is required.

[0130] In some example embodiments, the first terminal device is caused to determine whether a packet data unit session is required by: receiving an indication that a packet data unit session is required from a first network device of the at least one network device; and determining that a packet data unit session is required.

[0131] In some example embodiments, context information of a connection comprising a route associated with the second terminal device is indicated.

[0132] In some example embodiments, the context information includes at least one of a cell identifier and a public land mobile network identifier associated with the second terminal device, and the first terminal device is further caused to determine whether a packet data unit session is required by: using the cell identifier and the public land mobile network identifier to determine whether the first terminal device is served by the same cell or the same public land mobile network as the second terminal device; and in response to determining that the first terminal device is served by the same cell or the same public land mobile network as the second terminal device, sending an indication for switching to a first network device among the at least one network device, the indication including the context information.

[0133] In some example embodiments, the first terminal device is caused to determine a packet data unit session by: in response to the first terminal device being in a connected state, determining whether a packet data unit session served by the core network is available for communication via a routed connection; and in response to determining that no packet data unit session served by the core network is available, initiating establishment of a packet data unit session for communication via the routed connection.

[0134] In some example embodiments, the first terminal device is further caused to determine a packet data unit session by: in response to determining that the packet data unit session is available, determining whether a quality of service flow for the packet data unit session is available for communication via the routed connection; and in response to determining that no quality of service flow is available, adding a quality of service flow for the communication to the packet data unit session, or adjusting the quality of service flow for the packet data unit session for the communication.

[0135] In some example embodiments, the request includes a request for establishing or resuming a radio resource control connection, and the first terminal device is caused to send the request to the first network device by: in response to the first terminal device being in an idle or inactive state, sending the request for establishing or resuming a radio resource control connection, the request including a reason for the determined active switching.

[0136] In some aspects, a second terminal device comprises: at least one processor; and at least one memory comprising computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the second terminal device to: determine that a device-to-device connection for communicating with at least one first terminal device is to be switched to a connection routed by at least one network device; send an indication of the decision to switch from the device-to-device connection to the routed connection to at least one first terminal device; and perform switching from the device-to-device connection to the routed connection.

[0137] In some example embodiments, the second terminal device is further caused to receive a confirmation of the handover from the first terminal device via the device-to-device connection.

[0138] In some example embodiments, the second terminal device is caused to determine that the device-to-device connection is to be switched to a routed connection in response to: receiving a number of scheduling request rejections for communications via the device-to-device connection, the number of scheduling request rejections being above a threshold number, receiving scheduling request rejections for communications via the device-to-device connection, the scheduling request rejections indicating that the device-to-device connection is to be switched to a routed connection, determining that a traffic load via the device-to-device connection is above a threshold load, receiving an indication from an upper layer above the access layer that the device-to-device connection is to be switched to a routed connection, or receiving an indication from the access layer that a particular device-to-device transmission mode is not available.

[0139] In some example embodiments, the indication is sent in a message at an upper layer above the access layer or at the access layer.

[0140] In some example embodiments, the second terminal device is caused to send the indication by: sending a request for switching to a second network device of the at least one network device; receiving a response to the request from the second network device; and in response to the response indicating that switching is allowed, sending the indication to the first terminal device via the device-to-device connection.

[0141] In some example embodiments, the second terminal device is caused to perform the switching by: determining whether communication via the routed connection requires a packet data unit session served by the core network; and in response to determining that a packet data unit session is required, determining a packet data unit session.

[0142] In some example embodiments, the second terminal device is caused to determine whether a packet data unit session is required by: receiving an indication that a packet data unit session is required from a second network device of the at least one network device; and determining that a packet data unit session is required.

[0143] In some example embodiments, the second terminal device is caused to determine a packet data unit session by: in response to the second terminal device being in a connected state, determining whether a packet data unit session served by the core network is available for communication via the routed connection; and in response to determining that no packet data unit session served by the core network is available, initiating establishment of a packet data unit session for communication via the routed connection.

[0144] In some example embodiments, the second terminal device is further caused to determine the packet data unit session by: in response to determining that the packet data unit session is available, determining whether a quality of service flow for the packet data unit session is available for communication via the routed connection; and in response to determining that no quality of service flow is available, adding a quality of service flow for the communication to the packet data unit session, or adjusting the quality of service flow for the packet data unit session for the communication.

[0145] In some example embodiments, the second terminal device is further caused to determine the packet data unit session by initiating establishment of a radio resource control connection in response to the second terminal device being in an idle or inactive state.

[0146] In some example embodiments, the indication indicates that the packet data unit session is required for communication via the routed connection.

[0147] In some example embodiments, context information of a connection comprising a route associated with the second terminal device is indicated.

[0148] In some example embodiments, the context information comprises at least one of a cell identifier and a public land mobile network identifier associated with the second terminal device.

[0149] In some aspects, a method includes: receiving, by a first terminal device, from a second terminal device via a device-to-device connection, an indication of a decision to switch a device-to-device connection to a connection routed by at least one network device for communicating with the second terminal device; determining, based on the indication received from the second terminal device, that an active switch from the device-to-device connection to the routed connection is to be performed; and sending a request to a first network device among the at least one network device to establish the routed connection, the request indicating a reason for the determined active switch.

[0150] In some example embodiments, the method further comprises sending a confirmation for the handover to the second terminal device via the device-to-device connection.

[0151] In some example embodiments, the method further comprises: determining whether communication via the routed connection requires a packet data unit session serviced by the core network; and in response to determining that a packet data unit session is required, determining the packet data unit session.

[0152] In some example embodiments, determining whether a packet data unit session is required comprises: determining whether the indication indicates that a packet data unit session is required; and in response to the indication indicating that a packet data unit session is required, determining that a packet data unit session is required.

[0153] In some example embodiments, determining whether a packet data unit session is required includes: receiving an indication that a packet data unit session is required from a first network device of the at least one network device; and determining that a packet data unit session is required.

[0154] In some example embodiments, context information of a connection comprising a route associated with the second terminal device is indicated.

[0155] In some example embodiments, the context information includes at least one of a cell identifier and a public land mobile network identifier associated with the second terminal device, and determining whether a packet data unit session is required further includes: using the cell identifier and the public land mobile network identifier to determine whether the first terminal device is served by the same cell or the same public land mobile network as the second terminal device; and in response to determining that the first terminal device is served by the same cell or the same public land mobile network as the second terminal device, sending an indication for switching to a first network device among the at least one network device, the indication including the context information.

[0156] In some example embodiments, determining a packet data unit session includes: in response to the first terminal device being in a connected state, determining whether a packet data unit session served by the core network is available for communication via a routed connection; and in response to determining that no packet data unit session served by the core network is available, initiating establishment of a packet data unit session for communication via the routed connection.

[0157] In some example embodiments, determining a packet data unit session includes: in response to determining that the packet data unit session is available, determining whether a quality of service flow for the packet data unit session is available for communication via the routed connection; and in response to determining that no quality of service flow is available, adding a quality of service flow for the communication to the packet data unit session or adjusting the quality of service flow for the packet data unit session for the communication.

[0158] In some example embodiments, the request includes a request for establishing or resuming a radio resource control connection, and sending the request to the first network device includes: in response to the first terminal device being in an idle or inactive state, sending the request for establishing or resuming a radio resource control connection, the request including a reason for the determined active switching.

[0159] In some aspects, a method includes: determining, by a second terminal device, that a device-to-device connection for communicating with at least one first terminal device is to be switched to a connection routed by at least one network device; sending an indication of the decision to switch from the device-to-device connection to the routed connection to the at least one first terminal device; and performing the switching from the device-to-device connection to the routed connection.

[0160] In some example embodiments, the method further comprises receiving a confirmation for the handover from the first terminal device via the device-to-device connection.

[0161] In some example embodiments, determining includes determining that the device-to-device connection is to be switched to a routed connection in response to receiving a number of scheduling request rejections for communications via the device-to-device connection, the number of scheduling request rejections being above a threshold number, receiving scheduling request rejections for communications via the device-to-device connection, the scheduling request rejections indicating that the device-to-device connection is to be switched to the routed connection, determining that a traffic load via the device-to-device connection is above a threshold load, receiving an indication from an upper layer above the access layer that the device-to-device connection is to be switched to the routed connection, or receiving an indication from the access layer that a particular device-to-device transmission mode is not available.

[0162] In some example embodiments, the indication is sent in a message at an upper layer above the access layer or at the access layer.

[0163] In some example embodiments, sending the indication includes: a second network device of the at least one network device sending a request for switching; receiving a response to the request from the second network device; and in response to the response indicating that switching is allowed, sending the indication to the first terminal device via the device-to-device connection.

[0164] In some example embodiments, performing the handover includes: determining whether communication via the routed connection requires a packet data unit session serviced by the core network; and in response to determining that a packet data unit session is required, determining the packet data unit session.

[0165] In some example embodiments, determining whether a packet data unit session is required includes: receiving an indication that a packet data unit session is required from a second network device of the at least one network device; and determining that a packet data unit session is required.

[0166] In some example embodiments, determining a packet data unit session includes: in response to the second terminal device being in a connected state, determining whether a packet data unit session served by the core network is available for communication via a routed connection; and in response to determining that no packet data unit session served by the core network is available, initiating establishment of a packet data unit session for communication via the routed connection.

[0167] In some example embodiments, determining a packet data unit session further comprises: in response to determining that the packet data unit session is available, determining whether a quality of service flow for the packet data unit session is available for communication via the routed connection; and in response to determining that no quality of service flow is available, adding a quality of service flow for the communication to the packet data unit session or adjusting the quality of service flow for the packet data unit session for the communication.

[0168] In some example embodiments, determining the packet data unit session further comprises initiating establishment of a radio resource control connection in response to the second terminal device being in an idle or inactive state.

[0169] In some example embodiments, it is indicated that a packet data unit session is required for communication via the routed connection.

[0170] In some example embodiments, context information of a connection comprising a route associated with the second terminal device is indicated.

[0171] In some example embodiments, the context information comprises at least one of a cell identifier and a public land mobile network identifier associated with the second terminal device.

[0172] In some example embodiments, an apparatus includes: means for receiving, by a first terminal device, from a second terminal device via a device-to-device connection, an indication of a decision to switch a device-to-device connection to a connection routed by at least one network device for communicating with the second terminal device; means for determining, based on the indication received from the second terminal device, that an active switch from the device-to-device connection to the routed connection is to be performed; and means for sending a request to a first network device among the at least one network device to establish the routed connection, the request indicating a reason for the determined active switch.

[0173] In some example embodiments, the apparatus further comprises means for sending a confirmation for the handover to the second terminal device via the device-to-device connection.

[0174] In some example embodiments, the apparatus further comprises: means for determining whether communication via the routed connection requires a packet data unit session serviced by the core network; and means for determining a packet data unit session in response to determining that a packet data unit session is required.

[0175] In some example embodiments, means for determining whether a packet data unit session is required comprises means for determining whether an indication indicates that a packet data unit session is required; and means for determining that a packet data unit session is required in response to the indication indicating that a packet data unit session is required.

[0176] In some example embodiments, means for determining whether a packet data unit session is required includes means for receiving an indication that a packet data unit session is required from a first network device of the at least one network device; and means for determining that a packet data unit session is required.

[0177] In some example embodiments, context information of a connection comprising a route associated with the second terminal device is indicated.

[0178] In some example embodiments, the context information includes at least one of a cell identifier and a public land mobile network identifier associated with the second terminal device, and the component for determining whether a packet data unit session is required also includes: a component for determining, using the cell identifier and the public land mobile network identifier, whether the first terminal device is served by the same cell or the same public land mobile network as the second terminal device; and a component for sending an indication of switching to a first network device among the at least one network device in response to determining that the first terminal device is served by the same cell or the same public land mobile network as the second terminal device, the indication including the context information.

[0179] In some example embodiments, the means for determining a packet data unit session includes: means for determining whether a packet data unit session served by the core network is available for communication via a routed connection in response to the first terminal device being in a connected state; and means for initiating establishment of a packet data unit session for communication via a routed connection in response to determining that no packet data unit session served by the core network is available.

[0180] In some example embodiments, the means for determining a packet data unit session includes: means for determining whether a quality of service flow for the packet data unit session is available for communication via a routed connection in response to determining that the packet data unit session is available; and means for adding a quality of service flow for the communication to the packet data unit session or adjusting the quality of service flow for the packet data unit session for the communication in response to determining that no quality of service flow is available.

[0181] In some example embodiments, the request comprises a request for establishing or resuming a radio resource control connection, and the means for sending the request to the first network device comprises: means for sending the request for establishing or resuming a radio resource control connection in response to the first terminal device being in an idle or inactive state, the request including a reason for the determined active handover.

[0182] In some aspects, an apparatus includes: components for determining, by a second terminal device, that a device-to-device connection for communicating with at least one first terminal device is to be switched to a connection routed by at least one network device; components for sending an indication of the decision to switch from the device-to-device connection to the routed connection to at least one first terminal device; and components for performing the switching from the device-to-device connection to the routed connection.

[0183] In some example embodiments, the apparatus further comprises means for receiving a confirmation of the handover from the first terminal device via the device-to-device connection.

[0184] In some example embodiments, the means for determining includes means for determining that the device-to-device connection is to be switched to a routed connection in response to receiving a number of scheduling request rejections for communications via the device-to-device connection, the number of scheduling request rejections being above a threshold number, receiving scheduling request rejections for communications via the device-to-device connection, the scheduling request rejections indicating that the device-to-device connection is to be switched to a routed connection, determining that a traffic load via the device-to-device connection is above a threshold load, receiving an indication from an upper layer above the access layer that the device-to-device connection is to be switched to a routed connection, or receiving an indication from the access layer that a particular device-to-device transmission mode is not available.

[0185] In some example embodiments, the indication is sent in a message at an upper layer above the access layer or at the access layer.

[0186] In some example embodiments, the means for sending an indication includes: means for sending a request for switching to a second network device of at least one network device; means for receiving a response to the request from the second network device; and means for sending an indication to the first terminal device via the device-to-device connection in response to the response indicating that switching is allowed.

[0187] In some example embodiments, means for performing the handover includes means for determining whether communication via the routed connection requires a packet data unit session serviced by the core network; and means for determining the packet data unit session in response to determining that the packet data unit session is required.

[0188] In some example embodiments, means for determining whether a packet data unit session is required includes means for receiving an indication that a packet data unit session is required from a second network device of the at least one network device; and means for determining that a packet data unit session is required.

[0189] In some example embodiments, the means for determining a packet data unit session includes: means for determining whether a packet data unit session served by the core network is available for communication via a routed connection in response to the second terminal device being in a connected state; and means for initiating establishment of a packet data unit session for communication via a routed connection in response to determining that no packet data unit session served by the core network is available.

[0190] In some example embodiments, the component for determining a packet data unit session further includes: a component for determining whether a quality of service flow for the packet data unit session is available for communication via a routed connection in response to determining that the packet data unit session is available; and a component for adding a quality of service flow for the communication to the packet data unit session or adjusting the quality of service flow for the packet data unit session for the communication in response to determining that no quality of service flow is available.

[0191] In some example embodiments, the means for determining a packet data unit session further comprises means for initiating establishment of a radio resource control connection in response to the second terminal device being in an idle or inactive state.

[0192] In some example embodiments, the indication is that a packet data unit session is required for communication via the routed connection.

[0193] In some example embodiments, context information of a connection comprising a route associated with the second terminal device is indicated.

[0194] In some example embodiments, the context information comprises at least one of a cell identifier and a public land mobile network identifier associated with the second terminal device.

[0195] In some aspects, a computer-readable storage medium includes program instructions stored thereon, which, when executed by a processor of a device, cause the device to perform methods according to some example embodiments of the present disclosure.

Claims

1. A first terminal device, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, enable the first terminal device to: receiving, from a second terminal device via a device-to-device connection, an indication of a decision to switch the device-to-device connection to a connection routed by at least one network device for communicating with the second terminal device; determining, based on the indication received from the second terminal device, that an active handover of a connection from the device to the device connected to the route is to be performed; as well as In response to the first terminal device being in an idle or inactive state, sending a request for establishing or resuming a radio resource control connection to a first network device among the at least one network device, the request including a reason for the determined active switching; The first terminal device is further configured to: determining whether a packet data unit session served by a core network is required for said communication via said routed connection; and In response to determining that the packet data unit session is needed, determining the packet data unit session; wherein the determination and establishment of the packet data unit session are performed after the indication is sent to the first terminal device, and the establishment of the packet data unit session is initiated in parallel at the first terminal device and at the second terminal device; wherein the indication comprises context information of a connection of the route associated with the second terminal device; The context information includes at least one of a cell identifier and a public land mobile network identifier associated with the second terminal device, and the first terminal device is further caused to determine whether the packet data unit session is required by: determining, using the cell identifier or the public land mobile network identifier, whether the first terminal device is served by the same cell or the same public land mobile network as the second terminal device; as well as In response to determining that the first terminal device is served by the same cell or the same public land mobile network as the second terminal device, an indication for the handover is sent to a first network device among the at least one network device, the indication including the context information.

2. The first terminal device according to claim 1, wherein the first terminal device is further configured to: A confirmation of the switching is sent to the second terminal device via the device-to-device connection.

3. The first terminal device according to claim 1, wherein the first terminal device is caused to determine whether the packet data unit session is required by: determining whether the indication indicates that the packet data unit session is required; and In response to the indication indicating that the packet data unit session is required, it is determined that the packet data unit session is required.

4. The first terminal device according to claim 1, wherein the first terminal device is caused to determine whether the packet data unit session is required by: receiving, from a first network device of the at least one network device, an indication that the packet data unit session is required; and It is determined that the packet data unit session is required.

5. The first terminal device according to claim 1, wherein the first terminal device is caused to determine the packet data unit session by: responsive to the first terminal device being in a connected state, determining whether a packet data unit session served by the core network is available for the communication via the routed connection; and In response to determining that no packet data unit sessions serviced by the core network are available, establishing a packet data unit session is initiated for the communication via the routed connection.

6. The first terminal device according to claim 5, wherein the first terminal device is further configured to determine the packet data unit session by: In response to determining that the packet data unit session is available, determining whether a quality of service flow for the packet data unit session is available for the communication via the routed connection; and In response to determining that no quality of service flow is available, adding a quality of service flow for the communication to the packet data unit session, or A quality of service flow for the packet data unit session for the communication is adjusted.

7. A second terminal device, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, enable the second terminal device to: determining that a device-to-device connection for communicating with at least a first terminal device is to be switched to a connection routed by at least one network device; sending, to at least one of said first terminal devices, an indication of a decision to switch from said device-to-device connection to said routed connection; as well as performing a handover of a connection from the device to a device connected to the route; The second terminal device is configured to perform the switching by: determining whether a packet data unit session served by a core network is required for said communication via said routed connection; as well as In response to determining that the packet data unit session is needed, determining the packet data unit session; wherein the determination and establishment of the packet data unit session are performed after the indication is sent to the first terminal device, and the establishment of the packet data unit session is initiated in parallel at the first terminal device and at the second terminal device; The second terminal device is further configured to determine the packet data unit session by: In response to the second terminal device being in an idle or inactive state, initiating establishment of a radio resource control connection; wherein the indication comprises context information of a connection of the route associated with the second terminal device; The context information includes at least one of a cell identifier and a public land mobile network identifier associated with the second terminal device, so that the first terminal device determines whether the packet data unit session is required by: determining, using the cell identifier or the public land mobile network identifier, whether the first terminal device is served by the same cell or the same public land mobile network as the second terminal device; as well as In response to determining that the first terminal device is served by the same cell or the same public land mobile network as the second terminal device, an indication for the handover is sent to a first network device among the at least one network device, the indication including the context information.

8. The second terminal device according to claim 7, wherein the second terminal device is further configured to: A confirmation of the switching is received from the first terminal device via the device-to-device connection.

9. The second terminal device according to claim 7, wherein the second terminal device is caused to determine that the device-to-device connection is to be switched to the routed connection in response to: receiving a number of scheduling request rejections for the communication via the device-to-device connection, the number of scheduling request rejections being above a threshold number, receiving a scheduling request rejection for the communication via the device-to-device connection, the scheduling request rejection indicating that the device-to-device connection is to be switched to the routed connection, determining that a traffic load via the device-to-device connection is above a threshold load, receiving an indication from an upper layer above the access layer that the device-to-device connection is to be switched to the routed connection, or An indication is received from the access layer that a particular device-to-device transmission mode is not available.

10. The second terminal device according to claim 7, wherein the indication is sent in a message on an upper layer above the access layer or on the access layer.

11. The second terminal device according to claim 7, wherein the second terminal device is configured to send the indication by: Sending a request for the switching to a second network device among the at least one network device; receiving a response to the request from the second network device; and In response to the response indicating that the switching is allowed, the indication is sent to the first terminal device via the device-to-device connection.

12. The second terminal device according to claim 7, wherein the second terminal device is caused to determine whether the packet data unit session is required by: receiving an indication that the packet data unit session is required from a second network device of the at least one network device; and It is determined that the packet data unit session is required.

13. The second terminal device according to claim 7, wherein the second terminal device is caused to determine the packet data unit session by: responsive to the second terminal device being in a connected state, determining whether a packet data unit session served by the core network is available for the communication via the routed connection; and In response to determining that no packet data unit sessions serviced by the core network are available, establishing a packet data unit session is initiated for the communication via the routed connection.

14. The second terminal device according to claim 13, wherein the second terminal device is further configured to determine the packet data unit session by: In response to determining that the packet data unit session is available, determining whether a quality of service flow for the packet data unit session is available for the communication via the routed connection; and In response to determining that no quality of service flow is available, adding a quality of service flow for the communication to the packet data unit session, or A quality of service flow for the packet data unit session for the communication is adjusted.

15. The second terminal device of claim 7, wherein the indication indicates that the packet data unit session is required for the communication via the routed connection.

16. A method for communication, comprising: receiving, by a first terminal device from a second terminal device via a device-to-device connection, an indication of a decision to switch the device-to-device connection to a connection routed by at least one network device for communicating with the second terminal device; determining, based on the indication received from the second terminal device, that an active handover of a connection from the device to the device connected to the route is to be performed; as well as In response to the first terminal device being in an idle or inactive state, sending a request for establishing or resuming a radio resource control connection to a first network device among the at least one network device, the request including a reason for the determined active switching; The method further comprises: determining whether a packet data unit session served by a core network is required for said communication via said routed connection; and In response to determining that the packet data unit session is needed, determining the packet data unit session; wherein the determination and establishment of the packet data unit session are performed after the indication is sent to the first terminal device, and the establishment of the packet data unit session is initiated in parallel at the first terminal device and at the second terminal device; wherein the indication comprises context information of a connection of the route associated with the second terminal device; The context information includes at least one of a cell identifier and a public land mobile network identifier associated with the second terminal device, and determining whether the packet data unit session is required further comprises: determining, using the cell identifier or the public land mobile network identifier, whether the first terminal device is served by the same cell or the same public land mobile network as the second terminal device; and In response to determining that the first terminal device is served by the same cell or the same public land mobile network as the second terminal device, an indication for the handover is sent to a first network device among the at least one network device, the indication including the context information.

17. The method according to claim 16, further comprising: A confirmation of the switching is sent to the second terminal device via the device-to-device connection.

18. The method of claim 16, wherein determining whether the packet data unit session is required comprises: determining whether the indication indicates that the packet data unit session is required; as well as In response to the indication indicating that the packet data unit session is required, it is determined that the packet data unit session is required.

19. The method of claim 16, wherein determining whether the packet data unit session is required comprises: receiving, from a first network device of the at least one network device, an indication that the packet data unit session is required; as well as It is determined that the packet data unit session is required.

20. The method of claim 16, wherein determining the packet data unit session comprises: responsive to the first terminal device being in a connected state, determining whether a packet data unit session served by the core network is available for the communication via the routed connection; as well as In response to determining that no packet data unit sessions serviced by the core network are available, establishing a packet data unit session is initiated for the communication via the routed connection.

21. The method of claim 20, wherein determining the packet data unit session comprises: In response to determining that the packet data unit session is available, determining whether a quality of service flow for the packet data unit session is available for the communication via the routed connection; as well as In response to determining that no quality of service flow is available, adding a quality of service flow for the communication to the packet data unit session, or A quality of service flow for the packet data unit session for the communication is adjusted.

22. A method for communication, comprising: determining, by the second terminal device, that a device-to-device connection for communicating with at least the first terminal device is to be switched to a connection routed by at least one network device; sending, to at least one of said first terminal devices, an indication of a decision to switch from said device-to-device connection to said routed connection; as well as performing a handover of a connection from the device to a device connected to the route; The performing of the switching includes: determining whether a packet data unit session served by a core network is required for said communication via said routed connection; and In response to determining that the packet data unit session is needed, determining the packet data unit session; wherein the determination and establishment of the packet data unit session are performed after the indication is sent to the first terminal device, and the establishment of the packet data unit session is initiated in parallel at the first terminal device and at the second terminal device; Wherein determining the packet data unit session further comprises: In response to the second terminal device being in an idle or inactive state, initiating establishment of a radio resource control connection; wherein the indication indicates that the packet data unit session is required for the communication via the connection of the route; wherein the indication comprises context information of a connection of the route associated with the second terminal device; The context information includes at least one of a cell identifier and a public land mobile network identifier associated with the second terminal device, so that the first terminal device determines whether the packet data unit session is required by: determining, using the cell identifier or the public land mobile network identifier, whether the first terminal device is served by the same cell or the same public land mobile network as the second terminal device; and In response to determining that the first terminal device is served by the same cell or the same public land mobile network as the second terminal device, an indication for the handover is sent to a first network device among the at least one network device, the indication including the context information.

23. The method according to claim 22, further comprising: A confirmation of the switching is received from the first terminal device via the device-to-device connection.

24. The method of claim 22, wherein the determining comprises determining that the device-to-device connection is to be switched to the routed connection in response to: receiving a number of scheduling request rejections for the communication via the device-to-device connection, the number of scheduling request rejections being above a threshold number, receiving, via the device-to-device connection, a scheduling request rejection for the communication, the scheduling request rejection indicating the switching, determining that a traffic load via the device-to-device connection is above a threshold load, receiving an indication from an upper layer above the access layer that the device-to-device connection is to be switched to the routed connection, or An indication is received from the access layer that a particular device-to-device transmission mode is not available.

25. The method of claim 22, wherein the indication is sent in a message at an upper layer above the access layer or at the access layer.

26. The method of claim 22, wherein sending the indication comprises: Sending a request for the switching to a second network device among the at least one network device; receiving a response to the request from the second network device; as well as In response to the response indicating that the switching is allowed, the indication is sent to the first terminal device via the device-to-device connection.

27. The method of claim 22, wherein determining whether the packet data unit session is required comprises: receiving, from a second network device of the at least one network device, an indication that the packet data unit session is required; as well as It is determined that the packet data unit session is required.

28. The method of claim 22, wherein determining the packet data unit session comprises: responsive to the second terminal device being in a connected state, determining whether a packet data unit session served by the core network is available for the communication via the routed connection; as well as In response to determining that no packet data unit sessions serviced by the core network are available, establishing a packet data unit session is initiated for the communication via the routed connection.

29. The method of claim 28, wherein determining the packet data unit session further comprises: In response to determining that the packet data unit session is available, determining whether a quality of service flow for the packet data unit session is available for the communication via the routed connection; as well as In response to determining that no quality of service flow is available, adding a quality of service flow for the communication to the packet data unit session, or A quality of service flow for the packet data unit session for the communication is adjusted.

30. An apparatus for communication, comprising: means for receiving, by a first terminal device from a second terminal device via a device-to-device connection, an indication of a decision to switch the device-to-device connection to a connection routed by at least one network device for communicating with the second terminal device; means for determining, based on an indication received from the second terminal device, that an active handover of a connection from the device to the device connected to the route is to be performed; means for sending a request to a first network device of the at least one network device to establish a connection for the route, the request indicating a reason for the determined active switching; means for determining whether communication via said routed connection requires a packet data unit session serviced by a core network; as well as means for determining a packet data unit session in response to determining that a packet data unit session is required; wherein the determination and establishment of the packet data unit session are performed after the indication is sent to the first terminal device, and the establishment of the packet data unit session is initiated in parallel at the first terminal device and at the second terminal device; wherein the indication includes context information of a connection of a route associated with the second terminal device; The context information comprises at least one of a cell identifier and a public land mobile network identifier associated with the second terminal device, and the means for determining whether a packet data unit session is required further comprises: means for determining, using the cell identifier and the public land mobile network identifier, whether the first terminal device is served by the same cell or the same public land mobile network as the second terminal device; means for sending an indication of handover to a first network device of at least one network device in response to determining that the first terminal device is served by the same cell or the same public land mobile network as the second terminal device, the indication comprising the context information; The request comprises a request for establishing or resuming a radio resource control connection, and the component for sending the request to the first network device comprises: a component for sending a request for establishing or resuming a radio resource control connection in response to the first terminal device being in an idle or inactive state, the request including a reason for a determined active switching.

31. An apparatus for communication, comprising: means for determining, by the second terminal device, that a device-to-device connection for communicating with at least the first terminal device is to be switched to a connection routed by at least one network device; means for sending to at least one of said first terminal devices an indication of a decision to switch from said device-to-device connection to said routed connection; as well as means for performing a handover of a connection from said device to a device connected to said route; The components for performing the switching include: means for determining whether communication via the routed connection requires a packet data unit session serviced by the core network; and means for determining a packet data unit session in response to determining that a packet data unit session is required; wherein the determination and establishment of the packet data unit session are performed after the indication is sent to the first terminal device, and the establishment of the packet data unit session is initiated in parallel at the first terminal device and at the second terminal device; The means for determining a packet data unit session further comprises: means for initiating establishment of a radio resource control connection in response to the second terminal device being in an idle or inactive state; wherein the indication indicates that the packet data unit session is required for the communication via the connection of the route; wherein the indication comprises context information of a connection of the route associated with the second terminal device; The context information includes at least one of a cell identifier and a public land mobile network identifier associated with the second terminal device, so that the first terminal device determines whether the packet data unit session is required by: determining, using the cell identifier or the public land mobile network identifier, whether the first terminal device is served by the same cell or the same public land mobile network as the second terminal device; and In response to determining that the first terminal device is served by the same cell or the same public land mobile network as the second terminal device, an indication for the handover is sent to a first network device among the at least one network device, the indication including the context information.

32. A computer-readable storage medium comprising program instructions stored thereon, which instructions, when executed by a processor of a device, cause the device to perform the method according to any one of claims 16 to 21.

33. A computer-readable storage medium comprising program instructions stored thereon, which instructions, when executed by a processor of a device, cause the device to perform the method according to any one of claims 22 to 29.