IP Library › Granted Patent US 12,513,200
Granted Patent B2
US 12,513,200 · App. 17/707,232 · Granted Dec 30, 2025

Network API capability reporting method, apparatus, and system

Inventors: Yali Yan (Shanghai, CN); Qianghua Zhu (Beijing, CN); Xiaoyun Zhou (Nanjing, CN)
Assignee: HUAWEI TECHNOLOGIES CO., LTD.
H04L65/1063G06F9/547H04L65/611H04L67/02H04W4/50H04W24/10H04W36/00222
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,513,200
App. No.
17/707,232
Granted
Dec 30, 2025
Kind
B2
Abstract

A network API capability reporting method includes: A first entity receives first information, where the first information is used to subscribe to an API capability of a network that serves a terminal device. The first entity sends second information to a second entity when a type of the network that serves the terminal device changes, where the second information includes an API capability of a network that currently serves the terminal device, and where the API capability includes an API supported by the network that serves the terminal device and an availability feature of at least one API in the supported API.

Claims (37)

1 . A network application programming interface (API) capability reporting method implemented by a first entity and comprising:

receiving first information usable for subscribing to an API capability of a network serving a terminal device; and

sending second information to a second entity when the network changes from a first network of a first type to a second network of a second type,

wherein the second information comprises a second API capability of the second network,

wherein the second API capability indicates an API supported by the second network and at least one feature that is of the API and that is capable of being used in the second network,

wherein the second API capability indicating the API and the at least one feature comprises the second API capability indicating all APIs supported by the second network and all features that are of all the APIs supported by the second network and that are capable of being used in the second network.

2 . The network API capability reporting method according to claim 1 , wherein the first entity comprises at least one of a service capability exposure function entity or a network exposure function entity, and wherein the second entity comprises at least one of a service capability server/application server or an application function entity.

3 . The network API capability reporting method according to claim 1 , wherein receiving the first information comprises receiving the first information from the second entity, and wherein the second entity is a service capability server/application server or an application function entity.

4 . The network API capability reporting method according to claim 1 , wherein the at least one feature is of an API that has been subscribed to and has not expired.

5 . The network API capability reporting method according to claim 1 , wherein the at least one feature is of an API of interest.

6 . The network API capability reporting method according to claim 1 , wherein the at least one feature comprises a first feature and a second feature, wherein the first feature is of a first API that has been subscribed to and has not expired, and wherein the second feature is of a second API of interest.

7 . The network API capability reporting method according to claim 1 , further comprising receiving, from a unified data management entity when the network changes from a 4 th generation (4G) network to a 5 th generation (5G) network, notification that a type of the network has changed, wherein the first entity is a network exposure entity, and wherein the second entity is an application function entity.

8 . The network API capability reporting method according to claim 1 , further comprising receiving, from a home subscriber server entity when the network changes from a 5 th generation (5G) network to a 4 th generation (4G) network, notification that a type of the network has changed, wherein the first entity is a service capability exposure function entity, and wherein the second entity is an application server.

9 . The network API capability reporting method according to claim 1 , wherein receiving the first information comprises receiving a Hypertext Transfer Protocol (HTTP) post request message, and wherein the HTTP post request message comprises the first information.

10 . The network API capability reporting method according to claim 1 , wherein sending the second information comprises sending a Hypertext Transfer Protocol (HTTP) post request message, and wherein the HTTP post request message comprises the second information.

11 . An apparatus comprising:

a memory configured to store program instructions; and

at least one processor configured to execute the program instructions to cause the apparatus to:

receive first information usable for subscribing to an application programming interface (API) capability of a network serving a terminal device; and

send second information to a second entity when the network changes from a first network of a first type to a second network of a second type,

wherein the second information indicates a second API capability of the second network,

wherein the second API capability indicates an API supported by the second network and at least one feature that is of the API and that is capable of being used in the second network, and

wherein the second API capability indicating the API and the at least one feature comprises the second API capability indicating all APIs supported by the second network and all features that are of all the APIs supported by the second network and that are capable of being used in the second network.

12 . The apparatus according to claim 11 , wherein the apparatus comprises at least one of a service capability exposure function entity or a network exposure function entity, and wherein the second entity comprises at least one of a service capability server/application server or an application function entity.

13 . The apparatus according to claim 11 , wherein the at least one processor is further configured to execute the program instructions to cause the apparatus to further receive the first information from the second entity, and wherein the second entity is a service capability server/application server or an application function entity.

