Abstract: The invention relates to a method for selecting a set of functions (TR1, TR2, TR3) of a communications infrastructure (10), referred to as a network slice, for routing data relating to an application (App1, App2, App3 App4) installed in a user terminal (51, 53) connected to said infrastructure (10), which method is implemented by the terminal (51, 53) and comprises a step of transmitting, to a rule management entity (40), an identifier of at least one application in the terminal, a step of receiving, from the rule management entity (40), at least one rule relating to the network slice (TR1, TR2, TR3) associated with the identifier of the at least one application received, and a step of determining a network slice (TR1, TR2, TR3) based on the at least one rule obtained.
CLAIMS
1. A method for selecting a, so-called network slice, set (TR1, TR2, TR3) of
5 functions of a communications infrastructure (10), for the conveying of data
relating to at least one application (App1, App2, App3, App4, App5) installed on a user terminal (51, 53) attached to said infrastructure (10), implemented by the terminal (51, 53) and comprising:
- a step of sending, to a rules management entity (40, 60), a request message
10 comprising at least one application identifier,
- a step of receiving, from the rules management entity (40, 60), a response
message comprising at least one rule relating to the network slice (TR1, TR2,
TR3) associated with the at least one identifier,
- a step of selecting the network slice (TR1, TR2, TR3) as a function of the at
15 least one rule obtained.
2. The selection method, as claimed in claim 1, where the request message
comprises the identifiers of the applications (App1, App2, App3, App4, App5)
installed on the terminal (51, 53) at the moment of attachment of said terminal
20 (51, 53) to said infrastructure (10).
3. The selection method, as claimed in claim 2, where the request message is a
message relating to the attachment of the terminal (51, 53) to said infrastructure
(10).
25
4. The selection method, as claimed in claim 1, where the at least one identifier
furthermore comprises an item of information relating to an application version
(App1, App2, App3, App4, App5).
30 5. The selection method, as claimed in claim 1, where the at least one
WO 2018/220291
27
PCT/FR2018/000142
application identifier is determined by the terminal (51, 53).
6. A method for associating at least one rule relating to a, so-called network
slice, set (TR1, TR2, TR3) of functions of a communications infrastructure (10),
5 with an identifier of an application (App1, App2, App3, App4, App5) of a terminal
(51, 53) attached to said infrastructure (10), implemented in a rules management entity (40, 60), characterized in that it comprises:
- a step of receiving from the terminal (51, 53) a request message comprising at
least one application identifier (App1, App2, App3, App4, App5),
10 - a step of determining at least one rule relating to the network slice (TR1, TR2,
TR3) associated with the at least one identifier,
- an step of sending to the terminal (51, 53) a response message comprising
the at least one rule determined.
15 7. The association method, as claimed in claim 6, where a priority parameter is
associated with the at least one rule and transmitted to the terminal (51, 53).
8. The association method, as claimed in claim 6, where the rule associated
with the at least one identifier relates to a service class.
20
9. The association method, as claimed in claim 6, where a default rule is
determined and transmitted to the terminal (51, 53) in the case where the at
least one application identifier (App1, App2, App3, App4, App5) is not
associated with any rule.
25
10. The selection method, as claimed in claim 6, where the rules management
entity (40, 60) is implemented in an applications server (70).
11. A device (100) for selecting a, so-called network slice, set (TR1, TR2, TR3)
30 of functions of a communications infrastructure (10), for the conveying of data
WO 2018/220291
28
PCT/FR2018/000142
relating to at least one application (App1, App2, App3, App4, App5) of a user terminal (51, 53) attached to said infrastructure (10), comprising:
- a sender (110) able to send, to a rules management entity, a request message
comprising at least one application identifier,
5 - a receiver (120), able to receive, from the rules management entity, a
response message comprising at least one rule relating to the network slice associated with the at least one identifier,
- a selection module (101), able to select a network slice as a function of the at
least one rule obtained.
10
12. A device (200) for associating a rule relating to a, so-called network slice,
set (TR1, TR2, TR3) of functions of a communications infrastructure (10), with
an identifier of an application (App1, App2, App3, App4, App5) of a terminal (51,
53) attached to said infrastructure (10), implemented in a rules management
15 entity (40, 60), comprising:
- a receiver (220), able to receive from a terminal a request message
comprising at least one application identifier,
- a determination module (201), able to determine at least one rule relating to
the network slice associated with the at least one identifier,
20 - a sender (210), able to send to the terminal a response message comprising
the at least one rule determined.
13. A system for selecting a network slice comprising
- A terminal (51, 53) comprising a selection device (100) as claimed in
25 claim 11,
- A rules management entity (40, 60) comprising an association device
(200) as claimed in claim 12.
14. A computer program, characterized in that it comprises instructions for the
30 implementation of the steps of the selection method as claimed in claim 1, when
WO 2018/220291
29
PCT/FR2018/000142
this method is executed by a processor.
15. A recording medium readable by a selection device in accordance with claim 11, on which the program as claimed in claim 14 is recorded.
5
Dated this 12th day of December 2019
[MAHUA RAY]
[IN/PA-867]
OF REMFRY AND SAGAR
ATTORNEY FOR THE APPLICANT(S)
| # | Name | Date |
|---|---|---|
| 1 | 201947051568.pdf | 2019-12-12 |
| 2 | 201947051568-TRANSLATIOIN OF PRIOIRTY DOCUMENTS ETC. [12-12-2019(online)].pdf | 2019-12-12 |
| 3 | 201947051568-STATEMENT OF UNDERTAKING (FORM 3) [12-12-2019(online)].pdf | 2019-12-12 |
| 4 | 201947051568-FORM 1 [12-12-2019(online)].pdf | 2019-12-12 |
| 5 | 201947051568-DRAWINGS [12-12-2019(online)].pdf | 2019-12-12 |
| 6 | 201947051568-DECLARATION OF INVENTORSHIP (FORM 5) [12-12-2019(online)].pdf | 2019-12-12 |
| 7 | 201947051568-COMPLETE SPECIFICATION [12-12-2019(online)].pdf | 2019-12-12 |
| 8 | abstract 201947051568.jpg | 2019-12-16 |
| 9 | 201947051568-FORM-26 [17-12-2019(online)].pdf | 2019-12-17 |
| 10 | Correspondence by Agent_Power of Attorney_18-12-2019.pdf | 2019-12-18 |
| 11 | 201947051568-Certified Copy of Priority Document (MANDATORY) [20-01-2020(online)].pdf | 2020-01-20 |
| 12 | 201947051568-Priority Document_27-01-2020.pdf | 2020-01-27 |
| 13 | 201947051568-Correspondence_27-01-2020.pdf | 2020-01-27 |
| 14 | 201947051568-FORM 18 [29-04-2021(online)].pdf | 2021-04-29 |
| 15 | 201947051568-FER.pdf | 2022-02-16 |
| 16 | 201947051568-Proof of Right [23-03-2022(online)].pdf | 2022-03-23 |
| 17 | 201947051568-FORM 3 [23-03-2022(online)].pdf | 2022-03-23 |
| 18 | 201947051568-PETITION UNDER RULE 137 [11-08-2022(online)].pdf | 2022-08-11 |
| 19 | 201947051568-OTHERS [11-08-2022(online)].pdf | 2022-08-11 |
| 20 | 201947051568-Information under section 8(2) [11-08-2022(online)].pdf | 2022-08-11 |
| 21 | 201947051568-FORM 3 [11-08-2022(online)].pdf | 2022-08-11 |
| 22 | 201947051568-FER_SER_REPLY [11-08-2022(online)].pdf | 2022-08-11 |
| 23 | 201947051568-COMPLETE SPECIFICATION [11-08-2022(online)].pdf | 2022-08-11 |
| 24 | 201947051568-CLAIMS [11-08-2022(online)].pdf | 2022-08-11 |
| 25 | 201947051568-PatentCertificate30-04-2024.pdf | 2024-04-30 |
| 26 | 201947051568-IntimationOfGrant30-04-2024.pdf | 2024-04-30 |
| 1 | SearchHistoryE_15-02-2022.pdf |