IP Library › Granted Patent US 12,250,276
Granted Patent B2
US 12,250,276 · App. 18/457,669 · Granted Mar 11, 2025

Method for routing data of a session initialized between a terminal and a server

Inventors: Gael Fromentoux (Chatillon, FR); Frederic Fieau (Chatillon, FR); Emile Stephan (Chatillon, FR)
Assignee: ORANGE
H04L67/141H04L69/326H04W12/02H04W48/18H04W76/11
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,250,276
App. No.
18/457,669
Granted
Mar 11, 2025
Kind
B2
Abstract

A method for routing data of a session initialized between a terminal and a server, over a first network slice corresponding to a set of data-processing functions of a communication infrastructure, implemented by the terminal. This method includes receiving from the server at least one routing identifier determined as a function of at least one communication parameter of the session, configuring session information as a function of the at least one identifier received, and emitting to the server subsequent data routed over at least one second slice corresponding to the configured information.

Claims (44)

1. A routing method for routing data of a session initialized between a terminal and an application server, over a first network slice corresponding to a set of data processing functions of a communication infrastructure, implemented by the terminal, and comprising:

receiving from the application server, in a HyperText Transfer Protocol (HTTP), at least one routing identifier determined based on at least one communication parameter of the session,

configuring a piece of session information based on the at least one routing identifier received, and

transmitting to the application server subsequent data routed over at least a second slice corresponding to the configured piece of session information.

2. The routing method as claimed in claim 1 , comprising ciphering the session by the terminal.

3. The routing method as claimed in claim 1 , comprising initializing the session by the terminal by configuring a default piece of session information.

4. The routing method as claimed in claim 1 , where the piece of session information comprises a data element relating to a piece of Network Slice Selection Assistance Information (NSSAI) information.

5. The routing method as claimed in claim 1 , further comprising the terminal storing in memory the at least one routing identifier received based on the at least one communication parameter of the session.

6. The routing method according to claim 1 wherein the session is an HTTP session.

7. A determination method for determining at least one routing identifier of data of a session initialized between a terminal and an application server, over a first network slice corresponding to a set of functions for processing data of a communication infrastructure, implemented by the application server and comprising:

determining at least one routing identifier of the communication infrastructure based on at least one communication parameter of the session,

transmitting to the terminal, in a HyperText Transfer Protocol (HTTP) the at least one routing identifier determined, and

receiving from the terminal subsequent data routed over at least a second slice.

8. The determination method as claimed in claim 7 , where the at least one communication parameter relates to a transport layer of the session.

9. The determination method as claimed in claim 7 , where the at least one communication parameter relates to the Quick UDP Internet Connections (QUIC) protocol.

10. The determination method as claimed in claim 7 , where the at least one communication parameter relates to a protocol version of a transport layer.

11. The determination method as claimed in claim 7 , where the at least one routing identifier is transmitted in a data element of a transport protocol.

12. The determination method according to claim 7 wherein the session is an HTTP session.

13. A device for routing data of a session initialized between a terminal and a server, over a first network slice corresponding to a set of data processing functions of a communication infrastructure, implemented by the terminal, wherein the device comprises:

a receiver;

a transmitter; and

a processor configured to:

use the receiver to receive in a HyperText Transfer Protocol (HTTP) from the server at least one routing identifier determined on the basis of at least one communication parameter of the session,

configure a piece of session information based on the at least one routing identifier received, and

use the transmitter to transmit to the application server subsequent data routed over at least a second slice corresponding to the configured information.

14. The terminal comprising the device for routing as claimed in claim 13 .

15. The device according to claim 13 wherein the session is an HTTP session.

16. A device for determining at least one routing identifier of data of a session initialized between a terminal and an application server, over a first network slice corresponding to a set of functions for processing data of a communication infrastructure, implemented by the application server, wherein the device comprises:

a transmitter;

a receiver; and

a processor, configured to:

determine at least one routing identifier based on at least one communication parameter of the session,

use the transmitter to transmit in a HyperText Transfer Protocol (HTTP) to the terminal the at least one routing identifier determined, and

use the receiver to receive from the terminal subsequent data routed over at least a second slice.

17. The device according to claim 16 wherein the session is an HTTP session.

