WO2021006376A1 - Method for efficiently supporting handover of tcu mounted on vehicle in next-generation mobile communication system, and server therefor - Google Patents

Abstract

A disclosure of the present specification provides a server for efficiently supporting handover of a telematics communication unit (TCU) mounted on a vehicle in a next-generation mobile communication system. The server may include: a transmission or reception unit; and a processor for controlling the transmission or reception unit. The processor may perform the operations of: on the basis of information on a location of a first vehicle, the information being received from a first TCU mounted on the first vehicle, through a first base station, predicting a path through which the first vehicle can move; determining a second server connected to a second base station existing on a path through which the first vehicle is to move; and transmitting TCU information and service information of the first vehicle to the determined second server.

Description

Method for efficiently supporting handover of TCU installed in vehicle in next-generation mobile communication system and server thereof

The present invention relates to communication with a telematics communication unit installed in a vehicle in next-generation mobile communication.

Thanks to the success of LTE (long term evolution)/LTE-Advanced (LTE-A) for 4G mobile communication, interest in the next generation, that is, 5G (so-called 5G) mobile communication, is also increasing, and research is continuing. .

　5th generation mobile communication defined by the International Telecommunication Union (ITU) refers to providing a maximum 　20Gbps data transmission speed and a sensible transmission speed of at least 　100Mbps　 or more anywhere. Its official name is'IMT-2020' and it aims to be commercialized globally in 2020.

ITU proposes three usage scenarios, e.g. eMBB (enhanced mobile broadband), mMTC (massive machine type communication), and URLLC (Ultra Reliable and Low Latency Communications).

First, URLLC relates to a usage scenario that requires high reliability and low latency. For example, services such as automatic driving, factory automation, and augmented reality require high reliability and low latency (for example, a delay time of 1 ms or less). Currently, the latency of 4G (LTE) is statistically 21-43ms (best 10%), 33-75ms (median). This is insufficient to support a service that requires a delay time of less than 1ms.

Next, the eMBB usage scenario relates to a usage scenario requiring mobile ultra-wideband.

This ultra-wideband high-speed service seems difficult to be accommodated by the core network designed for the existing LTE/LTE-A.

Therefore, in the so-called 5th generation mobile communication, redesign of the core network is urgently required.

1 is a structural diagram of a next-generation mobile communication network.

5GC (5G Core) may include various components, and in FIG. 1, some of them include Access and Mobility Management Function (AMF) 51, Session Management Function (SMF) 52, and Policy Control (PCF). Function) (53), UPF (User Plane Function) (54), AF (Application Function) (55), UDM (Unified Data Management) (56), and N3IWF (Non-3GPP InterWorking Function) (59).

The UE 10 is connected to the data network 60 through the UPF 55 through a Next Generation Radio Access Network (NG-RAN).

The UE 10 may receive a data service even through untrusted non-3GPP access, for example, a wireless local area network (WLAN). In order to connect the non-3GPP access to the core network, an N3IWF 59 may be deployed.

<Autonomous driving>

Automotive driving is expected to be an important new driving force in 5G, along with various use cases of mobile communication for vehicles.

In the case of autonomous driving in which the server remotely controls the vehicle, the vehicle transmits data to the server and the vehicle receives control data from the server to achieve ultra-reliable and low-latency communication (URLLC) specified in 5G. It should take less than 5msec for operation.

However, in a conventional cloud server-based network structure (e.g., base station-wired network-cloud server), the base station transmits data received from the vehicle to the cloud server, analyzes the data in the cloud server, and transmits the data to the base station. , There is a problem that it takes about 30 to 40 msec only for the base station to receive it.

In order to improve the conventional network structure and achieve URLLC, discussions on Multi-access Edge Computing (MEC) have been made in ETSI (European Telecommunications Standards Institute) and 5GAA. However, in the past, there has been no way to quickly and efficiently transmit and receive data between the MEC server and a telematics communication unit (TCU) provided in a vehicle.

In particular, there was no way to efficiently and quickly transmit data to the TCU during the handover process.

Accordingly, the disclosures of the present specification aim to solve the above-described problems.

In order to achieve the above object, one disclosure of the present specification provides a server that efficiently supports handover of a Telematics Communication Unit (TCU) mounted on a vehicle in a next-generation mobile communication system. The server includes a transceiver; And it may include a processor that controls the transceiver. The processor predicts a path to which the first vehicle can move based on the location information of the first vehicle received from a first TCU mounted on the first vehicle through a first base station, and the first vehicle moves. A process of determining a second server connected to a second base station existing on a path and a process of transmitting TCU information and service information of the first vehicle to the determined second server may be performed.

The processor may further perform a process of receiving lane information and traffic signal information on which the first vehicle is traveling from the first TCU through the transmission/reception unit.

The process of performing transmission to the determined second server may include: transmitting lane information and traffic signal information on which the first vehicle is running to the determined second server.

The traffic signal information may include traffic light information. The traffic light information may include one or more of signal information currently displayed on the traffic light, information on the next signal of the traffic light, information on a time elapsed after the signal of the traffic light is changed, and information on the remaining time until the signal of the traffic light is changed. .

The TCU information may include the ID of the first TCU and current location information.

The service information may include one or more of related information for controlling an engine control unit (ECU) and information on a service provided in the first vehicle.

The related information for controlling the ECU may include at least one of: a minimum data rate for receiving the ECU control command by the first TCU and information on the type of the ECU control command.

The information on the service provided in the first vehicle may include at least one of: information on a data rate for video streaming, and information on an available buffer size in the first TCU.

The processor includes: when a second vehicle equipped with a second TCU intends to handover to the first base station, a process of receiving TCU information and service information of the second vehicle from a second server, and to the second vehicle The process of preparing data to be transmitted may be further performed.

The processor: when receiving information indicating that the second vehicle is handed over to a third base station from the second server, may further perform a process of deleting the prepared data.

In order to achieve the above object, one disclosure of the present specification provides a method in which a server efficiently supports handover of a Telematics Communication Unit (TCU) installed in a vehicle in a next generation mobile communication system. The method includes the steps of predicting a path through which the first vehicle can move based on location information of the first vehicle received from a first TCU mounted on the first vehicle through a first base station; Determining a second server connected to a second base station existing on a path to which the first vehicle will move; And it may include the step of transmitting the TCU information and service information of the first vehicle to the determined second server.

According to the disclosure of the present specification, existing problems are solved.

1 is a structural diagram of a next-generation mobile communication network.

