IP Library Granted Patent US 12,432,259
Granted Patent B2
US 12,432,259 · App. 18/034,258 · Granted Sep 30, 2025

Obtaining information pertaining to a network function in lawful interception

Inventors: Domenico Raffaele Cione (Caserta, IT); Elvira Villani (Salerno, IT); Biagio Maione (Naples, IT); Dario De Vito (Mercato San Severino, IT); Daniele Gaito (Naples, IT)
Assignee: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
H04L63/306
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,432,259
App. No.
18/034,258
Granted
Sep 30, 2025
Kind
B2
Abstract

A lawful interception provisioning function, LIPF ( 113 ) and a system information retrieval function, SIRF ( 114 ), communicate with each other via the X1 and X2 protocols. The LIPF ( 113 ) obtains, from the SIRF ( 114 ), information pertaining to a network function, NF( 107 ), which is an instance of a virtual network function, VNF, in a telecommunication 5 network ( 100 ), where said information is unrelated to any LI target and any task associated with a point of interception, POI ( 135 ), in the NF ( 107 ).

Claims (78)

1. A method performed by a computer system in a telecommunication network, the computer system hosting at least a lawful interception provisioning function (LIPF) and a system information retrieval function (SIRF), the method comprising:

obtaining, by the LIPF from the SIRF, information pertaining to a network function (NF) that is an instance of a virtual network function (VNF) in the telecommunication network, wherein the information is unrelated to any lawful interception (LI) target associated with a point of intercept (POI) in the NF, wherein the obtaining information pertaining to a NF comprises:

transmitting, from the LIPF to the SIRF over an X1 interface, a request that comprises a RequestMessageType having a value that indicates a request for information pertaining to a plurality of NF instances;

obtaining, by the SIRF from a NF repository function (NRF) the information pertaining to a plurality of NF instances and comprising an identifier of each NF instance; and

transmitting, from the SIRF to the LIPF over the X1 interface, a response that comprises the information pertaining to a plurality of NF instances.

2. The method of claim 1 , wherein the obtaining information pertaining to a plurality of NF instances comprises obtaining profile information pertaining to each NF instance, and wherein the transmitting comprises transmitting the information pertaining to each NF instance.

3. The method of claim 1 , wherein the obtaining information pertaining to a NF comprises obtaining a subscription to receiving notifications of status changes of at least one NF instance.

4. The method of claim 3 , wherein the obtaining information pertaining to a NF comprises:

transmitting, from the LIPF to the SIRF over the X1 interface, a CreateDestinationRequest message that comprises a DeliveryType having a value that indicates a request for the subscription to receiving notifications of status changes of NF instances,

determining, by the SIRF based at least on the DeliveryType value, that a subscription to receiving notifications of status changes of NF instances is required by the LIPF,

obtaining, by the SIRF from the NRF, the subscription to receiving notifications of status changes of NF instances, and

transmitting, from the SIRF to the LIPF over the X1 interface, a CreateDestinationResponse message comprising a positive acknowledgment of the obtained subscription.

5. The method of claim 4 , comprising:

transmitting, from the LIPF to the SIRF over the X1 interface, a RemoveDestinationRequest message that comprises an identifier of a destination,

determining, by the SIRF, based at least on the identifier of the destination in the RemoveDestinationRequest message that a subscription has been obtained,

transmitting, from the SIRF to the NRF, a request to delete the subscription, and

transmitting, from the SIRF to the LIPF over the X1 interface, a RemoveDestinationResponse message comprising a positive acknowledgment of the terminated subscription.

6. The method of claim 4 , wherein

the CreateDestinationRequest message comprises DestinationDetailsExtensions comprising filtering information that specifies how notifications of status changes of the NF instances are to be selected for transmission to the LIPF, and comprising:

storing, by the SIRF, the filtering information.

7. The method of claim 6 , wherein the filtering information comprises:

an identifier of an NF instance,

NF instance type,

NF instance status change type, and/or

NF instance profile information.

8. The method of claim 3 , wherein the obtaining information pertaining to a NF comprises:

transmitting, from the LIPF to the SIRF over the X1 interface, an ActivateTaskRequest message that comprises a DeliveryType having a value that indicates a request for the subscription to receiving notifications of status changes of NF instances,

determining, by the SIRF based at least on the DeliveryType value, that a subscription to receiving notifications of status changes of NF instances is required by the LIPF,

obtaining, by the SIRF from the NRF, the subscription to receiving notifications of status changes of NF instances, and

