SELECTION OF A NETWORK SLICE WITH RESPECT TO AN APPLICATION

Description

1. Domaine de l'invention

[0001] The invention application lies in the field of telecommunications infrastructure and network slice techniques (in English) network slices ). 2. Etat de la technique antérieure

[0002] The architecture of mobile telecommunications networks is standardized through a standardization group known as 3GPP. This is particularly true for so-called "2G", "3G" and "4G" mobile networks, whose different architectures are defined in technical specifications established by this organization.

[0003] Until the advent of the "4G" generation of mobile networks, currently being deployed in most countries, network architectures have generally relied on highly specific equipment dedicated to precise functionalities, whether at the access network or core network level, particularly regarding the transmission of packets to and from a mobile device. In network infrastructures deployed to date, a single set of functions is used regardless of the type of traffic. The various session flows are thus processed by the same set of functions (routing, addressing, data flow control, naming, etc.).

[0004] The lack of flexibility and scalability inherent in this type of conventional architecture has led to the consideration of adopting more flexible architectures for the next generation of mobile networks, known as "5G," in order to respond quickly to extremely diverse demands in terms of traffic and quality of service. It should be noted that 5G networks are intended to encompass both mobile and fixed networks. Consequently, the techniques involved in developing 5G networks apply to both fixed and mobile infrastructures.

[0005] Among the solutions considered, one of the most promising is based on a network slicing technique, mentioned in particular in the 3GPP TR 23.799 v2.0.0 technical report of December 2016.

[0006] The network slice concept is designed to create multiple network instances, also called "Network Slices" in English. figure 1 presents a simplified view of a communications infrastructure organization 10, according to previous techniques, comprising network slices TR1, TR2, TR3, each representing a mobile network that share functions (routing, addressing, data flow control, naming, etc.) implemented, for example, in data centers. Centers Terminal 50 is connected to two network slices, TR1 and TR2, while terminal 51 is connected to slice TR2 and terminal 53 to slice TR3. Slice TR1 provides access to data network 12, network slice TR2 provides access to network 22, and network slice TR3 provides access to network 32. In this example, the network slices provide access to distinct data networks, but they can also provide access to the same communication network. These network slices, which can be considered as separate mobile networks, are defined by the characteristics of the data flows passing through them. These flows share common features in terms of destination, routing, and security constraints, justifying joint management within a network slice.

[0007] Each of the slices is thus optimized for the needs of a particular type of service and / or a particular type of customer or terminal.

[0008] A terminal, particularly a mobile terminal, supports an ever-increasing number of applications offered by various stakeholders, including the network operator to which the terminal connects and application providers. The traffic generated by these various applications must be carried across the different network slices implemented in the communications infrastructure to which the terminal is connected. A network slice is composed of network functions and configurations designed to meet the requirements of the services, clients, or terminals associated with that slice. The network slices deployed by an operator are not all configured with the same routing characteristics, as the aim is to adapt the architecture and network slices to the needs of the specific use case associated with that slice. For example, a network slice implemented for IoT-related services (in English) Internet of Things This may require managing a large number of terminals but a relatively low throughput per terminal, for example, if it involves meter readings. A service offered to business customers will require advanced security and availability features. The goal is to activate, for a given network slice, only the essential functions for the use case corresponding to that slice. This network slice architecture aims to provide greater flexibility to the operator and to offer customers services that meet their needs by activating only the functions necessary for the required service.

[0009] Such a network slicing technique allows a telecommunications network operator to create "tailor-made" networks capable of providing optimized solutions for very diverse scenarios with very diverse constraints in terms of functionality and performance.

[0010] It is planned that a multitude of network slices can be run simultaneously within the same telecommunications network, in order to offer different services to different customers on the same network.

[0011] When a terminal connects to the telecommunications network, one or more network slices corresponding to the terminal or the service activated on the terminal must be selected. As mentioned above, a terminal has a large number of applications, each of which may require data routing parameters related to those specific services; therefore, network slices adapted to their needs must be selected.

[0012] The 3GPP TR 23.799 specification (version 2.0.0, December 2016) states that the network can provide the endpoint with rules allowing it to select a network slice based on the services it wants to use. This specification does not specify when or how these rules are generated and used by an endpoint to actually ensure that an application's data is routed over an appropriate network slice. The 3GPP TS 23.501 standard, Vol. SA WG2, No. V0.4.0, April 20, 2017, is a document that describes an NSSP provisioning architecture involving a mapping between application identifiers and suitable network slices to provide corresponding application services. Document WO 2017 / 063708 A1 discloses the receipt of an entire list of network slice identities at the endpoint level.

