• Re: Emergy mobile phone alert test. Wyse

    From Dave Holland@21:1/5 to usenet@listmail.good-stuff.co.uk on Mon Apr 24 16:00:31 2023
    Mark Goodge <usenet@listmail.good-stuff.co.uk> wrote:
    [1] This is probably one of the reasons why a lot of people thought it had >been sent early. Because, in reality, there's typically a network delay over

    I think this isn't a plausible explanation. Over several years and
    several (Android) phones, I've found that "set phone time from
    network" results in the phone's clock being within 1 second of NTP
    time.

    I think it's more likely that the test alert was actually started
    slightly early because -- as I understand it -- phones are not
    constantly listening for that sort of broadcast. They check in with
    the network approximately once a minute (in the absence of any other
    activity) and if the "hey, there's an alert" flag appears, only then
    do they listen for the actual alert message. So I guess that by
    starting just before 3pm, the networks hoped to avoid a barrage of
    criticism if the alerts had started firing *after* 3pm. ("Late! Can't
    even broadcast an emergency alert on time!" etc etc)

    Dave

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From pensive hamster@21:1/5 to Jeff Layman on Mon Apr 24 08:28:56 2023
    On Sunday, April 23, 2023 at 10:05:44 PM UTC+1, Jeff Layman wrote:
    On 23/04/2023 19:51, pensive hamster wrote:
    On Sunday, April 23, 2023 at 6:37:48 PM UTC+1, Jeff Layman wrote:

    My phone (Xiaomi Redmi Note 10 - Voda) behaved itself and I had no alert >> as I had switched them off. I see in "Settings" under Emergency Alerts
    there is "Emergency alert history". The entry for that is "No previous
    alerts". What do others see if they have that heading?

    Under "Emergency alert history", my phone (Xiaomi Poco M4 Pro
    - 1p mobile / EE) says "Severe alert 23 Apr 14:59 - This is a test
    of Emergency Alerts ..."

    Did you have alerts switched on? If so, that would explain the difference.

    Well, yes. At least we both now know that it is possible to switch
    the alerts off. At least up to a point. According to the Guardian:

    https://www.theguardian.com/society/2023/apr/23/uk-emergency-alert-test-three-looking-into-why-users-failed-to-get-text

    '... All phones allow users to opt out of the second and third
    highest tier of the alerts, called "extreme" and "severe" alerts,
    but few provide the option to opt out of the highest tier, officially
    called "presidential" but renamed “government” in the UK. The
    test was sent as a "severe" warning.'

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mark Goodge@21:1/5 to Dave Holland on Mon Apr 24 16:47:15 2023
    On 24 Apr 2023 16:00:31 +0100 (BST), Dave Holland <dave@biff.org.uk> wrote:

    Mark Goodge <usenet@listmail.good-stuff.co.uk> wrote:
    [1] This is probably one of the reasons why a lot of people thought it had >>been sent early. Because, in reality, there's typically a network delay over

    I think this isn't a plausible explanation. Over several years and
    several (Android) phones, I've found that "set phone time from
    network" results in the phone's clock being within 1 second of NTP
    time.

    I think it's more likely that the test alert was actually started
    slightly early because -- as I understand it -- phones are not
    constantly listening for that sort of broadcast. They check in with
    the network approximately once a minute (in the absence of any other >activity) and if the "hey, there's an alert" flag appears, only then
    do they listen for the actual alert message. So I guess that by
    starting just before 3pm, the networks hoped to avoid a barrage of
    criticism if the alerts had started firing *after* 3pm. ("Late! Can't
    even broadcast an emergency alert on time!" etc etc)

    The phone doesn't need to "check in" to get this. It doesn't go over the
    normal mobile phone network. It's a *broadcast* transmission, in exactly the same way as any other radio transmission, and, like any other radio transmission, is received entirely passively by any device capable of
    receiving it.

    The fact that the broadcast mechanism uses the same cell towers as the
    mobile phone network, and broadcasts over the same frequencies, and is
    received by phones, is all a bit of a red herring in this context. Cell Broadcast is a different technology to mobile telecommunications.

    Because it is a broadcast, and doesn't require any use of the regular
    two-way communication system, you could probably rig up a standalone
    receiver using a Raspberry Pi or similar.

    Mark

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tikli Chestikov@21:1/5 to Mark Goodge on Mon Apr 24 08:32:48 2023
    On Monday, 24 April 2023 at 12:17:35 UTC+1, Mark Goodge wrote:

    It's purely a broadcast system. That is, one way. The system has no
    knowledge of which devices have received the message, or, indeed, which devices are able to receive it.

    Mark

    I'd be interested to hear your views on what Three are going to do in their "investigation" into why many of their users didn't receive the alert.

    As a former Business Intelligence Analyst, my project scope for this would be along the lines of:

    (a) identify all phones (i.e numbers) connected to a cell at 3.pm
    (b) tie those phones (i.e numbers) to a cell tower
    (c) identify which numbers received the alert
    (b) identify which numbers didn't receive the alert

    From there, it's a data trawl exercise to spot patterns. My O2 account, for example, knows the make and model of my phone despite the fact I've never told O2.

    So that's another avenue; was it only certain models of phone? Only phones connected to a certain cell tower?

    But the upshot is; they know *way* *way* more than you'd believe.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tikli Chestikov@21:1/5 to pensive hamster on Mon Apr 24 09:54:03 2023
    On Monday, 24 April 2023 at 16:29:03 UTC+1, pensive hamster wrote:

    '... All phones allow users to opt out of the second and third
    highest tier of the alerts, called "extreme" and "severe" alerts,
    but few provide the option to opt out of the highest tier, officially
    called "presidential" but renamed “government” in the UK. The
    test was sent as a "severe" warning.'

    Yeah that ties in with my experience; the option was greyed out.

    Should we just proclaim Kim Jong-Un our elected leader now?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jon Ribbens@21:1/5 to Tikli Chestikov on Mon Apr 24 18:39:25 2023
    On 2023-04-24, Tikli Chestikov <tikli.chestikov@gmail.com> wrote:
    On Monday, 24 April 2023 at 12:17:35 UTC+1, Mark Goodge wrote:
    It's purely a broadcast system. That is, one way. The system has no
    knowledge of which devices have received the message, or, indeed, which
    devices are able to receive it.

    I'd be interested to hear your views on what Three are going to do in
    their "investigation" into why many of their users didn't receive the
    alert.

    As a former Business Intelligence Analyst, my project scope for this
    would be along the lines of:

    (a) identify all phones (i.e numbers) connected to a cell at 3.pm
    (b) tie those phones (i.e numbers) to a cell tower
    (c) identify which numbers received the alert
    (b) identify which numbers didn't receive the alert

    From there, it's a data trawl exercise to spot patterns. My O2
    account, for example, knows the make and model of my phone despite the
    fact I've never told O2.

    So that's another avenue; was it only certain models of phone? Only
    phones connected to a certain cell tower?

    But the upshot is; they know *way* *way* more than you'd believe.

    ... either that, or you know *way* *way* less than you believe.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jon Ribbens@21:1/5 to Mark Goodge on Mon Apr 24 18:40:57 2023
    On 2023-04-24, Mark Goodge <usenet@listmail.good-stuff.co.uk> wrote:
    On 24 Apr 2023 16:00:31 +0100 (BST), Dave Holland <dave@biff.org.uk> wrote:
    Mark Goodge <usenet@listmail.good-stuff.co.uk> wrote:
    [1] This is probably one of the reasons why a lot of people thought it had >>>been sent early. Because, in reality, there's typically a network delay over >>
    I think this isn't a plausible explanation. Over several years and
    several (Android) phones, I've found that "set phone time from
    network" results in the phone's clock being within 1 second of NTP
    time.

    I think it's more likely that the test alert was actually started
    slightly early because -- as I understand it -- phones are not
    constantly listening for that sort of broadcast. They check in with
    the network approximately once a minute (in the absence of any other >>activity) and if the "hey, there's an alert" flag appears, only then
    do they listen for the actual alert message. So I guess that by
    starting just before 3pm, the networks hoped to avoid a barrage of >>criticism if the alerts had started firing *after* 3pm. ("Late! Can't
    even broadcast an emergency alert on time!" etc etc)

    The phone doesn't need to "check in" to get this. It doesn't go over the normal mobile phone network. It's a *broadcast* transmission, in exactly the same way as any other radio transmission, and, like any other radio transmission, is received entirely passively by any device capable of receiving it.

    The fact that the broadcast mechanism uses the same cell towers as the
    mobile phone network, and broadcasts over the same frequencies, and is received by phones, is all a bit of a red herring in this context. Cell Broadcast is a different technology to mobile telecommunications.

    Because it is a broadcast, and doesn't require any use of the regular
    two-way communication system, you could probably rig up a standalone
    receiver using a Raspberry Pi or similar.

    I'm having difficulty reconciling your "it's just a radio signal
    unrelated to mobile networks" with "customers of Three didn't receive
    it". If you had rigged up such a Raspberry Pi, how would it have known
    whether to fail to receive the signal or not?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From kat@21:1/5 to Mark Goodge on Mon Apr 24 19:51:19 2023
    On 24/04/2023 12:21, Mark Goodge wrote:
    On 23 Apr 2023 20:37:46 GMT, Roger Hayter <roger@hayter.org> wrote:

    On 23 Apr 2023 at 20:09:37 BST, "Jon Ribbens" <jon+usenet@unequivocal.eu>
    wrote:

    On 2023-04-23, Roger Hayter <roger@hayter.org> wrote:
    Presumably not. But they have the infrastructure to detect the
    presence of a wifi connection with some of their customers' phones,
    and this cannot coexist with an active 4G or 5G connection, so why not >>>> send an alert to those customers over the internet?

    That would be effort. There are mechanisms for broadcasting information
    over the Internet, but as far as I'm aware they have never seen
    widespread adoption.

    We're talking about sending a message over what is effectively a permanently >> open VOIP and SMS link between the mobile phone and the same EE servers that >> carry mobile calls. The Internet is just a transmission medium. The answer may
    well be that mobile phones have a (2-way) voice to IP protocol and an SMS to >> IP protocol but not a IP to Alert one.

    More specifically, the Alert system doesn't go over the Internet[1] and doesn't go over the mobile network. it's just a radio broadcast.

    [1] This is probably one of the reasons why a lot of people thought it had been sent early. Because, in reality, there's typically a network delay over IP, and if your phone is set to take its time from the network, it may actually be a bit slow compared to the correct time. It's like listening to the pips on the radio over FM, DAB and IP. Network delays mean that they won't, actually, be heard simultaneously.

    Mark

    I was looking at a clock, one where the time is radio controlled.
    --
    kat
    >^..^<

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jethro_uk@21:1/5 to Martin Brown on Mon Apr 24 18:56:33 2023
    On Mon, 24 Apr 2023 09:47:23 +0100, Martin Brown wrote:

    Also that the Welsh language version had a daft spelling mistake in and
    that the alert was incomprehensible to those unsighted people who rely
    on a reader app since the siren drowned out the spoken reading voice.

    Whilst this is a good illustration of the need to *test* the system, I
    struggle to believe such learnings have not been experienced - and
    addressed - in places that have been doing this for years.

    Which reinforces my observation that "Not invented here" is much more
    powerful a driver in tech than "Let's get this right".

    There must be some explanation for all the local authorities that seem to
    be incapable of configuring tried and tested systems in preference to
    spending eye watering sums on their own bespoke systems. That either
    never work, or when they do aren't worth it (looks at Birmingham City
    Councils car crash efforts).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Tikli Chestikov on Mon Apr 24 18:50:59 2023
    Tikli Chestikov wrote:

    hould we just proclaim Kim Jong-Un our elected leader now?

    I take it your sekrit fuck-buddy/drug-dealer phone didn't go off at 7am
    then?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Owen Rees@21:1/5 to Mark Goodge on Mon Apr 24 19:09:34 2023
    Mark Goodge <usenet@listmail.good-stuff.co.uk> wrote:
    On 23 Apr 2023 20:37:46 GMT, Roger Hayter <roger@hayter.org> wrote:

    On 23 Apr 2023 at 20:09:37 BST, "Jon Ribbens" <jon+usenet@unequivocal.eu>
    wrote:

    On 2023-04-23, Roger Hayter <roger@hayter.org> wrote:
    Presumably not. But they have the infrastructure to detect the
    presence of a wifi connection with some of their customers' phones,
    and this cannot coexist with an active 4G or 5G connection, so why not >>>> send an alert to those customers over the internet?

    That would be effort. There are mechanisms for broadcasting information
    over the Internet, but as far as I'm aware they have never seen
    widespread adoption.

    We're talking about sending a message over what is effectively a permanently >> open VOIP and SMS link between the mobile phone and the same EE servers that >> carry mobile calls. The Internet is just a transmission medium. The answer may
    well be that mobile phones have a (2-way) voice to IP protocol and an SMS to >> IP protocol but not a IP to Alert one.

    More specifically, the Alert system doesn't go over the Internet[1] and doesn't go over the mobile network. it's just a radio broadcast.

    [1] This is probably one of the reasons why a lot of people thought it had been sent early. Because, in reality, there's typically a network delay over IP, and if your phone is set to take its time from the network, it may actually be a bit slow compared to the correct time. It's like listening to the pips on the radio over FM, DAB and IP. Network delays mean that they won't, actually, be heard simultaneously.

    Mark


    If your phone gets the time via NTP then it should be compensating for
    network latency. According to my time app that shows the offsets from
    various NTP servers, my iPhone internal clock is currently off by +0.003 seconds.

    I think it is much more likely that the alert was sent early in some cases.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Jon Ribbens on Mon Apr 24 20:16:04 2023
    On 24/04/2023 19:40, Jon Ribbens wrote:
    On 2023-04-24, Mark Goodge <usenet@listmail.good-stuff.co.uk> wrote:
    On 24 Apr 2023 16:00:31 +0100 (BST), Dave Holland <dave@biff.org.uk> wrote:

    I think it's more likely that the test alert was actually started
    slightly early because -- as I understand it -- phones are not
    constantly listening for that sort of broadcast. They check in with
    the network approximately once a minute (in the absence of any other
    activity) and if the "hey, there's an alert" flag appears, only then
    do they listen for the actual alert message. So I guess that by
    starting just before 3pm, the networks hoped to avoid a barrage of
    criticism if the alerts had started firing *after* 3pm. ("Late! Can't
    even broadcast an emergency alert on time!" etc etc)

    They touch base with the network I think every few minutes so that a
    broadcast which lasts at least ten minutes ought to hit every phone
    apart from the ones which are out of signal range.

    The phone doesn't need to "check in" to get this. It doesn't go over the
    normal mobile phone network. It's a *broadcast* transmission, in exactly the >> same way as any other radio transmission, and, like any other radio
    transmission, is received entirely passively by any device capable of
    receiving it.

    I think it probably does need to be registered with the base station and
    when it pings the base station gets the pending broadcast message thrown
    at it. Broadcast in this context being equivalent to sending an SMS to
    every possible number. The masts know which numbers they have so send it
    on. I don't see how Three could cock it up so comprehensively otherwise.

    The fact that the broadcast mechanism uses the same cell towers as the
    mobile phone network, and broadcasts over the same frequencies, and is
    received by phones, is all a bit of a red herring in this context. Cell
    Broadcast is a different technology to mobile telecommunications.

    It is also broadcast in a way that mobile phones can decode it.

    Because it is a broadcast, and doesn't require any use of the regular
    two-way communication system, you could probably rig up a standalone
    receiver using a Raspberry Pi or similar.

    No reply or ack is expected but the transmission protocol must be
    similar to what is used for SMS messages or it wouldn't get there.
    I didn't think to run an SDR scanner on the appropriate band :(

    I'm having difficulty reconciling your "it's just a radio signal
    unrelated to mobile networks" with "customers of Three didn't receive
    it". If you had rigged up such a Raspberry Pi, how would it have known whether to fail to receive the signal or not?

    It could be just be a radio signal but I reckon it is more like a
    message sent to the filename equivalent of *.* in phone number terms.

    IOW every device connected to a network base station should get a copy
    of the message (quite how this is done is presently unclear).

    I'm guessing that it uses some unreasonable txt number like 0000 000000
    and a magic key that the towers will accept as genuine emergency access
    as an alias for sending a msg out that every mobile phone will accept.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mark Goodge@21:1/5 to All on Mon Apr 24 20:58:01 2023
    On Mon, 24 Apr 2023 20:16:04 +0100, Martin Brown <'''newspam'''@nonad.co.uk> wrote:

    On 24/04/2023 19:40, Jon Ribbens wrote:
    On 2023-04-24, Mark Goodge <usenet@listmail.good-stuff.co.uk> wrote:
    On 24 Apr 2023 16:00:31 +0100 (BST), Dave Holland <dave@biff.org.uk> wrote:

    I think it's more likely that the test alert was actually started
    slightly early because -- as I understand it -- phones are not
    constantly listening for that sort of broadcast. They check in with
    the network approximately once a minute (in the absence of any other
    activity) and if the "hey, there's an alert" flag appears, only then
    do they listen for the actual alert message. So I guess that by
    starting just before 3pm, the networks hoped to avoid a barrage of
    criticism if the alerts had started firing *after* 3pm. ("Late! Can't
    even broadcast an emergency alert on time!" etc etc)

    They touch base with the network I think every few minutes so that a >broadcast which lasts at least ten minutes ought to hit every phone
    apart from the ones which are out of signal range.

    The phone doesn't need to "check in" to get this. It doesn't go over the >>> normal mobile phone network. It's a *broadcast* transmission, in exactly the
    same way as any other radio transmission, and, like any other radio
    transmission, is received entirely passively by any device capable of
    receiving it.

    I think it probably does need to be registered with the base station and
    when it pings the base station gets the pending broadcast message thrown
    at it.

    No, it doesn't. The message is *broadcast* to *all* listening devices.
    Whether any device receives it is entirely up to the device.

    https://en.wikipedia.org/wiki/Cell_Broadcast

    Broadcast in this context being equivalent to sending an SMS to
    every possible number.

    No, it's not. That is precisely the point. Sending an SMS to every possible number would have huge capacity issues.

    The masts know which numbers they have so send it
    on. I don't see how Three could cock it up so comprehensively otherwise.

    Three just didn't transmit it. At least, not from all their cell
    transmitters.

    https://en.wikipedia.org/wiki/Cell_Broadcast

    I'm having difficulty reconciling your "it's just a radio signal
    unrelated to mobile networks" with "customers of Three didn't receive
    it". If you had rigged up such a Raspberry Pi, how would it have known
    whether to fail to receive the signal or not?

    It could be just be a radio signal but I reckon it is more like a
    message sent to the filename equivalent of *.* in phone number terms.

    No, it isn't.

    https://en.wikipedia.org/wiki/Cell_Broadcast

    Mark

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mark Goodge@21:1/5 to tikli.chestikov@gmail.com on Mon Apr 24 21:00:33 2023
    On Mon, 24 Apr 2023 08:32:48 -0700 (PDT), Tikli Chestikov <tikli.chestikov@gmail.com> wrote:


    As a former Business Intelligence Analyst, my project scope for this would be along the lines of:

    (a) identify all phones (i.e numbers) connected to a cell at 3.pm

    That's possible.

    (b) tie those phones (i.e numbers) to a cell tower

    That's possible.

    (c) identify which numbers received the alert

    That's not possible with Cell Broadcast.

    (b) identify which numbers didn't receive the alert

    That's not possible with Cell broadcast.

    But the upshot is; they know *way* *way* more than you'd believe.

    No; the upshot is that you know far less than you believe.

    Mark

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to All on Mon Apr 24 22:23:49 2023
    On 24/04/2023 19:56, Jethro_uk wrote:
    On Mon, 24 Apr 2023 09:47:23 +0100, Martin Brown wrote:

    Also that the Welsh language version had a daft spelling mistake in and
    that the alert was incomprehensible to those unsighted people who rely
    on a reader app since the siren drowned out the spoken reading voice.

    Whilst this is a good illustration of the need to *test* the system, I struggle to believe such learnings have not been experienced - and
    addressed - in places that have been doing this for years.

    Which reinforces my observation that "Not invented here" is much more powerful a driver in tech than "Let's get this right".

    There must be some explanation for all the local authorities that seem to
    be incapable of configuring tried and tested systems in preference to spending eye watering sums on their own bespoke systems. That either
    never work, or when they do aren't worth it (looks at Birmingham City Councils car crash efforts).

    Why were they crashing cars together? ISTR they actually used an
    Internet downloaded wrong Birmingham, Alabama image on a brochure once.

    https://www.business-live.co.uk/economic-development/city-council-puts-wrong-birmingham-3956386

    North Yorkshire has amalgamated its district councils into a unitary
    authority in a measure that supposedly saves money but in practice has
    led to such an increase in most of the rural DCs that we have had to be protected from the insane jump in council tax by some ad hoc "discount".

    Only spendthrift Harrogate has seen its council tax go down...

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Norman Wells@21:1/5 to Martin Brown on Mon Apr 24 22:55:28 2023
    On 24/04/2023 22:23, Martin Brown wrote:

    North Yorkshire has amalgamated its district councils into a unitary authority in a measure that supposedly saves money but in practice has
    led to such an increase in most of the rural DCs that we have had to be protected from the insane jump in council tax by some ad hoc "discount".

    Only spendthrift Harrogate has seen its council tax go down...

    You sure you mean 'spendthrift'?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Norman Wells on Tue Apr 25 09:37:03 2023
    On 24/04/2023 22:55, Norman Wells wrote:
    On 24/04/2023 22:23, Martin Brown wrote:

    North Yorkshire has amalgamated its district councils into a unitary
    authority in a measure that supposedly saves money but in practice has
    led to such an increase in most of the rural DCs that we have had to
    be protected from the insane jump in council tax by some ad hoc
    "discount".

    Only spendthrift Harrogate has seen its council tax go down...

    You sure you mean 'spendthrift'?

    Absolutely certain. Their district councils profligate spending is now
    being subsidised by all the other rural district council residents that
    have been amalgamated into the new North Yorkshire Council.

    Council tax bills in the rural districts have gone up by so much that an interim fudge has had to be applied or they were facing a tax strike.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dave Holland@21:1/5 to usenet@listmail.good-stuff.co.uk on Tue Apr 25 10:26:59 2023
    Mark Goodge <usenet@listmail.good-stuff.co.uk> wrote:
    The phone doesn't need to "check in" to get this. It doesn't go over the >normal mobile phone network. It's a *broadcast* transmission, in exactly the >same way as any other radio transmission, and, like any other radio >transmission, is received entirely passively by any device capable of >receiving it.

    Yet the phone is not constantly listening for this type of message --
    in order to save battery life. The phone has to be told that there's a emergency message being broadcast, by the "alert" bit being set in the
    paging message which phones expect to receive regularly (that's what I
    meant by "check in"). Only then will the phone listen for and try to
    receive the emergency message.

    Have a read: https://twitter.com/davwheat_/status/1650149573313085441

    Dave

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jon Ribbens@21:1/5 to Martin Brown on Tue Apr 25 10:10:56 2023
    On 2023-04-25, Martin Brown <'''newspam'''@nonad.co.uk> wrote:
    On 24/04/2023 22:55, Norman Wells wrote:
    On 24/04/2023 22:23, Martin Brown wrote:
    North Yorkshire has amalgamated its district councils into a unitary
    authority in a measure that supposedly saves money but in practice has
    led to such an increase in most of the rural DCs that we have had to
    be protected from the insane jump in council tax by some ad hoc
    "discount".

    Only spendthrift Harrogate has seen its council tax go down...

    You sure you mean 'spendthrift'?

    Absolutely certain. Their district councils profligate spending is now
    being subsidised by all the other rural district council residents that
    have been amalgamated into the new North Yorkshire Council.

    To be fair to Norman, the word "spendthrift" is rather confusing.
    The most common usage of "thrift" these days is to mean someone who
    is careful and frugal with their expenditure, so "spendthrift" sounds
    like someone whose spending is frugal. But it means the opposite,
    perhaps because "thrift" is one of those words that over time has come
    to be its own opposite - it originally meant "thriving, prosperous, well-to-do", i.e. "rich", but later acquired the "frugal" meaning too.
    So "spendthrift" I guess means something like "spending as if one was
    rich" or perhaps "one who (carelessly) spends the fruits of their
    labour".

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Adam Funk@21:1/5 to Mark Goodge on Tue Apr 25 10:24:18 2023
    On 2023-04-23, Mark Goodge wrote:

    On Sat, 22 Apr 2023 16:01:34 +0100, I <usenet@listmail.good-stuff.co.uk> wrote:

    I may, possibly, find out tomorrow. Because tomorrow happens to be St >>George's Day, and the local Scout Association will, therefore, be holding >>its annual St George's Day parade and church service. As a local councillor, >>I have been invited to attend. The church service starts at 2.30pm and will >>last about an hour. So, at 3pm tomorrow, I will be in church.

    I will, of course, turn my phone off, because I don't want to be the one >>that everybody ends up glaring at (and I hope the vicar remembers to tell >>everyone else to turn theirs off as well, otherwise we're definitely going >>to be interrupted by at least one phone, albeit not mine). But I'll turn it >>back on when we're finished. So if the broadcast is still being repeated 30 >>minutes later, I'll get it.

    Well, I didn't get the alert at 3pm, because my phone was in flight mode and therefore had no 4G connectivity at the time. Which is precisely what I expected. However, as I also expected, several other phones did go off, despite the vicar having made a point of reminding people to turn them off.

    As it happened, though, the service was a lot shorter than I'd expected
    (only just over half an hour, rather than an hour), so I re-enabled network services at 3:09pm. And got the alert. But a colleague who was also there didn't re-enable his until a few minutes after me, and didn't get it. So it seems to have been broadcast for about ten minutes.

    There are reports in the media that not everybody got it who was expecting to. In particular, a lot of Three customers didn't get it. And there seem to have been other instances where specific cell towers didn't broadcast it. Some people also report getting multiple messages, which suggests a failure by their device to properly log the broadcast ID. So the system does appear to be not quite as robust as had been hoped, although of course that's precisely why a test was done.

    Interesting report --- thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Vir Campestris@21:1/5 to Martin Brown on Tue Apr 25 16:07:12 2023
    On 23/04/2023 21:03, Martin Brown wrote:

    I can't see a reason why they can't broadcast the same emergency message
    to internet connected mobile phones as they to to mast connected ones -
    apart from having forgotten completely about that functionality.

    They could. But it wouldn't be any use.

    You can send a message to all phones on a mast saying "The high street
    is shut due to a fire".

    Which mast's messages would you like to see on an IP connected 'phone?

    Andy

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Vir Campestris on Tue Apr 25 16:16:45 2023
    Vir Campestris wrote:

    Martin Brown wrote:

    I can't see a reason why they can't broadcast the same emergency
    message to internet connected mobile phones as they to to mast
    connected ones

    They could. But it wouldn't be any use.

    You can send a message to all phones on a mast saying "The high street
    is shut due to a fire".

    Which mast's messages would you like to see on an IP connected 'phone?

    I wouldn't be surprised if phones using VoWiFi kept trying to connect to
    local masts ready for if/when they lose WiFi and have to go back to the
    least bad mobile signal they can see ... so *that* mast.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Vir Campestris on Tue Apr 25 17:11:25 2023
    On 25/04/2023 16:07, Vir Campestris wrote:
    On 23/04/2023 21:03, Martin Brown wrote:

    I can't see a reason why they can't broadcast the same emergency
    message to internet connected mobile phones as they to to mast
    connected ones - apart from having forgotten completely about that
    functionality.

    They could. But it wouldn't be any use.

    You can send a message to all phones on a mast saying "The high street
    is shut due to a fire".

    Which mast's messages would you like to see on an IP connected 'phone?

    An IP connected phone still knows approximately where it is according to
    the node(s) through which it is connected.

    Mine is about 3 miles out in its simplistic approach when GPS is disabled.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roger Hayter@21:1/5 to All on Tue Apr 25 23:31:19 2023
    On 24 Apr 2023 at 19:40:57 BST, "Jon Ribbens" <jon+usenet@unequivocal.eu> wrote:

    On 2023-04-24, Mark Goodge <usenet@listmail.good-stuff.co.uk> wrote:
    On 24 Apr 2023 16:00:31 +0100 (BST), Dave Holland <dave@biff.org.uk> wrote: >>> Mark Goodge <usenet@listmail.good-stuff.co.uk> wrote:
    [1] This is probably one of the reasons why a lot of people thought it had >>>> been sent early. Because, in reality, there's typically a network delay over

    I think this isn't a plausible explanation. Over several years and
    several (Android) phones, I've found that "set phone time from
    network" results in the phone's clock being within 1 second of NTP
    time.

    I think it's more likely that the test alert was actually started
    slightly early because -- as I understand it -- phones are not
    constantly listening for that sort of broadcast. They check in with
    the network approximately once a minute (in the absence of any other
    activity) and if the "hey, there's an alert" flag appears, only then
    do they listen for the actual alert message. So I guess that by
    starting just before 3pm, the networks hoped to avoid a barrage of
    criticism if the alerts had started firing *after* 3pm. ("Late! Can't
    even broadcast an emergency alert on time!" etc etc)

    The phone doesn't need to "check in" to get this. It doesn't go over the
    normal mobile phone network. It's a *broadcast* transmission, in exactly the >> same way as any other radio transmission, and, like any other radio
    transmission, is received entirely passively by any device capable of
    receiving it.

    The fact that the broadcast mechanism uses the same cell towers as the
    mobile phone network, and broadcasts over the same frequencies, and is
    received by phones, is all a bit of a red herring in this context. Cell
    Broadcast is a different technology to mobile telecommunications.

    Because it is a broadcast, and doesn't require any use of the regular
    two-way communication system, you could probably rig up a standalone
    receiver using a Raspberry Pi or similar.

    I'm having difficulty reconciling your "it's just a radio signal
    unrelated to mobile networks" with "customers of Three didn't receive
    it". If you had rigged up such a Raspberry Pi, how would it have known whether to fail to receive the signal or not?

    ITYWF that, apart from the high frequencies involved, and the considerable complexity of the moduation, the receiver will actually have to be tuned to a frequency pre-negotiated with the nearest tower to get a good enough signal to decode. And, as you say, will have to check that it is a message from its chosen network, and negotiate encryption keys. So the theory that a phone could receive such a broadcast without first registeering with a cell tower is not very convincing. Maybe it could be done without encryption, but that would probably make authentication more rather then less difficult. And we don't really want anyone with appropriate equipment to be able to spoof alerts.

    --
    Roger Hayter

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roger Hayter@21:1/5 to usenet@listmail.good-stuff.co.uk on Tue Apr 25 23:46:30 2023
    On 24 Apr 2023 at 12:17:27 BST, "Mark Goodge" <usenet@listmail.good-stuff.co.uk> wrote:

    On 23 Apr 2023 17:23:25 GMT, Roger Hayter <roger@hayter.org> wrote:

    On 23 Apr 2023 at 17:47:55 BST, "JNugent" <jenningsandco@mail.com> wrote:

    Te impression given up until now is that it is sent out over the mobile
    phone transmitter network(s).

    Presumably not. But they have the infrastructure to detect the presence of a >> wifi connection with some of their customers' phones, and this cannot coexist
    with an active 4G or 5G connection, so why not send an alert to those
    customers over the internet?

    It's purely a broadcast system. That is, one way. The system has no
    knowledge of which devices have received the message, or, indeed, which devices are able to receive it.

    It's no different to the fact that a radio or TV transmitter has no way of knowing which devices have received the signal. All that a transmitter does is transmit.

    What's confusing a lot of people about the emergency alerts is that,
    because, in this case, the transmitters are the same physical devices (the cell towers) that their phones communicate with in the normal way, they are assuming that it's part of the phone/data communication system that their [hones are a part of. But it isn't. It's just a broadcast system that
    happens to use the physical infrastructure of the mobile phone netwoork as the transmitter, sending a broadcast that more recent phone OSes are capable of receiving. In every other respect, though, it's just the same as any
    other radio broadcast.

    Mark

    A phone won't hear it unless it is from a cell transmitter on their own
    network that they have already checked in with.
    --
    Roger Hayter

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roger Hayter@21:1/5 to All on Tue Apr 25 23:51:27 2023
    On 24 Apr 2023 at 19:39:25 BST, "Jon Ribbens" <jon+usenet@unequivocal.eu> wrote:

    On 2023-04-24, Tikli Chestikov <tikli.chestikov@gmail.com> wrote:
    On Monday, 24 April 2023 at 12:17:35 UTC+1, Mark Goodge wrote:
    It's purely a broadcast system. That is, one way. The system has no
    knowledge of which devices have received the message, or, indeed, which
    devices are able to receive it.

    I'd be interested to hear your views on what Three are going to do in
    their "investigation" into why many of their users didn't receive the
    alert.

    As a former Business Intelligence Analyst, my project scope for this
    would be along the lines of:

    (a) identify all phones (i.e numbers) connected to a cell at 3.pm
    (b) tie those phones (i.e numbers) to a cell tower
    (c) identify which numbers received the alert
    (b) identify which numbers didn't receive the alert

    From there, it's a data trawl exercise to spot patterns. My O2
    account, for example, knows the make and model of my phone despite the
    fact I've never told O2.

    So that's another avenue; was it only certain models of phone? Only
    phones connected to a certain cell tower?

    But the upshot is; they know *way* *way* more than you'd believe.

    ... either that, or you know *way* *way* less than you believe.

    They know which phones were connected to which of their base stations at the time of the alert (with some uncertainty related to phones leaving or joining that exact minute or 10 minutes, whichever). They could sample them, perhaps
    by SMS, to estimate the success rate from each tower. It would probably be
    GDPR compliant if they made it clear reply was voluntary. By definition, they are their own customers.


    --
    Roger Hayter

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roger Hayter@21:1/5 to usenet@listmail.good-stuff.co.uk on Tue Apr 25 23:53:37 2023
    On 24 Apr 2023 at 21:00:33 BST, "Mark Goodge" <usenet@listmail.good-stuff.co.uk> wrote:

    On Mon, 24 Apr 2023 08:32:48 -0700 (PDT), Tikli Chestikov <tikli.chestikov@gmail.com> wrote:


    As a former Business Intelligence Analyst, my project scope for this would be
    along the lines of:

    (a) identify all phones (i.e numbers) connected to a cell at 3.pm

    That's possible.

    (b) tie those phones (i.e numbers) to a cell tower

    That's possible.

    (c) identify which numbers received the alert

    That's not possible with Cell Broadcast.

    They could ask a representative sample. Perhaps offer a pound off their next payment in return for a volunary reply.


    (b) identify which numbers didn't receive the alert

    That's not possible with Cell broadcast.

    But the upshot is; they know *way* *way* more than you'd believe.

    No; the upshot is that you know far less than you believe.

    Same thing as an exit poll, really.



    Mark


    --
    Roger Hayter

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roger Hayter@21:1/5 to usenet@listmail.good-stuff.co.uk on Tue Apr 25 23:58:10 2023
    On 24 Apr 2023 at 12:36:33 BST, "Mark Goodge" <usenet@listmail.good-stuff.co.uk> wrote:

    On Sun, 23 Apr 2023 15:47:13 -0000 (UTC), Jon Ribbens <jon+usenet@unequivocal.eu> wrote:

    On 2023-04-23, Martin Brown <'''newspam'''@nonad.co.uk> wrote:
    On 23/04/2023 15:06, JNugent wrote:
    Anti-climax.

    Out of curiousity which carrier and at what exact time?
    Mine on EE was about 35s early!

    That is pretty sloppy for a warning supposed to go out at 15:00:00!

    Indeed, it being 30 seconds or so early is pretty inexcusable.
    And I certainly wasn't expecting to get it twice! (Possibly this
    is because my phone has dual SIM, but it's still surprising.)

    Are you sure it's not the time on your phone which is 30 seconds slow? Bearing in mind that if your phone is syncing the time over the network, the it will be affected by network delays. The only reliable way to get an accurate timestamp on your phone is to use a non-IP means of getting it,
    such as calling the speaking clock.

    Not so. There is at least one IP protocol for getting accurate time by measuring propagation delay and this is quite adequate for human perception purposes, within tens of milliseconds or better.




    I have a clock in my kitchen that gets its time via the radio signal from
    the NPL (a so-called "atomic clock"). It is, consistently, ahead of the
    times displayed on everybody's phones. And the phones themselves aren't 100% identical to each other, or, indeed to other IP devices. My phone is 2 seconds ahead of my desktop Windows PC, and my iPad is about a second behind the PC.

    Mark


    --
    Roger Hayter

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Roger Hayter on Wed Apr 26 09:39:08 2023
    On 26/04/2023 00:31, Roger Hayter wrote:
    On 24 Apr 2023 at 19:40:57 BST, "Jon Ribbens" <jon+usenet@unequivocal.eu> wrote:

    On 2023-04-24, Mark Goodge <usenet@listmail.good-stuff.co.uk> wrote:
    On 24 Apr 2023 16:00:31 +0100 (BST), Dave Holland <dave@biff.org.uk> wrote: >>>> Mark Goodge <usenet@listmail.good-stuff.co.uk> wrote:

    The fact that the broadcast mechanism uses the same cell towers as the
    mobile phone network, and broadcasts over the same frequencies, and is
    received by phones, is all a bit of a red herring in this context. Cell
    Broadcast is a different technology to mobile telecommunications.

    Because it is a broadcast, and doesn't require any use of the regular
    two-way communication system, you could probably rig up a standalone
    receiver using a Raspberry Pi or similar.

    I'm having difficulty reconciling your "it's just a radio signal
    unrelated to mobile networks" with "customers of Three didn't receive
    it". If you had rigged up such a Raspberry Pi, how would it have known
    whether to fail to receive the signal or not?

    ITYWF that, apart from the high frequencies involved, and the considerable complexity of the moduation, the receiver will actually have to be tuned to a frequency pre-negotiated with the nearest tower to get a good enough signal to
    decode. And, as you say, will have to check that it is a message from its

    I doubt it. The way spread spectrum works the whole channel may contain relevant data. The phone must listen at some level (receivers are
    relatively low power - although SDRs are more thirsty).

    I recall in the old days of CRT computer monitors you could tell when
    you were about to get a call because the screen would distort in the
    corner nearest to the phone as it began to transmit (and before it had
    actually started to ring out).

    chosen network, and negotiate encryption keys. So the theory that a phone could receive such a broadcast without first registeering with a cell tower is
    not very convincing. Maybe it could be done without encryption, but that would
    probably make authentication more rather then less difficult. And we don't really want anyone with appropriate equipment to be able to spoof alerts.

    It is spread spectrum so any SDR could in principle decode the message
    if it knew the message key. The puzzle here is that it only works for 4G
    and 5G phones - although that may well be a CBA to do it factor.

    I somehow doubt that each phone gets its own personalised message from
    the mast and that is *not* what the standard says.

    See this Wiki entry that Mark kindly provided or the 3GPP standard if
    you are a glutton for punishment:

    https://en.wikipedia.org/wiki/Cell_Broadcast

    It doesn't explain how such a message is authenticated before broadcast
    but I presume that they have made that stage secure.

    The crucial point it that it is a one to many broadcast with no
    verification of reception that can be repeated again and again for a predetermined period of time up to about half an hour. The message has identical ID tags so that it should only be displayed once.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roger Hayter@21:1/5 to than the routine ident it normally on Wed Apr 26 09:42:09 2023
    On 26 Apr 2023 at 09:39:08 BST, "Martin Brown" <'''newspam'''@nonad.co.uk> wrote:

    On 26/04/2023 00:31, Roger Hayter wrote:
    On 24 Apr 2023 at 19:40:57 BST, "Jon Ribbens" <jon+usenet@unequivocal.eu>
    wrote:

    On 2023-04-24, Mark Goodge <usenet@listmail.good-stuff.co.uk> wrote:
    On 24 Apr 2023 16:00:31 +0100 (BST), Dave Holland <dave@biff.org.uk> wrote:
    Mark Goodge <usenet@listmail.good-stuff.co.uk> wrote:

    The fact that the broadcast mechanism uses the same cell towers as the >>>> mobile phone network, and broadcasts over the same frequencies, and is >>>> received by phones, is all a bit of a red herring in this context. Cell >>>> Broadcast is a different technology to mobile telecommunications.

    Because it is a broadcast, and doesn't require any use of the regular
    two-way communication system, you could probably rig up a standalone
    receiver using a Raspberry Pi or similar.

    I'm having difficulty reconciling your "it's just a radio signal
    unrelated to mobile networks" with "customers of Three didn't receive
    it". If you had rigged up such a Raspberry Pi, how would it have known
    whether to fail to receive the signal or not?

    ITYWF that, apart from the high frequencies involved, and the considerable >> complexity of the moduation, the receiver will actually have to be tuned to a
    frequency pre-negotiated with the nearest tower to get a good enough signal to
    decode. And, as you say, will have to check that it is a message from its

    I doubt it. The way spread spectrum works the whole channel may contain relevant data. The phone must listen at some level (receivers are
    relatively low power - although SDRs are more thirsty).

    I suppose it is possible that the alert is at the nework identification stage before the phone has signed up, and is sent as clear text, so all the phone
    has to do is identify the sending network and see that it is an alert rather than the routine ident it normally replies to.




    I recall in the old days of CRT computer monitors you could tell when
    you were about to get a call because the screen would distort in the
    corner nearest to the phone as it began to transmit (and before it had actually started to ring out).

    chosen network, and negotiate encryption keys. So the theory that a phone >> could receive such a broadcast without first registeering with a cell tower is
    not very convincing. Maybe it could be done without encryption, but that would
    probably make authentication more rather then less difficult. And we don't >> really want anyone with appropriate equipment to be able to spoof alerts.

    It is spread spectrum so any SDR could in principle decode the message
    if it knew the message key. The puzzle here is that it only works for 4G
    and 5G phones - although that may well be a CBA to do it factor.

    I somehow doubt that each phone gets its own personalised message from
    the mast and that is *not* what the standard says.

    You're probably right and if you know the code for, say, EE you can read the alert that EE sent in plain text.

    See this Wiki entry that Mark kindly provided or the 3GPP standard if
    you are a glutton for punishment:

    https://en.wikipedia.org/wiki/Cell_Broadcast

    It doesn't explain how such a message is authenticated before broadcast
    but I presume that they have made that stage secure.

    It seems only to deal with how the alert gets from an alert initiator to a "cell broadcasting centre (CBC)" and it does not make it clear, at least to
    me, whether the CBC is one per network or a joint enterprise. It says nothing about how the alert gets from the base station to the phone, and nothing technical about how it gets from the CBC to each base station.



    The crucial point it that it is a one to many broadcast with no
    verification of reception that can be repeated again and again for a predetermined period of time up to about half an hour. The message has identical ID tags so that it should only be displayed once.

    I agree it is broadcast and not sent to each phone, but I am still not sure that a phone which hasn't signed on to the base station will be able to
    resolve it. Maybe so. I don't know what the normal base station broadcasts advertising its presence look like.

    --
    Roger Hayter

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Martin Brown on Wed Apr 26 09:41:21 2023
    Martin Brown wrote:

    It is spread spectrum so any SDR could in principle decode the message
    if it knew the message key. The puzzle here is that it only works for 4G
    and 5G phones - although that may well be a CBA to do it factor.

    certainly similar alert systems have been implemented elsewhere over
    older mobile networks, but it seems to be a choice here not to bother
    with GPRS/3G etc, probably sensible as they'll be on the way out soon.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Andy Burns on Wed Apr 26 13:27:11 2023
    On 26/04/2023 09:41, Andy Burns wrote:
    Martin Brown wrote:

    It is spread spectrum so any SDR could in principle decode the message
    if it knew the message key. The puzzle here is that it only works for
    4G and 5G phones - although that may well be a CBA to do it factor.

    certainly similar alert systems have been implemented elsewhere over
    older mobile networks, but it seems to be a choice here not to bother
    with GPRS/3G etc, probably sensible as they'll be on the way out soon.

    A lot of rural areas (subject to flooding) are still only 3G or 2.5G.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Roger Hayter on Wed Apr 26 13:33:05 2023
    On 26/04/2023 10:42, Roger Hayter wrote:

    resolve it. Maybe so. I don't know what the normal base station broadcasts advertising its presence look like.

    I don't know either and in fact having lived in a not spot I am more
    inclined to think that each mobile pings the base stations rather than
    the other way round to make its connection. The one with the best signal routing the call.

    That would be more consistent with the battery graph I see as a function
    of signal strength. The weaker the incoming signal the steeper the
    discharge curve and it is steepest of all when completely out of range
    of any base station. When ET calls home at maximum transmit power again
    and again until the battery runs out unless you enable airplane mode...


    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tikli Chestikov@21:1/5 to Andy Burns on Wed Apr 26 08:40:56 2023
    On Monday, 24 April 2023 at 19:58:50 UTC+1, Andy Burns wrote:

    I take it your sekrit fuck-buddy/drug-dealer phone didn't go off at 7am
    then?

    Erm, quite an interesting choice of vocabulary there but, no, it did not.

    What I was more amused by was the report here

    https://www.bbc.co.uk/news/uk-politics-65391455

    So we've gone from "there's no way we can trace who has received the alert, it'll just be any phone connected to a mast" to "we know that 7% of compatible devices didn't receive the alert".

    How do they know that much?

    A bit like how we went from "three weeks to flatten the curve" to "show us your papers" in the space of about six months.

    The UK Government really is *so* transparent.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jon Ribbens@21:1/5 to Roger Hayter on Wed Apr 26 16:03:12 2023
    On 2023-04-25, Roger Hayter <roger@hayter.org> wrote:
    On 24 Apr 2023 at 19:39:25 BST, "Jon Ribbens" <jon+usenet@unequivocal.eu> wrote:

    On 2023-04-24, Tikli Chestikov <tikli.chestikov@gmail.com> wrote:
    On Monday, 24 April 2023 at 12:17:35 UTC+1, Mark Goodge wrote:
    It's purely a broadcast system. That is, one way. The system has no
    knowledge of which devices have received the message, or, indeed, which >>>> devices are able to receive it.

    I'd be interested to hear your views on what Three are going to do in
    their "investigation" into why many of their users didn't receive the
    alert.

    As a former Business Intelligence Analyst, my project scope for this
    would be along the lines of:

    (a) identify all phones (i.e numbers) connected to a cell at 3.pm
    (b) tie those phones (i.e numbers) to a cell tower
    (c) identify which numbers received the alert
    (b) identify which numbers didn't receive the alert

    From there, it's a data trawl exercise to spot patterns. My O2
    account, for example, knows the make and model of my phone despite the
    fact I've never told O2.

    So that's another avenue; was it only certain models of phone? Only
    phones connected to a certain cell tower?

    But the upshot is; they know *way* *way* more than you'd believe.

    ... either that, or you know *way* *way* less than you believe.

    They know which phones were connected to which of their base stations
    at the time of the alert (with some uncertainty related to phones
    leaving or joining that exact minute or 10 minutes, whichever). They
    could sample them, perhaps by SMS, to estimate the success rate from
    each tower. It would probably be GDPR compliant if they made it clear
    reply was voluntary. By definition, they are their own customers.

    Voluntary you say? I don't think Kim Jong Un would approve of that.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jeff Layman@21:1/5 to Tikli Chestikov on Wed Apr 26 17:17:32 2023
    On 26/04/2023 16:40, Tikli Chestikov wrote:
    On Monday, 24 April 2023 at 19:58:50 UTC+1, Andy Burns wrote:

    I take it your sekrit fuck-buddy/drug-dealer phone didn't go off at 7am
    then?

    Erm, quite an interesting choice of vocabulary there but, no, it did not.

    What I was more amused by was the report here

    https://www.bbc.co.uk/news/uk-politics-65391455

    So we've gone from "there's no way we can trace who has received the alert, it'll just be any phone connected to a mast" to "we know that 7% of compatible devices didn't receive the alert".

    "Sunday's emergency alert did not reach an estimated 7% of compatible
    devices in the UK, the government has said.
    ...
    The 7% of devices that did not receive the alert includes those which
    were turned off or on aeroplane mode, and where the user had opted out
    of emergency alerts."

    How do they know that much?

    Unfortunately they don't say /how/ they estimated there were 7% of
    devices which weren't reached. Nor do they say how they know that this
    included phones turned off, in aeroplane mode, or emergency alerts were
    turned off. There is nothing in Dowden's statement at <https://questions-statements.parliament.uk/written-statements/detail/2023-04-25/hcws740>
    (which was linked to in the BBC article).

    Basically the same information appeared on the ITV webpage at <https://www.itv.com/news/2023-04-25/government-website-error-causes-uk-emergency-alert-confusion>,
    so /someone/ in the government must have told them.

    A bit like how we went from "three weeks to flatten the curve" to "show us your papers" in the space of about six months.

    The UK Government really is *so* transparent.

    --

    Jeff

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Jeff Layman on Wed Apr 26 20:24:02 2023
    On 26/04/2023 17:17, Jeff Layman wrote:
    On 26/04/2023 16:40, Tikli Chestikov wrote:
    On Monday, 24 April 2023 at 19:58:50 UTC+1, Andy Burns wrote:

    I take it your sekrit fuck-buddy/drug-dealer phone didn't go off
    at 7am then?

    Erm, quite an interesting choice of vocabulary there but, no, it
    did not.

    What I was more amused by was the report here

    https://www.bbc.co.uk/news/uk-politics-65391455

    So we've gone from "there's no way we can trace who has received
    the alert, it'll just be any phone connected to a mast" to "we know
    that 7% of compatible devices didn't receive the alert".

    "Sunday's emergency alert did not reach an estimated 7% of compatible
    devices in the UK, the government has said. ... The 7% of devices
    that did not receive the alert includes those which were turned off
    or on aeroplane mode, and where the user had opted out of emergency
    alerts."

    How do they know that much?

    Think of a number and divide by Three?

    Unfortunately they don't say /how/ they estimated there were 7% of
    devices which weren't reached. Nor do they say how they know that
    this included phones turned off, in aeroplane mode, or emergency
    alerts were turned off. There is nothing in Dowden's statement at <https://questions-statements.parliament.uk/written-statements/detail/2023-04-25/hcws740>
    (which was linked to in the BBC article).

    Basically the same information appeared on the ITV webpage at <https://www.itv.com/news/2023-04-25/government-website-error-causes-uk-emergency-alert-confusion>,
    so /someone/ in the government must have told them.

    Straw polls on some tech forums put it as high as 40% with a compatible
    phone that didn't get the message and I heard a figure of 20% fail rate
    quoted much earlier on (for any reason) which with Three having a major
    fail might be about right. Coincidentally (or perhaps not) 7% did say
    they had such alerts disabled. eg.

    https://www.ispreview.co.uk/index.php/2023/04/three-uk-coughs-to-problems-with-emergency-alert-test.html

    There is bound to be some sampling bias since people who didn't get it
    and think they should have are more likely to complain and post...

    You can view the straw poll at ISPreview by clicking on it.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jeff Layman@21:1/5 to Martin Brown on Thu Apr 27 09:31:07 2023
    On 26/04/2023 20:24, Martin Brown wrote:
    On 26/04/2023 17:17, Jeff Layman wrote:
    On 26/04/2023 16:40, Tikli Chestikov wrote:
    On Monday, 24 April 2023 at 19:58:50 UTC+1, Andy Burns wrote:

    I take it your sekrit fuck-buddy/drug-dealer phone didn't go off
    at 7am then?

    Erm, quite an interesting choice of vocabulary there but, no, it
    did not.

    What I was more amused by was the report here

    https://www.bbc.co.uk/news/uk-politics-65391455

    So we've gone from "there's no way we can trace who has received
    the alert, it'll just be any phone connected to a mast" to "we know
    that 7% of compatible devices didn't receive the alert".

    "Sunday's emergency alert did not reach an estimated 7% of compatible
    devices in the UK, the government has said. ... The 7% of devices
    that did not receive the alert includes those which were turned off
    or on aeroplane mode, and where the user had opted out of emergency
    alerts."

    How do they know that much?

    Think of a number and divide by Three?

    Unfortunately they don't say /how/ they estimated there were 7% of
    devices which weren't reached. Nor do they say how they know that
    this included phones turned off, in aeroplane mode, or emergency
    alerts were turned off. There is nothing in Dowden's statement at
    <https://questions-statements.parliament.uk/written-statements/detail/2023-04-25/hcws740>
    (which was linked to in the BBC article).

    Basically the same information appeared on the ITV webpage at
    <https://www.itv.com/news/2023-04-25/government-website-error-causes-uk-emergency-alert-confusion>,
    so /someone/ in the government must have told them.

    Straw polls on some tech forums put it as high as 40% with a compatible
    phone that didn't get the message and I heard a figure of 20% fail rate quoted much earlier on (for any reason) which with Three having a major
    fail might be about right. Coincidentally (or perhaps not) 7% did say
    they had such alerts disabled. eg.

    https://www.ispreview.co.uk/index.php/2023/04/three-uk-coughs-to-problems-with-emergency-alert-test.html

    There is bound to be some sampling bias since people who didn't get it
    and think they should have are more likely to complain and post...

    You can view the straw poll at ISPreview by clicking on it.

    Interesting. I'd searched for "7%" and "alert" and found nothing other
    than the BBC and ITV news pages which mentioned it. Even on that
    ISPreview page, search the text for "7%" and it doesn't find it - at
    least, not until the straw poll results are revealed!

    Do you think that page is the source of the 7% quoted in the news articles??

    --

    Jeff

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jon Ribbens@21:1/5 to Jeff Layman on Thu Apr 27 13:04:22 2023
    On 2023-04-27, Jeff Layman <Jeff@invalid.invalid> wrote:
    On 26/04/2023 20:24, Martin Brown wrote:
    On 26/04/2023 17:17, Jeff Layman wrote:
    On 26/04/2023 16:40, Tikli Chestikov wrote:
    What I was more amused by was the report here

    https://www.bbc.co.uk/news/uk-politics-65391455

    So we've gone from "there's no way we can trace who has received
    the alert, it'll just be any phone connected to a mast" to "we know
    that 7% of compatible devices didn't receive the alert".

    "Sunday's emergency alert did not reach an estimated 7% of compatible
    devices in the UK, the government has said. ... The 7% of devices
    that did not receive the alert includes those which were turned off
    or on aeroplane mode, and where the user had opted out of emergency
    alerts."

    How do they know that much?

    Think of a number and divide by Three?

    Unfortunately they don't say /how/ they estimated there were 7% of
    devices which weren't reached. Nor do they say how they know that
    this included phones turned off, in aeroplane mode, or emergency
    alerts were turned off. There is nothing in Dowden's statement at
    <https://questions-statements.parliament.uk/written-statements/detail/2023-04-25/hcws740>
    (which was linked to in the BBC article).

    Basically the same information appeared on the ITV webpage at
    <https://www.itv.com/news/2023-04-25/government-website-error-causes-uk-emergency-alert-confusion>,
    so /someone/ in the government must have told them.

    Straw polls on some tech forums put it as high as 40% with a compatible
    phone that didn't get the message and I heard a figure of 20% fail rate
    quoted much earlier on (for any reason) which with Three having a major
    fail might be about right. Coincidentally (or perhaps not) 7% did say
    they had such alerts disabled. eg.

    https://www.ispreview.co.uk/index.php/2023/04/three-uk-coughs-to-problems-with-emergency-alert-test.html

    There is bound to be some sampling bias since people who didn't get it
    and think they should have are more likely to complain and post...

    You can view the straw poll at ISPreview by clicking on it.

    Interesting. I'd searched for "7%" and "alert" and found nothing other
    than the BBC and ITV news pages which mentioned it. Even on that
    ISPreview page, search the text for "7%" and it doesn't find it - at
    least, not until the straw poll results are revealed!

    Do you think that page is the source of the 7% quoted in the news
    articles??

    The government will obviously have arranged for a survey to be carried
    out promptly after the test was transmitted. That survey will be the
    source of the figure presumably.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Jeff Layman on Thu Apr 27 19:19:18 2023
    On 27/04/2023 09:31, Jeff Layman wrote:

    Do you think that page is the source of the 7% quoted in the news
    articles??

    Only with my most cynical hat on...

    Of my capable phones two out of three failed to get the message but that
    could be because Three have the least bad signal here. An O2 not spot.

    One didn't have a SIM in at the time to see if an emergency message
    would get through to a phone that was connected to a network but on an "emergency calls only" basis. The answer seems to be no, but with a
    connected iPhone X failing to see it on Three it is hard to be sure.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roland Perry@21:1/5 to All on Fri Apr 28 07:53:29 2023
    In message <kar72mFdsrU1@mid.individual.net>, at 23:46:30 on Tue, 25 Apr
    2023, Roger Hayter <roger@hayter.org> remarked:

    A phone won't hear it unless it is from a cell transmitter on their own >network that they have already checked in with.

    And additionally, only if it's a 4/5G connection. The phone will only *translate* the alert into human-recognisable form if there's suitable
    firmware installed - and the phone settings haven't (where available)
    turned that off.

    My own theory about the "3" issue is still that despite having a 4G
    phone many people end up being connected on 3G.
    --
    Roland Perry

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roland Perry@21:1/5 to All on Fri Apr 28 07:44:46 2023
    In message <u28u3f$ub5m$1@dont-email.me>, at 17:11:25 on Tue, 25 Apr
    2023, Martin Brown <'''newspam'''@nonad.co.uk> remarked:
    On 25/04/2023 16:07, Vir Campestris wrote:
    On 23/04/2023 21:03, Martin Brown wrote:

    I can't see a reason why they can't broadcast the same emergency
    message to internet connected mobile phones as they to to mast
    connected ones - apart from having forgotten completely about that >>>functionality.

    They could. But it wouldn't be any use.
    You can send a message to all phones on a mast saying "The high
    street is shut due to a fire".

    Which mast's messages would you like to see on an IP connected
    'phone?

    An IP connected phone still knows approximately where it is according
    to the node(s) through which it is connected.

    Geolocation services are available which can make a guess at where
    someone is (on whatever flavour of IP-connected device) based on a whole
    bundle of things they've observed in the past.

    It's an app on the phone, not the phone itself, which can ask for that
    estimate of location.

    Mine is about 3 miles out in its simplistic approach when GPS is disabled.

    That sounds more like cell-site based [coarse] location, but you
    specified (only) IP-connected.
    --
    Roland Perry

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roland Perry@21:1/5 to All on Fri Apr 28 07:54:40 2023
    In message <djpc4i144u8r0jg9uac3cnk73t5sopeqld@4ax.com>, at 12:24:49 on
    Mon, 24 Apr 2023, Mark Goodge <usenet@listmail.good-stuff.co.uk>
    remarked:
    On Sun, 23 Apr 2023 19:39:52 +0100, SH <i.love@spam.com> wrote:

    and what about Dual SIM phones? I have such a beast and I have a EE sim
    and a 3 SIM and I got one alert message..... I don;t know which network
    it came over.

    A lot of Three customers report not getting it at all, so it's possible that >the one you got was the one which arrived via EE. But it's also possible
    that the software on your phone correctly recognises duplicate messages from >mutiple sources, and hence only displays it once. From social media
    anecdata, it appears that some people with dual-sim phones got it twice,
    once for each sim, but others only got it once. So I don't think there's any >consistency there.

    Many dual-SIM phones only do 2G on the second SIM, so there's no
    possibility of an alert being delivered through it.
    --
    Roland Perry

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roland Perry@21:1/5 to All on Fri Apr 28 08:01:54 2023
    In message <u2biqs$1erpd$1@dont-email.me>, at 17:17:32 on Wed, 26 Apr
    2023, Jeff Layman <Jeff@invalid.invalid> remarked:

    What I was more amused by was the report here
    https://www.bbc.co.uk/news/uk-politics-65391455

    So we've gone from "there's no way we can trace who has received the >>alert, it'll just be any phone connected to a mast" to "we know that
    7% of compatible devices didn't receive the alert".

    "Sunday's emergency alert did not reach an estimated 7% of compatible
    devices in the UK, the government has said.

    At least they said "compatible", which is very much at the heart of the analysis, with the information in the public consciousness about what it
    is which makes a phone compatible, so shrouded in the fog of war.

    ...
    The 7% of devices that did not receive the alert includes those which
    were turned off or on aeroplane mode, and where the user had opted out
    of emergency alerts."

    And those which were in a 4G not-spot at the time.

    How do they know that much?

    Unfortunately they don't say /how/ they estimated there were 7% of
    devices which weren't reached.

    I would imagine they had a panel of users (there have been several
    earlier non-public tests using volunteers) who reported their outcomes.

    This is market research 101.

    --
    Roland Perry

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roland Perry@21:1/5 to All on Fri Apr 28 08:09:41 2023
    In message <m0rc4i9m022sraeg8q4qfr298ms1a8vto5@4ax.com>, at 12:51:31 on
    Mon, 24 Apr 2023, Mark Goodge <usenet@listmail.good-stuff.co.uk>
    remarked:
    As far as the time is concerned, bear in mind that your phone will show
    14:59 from 4:59:00 right up to 14:59:59, so if your phone is a few seconds >slow[1] then it will still have been showing 14:59 at the time the alert was >first broadcast.

    Reports of "early" alerts were typically tens of seconds, not tenths of seconds.

    [1] Which it almost certainly is, because the timestamp on your phone is >obtained over the network and is subject to network delays.

    The speed of light is a constant were I live, even it apparently it's
    not in Evesham.
    --
    Roland Perry

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roland Perry@21:1/5 to All on Fri Apr 28 08:15:13 2023
    In message <n0ka4it4tdkljmoqhi0admq8kuurprr8uh@4ax.com>, at 16:36:03 on
    Sun, 23 Apr 2023, Mark Goodge <usenet@listmail.good-stuff.co.uk>
    remarked:
    On Sun, 23 Apr 2023 15:18:46 +0100, Andy Burns <usenet@andyburns.uk> wrote:

    Michael Chare wrote:

    "The alert will disable users’ phones leaving a "welcome message" on
    screen until they acknowledge it by clicking on an “OK”  message.

    I had four phones turned on and waiting ...

    Nexus 1, this is a 3G device, with no SIM (emergency calls only), has no >>mention of emergency alerts in the settings and did not generate an alert.

    Pixel 3, this is a 4G device, with an inactive (plusnet/ee) SIM
    emergency calls only, alerts enabled in settings, but it did not
    generate an alert

    Samsung A21s, this is a 4G device, an active (asda/voda) SIM, alerts >>enabled, I was on a voice call from my landline waiting for the alert,
    the alert popped up on screen, the call was not dropped, there was no >>interruption to the call in progress, the alert does appear in history.

    Pixel 5a, this is a 5G device, with an active (virgin/voda) SIM, alerts >>disabled, it did not generate a alert, it has no alert in its history

    Those four results are precisely what I would have expected.

    What is it about the Pixel 3 which makes you say that? Emergency calls
    only being a 2G thing, perhaps.
    --
    Roland Perry

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roland Perry@21:1/5 to All on Fri Apr 28 08:16:44 2023
    In message <kakt25Foe5U1@mid.individual.net>, at 15:18:46 on Sun, 23 Apr
    2023, Andy Burns <usenet@andyburns.uk> remarked:
    Michael Chare wrote:

    "The alert will disable users’ phones leaving a "welcome message"
    on screen until they acknowledge it by clicking on an “OK”  message.

    I had four phones turned on and waiting ...

    Nexus 1, this is a 3G device, with no SIM (emergency calls only), has
    no mention of emergency alerts in the settings and did not generate an
    alert.

    You need a phone contemporaneously connected to at least 4G to get these alerts.

    Pixel 3, this is a 4G device, with an inactive (plusnet/ee) SIM
    emergency calls only, alerts enabled in settings, but it did not
    generate an alert

    First step in the diagnosis: Was it operating on 4G at the time? Or does
    the lack of SIM mean it doesn't display that.

    Samsung A21s, this is a 4G device, an active (asda/voda) SIM, alerts
    enabled, I was on a voice call from my landline waiting for the alert,
    the alert popped up on screen, the call was not dropped, there was no >interruption to the call in progress, the alert does appear in history.

    Pixel 5a, this is a 5G device, with an active (virgin/voda) SIM, alerts >disabled, it did not generate a alert, it has no alert in its history

    Was it showing up as 4G connected? Although "alerts" [which alerts
    though] disabled might well be a clue. As far as I can tell very few
    phones which allow alerts to be disabled log the fact that there has
    been a "missed alert".
    --
    Roland Perry

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roland Perry@21:1/5 to All on Fri Apr 28 07:56:49 2023
    In message <a56d6566-1f21-4dba-9893-1f5e2476f4bdn@googlegroups.com>, at 08:28:56 on Mon, 24 Apr 2023, pensive hamster
    <pensive_hamster@hotmail.co.uk> remarked:
    On Sunday, April 23, 2023 at 10:05:44 PM UTC+1, Jeff Layman wrote:
    On 23/04/2023 19:51, pensive hamster wrote:
    On Sunday, April 23, 2023 at 6:37:48 PM UTC+1, Jeff Layman wrote:

    My phone (Xiaomi Redmi Note 10 - Voda) behaved itself and I had no alert >> >> as I had switched them off. I see in "Settings" under Emergency Alerts
    there is "Emergency alert history". The entry for that is "No previous
    alerts". What do others see if they have that heading?

    Under "Emergency alert history", my phone (Xiaomi Poco M4 Pro
    - 1p mobile / EE) says "Severe alert 23 Apr 14:59 - This is a test
    of Emergency Alerts ..."

    Did you have alerts switched on? If so, that would explain the difference.

    Well, yes. At least we both now know that it is possible to switch
    the alerts off. At least up to a point. According to the Guardian:

    https://www.theguardian.com/society/2023/apr/23/uk-emergency-alert-test- >three-looking-into-why-users-failed-to-get-text

    '... All phones allow users to opt out of the second and third
    highest tier of the alerts, called "extreme" and "severe" alerts,
    but few provide the option to opt out of the highest tier, officially
    called "presidential" but renamed “government� in the UK. The
    test was sent as a "severe" warning.'

    "All phones" is such a breathtakingly sweeping statement, one should
    really stop reading the remainder of their drivel.
    --
    Roland Perry

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to Roland Perry on Fri Apr 28 09:22:39 2023
    Roland Perry wrote:

    Andy Burns remarked:

    Nexus 1, this is a 3G device, with no SIM (emergency calls only), has
    no mention of emergency alerts in the settings and did not generate an
    alert.

    You need a phone contemporaneously connected to at least 4G to get these alerts.

    Yes it was only on "for fun" while I was digging old phones out of drawers.

    Pixel 3, this is a 4G device, with an inactive (plusnet/ee) SIM
    emergency calls only, alerts enabled in settings, but it did not
    generate an alert

    First step in the diagnosis: Was it operating on 4G at the time? Or does
    the lack of SIM mean it doesn't display that.

    Clearly it's not possible to guarantee how it connects today vs sunday,
    but the same phone with the same SIM in the same location is "reasonably likely" to connect to the network in the same manner.

    The phone has WiFi off, is set to prefer 4G

    A cell-info monitoring app shows it is connected by 3G in emergency
    calls only mode, though it can "see" 2G/3G/4G masts from EE (the parent
    of the MVNO of the inactive SIM)

    Samsung A21s, this is a 4G device, an active (asda/voda) SIM, alerts
    enabled, I was on a voice call from my landline waiting for the alert,
    the alert popped up on screen, the call was not dropped, there was no
    interruption to the call in progress, the alert does appear in history.

    Pixel 5a, this is a 5G device, with an active (virgin/voda) SIM,
    alerts disabled, it did not generate a alert, it has no alert in its
    history

    Was it showing up as 4G connected?

    Yes it always gets 4G here, only ever gets 5G away from here.

    Although "alerts" [which alerts though] disabled might well be a
    clue.
    That was indeed the intent, every alert setting which the phone exposes
    is disabled.

    As far as I can tell very few phones which allow alerts to be
    disabled log the fact that there has been a "missed alert".
    Of the two phones which had no reason to not receive the actual
    broadcast packets, the one which sounded the alert does show it in
    history, the one that is set to ignore alerts, does not show it in history.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Roland Perry on Fri Apr 28 10:36:07 2023
    On 28/04/2023 07:44, Roland Perry wrote:
    In message <u28u3f$ub5m$1@dont-email.me>, at 17:11:25 on Tue, 25 Apr
    2023, Martin Brown <'''newspam'''@nonad.co.uk> remarked:
    On 25/04/2023 16:07, Vir Campestris wrote:
    On 23/04/2023 21:03, Martin Brown wrote:

    I can't see a reason why they can't broadcast the same emergency
    message to internet connected mobile phones as they to to mast
    connected ones - apart from having forgotten completely about that
    functionality.

     They could. But it wouldn't be any use.
     You can send a message to all phones on a mast saying "The high
    street  is shut due to a fire".

     Which mast's messages would you like to see on an IP connected 'phone?

    An IP connected phone still knows approximately where it is according
    to the node(s) through which it is connected.

    Geolocation services are available which can make a guess at where
    someone is (on whatever flavour of IP-connected device) based on a whole bundle of things they've observed in the past.

    It's an app on the phone, not the phone itself, which can ask for that estimate of location.

    Mine is about 3 miles out in its simplistic approach when GPS is
    disabled.

    That sounds more like cell-site based [coarse] location, but you
    specified (only) IP-connected.

    My PC doesn't have any mobile network connectivity. I presume that when
    I allow it to geolocate it tells me where the fibre I'm on goes to.

    I get the same answer on my mobile phone doing Wifi calling (which in
    bad weather is essential since the mobile signal drops below usability).
    I get a slightly different answer if it is on the mobile network.

    Thinking about it - despite the fact that my phone fairly often goes
    direct to answerphone when inside the house for incoming calls I can
    make outgoing calls OK. There seems to be a curious asymmetry.

    NB my phone got the emergency message OK and very early. It was the
    phone on the much stronger Three 4G mobile signal that didn't!

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Roland Perry on Fri Apr 28 09:03:15 2023
    On 28/04/2023 07:53, Roland Perry wrote:
    In message <kar72mFdsrU1@mid.individual.net>, at 23:46:30 on Tue, 25 Apr 2023, Roger Hayter <roger@hayter.org> remarked:

    A phone won't hear it unless it is from a cell transmitter on their own
    network that they have already checked in with.

    And additionally, only if it's a 4/5G connection. The phone will only *translate* the alert into human-recognisable form if there's suitable firmware installed - and the phone settings haven't (where available)
    turned that off.

    My own theory about the "3" issue is still that despite having a 4G
    phone many people end up being connected on 3G.

    My wife's phone was definitely well connected on 4G but showed no sign
    at all of the message. Three royally cocked it up big time - most likely
    a single transmission of the msg. Taking a leaf from 'Allo 'Allo

    Lizen very carefully, I vill zay zis only once.

    Unfortunately by the time most phones had woken up to receive state the
    first block of the message had already passed them by.

    I am more inclined to think that only people on Three 5G got it!
    (or perhaps had an active phone conversation in progress on 4G)

    The government claim of 7% isn't credible based on a straw poll of
    friends and neighbours (admittedly all on the same Three base station).
    I will allow the possibility that they CBA to upgrade the facilities to
    do this on the sparse rural network of base stations.

    However, other reports from friends in Manchester seem to confirm that
    Three was also screwed in some major cities too. eg

    https://www.manchestereveningnews.co.uk/news/greater-manchester-news/confusion-emergency-alert-happens-phones-26762976

    Yet another north south divide perhaps?

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roland Perry@21:1/5 to All on Sat Apr 29 08:28:58 2023
    In message <u2g429$2ctmp$1@dont-email.me>, at 10:36:07 on Fri, 28 Apr
    2023, Martin Brown <'''newspam'''@nonad.co.uk> remarked:
    On 28/04/2023 07:44, Roland Perry wrote:
    In message <u28u3f$ub5m$1@dont-email.me>, at 17:11:25 on Tue, 25 Apr
    2023, Martin Brown <'''newspam'''@nonad.co.uk> remarked:
    On 25/04/2023 16:07, Vir Campestris wrote:
    On 23/04/2023 21:03, Martin Brown wrote:

    I can't see a reason why they can't broadcast the same emergency >>>>>message to internet connected mobile phones as they to to mast >>>>>connected ones - apart from having forgotten completely about that


    They could. But it wouldn't be any use.
    You can send a message to all phones on a mast saying "The high >>>>street is shut due to a fire".

    Which mast's messages would you like to see on an IP connected >>>>'phone?

    An IP connected phone still knows approximately where it is
    according to the node(s) through which it is connected.

    Geolocation services are available which can make a guess at where >>someone is (on whatever flavour of IP-connected device) based on a
    whole bundle of things they've observed in the past.

    It's an app on the phone, not the phone itself, which can ask for
    that estimate of location.

    Mine is about 3 miles out in its simplistic approach when GPS is >>>disabled.

    That sounds more like cell-site based [coarse] location, but you >>specified (only) IP-connected.

    My PC doesn't have any mobile network connectivity. I presume that when
    I allow it to geolocate it tells me where the fibre I'm on goes to.

    The geolocation sevices don't have access to the Openreach customer
    records, not that this would help, because they only know your retail
    ISP's details[1]. The way they gelocate PCs is a bundle of "big data" correlation of the activities you've done from it.

    Using it to plot a Google Maps route is a sure-fire one, but others are
    more subtle. A wifi-connected PC (and I'm in a very small minority who
    uses an Ethernet-connected laptop at home) can potentially leak the
    SSID, and the location providers know where those all are by
    crowdsourcing that data from passing GPS-connected mobile phones (having originally seeded it by their own wardriving).

    NB my phone got the emergency message OK and very early.

    Please quantify "very". A few tens of milliseconds, or tens of seconds?

    It was the phone on the much stronger Three 4G mobile signal that
    didn't!

    Could be the phone just as much as the "Three" 4G.

    [1] The missing ingredient when it comes to presenting results to
    consumers is the degree of uncertainty reported by the location
    services. So it's not unusual for them to tell an App "somewhere
    within 100km of Brick Lane" if that's where a consumer's ISP's data
    centre is reported to be
    --
    Roland Perry

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roland Perry@21:1/5 to All on Sat Apr 29 08:30:15 2023
    In message <u2fuk5$2c6qs$1@dont-email.me>, at 09:03:15 on Fri, 28 Apr
    2023, Martin Brown <'''newspam'''@nonad.co.uk> remarked:

    The government claim of 7% isn't credible based on a straw poll of
    friends and neighbours (admittedly all on the same Three base station).

    I doubt a national market survey can be trumped by your local straw
    poll.
    --
    Roland Perry

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Roland Perry on Sat Apr 29 09:22:36 2023
    On 29/04/2023 08:28, Roland Perry wrote:
    In message <u2g429$2ctmp$1@dont-email.me>, at 10:36:07 on Fri, 28 Apr
    2023, Martin Brown <'''newspam'''@nonad.co.uk> remarked:

    NB my phone got the emergency message OK and very early.

    Please quantify "very". A few tens of milliseconds, or tens of seconds?

    I stated at the outset 35s early - later revised to 37s early after I discovered that the system clock on my phone was actually 2s *fast*
    relative to my synchronised reference atomic clock. I was counting down
    to message transmit at the time. It was early enough to have my wife
    find her own phone put it into camera mode and take a screenshot showing
    14:59 and the msg (I didn't expect to be believed when I claimed this).

    There is no excuse for IP connected or network connected devices to have
    system clocks out by more than a few tens of ms. NTP is pretty good.

    Government later said they authorised transmitting early to "avoid"
    annoying sporting events that started at 3pm exactly. It might have been smarter of them to say it will be at eg. 14:57 BST (or some other daft
    exact time like some of the parcel delivery firms do).

    It was the phone on the much stronger Three 4G mobile signal that didn't!

    Could be the phone just as much as the "Three" 4G.

    Apple iPhone X on iOS 16.4.1 should have been fully capable. And
    obviously it was fully active from the moment the camera was in use.

    So many people on Three near me didn't get it that I strongly suspect
    that Three either didn't transmit it at all or did it just once only and
    the majority of phones didn't come out of torpor fast enough to see it.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From pensive hamster@21:1/5 to Roland Perry on Sat Apr 29 06:21:40 2023
    On Friday, April 28, 2023 at 8:28:32 AM UTC+1, Roland Perry wrote:
    on Mon, 24 Apr 2023, pensive hamster remarked:

    According to the Guardian:

    https://www.theguardian.com/society/2023/apr/23/uk-emergency-alert-test-three-looking-into-why-users-failed-to-get-text

    '... All phones allow users to opt out of the second and third
    highest tier of the alerts, called "extreme" and "severe" alerts,
    but few provide the option to opt out of the highest tier, officially >called "presidential" but renamed "government" in the UK. The
    test was sent as a "severe" warning.'

    "All phones" is such a breathtakingly sweeping statement, one should
    really stop reading the remainder of their drivel.

    Given the context, "All phones" may be shorthand for "all mobile
    devices connected to the UK’s 4G and 5G networks". I don't
    think they meant to include landline phones, for example.

    The Guardian article linked-to above earler stated:

    "... The alarm was scheduled to sound at 3pm on all mobile
    devices connected to the UK’s 4G and 5G networks,

    "... Users whose phones have not received a software update
    in more than two years, and those who were not within reach
    of a 4G or 5G network were not expected to successfully
    receive it."

    Would you consider "All phones" in that sense to be a
    breathtakingly sweeping category?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sam Plusnet@21:1/5 to pensive hamster on Sun Apr 30 19:40:43 2023
    On 29-Apr-23 14:21, pensive hamster wrote:
    On Friday, April 28, 2023 at 8:28:32 AM UTC+1, Roland Perry wrote:
    on Mon, 24 Apr 2023, pensive hamster remarked:

    According to the Guardian:

    https://www.theguardian.com/society/2023/apr/23/uk-emergency-alert-test-three-looking-into-why-users-failed-to-get-text

    '... All phones allow users to opt out of the second and third
    highest tier of the alerts, called "extreme" and "severe" alerts,
    but few provide the option to opt out of the highest tier, officially
    called "presidential" but renamed "government" in the UK. The
    test was sent as a "severe" warning.'

    "All phones" is such a breathtakingly sweeping statement, one should
    really stop reading the remainder of their drivel.

    Given the context, "All phones" may be shorthand for "all mobile
    devices connected to the UK’s 4G and 5G networks". I don't
    think they meant to include landline phones, for example.

    The Guardian article linked-to above earler stated:

    "... The alarm was scheduled to sound at 3pm on all mobile
    devices connected to the UK’s 4G and 5G networks,

    "... Users whose phones have not received a software update
    in more than two years, and those who were not within reach
    of a 4G or 5G network were not expected to successfully
    receive it."

    Would you consider "All phones" in that sense to be a
    breathtakingly sweeping category?

    No.
    The type of phones under discussion was clearly identified in other
    parts of the article.

    Quoting out of context creates the problem.

    --
    Sam Plusnet

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Vir Campestris@21:1/5 to Roger Hayter on Mon May 1 21:38:05 2023
    On 26/04/2023 00:58, Roger Hayter wrote:
    On 24 Apr 2023 at 12:36:33 BST, "Mark Goodge" <usenet@listmail.good-stuff.co.uk> wrote:

    Are you sure it's not the time on your phone which is 30 seconds slow?
    Bearing in mind that if your phone is syncing the time over the network, the >> it will be affected by network delays. The only reliable way to get an
    accurate timestamp on your phone is to use a non-IP means of getting it,
    such as calling the speaking clock.

    Not so. There is at least one IP protocol for getting accurate time by measuring propagation delay and this is quite adequate for human perception purposes, within tens of milliseconds or better.


    The speaking clock will be slow on your mobile phone. Try calling
    another phone in the same room - the delays are quite perceptible.

    OTOH right now my left channel, right channel, and subwoofer are
    synchronised perfectly. And they're running over WiFi...

    Andy

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Vir Campestris on Tue May 2 12:52:04 2023
    On 01/05/2023 21:38, Vir Campestris wrote:
    On 26/04/2023 00:58, Roger Hayter wrote:
    On 24 Apr 2023 at 12:36:33 BST, "Mark Goodge"
    <usenet@listmail.good-stuff.co.uk> wrote:

    Are you sure it's not the time on your phone which is 30 seconds slow?
    Bearing in mind that if your phone is syncing the time over the
    network, the
    it will be affected by network delays. The only reliable way to get an
    accurate timestamp on your phone is to use a non-IP means of getting it, >>> such as calling the speaking clock.

    Not so. There is at least one IP protocol for getting accurate time by
    measuring propagation delay and this is quite adequate for human
    perception
    purposes, within tens of milliseconds or better.

    The speaking clock will be slow on your mobile phone. Try calling
    another phone in the same room - the delays are quite perceptible.

    Indeed but that is a realtime delay. Any systematic routing delay can be
    dealt with by the mast to mobile phone transaction. They use time gating
    of packets to prevent you connecting to masts more than ~35km away.

    I accept that mobile phone network time sync is not as good as I would
    have expected - when checked against a laboratory standard reference
    atomic clock it was 2s fast. Long enough to be very obviously wrong.

    OTOH right now my left channel, right channel, and subwoofer are
    synchronised perfectly. And they're running over WiFi...

    Modern Wifi is actually fast low latency high throughput and the speed
    of light is enormous when compared to the speed of sound or the
    bandwidth needed to carry hifi grade audio.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roland Perry@21:1/5 to All on Wed May 3 06:57:53 2023
    In message <u2ik4d$2sjdb$1@dont-email.me>, at 09:22:36 on Sat, 29 Apr
    2023, Martin Brown <'''newspam'''@nonad.co.uk> remarked:
    On 29/04/2023 08:28, Roland Perry wrote:
    In message <u2g429$2ctmp$1@dont-email.me>, at 10:36:07 on Fri, 28 Apr >>2023, Martin Brown <'''newspam'''@nonad.co.uk> remarked:

    NB my phone got the emergency message OK and very early.

    Please quantify "very". A few tens of milliseconds, or tens of
    seconds?

    I stated at the outset 35s early - later revised to 37s early after I >discovered that the system clock on my phone was actually 2s *fast*
    relative to my synchronised reference atomic clock.

    Jolly good. It must have go snipped en-route.

    I was counting down to message transmit at the time. It was early
    enough to have my wife find her own phone put it into camera mode and
    take a screenshot showing 14:59 and the msg (I didn't expect to be
    believed when I claimed this).

    There is no excuse for IP connected or network connected devices to
    have system clocks out by more than a few tens of ms. NTP is pretty
    good.

    This isn't about what time the infrastructure believes it to be, but how precise a time such as "3pm" in a press release has to be implemented.

    Government later said they authorised transmitting early to "avoid"
    annoying sporting events that started at 3pm exactly. It might have
    been smarter of them to say it will be at eg. 14:57 BST (or some other
    daft exact time like some of the parcel delivery firms do).

    I think "around 3pm" would cover almost all the potential OCD-sufferers' issues.

    It was the phone on the much stronger Three 4G mobile signal that didn't!

    Could be the phone just as much as the "Three" 4G.

    Apple iPhone X on iOS 16.4.1 should have been fully capable.

    Should'a would'a might'a been. What's the date of the latest firmware
    update on *that* handset?

    And obviously it was fully active from the moment the camera was in
    use.

    So many people on Three near me didn't get it that I strongly suspect
    that Three either didn't transmit it at all or did it just once only
    and the majority of phones didn't come out of torpor fast enough to see
    it.

    Or the were connected via 3G at the time.
    --
    Roland Perry

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Roland Perry@21:1/5 to All on Wed May 3 06:59:44 2023
    In message <014d6ebc-8272-46a9-a521-52cbaed0cc57n@googlegroups.com>, at 06:21:40 on Sat, 29 Apr 2023, pensive hamster
    <pensive_hamster@hotmail.co.uk> remarked:
    On Friday, April 28, 2023 at 8:28:32 AM UTC+1, Roland Perry wrote:
    on Mon, 24 Apr 2023, pensive hamster remarked:

    According to the Guardian:

    https://www.theguardian.com/society/2023/apr/23/uk-emergency-alert-test- >three-looking-into-why-users-failed-to-get-text

    '... All phones allow users to opt out of the second and third
    highest tier of the alerts, called "extreme" and "severe" alerts,
    but few provide the option to opt out of the highest tier, officially
    called "presidential" but renamed "government" in the UK. The
    test was sent as a "severe" warning.'

    "All phones" is such a breathtakingly sweeping statement, one should
    really stop reading the remainder of their drivel.

    Given the context, "All phones" may be shorthand for "all mobile
    devices connected to the UK’s 4G and 5G networks". I don't
    think they meant to include landline phones, for example.

    The Guardian article linked-to above earler stated:

    "... The alarm was scheduled to sound at 3pm on all mobile
    devices connected to the UK’s 4G and 5G networks,

    "... Users whose phones have not received a software update
    in more than two years, and those who were not within reach
    of a 4G or 5G network were not expected to successfully
    receive it."

    Would you consider "All phones" in that sense to be a
    breathtakingly sweeping category?

    Yes, when that's the selective quote the newspaper publishes in its
    opening paragraph.
    --
    Roland Perry

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Roland Perry on Wed May 3 09:39:38 2023
    On 03/05/2023 06:57, Roland Perry wrote:
    In message <u2ik4d$2sjdb$1@dont-email.me>, at 09:22:36 on Sat, 29 Apr
    2023, Martin Brown <'''newspam'''@nonad.co.uk> remarked:

    So many people on Three near me didn't get it that I strongly suspect
    that Three either didn't transmit it at all or did it just once only
    and the majority of phones didn't come out of torpor fast enough to
    see it.

    Or the were connected via 3G at the time.
    That's unlikely since both Three and EE have 4G good coverage here from relatively nearby masts. It's unlikely they would be on another mast.
    Vodafone is more remote so hit and miss depending on local topography.
    O2 has no coverage at all here so they obviously didn't get it.

    My wife's wasn't - it was definitely on a 4G connection with acceptable
    but not great signal of 2 bars. It was also powered up active being used
    as a camera to photograph my phone with the message and 14:59 displayed.

    The more friends I talk to about this (mostly geeks with newish high end
    mobile phones) the more I find that they also didn't get anything from
    Three. All other networks seem to have been OK.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From pensive hamster@21:1/5 to Roland Perry on Wed May 3 06:33:15 2023
    On Wednesday, May 3, 2023 at 9:20:40 AM UTC+1, Roland Perry wrote:
    on Sat, 29 Apr 2023, pensive hamster remarked:
    On Friday, April 28, 2023 at 8:28:32 AM UTC+1, Roland Perry wrote: >>on Mon, 24 Apr 2023, pensive hamster remarked:

    According to the Guardian:
    https://www.theguardian.com/society/2023/apr/23/uk-emergency-alert-test- >three-looking-into-why-users-failed-to-get-text

    '... All phones allow users to opt out of the second and third
    highest tier of the alerts, called "extreme" and "severe" alerts,
    but few provide the option to opt out of the highest tier, officially
    called "presidential" but renamed "government" in the UK. The
    test was sent as a "severe" warning.'

    "All phones" is such a breathtakingly sweeping statement, one should
    really stop reading the remainder of their drivel.

    Given the context, "All phones" may be shorthand for "all mobile
    devices connected to the UK's 4G and 5G networks". I don't
    think they meant to include landline phones, for example.

    The Guardian article linked-to above earler stated:

    "... The alarm was scheduled to sound at 3pm on all mobile
    devices connected to the UK's 4G and 5G networks,

    "... Users whose phones have not received a software update
    in more than two years, and those who were not within reach
    of a 4G or 5G network were not expected to successfully
    receive it."

    Would you consider "All phones" in that sense to be a
    breathtakingly sweeping category?

    Yes, when that's the selective quote the newspaper publishes in its
    opening paragraph.

    But the "All phones" bit was in the 7th paragraph.

    The "... The alarm was scheduled to sound at 3pm on all mobile
    devices connected to the UK’s 4G and 5G networks" bit was in
    the 2cd paragraph.

    https://www.theguardian.com/society/2023/apr/23/uk-emergency-alert-test-three-looking-into-why-users-failed-to-get-text

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)