transmitting, from the SIRF to the LIPF over the X1 interface, a ActivateTaskResponse message comprising a positive acknowledgment of the obtained subscription.

9. The method of claim 8 , wherein t

he ActivateTaskRequest message comprises TaskDetailsExtensions comprising filtering information that specifies how notifications of status changes of the NF instances are to be selected for transmission to the LIPF, and

the method further comprisesstoring, by the SIRF, the filtering information.

10. The method of claim 8 , comprising:

transmitting, from the LIPF to the SIRF over the X1 interface, a DeactivateTaskRequest message that comprises a task identifier,

determining, by the SIRF, based at least on the task identifier in the DeactivateTaskRequest message that a subscription has been obtained,

transmitting, from the SIRF to the NRF, a request to delete the subscription, and

transmitting, from the SIRF to the LIPF over the X1 interface, a DeactivateTaskResponse message comprising a positive acknowledgment of the terminated subscription.

11. The method of claim 3 , wherein the obtaining information pertaining to a NF comprises:

transmitting, from the LIPF to the SIRF over the X1 interface, a CreateNFSubscriptionRequest message that indicates a request for the subscription to receiving notifications of status changes of NF instances,

determining, by the SIRF based on the CreateNFSubscriptionRequest, that a subscription to receiving notifications of status changes of NF instances is required by the LIPF,

obtaining, by the SIRF from the NRF, the subscription to receiving notifications of status changes of NF instances, and

transmitting, from the SIRF to the LIPF over the X1 interface, a CreateNFSubscriptionResponse message comprising a positive acknowledgment of the received subscription.

12. The method of claim 11 , wherein:

the CreateNFSubscriptionRequest message comprises CreateNFSubscriptionExtensions comprising filtering information that specifies how notifications of status changes of the NF instances are to be selected for transmission to the LIPF, and the method further comprises storing, by the SIRF, the filtering information.

13. The method of claim 11 , comprising:

transmitting, from the LIPF to the SIRF over the X1 interface, a RemoveNFSubscriptionRequest message,

determining, by the SIRF, based on the RemoveNFSubscriptionRequest message that a subscription has been obtained,

transmitting, from the SIRF to the NRF, a request to delete the subscription, and

transmitting, from the SIRF to the LIPF over the X1 interface, a RemoveNFSubscriptionResponse message comprising a positive acknowledgment of the terminated subscription.

14. The method of claim 3 , comprising:

transmitting, from the LIPF to the SIRF over the X1 interface, a RemoveAllDestinationsRequest message, a DeactivateAllTasksRequest message, and/or a RemoveAllNFSubscriptions message;

transmitting, from the SIRF to the NRF, a request to delete all subscriptions to receiving notifications of status changes of NF instances; and

transmitting, from the SIRF to the LIPF over the X1 interface, a message comprising a positive acknowledgment of the terminated subscription.

15. The method of claim 3 , wherein the obtaining information pertaining to a NF comprises receiving at least one notification of a status change of an NF instance.

16. The method of claim 15 , comprising:

receiving, by the SIRF from the NRF, at least one notification of a status change of an NF instance, and

transmitting, from the SIRF to the LIPF over an X2 interface, a protocol data unit (PDU) that specifies the at least one notification of a status change of an NF instance.

17. The method of claim 16 , comprising:

reading, by the SIRF, stored filtering information that specifies how notifications of status changes of the NF instance are to be selected for transmission to the LIPF, wherein

the transmitting of the PDU is performed depending on the filtering information.

18. The method of claim 17 , wherein the filtering information comprises:

an identifier of an NF instance,

NF instance type,

NF instance status change type, and/or

NF instance profile information.

19. The method of claim 16 , wherein the PDU that specifies the at least one notification of a status change of an NF instance comprises:

an X1 identifier, XID, header field set to a value of zero or a valid task identifier,

a payload direction header field set to a value of 5,

a PDU type header field set to a value that is none of the integer values 1 to 4,

a correlation identity header field set to a value of zero,

a payload format header field set to a value that is none of the integer values 0 to 13, and

a payload field comprising at least one message having a Hypertext Transfer Protocol/2, HTTP/2, format.

20. A computer system comprising processing circuitry, comprising at least one processor, and a memory, the memory containing instructions, executable by the processing circuitry, for configuring the computer system to:

obtain, by a lawful interception provisioning function (LIPF) from a system information retrieval function (SIRF) over an X1 interface, information pertaining to a network function (NF) that is an instance of a virtual network function (VNF) in a telecommunication network, where the information is unrelated to any lawful interception (LI) target associated with a point of intercept (POI) in the NF, wherein the obtaining information pertaining to a NF comprises:

