What you need to know
- China's ambassador to the U.K. accused the Conservative party of engaging in a witch-hunt over Huawei's 5G security fears.
- In France, the government said that further reprisal against Huawei could see similar sanctions enacted against European firms like Nokia and Ericsson in China
- The Chinese government also requested for more transparent criteria in France.
As the UK continues to make decisions over its 5G network, China takes umbrage with Huawei's role as a villain on this stage. While the U.K. government decided not to ban Huawei from its 5G network, senior conservatives have argued that Huawei and other high-risk vendors be phased out slowly from key parts of telecoms infrastructure — or be ruled out entirely.
"I think what they are doing is a kind of a witch-hunt," China's ambassador to the UK, Liu Xiaoming told the BBC, "Huawei is a private-owned company, nothing to do with the Chinese government... the only problem they have is they are a Chinese company."
While the U.S. has banned Huawei from its shores entirely and even sought up ways to take the fight to Huawei on a global scale, China has taken a dim view of the whole affair.
The government also took a strong stance in France, as the firm was preparing to roll out its own 5G network. It warned them against taking restrictive steps against Huawei, noting that European companies like Nokia and Ericcson also do business in China. It would be a shame, the government implied, if anything happened to them as a result of discrimination against Huawei.
Calling for transparency via a statement on the embassy website, the Chinese government said:
For its part, Huawei has always acted extremely positive about the EU's approach to 5G security, hailing it as a "fact-based approach."
Just the way how China makes its treats to countries for not going with their tech champions 5G they should just get band outright period.
Signs of desperation...
Thank you for signing up to Android Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.