2 is an exemplary diagram showing an expected structure of next-generation mobile communication from a node perspective.

3 is an exemplary diagram showing an architecture for supporting simultaneous access to two data networks.

4 is another exemplary diagram showing the structure of a radio interface protocol between a UE and a gNB.

5A is a flowchart illustrating a random access process.

5B shows a connection process in a radio resource control (RRC) layer.

6 is a flowchart showing a handover process.

7A to 7D show an example implementation of a MEC server.

8 shows an example in which the MEC server remotely controls the vehicle.

9 is a block diagram illustrating an example of a MEC server and an example of a TCU according to one disclosure of the present specification.

10 is an exemplary view showing an exemplary situation for explaining one method of the present specification.

11 is a flow chart showing one method of the present specification.

12A shows an example of a combination of an antenna pair, and FIG. 12B shows an example of a method of determining a combination of an antenna pair.

13 shows an example in which the TCU performs data transmission/reception according to the disclosure of the present specification.

14 is a block diagram of a MEC server and a TCU according to an embodiment.

15 is a block diagram showing in detail the configuration of a TCU according to an embodiment of the present invention.

It should be noted that the technical terms used in the present specification are only used to describe specific embodiments, and are not intended to limit the present invention. In addition, the technical terms used in the present specification should be interpreted as generally understood by those of ordinary skill in the technical field to which the present invention belongs, unless otherwise defined in the present specification, and excessively comprehensive It should not be construed as a human meaning or an excessively reduced meaning. In addition, when a technical term used in the present specification is an incorrect technical term that does not accurately express the spirit of the present invention, it will be replaced with a technical term that can be correctly understood by those skilled in the art to be understood. In addition, general terms used in the present invention should be interpreted as defined in the dictionary or according to the context before and after, and should not be interpreted as an excessively reduced meaning.

In addition, the singular expression used in the present specification includes a plurality of expressions, unless the context clearly indicates otherwise. In the present application, terms such as constitute or have should not be construed as necessarily including all of the various components or steps described in the specification, and some components or some steps may not be included, and Or, it should be interpreted that it may further include additional components or steps.

In addition, terms including ordinal numbers such as first and second used herein may be used to describe various elements, but the elements should not be limited by the terms. These terms are only used for the purpose of distinguishing one component from another component. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may be referred to as a first component.

When a component is connected to or is said to be connected to another component, it may be directly connected or connected to the other component, but other components may exist in the middle. On the other hand, when a component is directly connected to or directly connected to another component, it should be understood that there is no other component in the middle.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings, but the same or similar components are assigned the same reference numerals regardless of the reference numerals, and redundant descriptions thereof will be omitted. In addition, in describing the present invention, when it is determined that a detailed description of a related known technology may obscure the subject matter of the present invention, a detailed description thereof will be omitted. In addition, it should be noted that the accompanying drawings are only intended to facilitate understanding of the spirit of the present invention, and should not be construed as limiting the spirit of the present invention by the accompanying drawings. The spirit of the present invention should be construed as extending to all changes, equivalents, or substitutes in addition to the accompanying drawings.

<Next-generation mobile communication system structure>

2 is an exemplary diagram showing an expected structure of next-generation mobile communication from a node perspective.

As can be seen with reference to FIG. 2, the UE is connected to a data network (DN) through a next-generation radio access network (RAN).

The illustrated control plane function (CPF) node is all or part of the functions of a mobility management entity (MME) of 4G mobile communication, and a control plane function of a serving gateway (S-GW) and a PDN gateway (P-GW). Do all or part of. The CPF node includes an Access and Mobility Management Function (AMF) and a Session Management Function (SMF).

The illustrated User Plane Function (UPF) node is a type of gateway through which user data is transmitted and received. The UPF node may perform all or part of the user plane functions of S-GW and P-GW of 4G mobile communication.

The illustrated PCF (Policy Control Function) is a node that controls the operator's policy.

The illustrated application function (AF) is a server for providing various services to the UE.

The illustrated Unified Data Management (UDM) is a kind of server that manages subscriber information, such as a 4G mobile communication HSS (Home Subscriber Server). The UDM stores and manages the subscriber information in a Unified Data Repository (UDR).

The illustrated authentication server function (AUSF) authenticates and manages the UE.

The illustrated network slice selection function (NSSF) is a node for network slicing as described below.

In FIG. 2, the UE can simultaneously access two data networks using multiple Protocol Data Unit (PDU) sessions.

3 is an exemplary diagram showing an architecture for supporting simultaneous access to two data networks.

In FIG. 3, an architecture for a UE to access two data networks simultaneously using one PDU session is shown.

In FIGS. 2 and 3, AF by a third parity other than an operator may be connected to 5GC through a Network Exposure Function (NEF).

4 is another exemplary diagram showing the structure of a radio interface protocol between a UE and a gNB.

The radio interface protocol is based on the 3GPP radio access network standard. The radio interface protocol horizontally consists of a physical layer (Physical layer), a data link layer (Data Link layer), and a network layer (Network layer), and vertically, a user plane and control for data information transmission. It is divided into a control plane for signal transmission.

The protocol layers are L1 (layer 1), L2 (layer 2), and L3 (layer 3) based on the lower 3 layers of the Open System Interconnection (OSI) reference model widely known in communication systems. ) Can be separated.

In the following, each layer of the radio protocol will be described.

The first layer, the physical layer, provides an information transfer service using a physical channel. The physical layer is connected to an upper medium access control layer through a transport channel, and data between the medium access control layer and the physical layer is transmitted through the transport channel. In addition, data is transmitted between different physical layers, that is, between the physical layers of the transmitting side and the receiving side through a physical channel.

The second layer includes a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer.

The third layer includes Radio Resource Control (hereinafter abbreviated as RRC). The RRC layer is defined only in the control plane, and is related to the setting (setting), resetting (Re-setting) and release (Release) of radio bearers (Radio Bearers; In charge of control. In this case, RB means a service provided by the second layer for data transfer between the UE and the E-UTRAN.

The NAS (Non-Access Stratum) layer performs functions such as connection management (session management) and mobility management.

The NAS layer is divided into a NAS entity for mobility management (MM) and a NAS entity for session management (SM).

1) NAS entity for MM provides the following functions in general.

As a NAS procedure related to AMF, it includes the following.

-Registration management and access management procedures. AMF supports the following functions.

-Secure NAS signal connection between UE and AMF (integrity protection, encryption)

2) The NAS entity for the SM performs session management between the UE and the SMF.

