[go: up one dir, main page]

WO2019087464A1 - Dispositif de serveur, son procédé de commande et programme - Google Patents

Dispositif de serveur, son procédé de commande et programme Download PDF

Info

Publication number
WO2019087464A1
WO2019087464A1 PCT/JP2018/025361 JP2018025361W WO2019087464A1 WO 2019087464 A1 WO2019087464 A1 WO 2019087464A1 JP 2018025361 W JP2018025361 W JP 2018025361W WO 2019087464 A1 WO2019087464 A1 WO 2019087464A1
Authority
WO
WIPO (PCT)
Prior art keywords
vehicle
cell
information
communication
point cloud
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2018/025361
Other languages
English (en)
Japanese (ja)
Inventor
晃就 難波
北原　武
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
KDDI Corp
Original Assignee
KDDI Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by KDDI Corp filed Critical KDDI Corp
Publication of WO2019087464A1 publication Critical patent/WO2019087464A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/086—Load balancing or load distribution among access entities
    • H04W28/0861—Load balancing or load distribution among access entities between base stations
    • G—PHYSICS
    • G08—SIGNALLING
    • G08G—TRAFFIC CONTROL SYSTEMS
    • G08G1/00—Traffic control systems for road vehicles
    • G08G1/09—Arrangements for giving variable traffic instructions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H04W4/44—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P] for communication between vehicles and infrastructures, e.g. vehicle-to-cloud [V2C] or vehicle-to-home [V2H]