[0013] The present invention aims to remedy these drawbacks. 3. Exposé de l'invention

[0014] The invention improves the situation by means of methods, devices, computer programs, and computer-readable media as claimed in the attached independent claims. Preferred embodiments are covered by the dependent claims.

[0015] A network slice can be advantageously implemented to transport data for one or more applications, provided these applications share similar quality of service requirements (latency, throughput, priority). A network composed of multiple slices can thus carry a variety of data streams with different characteristics, while ensuring that each data type has a configuration and routing parameters tailored to the specific needs of the various data streams associated with the applications used.

[0016] The selection process advantageously allows for the selection of the network slice that meets the needs of the application whose data is streamed over the selected slice. The terminal, on which the application is implemented, transmits the identifier of the application for which a network slice must be selected to a rule management entity responsible for associating a rule with the application. When a new application is installed on the terminal, the terminal determines the identifier of this application and transmits it to the management entity so that it receives a rule allowing it to associate a network slice with this identifier. Upon receiving the rule, the terminal is able to determine the network slice, for example, by maintaining a table associating the rule with the network slice to be chosen.This selection process ensures that only the relevant rules are retrieved, i.e., those corresponding to applications installed on the terminal. Alternatively, if the management entity knows that the terminal can support a large number of rules, the rules management entity returns a set of rules to the terminal, not limited to the single rule corresponding to the received identifier. The transmitted rule could, for example, correspond to the S-NSSAI parameter. Single Network Slice Selection Assistance Information ), used by the terminal to determine the network slice corresponding to the application.

[0017] According to the previous technique, the need to structure a communication network into network slices was clearly identified. However, this previous technique did not offer a way to associate a network slice with application characteristics so that data flows from a terminal could be routed according to those characteristics, by selecting a network slice suited to those characteristics.

[0018] According to one aspect of the invention, in the selection process, the request message includes the identifiers of the applications installed on the terminal at the time the terminal was attached to said infrastructure.

[0019] A device joining the network may already have several applications installed. In this case, the device needs to obtain the set of rules corresponding to these different applications. Therefore, it is necessary for the device to obtain these rules when it joins the network. This allows the device to have all the rules immediately upon joining, resulting in faster application usage since the device does not have to request the rules management entity every time an application needs to be used. The protocol used to transmit the request message can be an infrastructure-attached protocol or an attachment-independent protocol such as a REST API. Applications Programming Interface - Representational State Transfer ) dedicated to the need to transmit the identifiers to a rules server.

[0020] According to another aspect of the invention, in the selection process, the request message is a message relating to the attachment of the terminal.

[0021] Retrieving rules during terminal attachment can also be implemented using the communication protocols used during attachment. For example, when the terminal connects to a mobile telecommunications network, the terminal can retrieve the rules, for example, from the data present in the PCO (in English). Protocol Configuration Option ) during the establishment of the PDN connection (in English Packet Data Network ) and if it is a fixed network, the terminal can obtain the rules in a DHCP message (in English Dynamic Host Configuration Protocol ) or PPP (in English Point-to-Point Protocol ) of connection to the fixed network.

[0022] According to another aspect of the invention, in the selection process, at least one application identifier further includes information relating to an application version.

[0023] Depending on the network architecture and network slice deployment options, application version information may be required to associate a rule. For example, one version of an application might be associated with a network slice, while a newer version, which incorporates, for instance, more security or routing performance settings, might be associated with a network slice that aligns with the advanced settings of the higher-performing version.

[0024] According to another aspect of the invention, at least one application identifier is determined by the terminal.

[0025] It is possible for an application to have a unique identifier that allows the authority rule management entity to unambiguously distinguish the application, or even the application version, based on this identifier. This is particularly true if the application is loaded from an application server accessible from a terminal connected to any type of communication infrastructure. In some cases, the application identifier is not sufficiently explicit for the management entity to use, and the terminal can determine a unique identifier for an application. Depending on the situation, it may, for example, add a suffix or prefix to an identifier that is not sufficiently explicit. The suffix or prefix could, for example, identify the application server used to load the application, the terminal's operating system, a terminal identifier, or a combination of these pieces of information.The determined identifier must be explicit to the management entity so that it can select a rule based on that identifier. Any added prefix or suffix must be interpreted by the management entity.

[0026] The different aspects of the selection process that have just been described can be implemented independently of each other or in combination with each other.

