My Wiki!

20190322T1117+0000: D3.4 Telco

  • IMAC?? leaves consortium
  • Internal discussion on right leading partners
    • mno, authorities, etc
  • ToC Deliverable
    • Kostsas: only reporting, revise when d2.x are mature
    • Comment.
  • Meeting, core team adhoc, telco in few weeks.

20190222T1014+0000:

  • local trial site focuses on aspects that can support corridor use-cases (e.g., TR-GR): handover, beam forming, etc.
    • TR use case see what I see: needs MEC, handover
    • TR border control: exchange information between countries, handover, data fusion
  • TODO for local site:
    • in 2 weeks. align with border use-cases from border partner

20190319T1043+0000: German site meeting @DAI

1. Use case discussion

1.1 L4 Platooning

  • MK presents
  • Do we have 2 other L4 vehicles (Valeo, JD, vicom)?
    • Valeo: for highway L4 is available
  • DE: getting 4G, 5G network slice from Deutsche Telekom
    • What API for slice config we can use?
  • Can TR corridor support for the use-case? (MNOs, Handover)
    • Requirements for TR corridor demo:
      • Certification for the AV to operates on TR road (in DE we have TüV Nord)
      • Timeline 2020-2021 (MK, Francoi)
      • Bring AV to corridor for trial
      • ITS services: LDM, EDM, cloud
      • Similar operator infrastructure as in DE trial site

1.2 HD Map

  • Gorka presents
  • Connecting EDM, 3D maap with relevant standards, e.g., AI, OEM
  • Can be align with TR but preferably with PT corridor (deployment at 1 place)
    • PT is also preferred by DE if telefonica joins
    • Coordinate more often with target corridor site
  • Align with other Deliverable
  • Challenges of data sharing, trust (sensors data at EDM), inter-stakeholders, authority
    • Addresses in this project or extended activities.

1.3 New use case from Daimler/JD


Navigation