The SM signaling message is processed, that is, generated and processed at the NAS-SM layer of the UE and SMF. The contents of the SM signaling message are not interpreted by the AMF.

-In the case of SM signaling transmission,

-The NAS entity for the MM generates a NAS-MM message that derives how and where to deliver the SM signaling message through the security header representing the NAS transmission of SM signaling, and additional information about the receiving NAS-MM.

-Upon receiving the SM signaling, the NAS entity for the SM performs an integrity check of the NAS-MM message, analyzes the additional information, and derives a method and place to derive the SM signaling message.

Meanwhile, in FIG. 4, an RRC layer, an RLC layer, a MAC layer, and a PHY layer located below the NAS layer are collectively referred to as an Access Stratum (AS).

5A is a flowchart illustrating a random access process.

The UE 10 transmits a random access preamble to the eNodeB 20.

Upon receiving the random access preamble, the gNB 20 sends a random access response (RAR) to the UE 10. The random access response is detected in two steps. First, the UE 10 detects a PDCCH masked with a random access-RNTI (RA-RNTI). The UE 10 receives a random access response in a Medium Access Control (MAC) Protocol Data Unit (PDU) on a PDSCH indicated by the detected PDCCH.

5B shows a connection process in a radio resource control (RRC) layer.

As shown in FIG. 5B, the RRC state is shown depending on whether the RRC is connected. The RRC state refers to whether or not an entity of the RRC layer of the UE 10 is in a logical connection with an entity of the RRC layer of the gNB 20, and if connected, the RRC connected state (connected state), and the state that is not connected is called the RRC idle state. In addition, the inactive state is not a connected state, but refers to a state in which the AS layer context of the UE is stored in the UE and the gNB 20.

The UE 10 first searches for an appropriate cell and then stays in an idle state in the cell. The UE 10, which has stayed in the idle state, establishes an RRC connection with the RRC layer of the eNodeB 20 through an RRC connection procedure when it is necessary to establish an RRC connection, and the RRC connection state transition to (connected state).

In order for the UE 10 in the idle state to establish an RRC connection with the gNB 20, the RRC connection establishment process must be performed as described above. This process will be described in more detail with reference to FIG. 5B as follows.

1) When the UE 10 in the idle state attempts to establish an RRC connection, the UE 10 first transmits an RRC setup request message to the gNB 20.

2) Upon receiving the RRC setup request message from the UE 10, the egB 20 accepts the RRC connection request of the UE 10 when radio resources are sufficient, and a response message, RRC setup It transmits a message to the UE 10.

3) When the UE 10 receives the RRC setup message, it transmits an RRC setup complete message to the gNB 20. When the UE 10 successfully transmits the RRC setup complete message, the UE 10 finally establishes an RRC connection with the gNB 20 and transitions to the RRC connection mode.

6 is a flowchart showing a handover process.

6, the UE 10 in the RRC connected state transmits a measurement report message to the source gNB 20a. The source gNB 20a means a serving base station that has an RRC connection with the UE 10.

The source gNB 20a determines handover. The handover may be determined based on a measurement report message received from the UE 10. That is, the source gNB 20a decides to handover the UE 10 to a target gNB 20b more suitable for the UE 10.

The source gNB 20a transmits a HANDOVER REQUEST message to the target gNB 20b in order to handover the UE 10 to the target gNB 20b.

The target gNB 20b performs admission control and transmits a HANDOVER REQUEST ACKNOWLEDGE message including a new RRC setting to the source gNB 20a.

The source gNB 20a transmits an RRC Reconfiguration message including the new RRC configuration to the UE 10. The RRC reconfiguration message may include all information necessary to access the target gNB 20b, eg, a cell ID. In addition, the RRC reconfiguration message may include information necessary to perform a random access procedure if necessary.

The UE 10 moves the existing RRC connection to the target gNB 20b and transmits an RRC Reconfiguration Complete message to the target gNB 20b.

< Multi-access Edge Computing (MEC)>

In order to achieve ultra-reliable and low latency communications (URLLC), discussions on Multi-access Edge Computing (MEC) have been made in ETSI (European Telecommunications Standards Institute) and 5GAA.

MEC is a network architecture that enables cloud computing functions and IT service environments at the edge of the cellular network (typically, the edge of any network). The basic idea of MEC is to reduce network congestion and perform applications better by running applications (applications) and performing processing tasks related to cellular customers. MEC technology is designed to be implemented in a cellular base station or other edge node. MEC technology can flexibly and quickly deploy new applications and new services for customers. MEC enables cellular operators to open up a Radio Access Network (RAN) to authorized third parties such as application developers and content providers.

The MEC server described in the present specification refers to a communication device that provides a cloud computing function or an IT service environment at the edge of a network.

7A to 7D show an example implementation of a MEC server.

The UPF node 540 of FIGS. 7A to 7D is a type of gateway through which user data is transmitted/received. The UPF node 540 may perform all or part of a user plane function of a serving-gateway (S-GW) and a packet data network-gateway (P-GW) of 4G mobile communication. The core network 500 may be an Evolved Packet Core (EPC) or a 5G Core Network (5GC). N3 is a reference point between the (R)AN and the UPF node 540. N6 is a reference point between the UPF node 540 and the data network. The base station 200 may be a 5G base station (gNB) or an LTE base station (eNB). The base station 200 may be a base station including both a gNB and an eNB.

Logically, the MEC server (MEC host) 551 may be implemented in an edge or central data network. The UPF node 540 may play a role of coordinating user plane (UP) traffic to a target MEC application (application in the MEC server 551) of the data network. The location of the data network and UPF can be selected by the network operator. Network operators may allocate physical computing resources based on technical and business variables such as available facilities, supported applications and application requirements, measured or estimated user loads, and the like. The MEC management system can dynamically determine where to distribute the MEC application by adjusting the operation of the MEC server 551 (MEC host) and the application.

7A is an example implementation in which the MEC server 551 and the UPF node 540 are disposed together with the base station 200. 7B is an example implementation in which the MEC server 551 is deployed with a transmitting node (eg, the UPF node 540). In FIG. 7B, the UPF node 540 and the MEC server 551 may perform communication through a network aggregation point. 7C is an example implementation in which the MEC server 551 and the UPF node 540 are deployed together with a network aggregation point. 7D is an example implementation in which the MEC server 551 is deployed together with core network functions (CPF). In FIG. 7D, the MEC server 551 may be located in the same data center as the core network functions.

<Disclosures of this specification>

8 shows an example in which the MEC server remotely controls the vehicle.