[0027] The invention also relates to a method of associating at least one rule relating to a set of functions of a communications infrastructure, called a network slice, with an application identifier of a terminal attached to said infrastructure, implemented in a rule management entity, characterized in that it comprises: a step of receiving from the terminal a request message including at least one application identifier, a step of determining at least one rule relating to the network slice associated with at least one identifier, a step of sending to the terminal a response message including at least one determined rule.

[0028] The association process is implemented by the rules management entity in its client-server relationship with the terminal requesting a rule for an application. To determine which rule to associate with an application identifier, for which it is requested by a terminal, the rules management entity may include an internal or external database in which the rules corresponding to the application identifiers are maintained. When attaching a terminal to the communications infrastructure, this association process can advantageously allow the identification of all network segments corresponding to the various applications, or even the various versions of applications, present on the terminal.

[0029] According to one aspect of the invention, in the association method, a priority parameter is associated with at least one rule and transmitted to the terminal.

[0030] Application data can be transmitted across multiple network segments. For example, depending on whether the device is connected to a visited network (roaming) or its home network, application data may be transmitted across different network segments. Alternatively, application data can be routed across separate segments based on factors such as availability or quality of service (QoS) criteria at a given time. It can be helpful for the management entity to transmit a priority indicator in addition to the rules. This allows the device to determine which rule to prioritize and, if that rule is unavailable, which alternative rule to consider.In the case of "roaming", the network slice with the highest priority, corresponding to a network slice of the parent network, cannot be selected and the terminal then opts for the second or one of the network slices with a lower priority, according to the terminal's selection algorithm.

[0031] According to another aspect of the invention, in the association method, the rule associated with at least one identifier relates to a service class.

[0032] A network slice can be advantageously implemented for applications requiring the same processing by an operator, particularly to meet quality of service criteria. Thus, real-time applications can be associated with one network slice, while applications with fewer constraints can be associated with another. A service class can therefore be determined from an application identifier, and the terminal will use the received service class information to select a suitable network slice, either by querying a server or from an internal database.

[0033] According to another aspect of the invention, in the association method, a default rule is determined and transmitted to the terminal in the case where at least one application identifier is not associated with any rule.

[0034] A large number of applications, or even application versions, are installed on an operator's customer terminals, making it difficult for the operator to associate an explicit rule with each application or application version. The management entity must be updated very regularly with new applications, and these applications must be analyzed to match them with a rule so that their data is routed according to the application's parameters and the operator's policies for the communication network segments. Therefore, it is advantageous to define explicit rules for the most widely used applications or application versions and to associate a default rule with less common or less strategic applications for the operator responsible for rule assignment.Thus, a limited number of rules will be used to manage the diversity of applications, and data from applications that are less important to the operator will be routed on a network slice associated with a default rule.

[0035] According to another aspect of the invention, in the association method, the rule management entity is implemented in an application server.

[0036] The rules management entity can be advantageously implemented on an application server. Indeed, when a device downloads a new application, it can also retrieve the rules corresponding to that downloaded application. This optimizes rule retrieval, as there is no need to request a separate server when an application is downloaded. Furthermore, it is beneficial to transmit, along with the application itself, the rule(s) enabling its use on a communications infrastructure. Given that communication network architectures are operator-specific, it may be necessary to identify the operator's network or the operator itself to provide the rules corresponding to the network or operator providing the device's connection, particularly if the application server is not operator-specific.

[0037] The different aspects of the association process that have just been described can be implemented independently of each other or in combination with each other.

[0038] The invention also relates to a device for selecting a set of functions of a communications infrastructure, called a network slice, for routing data relating to at least one application of a user terminal attached to said infrastructure, comprising: a sender capable of sending to a rule management entity, a request message including at least one application identifier, a receiver capable of receiving from the rule management entity, a response message including at least one rule relating to the network slice associated with at least one identifier, a selection module capable of selecting a network slice based on at least one rule obtained.

[0039] This device, capable of implementing in all its embodiments the selection process that has just been described, is intended to be implemented in a terminal.

[0040] The invention also relates to a device for associating a rule relating to a set of functions of a communications infrastructure, called a network slice, with an application identifier of a terminal attached to said infrastructure, implemented in a rule management entity, comprising: a receiver, capable of receiving from a terminal a request message including at least one application identifier, a determination module, capable of determining at least one rule relating to the network slice associated with at least one identifier, a sender, capable of sending to the terminal a response message including at least one determined rule.

[0041] This device, capable of implementing in all its modes of realization the association process which has just been described, is intended to be implemented in a rules management entity.

