bodyType

customContents

entityId

printArticlePageQuery

filter

article

body

urlAlias

articleSectionsContent

articleSeoArticle

articleSourceHeaderArticle

contentSchemaRenderContent

contentSubHeadlineContent

contentHeadlineContent

mainImagePrintArticleArticle

authorBlockPrintArticleArticle

contentSponsorTagContent

articlePianoPaywallContent

scmpYoutubeContent

hooksTrackPageViewArticle

query printArticlePageQuery(
  $entityId: String!
  $customContents: [CustomContentInput]
  $bodyType: BodyFormatTypeEnum
) {
  article(filter: {entityId: $entityId}) {
    entityId
    body(customContents: $customContents, type: $bodyType) {
      json
    }
    urlAlias
    ...articleSectionsContent
    ...articleSeoArticle_3o8td4
    ...articleSourceHeaderArticle
    ...contentSchemaRenderContent
    ...contentSubHeadlineContent
    ...contentHeadlineContent
    ...mainImagePrintArticleArticle
    ...authorBlockPrintArticleArticle
    ...contentSponsorTagContent
    ...articlePianoPaywallContent
    ...scmpYoutubeContent
    ...hooksTrackPageViewArticle
    id
  }
}

fragment articlePianoPaywallContent on Content {
  __isContent: __typename
  ...hooksPaywallPromiseContent
}

fragment articleSectionsContent on Content {
  __isContent: __typename
  sections {
    value {
      ...helpersCheckIfNewsSectionInFirstIndexSection
      ...entityLink
      name
      id
    }
  }
}

fragment articleSeoArticle_3o8td4 on Article {
  ...hooksArticleSeoArticle
  ...helpersCheckIsPostiesArticle
  ...helpersGetArticleTypeArticle
  entityId
  publishedDate
  updatedDate
  summary {
    text
  }
  subHeadline {
    text
  }
  body(customContents: $customContents, type: $bodyType) {
    text
  }
  keywords
  sections {
    value {
      name
      id
    }
  }
  topics {
    name
    entityId
    id
  }
  urlAlias
  authors {
    name
    id
  }
  images {
    style(filter: {style: "768x768"}) {
      url
    }
  }
  readingTime
}

fragment articleSourceHeaderArticle on Article {
  urlAlias
  ...entityLink
}

fragment authorBlockPrintArticleArticle on Article {
  ...defaultArticleDateContent
  ...authorNamesArticle
}

fragment authorNameAuthor on Author {
  ...entityLink
  name
  entityUuid
}

fragment authorNamesArticle on Article {
  authorLocations
  authors {
    entityId
    location
    ...authorNameAuthor
    id
  }
}

fragment blockquoteQuoteContent on Content {
  __isContent: __typename
  ...contentShareWidgetContent
}

fragment checkersCheckContentContainsStarlingImageContent on Content {
  __isContent: __typename
  topics {
    entityId
    id
  }
}

fragment contentHeadlineContent on Content {
  __isContent: __typename
  headline
  socialHeadline
  ...contentHeadlineTagContent
  ...helpersUseContentSponsorContent
}

fragment contentHeadlineTagContent on Content {
  __isContent: __typename
  ...hooksContentHeadlineTagContent
}

fragment contentNewsletterWidgetContent on Content {
  __isContent: __typename
  topics {
    relatedNewsletters {
      ...helpersMassageToNewsletterItemNewsletter
      id
    }
    id
  }
  sections {
    value {
      relatedNewsletters {
        ...helpersMassageToNewsletterItemNewsletter
        id
      }
      id
    }
  }
  ... on Article {
    relatedNewsletters {
      ...helpersMassageToNewsletterItemNewsletter
      id
    }
  }
}

fragment contentSchemaRenderContent on Content {
  __isContent: __typename
  ...blockquoteQuoteContent
  ...imageContent
  ...inlineWidgetContent
  ...photoGalleryWidgetContent
  ...scmpYoutubeContent
}

fragment contentShareWidgetContent on Content {
  __isContent: __typename
  entityId
  urlAlias
  shortUrl
  socialHeadline
  headline
}

fragment contentSponsorTagContent on Content {
  __isContent: __typename
  ...helpersUseContentSponsorContent
}

fragment contentSubHeadlineContent on Content {
  __isContent: __typename
  subHeadline {
    json
  }
  summary {
    json
  }
  ...contentSchemaRenderContent
}

fragment defaultArticleDateContent on Content {
  __isContent: __typename
  ...hooksArticleDateUtilsContent
}

fragment entityLink on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  __typename
  entityId
  entityUuid
  urlAlias
  urlRedirect {
    toUrl
    id
  }
  application {
    entityId
    id
  }
  ... on Section {
    fullSectionPath {
      entityId
      id
    }
    parentSection
  }
  ...helpersAppBarVariantBase
  ...helpersApplicationBase
  ...helpersCheckIsPlusArticle
  ...helpersStyleSectionContent
}

