including data extraction from EV batteries

Concept.
https://youtu.be/5p4N_G4ndlY The project.

Excellence The ELECTRIFIC project addresses the call “GV.8-2015

Electric vehicles’ enhanced performance and integration into the transport system and the grid”.
Specifically, it targets the third domain of the call: Integration   of  the  overall  cycle  of  EV  energy  management  into  a  comprehensive EV battery  and ICT-based  re-charging  system management,  providing  ergonomic  and seamless user support.
Objectives “Because of its shortcomings — driving range, cost and recharging time — the electric vehicle is not a viable replacement for most conventional cars,” Takeshi Uchiyamada, Toyota [1] Changing, this is the challenge.
And the prize is: the electric vehicle (EV) theoretically can be run entirely by renewable en ergy resources if travel plans and charging schedules are coordinated among multiple users and aligned with power supply and grid requirements.
ELECTRIFIC will develop novel technologies and theoretical understanding that enable highly attractive and sustainable electro-mobility through smart vehicle-grid integration .  The technologies will be developed at three layers – the grid, the EV and the user.
Seamless and ergonomic collaboration between all layers will be created to make using EVs at least as convenient and attractive as combustion engine vehicles, all the while optimizing the grid, .

The EV infrastructure utilization and maximizing the use of renewable energy resources

An intelligent charging infrastructure that integrates grid optimization, renewable energy and user guidance will be bundled into a Decision Making Engine (DME) with an advanced drivers assistant system (ADAS) as human machine interface (HMI).
The DME provides multi-criteria routing alternatives customized to user based energy-aware EV routing and charging needs.
Through the provision of APIs and a common data layer, the system is agnostic to car manufacturers and navigation systems so it can become a European standard solution for energy-aware EV mobility.
Before the driver enters, the DME has available all data about the grid stability and grid optimisation opportunities , the EV and battery management system (BMS) parameters like State of Charge (SOC),  State of Health (SOH), the country and weather conditions, and the geography.
When identifying the user and the organisational requirements respectively, the system has all data about user policies, schedules and user contacts which have been collected from previous uses, the Personal Information Manager and/or certain Enterprise Resource Planning Tools.
Objective 1 To radically simplify the use of EVs by seamlessly integrating charging into the EV usage cycle, thus making the convenience of EVs match or even surpass the convenience of combustion-engine vehicles.
Research Area Driver’s need – and grid-aware EV travel planning and energy management algorithms Result/Metric Scalable EV travel planning and energy management algorithms capable of considering the planned (daily) activities of the user, .

The availability of the charging capacity and the state of the EV itself

The algorithms will be open to integration with in-car navigation and battery management systems, integration with charging capacity allocation procedures and persuasive EV user interfaces.
Metric: Within ELECTRIFY an approach to an ordinal evaluation of attractiveness by users will be developed.
Through the research and technical activities in ELECTRIFIC attractiveness of EV will for a majority of user groups be rated higher than that of combustion-engine vehicles.
Expected impact Significant improvements to the EV usage ergonomy.

The eco-friendliness of EVs and the cost-performance ratio of EV

all contributing to faster and broader market take-up.
Higher utilization of renewable energy sources for EV charging Objective 2 To improve the interoperability within the electromobility ecosystem by creating a normalized EV data layer that homogenizes all kinds of external data sources and is agnostic to car and batteries manufacturers and to ADAS developers.
Research areas Development of battery friendly charging algorithms Development of battery health monitoring to support battery friendly long term allocation of EVs in a car fleet Result/Metric The creation of a common EV mobility data model and the provision of OpenAPIs and services related to EV mobility.
Metric: Ensure compatibility between ELECTRIFIC ADAS approach and two major manufacturers of batteries, cars and ADAS.
Expected impact European standardization for interfaces that allow energy-aware charging routing and BMS, including data extraction from EV batteries, grid, charging stations and personal calendars.
Objective 3 To improve the grid friendliness of EV charging and to increase the intake of renewable energy at charging stations through decentralized monitoring and control of the charging process.
Research areas · Maximising the intake of renewables generated at the same geographical location as the charging stations, in addition to those in the mix of the power grid.
· Charging station grid-friendliness by taking into account the quality of power.
Result/Metric Design and implementation of a completely decentralized and non-intrusive distribution grid monitoring and control scheme.
Voltage band: Reduce number of necessary interventions of grid operators due to voltage band fluctuations by 20%.

Increase share or renewable energy at the computed energy mix in EV batteries by 20%

depending on renewable resource availability.

Expected impact To charge EVs cost-effectively

