IP Library › Granted Patent US 12,588,107
Granted Patent B2
US 12,588,107 · App. 17/172,699 · Granted Mar 24, 2026

Message transmission method, apparatus, and storage medium

Inventors: Zaifeng Zong (Nanjing, CN); Fenqin Zhu (Shanghai, CN)
Assignee: HUAWEI TECHNOLOGIES CO., LTD.
H04W88/182H04W48/16H04W48/18H04W88/184H04W92/02
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,588,107
App. No.
17/172,699
Granted
Mar 24, 2026
Kind
B2
Abstract

A message transmission method includes receiving, by a first transmission proxy, a first message from a first service instance, where the first message includes an identifier of a first service set, obtaining, by the first transmission proxy, a second service instance in the first service set based on the identifier that is of the first service set and that is included in the received first message, and sending, by the first transmission proxy, a second message to the second service instance based on the first message.

Claims (56)

1 . A message transmission system comprising:

service sets comprising a first service set, wherein the first service set has a first identifier and comprises at least one service instance, wherein the at least one service instance comprises a second service instance, wherein each of the at least one service instance has a same capability information, and wherein the capability information comprises a capability of a supported network slice, a capacity, or a data network name (DNN);

a first service instance configured to:

obtain the first identifier; and

send a first message, wherein the first message is a Hypertext Transfer Protocol (HTTP) message comprising a message header, and wherein the message header comprises the first identifier;

a second transmission proxy connected to the first service instance and configured to:

receive the first message from the first service instance; and

send the first message; and

a first transmission proxy connected to the service sets, based on the first identifier, and configured to:

receive the first message from the second transmission proxy;

obtain the second service instance from the first service set identified by the first identifier; and

send a second message to the second service instance based on the first message,

wherein the first identifier enables determination of the first transmission proxy.

2 . The message transmission system of claim 1 , wherein the first service instance is further configured to obtain the first identifier by:

receiving, from the second service instance, a response message comprising the first identifier; and

obtaining the first identifier from the response message.

3 . The message transmission system of claim 1 , wherein the first service instance is further configured to obtain the first identifier by:

sending the capability information of a requested service instance of the first service instance to a network registration network element; and

receiving the first identifier from the network registration network element, wherein the at least one service instance provides the capability information.

4 . The message transmission system of claim 3 , wherein the first service instance is further configured to receive a second identifier of the first transmission proxy from the network registration network element, and wherein the first transmission proxy corresponds to the first service set.

5 . The message transmission system of claim 3 , wherein the capability information further comprises a serving area or a service type.

6 . The message transmission system of claim 1 , wherein the first transmission proxy is further configured to further obtain the second service instance by:

determining the first service set based on the first identifier; and

determining the second service instance in the first service set based on a load status of each of the at least one service instance.

7 . A message transmission method comprising:

obtaining, by a first service instance, a first identifier of a first service set, wherein the first identifier enables determination of a first transmission proxy that is based on the first identifier, wherein the first service set comprises at least one service instance, wherein the at least one service instance comprises a second service instance, wherein each of the at least one service instance has a same capability information, and wherein the capability information comprises a capability of a supported network slice, a capacity, or a data network name (DNN);

sending, by the first service instance to a second transmission proxy connected to the first service instance, a first message, wherein the first message is a Hypertext Transfer Protocol (HTTP) message comprising a message header, and wherein the message header comprises the first identifier;

receiving, by the second transmission proxy from the first service instance, the first message;

sending, by the second transmission proxy to the first transmission proxy, the first message;

receiving, by the first transmission proxy from the second transmission proxy, the first message, wherein the first transmission proxy is connected to service sets comprising the first service set;

obtaining, by the first transmission proxy, the second service instance from the first service set identified by the first identifier; and

sending, by the first transmission proxy to the second service instance, a second message based on the first message.

8 . The message transmission method of claim 7 , wherein obtaining the first identifier comprises:

receiving, by the first service instance from the second service instance, a response message comprising the first identifier; and

obtaining, by the first service instance from the response message, the first identifier.

9 . The message transmission method of claim 7 , wherein obtaining the first identifier comprises:

sending, by the first service instance to a network registration network element, the capability information of a requested service instance of the first service instance; and

receiving, by the first service instance from the network registration network element, the first identifier, wherein the at least one service instance provides the capability information.

10 . The message transmission method of claim 9 , further comprising receiving, by the first service instance from the network registration network element, a second identifier of the first transmission proxy, wherein the first transmission proxy corresponds to the first service set.

11 . The message transmission method of claim 9 , wherein the capability information further comprises a serving area or a service type.

12 . The message transmission method of claim 7 , wherein obtaining, by the first transmission proxy, the second service instance comprises:

determining the first service set based on the first identifier; and

determining the second service instance in the first service set based on a load status of each of the at least one service instance.

13 . A first service instance apparatus comprising:

a memory configured to store instructions; and

one or more processors coupled to the memory and configured to execute the instructions to cause the first service instance apparatus to:

obtain a first identifier of a first service set, wherein the first identifier enables determination of a first transmission proxy that is based on the first identifier, wherein the first service set comprises at least one service instance, wherein the at least one service instance comprises a second service instance, wherein each of the at least one service instance has a same capability information, and wherein the capability information comprises a capability of a supported network slice, a capacity, or a data network name (DNN); and