fragment helpersAppBarVariantBase on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  ...helpersCheckIsLiveArticle
  ...helpersCheckIsPlusPage
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostiesPage
  ...helpersCheckIsPostMagazineArticle
  ...helpersCheckIsStyleArticle
  ...helpersSectionContent
  ...helpersStyleSectionContent
}

fragment helpersApplicationBase on BaseWithApplicationAndUrlAlias {
  __isBaseWithApplicationAndUrlAlias: __typename
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostiesPage
  ...helpersCheckIsPlusPage
}

fragment helpersCheckIfNewsSectionInFirstIndexSection on Section {
  name
}

fragment helpersCheckIsAmpEnabledArticle on Article {
  entityId
  types {
    value {
      entityId
      id
    }
  }
  sections {
    value {
      entityId
      id
    }
  }
  disableOffPlatformContent
  sponsorType
  published
  ...helpersCheckIsPlusArticle
  ...helpersCheckIsPostiesArticle
}

fragment helpersCheckIsLiveArticle on Article {
  flattenTypeIds
  liveArticle {
    status
    id
  }
}

fragment helpersCheckIsMainTopicContent on Content {
  __isContent: __typename
  topics {
    entityId
    id
  }
}

fragment helpersCheckIsPlusArticle on Content {
  __isContent: __typename
  ... on Article {
    paywallTypes {
      entityUuid
      id
    }
  }
}

fragment helpersCheckIsPlusPage on Page {
  urlAlias
}