[0042] The invention also relates to a network slice selection system including a terminal comprising a selection device and a rules management entity comprising an association device.

[0043] The invention also relates to a computer program comprising instructions for implementing the steps of the selection process just described, when this program is executed by a processor.

[0044] The invention also relates to a computer program comprising instructions for implementing the steps of the association process just described, when this program is executed by a processor.

[0045] These programs can use any programming language, and be in the form of source code, object code, or code somewhere between source code and object code, such as in a partially compiled form, or in any other desirable form.

[0046] The invention also relates to a computer-readable information carrier, containing instructions for computer programs as mentioned above.

[0047] The information medium can be any entity or device capable of storing programs. For example, the medium can include a storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or a magnetic recording means, for example a floppy disk or a hard disk drive.

[0048] On the other hand, the information medium can be a transmissible medium such as an electrical or optical signal, which can be transmitted via an electrical or optical cable, by radio, or by other means. The program according to the invention can, in particular, be uploaded to a network such as the Internet.

[0049] Alternatively, the information carrier may be an integrated circuit in which the program is incorporated, the circuit being adapted to execute or to be used in the execution of the process in question. 4. Présentation des figures

[0050] Other advantages and features of the invention will become more apparent upon reading the following description of a particular embodiment of the invention, given by way of simple illustrative and non-limiting example, and the accompanying drawings, among which: there figure 1 presents a simplified view of the organization of a communications infrastructure according to the previous technique, the figure 2 presents a communications infrastructure according to one aspect of the invention, the figure 3 presents an overview of the process for selecting a network slice, according to a first embodiment of the invention, the figure 4 presents an overview of the method for selecting a network slice according to a second embodiment of the invention, the figure 5 presents an example of the structure of a network slice selection device, according to one aspect of the invention, the figure 6 presents an example of the structure of a device for associating a rule, according to one aspect of the invention, 5. Description détaillée d'au moins un mode de réalisation de l'invention

[0051] The following description presents examples of several embodiments of the invention in a mobile communications infrastructure, but the invention can also be implemented in a fixed network infrastructure.

[0052] We refer first to the figure 2 which presents a communications infrastructure according to one aspect of the invention.

