IP Library Granted Patent US 12,192,075
Granted Patent B2
US 12,192,075 · App. 18/368,418 · Granted Jan 7, 2025

Method and device for provisioning bidirectional filter in PFD management procedure

Inventors: Jeonghwa Lee (Suwon-si, KR); Euikyum Moon (Suwon-si, KR)
Assignee: SAMSUNG ELECTRONICS CO., LTD.
H04L43/028H04L43/062H04L67/14
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,192,075
App. No.
18/368,418
Granted
Jan 7, 2025
Kind
B2
Abstract

The present disclosure provides methods and apparatuses for provisioning a bidirectional filter. In some embodiments, a method of a first network entity performing a session management function (SMF) in a communication system includes obtaining a first filter for a first direction and a second filter for a second direction that are associated with an application, identifying whether the first filter is a bidirectional filter based on a result of comparing the first filter and the second filter, identifying whether a second network entity performing a user plane function (UPF) supports a function of obtaining the second filter, based on the first filter being identified as the bidirectional filter, and transmitting, to the second network entity, a first message including the first filter and information indicating that the first filter is the bidirectional filter, based on identifying that the second network entity supports the function of obtaining the second filter.

Claims (72)

1. A method of a first network entity performing a session management function (SMF) in a communication system, comprising:

obtaining a first filter for a first direction and a second filter for a second direction, the first filter and the second filter being associated with an application;

identifying whether the first filter is a bidirectional filter based on a result of comparing the first filter and the second filter;

identifying whether a second network entity performing a user plane function (UPF) supports a function of obtaining the second filter, based on the first filter being identified as the bidirectional filter; and

transmitting, to the second network entity, a first message comprising the first filter and information indicating that the first filter is the bidirectional filter, based on identifying that the second network entity supports the function of obtaining the second filter.

2. The method of claim 1 , further comprising:

transmitting, to the second network entity, an association setup request message; and

receiving, from the second network entity in response to the association setup request message, an association setup response message comprising functional information of the second network entity,

wherein the functional information indicates whether the second network entity supports the function of obtaining the second filter.

3. The method of claim 1 , further comprising:

determining, based on the result of the comparing of the first filter and the second filter, that first source information and first destination information of the first filter respectively correspond to second source information and second destination information of the second filter; and

identifying that the first filter is the bidirectional filter based on the determining,

wherein the second filter has been obtained by the second network entity based on the first filter being identified as the bidirectional filter, and

wherein the first filter and the second filter are configured to detect traffic of the application.

4. The method of claim 1 , further comprising:

transmitting, to the second network entity, a second message comprising the first filter and the second filter, based on the first filter not being identified as the bidirectional filter.

5. The method of claim 1 , further comprising:

transmitting, to the second network entity, a second message comprising the first filter and the second filter to the second network entity, based on identifying that the second network entity does not support the function of obtaining the second filter.

6. A method of a second network entity performing a user plane function (UPF) in a communication system, comprising:

receiving a first message comprising a first filter for a first direction associated with an application from a first network entity performing a session management function (SMF);

identifying a second filter for a second direction based on information of the first filter, based on the first message indicating that the first filter is a bidirectional filter; and

detecting traffic of the application based on the first filter and the second filter.

7. The method of claim 6 , further comprising:

receiving, from the first network entity, an association setup request message; and

transmitting, to the first network entity in response to the association setup request message, an association setup response message comprising functional information of the second network entity,

wherein the functional information indicates that the second network entity supports a function of identifying the second filter based on the first filter.

8. The method of claim 6 , wherein:

the first filter has been identified as the bidirectional filter based on a determination, based on a result of a comparison of the first filter and the second filter, that first source information and first destination information of the first filter respectively correspond to second source information and second destination information of the second filter,

wherein the second filter has been obtained by the second network entity based on the first filter being identified as the bidirectional filter, and

wherein the first filter and the second filter are configured to detect the traffic of the application.

9. The method of claim 6 , further comprising:

receiving, from the first network entity, a second message comprising the first filter and the second filter, based on the first filter not being identified as the bidirectional filter.

10. The method of claim 6 , wherein the detecting of the traffic of the application comprises identifying whether the traffic matches at least one of the first filter and the second filter.

11. A first network entity that performs a session management function (SMF) in a communication system, the first network entity comprising:

a transceiver; and

a controller controlling the transceiver,

wherein the controller is configured to:

obtain a first filter for a first direction and a second filter for a second direction, the first filter and the second filter being associated with an application;

identify whether the first filter is a bidirectional filter based on a result of comparing the first filter and the second filter;

identify whether a second network entity performing a user plane function (UPF) supports a function of obtaining the second filter, based on the first filter being identified as the bidirectional filter; and

transmit, to the second network entity, a first message comprising the first filter and information indicating that the first filter is the bidirectional filter, based on identification that the second network entity supports the function of obtaining the second filter.

12. The first network entity of claim 11 , wherein the controller is further configured to:

transmit, via the transceiver to the second network entity, an association setup request message; and

receive, via the transceiver from the second network entity in response to the association setup request message, an association setup response message comprising functional information of the second network entity,

wherein the functional information indicates whether the second network entity supports the function of obtaining the second filter.

13. The first network entity of claim 11 , wherein the controller is further configured to:

determine, based on the result of comparing of the first filter and the second filter, that first source information and first destination information of the first filter respectively correspond to second source information and second destination information of the second filter; and

identify that the first filter is the bidirectional filter based on the determination,

wherein the second filter has been obtained by the second network entity based on the first filter having been identified as the bidirectional filter, and

wherein the first filter and the second filter are configured to detect traffic of the application.

14. The first network entity of claim 11 , wherein the controller is further configured to:

