Input of downloadFirmwareComponent RPC

1 view
Skip to first unread message

Thorsten Heinze

unread,
Feb 17, 2021, 6:57:48 AMFeb 17
to wireless-...@opennetworking.org, Martin Skorupski (External), EDUARDO YUSTA PADILLA, Axel Lauer, Andreas Lattoch (External), Andreas Chrissostomidis, Andreas Haack
Hi together,

in regard to today's discussion about how to structure the input information of the downloadFirmwareComponent RPC, I had the chance to catch two super experts from Telefonica Germany BackOffice for a brief interview.

It's several different files to be downloaded for updating an individual device.
These files are located in the same folder on the FTP server. (The folders are distinguishing device types.)

Based on this information, I would say there should be a separate filename : string attribute aside the uri : string attribute.

Best regards,
Thorsten


Thorsten Heinze | Telefónica Germany GmbH & Co. OHG
Lead Access Network Design
Access Network Technology
Georg-Brauchle-Ring 50 80992 München
M +49 (0)176 2442 4852 | T +49 (0)89 2442 4852 | F +49 (0)89 2442 7268
thorste...@telefonica.com<mailto:thorste...@telefonica.com> | www.telefonica.de<http://www.telefonica.de/>

Bitte finden Sie hier die handelsrechtlichen Pflichtangaben: www.telefonica.de/pflichtangaben<http://www.telefonica.de/pflichtangaben>




________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
winmail.dat

Spreafico, Daniela (Nokia - IT/Vimercate)

unread,
Feb 17, 2021, 8:28:53 AMFeb 17
to Thorsten Heinze, wireless-...@opennetworking.org, Martin Skorupski (External), EDUARDO YUSTA PADILLA, Axel Lauer, Andreas Lattoch (External), Andreas Chrissostomidis, Andreas Haack
Hi all,
in addition to the file name to be downloaded to the device (according to vendor device behaviour this could be the first file, a descriptor, defining the list of files that the device get from the server) , it is needed to define on this rpc also the information useful to fill the appropriate class for sw package: firmwareComponentVersion, firmwareComponentName .
 
BR, Daniela
 
_____________________________________________
From: wireless-...@opennetworking.org <wireless-...@opennetworking.org> On Behalf Of Thorsten Heinze
Sent: Wednesday, February 17, 2021 12:58 PM
To: wireless-...@opennetworking.org
Cc: Martin Skorupski (External) <martin.s...@highstreet-technologies.com>; EDUARDO YUSTA PADILLA <eduardo.yu...@telefonica.com>; Axel Lauer <axel....@telefonica.com>; Andreas Lattoch (External) <andreas.latt...@telefonica.com>; Andreas Chrissostomidis <andreas.chr...@telefonica.com>; Andreas Haack <andrea...@telefonica.com>
Subject: Input of downloadFirmwareComponent RPC
Sensitivity: Confidential
 
 
Hi together,
 
in regard to today’s discussion about how to structure the input information of the downloadFirmwareComponent RPC, I had  the chance to catch two super experts from Telefonica Germany BackOffice for a brief interview.
 
It’s several different files to be downloaded for updating an individual device.
These files are located in the same folder on the FTP server. (The folders are distinguishing device types.)
 
Based on this information, I would say there should be a separate filename : string attribute aside the uri : string attribute.
 
Best regards,
                Thorsten
 
Thorsten Heinze | Telefónica Germany GmbH & Co. OHG
Lead Access Network Design
Access Network Technology
Georg-Brauchle-Ring 50  80992 München
M +49 (0)176 2442 4852 | T +49 (0)89 2442 4852 | F +49 (0)89 2442 7268


Bitte finden Sie hier die handelsrechtlichen Pflichtangaben: www.telefonica.de/pflichtangaben
Reply all
Reply to author
Forward
0 new messages