Title of the invention: Method for configuring user equipment, user equipment, and rule management entity

Prior technique

The present invention is in the field of telecommunications.

[0002] It relates more particularly to telecommunications network architectures implementing a network slicing technique, more commonly known as “network slicing”.

The invention applies in a privileged way to mobile telecommunications networks.

[0004] The architecture of mobile telecommunications networks currently deployed or being deployed is defined by the standardization group known as 3GPP (Third Generation Partnership Project). This is particularly the case for so-called second generation (“2G or GSM”), third generation (“3G”) and fourth generation (“4G”) mobile networks.

[0005] Until the fourth generation, the network architectures defined by the 3GPP group are most often based on specific equipment, dedicated to specific functionalities, whether at the level of the access network or the core network, in particular with regard to the transmission of packets from or to a mobile terminal.

[0006] The lack of flexibility and scalability inherent in this type of architecture has led the 3GPP group to consider adopting more flexible architectures for the next generation of so-called "5G" mobile networks, in order to be able to respond quickly extremely diverse demands in terms of traffic and/or quality of service envisaged by 5G networks. It should be noted that 5G networks are intended to concern both mobile networks and fixed networks.

[0007] Among the solutions envisaged, one of the most promising solutions is based on a network slicing technique. This technique is described in particular in the technical specification 3GPP TS 23.501 V15.7.0, September 2019. It allows the operator of a network to create tailor-made and independent end-to-end logical networks for its customers, from of the same physical network infrastructure, capable of providing optimized solutions for various scenarios corresponding to various constraints in terms of functionalities, performance and quality of service.

[0008] More specifically, the concept of network slices makes it possible to create several network instances also called “network slices”. A network slice is made up of network functions, hardware resources (for example storage and calculation) and configurations making it possible to satisfy the requirements linked to the services, clients and/or terminals attached to this slice.

By way of illustration, FIG. 1 represents a simplified view of a communications infrastructure INF comprising network slices SL1, SL2 and SL3 each representing a mobile network, the network slices SL1, SL2 and SL3 sharing functions implemented in data centers, such as for example routing, addressing, data flow control, naming, etc. functions. In the example of Figure 1, network slices SL1, SL2 and SL3 provide access to three separate data networks DN1, DN2 and DN3. Note however that network slices can provide access to the same data network. Each network slice can be related to a separate mobile network, and is determined by the characteristics of the data flows passing through this network slice, which have common points in terms, for example, of destination, routing, and security constraints, justifying common management within the same slice network. Each of the slices is thus optimized for the needs of a type of service and/or of a type of customer and/or of terminals. In the example illustrated in FIG. 1, the terminal T1 is connected to the network slices SL1 and SL2, the terminal T2 is connected to the slice SL2, and the terminal T3 is connected to the slice SL3. Each of the slices is thus optimized for the needs of a type of service and/or of a type of customer and/or of terminals. In the example illustrated in FIG. 1, the terminal T1 is connected to the network slices SL1 and SL2, the terminal T2 is connected to the slice SL2, and the terminal T3 is connected to the slice SL3. Each of the slices is thus optimized for the needs of a type of service and/or of a type of customer and/or of terminals. In the example illustrated in FIG. 1, the terminal T1 is connected to the network slices SL1 and SL2, the terminal T2 is connected to the slice SL2, and the terminal T3 is connected to the slice SL3.

[0010] Mobile network user terminals now also support an ever-increasing number of applications offered by various players in the world of telecommunications (network operators, service providers, terminal manufacturers, etc.) Each of these applications may have specific needs with regard to the routing of the data attached to it (in other words, whether it sends or receives). These data are conveyed on sections of the network after which the terminal is registered or associated, via for example a USIM module (Universal Subscriber Identity Module) embedded in the terminal. In a known manner, a USIM module designates an application stored in a UICC card (Universal Integrated Circuit Card), also commonly called a SIM card,

[0011] It is therefore recommended to select, to convey the data transmitted and received by each application, a section of the network adapted to its needs. Technical specification 3GPP TS 23.501 V15.7.0, September 2019, indicates that the network can provide the terminal with rules allowing it to select a slice of a network according to the services that it wants to use. However, this technical specification considers a terminal equipped with a single USIM card enabling it to register with a single network. Thus, the rules provided to the terminal implicitly relate to the slices of a single network with which the terminal can register via its USIM card.

