IP Library › Granted Patent US 12,483,564
Granted Patent B2
US 12,483,564 · App. 18/517,924 · Granted Nov 25, 2025

Method for providing restricted service, and communications device

Inventors: Manli Sun (Shenzhen, CN); Zhenglei Huang (Shenzhen, CN); Yanmei Yang (Beijing, CN); Haiyang Sun (Beijing, CN)
Assignee: HUAWEI TECHNOLOGIES CO., LTD.
H04L63/1408G16Y30/10G16Y40/50H04L47/20H04L63/20H04L67/12H04L67/14H04L41/0894
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,483,564
App. No.
18/517,924
Granted
Nov 25, 2025
Kind
B2
Abstract

A method for providing a restricted service and a communications device, where the method includes: receiving, by a policy control function (PCF), an identifier of a terminal and indication information, where the indication information is used to indicate that the terminal is in a state of exception or indicate an exception type of the terminal; and sending, by the PCF, the identifier of the terminal and a first restricted service policy according to the indication information, where the first restricted service policy is used to provide a restricted service for the terminal.

Claims (59)

1 . A system, comprising:

a policy control function (PCF) configured to:

receive an identifier of a terminal and indication information, wherein the indication information indicates an exception type of the terminal, and wherein the exception type comprises that performance of a flow of the terminal is abnormal;

determine a first service policy corresponding to the exception type; and

send the first service policy; and

a network data analytics function (NWDAF) configured to:

determine the exception type; and

send, to the PCF, the identifier and the indication information.

2 . The system of claim 1 , wherein the first service policy comprises:

stopping a data flow; or

restricting the data flow.

3 . The system of claim 1 , wherein the first service policy comprises:

stopping an uplink data flow;

restricting a downlink data flow; or

stopping the uplink data flow and restricting the downlink data flow.

4 . The system of claim 1 , wherein the NWDAF is further configured to determine the exception type by determining, based on traffic information of the terminal, the exception type of the terminal, and wherein the traffic information comprises uplink traffic information or downlink traffic information.

5 . The system of claim 1 , wherein the performance of the flow of the terminal is abnormal comprises:

abnormal uplink traffic;

abnormal downlink traffic; or

the abnormal uplink traffic and the abnormal downlink traffic.

6 . The system of claim 1 , wherein the system further comprises a session management function (SMF), and wherein the SMF is configured to receive the first service policy.

7 . The system of claim 1 , wherein that the performance of the flow of the terminal is abnormal comprises a rate of the flow is abnormal.

8 . A method, comprising:

receiving, by a policy control function (PCF) and from a network data analytics function (NWDAF), an identifier of a terminal and indication information, wherein the indication information indicates an exception type of the terminal, and wherein the exception type comprises that performance of a flow of the terminal is abnormal;

determining, by the PCF, a first service policy corresponding to the exception type;

sending, by the PCF, the first service policy;

determining, by the NWDAF, the exception type; and

sending, by the NWDAF to the PCF, the identifier and the indication information.

9 . The method of claim 8 , wherein the first service policy comprises:

stopping a data flow; or

restricting the data flow.

10 . The method of claim 8 , wherein the first service policy comprises:

stopping an uplink data flow;

restricting a downlink data flow; or

stopping the uplink data flow and restricting the downlink data flow.

11 . The method of claim 8 , wherein determining, by the NWDAF, the exception type comprises determining, by the NWDAF and based on traffic information of the terminal, the exception type of the terminal, and wherein the traffic information comprises uplink traffic information or downlink traffic information.

12 . The method of claim 8 , wherein the performance of the flow of the terminal is abnormal comprises:

abnormal uplink traffic;

abnormal downlink traffic; or

the abnormal uplink traffic and the abnormal downlink traffic.

13 . The method of claim 8 , wherein that the performance of the flow is abnormal comprises a rate of the flow is abnormal.

14 . The method of claim 8 , wherein sending, by the PCF, the first service policy comprises sending, by the PCF, the first service policy to a session management function (SMF), and wherein the method further comprises receiving, by the SMF, the first service policy.

15 . A computer program product comprising instructions stored on a non-transitory computer-readable medium that, when executed by one or more processors, cause an apparatus to:

receive, from a data network data analytics function (NWDAF), an identifier of a terminal and indication information, wherein the indication information indicates an exception type of the terminal, and wherein the exception type comprises that performance of a flow of the terminal is abnormal;

determine a first service policy corresponding to the exception type; and

send, to a session management function (SMF), the first service policy.

16 . The computer program product of claim 15 , wherein the one or more processors are further configured to execute the instructions to cause the apparatus to:

stop a data flow; or

restrict the data flow.

17 . The computer program product of claim 15 , wherein the first service policy comprises:

stopping an uplink data flow;