Referring to FIG. 8, a MEC server 551, a base station 200, and a vehicle are shown. The base station 200 may be a gNB or an eNB. The base station 200 may be a base station including both a gNB and an eNB. The MEC server 551 may be connected to the base station 200 through wired communication or wireless communication. The MEC server 551 may transmit data to or receive data from the base station 200. The figure shows that the MEC server 551 and the base station 200 are directly connected, but this is only an example, and the MEC server 551 may be connected to the base station 200 through another network node.

The base station 200 may transmit and receive data to and from the Telematics Communication Unit (TCU) 100 provided in the vehicle.

The TCU 100 may obtain state information from devices provided in the vehicle, and the state information may include various sensor data, video data, and the like. The TCU may transmit state information to the base station 200, and the base station 200 may transmit the state information to the MEC server 551. Then, the MEC server 551 may transmit data for controlling the vehicle to the base station 200 based on the state information. When the base station 200 transmits data for controlling the vehicle to the TCU 100, the TCU 100 may control the vehicle by transmitting the received data to electronic devices provided in the vehicle. In addition, the MEC server 551 may transmit map information to the base station 200, and the base station 200 may transmit it to the TCU. The TCU can control the vehicle using the map information.

The MEC server 551 and the TCU provided in the vehicle will be described in detail with reference to FIG. 9.

9 is a block diagram illustrating an example of a MEC server and an example of a TCU according to one disclosure of the present specification.

The MEC server is the MEC server 551 described with reference to FIGS. 7A to 7D and 8, and will be described below by omitting reference numerals.

The MEC server may be implemented like the examples described in FIGS. 7A to 7D. 7 shows that the MEC server communicates directly with base stations, but this is only an example, and the MEC server may communicate with base stations through other network nodes (eg, UPF node or NEF). The MEC server may include a processor (not shown) and a memory (not shown). The memory can store MEC server apps. The processor may perform the operations described in the disclosure of the present specification using the MEC server app stored in the memory.

The first 5G base station (eg, a 5G base station using sub 6 GHz) is a base station that performs communication based on the 5G standard in a frequency range 1 (FR1) band (a frequency band of 7125 MHz or less). The second 5G base station (eg, a 5G base station using mmWave) is a base station that performs communication based on the 5G standard in a frequency range 2 (FR2) band (frequency band of 24250-52600 MHz). The LTE base station performs communication based on the LTE standard. The Wi-Fi access point (AP) performs communication based on the Wi-Fi standard. The MEC server communicates with the TCU using at least one of a first 5G base station (eg, a 5G base station using sub 6 GHz), a second 5G base station (eg, a 5G base station using mmWave), an LTE base station, and a Wi-Fi base station. can do.

The TCU is an LTE transceiver (ie, LTE modem/antenna), a first 5G transceiver (ie, a modem/antenna using sub 6GHz), a second 5G transceiver (ie, a modem/antenna using mmWave), a WLAN transceiver (Ie, WiFi transceiver), a processor, and a memory may be included. The LTE transceiver is a communication module that performs communication based on the LTE standard. The first 5G transmission/reception unit (ie, modem/antenna using sub 6GHz) is a communication module that performs communication based on the 5G standard in the FR 1 band. The second 5G transceiver (ie, a modem/antenna using mmWave) is a communication module that performs communication based on the 5G standard in the FR 2 band. The WLAN transceiver (ie, WiFi transceiver) is a communication module that performs communication based on the WiFi standard. The LTE transceiver, the first 5G transceiver (i.e., modem/antenna using sub 6GHz), the second 5G transceiver (i.e., modem/antenna using mmWave) and WLAN transceiver (i.e., WiFi transceiver) are PCIe ( PCI express) can be connected to the processor through an interface. In addition, the LTE transceiver, the first 5G transceiver (ie, modem/antenna using sub 6GHz), the second 5G transceiver (ie, modem/antenna using mmWave) and WLAN transceiver (ie, WiFi transceiver) Although each is shown as a separate object, one communication module includes an LTE transceiver, a first 5G transceiver (ie, a modem/antenna using sub 6GHz), a second 5G transceiver (ie, a modem/antenna using mmWave) And it may perform the function of the WLAN transceiver (ie, WiFi transceiver).

The processor of the TCU includes a first 5G transceiver (ie, a modem/antenna using sub 6GHz), a second 5G transceiver (ie, a modem/antenna using mmWave), a WLAN transceiver (ie, a WiFi transceiver), and a memory. Connected. The memory can store MEC client apps. The processor includes an LTE transceiver, a first 5G transceiver (ie, a modem/antenna using sub 6GHz), a second 5G transceiver (ie, a modem/antenna using mmWave), and a WLAN transceiver (ie, a WiFi transceiver). The data transmitted by the base stations or terminals (terminal 1 and terminal 2) can be received. The processor includes an LTE transceiver, a first 5G transceiver (ie, a modem/antenna using sub 6GHz), a second 5G transceiver (ie, a modem/antenna using mmWave), and a WLAN transceiver (ie, a WiFi transceiver). By using, data can be transmitted to base stations or terminals (terminal 1 and terminal 2). Here, the terminals (terminal 1 and terminal 2) may be wireless communication devices used by a user in a vehicle.

The processor of the TCU may be connected to devices provided in the vehicle. For example, the processor may be connected to a Domain Control Unit (DCU), a Local Interconnect Network (LIN) master, a Media Oriented System Transport (MOST) master, and an Ethernet switch. The processor of the TCU can communicate with the DCU using CAN (Controller Area Network) communication technology. The processor of the TCU can communicate with the LIN master using LIN (Local Interconnect Network) communication technology. The TCU's processor can communicate with the MOST master connected by fiber optics using MOST communication technology. The TCU's processor can communicate with Ethernet switches and devices connected to them using Ethernet communication technology.

DCU is a device that controls a plurality of ECUs. The DCU can communicate with multiple ECUs using CAN communication technology. Here, CAN is a standard communication technology designed to allow microcontrollers or devices to communicate with each other in a vehicle. CAN is a non-host bus message-based network protocol that is mainly used for communication between controllers.

The DCU may communicate with ECUs such as an engine ECU that controls an engine, a brake ECU that controls a brake, and an HVAC ECU that controls a heating, ventilation, & air conditioning (HVAC) device. The DCU may transmit data received from the processor of the TCU to each ECU. In addition, the DCU can transmit the data received from each ECU to the processor of the TCU.