[0053] Terminal 51 supports applications App1, App2, and App3, while terminal 53 supports applications App2 and App4. In this example, App1 and App2 are considered audio and video applications, respectively, while App3 and App4 are non-real-time applications, such as those used for text transfer. The communications infrastructure operator structures its infrastructure by deploying three network slices, TR1, TR2, and TR3, used to route audio, video, and non-real-time data, respectively. These three slices, TR1, TR2, and TR3, are implemented within the same communications infrastructure and instantiated using shared data center software resources, but offer routing capacities and performance tailored to the data flows of their respective applications.In particular, the TR1 network slice offers limited routing capacity but with very low latency. The TR2 network slice requires significant transport capacity to handle video data streams as well as fairly low latency. This slice also has temporary storage capabilities (in English, ". buffering Finally, the last TR3 segment is characterized by fairly significant capacity and relatively high latency. This infrastructure can be supplemented by other network segments not shown in the figure, depending on the operator's needs. In particular, a default network segment could be considered for unidentified application flows or those not requiring specific routing.

[0054] The TR1 and TR2 network slices provide access to a service platform hosted in a communication network 22 included in the operator's communication infrastructure 10, while the TR3 slice provides access to a data network 32 not included in the infrastructure 10. This data network can, for example, be a service provider's network or a corporate network.

[0055] The communications infrastructure also includes a rules server 40 whose role is to provide network slice association rules to terminal applications.

[0056] It should be noted that network slices, depending on the alternative configuration, can include only access network functions, only core network functions, or both access and core network functions. The selection process can indeed be implemented for any type of network slice considered.

[0057] In relation to the figure 3 , We present an overview of the process for selecting a network slice, according to a first embodiment of the invention.

[0058] Terminal 51, in a step not shown in the figure, attaches to the network according to a procedure known and specified in prior art, notably by the 3GPP organization (in English Third Generation Partnership Project ) if terminal 51 connects to a mobile network or the BBF organization (in English " BroadBand Forum " if the terminal connects to a fixed network.

[0059] During an E1 step, either during the attachment procedure or, depending on an option, once the terminal has attached to the communications infrastructure, terminal 51 sends a request message (M1) to the Rule Server 40. This message includes the identifiers of the applications already installed on terminal 51. The message can be a specific message or a message related to the attachment of terminal 51, particularly if the Rule Server 40 is co-located with another server requested by terminal 51 to attach to the communications infrastructure, for example, an AAA server. Authentication Authorization Accounting ) or a DHCP server (in English Dynamic Host Configuration Protocol The protocol used to transport the message could be, for example, the HTTP protocol (in English). HyperText Transfer Protocol ). It should be noted that terminal 51 can transmit all identifiers in a single message or, alternatively, send one identifier per message.

[0060] In one variant, terminal 51 can transmit a message to the rule server 40 that includes not only the application but also its version. In this case, it is possible to associate a suitable network slice corresponding not only to the application but also to its version. A newer version of an application can thus benefit from more efficient network slice routing parameters. Furthermore, the prospect of offering network slices that are compatible with application versions can be an incentive for users to adopt newer application versions, thereby reducing the complexity of managing different application versions.

[0061] Several options exist for informing the terminal about the identity and / or address of the rule server to contact to obtain the rules. In the case where the terminal has a SIM card (in English Subscriber Identity Module ), the information can be configured on this card. Alternatively, the terminal can obtain the information via a protocol such as OMA-DM (in English Open Mobile Alliance - Device Management ) or DHCP. An alternative is to obtain the rule server information from a command plan message, for example, when attaching the terminal to an access network. Alternatively, the rule server information can be inferred from part of the application identifier. For example, the rule server can be reached at slice.com.xample for rules applicable to applications whose identifiers begin with com.example.

[0062] During step F1, upon receiving the request message M1 from terminal 51, the rule server 40 determines, during step E20, the rules corresponding to the received application identifiers. To accomplish this task, the rule server 40 can use an internal database or one located outside the rule server. Depending on the option chosen, it can query an administration server to obtain the rules.

[0063] During step E2, the rule server 40 transmits the rules to terminal 51 in a response message M2. The rule server can choose to transmit one rule per message or to transmit all the rules in a single message.

[0064] Terminal 51 receives the response message M2 in step F2 and, based on the received rules, determines in step E21 the network slices associated with the various installed applications. Terminal 51 can, for example, maintain a table associating each application with a network slice and refer to it when the application is used to stream data related to that application. Alternatively, it can add network slice information to each application's software so that the network slice is directly identified when the application is launched. It should be noted that the determination of network slices is not linked to the application's usage and can be performed before the application is actually activated.

[0065] During step E3, on terminal 51, an application is activated, for example, following an action by the terminal user. The network slice TR2 was determined for this application during step E21. In this example, it is assumed that terminal 51 has not yet associated any applications with the network slice TR2. Indeed, no application activated on terminal 51 up to that point required TR2 slice selection. Terminal 51 transmits an M3 attachment message to the network slice TR2 using the previous technique, notably described in the 3GPP TS 23.502 specification (version 0.3.0 of March 2017), using in particular the S-NSSAI parameter. Single- Network Slice Selection Assistance Information ) identifying the network slice TR2.

[0066] If the attachment procedure is successful, in accordance with the authentication procedures in particular, a piece of equipment from the TR2 tranche, for example a mobile gateway or a BNG type device (in English Broadband Network Gateway ) receives the M3 message during an F3 step and transmits a connection acknowledgment M4 message to terminal 51 during an E4 step and from that moment on, when terminal 51 receives the M4 message during an F4 step, the application data can be effectively routed on the TR2 slice.

[0067] During step E5, terminal 51 requests a new application from application server 70. Terminal 51 therefore transmits an application request message (M5) using the HTTP protocol. Server 70 can be either a public application server or a server belonging to the operator responsible for the communications infrastructure where the network slices are deployed. Upon receiving the M5 message during step F5, and if the application server agrees to send the new application requested by terminal 51, it transmits the requested application in an M6 message to terminal 51 during step E6. Upon receiving the M6 ​​message during step F6, terminal 51 then has a new application for which no network slice is selected.

[0068] It then queries the rule server 40 during step E7 by transmitting a message M7 containing the identifier of the application loaded during steps E5, F5, E6, and F6. The application identifier may have been transmitted by the application server 40, particularly if it is a public application with an unambiguous identifier, or the terminal may have defined its own identifier using a technique that the rule server can understand, typically by adding an identifier of the terminal or the terminal's operating system to an application identifier, thus making it unambiguous and usable by the rule server. After receiving the request message M7 during step F7, the rule server 40 associates a rule with the identifier received during step E22 and transmits it in a message M8 to the terminal 51 during step E8.