restricting a downlink data flow; or

stopping the uplink data flow and restricting the downlink data flow.

18 . The computer program product of claim 15 , wherein the exception type of the terminal is determined based on traffic information of the terminal, and wherein the traffic information comprises uplink traffic information or downlink traffic information.

19 . The computer program product of claim 15 , wherein the performance of the flow of the terminal is abnormal comprises:

abnormal uplink traffic;

abnormal downlink traffic; or

the abnormal uplink traffic and the abnormal downlink traffic.

20 . The computer program product of claim 15 , wherein that the performance of the flow of the terminal is abnormal comprises a rate of the flow is abnormal.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 22, 2023
From: SUN, MANLI; HUANG, ZHENGLEI; YANG, YANMEI; SUN, HAIYANG
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 065649/0428 →
Priority Claims (1)
CN 201810627352.8 · Jun 13, 2018 · national
Continuity (3)
Continuation 17120720 · Dec 14, 2020
Continuation PCTCN2019091145 · Jun 13, 2019
Related Publication 20240089299A1 · Mar 14, 2024
References Cited (34)
US 11848963B2 · Sun · 2023 [cited by examiner]
US 20060256012A1 · Fok et al. · 2006 [cited by applicant]
US 20110225306A1 · Delsesto et al. · 2011 [cited by applicant]
US 20140059678A1 · Parker · 2014 [cited by applicant]
US 20160338073A1 · Nuggehalli et al. · 2016 [cited by applicant]
US 20170105155A1 · Zhao et al. · 2017 [cited by applicant]
US 20200214054A1 · Qiao et al. · 2020 [cited by applicant]
US 20210250890A1 · Won · 2021 [cited by applicant]
CN 102457938A · 2012 [cited by applicant]
CN 102868444A · 2013 [cited by applicant]
CN 102882712A · 2013 [cited by applicant]
CN 102893640A · 2013 [cited by applicant]
CN 105163335A · 2015 [cited by applicant]
CN 105187290A · 2015 [cited by applicant]
CN 106028356A · 2016 [cited by applicant]
CN 106331184A · 2017 [cited by applicant]
CN 107079462A · 2017 [cited by applicant]
EP 2897336B1 · 2017 [cited by applicant]
EP 3236377A1 · 2017 [cited by applicant]
IN 201847008803A · 2018 [cited by applicant]
WO 2015133754A1 · 2015 [cited by applicant]
China Mobile: “Solution for performance improvement and supervision of mIoT terminals,” 3GPP Draft; S2-183604, Apr. 10, 2018, XP051437905, 3 pages. [cited by applicant]
Orange: “New use case: Prevention of various security attacks,” 3GPP Draft; S2-183942 WAS-3837, Apr. 20, 2018, XP051432867, 1 page. [cited by applicant]
3GPP TS 23.501 V15.1.0 (Mar. 2018), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15), 201 pages. [cited by applicant]
3GPP TS 23.502 V15.1.0 (Mar. 2018), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15), 285 pages. [cited by applicant]
3GPP TS 23.503 V15.1.0 (Mar. 2018), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and Charging Control Framework for the 5G System; Stage 2 (Release 15), 65 pages. [cited by applicant]
3GPP TS 23.682 V15.4.0 (Mar. 2018), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements to facilitate communications with packet data networks and app… [cited by applicant]
3GPP TR 23.791 V0.3.0 (Apr. 2018), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study of Enablers for Network Automation for 5G (Release 16), 19 pages. [cited by applicant]
3GPP TS 29.512 V1.0.0 (Jun. 2018), 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Session Management Policy Control Service; Stage 3 (Release 15), 82 pages. [cited by applicant]
China Mobile, “Use Case on mIoT behaviour data collection and analysis,” SA WG2 Meeting #126, S2-182086, Feb. 26-Mar. 2, 2018, Montreal, Canada, 2 pages. [cited by applicant]
China Mobile, “Use Case on mIoT behaviour data collection and analysis,” SA WG2 Meeting #126, S2-182353, Feb. 26-Mar. 2, 2018, Montreal, Canada, 2 pages. [cited by applicant]
China Mobile, “Key issue on performance improvement and supervision of mIoT terminals”, SA WG2 Meeting #127, S2-183601, Apr. 16-20, 2018, Sanya, China, 2 pages. [cited by applicant]
China Mobile, “Key issue on performance improvement and supervision of mIoT terminals,” SA WG2 Meeting #127, S2-183948, Apr. 16-20, 2018, Sanya, China, 2 pages. [cited by applicant]
China Mobile, “Key issue on performance improvement and supervision of mIoT terminals,” SA WG2 Meeting #127, S2-184575, Apr. 16-20, 2018, Sanya, China, 2 pages. [cited by applicant]