The LIN master can communicate with LIN slaves (LIN Slave #1 and LIN Slave #2) using LIN communication technology. For example, LIN Slave #1 may be a slave that controls one of a steering wheel, a roof top, a door, a seat, and a small motor. Here, LIN is a serial communication technology for communication between components in a vehicle network. The LIN master may receive data from the processor of the TCU and transmit it to the LIN slaves (LIN Slave #1 and LIN Slave #2). In addition, the LIN master can transmit data received from the LIN slaves to the processor of the TCU.

The MOST master can communicate with MOST slaves (MOST Slave #1 and MOST Slave #2) using MOST communication technology. Here, MOST is a serial communication technology that transmits audio, video, and control information using an optical cable. The MOST master can transmit data received from the processor of the TCU to the MOST slaves. In addition, the MOST master can transmit data received from MOST slaves to the processor of the TCU.

Ethernet is a computer networking technology used in local area networks (LAN), metropolitan area networks (MAN) and wide area networks (WAN). The TCU's processor can transmit data to individual devices through an Ethernet switch using Ethernet communication technology. Each device can transmit data to the TCU's processor through an Ethernet switch using Ethernet communication technology.

Radar (radio detection and ranging) is a technology that uses radio waves to measure the distance, direction, angle, and speed of a target. Radar sensors 1 to 5 are provided in the vehicle and measure the distance, direction, angle and speed of objects around the vehicle. Radar sensors 1 to 5 may transmit the measured sensor data to the processor of the TCU.

LiDAR (light detection and ranging) is a sensing technology that uses a light source and a receiver to detect remote objects and measure distances. Specifically, Rida is a technology that illuminates an object with pulsed laser light and measures the pulse reflected by the sensor to measure the distance, intensity, and speed to the object. LiDAR sensors 1 to 5 measure the distance and speed to the object. The lidar sensors 1 to 5 may transmit the measured sensor data to the processor of the TCU.

AVN (Audio, Video, Navigation) is a device that is provided in a vehicle and provides sound, video, and navigation. AVN may receive data from the processor of the TCU using Ethernet communication technology, and may provide sound, video, and navigation based on the received data. AVN can transmit data to the TCU's processor using Ethernet communication technology.

The camera (front) and camera (rear) can take images from the front and rear of the vehicle. In FIG. 9, it is shown that there are one camera in the front and only one in the rear, but this is only an example, and cameras may be provided in the left and right sides. In addition, a plurality of cameras may be provided at each of the front and rear sides. Cameras may use Ethernet communication technology to transmit camera data to the TCU's processor and receive data from the TCU's processor.

Rear Side Entertainment (RSE) means rear seat entertainment. RSE is a device that provides entertainment to occupants by being installed behind the passenger seat or driver seat of a vehicle. A tablet may also be provided inside the vehicle. The RSE or tablet can receive data from the processor of the TCU and transmit the data to the processor of the TCU using Ethernet communication technology.

The MEC server according to the disclosure of the present specification performs a function of receiving/storing/transmitting/analyzing various data such as video/audio/sensor data, which were performed in a conventional cloud server, and managing the TCU and devices provided in the vehicle. I can.

A MEC server application for performing operations according to various purposes may exist in the MEC server according to the disclosure of the present specification. The MEC server can perform the following functions using the MEC server application.

-The operation of the TCU and the ECU in the vehicle is monitored to comply with regulations such as the Road Traffic Act, ISO26262 (Standard for Industrial Safety, Road vehicles-Functional safety) or SAE (System Architecture Evolution) standards. If the operation of the TCU and the ECU in the vehicle violates the regulations, the operation of the vehicle's ECU is controlled based on a predefined scenario.

-Vehicle-related information received from the TCU in the vehicle (e.g., engine ECU-related data, RPM (revolutions per minute) ECU-related data, wheel-related data, brake-related data, HVAC (heating, ventilation, & A function to analyze the status information of devices equipped in the vehicle, such as air conditioning) related data, and control the operation of the devices in the vehicle connected to the TCU based on a predefined operation scenario

-The MEC server can monitor the operation status of the TCU and determine the current status of the TCU. For example, the MEC server can monitor the operating state of the TCU and determine the current state of the TUC as one of inactive, active, sleeping, and moving.

-The MEC server can receive vehicle-related information (eg, information related to the location of the vehicle) from the TCU and manage the location of the vehicle (eg, collect/analyze/control/record).

-The MEC server can receive vehicle-related information (eg, vehicle speed-related information) from the TCU and manage the vehicle speed-related information (eg, collect/analyze/control/record). The MEC server manages information related to the speed of the vehicle and can determine whether the vehicle is speeding or whether the vehicle observes a safe speed.

-The MEC server can receive vehicle-related information (eg, engine ECU information) from the TCU and manage (eg, collect/analyze/control/record) engine ECU (ECU that controls the engine) information.

-The MEC server receives vehicle-related information from the TCU (e.g., information received from sensors and cameras provided in the vehicle) and manages vehicle sensor and camera information (Lidar, Radar, and front/rear/measurement/cabin camera) ( Example: collection/analysis/control/recording).

-As a result of analyzing the vehicle sensor and camera information, the MEC server transmits control data to the TCU based on the emergency response scenario when a vehicle collision with pedestrians, obstacles, etc. is expected to transmit the ECU (engine ECU, brake ECU, etc.) in the vehicle. Can be controlled.

10 is an exemplary view showing an exemplary situation for explaining one method of the present specification. 11 is a flow chart showing one method of the present specification.

Hereinafter, a method shown in FIG. 11 will be described based on the exemplary situation shown in FIG. 10.

First, as can be seen with reference to FIG. 10, base station #1 (200a) is connected to MEC server #1 (551a), base station #2 (200b) is connected to MEC server #2 (551b), , Base station #3 (200c) is connected to MEC server #3 (551c).

The vehicle equipped with the TCU 100 is running on the road. The TCU 100 has an RRC connection with the base station #1 200a. Accordingly, a cell operated by the base station #1 200a may be a serving cell of the TCU 100. When the vehicle continues to go straight, it enters the coverage of base station #2 200b. However, when the vehicle turns right, it enters the coverage of the base station #3 (200c).

1) Referring to FIG. 11, the in-vehicle TCU 100 has its own location information (a measurement result through a satellite navigation system or a measurement result using an LTE positioning protocol (LPP) or a secure user (SUPL)) while driving. Plane Location) is transmitted to MEC server #1 (551a) through base station #1 (200a) corresponding to its serving cell.

2) Then, the MEC server #1 (551a) calculates a physical location, that is, paths to which the vehicle can move, based on the received location information. In other words, the MEC server #1 (551a) predicts a location where the vehicle can move next, that is, paths on the map, based on the path that the vehicle equipped with the TCU 100 has traveled in the past.