[0069] Terminal 51, once it receives the rule in message M8 during step F8, determines a network slice for this application during step E23 based on the rule received in message M8. It is assumed here that the network slice TR2 is determined for this application, which is enabled on the terminal, and terminal 51 does not need to attach to it again since it already did so during steps E3, F3, E4, and F4.

[0070] Terminal 51 can store the received rule for the application so that it avoids having to request the rule from the rule server again if it needs to associate a rule with the application, which may have been uninstalled or for which it has lost the original rule. This storage step prevents overloading the network with rule request and reception messages and avoids repeated requests to the management entity. Storing the obtained rule also allows for faster application use since the step of retrieving the rule from the management entity is no longer necessary. Alternatively, this storage can prevent the terminal from requesting the rule server altogether, even if it is for a different application.If the applications have standardized identifiers, the terminal could deduce the rule to apply to a second application from a first rule obtained for a first application. For example, if the first application is App1.tpsreel.com and it retrieved a rule A, it could reuse this rule for all applications of the type %.tpsreel.com, where % takes any value.

[0071] Terminal 53 also loads a new application, which may be identical or different from an application loaded by terminal 51, during steps E9, F9 and E10, F10 in accordance with the sequence of steps E5, F5, E6, F6 for terminal 51.

[0072] Terminal 53, once the application is received in message M10 during step F10, requests a rule from the rule server 40 during step E11 to associate a network slice with that application by sending the application's identifier in a request message M11. The rule server 40 receives the M11 message during step F11. During step E24, the server 40 associates a rule determining a default slice because the identifier transmitted by terminal 53 does not correspond to any specific slice, or because the application data does not require, according to the entity in charge of the rules, specific processing applied to a particular network slice. The server transmits this rule during step E12 in a message M12. The terminal receives the response message M12 during step F12.Terminal 53 selects a default TR1 slice during step E25 when it receives the rule from server 40 and connects to it upon application activation if it is not already connected. This connection is established during steps E13, F13, E14, and F14 according to the descriptions of steps E3, F3, E4, and F4, except that the network slice differs.

[0073] We now refer to the figure 4 which presents an overview of the method for selecting a network slice according to a second embodiment of the invention. This second embodiment differs from the first embodiment in that an application server itself contacts an authority server to obtain a rule relating to an application and then transmits the application and the associated rule to the terminal that wishes to install the application.

[0074] Terminal 51 transmits a request message M'1 to the application server 70 during step E'1 to load a new application. The application server 70 is also a rules server but obtains the rules from an authority server specific to the network operator to which terminal 51 is connected. Upon receiving the request message M'1 during step F'1, server 70 associates the rule with the application requested by terminal 51 by querying the rules server 40. If the application server is not operator-specific, server 70 identifies the rules server 40 to query, depending on one option, using the application identifier transmitted by terminal 51, if the identifier was established by the terminal by adding an operator prefix or suffix, for example. Alternatively, server 70 identifies server 40 using the IP address. Internet Protocol ) used by terminal 51 to transmit message M'1 or, alternatively, by configuring the rule server to a parameter of terminal 51 (IMEI code (in English) International Mobile Equipment Identity ), IMSI code (in English International Mobile Subscriber Identity In step E'2, server 70 queries the authority server 40 by transmitting a message M'2 to obtain the rule(s) associated with the application requested by terminal 51. Upon receiving message M'2 in step F'2, the authority server 40 transmits several rules, each with a priority parameter specific to the rule, in a message M'3 to the application server 70 in step E'3. The rule server 70 receives message M'3 in step F'3.

[0075] The rule server 70 transmits the application, along with the received rules and associated priority parameters, to terminal 51 during step E'4 in a response message M'4. Upon receiving this message M'4 during step F'4, terminal 51 determines the network slice to use for the received application during step E'21. Since terminal 51 is attached to its "home" network, it considers the rule with the highest priority to determine the network slice corresponding to the application. Terminal 51 then attaches during steps E'5, F'5, E'6, and F'6, which are comparable to steps E3, F3, E4, and F4 of the... figure 3 .

[0076] Terminal 51 requests a new application from server 70 during step E'7 by transmitting message M'7. This message is identical to message M'1 except for the application, which differs. Server 70 receives message M'7 during step F'7 and associates one or more rules with the application requested by terminal 51. Server 70 has already associated a rule with this application during a previous request and has stored this rule. Therefore, it associates the requested application with a stored rule during step E'22, without querying an authority server, and transmits the application and the rule to terminal 51 in message M'8 during step E'8. Terminal 51 receives message M'8 during step F'8 and selects network slice TR2 from this rule. It does not connect to this slice when launching the application because it has already connected to it previously.