[0012] However, some terminals are configured to receive two USIM cards (we speak of a “dual SIM” terminal). These two USIM cards allow them to benefit simultaneously or not from connectivity offered for example by two distinct network infrastructures managed by different operators, or by the same network infrastructure but according to two different offers, for example a "professional offer" and a “personal offer”, each offer being able to be associated with specific services offered by the operator of the network infrastructure. In the current state of the art, the user of a "dual SIM" terminal can, if his terminal allows it, manually configure in his terminal which USIM card he wishes to use according to the type of traffic transmitted and received by the terminal (voice, data or SMS (Short Message Service) messages). From then on, all voice-type traffic sent or received by the terminal uses the USIM card manually configured by the user for voice-type traffic, all data-type traffic sent or received by the terminal uses the USIM card manually configured by the user for data type traffic, all SMS type traffic transmitted or received by the terminal uses the USIM card manually configured by the user for SMS type traffic, and this, all applications installed on the terminal combined .

[0013] The 3GPP technical specification TS 23.501 does not mention how to manage the use of this type of “dual SIM”, or more generally “multi SIM” terminals in combination with a network slicing technique.

Disclosure of Invention

[0014] The invention overcomes this drawback in particular by proposing a method for configuring user equipment intended to be used by a user to whom is allocated a plurality of identifiers, each uniquely identifying said user on at least one network of communications, this method being implemented by the user equipment and comprising, for at least one application:

- a step of obtaining at least one rule associating with at least one stream of said application, at least one slice of said at least one communications network for routing data relating to said at least one stream and information linking said slice to an identifier among said plurality of identifiers of the user; and

- a step of configuring the user equipment with said at least one rule so that it executes said at least one rule when accessing said application.

Correlatively, the invention also relates to user equipment intended to be used by a user to whom is allocated a plurality of identifiers each uniquely identifying the user on at least one communications network, this user equipment comprising:

- an obtaining module, configured to obtain at least one rule associating with at least one flow of an application, at least one slice of said at least one communications network for routing data relating to said at least one flow and information linking said slice to an identifier among said plurality of identifiers of the user; and

- an execution module, configured to execute said at least one rule during access to the application.

[0016] By application, we mean here any type of program or software, intended to be installed on equipment to perform a task, or a set of elementary tasks which is executed using the operating system and the hardware resources. equipment. It can be, for example, an electronic game, a web browser, a multimedia player, an e-commerce application, the transmission of health data, etc. It should be noted that the invention applies just as well when the application is installed on the user equipment or on another equipment accessible by the user equipment (for example on a remote server, etc.).

[0017] No limitation is attached to the nature of the user equipment (or UE) to which the invention applies. It can be a terminal such as a smart phone (or "smartphone"), a laptop computer, a digital tablet, a connected object, but also a router, etc. Furthermore, the different modules of the user equipment can be hosted by different physical entities.

It is noted that the invention is described, with regard to the technical problem mentioned above, with reference to a “dual SIM” or “multi SIM” user equipment; however, it applies more generally to any user equipment intended to be used by a user to whom is allocated a plurality of distinct identifiers, each identifying him uniquely on at least one communications network. Such identifiers are for example identifiers of the IMSI (International Mobile Subscriber Identifier) ​​type used in particular in 4G networks or of the SUPI (SUbscription Permanent Identifier) ​​type used in particular in 5G networks, or even of the MAC (Medium Access Control) for non-3GPP networks such as WLAN (Wireless Access Network). These are identifiers that are allocated to the user independently of each other and permanently: in other words, they are invariant as long as the user has a subscription or a subscription with a network. These identifiers can be stored respectively, in a particular embodiment, in a plurality of on-board USIM modules and/or network cards in the user equipment.

Thus, in a particular embodiment, the invention also relates to user equipment configured to receive a plurality of USIM modules and/or network cards, each card or each module being associated with an identifier distinct from the plurality of identifiers allocated to the user.

This plurality of identifiers identify the user and allow him to register via his user equipment with a plurality of distinct networks (for example with public land mobile networks or PLMN (for Public Land Mobile Network) different ), or with the same network but benefiting from independent offers or subscriptions, each associated) with a different user identifier (for example a "professional subscription" and a "personal subscription" offered by the same network operator and based on the same network infrastructure). From the network point of view, these identifiers are managed as

if they were allocated respectively to as many different users.

