IP Library › Granted Patent US 12,189,484
Granted Patent B2
US 12,189,484 · App. 18/246,258 · Granted Jan 7, 2025

Error handling of responses

Inventors: Ioannis Mouroulis (Athens, GR); Bruno Landais (Pleumeur-Bodou, FR)
Assignee: NOKIA TECHNOLOGIES OY
G06F11/1443G06F11/0751
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,189,484
App. No.
18/246,258
Granted
Jan 7, 2025
Kind
B2
Abstract

It is provided a method comprising: monitoring if a communication initiator receives a confirmation in response to an initial message from the communication initiator to a communication partner; supervising if the communication initiator successfully processes the confirmation; providing a non-successful information at a callback resource if the confirmation comprises the identifier of the callback resource and the communication initiator does not successfully process the confirmation; wherein the confirmation comprises an identifier of the callback resource; and the confirmation confirms that the initial message is successfully processed by the communication partner.

Claims (22)

1. Apparatus comprising:

one or more processors, and

memory storing instructions that, when executed by the one or more processors, cause the apparatus to:

monitor if a communication initiator receives a confirmation in response to an initial message from the communication initiator to a communication partner, wherein the initial message is a notification;

supervise if the communication initiator successfully processes the confirmation;

provide a non-successful information at a callback resource if the confirmation comprises the identifier of the callback resource and the communication initiator does not successfully process the confirmation; wherein

the confirmation comprises an identifier of the callback resource; and

the confirmation confirms that the initial message is successfully processed by the communication partner;

check if an acknowledgment to the non-successful information provided at the callback resource is received;

operate according to a status information if the acknowledgment is received, wherein

the acknowledgment comprises the status information, and

the status information informs about a status of inverting the processing of the initial message; and

inhibit the providing the non-successful information at the callback resource if the communication initiator successfully processes the confirmation,

wherein the confirmation contains a hypertext transfer protocol header including a hypertext transfer protocol uniform resource identifier of the callback resource,

wherein the communication initiator is configured to act as a service consumer, and the communication partner is configured to act as a service producer or as a communication proxy,

if the communication partner is configured to act as the communication proxy, the initial message requests to create a resource in a further server of the hypertext transfer protocol,

wherein the communication initiator does not successfully process the confirmation if the following conditions are fulfilled:

a format of the confirmation is incorrect such that the communication initiator does not understand the confirmation;

the communication initiator receives the confirmation after a predetermined time has elapsed after the communication initiator sent the initial message; and

the communication initiator acts as a communication proxy relaying the communication between an original communication initiator and the communication partner, and the communication proxy cannot or must not forward the confirmation to the original communication initiator,

wherein if the communication partner is configured to act as the service producer, the initial message requests to create a resource in the server of the hypertext transfer protocol, and

wherein the non-successful information provided at a callback resource includes the response to the initial message.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 5, 2023
From: LANDAIS, BRUNO
To: ALCATEL-LUCENT INTERNATIONAL S.A
Reel/Frame 063849/0042 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 5, 2023
From: MOUROULIS, IOANNIS
To: NOKIA SOLUTIONS AND NETWORKS HELLAS SINGLE MEMBER S.A.
Reel/Frame 063849/0058 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 5, 2023
From: ALCATEL-LUCENT INTERNATIONAL S.A.
To: NOKIA TECHNOLOGIES OY
Reel/Frame 063849/0075 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 5, 2023
From: NOKIA SOLUTIONS AND NETWORKS HELLAS SINGLE MEMBER S.A.
To: NOKIA TECHNOLOGIES OY
Reel/Frame 063849/0096 →
Continuity (1)
Related Publication 20230359528A1 · Nov 9, 2023
References Cited (15)
US 20200267201A1 · Rauschenbach et al. · 2020 [cited by applicant]
WO 2019027480A1 · 2019 [cited by applicant]
WO 2020069825A1 · 2020 [cited by applicant]
WO 2020094914A1 · 2020 [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Principles and Guidelines for Services Definition; Stage 3 (Release 16)”, 3GPP TS 29.501, V16.4.0, Jun. 2020, pp.… [cited by applicant]
Belshe et al., “Hypertext Transfer Protocol Version 2 (HTTP/2)”, Internet Engineering Task Force (IETF), RFC 7540, May 2015, pp. 1-96. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16)”, 3GPP TS 23.501, V16.5.1, Aug. 2020, pp. 1-440. [cited by applicant]
“List of HTTP status codes”, Wikipedia, Retrieved on May 24, 2024, Webpage available at : https://en.wikipedia.org/wiki/List_of_HTTP_status_codes. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Session Management Services; Stage 3 (Release 16)”, 3GPP TS 29.502, V16.4.0, Jul. 2020, pp. 1-256. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Session Management Policy Control Service; Stage 3 (Release 16)”, 3GPP TS 29.512, V16.5.0, Jun. 2020, pp. 1-197. [cited by applicant]
International Search Report and Written Opinion received for corresponding Patent Cooperation Treaty Application No. PCT/FI2020/050614, dated Mar. 26, 2021, 19 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of Service Based Architecture; Stage 3 (Release 16)”, 3GPP TS 29.500, V16.4.0, Jun. 2020, p… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Unified Data Management Services; Stage 3 (Release 16)”, 3GPP TS 29.503, V16.4.0, Jul. 2020, pp. 1-347. [cited by applicant]
“Multi-access Edge Computing (MEC); General principles, patterns and common aspects of MEC Service APIs”, Draft ETSI GS MEC 009, V2.1.5, Jul. 2020, pp. 1-70. [cited by applicant]
Extended European Search Report received for corresponding European Patent Application No. 20955113.4, dated May 10, 2024, 11 pages. [cited by applicant]