[0077] Terminal 53 is considered to be connected to a network that it visits and is therefore in a roaming state. During step E'11, terminal 53 requests an application from the application server 70 by transmitting a message M'11. The server receives the request message M'11 during step F'11. During step E'12, the server 70 initiates the association phase by sending a message M'12 to the rule server 60 corresponding to terminal 53 or to the operator providing the connection between terminal 53 and the communications infrastructure. The server 60 receives the message M'12 during step F'12 and, during step E'13, transmits the rules associated with the identifier of the application requested by terminal 53 in a message M'13 to the application server 70. Priority parameters are also transmitted.During step F'13, server 70 receives message M'13, which contains the rules and priority parameters, and stores this information related to the application identifier for which it requested these rules. This information is valid because it was transmitted by the authority server 60. Server 70 then transmits these rules to terminal 53 either along with the application or in a separate message M'14, distinct from the message containing the application during step E'14. Application server 70 stores the rules based on the rule server that transmitted them, ensuring that invalid or non-compliant rules are not sent to a terminal requesting the same application but from a different communication infrastructure. During step F'14, terminal 53 receives message M'14, which contains the rules and, optionally, the application.During step E'25, terminal 53 selects a rule based on the retrieved rules, with the priority parameter corresponding to a roaming situation because terminal 53 is on a visited network. In step E'25, terminal 53 determines the network slice TR1 corresponding to the lowest priority rule among the retrieved rules. When the application is activated, terminal 53 then connects to network slice TR1 during steps E'15, F'15, E'16, and F'16, which are equivalent to steps E'5, F'5, E'6, and F'6, except that the terminal connects to a visited network.

[0078] In another embodiment, the selection of a rule by a terminal can be performed in two steps. In the two previous embodiments, a terminal obtains a rule from a rule server or an application server that has previously obtained a rule from an authority server. In a third embodiment, a rule server transmits to a terminal information about a service class corresponding to the received application identifier. Upon receiving the information about the service class, the terminal associates a slice identifier with that service class, either by querying a server or by using an internal database that associates the service class with a network slice. If it contacts a server to associate the service class with a slice, this can be the same server that was queried to obtain the service class or a different server.The service class information obtained corresponds to a rule relating to the required network slice, but the slice selection differs from the two previous embodiments. This embodiment is particularly suited to a context where an operator has structured its communication network by deploying network slices specifically designed to carry data based on their relative service class characteristics, as defined for example, and not only, in the Diffserv approach. Differentiated Services).

[0079] In relation to the figure 5 , We present an example of the structure of a network slice selection device, according to one aspect of the invention.

[0080] Device 100 for selecting a set of functions of a communications infrastructure, called a network slice, implements the selection process, various modes of implementation of which have just been described.

[0081] Such a device can be implemented in a terminal. The terminal can be a mobile terminal or a fixed terminal.

[0082] For example, the device 100 comprises a processing unit 106, equipped, for example, with a microprocessor µP, and controlled by a computer program 105, stored in a memory 107 and implementing the selection process according to the invention. At initialization, the code instructions of the computer program 105 are, for example, loaded into a RAM memory before being executed by the processor of the processing unit 106.

[0083] Such a device 100 includes: a transmitter 110 capable of transmitting to a rule management entity, an identifier Ident of at least one application on the terminal, a receiver 120 capable of receiving from the rule management entity, at least one rule Reg relating to the network slice associated with the identifier of at least one application received, a determination module 101, capable of determining a network slice based on the at least one rule Reg obtained.

[0084] In relation to the figure 6 , We present an example of the structure of a device for associating a rule, according to one aspect of the invention.

[0085] Device 200 for associating a rule relating to a set of functions of a communications infrastructure, called a network slice, implements the selection process, various modes of implementation of which have just been described.

[0086] Such a 200 device can be implemented in a terminal which can be a mobile terminal or a fixed terminal.

[0087] For example, the device 200 comprises a processing unit 206, equipped, for example, with a microprocessor µP, and controlled by a computer program 205, stored in a memory 207 and implementing the selection process according to the invention. At initialization, the code instructions of the computer program 205 are, for example, loaded into a RAM memory before being executed by the processor of the processing unit 206.