transmit, via the transceiver to the second network entity, a second message comprising the first filter and the second filter, based on the identification that the first filter is not the bidirectional filter.

15. The first network entity of claim 11 , wherein the controller is further configured to:

transmit, via the transceiver to the second network entity, a second message comprising the first filter and the second filter, based on the identification that the second network entity does not support the function of obtaining the second filter.

16. A second network entity performing a user plane function (UPF) in a communication system, comprising:

a transceiver; and

a controller controlling the transceiver,

wherein the controller is configured to:

receive, via the transceiver, a first message comprising a first filter for a first direction associated with an application from a first network entity performing a session management function (SMF);

identify a second filter for a second direction based on information of the first filter, based on the first message indicating that the first filter is a bidirectional filter; and

detect traffic of the application based on the first filter and the second filter.

17. The second network entity of claim 16 , wherein the controller is further configured to:

receive, from the first network entity, an association setup request message; and

transmit, to the first network entity in response to the association setup request message, an association setup response message comprising functional information of the second network entity,

wherein the functional information indicates that the second network entity supports a function of identifying the second filter based on the first filter.

18. The second network entity of claim 16 , wherein:

the first filter has been identified as the bidirectional filter based on a determination, based on a result of a comparison of the first filter and the second filter, that first source information and first destination information of the first filter respectively correspond to second source information and second destination information of the second filter,

wherein the second filter has been obtained by the second network entity based on the first filter being identified as the bidirectional filter, and

wherein the first filter and the second filter are configured to detect the traffic of the application.

19. The second network entity of claim 16 , wherein the controller is further configured to:

receive, from the first network entity, a second message comprising the first filter and the second filter, based on the first filter not being identified as the bidirectional filter.

20. The second network entity of claim 16 , wherein the controller is further configured to identify whether the traffic matches at least one of the first filter and the second filter.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 14, 2023
From: LEE, JEONGHWA; MOON, EUIKYUM
To: SAMSUNG ELECTRONICS CO., LTD.
Reel/Frame 064910/0628 →
Priority Claims (1)
KR 10-2021-0033158 · Mar 15, 2021 · national
Continuity (2)
Continuation PCTKR2021003158 · Mar 15, 2021
Related Publication 20240031257A1 · Jan 25, 2024
References Cited (41)
US 9306818B2 · Aumann et al. · 2016 [cited by applicant]
US 9392531B2 · Pinheiro et al. · 2016 [cited by applicant]
US 9609647B2 · You et al. · 2017 [cited by applicant]
US 9749895B2 · Phan et al. · 2017 [cited by applicant]
US 10602538B2 · LOee et al. · 2020 [cited by applicant]
US 10693918B2 · Verma et al. · 2020 [cited by applicant]
US 20160269104A1 · Lee et al. · 2016 [cited by applicant]
US 20190357082A1 · Kim et al. · 2019 [cited by applicant]
US 20200128503A1 · Li et al. · 2020 [cited by applicant]
US 20200154350A1 · Dao · 2020 [cited by examiner]
US 20210282048A1 · Lee · 2021 [cited by applicant]
US 20210329485A1 · Han et al. · 2021 [cited by applicant]
US 20210360501A1 · Jin et al. · 2021 [cited by applicant]
US 20220377645A1 · Muoz De La Torre Alonso · 2022 [cited by examiner]
US 20220417121A1 · Muoz De La Torre Alonso · 2022 [cited by examiner]
US 20230133781A1 · Yao · 2023 [cited by examiner]
CN 106255148A · 2016 [cited by applicant]
CN 111163495A · 2020 [cited by applicant]
CN 111465062A · 2020 [cited by applicant]
CN 111465063A · 2020 [cited by applicant]
EP 1884037B1 · 2016 [cited by applicant]
EP 3101944B1 · 2020 [cited by applicant]
KR 1020190132921A · 2019 [cited by applicant]
KR 1020200018220A · 2020 [cited by applicant]
KR 102167343B1 · 2020 [cited by applicant]
KR 102207786B1 · 2021 [cited by applicant]
KR 102366709B1 · 2022 [cited by applicant]
WO 2014051322A1 · 2014 [cited by applicant]
WO 2014161175A1 · 2014 [cited by applicant]
WO 2015069065A1 · 2015 [cited by applicant]
WO 2016048100A1 · 2016 [cited by applicant]
WO WO2020019991A1 · 2020 [cited by examiner]
WO 2020041368A1 · 2020 [cited by applicant]
WO WO2023035894A1 · 2023 [cited by examiner]
International Search Report (PCT/ISA/210) issued Dec. 13, 2021 by the International Searching Authority in counterpart International Patent Application No. PCT/KR2021/003158. [cited by applicant]
Written Opinion (PCT/ISA/237) issued Dec. 13, 2021 by the International Searching Authority in counterpart International Patent Application No. PCT/KR2021/003158. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Interface between the Control Plane and the User Plane Nodes; Stage 3, (Release 16), 3GPP TS 29.244, V16.6.0, Dec. 2020. (318… [cited by applicant]
“3rdGeneration Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control (PCC); Reference points”, (Release 16), 3GPP TS 29.212 V16.4.0, Sep. 2020. (287 pages total). [cited by applicant]
Ericsson et al., “Filter ID”, 3GPP TSG-CT WG4 Meeting #102e, E-Meeting, Feb. 24, 2021-Mar. 5, 2021, C4-211630. (23 pages total). [cited by applicant]
3GPP, “5G; NR; Overall description; Stage-2”, ETSI TS 138 300, V15.2.0, Sep. 2018. (86 pages total). [cited by applicant]
5G PPP, “View on 5G Architecture”, 5G PPP Architecture Working Group, Version 3.0, Jun. 19, 2019. (166 pages total). [cited by applicant]