3-4) Meanwhile, the TCU 100 transmits information on the currently driving lane and traffic signal information received from the neighboring RSU to the MEC server #1 551a through the base station #1 200a. The traffic signal information may include traffic light information. The traffic light information may include information on whether the traffic light is a traffic light for four signals or a traffic light for three signals. In addition, the traffic light information includes signal information currently displayed on the traffic light (i.e., information indicating whether the current signal is a straight signal or a stop signal) and next signal information of the traffic light (for example, when the signal is changed from a straight signal to a stop signal, a stop signal) Information) may include one or more. The traffic light information may include change time information of the traffic light. The new information on the change of the traffic light may include a time elapsed after the color of the traffic light is changed, and a time remaining until the color of the traffic light is changed.

5) The MEC server #1 551a determines the base stations on the path to which the vehicle will travel.

Specifically, the MEC server #1 (551a) calculates the past location information (X1, X2) and the current location information (X2, Y2) of the TCU 100 as a vector using the following equation.

The MEC server #1 (551a) uses the vector calculated by the above equation to determine the base stations existing on the map when the vehicle is turning left, the path when turning right, or the path when going straight on the map. do. For example, when the vehicle goes straight or turns left, it enters the coverage of base station #2 (200b). However, when the vehicle turns right, it enters the coverage of the base station #3 (200c).

In addition, the MEC server #1 (551a) determines MEC servers (eg, MEC server #2 (551b) and MEC server #3 (551c)) connected to base stations existing in the predicted paths.

6) The MEC server #1 (551a) provides information on the TCU 100 mounted on the vehicle and service information provided to the vehicle to MEC servers (e.g., MEC server #2 ( 551b) and transfer to MEC server #3 (551c)).

When the vehicle is predicted to go straight or turn left, for example, and it is predicted that the vehicle will enter the coverage of the base station #2 (200b), the information is a MEC server connected to the base station #2 (200b). It may be transmitted only to #2 (551b). However, when it is not predicted where the vehicle will move, the information may be transmitted to MEC servers (eg, MEC server #2 551b and MEC server #3 551c) existing on all routes.

Among the pieces of information, the TCU information of the vehicle may include the ID of the TCU and current location information. Among the information, the service information may include related information for ECU control. The related information for controlling the ECU may include a minimum data rate for the TCU 100 to receive an ECU control command for autonomous driving and a type of ECU control command (eg, brake, RPM, etc.). have. In addition, the service information may include information on requirements of a plurality of services provided by the TCU (eg, RSE: 100Mbps video streaming, in-vehicle electronic device 1: 50Mbps video streaming through WLAN). The service information may include information on an available buffer size in the TCU 100.

On the other hand, the MEC server #1 (551a) is a MEC server (e.g., MEC server) existing in the predicted paths the information of the lane and the traffic signal information acquired from the TCU 100 in step 4 above. #2 (551b) and MEC server #3 (551c)).

7) MEC servers (eg, MEC server #2 (551b) and MEC server #3 (551c)) that have received the above information prepare for data transmission.

8) On the other hand, the base station #1 (200a) determines the handover. At this time, the path to which the vehicle will travel is determined definitively, and the base station #1 (200a) notifies the MEC server #1 (100a). If, for example, if the moving path of the vehicle is definitively determined to go straight, the vehicle will enter into the coverage of base station #2 (200b), so the target base station for the handover is base station #2 (200b) Is determined by Then, the base station #1 (200a) determines to hand over the TCU (100) to the base station #2 (200b), and informs the MEC server #1 (100a) of this. Then, the MEC server #1 (100a) sends information on the TCU (100) to other MEC servers other than the MEC server #2 (551b) connected to the base station #2 (200b), that is, MEC server #3 (551c). (Eg, the ID of the TCU) is transmitted. Alternatively, the MEC server #1 (100a) informs another MEC server, that is, MEC server #3 (551c) to stop preparing data for the TCU (100). Then, the MEC server #3 (551c) deletes the information related to the TCU (100). Further, the MEC server #3 (551c) deletes the data prepared for the TCU (100).

9) The TCU 100 of the vehicle, the base station #1 (200a), and the base station #2 (200b) perform a handover procedure as shown in FIG. 6.

10) The TCU 100 transmits its own data (eg, image data of sensors and cameras) to the MEC server #2 551b through the base station #2 200b. Similarly, the MEC server #2 (551b) transmits the prepared data to the TCU (100) through the base station #2 (200b).

Specifically, when the MEC server #2 551b receives sensor data from the TCU 100 and image data of the front and rear cameras, it analyzes. Further, the MEC server #2 (551b) transmits related information for vehicle control (eg, ECU control) and various service data to the TCU 100 through the base station #2 (200b).

As described above, the various service data may include high-definition video streaming data or high-quality sound source streaming data. In addition, the various service data may include high-definition map data.

In step 7 above, the MEC server #2 (551b) acquires various service data to be transmitted from a remote cloud server to the TCU 100 before the handover is performed, stores it in the buffer memory, and stores it in the buffer memory. When the handoff of the process is completed, it can be transmitted in step 11.

When the TCU 100 receives related information for vehicle control (eg, ECU control) and various service data, it is transmitted to the ECU and electronic device in the vehicle. Then, the ECU in the vehicle returns the execution result of the control command to the TCU 100. Then, the TCU 100 transmits the execution result of the control command to the MEC server #2 551b.

Meanwhile, the MEC server #2 551b stores the result of executing the received control command. Then, the MEC server #2 (551b) determines whether the control command is a command related to safety according to priority. If it is determined that the priority is high, the MEC server #2 551b may repeatedly transmit the control command. Further, the MEC server #2 551b may retransmit the control command based on the result of executing the received control command.

The above operation is repeated until the maximum number of retransmissions has elapsed, and when the maximum number of retransmissions is exceeded, the MEC server #2 551b leaves a record and notifies the result to the cloud server of the vehicle manufacturer.

Meanwhile, although not shown, when the vehicle is handed over from the second base station 200b to the third base station 200c, the MEC server #2 551b performs the operation of the MEC server #1 551a. It can be performed similarly, and the MEC server #3 (551c) can similarly perform the operation of the MEC server #2 (551b).

On the other hand, although not shown, when another vehicle is handed over to the first base station 200a, the MEC server #1 (551a) may perform the same operation of the MEC server #2 (551b). have.