The invention proposes to configure (for example, automatically) a user's equipment having a plurality of identifiers allowing the user equipment to access one or more networks, with one or more rules allocating one or more slices of this or these networks to at least one flow of an application. Each rule preferably includes an identifier of the application to which it relates. It is noted that the rules can associate with all the streams of the same application the same slices of the network or networks to which the user equipment can access via the plurality of identifiers allocated to the user. However, the invention also offers, if necessary, an additional granularity making it possible to distinguish the network slices to be used according to different types of streams that can be sent or received by the same application, or even individually of each stream that can be sent or received by the same application. Different types of streams or different streams can correspond, for example, to streams transporting data of different natures (audio, video, text data, etc.), to streams having different destination addresses, a different remote IP address, a port different remote, etc. For example, the flow differentiation criteria listed in table 5.2.1 of the 3GPP TS 24.526 specification entitled “User Equipment (UE) policies for 5G System (5GS); Stage 3”, vlô.lO, September 2019 can be considered.

[0022] In other words, the rules transmitted to the user equipment for its configuration take account of the fact that the latter benefits from multiple connectivity thanks to the multiple identifiers which are allocated to the user. They are advantageously established taking into account the characteristics of the network slices associated with the different network(s) with which the user equipment can register and the services associated with these network slices taking into account the specificities of the considered applications. It should be noted that the rules provided to the user equipment can relate to applications which are not installed on the latter or which will not be executed by the latter; in this case, they are not taken into account by the latter,

[0023] In a variant embodiment, the rules obtained by the user equipment relate to applications installed on it.

[0024] For example, the user equipment can provide an entity in charge of establishing the rules with the identifiers of the applications that it hosts, when registering with the network or networks on which the user has identifiers, or at any other time (eg when installing a new application).

The information associated explicitly in each rule with each network slice in accordance with the invention advantageously makes it possible to uniquely designate the network to which the slice is attached if the identifiers allocated to the user correspond to different networks, or if the slices are attached to the same network, the identifier that the user equipment must use to access this network slice.

In a particular embodiment, this information comprises for a slice of a communications network:

- said identifier among said plurality of identifiers of the user;

- an identifier of a module of said terminal containing said identifier; Where

- an identifier of the communication network for which said identifier is allocated to said user.

In other words, the information associated with each network slice associated with an application flow contains either a direct reference to the identifier of the user to be used to communicate on this network slice, or a indirect reference to this identifier through, for example, the module which contains this identifier or else the network to which it is attached (if the identifiers allocated to the user typically identify him on different networks). In the example of a multi-SIM user equipment, this information thus makes it possible to designate the SIM to which

corresponds to the slice in question and that the user equipment must use for the flow of the application which is associated with this slice.

[0028] It follows from the invention that a multi-SIM user equipment can thus receive association rules between applications (or even application flows) and network slices for each of the USIM modules and/or network cards that he embarks. The invention thus makes it possible to associate for an application of the user equipment, or even for different streams of the same application of the user equipment, a USIM module and a section of the corresponding network. The flows of the same application can therefore be distributed over different slices of different networks according to the specificity of each of these flows: we are no longer limited to a static distribution according to a type of traffic exchanged with the equipment. user (voice, data, SMS).

In a particular embodiment, the rules obtained by the user equipment are determined by a rules management entity. This rules management entity can be located in a mediation gateway between the different networks to which the user is subscribed or if the user is subscribed to a single network via different subscriptions, in this network. As a variant, it is not necessarily associated with the networks and may be an entity independent of the latter.

Thus, according to another aspect, the invention also relates to a rule management method, implemented by a rule management entity, this method comprising, for at least one user to whom a plurality of identifiers is allocated respectively identifying said user uniquely on at least one communications network:

- a step of determining at least one rule associating with at least one stream of an application, at least one slice of said at least one communications network for routing data relating to said at least one stream and information linking said slice to an identifier among said plurality of identifiers of said user; and

- A step of transmitting said at least one rule to the user's user equipment.

[0031] Correlatively, the invention also relates to a rule management entity comprising:

- a determination module, configured to determine at least one rule associating with at least one flow of an application, at least one slice of at least one communications network for routing data relating to said at least one flow and information linking said slice to an identifier among a plurality of identifiers allocated to said user and respectively identifying said user uniquely on said at least one communications network; and

- a transmission module configured to transmit said at least one rule to a user equipment of the user.

It is noted that depending on the context considered, the transmission of the rule to the user equipment can be done directly or indirectly via one or more entities of the networks to which the user equipment is subscribed.

For example, in a particular embodiment, said at least one rule is obtained during an association (or a registration or an attachment) of the user equipment to said at least one communications network.

[0034] In this way, the user equipment automatically and without delay has rules to apply to access the applications that it hosts or to which it is likely to access. This is done transparently for the user of the user equipment.