[0088] Such a 200-unit system includes: a receiver 220, capable of receiving from a terminal an identifier Ident of at least one application of a terminal an association module 201, capable of associating at least one rule Reg relating to the identifier of at least one application received, a transmitter 220, capable of transmitting to the terminal at least one associated rule Reg.

[0089] The modules described in relation to the figure 5 and the figure 6 They can be hardware or software modules.

[0090] The examples of the invention presented above are only a few of the possible embodiments. The method for selecting a network slice and the method for associating a rule with a set of functions within a communication infrastructure improve the quality of customer experience. It is indeed possible to match a network slice to the specific characteristics of a group of applications that share common features and require identical or similar processing. Thus, a communications infrastructure operator can implement distinct mobile networks, here identified as network slices, within the same infrastructure to carry data flows with identical characteristics.This structuring of the communication infrastructure can be more or less granular depending on whether the operator considers an application version, a single application, or a set of applications, taking into account, for example, a service class. As another example, an operator can also associate network segments based on the service provider offering the application. For instance, depending on whether the application is provided by provider A or B, or by the operator itself, it is possible to associate the application's data with a segment that implements varying levels of service quality guarantees.

Claims

1. Method for selecting a set (TR1, TR2, TR3) of functions of a communications infrastructure (10), referred to as a network slice, 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 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 application identifier, - a step of selecting the network slice (TR1, TR2, TR3) as a function of the at least one rule obtained, - a step of sending an attachment message to the selected network slice using a parameter S-NSSAI (Single-Network Slice Selection Assistance Information) identifying said selected slice.

2. Selection method according to Claim 1, wherein 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 (51, 53) to said infrastructure (10).

3. Selection method according to Claim 2, wherein the request message is a message relating to the attachment of the terminal (51, 53) to said infrastructure (10).

4. Selection method according to Claim 1, wherein the at least one identifier furthermore comprises an item of information relating to an application (App1, App2, App3, App4, App5) version.

5. Selection method according to Claim 1, wherein the at least one application identifier is determined by the terminal (51, 53).

6. Method for associating at least one rule relating to a set (TR1, TR2, TR3) of functions of a communications infrastructure (10), referred to as a network slice, 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 (App1, App2, App3, App4, App5) identifier, - a step of determining at least one rule relating to the network slice (TR1, TR2, TR3) associated with the at least one application identifier, - a step of sending to the terminal (51, 53) a response message comprising the at least one rule determined, said rule being used by the terminal to select the network slice and send an attachment message to the slice using a parameter S-NSSAI (Single-Network Slice Selection Assistance Information) identifying said selected slice.

7. Association method according to Claim 6, wherein a priority parameter is associated with the at least one rule and transmitted to the terminal (51, 53).

8. Association method according to Claim 6, wherein the rule associated with the at least one identifier determined relates to a service class.

9. Association method according to Claim 6, wherein a default rule is determined and transmitted to the terminal (51, 53) in the case where the at least one application (App1, App2, App3, App4, App5) identifier determined is not associated with any rule.

10. Association method according to Claim 6, wherein the rules management entity (40, 60) is implemented in an application server (70).

11. Device (100) for selecting a set (TR1, TR2, TR3) of functions of a communications infrastructure (10), referred to as a network slice, for the conveying of data relating to at least one application (App1, App2, App3, App4, App5) of a user terminal (51, 53) attached to said infrastructure (10), said device (100) being implemented in the terminal (51, 53) comprising: - a sender (110) able to send, to a rules management entity, a request message comprising at least one application identifier, - 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 application identifier - a selection module (101), able to select a network slice as a function of the at least one rule obtained, - the sender also being able to send an attachment message to the selected network slice using a parameter S-NSSAI (Single-Network Slice Selection Assistance Information) identifying said selected slice.

12. Device (200) for associating a rule relating to a set (TR1, TR2, TR3) of functions of a communications infrastructure (10), referred to as a network slice, 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), 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 application identifier, - a sender (210) able to send, to the terminal, a response message comprising the at least one rule determined, said rule being used by the terminal to select the network slice and send an attachment message to the slice using a parameter S-NSSAI (Single-Network Slice Selection Assistance Information) identifying said selected slice.

13. Terminal comprising a selection device according to Claim 11.

14. System for selecting a network slice comprising - A terminal (51, 53) according to Claim 13, - A rules management entity (40, 60) comprising an association device (200) according to Claim 12.

15. Computer program, characterized in that it comprises instructions for implementing the steps of the selection method according to Claim 1, when this method is executed by a processor.

16. Recording medium able to be read by a selection device according to Claim 11 and on which the program according to Claim 15 is recorded.