Definitions

  • the present invention relates to a server device that provides a dynamic map for automatic travel of a vehicle using edge computing, a control method thereof, and a program.
  • a dynamic map (high-precision three-dimensional map) has been studied as an elemental technology for realizing a level of automatic driving that does not require a driver's operation in a vehicle such as a passenger car.
  • MEC multi-access edge computing
  • ETSI European Telecommunications Standards Institute
  • the server apparatus distributed near the edge of the mobile network (for example, between the base station and the core network), in the cell of the base station connected to the server apparatus Provide a dynamic map of the narrow area to This is expected to reduce, for example, the network load involved in the communication between the cloud server that provides a wider dynamic map and the vehicle.
  • Non-Patent Document 1 proposes a technology for reducing communication errors in inter-vehicle communication and road-vehicle communication. Specifically, each vehicle transmits the communication success rate in each geographical area divided into meshes to the server device, acquires heat map information of the communication success rate generated by the server device from the server device, and performs communication Car-to-car communication and road-to-vehicle communication are performed in a high success rate area. Communication errors are reduced by performing communication in an area (mesh) in which the communication success rate is high.
  • An object of the present invention is to provide a technology capable of leveling the network load involved in communication between a server and a vehicle that provides a dynamic map using edge computing.
  • a server apparatus is connected between a plurality of base stations and a core network, and provides a dynamic map for automatic traveling of a vehicle in a plurality of cells corresponding to the plurality of base stations.
  • a server apparatus acquisition means for acquiring communication state information indicating communication states in each of the plurality of cells, and communication in each of the plurality of cells from the communication state information acquired by the acquisition means.
  • the generation unit for generating heat map information correlated with the use status of resources, and three-dimensional coordinates of an object around each vehicle among vehicles traveling in the plurality of cells, and the server device
  • the heat map information generated by the generation means is one or more vehicles that transmit point cloud data used for updating the dynamic map in Zui determined, the determined said one or more vehicles, characterized in that it and a request means for requesting transmission of the point group data to the server device.
  • FIG. 1 shows a network configuration including an MEC server according to an embodiment.
  • FIG. 2 is a block diagram showing an example of the hardware configuration of an MEC server according to an embodiment.
  • FIG. 2 is a block diagram showing an example of the functional configuration of an MEC server according to an embodiment.
  • FIG. 5 is a sequence diagram of communication between a vehicle and an MEC server according to one embodiment.
  • FIG. 5 is a sequence diagram of communication between a vehicle and an MEC server according to one embodiment.
  • an LTE (LTE / LTE-Advanced) network is assumed as an example of a mobile network to which the present invention is applied.
  • the present invention may be applied to mobile networks other than LTE networks.
  • the present invention may be applied to a fifth generation (5G) mobile network that is being standardized in the Third Generation Partnership Project (3GPP).
  • 5G fifth generation
  • FIG. 1 is a diagram showing an example of a network configuration including an MEC server 10 which is a server apparatus according to an embodiment of the present invention.
  • the LTE network assumed in this embodiment is configured of a radio access network E-UTRAN (Evolved Universal Terrestrial Radio Network) and a core network EPC (Evolved Packet Core).
  • the E-UTRAN is composed of a number of base stations (base station devices) connected to the EPC via the S1 interface, respectively.
  • a base station is referred to as an eNodeB (evolved NodeB) (hereinafter, "eNodeB" is described as "eNB").
  • eNodeB evolved NodeB
  • the MEC server 10 is a server device for edge computing (MEC in the present embodiment). As shown in FIG. 1, the MEC server 10 (each of the MEC servers 10 a and 10 b) is connected between a plurality of base stations (eNBs) and a core network (EPC) 20.
  • the MEC server 10 manages a plurality of cells (corresponding to the plurality of eNBs), which are communication ranges of the plurality of connected eNBs, for automatically traveling a vehicle in the plurality of cells.
  • a dynamic map of In addition, each vehicle which travels the inside of a cell is equipped with the automatic travel system for performing automatic travel using a dynamic map.
  • FIG. 2A is a diagram showing an example of the configuration of the dynamic map
  • FIG. 2B is a diagram showing an example of the data of each item constituting the dynamic map in detail.
  • the dynamic map is composed of data of a plurality of items having different contents, and the data of each item is updated at an update frequency according to the contents.
  • the dynamic map is configured by static information (point cloud data), quasi-static information, quasi-dynamic information, and dynamic information.
  • the point cloud data included in the dynamic map is data indicating the three-dimensional coordinates of the object (showing the three-dimensional coordinates of points on the surface of the object), and is updated at a monthly update frequency.
  • point cloud data acquired by the vehicle provided (uploaded) from (the automatic traveling system of) the traveling vehicle may be used.
  • the MEC server 10 requests the vehicle traveling in the cell managed by the MEC server 10 to transmit point cloud data used for updating the dynamic map held for provision to the vehicle.
  • the automatic travel system of the traveling vehicle acquires point cloud data on an object around the vehicle by measurement using a laser scanner, and also acquires the acquired point cloud data in response to a transmission request from the MEC server 10. Send to the MEC server 10
  • the semi-static information, the semi-dynamic information and the dynamic information included in the dynamic map are an example of specific information on the road condition around the vehicle, and are updated with a short update frequency in hours, minutes or seconds.
  • the semi-static information and the semi-dynamic information include at least information on traffic regulation and traffic congestion around the vehicle, and the dynamic information includes information on vehicles, pedestrians and signals around the vehicle. At least Quasi-static information, quasi-dynamic information and dynamic information need to be continuously provided to the vehicle at relatively short time intervals while the vehicle is traveling, in order to realize automatic traveling.
  • the MEC server 10 may individually provide data of each item shown in FIGS. 2A and 2B to the vehicle, or may provide data of all items collectively to the vehicle. Also, at least a portion of the dynamic map is provided to the vehicle from the cloud server disposed in the external network (for example, packet data network (PDN) or the Internet) higher than the EPC 20 via the EPC 20 and any eNB. It is also good.
  • the MEC server 10 may provide a dynamic map of a border area covered by a plurality of cells managed by itself, and a cloud server may provide a dynamic map of a wider area.
  • the MEC server 10 provides the vehicle running in the cell of each connected eNB with a dynamic map (quasi-static information, quasi-dynamic information, dynamic information, etc.) as well as dynamic In order to update the map, it is necessary to acquire point cloud data from each vehicle. Since point cloud data has a large data size, network load may increase if point cloud data is simultaneously transmitted from a large number of vehicles. In addition, when point cloud data is transmitted from a vehicle in a cell where there are few free communication resources (that is, communication resources are tight), communication resources are further strained, and the network load is locally large. It can be.
  • the MEC server 10 appropriately determines one or more vehicles that transmit point cloud data to the MEC server 10 based on the communication status in the plurality of cells to be managed, and determines the determined vehicle Request transmission of group data.
  • the MEC server 10 acquires communication status information indicating the communication status in each of the plurality of cells to be managed.
  • the communication status information as will be described later with reference to FIGS. 10A and 10B, for example, information indicating the usage status of communication resources (radio resources) in each cell, information on vehicles communicating in each cell, and vehicles It includes information indicating communication quality such as throughput for each unit.
  • the radio network information service (RNIS) function of the MEC server 10 is used to acquire the communication status information.
  • RNIS is a service for acquiring network related information such as communication quality in a mobile network, which has been formulated in MEC standard specifications which are being standardized in ETSI.
  • the MEC server 10 generates, from the acquired communication status information, heat map information on the usage status of the communication resource, in which the plurality of cells to be managed are associated with the usage status of the communication resource in each cell.
  • FIG. 3 is a diagram showing an example of heat map information generated in the MEC server 10.
  • the MEC server 10 manages seven cells of cells # 1 to # 7, and indicates the ratio in use of communication resources (communication band in the present embodiment) as the use status of communication resources.
  • the MEC server 10 generates heat map information in which cells # 1 to # 7 are associated with usage rates B r1 to B r7 of communication resources in the respective cells.
  • the MEC server 10 is one or more vehicles that transmit the point cloud data used for updating the dynamic map in the MEC server 10 among the vehicles traveling in the plurality of cells (cells # 1 to # 7) to be managed. Are determined based on the generated heat map information. Furthermore, the MEC server 10 requests the determined one or more vehicles to transmit point cloud data to the MEC server 10. Specifically, MEC server 10 than vehicle running in the cell usage rate B r higher communication resources (communication band), with priority vehicles traveling the utilization in low cell, point group Decide which vehicle will transmit data. This is equivalent to determining a vehicle that transmits point cloud data by prioritizing a vehicle traveling in a cell with many vacant communication resources over a vehicle traveling in a cell with few vacant communication resources. It is.
  • the MEC server 10 effectively uses the idle communication resource while avoiding requesting the transmission of the point cloud data to the vehicle traveling in the cell with a small margin of the communication resource. Communication can be performed to obtain point cloud data from the vehicle. As a result, communication resources may be strained due to communication between vehicles in some cells and the MEC server 10, and network load may be prevented from increasing. Therefore, it becomes possible to equalize the network load accompanying communication between MEC server 10 which provides a dynamic map, and each vehicle between cells (between eNBs).
  • Each MEC server 10 can communicate with other MEC servers, and can share heat map information with other MEC servers.
  • the MEC server 10a can share heat map information with the nearby MEC server 10b.
  • the MEC server 10a may determine one or more vehicles that transmit point cloud data, based on the heat map information generated by itself and the heat map information generated in the MEC server 10b. This makes it possible to achieve network load balancing over a wider geographical area.
  • FIG. 4 is a block diagram showing an example of the hardware configuration of the MEC server 10 according to the present embodiment.
  • the MEC server 10 includes a CPU 41, a ROM 42, a RAM 43, an external storage device 44 (such as an HDD), and a communication device 45 (a communication interface).
  • a program stored in any of the ROM 42, the RAM 43, and the external storage device 44 for executing the functions of the MEC server 10 is executed by the CPU 41.
  • the CPU 41 may be replaced by one or more processors such as an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), and a DSP (digital signal processor).
  • the communication device 45 transfers (receives and transmits) a packet transmitted between a node in the EPC 20 and each eNB connected to the MEC server 10 under the control of the CPU 41, and communicates with each eNB ( Communication with the vehicle via each eNB may be performed.
  • the communication device 45 can also communicate with another adjacent MEC server under control of the CPU 41.
  • the MEC server 10 may have a plurality of communication devices 45 with different connection destinations.
  • the MEC server 10 may include dedicated hardware for executing each function, or may execute a part of the hardware and a computer that operates a program to execute other parts. Also, all functions may be performed by a computer and a program.
  • FIG. 5 is a block diagram showing an example of the functional configuration of the MEC server 10 according to the present embodiment.
  • Each function of the MEC server 10 is, for example, a logical function realized by the hardware in FIG. 4 and can be realized by the CPU 41 executing a program stored in the ROM 42 or the like.
  • the MEC server 10 includes a communication information acquisition unit 51, a communication information collection unit 52, a communication information management unit 53, a communication information provision unit 54, and a dynamic map application (DMAP) 55.
  • DMAP dynamic map application
  • the communication information acquisition unit 51 has a function of analyzing the contents of packets transmitted between each eNB and the EPC 20.
  • the communication information acquisition unit 51 has an RNIS function of acquiring network related information such as communication quality in the mobile network based on the analysis result of such a packet, and transmits the API of the RNIS function to the communication information collection unit 52. provide.
  • the communication information acquisition unit 51 acquires communication status information indicating the communication status in each of a plurality of (managed) cells corresponding to a plurality of eNBs connected to the MEC server 10 using this RNIS function.
  • the communication information collection unit 52 periodically collects communication status information using the communication information acquisition unit 51 (RNIS function), and transmits the collected communication status information to the communication information management unit 53.
  • the communication information management unit 53 manages the heat map information by generating the heat map information as described above from the communication state information each time the communication state information is received, and storing the heat map information in the RAM 43 or the external storage device 44.
  • the communication information provider 54 periodically acquires the heat map information managed by the communication information manager 53 and provides the DMAP 55 with the heat map information.
  • the DMAP 55 is an application for providing a dynamic map to a vehicle traveling in a plurality of cells to be managed.
  • a dynamic map for example, point cloud data, quasi-static information, quasi-dynamic information and dynamic information
  • Point cloud data is acquired from the vehicle.
  • the DMAP 55 is used to update the dynamic map in the MEC server 10 among the vehicles traveling in the plurality of cells to be managed based on the heat map information provided from the communication information provider 54. Determine one or more vehicles to transmit point cloud data. Further, the DMAP 55 requests the determined one or more vehicles to transmit point cloud data to the MEC server 10.
  • eNB # 1 and eNB # 2 are connected to the MEC server 10, and a road passing through adjacent cells # 1 and # 2 formed by eNB # 1 and eNB # 2 is a vehicle group A and B are traveling.
  • each vehicle of vehicle group A and B is drive
  • MEC server 10 transmits point cloud data to vehicle # 1 included in vehicle group A based on the heat map information.
  • An example of requesting transmission of among the vehicles included in the vehicle group A, attention is paid to the vehicle # 1, but the same applies to other vehicles included in the vehicle group A. Further, among the vehicles included in the vehicle group B, attention is paid to the vehicle # 2, but the same applies to other vehicles included in the vehicle group B.
  • FIG. 7 is a diagram showing an example of the use status of communication resources (communication band) before and after the start of transmission of point group data from the vehicle # 1 in the cells # 1 and # 2 of FIG. It is.
  • communication resource of cell # 2 to which vehicle # 1 is moving is an empty communication resource than cell # 1 in which vehicle # 1 is traveling.
  • the (available bandwidth) is small (ie, the communication bandwidth usage rate Br is high), which indicates that communication resources are under pressure.
  • the DMAP 55 of the MEC server 10 requests the vehicle # 1 to transmit point cloud data not in the cell # 2 but in the cell # 1.
  • DMAP55 rather than cell # 1 of the vehicle # 1 is traveling, towards the cell # 2 as the destination of the vehicle # 1, free bandwidth is large (i.e., low usage B r of the communication band)
  • the process opposite to the above process is performed. That is, by requesting the vehicle # 1 to transmit the point cloud data in the cell # 2 instead of the cell # 1, the DMAP 55 equalizes the network load involved in the communication between the vehicle and the MEC server 10 between the cells.
  • FIGS. 8 and 9 are sequence diagrams of communication between the vehicle and the MEC server 10. As described with reference to FIGS. 6 and 7, the vehicle # 1 traveling in the cell # 1 is shown. Shows a processing procedure of the MEC server 10 in the case of requesting transmission of point cloud data.
  • the vehicle # 1 in the cell # 1 performs a radio connection process (attach process) on the eNB # 1, and the vehicle # 2 in the cell # 2 wirelessly to the eNB # 2 Perform connection processing (attach processing).
  • the wireless connection process to each eNB may be a handover process accompanying the movement of a vehicle between cells.
  • the vehicle # 1 accesses the MEC server 10 and starts communication for acquiring the quasi-static information, the quasi-dynamic information, and the dynamic information included in the dynamic map from the DMAP 55.
  • the vehicle # 2 accesses the MEC server 10 and starts communication for acquiring the quasi-static information, the quasi-dynamic information, and the dynamic information included in the dynamic map from the DMAP 55.
  • the quasi-static information, the quasi-dynamic information and the dynamic information are information necessary for the automatic traveling of the vehicles # 1 and # 2. Therefore, vehicles # 1 and # 2 acquire semi-static information, quasi-dynamic information and dynamic information from MEC server 10 periodically while traveling according to the update frequency of each information (FIG. 2B). To run.
  • the communication information collection unit 52 calls the communication information acquisition unit 51 (RNIS function) to request communication status information corresponding to the cell # 1 and the cell # 2.
  • the communication information acquisition unit 51 acquires communication status information by the RNIS function, and returns a response including the acquired communication status information to the communication information collection unit 52.
  • 10A and 10B are diagrams showing an example of communication status information acquired by the communication information acquisition unit 51.
  • the communication status information includes, as shown in FIG. 10A, information on vehicles communicating in each cell, and information indicating communication quality (throughput) for each vehicle. Also, as shown in FIG. 10B, the communication status information further includes information indicating the usage status of the communication resource (radio resource) in each cell.
  • the communication information collection unit 52 transmits the communication status information included in the response to the communication information management unit 53 in S5.
  • the communication information management unit 53 generates and stores the above-mentioned heat map information from the received communication status information in response to the reception of the communication status information.
  • the above-described processes (S3 to S6) (81) are repeatedly executed at predetermined time intervals (for example, at intervals of 5 seconds).
  • the heat map information continues to be updated at predetermined time intervals.
  • the communication information management unit 53 is obtained from the communication status information, obtains a time average of the utilization B r of the communication resources of each cell, may generate heat map information based on the average the time. This makes it possible to achieve network load leveling without being affected by instantaneous traffic increase.
  • the communication information providing unit 54 requests the communication information management unit 53 for heat map information.
  • the communication information management unit 53 returns a response including the stored heat map information to the communication information providing unit 54 in S8.
  • the communication information provision unit 54 notifies the DMAP 55 of the heat map information included in the response in S9.
  • the DMAP 55 determines one or more vehicles that transmit point cloud data to the MEC server 10 each time the heat map information notification is received. For example, DMAP55 among the cell # 1 and cell # 2 (in this example, cell # 1) cell usage rate B r is low communication resources in utilization B r is the threshold B th (e.g., 0.7 If not (B r ⁇ B th ), the vehicle # 1 traveling in the cell # 1 is requested to transmit point cloud data to the MEC server 10. In the DMAP 55, when the usage rate B r1 exceeds the predetermined threshold B th (B r1 > B th ), the vehicle # 1 traveling in the cell # 1 is a point to the MEC server 10 Does not require transmission of group data.
  • B th e.g., 0.7
  • the DMAP 55 predicts the staying time of each vehicle in the cells # 1 and # 2, and prioritizes the vehicle when the staying time is long, and determines it as a vehicle that transmits point cloud data, It may request transmission of data.
  • the DMAP 55 identifies and identifies the position and the traveling direction of each vehicle in the cells # 1 and # 2 based on, for example, quasi-static information, quasi-dynamic information, and dynamic information corresponding to each vehicle.
  • the residence time of each vehicle in the cell is predicted based on the position and the traveling direction. Thereby, it is possible to improve the temporal use efficiency of the communication resource used in the communication between the vehicle and the MEC server 10 in one cell.
  • the DMAP 55 can request the vehicle # 11 to transmit point cloud data in the cell # 1.
  • FIG. 11B shows a case where the usage rate Br2 of the communication resource becomes equal to or less than the threshold B th after the vehicles # 11 and # 12 move to the cell # 2.
  • the DMAP 55 may request the vehicle # 11 to transmit point cloud data in the cell # 2 as a result of the prediction of the staying times of the vehicles # 11 and # 12 in the cell # 2.
  • the vehicle which transmits point cloud data may be determined based on the communication quality (throughput) included in the communication status information. For example, a vehicle having high throughput may be prioritized to be determined as a vehicle that transmits point cloud data. Thereby, the point cloud data can be transmitted from the vehicle to the MEC server 10 in a shorter time, and it becomes possible to shorten the usage time of the communication resource for the transmission.
  • the above-described processes (S7 to S10) (82) are repeatedly performed at predetermined time intervals (for example, 10 seconds).
  • DMAP 55 requests vehicle # 1 to transmit point cloud data in S11.
  • the DMAP 55 may be able to designate data other than point cloud data as data to be transmitted.
  • the DMAP 55 determines, as a result of the determination in S10, a plurality of vehicles including the vehicle # 1 included in the vehicle group A as a vehicle transmitting point cloud data, the DMAP 55 simultaneously operates on the plurality of vehicles. A request may be sent.
  • the vehicle # 1 In response to the transmission request in S11, the vehicle # 1 starts transmitting point cloud data to the MEC server 10 in S12.
  • the vehicle # 1 receives the quasi-static information, the quasi-dynamic information, and the dynamic information (specific information) among the information constituting the dynamic map from the MEC server 10 at predetermined time intervals, in S11
  • the point cloud data is transmitted to the MEC server 10 in response to the transmission request.
  • FIG. 9 shows the processing procedure of the MEC server 10 when the vehicle # 1 moves from the cell # 1 to the cell # 2 in S21 after the processing shown in FIG.
  • the vehicle # 1 performs a handover process for switching the connection destination from the eNB # 1 to the eNB # 2.
  • the vehicle # 1 communicates (ie, receives quasi-static information, quasi-dynamic information and dynamic information, and transmits point cloud data) with the MEC server 10 via the eNB # 2. It will continue.
  • the processes 81 and 82 described above are periodically repeated.
  • process 82 the determination of the vehicle for transmitting the point cloud data to the MEC server 10, DMAP55, because the utilization B r2 of communication resources in the cell # 2 is higher than the threshold value B th (B r2> B th ), vehicle # 1 will be excluded from vehicles transmitting point cloud data.
  • the DMAP 55 requests the vehicle # 1 to stop the transmission of the point cloud data.
  • the DMAP 55 may be able to specify data other than the point cloud data as data for which transmission should be stopped.
  • vehicle # 1 stops transmission of point cloud data to the MEC server 10 in S24.
  • vehicle # 1 is in a state of receiving quasi-static information, quasi-dynamic information, and dynamic information (specific information) from MEC server 10 at predetermined time intervals without transmitting point cloud data. .
  • the MEC server 10 generates heat map information on the usage status of the communication resource from the communication status information obtained using the RNIS function. Furthermore, the MEC server 10 transmits at least one point cloud data to the MEC server 10 among vehicles traveling in the plurality of cells to be managed by the MEC server 10 based on the generated heat map information. Determine the vehicle and request transmission of point cloud data. This makes it possible to equalize the network load involved in the communication between the MEC server 10 providing the dynamic map and the vehicle. There is no need to introduce additional functions such as the transmission function of communication quality information into the automatic travel system equipped on the vehicle for the generation of heat map information by the MEC server 10, thus reducing the effort of kitting the automatic travel system it can.
  • the MEC server (server apparatus) according to this embodiment can be realized by a computer program for causing a computer to function as the MEC server.
  • the computer program is stored in a computer readable storage medium and can be distributed, or can be distributed via a network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Traffic Control Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon l'invention, un serveur informatique de bord à accès multiple (MEC) fournit une carte dynamique pour le déplacement automatique d'un véhicule dans une pluralité de cellules connectées entre une pluralité de stations de base et un réseau central et correspondant à la pluralité de stations de base. Le serveur MEC acquiert des informations de situation de communication indiquant une situation de communication dans chacune de la pluralité de cellules, et génère, à partir des informations de situation de communication acquises, des informations de carte de chaleur concernant la situation d'utilisation de ressources de communication. Le serveur MEC détermine, sur la base des informations de carte de chaleur générées, un ou plusieurs véhicules qui transmettent des données de groupe de points au serveur MEC parmi des véhicules se déplaçant dans la pluralité de cellules, et demande la transmission des données de groupe de points.
PCT/JP2018/025361 2017-11-06 2018-07-04 Dispositif de serveur, son procédé de commande et programme Ceased WO2019087464A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2017-213771 2017-11-06
JP2017213771A JP6765362B2 (ja) 2017-11-06 2017-11-06 サーバ装置及びその制御方法、並びにプログラム

Publications (1)

Publication Number Publication Date
WO2019087464A1 true WO2019087464A1 (fr) 2019-05-09

Family

ID=66333005

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2018/025361 Ceased WO2019087464A1 (fr) 2017-11-06 2018-07-04 Dispositif de serveur, son procédé de commande et programme

Country Status (2)

Country Link
JP (1) JP6765362B2 (fr)
WO (1) WO2019087464A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113375681A (zh) * 2020-03-09 2021-09-10 丰田自动车株式会社 地图数据更新装置及存储地图数据更新用计算机程序的存储介质
CN115841019A (zh) * 2022-11-04 2023-03-24 云南大学 热敏条件下mec网络中集成任务计算时间的最小化优化方法
EP4310813A4 (fr) * 2021-03-17 2024-05-01 Mitsubishi Electric Corporation Serveur d'application, station de base, système de distribution de cartes dynamiques, circuit de commande, support de stockage et procédé de distribution d'informations

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6999625B2 (ja) * 2019-11-06 2022-02-04 財団法人車輌研究測試中心 環境情報を提供可能なダイナミックマップ情報を生成するための方法およびシステム
CN112911344B (zh) * 2019-11-19 2024-05-24 中兴通讯股份有限公司 一种发送方法、存储介质和电子装置
JP7497999B2 (ja) 2020-03-05 2024-06-11 本田技研工業株式会社 情報処理装置、車両、プログラム、及び情報処理方法
JP7321122B2 (ja) * 2020-05-11 2023-08-04 Kddi株式会社 情報配信装置、情報取得装置、情報配信システム、コンピュータプログラム及び情報配信方法
CN114694368A (zh) * 2020-12-28 2022-07-01 比亚迪股份有限公司 车辆的管控系统
EP4303628A4 (fr) * 2021-03-01 2024-12-25 Pioneer Corporation Dispositif de traitement d'informations, procédé de commande, programme et support d'enregistrement
JP2022134583A (ja) * 2021-03-03 2022-09-15 株式会社デンソー 走行制御装置
KR102621696B1 (ko) * 2021-08-27 2024-01-08 한국건설기술연구원 가변 도로교통정보 제공 장치
US12356246B2 (en) 2022-05-31 2025-07-08 Rakuten Mobile, Inc. Network management for offloading

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016039445A (ja) * 2014-08-06 2016-03-22 日本電気株式会社 自己最適化移動体通信システム
JP2017194915A (ja) * 2016-04-22 2017-10-26 トヨタ自動車株式会社 周辺情報収集システム及び周辺情報取得装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2016039445A (ja) * 2014-08-06 2016-03-22 日本電気株式会社 自己最適化移動体通信システム
JP2017194915A (ja) * 2016-04-22 2017-10-26 トヨタ自動車株式会社 周辺情報収集システム及び周辺情報取得装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
KOYAMA HIROSHI ET AL.: "Construction of dynamic map for automated driving", SYSTEMS, CONTROL AND INFORMATION, vol. 60, no. 11, 463-468, 2016, pages 7 - 12, XP055613804 *
OKAMOTO SHOSHEI ET AL.: "An initial study on decrease of transmission delay by using MEC in transmission of dynamic map data", IEICE TECHNICAL REPORT, vol. 117, no. 103, 11 June 2017 (2017-06-11), pages 109 - 113 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113375681A (zh) * 2020-03-09 2021-09-10 丰田自动车株式会社 地图数据更新装置及存储地图数据更新用计算机程序的存储介质
US11933629B2 (en) 2020-03-09 2024-03-19 Toyota Jidosha Kabushiki Kaisha Map data updating device and storage medium storing computer program for map data updating
CN113375681B (zh) * 2020-03-09 2024-10-22 丰田自动车株式会社 地图数据更新装置及存储地图数据更新用计算机程序的存储介质
EP4310813A4 (fr) * 2021-03-17 2024-05-01 Mitsubishi Electric Corporation Serveur d'application, station de base, système de distribution de cartes dynamiques, circuit de commande, support de stockage et procédé de distribution d'informations
CN115841019A (zh) * 2022-11-04 2023-03-24 云南大学 热敏条件下mec网络中集成任务计算时间的最小化优化方法

Also Published As

Publication number Publication date
JP2019087847A (ja) 2019-06-06
JP6765362B2 (ja) 2020-10-07

Similar Documents

Publication Publication Date Title
JP6765362B2 (ja) サーバ装置及びその制御方法、並びにプログラム
JP7775872B2 (ja) 優先度の高い通信およびＱｏＳフィードバックのためのリソースの再割振りおよび予約
KR102002807B1 (ko) V2x 통신을 지원하는 통신 시스템에서 이종 rat를 사용한 부하 분산 방법 및 장치
KR20230035038A (ko) 근접 기반 서비스 원격 및 중계 엔티티 서비스 품질 관리
JP6858154B2 (ja) ノード装置及びその制御方法、並びにプログラム
US20210029674A1 (en) Communication device
WO2023082878A1 (fr) Procédé et appareil de communication
JP7468321B2 (ja) 通信制御装置、通信制御方法、及び中継サーバ
JP2019062510A (ja) 管理装置及びその制御方法、並びにプログラム
US20250150901A1 (en) Method for managing qos
JP2019146072A (ja) 通信制御装置及びその制御方法、並びにプログラム
US12464430B2 (en) LMF assisted MRO
WO2023082877A1 (fr) Procédé et appareil de communication
US20230199636A1 (en) Vehicle wireless communication device and communication control method
JP6951530B2 (ja) サーバ装置及びその制御方法、並びにプログラム
Yamada et al. Temporal traffic smoothing for IoT traffic in mobile networks
EP3503639B1 (fr) Procédé de gestion de mobilité, dispositif côté réseau, terminal d'internet des véhicules et système
EP4009714B1 (fr) Activation de support en fonction de l'état de la batterie
CN117478588B (zh) 高可用性冗余路由交换方法及系统
US20230209436A1 (en) Communication device, communication control method, communication method, and non-transitory computer-readable storage medium
Grammatikos et al. A mobile edge computing approach for vehicle to everything communications
CN113303007A (zh) 网络节点和在其中执行的用于处理基带资源的方法
EP4213126A1 (fr) Dispositif de radiocommunication pour véhicule et procédé de commande de communication
WO2020001769A1 (fr) Gestion de la qualité de service et de la mobilité destinée à des utilisateurs de véhicules avancés d'un réseau sans fil
WO2020095568A1 (fr) Serveur de gestion, procédé de traitement de données, et support non transitoire lisible par ordinateur

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18874185

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18874185

Country of ref document: EP

Kind code of ref document: A1