14 . The apparatus according to claim 11 , wherein the at least one feature is of an API that has been subscribed to and has not expired.

15 . The apparatus according to claim 11 , wherein the at least one feature is of an API of interest.

16 . The apparatus according to claim 11 , wherein the at least one feature comprises a first feature and a second feature, wherein the first feature is of an API that has been subscribed to and has not expired, and wherein the second feature is of an API of interest.

17 . The apparatus according to claim 11 , wherein the at least one processor is further configured to execute the program instructions to cause the apparatus to receive, from a unified data management entity when the network changes from a 4 th generation (4G) network to a 5 th generation (5G) network, notification that a type of the network has changed, and wherein the apparatus is a network exposure function entity, and wherein the second entity is an application function entity.

18 . The apparatus according to claim 11 , wherein the at least one processor is further configured to execute the program instructions to cause the apparatus to receive, from a home subscriber server entity when the network changes from a 5 th generation (5G) network to a 4 th generation (4G) network, notification that a type of the network has changed, and wherein the apparatus is a service capability exposure function entity, and wherein the second entity is an application server.

19 . A non-transitory computer-readable storage medium configured to store instructions, which when executed by at least one processor, cause an apparatus to:

receive first information usable for subscribing to an application programming interface (API) capability of a network serving a terminal device; and

send second information to a second entity when the network changes from a first network of a first type to a second network of a second type,

wherein the second information comprises a second API capability of the second network,

wherein the second API capability indicates an API supported by the second network and at least one feature that is of the API and that is capable of being used in the second network, and

wherein the second API capability indicating the API and the at least one feature comprises the second API capability indicating all APIs supported by the second network and all features that are of all the APIs supported by the second network and that are capable of being used in the second network.

20 . The non-transitory computer-readable storage medium according to claim 19 , wherein the instructions, when executed by the at least one processor, further cause the apparatus to further receive the first information from the second entity, and wherein the second entity is a service capability server/application server or an application function entity.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 22, 2025
From: YAN, YALI; ZHU, QIANGHUA; ZHOU, XIAOYUN
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 072091/0880 →
Priority Claims (1)
CN 201910936851.X · Sep 29, 2019 · national
Continuity (2)
Continuation PCTCN2020118092 · Sep 27, 2020
Related Publication 20220225149A1 · Jul 14, 2022
References Cited (20)
US 20080222238A1 · Ivanov et al. · 2008 [cited by applicant]
US 20160164945A1 · Ding et al. · 2016 [cited by applicant]
US 20180270780A1 · Xiong · 2018 [cited by examiner]
US 20190020549A1 · Kim · 2019 [cited by examiner]
US 20210014759A1 · Zhu · 2021 [cited by examiner]
CN 1878083A · 2006 [cited by applicant]
CN 102938763A · 2013 [cited by applicant]
CN 105704108A · 2016 [cited by applicant]
CN 105981471A · 2016 [cited by applicant]
CN 108111629A · 2018 [cited by applicant]
CN 109246653A · 2019 [cited by applicant]
CN 110366145A · 2019 [cited by applicant]
3GPP TS 29.522 V16.1.0, Sep. 2019, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Exposure Function Northbound APIs; Stage 3 (Release 16),” 82 pages. [cited by applicant]
3GPP TS 29.122 V16.3.0, Sep. 2019, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; T8 reference point for Northbound APIs; (Release 16),” 322 pages. [cited by applicant]
3GPP TS 23.502 V16.2.0, Sep. 2019, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 16),” Sep. 2019, 525 pages. [cited by applicant]
3GPP TS 23.501 V16.2.0, Sep. 2019, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System (5GS); Stage 2 (Release 16),” 389 pages. [cited by applicant]
Huawei, “Corrections on Network Parameter Configuration,” 3GPP TSG-CT WG3 Meeting #97, C3-183639, Osaka, Japan, May 21-25, 2018, 11 pages. [cited by applicant]
Secretary of SA WG2, “Draft Report of SA WG2 meetings #128,” SA WG2 Meeting #S2-128BIS, S2-187631, Aug. 20-24, 2018, Sophia Antipolis, France, 475 pages. [cited by applicant]
Huawei et al., “Resolve the editor″s notes in Solution 14,” 3GPP TSG-SA WG2 Meeting #127 Bis, S2-185115, May 28-Jun. 1, 2018, 8 pages. [cited by applicant]
3GPP TR 23.724 v16.1.0, Jun. 2019, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Cellular Internet of Things (IoT) support and evolution for the 5G System (Rele… [cited by applicant]