send a first message to a second transmission proxy connected to the first service instance apparatus to enable the second transmission proxy to send the first message to the first transmission proxy, wherein the first message is a Hypertext Transfer Protocol (HTTP) message comprising a message header, and wherein the message header comprises the first identifier.

14 . The first service instance apparatus of claim 13 , wherein the one or more processors are further configured to execute the instructions to cause the first service instance apparatus to obtain the first identifier by:

receiving, from the second service instance, a response message comprising the first identifier; and

obtaining the first identifier from the response message.

15 . The first service instance apparatus of claim 13 , wherein the one or more processors are further configured to execute the instructions to cause the first service instance apparatus to obtain the first identifier by:

sending the capability information of a requested service instance of the first service instance apparatus to a network registration network element; and

receiving the first identifier from the network registration network element, wherein the at least one service instance provides the capability information.

16 . The first service instance apparatus of claim 15 , wherein the one or more processors are further configured to execute the instructions to cause the first service instance apparatus to receive a second identifier of the first transmission proxy from the network registration network element, and wherein the first transmission proxy corresponds to the first service set.

17 . The first service instance apparatus of claim 15 , wherein the capability information further comprises a serving area or a service type.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 5, 2023
From: ZONG, ZAIFENG; ZHU, FENQIN
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 064793/0705 →
Priority Claims (1)
CN 201810918783.X · Aug 13, 2018 · national
Continuity (2)
Continuation PCTCN2019100434 · Aug 13, 2019
Related Publication 20210168906A1 · Jun 3, 2021
References Cited (37)
US 10848576B2 · Stammers · 2020 [cited by examiner]
US 11350274B2 · Watfa · 2022 [cited by examiner]
US 20130337822A1 · Rubin et al. · 2013 [cited by applicant]
US 20140244728A1 · Endo · 2014 [cited by examiner]
US 20160094632A1 · Jain et al. · 2016 [cited by applicant]
US 20180199279A1 · Baek · 2018 [cited by examiner]
US 20180376414A1 · Zeng · 2018 [cited by examiner]
US 20190141606A1 · Qiao · 2019 [cited by examiner]
US 20190200208A1 · Chandramouli · 2019 [cited by examiner]
US 20190260803A1 · Bykampadi · 2019 [cited by examiner]
US 20190306251A1 · Talebi Fard · 2019 [cited by examiner]
US 20190327317A1 · Lu et al. · 2019 [cited by applicant]
US 20190335392A1 · Qiao · 2019 [cited by examiner]
US 20210127265A1 · Chandramouli · 2021 [cited by examiner]
US 20210282003A1 · Li · 2021 [cited by examiner]
US 20210321245A1 · Landais · 2021 [cited by examiner]
US 20210385286A1 · Wang · 2021 [cited by examiner]
CN 101924768A · 2010 [cited by applicant]
CN 104662994A · 2015 [cited by applicant]
CN 105812488A · 2016 [cited by applicant]
CN 106031128A · 2016 [cited by applicant]
CN 107995045A · 2018 [cited by applicant]
CN 108243225A · 2018 [cited by applicant]
CN 108270621A · 2018 [cited by applicant]
CN 108270823A · 2018 [cited by applicant]
WO 2018128499A1 · 2018 [cited by applicant]
SGPP TR 23.742 V0.3.0 (Jul. 2018), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects;Study on Enhancements to the Service-Based Architecture(Release 16), total 66 pages. [cited by applicant]
Ravishankar Ravindran et al., “Deploying ICN in 3GPP S SG NextGen Core Architecture”,2018 IEEE 5G World Forum,Jul. 9, 2018, total 8 pages. [cited by applicant]
Dan Wang et al., “Service-based Architecture in 5G by NGMN Alliance”, V1.0,19—Jan. 2018, 17 pages. [cited by applicant]
China Mobile, “Further clarification for distributed service framework”, 3GPP TSG-SA WG2 Meeting #128 S2-186498, Vilnius, Lithuania, Jul. 2-6, 2018, 3 pages. [cited by applicant]
China Mobile, “Further clarification for distributed service framework”, 3GPP TSG-SA WG2 Meeting #128 S2-187517, Vilnius, Lithuania, Jul. 2-6, 2018, 3 pages. [cited by applicant]
3GPP TS 23.501 V15.2.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15),” Jun. 2018, 216 pages. [cited by applicant]
3GPP TS 23.502 V15.2.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15),” Jun. 2018, 308 pages. [cited by applicant]
3GPP TS 29.500 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of Service Based Architecture; Stage 3 (Release 15),” Jun. 2018, 28… [cited by applicant]
3GPP TS 29.510 V15.0.0, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 15),” Jun. 2018, 64 pages. [cited by applicant]
Sony, “NR-NTN—Text Proposal for TR 38.811 chap 6 NTN channel modelling,” 3GPP TSG RAN WG2 Meeting #102, R1-1807792, May 21-25, 2018, 33 pages. [cited by applicant]
Ericsson, “guami-Type in RRC Setup Complete,” 3GPP TSG-RAN WG2 #102, R2-1807912, May 21-25, 2018, 3 pages. [cited by applicant]