IP Library Granted Patent US 12,425,488
Granted Patent B2
US 12,425,488 · App. 18/552,636 · Granted Sep 23, 2025

Method of operating a telecommunications network

Inventors: Simon Beddus (London, GB); Claudia Cristina (London, GB); Fadi El-Moussa (London, GB)
Assignee: BRITISH TELECOMMUNICATIONS public limited company
H04L67/564H04L67/60
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,425,488
App. No.
18/552,636
Granted
Sep 23, 2025
Kind
B2
Abstract

Method of Operating a Telecommunications Network A computer-implemented method ( 200 ) of operating a telecommunications network ( 100 ), the telecommunications network comprising a client device ( 110 ) and a server ( 140 ), wherein the server and the client device are connected via an access point ( 120 ), the method comprising the steps of: receiving a service request from the client device, said service request requesting a service from the server ( 310 ); identifying client device characteristic information associated with the client device ( 340 ); identifying service requirement information associated with the requested service ( 330 ); comparing the identified client device characteristic information with the identified service requirement information so as to determine if the client device information complies with the service requirement information ( 350 ); and in response to said comparison: permitting the server to provide the requested service in accordance with the service request if the client device information complies with the service requirement information ( 370 ); and preventing the server from providing the requested service in accordance with the service request if the client device information does not comply with the service requirement information ( 380 ).

Claims (43)

1. A computer-implemented method of operating a telecommunications network, the telecommunications network comprising a client device, a server, and an edge device connecting the client device to the server, the method being performed by the edge device and comprising:

intercepting a service request from the client device en route to the server, said service request requesting a service from the server;

identifying client device characteristic information associated with the client device;

identifying service requirement information associated with the requested service;

comparing the identified client device characteristic information with the identified service requirement information so as to determine if the client device characteristic information complies with the service requirement information; and

in response to determining that the client device information:

complies with the service requirement information:

permitting the server to provide the requested service in accordance with the service request; and

does not comply with the service requirement information:

preventing the server from providing the requested service in accordance with the service request; and

in response to the preventing:

identifying a characteristic of the client device characteristic information that is non-compliant with the service requirement information;

identifying a reconfiguration for modifying a network connection between the client device and the server to render the characteristic compliant with the requirement information, wherein the reconfiguration comprises re-routing, to a new network path between the client device and the server, communications associated with the client device; and

implementing the identified reconfiguration.

2. A method according to claim 1 , wherein the client device characteristic information comprises pre-defined information provided by the client device.

3. A method according to claim 2 , wherein the pre-defined information is contained in a Manufacturer Usage Description file.

4. A method according to claim 1 , wherein identifying the client device characteristic information further comprises:

monitoring network communications with the client device;

compiling a behaviour profile for the client device in dependence on said network communications, wherein the client device characteristic information comprises the behaviour profile.

5. A method according to claim 1 , wherein the client device characteristic information comprises a classification of the type of client device.

6. A method according to claim 1 , wherein the client device characteristic information comprises a classification of the type of data generated by the client device.

7. A method according to claim 1 , wherein the client device characteristic information comprises network connection characteristics of the client device.

8. A method according to claim 1 , wherein the service requirement information is a rule requiring specific client device characteristic information of the client device.

9. A method according to claim 1 , wherein the reconfiguration comprises implementing a security policy.

10. A method according to claim 1 , wherein the reconfiguration comprises modifying the client device.

11. A non-transitory computer-readable carrier medium comprising a computer program, which, when the computer program is executed by a computer, causes the computer to perform steps of claim 1 .

12. A telecommunications network for a client device, the telecommunications network comprising:

a server, to which the client device is connected via an access point;

a receiver configured to receive a service request from the client device, said service request requesting a service from the server;

a processor configured to:

identify client device characteristic information associated with the client device;

identify service requirement information associated with the requested service;

compare the identified client device characteristic information with the identified service requirement information so as to determine if the client device characteristic information complies with the service requirement information; and

in response to a determination that the client device information:

complies with the service requirement information:

permit the server from providing the requested service in accordance with the service request; and

does not comply with the service requirement information:

prevent the server from providing the requested service in accordance with the service request;

in response to the preventing:

identify a characteristic of the client device characteristic information that is non-compliant with the service requirement information;

identify a reconfiguration for modifying a network connection between the client device and the server to render the characteristic compliant with the requirement information, wherein the reconfiguration comprises re-routing, to a new network path between the client device and the server, communications associated with the client device; and