maximally sustainable and yet conveniently, by helping to solve one of the most pressing and still unsolved management challenges of distribution grid operators.
Objective 4 To better align the behaviour of EV users with the requirements of the grid by incentivizing behaviours that maximize battery lifetime, range, and the intake of renewables.
Research Area · Specify psychological variables that predict which types of rewards, monetary or psychological, allow the user to best adopt optimal behaviour patterns.
· Market-based EV charging capacity allocation and demand management · Identify the optimal solution for the design of financial incentives to change routing, charging and driving behaviour.
Result/Metric Insights into the behavioural economics, .

And consumer psychology of EV usage

Optimised and scalable design for communicating between optimized DME and user

Novel algorithms through which limited charging capacity can be allocated to EVs in a way that optimally balances the convenience of using EVs to the user, the utilization of the charging infrastructure and the use of renewable energy resources, all while taking into account power transmission constraints of the grid.
The techniques will be able to operate in a heterogeneous environment involving a potential large number of grid operators, .

EV charging facility providers and EV vehicle fleet operators

The algorithms will be able to accommodate different levels of interaction between the actors in the EV ecosystem.
Metrics: Increase the adherence to ADAS recommendation and thereby the number of grid friendly charging operations by 40% compared to baseline.
Expected impact Seamless integration of batteries, smart grid and renewable sources leading to a) enormous savings in grid maintenance; b) increased attractiveness of EVs Dynamic balance between the demand for EV charging and available charging capacity, which maximizes the utilization of available charging capacity while it minimizes the occurrence of situations in which charging capacity is not available to EVs than need it most.

API Security in a Multi-Cloud Environment

API Security in a Multi-Cloud Environment.
Balaji Radhakrishnan, PMP, CISSP.
July 8, 2020.
, , API Security, , For App Developers, For Enterprise Architects.
The key challenge for enterprises in this digital journey using APIs is to ensure this exchange of information is occurring with the right consumer with the right privileges.
This is where API Security, one of the 5 Pillars of API Management , plays a key role in protecting enterprise digital assets.
API Security.
For most modern web, SPA, and mobile applications, .

Both OAuth 2.0 and OpenID connect are fundamental for API Security

OpenID connect with JWT has become the gold standard for today’s enterprise that has applications spread across a multi-cloud environment.
In one use case, where a consumer tries to access a backend microservice that resides in a multi-cloud (AWS/Azure/GCP) environment.
In a typical gateway deployment model.

We may have an API Gateway in the DMZ as our edge gateway

and it may be mutually integrated with several backend microservice applications that reside either on-premises or cloud.
For this example, .

This enterprise is having few of those applications in AWS and few in Azure

Each of those applications is front-ended with a parallel gateway and expects a signed JWT.
The API gateway will validate and authorize the request to relevant backend applications in their respective cloud platform.
With that said, when a request reaches the Edge gateway in DMZ: The API gateway may apply the required security policies that leverage OIDC protocols by using the “Authorization” header with a bearer token, upon successful authentication and corresponding authorization using the scope.
it may very well apply other policies that would protect their digital assets from common OWASP attacks.
Apply rate limit and throttle the incoming request.
And finally, .

Route the request to backend application (resides in AWS or AZURE)

But before routing, it could also bridge the security protocol with a custom JWT claims that would have relevant authorization details for cloud gateway to validate and authorize.
Also, sign and encrypt the JWT as needed (JWS and JWE) using specific private keys applicable for a particular backend application that resides in the cloud.
Once the request reaches AWS or AZURE cloud (parallel) API gateway: it may intercept the request and look for JWT header for validation and authorization.
For validating the signed JWT, it may call the OIDC JWKS , which is a read-only endpoint that would return JWKS containing public keys that enable cloud gateway to validate a JSON Web Token (JWT) issued by OpenID Connect Provider.

Once JWT is validated and decoded

the cloud gateway can extract required claims in the payload and authorize the call and route the request to appropriate backend applications/microservices.
A key challenge an enterprise usually faces here, when they have hundreds of applications deployed across multi-cloud environment, is that “JWKS URI” endpoint might return all the key set associated with a provider and that would be a security impact.
To avoid this situation, the calling API gateway may send a particular kid (key identifier) claim associated with a call (from JWT header).
So that provider can return only that specific public key associated with that kid claim to the cloud API gateway.
Conclusion.
With the growing app economy, there is an increased focus on digital transformation.
And APIs are becoming a key enabler in establishing secure communication with backend applications and Microservices.
Products like Layer7 API Management fulfill the demand of today’s enterprise in both securing and protecting their digital assets (applications/microservices) with OOTB capabilities and features.
As I have shown above, Layer7 API Gateway can provide several such security protocols and integrates with a broad list of IAM systems and supports OAuth2/OpenID Connect, PCI-DSS, FHIR, and PSD2.
Layer7 API Gateway is OOTB capable of bridging several security standards and solutions between consumers and providers.