Meanwhile, when the in-vehicle electronic device is a wireless communication device, the MEC server #2 551b may select an optimal antenna beam pair between the TCU 100 and the electronic device. This is described in detail as follows.

12A shows an example of a combination of an antenna pair, and FIG. 12B shows an example of a method of determining a combination of an antenna pair.

The numbers on the left shown in FIG. 12A are index numbers of reception (Rx) antennas of the TCU 100 for receiving downlink data from the base station. The numbers on the right side are index numbers of a transmission (Tx) antenna of the TCU 100 for transmitting downlink data to an electronic device in a vehicle.

When the reception (Rx) and the transmission (Tx) are performed through the same antenna, that is, when the index of the reception (Rx) antenna and the transmission (Tx) antenna have the same index, as will be described later with reference to FIG. Downlink data is received from the base station through the antenna in a downlink period within a time period, and the downlink data is transmitted to an electronic device in a vehicle through the antenna in a downlink period within a second time period.

In this case, the data rate R _i,i (t) can be obtained as follows.

The method of determining the combination of antenna pairs shown in FIG. 12B may be performed for each service. That is, the above scheme can be performed while increasing the service index m until the maximum number of services m _max is reached. For this, a for function can be used. The m is increased from 0.

In addition, the scheme shown in FIG. 12B may be performed for each antenna type. The antenna type may include an antenna for LTE, an antenna for a first 5G communication (ie, communication using sub 6 Ghz), and an antenna for a second 5G communication (ie, communication using mmWave). The above scheme may be performed while increasing the antenna type index j until the maximum number of antenna types j _max is reached. For this, a for function can be used. The j is increased from 0.

In addition, the scheme shown in FIG. 12B may be performed for each antenna. The above scheme can be performed while increasing the antenna index k until the maximum number of antennas k _max is reached. For this, a for function can be used. The k increases from zero. At this time, it is performed when the data rate R _i,j,k (t) is greater than S _m (t) of a specific service.

When the TCU 100 has an ECU control message in the data received from the base station, the TCU 100 transmits the ECU control message to an Ethernet switch at a rate R _E (t).

Then, the data rate R _i,j,k (t) is determined as follows.

Next, the TCU 100 determines the transmission speed to the electronic device in the vehicle as shown in the following equation.

In the above equation, the symbol is as follows.

i: index of TCU-i

j: antenna type index number

k: antenna index number

m: service index

S _i,j,k (t) is the data rate for the service requested by the user

R _E (t): This is the data rate of the ECU control message transmitted by the TCU to the ECU.

G _Sm (t): Service group of a specific user

G _Rx (t): TCU's receive antenna beam group for reception from the base station

G _Tx (t): TCU transmit antenna beam group for transmission to in-vehicle electronic devices

Next, the TCU 100 may select the k*th antenna of the J* type antenna and transmit data to the electronic device in the vehicle at a speed of λ ₂ .

In addition, the TCU 100 excludes the corresponding S ^*m (t) from the specific user service group G _sm (t).

Next, the TCU 100 excludes a specific antenna index k* from the G _Rx (t) group.

In addition, the TCU 100 excludes a specific antenna index k** from the G _Tx (t) group.

As described above, according to the disclosure of the present specification, when the MEC server 551 transmits various data to in-vehicle devices such as ECU, RSE, AVN through the TCU 100, the reception (Rx) antenna of the TCU 100 You can select the type (ie, LTE, 5G, etc.) and the receiving antenna beam. In addition, the MEC server 551 may adjust the transmission rate of downlink data according to the available buffer size in the TCU 100. At this time, the MEC server 551 may adjust the internal transmission rate of the TCU so that the ECU control message can be delivered with the highest priority.

Meanwhile, according to the disclosure of the present specification, the TCU 100 transmits data flowing from a plurality of transceivers (ie, an LTE transceiver, a first 5G transceiver, a second 5G transceiver, and a WLAN transceiver to an electronic device in the vehicle). When storing in the buffer before transmission, the size of the corresponding data can be controlled so that the size of the data does not exceed the buffer size. For this purpose, the MEC server 551 adjusts the data rate transmitted to the TCU 100 through the base station 200. I can.

In the exemplary system described above, the methods are described on the basis of a flowchart as a series of steps or blocks, but the present invention is not limited to the order of the steps, and certain steps may occur in a different order or concurrently with the steps described above. I can. In addition, those skilled in the art will appreciate that the steps shown in the flowchart are not exclusive, other steps may be included, or one or more steps in the flowchart may be deleted without affecting the scope of the present invention.

13 shows an example in which the TCU performs data transmission/reception according to the disclosure of the present specification.

According to one disclosure of the present specification, communication is performed between the base station 200 and the TCU 100 within a first time period, and communication between the TCU 100 and an electronic device in a vehicle is performed within a second time period.

Specifically, the base station 200 transmits a plurality of downlink data to the TCU 100 in a downlink interval within the first time interval, and the TCU 100 transmits a plurality of downlink data to the TCU 100 in the downlink interval within the first time interval. 200) to transmit uplink data. In the downlink section within the second time section, the TCU 100 transmits downlink data to the electronic device in the vehicle, and the electronic device within the vehicle transfers to the TCU 100 in the uplink section within the second time section. Transmit uplink data.

During the downlink period within the first time period, the TCU 100 includes a first 5G transceiver (ie, a modem/antenna using sub 6GHz) and a second 5G transceiver (ie, a modem/antenna using mmWave). , Using an LTE transceiver (ie, a modem/antenna using LTE), data is simultaneously received from the MEC server 551 through the base station 200, and data is copied from the internal memory of each TCU to a buffer.

Then, during the downlink period within the second time period, the TCU 100 transmits the buffered data to a plurality of communication methods based on a data rate requested by each of a plurality of electronic devices installed in the vehicle. (E.g., LTE communication, 5G communication, WLAN communication, direct communication) by using one or more of 500 Mbps or more data is transmitted at the same time.

14 is a block diagram of a MEC server and a TCU according to an embodiment.

Referring to FIG. 14, the MEC server 551 and the TCU 100 may each include a memory, a processor, and a transceiver.

The illustrated processor, memory, and transceiver may each be implemented as separate chips, or at least two or more blocks/functions may be implemented through a single chip.

The transceiver includes a transmitter and a receiver. When a specific operation is performed, only one of the transmitter and the receiver may be performed, or both the transmitter and the receiver may be performed. The transceiver may include one or more antennas for transmitting and/or receiving radio signals. In addition, the transmission/reception unit may include an amplifier for amplifying a reception signal and/or a transmission signal, and a bandpass filter for transmission over a specific frequency band.