As a variant, the rules can be configured manually in the user equipment, for example by the user of the user equipment, via a user interface provided for this purpose. Such an interface is for example a settings menu available on the user equipment.

According to yet another variant, the rules can be configured statically in the software of the user equipment.

[0037] As mentioned previously, the rules are determined for each application taking into account the different network slices and, where appropriate, the different networks available. It is noted that preferably, they are determined by taking into account the characteristics and subscriptions of each user, however it is also possible, in a particular embodiment, that the rules be defined solely according to the specificities of the applications and that the same rules are sent to all users, it is then up to them to disregard the rules that are not applicable. They can also take account of other parameters, such as for example the hardware and/or software characteristics of the user equipment.

Various configurations can be envisaged for each rule.

Thus, for example, the same rule can associate with one or more streams of an application a plurality of distinct network slices. This plurality of network slices can correspond to the same network or to distinct communications networks.

[0040] In this embodiment, the application can simultaneously access the different network slices identified by the rule, for example with a view to distributing the load between the different network slices.

As a variant, a priority of use can be assigned to each of said plurality of distinct slices.

[0042] If these slices are attached to separate networks, this allows the user equipment to determine which network (for example, which USIM module or which network card) it should use first, and if this is not accessible (for example because the corresponding USIM module or network card is not activated within the user equipment), a fallback solution.

The usage priorities assigned to the different network slices contained in a rule can be assigned, in a particular embodiment, by the rule management entity, for example so as to carry out load balancing on the different network slices. As a variant, other criteria can be envisaged to establish priorities between the network slices. These criteria can be linked to the user more particularly, for example according to the subscription he has with the network or networks concerned, or the network coverage he has, etc.

[0044] The rules may also contain instructions for using the network slices included in the rules, such as for example in a rule comprising a plurality of distinct network slices, the instruction to carry out a distribution of the load between these separate network sections, or to use one section nominally and another as backup, etc.

Furthermore, in a particular embodiment, the management entity can associate with each rule an execution priority of said rule.

[0046] Such a priority allows the user equipment, in the event of conflicts between two determined rules for two different applications to be executed simultaneously (for example the user equipment can only carry traffic with one network at a given time given, and two running applications are associated with network slices belonging to different networks), to select the rule to apply first. As a variant, this priority can be given as an indication and the user equipment can decide to act differently in the event of conflicts.

In a particular embodiment of the invention, the configuration method and/or the rule management method is implemented by a computer.

The invention also relates to a computer program on a recording medium, this program being capable of being implemented in a computer or more generally in user equipment in accordance with the invention and comprises instructions adapted to the implementation of a configuration method as described above.

The invention also relates to a computer program on a recording medium, this program being capable of being implemented in a computer or more generally in a rule management entity in accordance with the invention and comprises instructions adapted to the implementation of a method for managing rules as described above.

[0050] Each program may use any programming language, and be in the form of source code, object code, or intermediate code between source code and object code, such as in partially compiled form, or in no any other desirable shape.

The invention also relates to an information medium or a recording medium readable by a computer, and comprising instructions of the computer program mentioned above.

The information or recording medium can be any entity or device capable of storing the programs. For example, the medium may comprise a storage means, such as a ROM, for example a CD ROM or a microelectronic circuit ROM, or else a magnetic recording means, for example a hard disk, or a flash memory.

On the other hand, the information or recording medium can be a transmissible medium such as an electrical or optical signal, which can be routed via an electrical or optical cable, by radio link, by optical link without wire or by other means.

The program according to the invention can in particular be downloaded from an Internet-type network.

Alternatively, the information or recording medium may be an integrated circuit in which a program is incorporated, the circuit being adapted to execute or to be used in the execution of the configuration method, in accordance with the invention. , or of the method for managing rules, in accordance with the invention.

According to another aspect, the invention relates to a system comprising:

- at least one user equipment according to the invention, intended to be used by a user to whom is allocated a plurality of identifiers uniquely identifying said user on at least one communications network;

- a rules management entity according to the invention.

In a particular embodiment:

- said at least one communications network comprises a plurality of communications networks;

- the transmission module of said management entity is configured to transmit said at least one rule to an entity managing said user in each communications network; and

- each entity managing said user in each communications network is configured to transmit (directly or indirectly) said at least one rule to said user equipment of the user during an association of said user equipment with this communications network.

In another embodiment, said plurality of identifiers is allocated to the user by a single communications network and the rules management entity is an entity of this single communications network.

In yet another embodiment, the rules management entity is an entity independent of said at least one network.