18. A non-transitory computer-readable recording medium comprising a computer program recorded thereon, the computer program comprising instructions for implementing a routing method when the instructions are executed by a processor of a terminal, the routing method for routing data of a session initialized between the terminal and an application server, over a first network slice corresponding to a set of data processing functions of a communication infrastructure, wherein the instructions configure the terminal to:

receive in a HyperText Transfer Protocol (HTTP) from the server at least one routing identifier determined based on at least one communication parameter of the session,

configure a piece of session information based on the at least one routing identifier received, and

transmit to the application server subsequent data routed over at least a second slice corresponding to the configured information.

19. The non-transitory computer-readable recording medium according to claim 18 wherein the session is an HTTP session.

20. A non-transitory computer-readable recording medium comprising a computer program recorded thereon, the computer program comprising instructions for implementing a determination method when the instructions are executed by a processor of an application server, the determination method for determining at least one routing identifier of data of a session initialized between a terminal and the application server, over a first network slice corresponding to a set of functions for processing the data of a communication infrastructure, wherein the instructions configure the server to:

determine at least one routing identifier based on at least one communication parameter of the session,

transmit in a HyperText Transfer Protocol (HTTP) to the terminal the at least one routing identifier determined, and

receive from the terminal subsequent data routed over at least a second slice.