If you don’t have Layer7 API Gateway then

you need to ensure your gateway provider provides similar supports to a wide range of security protocols and solutions for API Security along with comparable microservices (secured) integration options.
Balaji Radhakrishnan, PMP, CISSP.
Balaji Radhakrishnan, PMP, .

CISSP has been in API management for the past 6+ years

Prior to that.

He was working in the SOA/BPM space

with 20+ years of overall experience in the Integration domain.
Currently, he is working for Broadcom as a Solution Architect in Product Pre-Sales, .

Helping customers to successfully implement secure API Management solutions

If you use the Discord Bot List

If Discord is a chat platform for gamers and other people

why does it need bots.
How do Discord bots work.
How do you build them.
What tricks can they pull off.
All these questions and more will be answered on this page.Gaming Discord is a chat platform that took over from the all-conquering TeamSpeak a couple of years ago.
Unlike Twitch or Mixer, these are just chat channels and not about streaming.
A Slack for gaming or other interests if you like.
It has been around for a while and counts its users by the million.
It’s easy to use, easy to run a channel and manage communities.
That ease of use is one reason why it is so popular.
Bots are a small part of discord but one of the elements that makes it stand out.
This page will discuss everything you need to know about bots but were afraid to ask.
Why does Discord need bots.
Discord doesn’t need bots.
It has them because it can.
Bots can perform some useful tasks around the chat channels and provide an excuse for those comfortable with code to show off a little.
Bots aren’t about need but about want and they can be pretty cool.
Usually, bots are viewed negatively as they either spam your email inbox, try to engage you on websites with supposedly live chat and generally get in the way.

On Discord they have been turned into something useful and given specific

and mostly useful jobs to do.
How do Discord bots work.

Discord bots are programmed in JavaScript

Most bots use the same APIs that Discord uses to run so can integrate tightly into how the platform works.

Bots are legit and the people behind Discord actively encourage bot development

As long as the bot works within Discords ToS

you can get them to do whatever you like.

The Discord API is made up of two separate elements

the WebSocket API and REST API.

The WebSocket API takes input from Discord in order to perform its actions

The REST API is used for most bot actions such as updating permissions, kicking and banning and seek information.
This page goes into a lot of detail around the specifics of how a Discord bot is put together and used within the platform.
It was written by a bot developer who really knows his stuff.
He explains it way better than I could.

How do you build a bot for Discord

The link above describes how to build a Discord bot but I’ll provide a quick overview of what you need to put together a basic bot.
I’ll also link to some resources that give you examples of bot code so you can try different kinds of bot.
You can then take it much further if you want to.

Navigate to the Discord bot portal and log in

Create an account if you don’t have one.
Create a new application within the bot portal and record the Client ID and Secret.
Select the Bot tab on the left and record the Token in the center pane.
Download Node JS and install it.
Open a command prompt or terminal as an administrator.
Type or paste ‘npm i -g nodemon’ and hit Enter.
Download Notepad++or other text editing app.
You now have all the building blocks you need to code your bot.
This website has a walkthrough of the code part, as does this website and even How to Geek has a simple bot so you can see how it all works.
What can Discord bots do.
Discord bots can do pretty much anything you can program them to do as long as it complies with Discord’s T&Cs.
The Discord Bot List is a page dedicated to the weird and wonderful world of bots and includes the most popular and the most random bots on the platform.
The list includes bots that can record streams, provide memes, clean up old chats, moderate chat, provide leveling advice, tell jokes, give news updates and a whole lot more.
Most are made by enthusiasts while some are created by studios or companies.

All should work within Discord and can be connected to your Discord server

How to add a Discord bot to your server Adding a bot to your own Discord server is very straightforward.
You will spend longer finding a bot you want to use than you will adding it.

Log into Discord and have it open in a browser tab

Locate the bot you want to add and select the ‘Add Bot to Server’ button if there is one

Most bot repositories have such a button.
If you use the Discord Bot List, you would select Invite, to invite the bot to your server.
Select your server and select Authorize.
Complete the Captcha.
The bot will load into your server.
Once loaded, you should be taken to the bot’s admin page where you can configure exactly how it works and what it can and cannot do.
.