The system benefits from the same advantages as the rules configuration and management methods (as well as the user equipment and the rule management entity) according to the invention, mentioned above.

It is also possible, in other embodiments, for the configuration method, the method for managing the rules, the user equipment, the entity for managing the rules and the system according to the invention to present in combination of all or part of the aforementioned characteristics.

Brief description of the drawings

Other characteristics and advantages of the present invention will become apparent from the description given below, with reference to the appended drawings which illustrate an example of embodiment devoid of any limiting character. In the figures:

[Fig. 1] FIG. 1, already described, represents a prior art network infrastructure in which a slicing technique is implemented;

[Fig. 2] FIG. 2 represents a system according to the invention in a first embodiment;

[Fig. 3] FIG. 3 represents an example of hardware architecture of a rules management entity in accordance with the invention, belonging to the system of FIG. 2, in a particular embodiment;

[Fig. 4] FIG. 4 represents an example of hardware and functional architecture of user equipment according to the invention, belonging to the system of FIG. 2, in a particular embodiment;

[Fig. 5] FIG. 5 illustrates the main steps of a rules management method as it is implemented by the rules management entity of the system of FIG. 2, in the first embodiment; and

[Fig. 6] FIG. 6 illustrates the main steps of a configuration method as it is implemented by a user equipment of the system of FIG. 2, in the first embodiment.

Description of the invention

As mentioned above, the invention falls within the context of communication networks using slicing techniques or network slicing.

In this context, it proposes a mechanism making it possible to configure user equipment with rules, each rule associating one or more streams of a given application with one or more network slices, these network slices possibly being attached to separate networks (e.g. PLMN). For this purpose, the user equipment is for example equipped with a plurality of USIM modules and/or network cards enabling it to be associated with these various networks, or with a single network but via various subscriptions (subscriptions).

It is noted that the invention applies to any type of application (audio, video, for text transfer, multimedia player, etc.), real time or not, which can be installed natively on the equipment users, or downloaded from an application server, public or managed by a service provider, or even by the operator of one of the networks, etc.

[0066] Figure 2 shows a system 1 according to the invention, configured for the implementation of such a mechanism, in a first embodiment.

In this first embodiment, it is assumed that a user U has user equipment UE2, in accordance with the invention, and configured to receive a plurality of UICC cards (for example K UICC cards, K designating a integer greater than or equal to 2), each UICC card storing a USIM module. Each module USIMk, k denoting an integer between 1 and K, comprises an application allowing the user U to register and gain secure access to a distinct communications network NWk with which he has taken out a subscription. For this purpose, each module USIMk stores an identifier IDk(U) allocated to the user U by the network operator NWk. This identifier identifies it in a unique way and in a permanent and invariant way on the NWk network (ie throughout the duration of its subscription or subscription to the network). It is noted that the user U can designate either an individual user or a group of users, such as for example a community.

In the example in FIG. 2, the communications networks NW1,...,NWK are 3GPP 5GS (5G System) networks, and the identifiers IDk(U) are SUPI type identifiers. However, no limitation is attached to the nature of the communications networks NW1, NW2,...,NWK, nor to the nature of the access networks allowing access thereto. This may include any cellular mobile networks as defined by the 3GPP standard (2G, 3G, 4G, 5G, etc.), or other types of networks, such as fixed networks, non-3GPP networks such as WLAN (Wireless Local Area Network) networks (eg Wi-Fi (Wireless Fidelity) networks), etc. The identifiers IDk(U) depend on the nature of the networks considered. Thus, it may for example be a variant of

It is assumed that each NWk network implements a slicing technique for its subscribers, as mentioned in the 3GPP TS 23.501 specification cited above. We note SLl(k),...,SLNk(k) the available slots of the network NWk, Nk designating an integer greater than or equal to 1 corresponding to the number of slots offered by the network NWk, Nk being able to vary from one network NWk to another, and being likely to change over time. Such a slicing technique is known per se and not described in more detail here. In a known manner, each network slice is uniquely identified on the network to which it belongs by an S-NSSAI identifier (for “Single Network Slice Selection Assistance Information”) defined by the 3GPP standard in the specifications TS 23.501 and TS 23. 003 entitled “Technical Specification Group Core Network and Terminals; Numbering, addressing and Identification”, V16.0.0, September 2019.