transmitting, from the LIPF to the SIRF over the X1 interface, a request that comprises a RequestMessageType having a value that indicates a request for information pertaining to a plurality of NF instances,

obtaining, by the SIRF from the NRF, the information pertaining to a plurality of NF instances and comprising an identifier of each NF instance, and

transmitting, from the SIRF to the LIPF over the X1 interface, a response comprising the information pertaining to a plurality of NF instances.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 24, 2023
From: CIONE, DOMENICO RAFFAELE; VILLANI, ELVIRA; MAIONE, BIAGIO; DE VITO, DARIO; GAITO, DANIELE
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 063755/0522 →
Continuity (1)
Related Publication 20240015187A1 · Jan 11, 2024
References Cited (26)
US 9235856B2 · Parker · 2016 [cited by examiner]
US 9860790B2 · Khan · 2018 [cited by examiner]
US 11722982B2 · Shan · 2023 [cited by examiner]
US 11757650B2 · Sood · 2023 [cited by examiner]
US 11950183B2 · Kedalagudde · 2024 [cited by examiner]
US 11962460B1 · Draznin · 2024 [cited by examiner]
US 20230135699A1 · Liao · 2023 [cited by examiner]
US 20230269591A1 · Vitiello · 2023 [cited by examiner]
WO 2019147435A1 · 2019 [cited by applicant]
WO 2020143917A1 · 2020 [cited by applicant]
International Search Report and Written Opinion issued in International Application No. PCT/SE2020/051046 dated May 26, 2021 (12 pages). [cited by applicant]
International Preliminary Report on Patentability issued in International Application No. PCT/SE2020/051046 dated May 26, 2021 (12 pages). [cited by applicant]
SA3-LI (BT Plc), “Virtualisation Details”, 3GPP SADLI#77e-quater, S3120023, e-Meeting, Jun. 2-3, 2020 (11 pages). [cited by applicant]
SA3-LI (Public Safety Canada), “ADMF descriptive details”, 3GPP SA3LI#76, S3i200035, Sophia Antipolis, France, Jan. 2020 (4 pages). [cited by applicant]
3GPP TS 23.502 V16.3.0 (Dec. 2019), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 16), Dec. 2019 (558 pages). [cited by applicant]
3GPP TS 29.500 V16.2.1 (Jan. 2020), 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of Service Based Architecture; Stage 3 (Release 16), Jan… [cited by applicant]
3GPP TS 23.501 V16.3.0 (Dec. 2019), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16), Dec. 2019 (417 pages). [cited by applicant]
3GPP TS 33.128 V16.1.0 (Dec. 2019), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security; Protocol and procedures for Lawful Interception (LI); Stage 3 (Release 16), De… [cited by applicant]
3GPP TS 33.127 V16.2.0 (Dec. 2019), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security; Lawful Interception (LI) architecture and functions (Release 16), Dec. 2019 (8… [cited by applicant]
3GPP TS 29.510 V16.2.0 (Dec. 2019), 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 16), Dec. 2019 (167 pag… [cited by applicant]
ETSI TS 102 232-1 V3.21.1 (Dec. 2019), Lawful Interception (LI); Handover Interface and Service-Specific Details (SSD) for IP delivery; Part 1: Handover specification for IP delivery, Dec. 2019 (74 pages). [cited by applicant]
ETSI TS 103 120 V1.5.1 (Mar. 2020), Lawful Interception (LI); Interface for warrant information, Mar. 2020 (70 pages). [cited by applicant]
ETSI TS 103 221-2 V1.3.1 (Aug. 2020), Lawful Interception (LI); Internal Network Interfaces; Part 2: X2/X3, Aug. 2020 (29 pages). [cited by applicant]
ETSI TS 103 221-2 V1.2.1 (Dec. 2019), Lawful Interceiption (LI); Internal Network Interfaces; Part 2: X2/X3, Dec. 2019 (28 pages). [cited by applicant]
ETSI TS 103 221-1 V1.7.1 (Aug. 2020), Lawful Interception (LI); Internal Network Interfaces; Part 1: X1, Aug. 2020 (44 pages). [cited by applicant]
ETSI TS 103 221-1 V1.6.1 (Dec. 2019), Lawful Interception (LI); Internal Network Interfaces; Part 1: X1, Dec. 2019 (44 pages). [cited by applicant]