As described above, the transceiver of the TCU includes a first 5G transceiver (ie, a modem/antenna using sub 6GHz), a second 5G transceiver (ie, a modem/antenna using mmWave), an LTE transceiver (i.e., LTE It may include a modem/antenna).

The processor may implement the functions, processes and/or methods proposed in the present specification. The processor may include an encoder and a decoder. For example, the processor may perform an operation according to the above description. Such a processor may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, a data processing device, and/or a converter for converting a baseband signal and a radio signal to each other.

The memory may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium, and/or other storage device.

15 is a block diagram showing in detail the configuration of a TCU according to an embodiment of the present invention.

The illustrated TCU 100 includes a transceiver 110, a processor 120, a memory 130, one or more antennas, and a subscriber identification module (SIM) card.

The illustrated TCU 100 may further include a speaker 161 and a microphone 162 as necessary.

The illustrated TCU 100 may further include a display 151 and an input unit 152 as necessary.

Processor 120 may be configured to implement the proposed functions, procedures, and/or methods described herein. Layers of the air interface protocol may be implemented in the processor 120. The processor 120 may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, and/or a data processing device. The processor 102 may be an application processor (AP). The processor 120 may include at least one of a digital signal processor (DSP), a central processing unit (CPU), a graphics processing unit (GPU), and a modem (modulator and demodulator). Examples of the processor 120 are SNAPDRAGONTM series processors manufactured by Qualcomm®, EXYNOSTM series processors manufactured by Samsung®, A series processors manufactured by Apple®, HELIOTM series processors manufactured by MediaTek®, INTEL®. It may be an ATOMTM series processor manufactured by or a corresponding next-generation processor.

The display 151 outputs a result processed by the processor 120. The input unit 152 receives an input to be used by the processor 120. The input unit 152 may be displayed on the display 151. A SIM card is an integrated circuit used to securely store an international mobile subscriber identity (IMSI) used to identify and authenticate a subscriber in a mobile phone device such as a mobile phone and a computer and a key associated therewith. The SIM card is not physically implemented, but may be implemented as a computer program and stored in the memory.

The memory 130 is operatively coupled to the processor 120 and stores various information for operating the processor 120. The memory 130 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium, and/or other storage device. When an embodiment is implemented as software, the techniques described in this specification may be implemented as a module (eg, a procedure, a function, etc.) that performs a function described in this specification. Modules can be stored in memory 130 and executed by processor 120. The memory 130 may be implemented inside the processor 120. Alternatively, the memory 130 may be implemented outside the processor 120 and may be communicatively connected to the processor 120 through various means known in the art.

The transceiver 110 is operatively coupled to the processor 120 and transmits and/or receives a radio signal. The transceiver 110 includes a transmitter and a receiver. The transceiver 110 may include a baseband circuit for processing a radio frequency signal. The transceiver unit controls one or more antennas to transmit and/or receive radio signals.

The speaker 161 outputs a sound-related result processed by the processor 120. The microphone 162 receives a sound related input to be used by the processor 120.

In the above, preferred embodiments of the present invention have been exemplarily described, but the scope of the present invention is not limited to such specific embodiments, and thus the present invention is in various forms within the scope described in the spirit and claims of the present invention. It can be modified, changed, or improved.

Claims (15)

1. As a server that efficiently supports handover of TCU (Telematics Communication Unit) installed in a vehicle in a next-generation mobile communication system,

   A transceiver; And

   And a processor for controlling the transmission/reception unit, wherein the processor

   A process of predicting a path to which the first vehicle can move based on location information of the first vehicle received from a first TCU mounted on a first vehicle through a first base station; and

   A process of determining a second server connected to a second base station existing on a path to which the first vehicle will move, and

   A server that transmits the TCU information and service information of the first vehicle to the determined second server.
2. The method of claim 1, wherein the processor

   A server further performing a process of receiving lane information and traffic signal information on which the first vehicle is running from the first TCU through the transceiver.
3. The method of claim 2, wherein the process of performing transmission to the determined second server

   And transmitting lane information and traffic signal information on which the first vehicle is running to the determined second server.
4. The method of claim 2, wherein the traffic signal information includes traffic light information,

   The traffic light information includes at least one of signal information currently displayed on the traffic light, information about the next signal of the traffic light, information about the time elapsed after the signal of the traffic light is changed, and information about the time remaining until the signal of the traffic light is changed.
5. The server of claim 1, wherein the TCU information includes an ID of the first TCU and current location information.
6. The server of claim 1, wherein the service information includes at least one of related information for controlling an engine control unit (ECU) and information on a service provided in the first vehicle.
7. The method of claim 6, wherein the related information for controlling the ECU is:

   A server including at least one of a minimum data rate for the first TCU to receive an ECU control command and information on a type of an ECU control command.
8. The method of claim 6, wherein the information on the service provided in the first vehicle is

   A server including at least one of information on a data rate for video streaming and information on an available buffer size in the first TCU.
9. The method of claim 1, wherein the processor

   When a second vehicle equipped with a second TCU intends to handover to the first base station, receiving TCU information and service information of the second vehicle from a second server; and

   A server that prepares data to be transmitted to the second vehicle.
10. The method of claim 9, wherein the processor

    When receiving information indicating that the second vehicle is handed over to a third base station from the second server, the server further performs a process of deleting the prepared data.
11. As a method of efficiently supporting handover of TCU (Telematics Communication Unit) installed in vehicle in next-generation mobile communication system,

    Predicting a path in which the first vehicle can move based on the location information of the first vehicle received from a first TCU mounted on the first vehicle through a first base station;

    Determining a second server connected to a second base station existing on a path to which the first vehicle will move; And

    And transmitting TCU information and service information of the first vehicle to the determined second server.
12. The method of claim 11,

    The method further comprising receiving lane information and traffic signal information on which the first vehicle is running from the first TCU.
13. The method of claim 1, wherein performing transmission to the determined second server comprises:

    The method further comprising transmitting lane information and traffic signal information on which the first vehicle is traveling to the determined second server.
14. The method of claim 11,

    Receiving TCU information and service information of the second vehicle from a second server when a second vehicle equipped with a second TCU intends to handover to the first base station; And

    The method further comprising preparing data to be transmitted to the second vehicle.
15. The method of claim 14,

    When receiving information indicating that the second vehicle is handed over to a third base station from the second server, deleting the prepared data.

Images