In the first embodiment described here, the rules, generally denoted RUL, used for the configuration of the user equipment UE2 are determined by a rules management entity 3, in accordance with the invention, associated with the different networks NW1,...,NWK, and hosted in a mediation gateway 4 interfacing with these different networks. More particularly here, assuming 5G networks, the mediation gateway 4 interfaces with the PCF (Policy Control Function) entities for managing the flow policy of each of the networks NW1,...,NWK, referenced by PCF1,...,PCFK respectively. In a manner known per se, the PCF entities allow the control of policies in 5GS networks, in particular at the level of the AMF (Access and Mobility Management Function) entities of the NW1 networks,...,

It is noted that in the example considered in Figure 2, for the sake of simplification, the rules management entity 3 is associated with the K networks NW1,...,NWK corresponding to the K USIM modules of the equipment user UE2, i.e. it defines RUL rules for users who have subscribed to these networks and has, for this purpose, visibility on the characteristics of the network slices corresponding to these different networks . However, this assumption is not limiting in itself. The rule management entity 3 can be associated with other networks in addition to the networks NW1,...,NWK. It can also be an entity independent of the NW1,...,NWK networks (which can, for example, use the connectivity of one of the networks to communicate with the

In the embodiment described here, the mediation gateway 4 has the hardware architecture of a computer, as represented schematically in FIG. 3, on which the rule management entity 3 is based. It comprises in particular a processor 5, a random access memory 6, a memory

ROM 7, a non-volatile flash memory 8, as well as communication means 9 comprising one or more communication interfaces enabling it to communicate in particular with the PCF entities of the networks NW1,...,NWK.

In the embodiment described here, the ROM 7 of the mediation gateway 4 is a recording medium according to the invention, readable by the processor 5 and on which is recorded a computer program PROG4 according to the invention, which comprises instructions defining the main steps of a method for managing rules in accordance with the invention. The program PROG4 defines equivalently functional modules of the rule management entity 3 (and correlatively of the mediation gateway 4), which are based on or control the hardware elements 5 to 9 mentioned above. These functional modules include in particular (see figure 2):

- a determination module 3A, configured to determine, for at least one user equipment, at least one RUL rule as described in more detail later, associating one or more slices of one or more networks with one or more streams of at least one application; and

- A transmission module 3B configured to transmit said at least one RUL rule to the user equipment(s) concerned. It is noted that this transmission can be done directly or indirectly, via one or more intermediate nodes. Thus, in the first embodiment described here, the RUL rules are sent to the user equipments concerned via the PCF and AMF entities of the networks with which they are associated, as described further below.

In the example considered in Figure 2, the user equipment UE2 is a terminal, such as for example a smart phone or smartphone, a computer, or even a digital tablet.

FIG. 4 schematically illustrates an example of functional and hardware architecture of the user equipment UE2. In the example of FIG. 4, the user equipment UE2 is a so-called dual-SIM device, that is to say it is configured to receive two distinct USIM modules, namely a USIM1 module and a USIM2 module. , allowing it to associate with the two networks NW1 and NW2 respectively.

Conventionally, the user equipment UE2 also comprises a TE (for “Terminal Equipment” in English) module and two ME (for “Mobile Equipment” in English) modules. Each ME module itself comprises a TA module (for “Terminal adapter”), an NT module (for “Network Termination”) and an RT module (for “Radio Termination”). These different modules communicate with each other via various interfaces (Cu, R, Tu, Uu) as shown in the figure. Such modules and interfaces are known per se and described in particular in the 3GPP specification document TS 21.905 entitled “Technical Specification Group Services and System Aspects; Vocabulary for 3GPP Specifications”, vl5.1.0, December 2018, and in chapter 9 of A. Kukushkin's book entitled “Introduction to Mobile Network Engineering: GSM, 3G-WCDMA, LTE and the Road to 5G”, John Wiley and Sons, 2018 (see figure 9.3 on page 123). The Tu interface connects the specific parts to the access network and to the core network in the user equipment; she is usually the owner.

The TE module of the UE2 user equipment differs from a conventional TE module in that it incorporates here different modules configured to implement a configuration method according to the invention, and more particularly in the first mode. implementation described here:

- an access module 2A, configured to access via an application interface provided for this purpose, a plurality of applications Appj, j=l,...,J, J designating an integer greater than or equal to 1, installed by for example on the user equipment UE2 (for example in a non-volatile memory 10 of the user equipment UE2). In the example illustrated in FIG. 4, three applications App1, App2 and App3 are installed on the user equipment UE2;

- a module 2B for obtaining, configured to obtain at least one RUL rule as determined

by the entity 3 for managing the rules for the applications installed on the user equipment UE2; and

- An execution module 2C, configured to execute said at least one rule during access to the applications installed on the user equipment UE2.

In the first embodiment described here, the modules 2A, 2B and 2C are for example software modules defined by means of instructions from a computer program PROG2, comprising instructions corresponding to the main steps of a configuration method according to the invention.

It is noted that the applications Appj, j=1,...,J are not necessarily applications present natively on the user equipment UE2; they may, at least for some of them, have been downloaded later onto the user equipment UE2 from a public or private application server. In addition, the applications and the number of applications present on the user equipment UE2 are likely to change over time (applications may be deleted, others added, so that the RUL rules configured at the level of the user equipment UE2 are also likely to change over time). It is assumed here that each application installed or not on the user equipment UE2 and generally denoted App (for example App=Appl, App2 or App3 in the example considered in FIG. 4), is identified by an application identifier denoted IDApp. No limitation is attached to the form of this identifier as long as it is understandable and known to the management entity 3 and to the user equipment UE2.

As a variant, all or part of the applications APPj, j=1,...,J can be installed on a physical entity distinct from the user equipment UE2, for example on a server accessible by the latter.

Furthermore, no limitation is attached to the nature of the user equipment UE2. The invention indeed also applies to other types of user equipment than terminals, and in particular to routers, or to user equipment whose TE and ME modules can be distributed over several distinct physical entities (for example partly on a terminal and partly on a company router, etc.).

We will now describe, with reference to FIG. 5, the different steps of the method for managing rules according to the invention as they are implemented by the entity 3 for managing the rules in the first mode of achievement.

In this first embodiment, the RUL rules are determined by the rule management entity 3 associated with the networks NW1,...,NWK, via its determination module 3A, during a so-called provision phase. ment, for a plurality of App applications (step E10). This plurality of applications includes in particular here all or part of the applications Appj, j=1,...,J installed on the user equipment UE2 of the user U.

In addition, in the first embodiment described here, the rules management entity 3 determines RUL rules individually for each user for which it is responsible for defining rules (in other words here, for each user having subscribed a subscription to the networks NW1,...,NWK with which the rule management entity 3 is associated). To this end, the entity 3 for managing the rules takes account of the characteristics of the subscriptions/subscriptions of the user with the operators of the networks NW1,...,NWK. It is assumed for this purpose that the rules management entity 3 is for example configured with information on the subscriptions available to each of the users for whom it must define rules. In particular, the rule management entity 3 is configured here with the list of networks (e.g. PLMN) to which these users have access via their respective user equipment, the rights offered by their subscriptions, the associated quality of service attributes, the hardware and software characteristics users' user equipment, etc. Of course, this list is neither exhaustive nor limiting.

the invention. These are only illustrative examples of information with which the rule management entity 3 can be configured and which it can use to define the RUL rules. In addition, it should be noted that this information is likely to change over time and is therefore dynamically updated at the level of the rule management entity 3 (for example continuously, or at time intervals (pre)determined, or upon detection of a change, etc.).

Alternatively, the rules management entity 3 can access this information by directly consulting the operators of the networks with which the users have taken out a subscription or by accessing a database filled in and updated by these operators so that it reflects a current state of subscriptions taken out by users with these operators.

According to yet another variant, an application installed in the user equipment of the users managed by the rule management entity 3 can be configured to register with the rule management entity 3 and provide it with this information. .

[0087] Note that in another embodiment, the rules management entity 3 can no longer determine RUL rules individually for each user, but by application, all users combined.

In the first embodiment described here, the plurality of applications for which the rules management entity 3 determines a set of RUL rules for each user is predefined. In the remainder of the description, reference is made to facilitate understanding to the rules established for the user U, the considerations presented however applying equally to all the users managed by the rule management entity 3 .

[0089] These may in particular be applications for which agreements have been established between the suppliers of the applications and the operators of the networks NW1,...,NWK associated with the rule management entity 3, or those with which the considered user U has taken out a subscription.

Claims

[Claim 1] Method for configuring a user equipment (UE2) intended to be used by a user (U) to whom a plurality of identifiers (ID1(U), ID2(U),...,IDK( U)), each uniquely identifying said user on at least one communications network (NW1,...,NWK), said method being implemented by said user equipment and comprising, for at least one application (Appj):

a step of obtaining (F30) at least one rule associating with at least one flow of said application, at least one slice of said at least one communications network for routing data relating to said at least one flow and information linking said slice to an identifier among said plurality of identifiers of the user;

a step of configuring (F40) the user equipment with said at least one rule (RUL(U)/Appj) so that it executes (F60) said at least one rule when accessing said application (F50) .

[Claim 2] Configuration method according to Claim 1, in which the said at least one rule is obtained during an association (F20) of the user equipment with the said at least one communications network.

[Claim 3] A configuration method according to claim 1 or 2 wherein said at least one rule comprises a plurality of distinct slices.

[Claim 4] A configuration method according to claim 3 wherein, in said at least one rule, a usage priority is assigned to each of said plurality of distinct slots.

[Claim 5] A configuration method according to any one of claims 1 to 4 wherein the steps of obtaining and configuring the user equipment are carried out via a user interface available on the user equipment.

[Claim 6] Method for managing rules, implemented by an entity (3) for managing rules, said method comprising, for at least one user (U) to whom is allocated a plurality of identifiers (ID1(U), ID2(U),...,IDK(U)) respectively uniquely identifying said user on at least one communications network (NW1,...,NWK):

a step (E10) for determining at least one rule associating with at least one flow of an application, at least one slice of said at least one communications network for routing data relating to said at least one flow and information linking said slice to an identifier among said plurality of identifiers of said user; and

a step (E20) of transmitting said at least one rule to a user equipment of said user.

[Claim 7] Method for managing rules according to claim 6 further comprising a step of assigning, in at least one determined rule comprising a plurality of slices of said at least one communications network, a priority of use to each slice.

[Claim 8] Method for managing rules according to claim 6 or 7 in which at least one determined rule comprising a plurality of slices of said at least one network of

communications includes an instruction to perform load balancing on said plurality of slices.

[Claim 9] A rule management method according to any one of claims 5 to 7 wherein rules associated with different application streams include priorities for use of said rules.

[Claim 10] Method according to any one of Claims 1 to 9, in which the said at least one item of information comprises, for a slice of a communications network:

said identifier among said plurality of identifiers of the user;

an identifier of a module of said user equipment containing said identifier; Where

an identifier of said communication network for which said identifier is allocated to said user.

[Claim 11] A method according to any one of claims 1 to 10 wherein said at least one rule includes an identifier of said application.

[Claim 12] A method according to any of claims 1 to 11 wherein said application is an application installed on said user equipment.

[Claim 13] A method according to any one of claims 1 to 12 wherein at least two of said identifiers allocated to the user identify said user on two different communication networks.

[Claim 14] A method according to any one of claims 1 to 13 wherein at least two of said identifiers allocated to the user identify said user on the same communication network.

[Claim 15] Method according to any one of Claims 1 to 14, in which at least one rule associates a plurality of slices corresponding to distinct communications networks with at least one flow of an application.

[Claim 16] User equipment (UE2) intended to be used by a user to whom is allocated a plurality of identifiers each uniquely identifying said user on at least one communications network, said user equipment comprising:

an obtaining module (2B), configured to obtain at least one rule associating with at least one flow of an application, at least one slice of said at least one communications network for routing data relating to said at least one flow and information linking said slice to an identifier among said plurality of identifiers of the user;

an execution module (2C), configured to execute said at least one rule during access to said application.

[Claim 17] User equipment (UE2) according to claim 16, configured to receive a plurality of USIM (Universal Subscriber Identity Module) modules and/or network cards, each card and/or each module (USIM1,...,USIMK ) being associated with an identifier (ID1(U),...,IDK(U)) distinct from among said plurality of identifiers.

[Claim 18] Rule management entity (3) comprising:

a determination module (3A), configured to determine at least one rule associating with at least one flow of an application, at least one slice of at least one

communications network for routing data relating to said at least one stream and information linking said slice to an identifier among a plurality of identifiers allocated to said user and respectively identifying said user uniquely on said at least one communications network; and a transmission module (3B) configured to transmit said at least one rule to a user equipment of said user.

[Claim 19] System (1) comprising:

- at least one user equipment (UE2) according to claim 16 or 17, intended to be used by a user to whom is allocated a plurality of identifiers uniquely identifying said user on at least one communications network;

- a rules management entity (3) according to claim 18.

[Claim 20] A system (1) according to claim 19 wherein:

said at least one communications network comprises a plurality of communications networks (NW1,..,NWK);

the transmission module of said management entity is configured to transmit said at least one rule to an entity (PCF1,...,PCFK) managing said user in each communications network; and

each entity (PCF1,...,PCFK) managing said user of each communications network is configured to transmit said at least one rule to said user equipment during an association of said user equipment with this communications network.

[Claim 21] System (1) according to claim 19 in which the said plurality of identifiers is allocated to the user by a single communications network (NW1) and the entity (3) for managing the rules is an entity of this single communications network.