# US 12,192,877 B2 · Proactive switching of V2X communication from sidelink connection to cellular connection

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 12,192,877 B2
- Document ID: US12192877B2
- Status: Granted
- Kind: B2
- Application number: 17/624,546
- Filed: 2019-07-04
- Published: 2022-08-04
- Granted: 2025-01-07
- Earliest claimed: 2019-07-04
- Assignees: Nokia Technologies Oy
- Applicants: Nokia Technologies Oy
- Inventors: Lianghai Ji; Jakob Lindbjerg Buthler; Vinh Van Phan; Ling Yu; Hajo Bakker; Rudraksh Shrivastava; Bernhard Wegmann; Xiang Xu
- Web page: https://patentgrep.com/patent/US12192877B2

## CPC

- H04W 40/30: for proactive routing
- H04W 40/34: Modification of an existing route
- H04L 5/0053: {Allocation of signalling, i.e. of overhead other than pilot signals}
- H04L 45/22: {Alternate routing}
- H04W 4/40: for vehicles, e.g. vehicle-to-pedestrians [V2P]
- H04W 40/248: {Connectivity information update}
- H04W 76/20: Manipulation of established connections
- H04W 4/44: for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]
- H04W 4/46: for vehicle-to-vehicle communication [V2V]
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04W 88/04: adapted for relaying to or from another terminal or user
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Embodiments of the present disclosure relate to devices, methods, apparatuses and computer readable storage media of a proactive switch of vehicle-to-everything communication from a device-to-device connection to a connection routed by one or more network devices. In example embodiments, a first terminal device receives, 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 communication with the second terminal device. Based on the received indication from the second terminal device, the first terminal device then determines proactive switching from the device-to-device connection to the routed connection to be performed. The first terminal device then sends a request to a first network device of the at least one network device to set up the routed connection, the request indicating a cause for the determined proactive switching.

## Claims

### Claim 1

A first terminal device, comprising:
at least one processor; and
at least one memory including computer program code;
the at least one memory and the computer program code configured to, with the at least one processor, cause the first terminal device to:
receive, 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 communication with the second terminal device;
determine, based on the received indication from the second terminal device, proactive switching from the device-to-device connection to the routed connection to be performed; and
send a request to a first network device of the at least one network device to set up the routed connection, the request indicating a cause for the determined proactive switching,
wherein the first terminal device is further caused to:
determine whether a packet data unit session served by a core network is required for the communication via the routed connection; and
in response to determining that the packet data unit session is required, determine the packet data unit session,
wherein the determining and setup of the packet data unit session is performed after the indication is received and a connection setup is initiated for both the first terminal device and the second terminal device in parallel.

### Claim 2 (depends on 1)

The first terminal device of claim 1, wherein the first terminal device is further caused to:
send, to the second terminal device via the device-to-device connection, an acknowledgement for the switching.

### Claim 3 (depends on 1)

The first terminal device of 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, determining that the packet data unit session is required.

### Claim 4 (depends on 1)

The first terminal device of 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
determining that the packet data unit session is required.

### Claim 5 (depends on 1)

The first terminal device of claim 1, wherein the indication contains context information of the routed connection associated with the second terminal device.

### Claim 6 (depends on 5)

The first terminal device of claim 5, wherein the context information contains 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, with 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, sending an indication for the switching to a first network device of the at least one network device, the indication containing the context information.

### Claim 7 (depends on 1)

The first terminal device of claim 1, wherein the first terminal device is caused to determine the 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 the communication via the routed connection; and
in response to determining that no packet data unit session served by the core network is available, initiating setup of a packet data unit session for the communication via the routed connection.

### Claim 8 (depends on 7)

The first terminal device of claim 7, wherein the first 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 of 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 into the packet data unit session, or
adjusting a quality of service flow of the packet data unit session for the communication.

### Claim 9 (depends on 1)

The first terminal device of claim 1, wherein the request comprises 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 containing the cause for the determined proactive switching.

### Claim 10

A second terminal device, comprising:
at least one processor; and
at least one memory including computer program code;
the at least one memory and the computer program code configured to, with the at least one processor, cause the second terminal device to:
determine that a device-to-device connection for communication with at least a first terminal device is to be switched to a connection routed by at least one network device,
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;
send, to the first terminal device, an indication of a decision to switch from the device-to-device connection to the routed connection; and
perform switching from the device-to-device connection to the routed connection.

### Claim 11 (depends on 10)

The second terminal device of claim 10, wherein the second terminal device is further caused to receive, from the first terminal device via the device-to-device connection, an acknowledgement for the switching; and
wherein:
the first and second terminal devices each comprise user equipment (UE) capable of wireless communications with each other and with a base station;
the device-to-device connection comprises a wireless sidelink connection directly from the first terminal device to the second terminal device;
the at least one network device comprises the base station; and
the routed connection comprises at least a Uu connection between one of the first and second terminal devices and the base station.

### Claim 12 (depends on 10)

The second terminal device of claim 10, 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 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, from an upper layer above an access stratum layer, an indication that the device-to-device connection is to be switched to the routed connection, or
receiving, from the access stratum layer, an indication that a specific device-to-device transmission mode is unavailable.

### Claim 13 (depends on 10)

The second terminal device of claim 10, wherein the indication is sent in a message either on an upper layer above an access stratum layer or on access stratum layer.

### Claim 14 (depends on 10)

The second terminal device of claim 10, wherein the second terminal device is caused to send the indication by:
sending a request for the switching to a second network device of the at least one network device;
receiving a response for the request from the second network device; and
in response the response indicating that the switching is allowed, sending the indication to the first terminal device via the device-to-device connection.

### Claim 15 (depends on 10)

The second terminal device of claim 10, wherein the second terminal device is caused to perform the switching by:
determining whether a packet data unit session served by a core network is required for the communication via the routed connection; and
in response to determining that the packet data unit session is required, determining the packet data unit session.

### Claim 16 (depends on 15)

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

### Claim 17 (depends on 15)

The second terminal device of claim 15, wherein the second terminal device is caused to determine the 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 the communication via the routed connection; and
in response to determining that no packet data unit session served by the core network is available, initiating setup of a packet data unit session for the communication via the routed connection.

### Claim 18 (depends on 17)

The second terminal device of claim 17, wherein 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 of 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 into the packet data unit session, or adjusting a quality of service flow of the packet data unit session for the communication.

### Claim 19 (depends on 17)

The second terminal device of claim 17, wherein the second terminal device is further caused to determine the packet data unit session by:
in response to the second terminal device being in an idle or inactive state, initiating setup of a radio resource control connection.

### Claim 20 (depends on 1)

The first terminal device of claim 1, wherein:
the first and second terminal devices each comprise user equipment (UE) capable of wireless communications with each other and with a base station;
the device-to-device connection comprises a wireless sidelink connection directly from the first terminal device to the second terminal device;
the at least one network device comprises the base station; and
the routed connection comprises at least a Uu connection between one of the first and second terminal devices and the base station.