Priority Claims (1)
FR 1761552 · Dec 1, 2017 · national
Continuity (3)
Continuation 17839799 · Jun 14, 2022
Continuation 16768410
Related Publication 20230403330A1 · Dec 14, 2023
References Cited (77)
US 10142994B2 · Lee · 2018 [cited by applicant]
US 10588022B2 · Mouquet · 2020 [cited by examiner]
US 10958541B2 · Chatras · 2021 [cited by examiner]
US 10959102B2 · Mouquet · 2021 [cited by examiner]
US 11394787B2 · Fromentoux · 2022 [cited by examiner]
US 11716631B2 · Mouquet · 2023 [cited by examiner]
US 11785095B2 · Fromentoux · 2023 [cited by examiner]
US 11818585B2 · Mouquet · 2023 [cited by examiner]
US 20160073327A1 · Clougherty · 2016 [cited by examiner]
US 20170164212A1 · Opsenica · 2017 [cited by examiner]
US 20170164229A1 · Callard · 2017 [cited by examiner]
US 20170245316A1 · Salkintzis · 2017 [cited by examiner]
US 20170289791A1 · Yoo · 2017 [cited by examiner]
US 20170303259A1 · Lee · 2017 [cited by examiner]
US 20170318450A1 · Salkintzis · 2017 [cited by examiner]
US 20170367036A1 · Chen · 2017 [cited by examiner]
US 20180176858A1 · Wang · 2018 [cited by examiner]
US 20180192445A1 · Jiang · 2018 [cited by examiner]
US 20180249375A1 · Goldhamer · 2018 [cited by examiner]
US 20180316779A1 · Dowlatkhah · 2018 [cited by examiner]
US 20180324577A1 · Faccin · 2018 [cited by examiner]
US 20180324645A1 · Park · 2018 [cited by examiner]
US 20180332441A1 · Shaw · 2018 [cited by examiner]
US 20180352592A1 · Zhu · 2018 [cited by examiner]
US 20180376338A1 · Ashrafi · 2018 [cited by examiner]
US 20190021010A1 · Senarath · 2019 [cited by examiner]
US 20190026094A1 · Stammers · 2019 [cited by examiner]
US 20190029065A1 · Park · 2019 [cited by examiner]
US 20190124561A1 · Faccin · 2019 [cited by examiner]
US 20190124704A1 · Sun · 2019 [cited by examiner]
US 20190150081A1 · Qiao · 2019 [cited by examiner]
US 20190159117A1 · Kuge · 2019 [cited by examiner]
US 20190191367A1 · Ni · 2019 [cited by examiner]
US 20190223093A1 · Watfa · 2019 [cited by examiner]
US 20190261233A1 · Duan · 2019 [cited by examiner]
US 20190327149A1 · Sun · 2019 [cited by examiner]
US 20190357122A1 · Li · 2019 [cited by examiner]
US 20190373520A1 · Sillanpaa · 2019 [cited by examiner]
US 20200022033A1 · Wei · 2020 [cited by examiner]
US 20200077327A1 · Duan · 2020 [cited by examiner]
US 20200112492A1 · Chatras · 2020 [cited by examiner]
US 20200112861A1 · Yao · 2020 [cited by examiner]
US 20200120580A1 · Jin · 2020 [cited by examiner]
US 20200120590A1 · Trivisonno · 2020 [cited by examiner]
US 20200137576A1 · Hu · 2020 [cited by examiner]
US 20200169921A1 · Zhu · 2020 [cited by examiner]
US 20200178139A1 · Shimojou · 2020 [cited by examiner]
US 20200187061A1 · Zhu · 2020 [cited by examiner]
US 20200235989A1 · Sun · 2020 [cited by examiner]
US 20200259786A1 · Saarinen · 2020 [cited by examiner]
US 20200260330A1 · Zhu · 2020 [cited by examiner]
US 20200275338A1 · Quintuna Rodriguez · 2020 [cited by examiner]
US 20200389527A1 · Fromentoux · 2020 [cited by examiner]
US 20210195509A1 · Ohlsson · 2021 [cited by examiner]
US 20210243686A1 · Baek · 2021 [cited by examiner]
US 20220311829A1 · Fromentoux · 2022 [cited by examiner]
US 20230021843A1 · Chen · 2023 [cited by examiner]
US 20230403329A1 · Fromentoux · 2023 [cited by examiner]
US 20230403330A1 · Fromentoux · 2023 [cited by examiner]
CN 106851589A1 · 2017 [cited by applicant]
WO 2017200978A1 · 2017 [cited by applicant]
International Search Report dated Jan. 30, 2019 for corresponding International Application No. PCT/FR2018/053047, filed Nov. 29, 2018. [cited by applicant]
Written Opinion of the International Searching Authority dated Jan. 30, 2019 for corresponding International Application No. PCT/FR2018/053047, filed Nov. 29, 2018. [cited by applicant]
English translation of the Written Opinion of the International Searching Authority dated Jun. 2, 2020 for corresponding International Application No. PCT/FR2018/053047, filed Nov. 29, 2018. [cited by applicant]
3GPP TR 23.799 v2.0.0, “Wireless technology evolution towards 5G, 3GPP release 13 to 15 and beyond” 5G Americas, dated Feb. 2017, 243 pages. [cited by applicant]
T. Pauly et al., “A Survey of Transport Security Protocols draft-pauly-taps-transport-security-00”, Network Working Group Internet-Draft, dated Jul. 3, 2017, 22 pages. [cited by applicant]
J. Iyengar et al., “QUIC: A UDP-Based Multiplexed and Secure Transport draft-ietf-quic-transport-07”, Internet-Draft, Oct. 13, 2017, 82 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Release 14), 3GPP TR 23.799 V2.0.0 (Nov. 2016), Technical Report, 523 page… [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15), 3GPP TS 23.501 V1.5.0 (Nov. 2017), Technical Specification, 170… [cited by applicant]
G. Fairhurst et al., “Services Provided by IETF Transport Protocols and Congestion Control Mechanisms,” Internet Engineering Task Force (IETF), ISSN: 2070-1721, dated Mar. 2017, 54 pages. [cited by applicant]
M. Belshe et al., “Hypertext Transfer Protocol Version 2 (HTTP/2),” Internet Engineering Task Force (IETF), ISSN: 2070-1721, dated May 2015, 96 pages. [cited by applicant]
Office Action dated Sep. 30, 2021 from the United States Patent and Trademark Office, for corresponding U.S. Appl. No. 16/768,410. [cited by applicant]
Notice of Allowance dated Mar. 15, 2022 from the United States Patent and Trademark Office, for corresponding U.S. Appl. No. 16/768,410. [cited by applicant]
Office Action dated Sep. 23, 2022 from the United States Patent and Trademark Office, for corresponding U.S. Appl. No. 17/839,799. [cited by applicant]
Final Office Action dated Mar. 13, 2023 from the United States Patent and Trademark Office, for corresponding U.S. Appl. No. 17/839,799. [cited by applicant]
Notice of Allowance dated Jun. 5, 2023 from the United States Patent and Trademark Office, for corresponding U.S. Appl. No. 17/839,799. [cited by applicant]
Office Action dated Mar. 21, 2024, from the United States Patent and Trademark Office for corresponding U.S. Appl. No. 18/457,667, filed Aug. 29, 2023. [cited by applicant]