fragment helpersCheckIsPostMagazineArticle on Article {
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersCheckIsPostiesArticle on Article {
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersCheckIsPostiesPage on Page {
  urlAlias
}

fragment helpersCheckIsStyleArticle on Content {
  __isContent: __typename
  sections {
    value {
      entityId
      id
    }
  }
}

fragment helpersGetArticleTypeArticle on Content {
  __isContent: __typename
  ... on Article {
    types {
      value {
        entityId
        id
      }
    }
  }
}

fragment helpersMassageToNewsletterItemNewsletter on Newsletter {
  entityId
  name
  alternativeName
  description {
    text
  }
  summary {
    text
  }
  homepageDescription {
    text
  }
}

fragment helpersSanitizeArticleTypeEntityIdsArticle on Article {
  types {
    value {
      entityId
      id
    }
  }
}

fragment helpersSanitizeAuthorTypesArticle on Article {
  authors {
    types
    id
  }
}

fragment helpersSanitizedAuthorEntityIdsArticle on Article {
  authors {
    entityId
    id
  }
}

fragment helpersSectionContent on Section {
  fullSectionPath {
    entityId
    id
  }
}

fragment helpersStyleSectionContent on Section {
  fullSectionPath {
    entityId
    id
  }
}

fragment helpersUseContentSponsorContent on Content {
  __isContent: __typename
  topics {
    entityId
    sponsor {
      ...sponsorTagSponsor
      name
      type
      id
    }
    id
  }
  ... on Article {
    sponsorType
  }
  ...helpersCheckIsMainTopicContent
}

fragment hooksArticleDateUtilsContent on Content {
  __isContent: __typename
  createdDate
  publishedDate
  updatedDate
}

fragment hooksArticleSeoArticle on Article {
  ...helpersCheckIsPostiesArticle
  ...helpersCheckIsPostMagazineArticle
  ...helpersCheckIsStyleArticle
  ...hooksContentHeadlineTagContent
  ...helpersCheckIsAmpEnabledArticle
  entityId
  headline
  socialHeadline
  types {
    value {
      entityId
      id
    }
  }
  authors {
    entityId
    id
  }
  images {
    generic_og: style(filter: {style: "og_image_scmp_generic"}) {
      url
    }
    styles(filter: {styles: ["og_image_posties_article", "og_postmag", "og_image_style", "og_image_scmp_analysis", "og_image_scmp_explainer", "og_image_scmp_editorial", "og_image_scmp_fact_check", "og_image_scmp_debate", "og_image_scmp_live", "og_image_scmp_obituary", "og_image_scmp_opinion", "og_image_scmp_review", "og_image_scmp_series", "og_image_scmp_generic"]}) {
      url
      style
    }
    type
  }
  urlAlias
}

fragment hooksContentHeadlineTagContent on Content {
  __isContent: __typename
  __typename
  ... on Article {
    types {
      value {
        name
        entityId
        description {
          text
        }
        id
      }
    }
    ...helpersCheckIsStyleArticle
  }
  flag
  sections {
    value {
      name
      id
    }
  }
  ...hooksContentHelperContent
}

fragment hooksContentHelperContent on Content {
  __isContent: __typename
  ...helpersSanitizeArticleTypeEntityIdsArticle
  ...helpersSanitizeAuthorTypesArticle
  ...helpersSanitizedAuthorEntityIdsArticle
  flag
}

fragment hooksPaywallPromiseContent on Content {
  __isContent: __typename
  entityId
  ...helpersCheckIsPostiesArticle
}

fragment hooksTrackPageViewArticle on Article {
  entityId
  publishedDate
  headline
  sections {
    value {
      name
      id
    }
  }
  urlAlias
  authors {
    name
    id
  }
  entityUuid
}

fragment imageContent on Content {
  __isContent: __typename
  headline
  ...checkersCheckContentContainsStarlingImageContent
}

fragment inlineWidgetContent on Content {
  __isContent: __typename
  ...contentNewsletterWidgetContent
}

fragment mainImagePrintArticleArticle on Article {
  images {
    title
    url
    isSlideshow
    size_652x446: style(filter: {style: "652x446"}) {
      url
    }
  }
}

fragment photoGalleryDialogContent on Content {
  __isContent: __typename
  __typename
  ...contentShareWidgetContent
}

fragment photoGalleryWidgetContent on Content {
  __isContent: __typename
  ...photoGalleryDialogContent
}

fragment scmpYoutubeContent on Content {
  __isContent: __typename
  entityId
  urlAlias
  publishedDate
}

fragment sponsorTagSponsor on Sponsor {
  name
  type
  images {
    url
  }
}


sections

types

disableOffPlatformContent

sponsorType

published

headline

socialHeadline

authors

images

publishedDate

updatedDate

summary

subHeadline

keywords

topics

readingTime

authorLocations

entityUuid

Li Tao

Tracy Qu

When Huawei Technologies’ latest flagship smartphone was unveiled in September at an event in Munich without details of its release, that situation all but confirmed how the world’s largest telecommunications equipment maker was struggling under a US trade ban.
Sale of the Mate 30 smartphone series in Europe, Huawei’s biggest market outside China, was delayed because the handsets have no access to Google apps and services after the Trump administration added the Shenzhen-based company to a trade blacklist in May. The Mate 30, sans Google apps, was finally released in limited quantities in Germany on December 12.
The immediate consequences of the US government’s campaign against Huawei, which is part of a broader trade and tech dispute between Washington and Beijing, have been well publicised. These include: a disruption in the global technology supply chain, a mad rush by major Chinese hi-tech companies to stockpile components, increased speculation about delays in 5G mobile network development worldwide and the Chinese government’s increased focus on spurring local development of core technologies.
The major unintended consequence, however, of the US action against China’s biggest technology company is that the world could be barrelling closer to a geographic split in hi-tech development and innovation, according to Paul Haswell, a partner who advises technology companies at international law firm Pinsent Masons. He said: “It’s like we’re heading back to the 80s, when North America supported a mobile communications system different from Europe’s, and Japan also ran its own wireless system.”


“The tech industry has been a major factor in expanding globalisation over the past decade, as innovation yielded global standards – such as those for the internet and advanced mobile networks – that have been widely adopted,” Haswell said. “My concern is that as US and Chinese tech development diverges, then so could trust in each country’s tech companies and innovations. That would be bad news for consumers around the world.”
Since US-China trade tensions started more than a year ago, the Trump administration has doubled down on its agenda by declaring war against Chinese technology firms in the name of US national security. US actions against Huawei, which is accused by Washington of being a conduit for espionage, have escalated since then.
Weeks before the recent announcement of an interim trade deal between Washington and Beijing, US Federal Communications Commission (FCC) chairman Ajit Pai reiterated the Trump administration’s concerns about China’s dominance in 5G technology development, as he warned of a “dangerous” US-China internet split.
Pai said “the end result [of China’s technological advances] is essentially to create two different internets”, with a version built by the Chinese government being heavily censored. “That will be something that’s unfortunate for consumers and something that’s potentially dangerous in the long run,” he said. “We don’t want the internet to be Balkanised.”
In October, US Vice-President Mike Pence accused China of using its power in “more proactive and coercive ways to interfere in the domestic policies and politics of the United States” at a speech made to US think tank the Hudson Institute.

 
China, in response, called US accusation of interference in its elections “extremely ridiculous”. Foreign Ministry spokeswoman Hua Chunying accused Pence of making “unfounded accusations”, which was “harming China’s interest and the China-US relationship”.
Shenzhen-based Huawei, meanwhile, has defied early predictions that it would stumble under the US trade ban.
The privately-held company has not only recalibrated its operations under the stringent conditions of the US government’s Entity List, but has continued to push a global agenda for 5G – the next-generation mobile technology that will help power advances such as the industrial internet, autonomous driving and smart cities.
In November, the Trump administration said it has begun issuing licences for some American companies to supply goods to Huawei. It was not immediately clear which products had been approved for sale, but the move granted much-needed clarity to US hi-tech suppliers that last year made billions of dollars in sales to Huawei.
“On November 20, the US Department of Commerce granted Microsoft’s request for a licence to export mass-market software to Huawei,” a Microsoft spokeswoman said in an email.
Google, Qualcomm and Taiwanese electronics contract manufacturer Foxconn Technology Group, formally known as Hon Hai Precision Industry, did not immediately respond to emailed inquiries.
Huawei bought about US$70 billion worth of software, hardware and related services from various hi-tech suppliers last year, including US$11 billion from major US firms. Huawei declined to comment.

 
Still, the tech war between the US and China is expected to intensify and result in the splintering of global tech supply chains.
“There is an obvious de-Americanising trend for China’s OEMs (original equipment manufacturers) because of the technology competition, which I don’t think will be a short-term thing even with the interim US-China trade agreement,” said Zhang Jun, a senior research analyst at Rosenblatt Securities.
“In the next two to three years, there will be a set of supply chains completely without US products. I don’t think building a domestic supply chain will work, so Chinese OEMs will still rely on supply chains with products from other countries [outside the US].”
Washington has already initiated a programme that would divide global tech supply chains. A new government agency, called the US International Development Finance Corp, plans to tap some of its US$60 billion budget to help developing countries and businesses purchase telecoms equipment from other companies. That followed US efforts to convince more countries not to buy telecoms network gear from Chinese suppliers, led by Huawei and ZTE Corp.

 
“The foundations of globalism have already been shaken by the [US-China] trade war and infighting between different trade blocs,” said Anshel Sag, a technology industry analyst with Moor Insights & Strategy.
American companies affected by the US Entity List have had a tough time to refine their strategy, and the uncertainty has ultimately forced them to be more conservative in their approach to Huawei and China as a whole, according to Sag.
While Google apps, for example, are not an issue in China’s restricted internet market, these are of critical importance to Huawei’s overseas smartphone business. Huawei introduced its own operating system, Harmony, in August, but the company said it had no plans to install that software on its smartphones yet because Android remains its top choice and it wants to protect the current app ecosystem.
Amid the current divisive climate in its industry, Huawei has turned to the courts to seek redress. The company recently filed a lawsuit in the US Court of Appeals for the Fifth Circuit to challenge the FCC’s November 22 ruling that bans carriers in rural America from tapping the government-backed Universal Service Fund to buy the Chinese firm’s network equipment. Huawei said the FCC’s order is unlawful because it labelled the company as a national security threat, which goes against required due process protections.

 
“The future direction of the global telecommunications industry could be adversely affected by the restrictions that effectively ban Huawei’s participation in some markets,” said Mark Gregory, an associate professor in the School of Engineering at RMIT University in Melbourne, Australia.
Echoing the view of Pinsent Masons’ Haswell, Gregory said: “A consequence of the failure to permit Huawei to fully participate in telecommunications markets could be a return to the time when different regions of the world utilised different telecommunications standards, and the equipment and systems being deployed in the areas where Huawei’s participation is restricted could have reduced features and capabilities.”
Gregory suggested that such an outcome could be corrected by implementing “a security assurance capability for all vendor equipment and systems”.
Efforts by Washington to restrict Chinese access to American technology and block Chinese companies like Huawei from selling network equipment to the US and other countries have reinforced fears of 5G fragmentation, as more countries roll out their next-generation mobile networks.
“There is always the possibility of fragmentation in the 5G standard, especially since Huawei has the lion’s share of 5G patents and has contributed so much to the [universal] standard,” said Kevin Curran, a professor of cybersecurity at Ulster University in Northern Ireland. He indicated that speculation on that happening only fosters “uncertainty and that is never good for consumers in the long run”.

For more insights into China tech, sign up for our tech newsletters, subscribe to our award-winning Inside China Tech podcast, and download the comprehensive 2019 China Internet Report. Also roam China Tech City, an award-winning interactive digital map at our sister site Abacus.



The unintended consequence of US campaign against Huawei could be a global split in technology standards

An attendee wears a badge strip with the logo of Huawei Technologies at the World 5G Exhibition in Beijing on November 22. Photo: Reuters

Huawei Technologies, the world’s largest telecommunications equipment supplier, has so far defied early predictions that it would stumble after the company was added to the US trade blacklist. Photo: AP

Tech

Big Tech

Business

China Business


The world could be set for a return to the 1980s when various regions used different telecommunications standards



The world could be barrelling closer to a geographic split in hi-tech development and innovation, despite the recent interim trade agreement between the US and China.