implement the identified reconfiguration.

13. The telecommunications network according to claim 12 , wherein a modification of the network connection comprises changing a routing policy for the network communications associated with the client device, including routing to a firewall.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 17, 2023
From: BEDDUS, SIMON; CRISTINA, CLAUDIA; EL-MOUSSA, FADI
To: BRITISH TELECOMMUNICATIONS PUBLIC LIMITED COMPANY
Reel/Frame 065595/0958 →
Priority Claims (1)
GB 2104476 · Mar 30, 2021 · national
Continuity (1)
Related Publication 20240171654A1 · May 23, 2024
References Cited (33)
US 10581690B2 · Salgueiro et al. · 2020 [cited by applicant]
US 10601664B2 · Kumar et al. · 2020 [cited by applicant]
US 20100325215A1 · De et al. · 2010 [cited by applicant]
US 20130007129A1 · German et al. · 2013 [cited by applicant]
US 20150188949A1 · Mahaffey et al. · 2015 [cited by applicant]
US 20160373344A1 · Wohlert · 2016 [cited by applicant]
US 20170126692A1 · Stuntebeck · 2017 [cited by examiner]
US 20170366646A1 · Bradley · 2017 [cited by examiner]
US 20190253319A1 · Kampanakis et al. · 2019 [cited by applicant]
US 20190260751A1 · Kale et al. · 2019 [cited by applicant]
US 20190311134A1 · Mahaffey et al. · 2019 [cited by applicant]
US 20190319953A1 · Lear et al. · 2019 [cited by applicant]
US 20200136991A1 · Salgueiro et al. · 2020 [cited by applicant]
US 20200137119A1 · Jin et al. · 2020 [cited by applicant]
US 20200242222A1 · Machani et al. · 2020 [cited by applicant]
US 20210367839A1 · Vanderveen · 2021 [cited by examiner]
EP 0915594A2 · 1999 [cited by applicant]
EP 3313118A1 · 2018 [cited by applicant]
GB 2506309A · 2014 [cited by applicant]
GB 2544049A · 2017 [cited by applicant]
WO 2020118377A1 · 2020 [cited by applicant]
What is MUD—Manufacturer Usage Description—Document—Cisco DevNet, https://developer.cisco.com/docs/mud/#!what-is-mud, 2021 Cisco DevNet (2 pages). [cited by applicant]
Combined Search and Examination Report under Sections 17 and 18(3) dated Apr. 13, 2022 issued for Application No. GB2115948.8 (9 pages). [cited by applicant]
Fortinet, Data Sheet FortiNAC 500C, 550C, 600C, 700C, VM, and Licenses, 2019 Fortinet, Inc. (10 pages). [cited by applicant]
Combined Search and Examination Report under Sections 17 and 18(3) dated Nov. 26, 2021 issued for Application No. GB2104476.3 (10 pages). [cited by applicant]
International Search Report and Written Opinion of the ISA dated Feb. 10, 2023, issued for International Application No. PCT/EP2022/078837 (14 pages). [cited by applicant]
International Search Report and Written Opinion of the ISA dated Jun. 17, 2022, issued for International Application No. PCT/EP2022/054362 (15 pages). [cited by applicant]
Ayyoob Hamza et al., “Verifying and Monitoring IoTs Network Behavior using MUD Profiles”, IEEE Transactions on Dependable and Secure Computing, 2020 (17 pages). [cited by applicant]
CISCO, “Visibility and Segmentation: first steps to securing Industrial Networks”, Francesca Martucci—Technical Solutions Architect, CyberSecurity—EMEAR, CISCO Live, Barcelona, Jan. 27-31, 2020 (96 pages). [cited by applicant]
Ayyoob Hamza et al., “Detecting Volumetric Attacks on IoT Devices via SDN-Based Monitoring of MUD Activity”, SOSR '19, Apr. 3-4, 2019, San Jose, CA, USA (13 pages). [cited by applicant]
Markus Miettinen et al., “IOT Sentinel: Automated Device-Type Identification for Security Enforcement in IoT”, arXiv:1611.04880v2 [cs.CR] Dec. 13, 2016 (11 pages). [cited by applicant]
International Preliminary Report on Patentability dated May 16, 2024, issued for International Application No. PCT/EP2022/078837 (9 pages). [cited by applicant]
Communication under Rule 71(3) EPC dated Oct. 11, 2024, issued for European Application No. 22 712 262.9 (7 pages). [cited by applicant]