Methods and devices for configuring and using a network supporting network slices

Abstract

The invention relates to a method for configuring a network supporting N network slices, the method comprising the steps of: - generating (1100) M connection elements, each connection element being configured to make it possible to obtain at least one connection identifier intended to be used at a transport and / or application layer during a communication via one or more network slices; - associating (1200) at least one connection element with at least one network slice according to a given association criterion; - transmitting (1300) data indicating the associations between connection elements and network slices to a set E of entities of the network that are configured to participate in the routing of data packets within the network.

Description

Description Title of the invention: Methods and devices for configuring and using a network supporting network slices Previous technique

[0001] The present invention belongs to the general field of telecommunications. More particularly, it relates to methods for configuring network slices, enabling a terminal connected to a network supporting such slices to discover their configuration, and also enabling terminals that have thus discovered network slices to communicate with each other via all or part of these slices. The invention also relates to devices and terminals configured to implement these methods. The invention finds a particularly advantageous, though not limiting, application in the context of 5G cellular networks.

[0002] Network operators can deploy end-to-end virtual private networks (VPNs) on demand, fully (or partially) dedicated to their customers. This practice has evolved into the concept of slicing a communication network, where the overall network architecture relies on a set of resources that can be used to create network partitions called "network slices" (or simply "network slices" hereafter).

[0003] The characteristics of a network slice are expressed in terms of capacity (bandwidth), quality of service (e.g., latency, one-way transit time), and even security (e.g., preserving the confidentiality of transmitted information through the use of encryption techniques). Regarding these aspects, and more generally, the work carried out by the IETF (Internet Engineering Task Force) can be usefully consulted, such as the document "A Framework for IETF Network Slices in Networks Built from IETF Technologies," by A. Farrell, J. Drake, R. Rokui, S. Homma, K. Makhijani, L.M. Contreras, and J. Tantsura, dated August 25, 2023.

[0004] Furthermore, several types of network slices are known. For example, in its technical specification TS 23.501 (paragraph 5.15.2.2), the 3GPP organization (“3rd Generation Partnership Project") defines and documents, in particular, the following types: - enhanced mobile broadband service “eMBB” (“Enhanced Mobile Broadband” in English), - massive deployment of the Internet of Things (or "mloT"), - ultra reliable and low latency communications (“Ultra Reliable Low Latency Communications” or “URLLC” in English).

[0005] An operator's choice to design and deploy one or more specific types of bandwidth is largely determined by the nature of the traffic generated by the applications used or the services subscribed to by a network user. For example, an "immersive" service that leverages augmented or virtual reality technologies is generally very demanding in terms of latency and data exchange reliability. Such an immersive service is therefore a "natural" client for a URLLC bandwidth.

[0006] Moreover, a network that supports network slices can itself be composed of several subnets (also called "domains"), each of said subnets supporting one or more network slices. An example of this principle is schematically represented by Figure 1, in which a NET network is decomposed into three subnets SS_NET_1, SS_NET_2, SS_NET_3 (each slice of a subnet SS_NET_i, i being an integer index between 1 and 3, being represented for illustrative purposes by a parallelogram in Figure 1).

[0007] Therefore, the slices of the SS_NET_i subnets can be linked together to provide value-added services. For example, a service provider wishing to leverage the NET network infrastructure can use specific slices deployed within the SS_NET_i subnets to provide a service whose traffic will be routed through those slices. The slices thus used form so-called "adjacent" slices, which are then virtually linked together for the service offered by the provider. The connection interfaces between adjacent slices can be managed using mechanisms such as those described in the following document proposed by the I ETF: "YANG Data Models for 'Attachment Qrcuits'-as-a-Service (ACaaS)", M. Boucadair, R. Roberts, O. Gonzalez de Dios, S. Barguil, B. Wu, July 10, 2023.

[0008] Such an example of interconnection between network slices is also illustrated by Figure 1 where a service provider relies on slices TR_1_2, TR_2_2, TR_3_3 belonging respectively to subnets SS_NET_1, SS_NET_2, SS_NET_3. It should be noted that this same provider may offer one or more services which use one or more of said network slices.

[0009] Conventionally, this type of configuration, where network slices deployed in subnets are interconnected to provide a specific service, is conceptually represented as a "multi-domain slice" (also known as a "stitched slice" or "hierarchical slice") that groups the slices of the subnets in question. The network slices that make up a multi-domain slice are then called "single-domain slices." Such a multi-domain slice, TR MULTI, is shown for illustrative purposes in Figure 1. This TR MULTI slice groups the slices TR_1_2, TR_2_2, and TR_3_3, which are deployed in the subnets SS_NET_1, SS_NET_2, and SS_NET_3, respectively.

[0010] It should be noted that there is no limitation attached to the nature of an SS_NET_i subnet. For example, it can be a radio access network (RAN), an aggregation network, a core network (CN), a transport network (TN), or a transit network, etc.

[0011] Furthermore, the implementation of a multi-domain slice is not contingent upon the availability or activation of the same techniques used for implementing single-domain slices on each subnet. For example, see Figure 1: - The SS_NET_1 subnet can be configured to implement tunnels IPsec, which are used to route traffic in the slices deployed in this SS_NET_1 subnetwork, - the SS_NET_2 subnet can be configured to implement a network-level virtual private network (“Layer 3 VPN” or “L3VPN” in English) combined with “TE” (“Traffic Engineering” in English) mechanisms, - The SS_NET_3 subnet can implement segment routing resources based on the I Pv6 protocol ("Segment Routing I Pv6" or "SRv6" in English) to route traffic in the slices deployed in this SS NET 3 subnet.

[0012] With regard to the realization of slices (whether multi-domain or single-domain) in IP / MPLS networks (“Internet Protocol” / “Multiprotocol Label Switching”), it is possible to consult the following document: “A Realization of I ETF Network Slices for 5G Networks Using Current IP / MPLS Technologies”, KG Szarkowicz, R. Roberts, J. Lucek, M. Boucadair, LM Contreras, May 23, 2023.

[0013] It follows from the foregoing considerations that the engineering and deployment of slices in a network are complex activities to implement, as they require taking into account multiple configuration parameters.

[0014] In addition, to guarantee access for data traffic to one or more network slices, that traffic must be authorized. Such authorization typically relies on traffic classification rules. These rules are applied at the "entry" (e.g., at the edge) of a network / subnetwork that supports the slice(s) in question, more specifically by one or more edge nodes.

[0015] For example, an edge node can be located at the connection interface of a Packet Gateway (FGW) that provides access to the Internet. As another example, an edge node can be located at the connection interface of a mobile terminal (or User Equipment (UE)) to a Radio Access Network (RAN).

[0016] However, the design and application of traffic classification rules also contribute very significantly to the overall complexity of deploying and operating a network supporting slices.

[0017] Indeed, and from a first perspective, it is necessary to consider a level of granularity characteristic of a network slice. This level can be macroscopic (for example, a slice deployed to route traffic to the Internet) or microscopic (for example, in the case of application traffic exchanged between two mobile devices for which a dedicated slice has been deployed). In any case, whether macroscopic or microscopic, this level of granularity impacts traffic classification management. because it generates difficulties in terms of optimizing the use of resources implemented by one or more network segments, and capable of meeting the varied requirements of the different segments (requirements which can be expressed in terms of quality of service, security, resilience, etc.).

[0018] Furthermore, a second aspect is problematic: the current method of identifying packets destined for routing through a given network slice. Specifically, this identification relies on the use of identifiers such as IP addresses or prefixes. However, in some environments, multiple applications can be reached using the same IP address, even though these applications may have constraints requiring their respective traffic to be routed through separate network slices.

[0019] Finally, and according to a third aspect, it is necessary to take into account the variety of uses of a network slice. This variety is manifested in particular in terms of traffic diversity, the nature of the structure that operates the slice (e.g. accounting department, R&D department, production department) or the way in which the slice is used (e.g. management of traffic overloads during busy hours, or principles of traffic load balancing).

[0020] This complexity related to the design and application of traffic classification rules can be further compounded by the evolution of these rules over time, according to the dynamics of a set of criteria such as changing user needs or traffic growth. This is the case, for example, in the context of deploying a channel slot for the broadcast of a sporting or cultural event, where the traffic classification rules may change with the number and profile of users of that slot.

[0021] Ultimately, it is clear that these various aspects to consider when designing classification rules generate a significant risk that one or more of these rules may be designed inappropriately. One possible consequence of such an inappropriate design is the suboptimal routing of data within a network. Description of the invention

[0022] The present invention aims to remedy all or part of the disadvantages of the prior art, in particular those set out above, by proposing a solution which allows for a much simpler and more efficient management of traffic routing in a network supporting network slices compared with the solutions of the prior art.

[0023] The solution proposed by the invention makes it possible in particular to simplify (in terms of traffic classification) the tasks performed by nodes of a network supporting network slices, for example edge nodes.

[0024] To this end, and according to a first aspect, the invention relates to a method for configuring a network supporting N network slices, N being an integer greater than or equal to 1, said method comprising the following steps: - generation of M connection elements, where M is an integer greater than or equal to 1, each connection element being configured to allow obtaining at least one connection identifier intended for use at a transport and / or application layer during communication via one or more network slices, - association of at least one connection element to at least one network slice based on a given association criterion, - transmission of data indicating the associations between connection elements and network slices to a set E of network entities configured to participate in the routing of data packets within the network.

[0025] Configuring network slices in this way proves particularly advantageous. The resulting connection elements are not only shared with network entities, including those responsible for traffic classification, particularly at the network edge, but are also intended to be shared with endpoints that wish to use one or more of these network slices for communication. More specifically, these connection elements enable the control and facilitated identification of one or more appropriate slices for routing data within the network, for example, when an endpoint is running an application function.

[0026] This optimized data routing via one or more network slices can be achieved by inserting connection identifiers into the data packets. obtained through said connection elements. More specifically, on the basis of such connection identifiers, a network entity, such as an edge node, which receives data packets can then determine the connection elements associated with said connection identifiers, and thus route the data packets into the appropriate slices.

[0027] No limitations are attached to the nature of the connection identifiers that can be obtained according to the invention. In particular, a connection identifier can be a "CI D" type identifier ("Connection ID") used by the QUIC protocol or the DTLS ("Datagram Transport Layer Security") protocol. These provisions also apply to connection elements.

[0028] In particular modes of implementation, the configuration process may further include one or more of the following characteristics, taken individually or in all technically possible combinations.

[0029] In particular modes of implementation, the number M is greater than or equal to the number N.

[0030] In particular modes of implementation, at least one connection element is a pattern configured to impose, among the sequence of bits forming a connection identifier, the value of at least one bit having a given position within said sequence of bits.

[0031] In particular implementation modes, at least one connection element is a set comprising at least one given connection identifier.

[0032] In particular modes of implementation, the said association criterion consists in a given connection element being associated with a given network slice.

[0033] In particular modes of implementation, the said association criterion consists in the fact that slices of the same type are associated with one or more of the same connection elements.

[0034] In specific implementation modes, the type of a slice is any one of the following: - Enhanced mobile broadband service, - massive deployment of the Internet of Things, - ultra-reliable and low-latency communications.

[0035] In specific implementation modes, the set E of entities includes at least one of the following: - a network address allocation server, - a network prefix allocation server, - a router configured to enable a network prefix delegation function, - a network edge node, such as an access router or an "ASBR" router ("Autonomous System Border Routers" in English).

[0036] In certain implementation modes, at least one network slice is a multi-domain slice.

[0037] According to another aspect, the invention also relates to a receiving method implemented by an entity of a network supporting network slices and configured in accordance with a configuration method according to the invention, said receiving method comprising a step of receiving said data indicating the associations between connection elements and network slices.

[0038] According to another aspect, the invention relates to a first data processing method implemented by a terminal connected to at least one network supporting network slices and configured according to a configuration method according to the invention, said first data processing method comprising the steps of: - transmission, to an entity of said network, of a request to obtain at least one connection element, - receipt, from said entity, of a response to said request, said response including at least one connection element associated with at least one network slice supported by the network.

[0039] According to another aspect, the invention relates to a second data processing method implemented by equipment in a network supporting network slices and configured according to a configuration method according to the invention, said second data processing method comprising the steps of: - reception, from a terminal connected to said network, of a request to obtain at least one connection element, - transmission to said terminal of a response to said request, said response comprising at least one connection element associated with at least one network slice supported by the network.

[0040] In particular modes of implementation, the first or second data processing method may further include one or more of the following characteristics, taken individually or in all technically possible combinations.

[0041] In particular implementation modes, the retrieval request includes at least one parameter corresponding to a slice identifier or a slice type to which the terminal is authorized to connect, the response to the request including at least one connection element associated with a slice itself associated with said identifier or with a slice of said type.

[0042] In particular implementation modes, in the absence in the request of a parameter corresponding to a slice identifier or a slice type to which the terminal is authorized to connect, the response to the request includes at least one connection element associated with at least one slice to which the terminal is authorized to connect.

[0043] In specific implementation methods, the type of a slice is any one of the following: - Enhanced mobile broadband service, - massive deployment of the Internet of Things, - ultra-reliable and low-latency communication.

[0044] In specific implementation modes, the response to the request also includes an identifier of said at least one network supporting network slices.

[0045] In specific implementation methods: - said terminal is a user terminal and the entity of said at least one network is an entity of said set E, or - said terminal is an application server and the entity of said at least one network is an orchestration device configured to manage service functions within said at least one network.

[0046] According to another aspect, the invention relates to a first communication method implemented by a first terminal, called the "client terminal," for exchanging data with a second terminal, called the "server terminal." The client terminal is connected to a network supporting network slices and configured according to a configuration method according to the invention, and at least one terminal, called the "server terminal." candidate”, among said client terminal and said server terminal being in possession of at least one connection element of said network, said process comprising the steps of: - obtaining data designating a terminal, referred to as the "primary terminal", from among at least one candidate terminal, - if the client terminal is the primary terminal: • transmission, to the server terminal, of at least one connection element, called "first connection element", among said at least one connection element that said client terminal possesses, • obtaining at least one connection identifier using said at least one first connection element, said at least one connection identifier being intended for use at a transport and / or application layer during communication via one or more network slices, - if the server terminal is the primary terminal: • reception, from the server terminal, of at least one connection element, referred to as the "second connection element", from among the at least one connection element that the server terminal possesses, • obtaining at least one connection identifier using said at least one second connection element, said at least one connection identifier being intended for use at a transport and / or application layer during communication via one or more network slices.

[0047] According to another aspect, the invention relates to a second communication method implemented by a second terminal, called the "server terminal," for exchanging data with a first terminal, called the "client terminal." The client terminal is connected to a network supporting network slices and configured according to a method of the invention, and at least one terminal, called the "candidate terminal," among said client terminal and said server terminal, is possessing at least one connection element of said network. This method comprises the following steps: - obtaining data designating a terminal, referred to as the "primary terminal", from among at least one candidate terminal, - if the client terminal is the primary terminal: • receipt, from the client terminal, of at least one connection element, referred to as the "first connection element", from among the at least one connection element that the client terminal possesses, • obtaining at least one connection identifier using said at least one first connection element, said at least one connection identifier being intended for use at a transport and / or application layer during communication via one or more network slices, - if the second terminal is the primary terminal: • transmission, to the client terminal, of at least one connection element, referred to as the "second connection element", from among the at least one connection element that the server terminal possesses, • obtaining at least one connection identifier using said at least one second connection element, said at least one connection identifier being intended for use at a transport and / or application layer during communication via one or more network slices.

[0048] In particular modes of implementation, the first or second communication method may also include one or more of the following characteristics, taken individually or in all technically possible combinations.

[0049] In specific implementation methods: - if the client terminal or the server terminal is the only candidate terminal, said candidate terminal is designated as the primary terminal, or - if the client terminal and the server terminal are both candidate terminals, the data designating the primary terminal is generated by one of said two candidate terminals according to a given designation criterion.

[0050] In specific implementation modes, obtaining at least one login identifier using at least one login element involves: - if said at least one connection element contains a pattern, a generation of at least one connection identifier conforming to said pattern, and / or - if said at least one connection element includes a set of given connection identifiers, a selection of at least one connection identifier from said set.

[0051] In specific implementation modes, the client terminal is connected to a set of network slices supported by the network, called "active slices", And : - if the client terminal is the primary terminal, then at least one first connection element is associated with one or more active slices, or - if the server terminal is the primary terminal, a list containing identifiers and / or types of said active slices is transmitted by the client terminal to the server terminal, said at least one second connection element being selected by the server terminal from said at least one connection element which it possesses and so as to be associated with at least one active slice.

[0052] In particular implementation modes, one or more slices among the active slices are configured to provide a given application function.

[0053] In particular implementation modes, before obtaining the data designating the primary terminal, each terminal transmits to the other terminal data configured to inform said other terminal that said terminal transmitting said data is capable of communicating by exploiting at least one of the network slices supported by the network.

[0054] According to another aspect, the invention relates to a third method of communication via a node of a network supporting network slices and configured according to a configuration method according to the invention, said node belonging to said assembly E, said communication method comprising the steps of: - reception of a data packet from a terminal, called the "sending terminal", said data packet being destined for another terminal, called the "receiving terminal", and containing at least one connection identifier intended to be used at the transport and / or application layer during communication via one or more network slices, - routing of the data packet to the receiving terminal based on at least one connection identifier.

[0055] In particular modes of implementation, the third communication method may further include one or more of the following characteristics, taken individually or in all technically possible combinations.

[0056] In particular implementation modes, the data packet includes a connection identifier associated with the sending terminal and another connection identifier associated with the receiving terminal, said process also including steps of: - evaluation of a conformity criterion based on the aforementioned connection identifiers contained in the data packet, and - if the conformity criterion is met: • determination of the connection element, referred to as the "useful connection element", associated with one of the connection identifiers contained in the data packet, • routing of the data packet to the receiving terminal using a network slice determined according to said useful connection element, - if the compliance criterion is not met, the data packet is routed to the receiving terminal using a network slice designated by default or without using a network slice supported by the network.

[0057] In particular modes of implementation, the evaluation of the conformity criterion involves a comparison of the values ​​of at least two bits belonging respectively to the connection identifiers of the sending terminal and the receiving terminal contained in the data packet, each of said bits having a given position within the sequence of bits forming the connection identifier to which it belongs, said conformity criterion being satisfied if said values ​​are identical.

[0058] In specific implementation modes, the receiving terminal is connected to a set of network slices supported by the network, called "active slices", and: - if the compliance criterion is met and if the slice associated with said useful connection element is an active slice, the data packet is routed using said network slice associated with said useful connection element, - if the compliance criterion is met and if the slice associated with said useful connection element is not an active slice, the data packet is routed using a network slice designated by default.

[0059] In specific implementation modes, the receiving terminal is connected to a set of network slices supported by the network, called "active slices," said process including a step of determining the connection element, called the "useful connection element," associated with a connection identifier from among at least one connection identifier contained in the data packet, and: - if the slice associated with said useful connection element is an active slice, the The data packet is routed using said network slice associated with said useful connection element. - if the slice associated with the useful connection element is not an active slice, the data packet is routed using a network slice designated by default.

[0060] In another aspect, the invention relates to a computer program comprising instructions for implementing a: - configuration method according to the invention, or - reception method according to the invention, or - first data processing method according to the invention, or - a second data processing method according to the invention, or - first communication method according to the invention, or - second communication method according to the invention, or - third communication method according to the invention, when said program is executed by a computer.

[0061] This program 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.

[0062] According to another aspect, the invention relates to a computer-readable information or recording medium on which a computer program according to the invention is recorded.

[0063] The information or recording medium can be any entity or device capable of storing the program. For example, the medium may 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 hard drive.

[0064] On the other hand, the information or recording 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 an Internet-type network.

[0065] Alternatively, the information or recording medium 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.

[0066] According to another aspect, the invention relates to a configuration device comprising means configured to implement a configuration method according to the invention.

[0067] In another aspect, the invention relates to a network entity supporting network slices and comprising means configured to implement: - a reception method according to the invention, and - a second data processing method according to the invention.

[0068] In another aspect, the invention relates to a terminal comprising means configured to implement: - a first data processing method according to the invention, as well as: - a first communication method according to the invention, or - a second communication method according to the invention.

[0069] According to another aspect, the invention relates to a network node supporting network slices and comprising means configured to implement a third communication method according to the invention. Brief description of the drawings

[0070] Other features and advantages of the present invention will become apparent from the description below, with reference to the accompanying drawings, which illustrate an example of an embodiment without being limiting in any way. In the figures: [Fig. 1] Figure 1 schematically represents an example of a network supporting network slices according to the state of the art; [Fig. 2] Figure 2 schematically represents a network configuration system supporting network slices according to a particular embodiment of the invention; [Fig. 3] Figure 3 schematically represents an example of the hardware architecture of a configuration device belonging to the system in Figure 2; [Fig. 4] Figure 4 represents, in the form of a flowchart, a particular method of implementing a first general process implemented by the system of Figure 2. Said general process includes a configuration process according to the invention implemented by the configuration device of Figure 3; [Fig. 5] Figure 5 schematically represents a data processing system according to a particular embodiment of the invention; [Fig. 6] Figure 6 represents, in the form of a flowchart, a particular method of implementing another general process implemented by the system of Figure 5. Said other general process encompasses first variants of first and second data processing methods according to the invention implemented respectively by a user terminal and a DHCP server; [Fig. 7] Figure 7 schematically represents a communication system according to a particular embodiment of the invention; [Fig. 8] Figure 8 represents, in the form of a flowchart, a particular method of implementing another general method implemented by the system of Figure 7. Said other general method encompasses first variants of first and second communication methods according to the invention implemented respectively by a client terminal and a server terminal; [Fig. 9] Figure 9 schematically represents another communication system according to a particular embodiment of the invention; [Fig. 10] Figure 10 represents, in the form of a flowchart, a particular method of implementing another general method implemented by the system of Figure 9. Said other general method includes a communication method according to the invention implemented by a (peripheral) node of the network, as well as communication methods respectively implemented by a transmitting terminal and a receiving terminal. Description of implementation methods

[0071] The present invention is described herein in the context of the configuration and operation of a 5G-type NET_5G network, supporting network slices and designed to allow the transmission and reception of data packets. This solution is called here UMAMI (“collaborative qUic-based MAnageMent of sliced ​​networks” in English).

[0072] This configuration and operation of the NET 5G network according to the invention aims at optimized management of traffic routing in said NET 5G network compared with prior art solutions, as described later.

[0073] It should be noted that the invention remains applicable to other types of networks such as, for example, B5G networks ("Beyond 5G" in English), but also 6G when this technology becomes available, IP / MPLS networks, etc. In general, there are no limitations attached to the nature of the communication networks that can be considered within the scope of the present invention.

[0074] More specifically, the implementation of the invention as described herein is carried out in four phases, each corresponding to a distinct aspect of the invention. These four phases comprise: - a first phase enabling the implementation of a specific configuration of the NET 5G network, so that a network slice is associated with a connection element and that network entities configured to participate in the routing of data packets within the network become aware of these associations; - a second phase enabling the configuration of a terminal connected to the NET 5G network so that it discovers the configuration of the latter as determined during the first phase, more particularly with regard to the connection element(s) associated with the slice(s) to which the terminal is authorized to connect; - a third phase enabling two terminals, at least one of which is configured in accordance with the second phase, to establish communication supported by the NET 5G network using connection elements from among those discovered during said second phase, - a fourth phase which consists of the communication established between the said two terminals via the NET 5G network being exploited to allow them to exchange data.

[0075] These different phases will now be described in detail in order to illustrate ways of implementing the invention.

[0076] It should be noted that a "network entity" here generally refers to an entity configured to perform at least one function within the network. As such, unless explicitly stated, a "network entity" can refer to either a hardware entity (e.g., a piece of hardware) or a software entity (e.g., a software application).

[0077] For the remainder of the description, and in order to simplify it, we consider in no way restrictively that the NET 5G network supports a number N of slices equal to 3. The three slices concerned are respectively noted TR_5G_1, TR_5G_2, TR_5G_3, and correspond to three multi-domain slices.

[0078] The inclusion of multi-domain slices does not, however, constitute a limitation of the invention. Thus, nothing precludes considering only single-domain slices, or one or more single-domain slices and one or more multi-domain slices.

[0079] The invention is not limited by considering a number N of slices equal to 3. In general, the invention can be implemented for any number N greater than or equal to 1 (i.e. in other words, as soon as the NET 5G network has at least one network slice).

[0080] It is important to note that the description here adopts the convention that a multi-domain slice is counted as a single slice, and not for the number of single-domain slices it comprises. This counting convention is, however, purely arbitrary, and nothing prevents the adoption of an alternative convention that counts the local slices used by a multi-domain slice individually.

[0081] Furthermore, there are no limitations attached to the respective types of the aforementioned TR_5G_1, TR_5G_2, and TR_5G_3 slices. Thus, the type of a TR 5GJ slice (where i is an integer index between 1 and 3) can, for example, be any one of the following: - Enhanced mobile broadband service, - massive deployment of the Internet of Things, - ultra-reliable and low-latency communications.

[0082] More generally, the invention can be implemented independently of any limitations concerning the following aspects: number of subnets (domains) per multi-domain slice, number of single-domain slices of a subnetwork, nature of a subnetwork (e.g. RAN, CN or TN), techniques used for the realization of single-domain slices (e.g. I Psec tunnels, L3VPN + TE or SRv6), etc.

[0083] For the remainder of this description, we also assume that each TR 5GJ slice is associated with a unique TRJ ID. This TRJ ID corresponds, for example, to an identifier used by the TR 5GJ slice and carried in data packets (e.g., to be added to a field within the data packets) that are routed through said TR 5GJ slice. In another example, this TRJ ID is distinct from an identifier used by the TR 5GJ slice to route data packets.

[0084] First phase

[0085] Figure 2 schematically represents a SYS_1 system for configuring the NET 5G network according to a particular embodiment of the invention.

[0086] As illustrated by Figure 2, the SYS_1 system comprises a first entity 110 and a second entity 120.

[0087] The first entity 110 is an edge node of the NET 5G network. As an edge node, it is specifically configured to classify packets received from terminals connected to the NET 5G network. It could be, for example, an access router or an "ASBR" type router.

[0088] In the example in Figure 2, the edge node 110 is shown at the edge of the NET 5G network, but it will be evident that this representation is only illustrative. Indeed, this edge node 110 could be located elsewhere in the NET 5G network, such as at the edge of a subnet belonging to one of the TR 5GJ bands (e.g., connection to a neighboring network). Generally speaking, those skilled in the art are familiar with the possible locations of an edge node in a communication network, so these aspects are not described in detail here.

[0089] Furthermore, there is nothing to preclude considering other types of nodes, since management traffic can be injected into a network slice via a router that is not necessarily located at the network edge. This could, for example, involve BFD (Bidirectional Forwarding Detection) traffic routed into a test slice deployed between certain routers in the network.

[0090] The second entity 120, meanwhile, is an address allocation server compliant with the "DHCP" protocol ("Dynamic Host Configuration Protocol" in English).

[0091] More generally, entities 110 and 120 belong to a set of entities, hereinafter referred to as "set E" (not shown in the figures), grouping entities of the NET 5G network configured to participate in the routing of data packets within said NET 5G network.

[0092] The fact that this embodiment considers a single edge node 110 and a single DHCP server is solely for the sake of simplifying the description of the invention. Therefore, there is nothing to preclude the possibility of using multiple edge nodes and / or multiple DHCP servers.

[0093] The list of entities capable of participating in the routing of data packets within the 5G NET network is not limited to one or more edge nodes and / or one or more DHCP servers. Thus, in addition to the aforementioned entities, set E may include at least one of the following: a network prefix allocation server, a router configured to enable a network prefix delegation function, etc.

[0094] In addition to the entities of set E, the SYS_1 system includes a configuration device 130.

[0095] Device 130 is configured to perform processing to determine a specific NET 5G network configuration, by implementing steps of a configuration process according to the invention. This could be, for example, an orchestration device, such as a network orchestrator or a network controller (e.g., an SDN controller).

[0096] Each of the entities 110, 120 (as well as more broadly any entity belonging to set E) is configured to carry out processing enabling the specific configuration of the NET 5G network determined by the device 130 to be known, by implementing steps of a reception process according to the invention.

[0097] Figure 3 schematically represents an example of the hardware architecture of the configuration device 130 belonging to the SYS_1 system of Figure 2.

[0098] As illustrated in Figure 3, the configuration device 130 has the hardware architecture of a computer. Thus, the configuration device 130 includes, in particular, a processor 131, a random access memory 132, a read-only memory 133 and a non-volatile memory 134. It also has means of communication 135.

[0099] The read-only memory 133 of the configuration device 130 constitutes a storage medium according to the invention, readable by the processor 131, on which a computer program PROG_136 according to the invention is stored, comprising instructions for executing steps of the configuration process. The program PROG_136 defines functional modules of the configuration device 130, which rely on or control the hardware elements 131 to 135 of the configuration device 130 mentioned above, and which are described in more detail below with reference to different implementation methods.

[0100] The communication means 135 enable the configuration device 130 to exchange data with any entity in the NET 5G network, including entities 110 and 120 of set E. For this purpose, the communication means 135 may, for example, include a computer data bus capable of transmitting said data. Alternatively, said data may be transmitted via a wired or wireless communication interface capable of implementing any suitable protocol known to those skilled in the art.

[0101] It is important to note that the representation of the hardware architecture of device 130, following the example in Figure 3, corresponds to a generic computer hardware architecture. As such, all other devices / entities / terminals described below in relation to the different phases of the invention and which implement at least one step of a process have, in the embodiment described here, a hardware architecture of the same type as that represented in Figure 3. Consequently, the hardware architectures of these other devices / entities / terminals are not shown in dedicated figures.

[0102] The peripheral node 110 has the hardware architecture of a computer and includes, in particular, a processor 111, a random access memory 112, a read-only memory 113 and a non-volatile memory 114. It also has means of communication 115.

[0103] The read-only memory 113 of the peripheral node 110 constitutes a recording medium according to the invention, readable by the processor 111 and on which a computer program PROG_116 according to the invention is recorded, comprising instructions for the execution of steps in the receiving process. The PROG_116 program defines functional modules of the peripheral node 110, which rely on or control the hardware elements 111 to 115 of the peripheral node 110 mentioned previously, and which are described in more detail below with reference to different implementation modes.

[0104] The communication means 115 enable the peripheral node 110 to exchange data with the configuration device 130. For this purpose, the communication means 115 may, for example, include a computer data bus capable of transmitting said data. Alternatively, said data may be transmitted via a wired or wireless communication interface capable of implementing any suitable protocol known to those skilled in the art.

[0105] The DHCP server 120 has the hardware architecture of a computer. Thus, the DHCP server 120 includes, in particular, a processor 121, RAM 122, ROM 123 and non-volatile memory 124. It also has communication means 125.

[0106] The read-only memory 123 of the DHCP server 120 constitutes a storage medium according to the invention, readable by the processor 121, on which is stored a computer program PROG_126 according to the invention, comprising instructions for executing steps in the reception process. The PROG_126 program defines functional modules of the DHCP server 120, which rely on or control the hardware elements 121 to 125 of the DHCP server 120 mentioned above, and which are described in more detail below with reference to different implementation methods.

[0107] The communication means 125 enable the DHCP server 120 to exchange data with the configuration device 130. For this purpose, the communication means 125 may, for example, include a computer data bus capable of transmitting said data. Alternatively, said data may be transmitted via a wired or wireless communication interface capable of implementing any suitable protocol known to those skilled in the art.

[0108] Figure 4 represents, in flowchart form, a particular implementation method of a first general process 1000 implemented by the SYS_1 system. This process 1000 encompasses the configuration process according to the invention implemented by the configuration device 130 of Figure 3, as well as the processes of reception according to the invention respectively implemented by the peripheral node 110 and the DHCP server 120.

[0109] As illustrated in Figure 4, the process 1000 first comprises a step 1100 for generating a number M of connection elements. This step 1100 is implemented by a MOD GEN 130 generation module fitted to the configuration device 130, and forms part of the configuration process.

[0110] More specifically, in the implementation described here, the number M is equal to 3. The three connection elements are respectively denoted ELE CX 1, ELE CX 2, and ELE CX 3 for the remainder of this description. Each of these ELE CXJ connection elements is configured to allow obtaining at least one connection identifier.

[0111] It is important to note that a connection identifier obtained from an ELE CXJ connection element constitutes additional reachability information in addition to usual reachability information such as an IP address, a default route, etc. As such, a connection identifier is intended to be used at the transport layer and / or the application layer of the OSI model ("Open Systems Interconnection" in English) during communication via one or more network slices supported by the NET 5G network (the communication concerned here is a communication between two terminals intended to be carried out during the fourth phase mentioned above, and it being understood that a connection identifier is therefore not specific to a terminal, i.e., it is not unique per terminal and does not allow reaching a remote terminal).

[0112] The connection identifiers obtainable from each of the aforementioned connection elements ELE CX 1, ELE CX 2, ELE CX 3 are distinct from the ID TR 1, ID TR 2, ID TR 3 identifiers used by the slices to mark data packets routed through the TR_5G_1, TR_5G_2, TR_5G_3 slices. This difference between connection identifier and TR 5GJ slice identifier stems from the use of connection identifiers to properly route data packets between two terminals, as described in detail later.

[0113] There are no limitations attached to the structure or size of a login identifier. Thus, each login identifier can be encoded using a given number of bits, for example, 64 bits. In a more specific example of implementation... In practice, a connection identifier is a "CID" type identifier ("Connection ID" in English) used by the QUICK protocol or the DTLS protocol (see, for example, the information provided in RFC 9000 and 9146 for these two protocols). These provisions can also apply to connection elements.

[0114] In the context of the present invention, there are different possible configurations for an ELE CXJ connection element. Thus, and according to a particular example of implementation, an ELE CXJ connection element is a pattern configured to impose, among the sequence of bits forming a connection identifier, the value of at least one bit having a given position within said sequence of bits.

[0115] For illustrative purposes, consider that the identifiers obtainable by a connection element each correspond to a sequence of 10 bits. Furthermore, consider, as a connection element, a pattern configured to impose the values ​​1, 1, 0, and 1 for the bits located in the second through fifth positions (considering a left-to-right bit traversal) within this sequence of 10 bits forming a connection identifier. In this way, the pattern allows for obtaining a plurality of connection identifiers, such as: 111011 1111, 0110111111, etc.

[0116] There is no limit to the number of bits for which a pattern assigns given values, except that this number is strictly less than the total number of bits forming a connection identifier. Furthermore, there is no limit to the respective positions of the bits to which values ​​are assigned within the sequence of bits forming a connection identifier.

[0117] According to another specific implementation example, an ELE CX J connection element is a set comprising at least one given connection identifier. Such a set may, for example, be ordered (according to any known ordering relation) or not. Furthermore, in the case where at least two connection elements correspond to sets of given connection identifiers, said at least two sets may be contiguous with respect to an ordering relation used to order each of them.

[0118] 11. It should be noted that the size (i.e., the cardinality) of a given set of connection identifiers does not constitute a limitation of the invention. Furthermore, two such sets may have identical or different sizes.

[0119] It follows from the above that a login identifier is said to be "compliant" with an ELE CX J login element when: - the bit sequence forming said connection identifier includes, at the appropriate positions, the values ​​imposed by said connection element ELE CXJ if the latter is a pattern, or - said connection identifier is part of the identifiers listed in a given set of connection identifiers if said connection element ELE CX J is such a set.

[0120] Once the ELE CX 1, ELE CX 2, and ELE CX 3 connection elements have been generated, process 1000 includes a step 1200 for associating at least one connection element with each network slice TR_5G_1, TR_5G_2, and TR_5G_3 based on a given association criterion. This step 1200 is implemented by an association module MOD_ASSO_130, which is part of the configuration device 130, and is an integral part of the configuration process.

[0121] More specifically, in the implementation described here, the association criterion consists of a given connection element being associated with a given network slice. Put another way, the association criterion establishes a one-to-one correspondence between the connection elements ELE CX 1, ELE CX 2, ELE CX 3 and the network slices TR_5G_1, TR_5G_2, TR_5G_3.

[0122] For the remainder of the description, we consider that for an index i between 1 and 3, the connecting element ELE CX J is associated with the slice TR 5GJ. Of course, nothing prevents us from considering other bijective associations.

[0123] In practice, the association between ELE CX J connection elements and TR 5GJ slices is achieved by populating a table TAB 1, which lists the correspondences between the ELE CX J connection elements and the ID TR J identifiers respectively associated with said TR 5GJ slices. This table TAB 1 is stored by the configuration device 130, for example in its non-volatile memory 134. In this implementation, the table TAB 1 also contains the correspondences between the ID TR J identifiers respectively associated with said TR 5GJ slices and the respective types of these slices.

[0124] The process 1000 then includes a data transmission step 1300 indicating the associations between ELE CX J connection elements and TR 5GJ network slices to the set E of NET 5G network entities configured to participate in The routing of data packets within said NET 5G network. Said step 1300 is implemented by a MOD TX 130 transmission module equipping the configuration device 130, and is part of the configuration process. Said MOD TX 130 transmission module is more specifically integrated into the communication means 135.

[0125] In the present implementation mode, and as illustrated by Figure 4, said data transmission of step 1300 more specifically includes a transmission of the TAB 1 table to the edge node 110 as well as to the DHCP server 120.

[0126] Subsequently, process 1000 includes a step 1400 of reception by the peripheral node 110 of said data indicating the associations between ELE CX J connection elements and TR 5GJ network slices (i.e., reception of table TAB 1). This step 1400 is implemented by a MOD RX 110 receiving module equipping the peripheral node 110, and is part of the reception process executed by said peripheral node 110. This MOD RX 110 receiving module is more specifically integrated into the communication means 115.

[0127] Similarly, process 1000 includes a step 1500 of reception by the DHCP server 120 of said data indicating the associations between the ELE CXJ connection elements and the TR 5GJ network slices (i.e., reception of the TAB 1 table). This step 1500 is implemented by a MOD RX 120 reception module equipping the DHCP server 120, and is part of the reception process executed by said DHCP server 120. This MOD RX 120 reception module is more specifically integrated into the communication means 125.

[0128] Once the TAB 1 table is received by the peripheral node 110 and the DHCP server 120, they store it in their respective non-volatile memories 114, 124.

[0129] It is important to note that process 1000, and more specifically the configuration process, is described here considering a bijective association between ELE CX J connecting elements and TR 5GJ slices, which implies that the numbers N and M are equal (in this case, N = M = 3). However, it is possible to consider other implementation methods in which the numbers N and M differ, which then impacts the associations that can be made between ELE CX J connecting elements and TR 5GJ slices.

[0130] Thus, according to one variant, the number M of connecting elements can be greater than the number N of slices. In this way, one or more slices can be associated with more than one connecting element. In this case, and purely for illustrative purposes, the association criterion could, for example, consist of iterating through the first N connecting elements (assuming they are ordered according to a specific order) and associating them respectively with the N slices (also assuming they are ordered according to a specific order). Then, the remaining MN connecting elements are associated, for example, with the first MN slices. In this way, the first MN slices are each associated with two connecting elements, and the last N slices are each associated with a single connecting element.

[0131] Furthermore, it should be noted that the first phase of the invention has been described so far assuming that each of the N slices supported by the NET 5G network is associated with at least one connection element. However, nothing precludes considering other implementations in which only a portion of the N network slices is configured according to method 1000, while the remaining slices are used, for example, to carry internal traffic specific to the network operator (i.e., the slices in said remaining portion are not associated with connection elements). A second variant then follows in which the number M of connection elements can be less than the number N of slices.

[0132] Second phase

[0133] Figure 5 schematically represents a SYS_2 data processing system according to a particular embodiment of the invention. As described below, the data processing in question consists, in particular, of establishing communications enabling the exchange of data between different entities.

[0134] As illustrated in Figure 5, the SYS_2 system includes a first terminal 210 and a second terminal 220. The SYS_2 system also includes the configuration device 130 of Figure 3 and the DHCP server 120.

[0135] It is important to note that the 5G NET network shown in Figure 5 is the one resulting from the execution of process 1000 of the first phase. In other words, With regard to this second phase, the NET 5G network is configured in a specific way, that is to say so that each TR 5GJ slice is associated with an ELE CXJ connection element, the entities of set E, therefore in particular the edge node 110 and the DHCP server 120, being aware of the associations via said table TAB 1.

[0136] It is also important to note that this second phase is independent of the third phase, which involves establishing communications between terminals connected to the network. In other words, the triggering of the second phase is not contingent upon that of the third phase.

[0137] The first terminal 210 is a user terminal (i.e., a terminal operated by a user). For example, it could be a landline or mobile phone, such as a smartphone, a tablet, a laptop, a personal digital assistant (PDA), a smartwatch, an e-reader, etc. It could also be a CPE (Customer-Premises Equipment) type entity. Generally speaking, there are no limitations on the nature of the user terminal 210.

[0138] The second 220 terminal, on the other hand, is an application server. As is well known, the 220 application server is configured to provide one or more service functions (known as "Service Functions" in RFC 7665, or "Network Functions" such as gNBs or UPFs, according to 3GPP terminology). A single service function can be provided by one or more service instances. A service instance can be hosted by the SSP (Slice Service Provider) or within another infrastructure.

[0139] It should be noted that, in the embodiment described here with reference to Figure 5, it is considered, without limitation, that the user terminal 210 and the application server 220 are connected only to the NET 5G network. However, these provisions do not limit the invention, and nothing precludes the user terminal 210 and / or the application server 220 from being connected to several other networks. These other networks may, in particular, include networks supporting network slices, and at least some (or even all) of them may be configured in accordance with the first phase.

[0140] The fact that the user terminal 210 and the application server 220 are connected to the NET 5G network results, for example, from a subscription of these terminals 210, 220 to a service offer from the network operator in charge of managing said NET 5G network, so as to be able to use one or more of the network slices supported by this network.

[0141] In any event, in this embodiment, the user terminal 210 (or application server 220) is authorized (enabled) to connect to at least one of the following slices: TR_5G_1, TR_5G_2, TR_5G_3. This authorization (enablement) depends on the user terminal 210's (or application server 220's) access rights to the NET 5G network, as configured when subscribing to a service offer. The slice(s) to which the user terminal 210 (or application server 220) is authorized (enabled) to connect are referred to as the "authorized slice(s)".

[0142] There is no limitation attached to the number of slices to which the user terminal 210 (respectively the application server 220) is allowed to connect, this aspect may for example depend on the service offer subscribed to.

[0143] For the remainder of the description, it is considered in a non-limiting manner that the slices to which the user terminal 210 (respectively the application server 220) is authorized to connect are the slices TR_5G_1, TR_5G_2 (respectively the slices TR_5G_2, TR_5G_3).

[0144] The user terminal 210 is configured to perform processing enabling it to discover the specific configuration of the NET 5G network resulting from the first phase, by implementing steps of a first variant of a first data processing method according to the invention.

[0145] More specifically, the discovery of this specific NET 5G network configuration by user terminal 210 is achieved through data exchanges with DHCP server 120. Also, in addition to the configuration already described above in the first phase, DHCP server 120 is also configured to carry out said data exchanges with user terminal 210, by implementing a first variant of a second data processing method according to the invention.

[0146] For this purpose, the user terminal 210 has the hardware architecture of a computer. Thus, the user terminal 210 includes, in particular, a processor 211, RAM 212, ROM 213 and non-volatile memory 214. It also has communication means 215.

[0147] The read-only memory 213 of the user terminal 210 constitutes a storage medium according to the invention, readable by the processor 211, on which is stored a computer program PROG_216 according to the invention, comprising instructions for executing steps of the first variant of the first data processing method. The program PROG_216 defines functional modules of the user terminal 210, which rely on or control the hardware elements 211 to 215 of the user terminal 210 mentioned above, and which are described in more detail below with reference to different implementation methods.

[0148] The communication means 215 enable the user terminal 210 to exchange data with entities on the 5G network, including the DHCP server 120. For this purpose, the communication means 215 may, for example, include a computer data bus capable of transmitting said data. Alternatively, said data may be transmitted via a wired or wireless communication interface capable of implementing any suitable protocol known to those skilled in the art.

[0149] Furthermore, the read-only memory 123 of the DHCP server 120 stores, in addition to the computer program PROG_126, another program PROG_127 according to the invention, comprising instructions for executing steps of the first variant of the second data processing method. The program PROG_127 defines functional modules of the DHCP server 120, which rely on or control the hardware elements 121 to 125 of the DHCP server 120, and which are described in more detail below with reference to different implementation methods. Moreover, the communication means 125 allow the DHCP server 120 to exchange data with the user terminal 210 according to any technical characteristics conceivable by a person skilled in the art, such as those already described above.

[0150] Unless otherwise stated, the remainder of the description aims to detail the implementation methods of the aforementioned first variants of the first and second data processing methods as executed respectively by the user terminal 210 and the DHCP server 120. Nevertheless, the invention also covers other variants of the first and second data processing methods, these other variants being executed respectively by the application server 220 and the configuration device 130. These aspects are detailed later.

[0151] Figure 6 represents, in the form of a flowchart, a particular method of implementing a second general process 2000 implemented by the SYS_2 system. Said process 2000 encompasses the first variants of the first and second data processing processes according to the invention respectively implemented by the user terminal 210 and the DHCP server 120.

[0152] As illustrated in Figure 6, process 2000 begins with a step 2100 in which the user terminal 210 transmits a REQ request to the DHCP server 120, requesting at least one connection element. This step 2100 is implemented by a MOD TX 210 transmission module installed on the user terminal 210 and is part of the first variant of the first data processing method. This MOD TX 210 transmission module is specifically integrated into the communication means 215.

[0153] To obtain at least one connection element, and according to a first implementation example, the REQ request can include at least one PAR CX parameter corresponding to a slice identifier or a slice type (e.g. enhanced mobile broadband service, massive deployment of the Internet of Things, ultra-reliable and low-latency communications) to which the terminal is authorized to connect.

[0154] In this case, and if the PAR CX parameter corresponds to a slice identifier to which the terminal is authorized to connect, it may be ID TR 1 or ID TR 2 since the authorized slices associated with user terminal 210 are TR_5G_1, TR_5G_2 slices.

[0155] Of course, nothing prevents us from considering that the request may include a plurality of parameters, each of said parameters corresponding to a slice identifier or a slice type to which the terminal is authorized to connect.

[0156] Furthermore, there are no limitations on how said at least one PAR CX parameter is inserted into the REQ query. For example, said at less a PAR CX parameter can be inserted into the body or header of the REQ query, for example in a specific field.

[0157] The said REQ request can, for example, be integrated into a request to obtain an IP address or IP prefix from the DHCP server. In other words, the said at least one PAR CX parameter can be seen as a new DHCP option configured to be inserted into such a request for the assignment of an IP address or IP prefix.

[0158] In a second implementation example, the REQ request does not include a parameter corresponding to a slice identifier or a slice type to which the terminal is authorized to connect. In other words, in this second implementation example, the REQ request is a general order request to obtain at least one connection element; this general order request contains no indication (information, pointer) relating to the network slices supported by the NET 5G network.

[0159] The DHCP server then receives said REQ request during a step 2200 of process 2000. Said step 2200 is implemented by the MOD RX 120 receive module equipping the DHCP server 120, and is part of the first variant of the second data processing process.

[0160] Process 2000 then includes a step 2300 of transmission, from the DHCP server 120 to the user terminal 210, of a REP REQ response to said REQ request. Said step 2200 is implemented by an MQD TX 120 transmission module equipping the DHCP server 120, and is part of the first variant of the second data processing process.

[0161] The REP REQ response includes at least one connection element associated with at least one slice of the NET 5G network. It should be noted that, following considerations similar to those described above regarding the insertion of said at least one PAR CX parameter into the REQ request, said at least one connection element may be inserted in the body or header of the REP REQ response, for example, in a specific field. The REP REQ response may optionally include connectivity information from terminal 210, such as an IP address or an IP prefix.

[0162] More specifically, the at least one connection element inserted in the REP REQ response depends on the content of the REQ query.

[0163] Thus, if we consider the first implementation example in which the REQ query includes at least one PAR CX parameter, the REP REQ response then includes at least one connection element associated with a slice itself associated with said identifier defined by said at least one PAR CX parameter or with a slice of said type defined by said at least one PAR CX parameter.

[0164] For example, if the REQ request includes a PAR CX parameter corresponding to the ID TR 1 identifier of the TR_5G_1 slice authorized for user terminal 210, the REP REQ response then includes the connection element ELE CXJ associated with the TR 5GJ slice thus identified by said ID TR 1 identifier. To find said connection element ELE CX 1 based on the ID TR 1 identifier, the DHCP server 120 uses the TAB 1 table obtained following the execution of the first phase.

[0165] In another scenario, if the PAR CX parameter is a slice type, the REP REQ response will include at least one ELE CXJ connection element associated with the TR 5GJ slice(s) (i can be either 1 or 2 here) of that type. For example, if the TR 5G and TR_5G_2 slices are both of the same type, and that type is the one designated by the PAR CX parameter, the REP REQ response may include the ELE CX 1 connection element and / or the ELE CX connection element. However, if the TR 5G and TR_5G_2 slices are of different types, and the type designated by the PAR CX parameter is that of the TR_5G_1 slice, then the REP REQ response will only include the ELE CX 1 connection element. To retrieve an ELE CXJ connection element based on a slice type, the DHCP server 120 uses the TAB 1 table obtained after the execution of the first phase.

[0166] Alternatively, if we now consider the second implementation example in which the REQ request does not include a parameter corresponding to a slice identifier or slice type to which terminal 210 is authorized to connect, then the REP REQ response includes at least one connection element associated with at least one slice to which user terminal 210 is authorized to connect.

[0167] The said minimum connection element may, for example, correspond to the set of ELE CX 1, ELE CXJ connection elements associated with the slices to which the user terminal 210 is authorized to connect.

[0168] Alternatively, said at least one connection element can be selected by the DHCP server 120 based on a given selection criterion.

[0169] As a non-limiting example, the selection criterion consists of a random selection between the connection elements ELE CX 1, ELE CX 2. According to another example, the selection criterion may depend on a more specific access rights policy defined at the DHCP server level. In general, there are no limitations attached to the way in which the selection criterion is defined.

[0170] It should be noted that if the REQ query has multiple parameters, including at least one parameter corresponding to a slice identifier and at least one parameter corresponding to a slice type, different rules can be considered to determine the content of the REP REQ response. For example, one rule might require that the REP REQ response contain all possible connection elements (i.e., connection elements associated with that identifier and / or associated with that type). As another example, a rule might require that a connection element in the REP REQ response must match both that identifier and that type.

[0171] Process 2000 ultimately includes a step 2400 for receiving the REP REQ response from the DHCP server 120, via the user terminal 210. This step 2400 is implemented by an MQD RX 210 receiver module installed on the user terminal 210 and is part of the first variant of the first data processing method. This MQD RX 210 receiver module is specifically integrated into the communication means 215.

[0172] The content of the REP REQ response is stored in the non-volatile memory 214 of the user phone 210, for example, as a table TAB 210. This TAB 210 table lists connection elements associated with network slices. The connection elements contained in this TAB 210 table can then be shared with software applications hosted by the user terminal 210, so that these applications can transmit data on the NET 5G network with connection identifiers that correspond to the connection elements in the TAB 210 table, as described in detail later. Sharing these connection elements with the software applications is achieved, for example, through an application programming interface (API) of a type known per se.

[0173] It should be noted that, according to other embodiments, the REP REQ response to the REQ request may include, in addition to one or more connection elements, a NET 5G network identifier. These provisions are advantageous insofar as the user terminal 210 has the possibility of being connected to other networks, including other networks supporting network slices. Therefore, including such a NET 5G network identifier allows the user terminal 210 to correctly associate the received connection elements with the appropriate network slices.

[0174] For example, user terminal 210 can maintain a single table, TAB 210, which then includes an entry allowing the user to distinguish, using network identifiers, the networks to which said user terminal 210 can connect. Alternatively, user terminal 210 can maintain multiple tables, for example, one table for each network to which it can connect.

[0175] The 2000 process has been described so far by considering that the user terminal 210 exchanges data with the DHCP server 120 to obtain connection elements associated with slices supported by the NET 5G network. However, nothing excludes considering that the 2000 process is implemented on the basis of data exchanges between the user terminal 210 and another entity of the network belonging to set E.

[0176] Furthermore, and as mentioned above, the invention also covers second variants of said first and second data processing methods, these second variants being respectively executed by the application server 220 and an orchestration device configured to manage service functions within said at least one network (e.g. a network orchestrator or an SDN controller), this role being played here by the configuration device 130.

[0177] The application server 220 has the hardware architecture of a computer. Thus, the application server 220 includes, in particular, a processor 221, RAM 222, ROM 223 and non-volatile memory 224. It also has communication means 225.

[0178] The read-only memory 223 of the application server 220 constitutes a storage medium according to the invention, readable by the processor 211, and on which is stored a computer program PROG_226 according to the invention, comprising instructions for executing steps of the second variant of the first method data processing. The PROG_226 program defines functional modules of the application server 220, which rely on or control the hardware elements 221 to 225 of the application server 220 mentioned previously, and which are described in more detail below with reference to different implementation modes.

[0179] The communication means 225 enable the application server 220 to exchange data with the configuration device 130. For this purpose, the communication means 225 may, for example, include a computer data bus capable of transmitting said data. Alternatively, said data may be transmitted via a wired or wireless communication interface capable of implementing any suitable protocol known to those skilled in the art.

[0180] Furthermore, as illustrated in Figure 3, the read-only memory 133 of the configuration device 130 stores, in addition to the computer program PROG_136, another program PROG_137 according to the invention, comprising instructions for executing steps of the second variant of the second data processing method. The program PROG_137 defines functional modules of the configuration device 130, which rely on or control the hardware elements 131 to 135 of the configuration device 130. These functional modules are also illustrated in Figure 3, but not exclusively, and are described in more detail below with reference to different implementation methods. Moreover, the communication means 135 allow the configuration device 130 to exchange data with the application server 220 according to any technical characteristics conceivable by a person skilled in the art, such as those already described above.

[0181] It is therefore possible to define a third general process 3000 (not illustrated by the figures) implemented by the SYS_2 system. Said process 3000 encompasses the second variants of the first and second data processing processes according to the invention respectively implemented by the application server 220 and the configuration device 130 of figure 3.

[0182] The implementation of process 3000 is similar to that of process 2000, except that the application server 220 (or configuration device 130) here plays the role of the user terminal 210 (or DHCP server 120). Consequently, process 3000 comprises: - a transmission step 3100 and a reception step 3400 respectively similar to steps 2100 and 2400. Said steps 3100 and 3400 are respectively implemented by a MOD TX 220 transmission module and a MOD RX 220 reception module equipping the application server 220, and are part of the second variant of the first data processing method; - a 3200 reception step and a 3300 transmission step respectively similar to steps 2200 and 2300. Said steps 3200 and 3200 are respectively implemented by a MOD RX 130 reception module and the MOD TX 130 transmission module equipping the configuration device 130, and are part of the second variant of the second data processing method.

[0183] It should be noted that, since the application server 220 exchanges data with the configuration device 130, the REQ request transmitted during step 3100 is not a request to obtain an IP address, as was the case in the example of process 2000. In process 3000, this REQ request is, for example, a request to subscribe to a service enabling the use of one or more of the network slices supported by the NET 5G network.

[0184] In general, all the technical characteristics described above within the framework of process 2000 and which are compatible with the implementation of process 3000 still apply within the framework of the latter. In particular, the content of the REP REQ response is stored in the non-volatile memory 224 of the application server 220, for example in the form of a table TAB 220 comprising one or more connection elements.

[0185] Third phase

[0186] Figure 7 schematically represents a SYS_3 communication system according to a particular embodiment of the invention.

[0187]

[0188] It is important to note that the NET 5G network shown in Figure 7 is the one resulting from the execution of process 1000 of the first phase. In other words, with regard to this third phase, the NET 5G network is configured in a specific way, that is, so that each TR 5GJ slice is associated with an ELE CXJ connection element.

[0189] As illustrated in Figure 7, the SYS_3 system comprises a first terminal 310 and a second terminal 320.

[0190] More specifically, we assume here that terminal 310 acts as a client and terminal 320 as a server in a communication intended to be established between them. The purpose of this communication is to allow client terminal 310 to use, within the framework of a service offering subscribed to by the user of said client terminal 310, a given application function (e.g., use of an augmented or virtual reality function) provided by server terminal 320.

[0191] For the remainder of the description, and purely for illustrative purposes, we consider that the NET 5G network slices allowing the exploitation of said application function are the TR_5G_1 and TR_5G_2 slices. More specifically, the TR_5G_1 slice (respectively the TR_5G_2 slice) is associated with the management of video aspects (respectively voice aspects) of said application function.

[0192] It is further assumed that client terminal 310 has undergone the execution of process 2000 of the second phase. In other words, client terminal 310 has stored a TAB 310 table containing connection elements relating to one or more bands supported by the NET 5G network. More specifically, it is assumed that: - Following the execution of process 2000 of the second phase, the client terminal 310 received the connection elements ELE CX 1, ELE CX 2, ELE CX 3, and - at the start of said third phase, the client terminal 310 is connected to the TR_5G_1, TR_5G_2, TR_5G_3 slices. For these reasons, said TR_5G_1, TR_5G_2, TR_5G_3 slices are referred to below as "active" slices.

[0193] 11. It is important to note, however, that the invention is not limited by the fact that the active slices correspond to all the slices for which the client terminal 310 has connection elements. Thus, the active slices to which the client terminal 310 is connected during the third phase may correspond to a subset of the slices for which the client terminal 310 has connection elements. Whether the client terminal 310 is connected to a particular slice at the beginning of the third phase depends, for example, on options to which a customer, a user of the terminal 310, has subscribed as part of a service offering.

[0194] As for the 320 server terminal, and insofar as it is configured to provide the said application function, it has the ELE CX 1 and ELE CX 2 connection elements respectively associated with the TR_5G_1 and TR_5G_2 bands. It should be noted that the 320 server terminal can be connected directly to the NET 5G network or directly to a network other than the said NET_5G network while of course being reachable via the said NET 5G network.

[0195] 11. It should be noted that the provisions according to which the client terminal 310 was subjected to an execution of process 2000 of the second phase are not limiting to the invention. Indeed, nothing precludes the possibility that the client terminal 310 acquired the connection elements ELE CX 1, ELE CX 2, ELE CX 3 in another way. For example, these elements may have been written to the memory of the client terminal 310 during its manufacture. Following similar considerations, no limitation is attached to the way in which the server terminal 320 acquires the connection elements ELE CX 1, ELE CX 2.

[0196] For the remainder of this description, and insofar as both client terminal 310 and terminal 320 possess connection elements, these terminals are referred to as "candidate" terminals. As detailed below, this terminology refers to the fact that each of said terminals 310 and 320 is a potential candidate for designation as the terminal capable of compelling the other terminal to use certain connection elements it possesses to communicate via the NET 5G network. In any event, the invention is not limited by the fact that both client terminal 310 and server terminal 320 are candidate terminals, as will be described later through alternative embodiments.

[0197] The client terminal 310 (respectively the server terminal 320) is configured to perform processing enabling communication with the server terminal 320 (respectively with the client terminal 310) supported by one or more of the active TR_5G_1, TR_5G_2 and TR_5G_3 slices, by implementing a first variant of a first communication method according to the invention (respectively a first variant of a second communication method according to the invention).

[0198] To this end, the 310 client terminal has the hardware architecture of a computer. The 310 client terminal includes, in particular, a 311 processor, a RAM 312, ROM 313 and non-volatile memory 314. It also has means of communication 315.

[0199] The read-only memory 313 of the client terminal 310 constitutes a recording medium according to the invention, readable by the processor 311 and on which is recorded: - a computer program PROG_316 according to the invention, comprising instructions for the execution of steps of the first variant of the first data processing method (given that it is assumed here that the client terminal 310 has been subjected to an execution of the 2000 method of the second phase), - a computer program PROG_317 according to the invention, comprising instructions for the execution of steps of the first variant of the first communication method.

[0200] The PROG_317 program defines functional modules of the client terminal 310, which rely on or control the hardware elements 311 to 315 of the client terminal 310 mentioned above, and which are described in more detail below with reference to different implementation methods.

[0201] The communication means 315 enable the client terminal 310 to exchange data with the server terminal 320. For this purpose, the communication means 315 may, for example, include a computer data bus capable of transmitting said data. Alternatively, said data may be transmitted via a wired or wireless communication interface capable of implementing any suitable protocol known to those skilled in the art.

[0202] By way of non-limiting example, the exchanges between the first terminal 310 and the second terminal 320, as described below, are based on the QUIC protocol. These exchanges include, in particular, the sending and receiving of data that can be encapsulated in existing QUIC frames or new frames specifically defined for the implementation of the invention.

[0203] The server terminal 320 also has the hardware architecture of a computer. Thus, the user terminal 320 includes, in particular, a processor 321, RAM 322, ROM 323 and non-volatile memory 324. It also has communication means 325.

[0204] The read-only memory 323 of the server terminal 320 constitutes a recording medium according to the invention, readable by the processor 321 and on which is recorded a computer program PROG_327 according to the invention, comprising instructions for the execution of steps of the first variant of the second communication method.

[0205] The PROG_327 program defines functional modules of the server terminal 320, which rely on or control the hardware elements 321 to 325 of the user terminal 320 mentioned previously, and which are described in more detail below with reference to different implementation modes.

[0206] The communication means 325 enable the server terminal 320 to exchange data with the client terminal 310 according to characteristics similar to those described above for the communication means 315 of the client terminal 310.

[0207] Figure 8 represents, in flowchart form, a particular method of implementing a fourth general method 4000 implemented by the SYS_3 system. Said method 4000 encompasses the first variants of the first and second communication methods according to the invention respectively implemented by the client terminal 310 and the server terminal 320 of.

[0208] The 4000 process begins with a step 4050, in which the client terminal 310 transmits a DATA_I NFO_310 configured to the server terminal 320, informing the server terminal 320 that the client terminal 310 is capable of communicating using at least one of the network segments supported by the NET 5G network. This step 4050 is implemented by the MOD TX 310 transmission module installed on the client terminal 310 and is part of the first variant of the first communication process.

[0209] It should be noted that the said data DATA_I NFO_310 has the sole purpose of informing the server terminal 320 that the client terminal 310 has the possibility of communicating via one or more slices supported by the NET 5G network, and as such does not include connection elements.

[0210] There are no limitations on how said DATA_I NFO_310 is transmitted to the server terminal 320. For example, said DATA_I NFO_310 can be encapsulated in a frame, for example a control frame or a data frame.

[0211] Furthermore, the nature of said data DATA_I NFO_310 is not a limitation of the invention, the latter being able to be a numeric parameter or predetermined text representing the fact that the client terminal 310 supports communication via network slices.

[0212] The server terminal 320 then receives said data DATA_I NFO_310 during a step 4100 of the process 4000. Said step 4100 is implemented by the receiving module MOD RX 320 equipping the server terminal 320, and is part of the first variant of the second communication process.

[0213] The 4000 process then includes a step 4150 of transmission, from the server terminal 320 to the client terminal 310, of a DATA_I NFO_320 indicating that the server terminal 320 is also capable of communicating by exploiting at least one of the network segments supported by the NET 5G network. This step 4150 is implemented by the MOD TX 320 transmission module equipping the server terminal 320, and is part of the first variant of the second communication process.

[0214] The client terminal 310 then receives said data DATA_I NFO_320 during a step 4200 of the process 4000. Said step 4200 is implemented by the receiving module MOD RX 310 equipping the client terminal 310, and is part of the first variant of the first communication process.

[0215] It should be noted that the execution of steps 4050 and 4100 is optional within the meaning of the present invention. Indeed, there is nothing to preclude the possibility that terminals 310 and 320 may have acquired knowledge of their respective capabilities to communicate via one or more segments supported by the NET 5G network before process 4000 is executed.

[0216] The process 4000 further includes a step 4250 of obtaining, by the client terminal 310, a D AT A PRI MARY data designating a terminal, called the "primary terminal", among the terminal 310 and the server terminal 320 which are, as mentioned above, both candidate terminals.

[0217] The role of "primary terminal" played by a terminal indicates that this terminal is designated to impose the connection elements to be used by the other terminal. to generate connection identifiers intended for use during exchanges between said two terminals via slices supported by the NET 5G network, as described below.

[0218] In this implementation, the achievement of step 4250 corresponds more specifically to the generation, by client terminal 310, of the data DAT A PRI MARY. Consequently, step 4250 is implemented by a first generation module MOD GEN 310 equipping client terminal 310, and is part of the first variant of the first communication method.

[0219] Once generated, the DAT A PRI MARY data is transmitted by the client terminal 310 to the server terminal 320 during a step 4300 of the process 4000. Said step 4300 is implemented by the MOD TX 310 transmission module equipping the client terminal 310, and is part of the first variant of the first communication process.

[0220] There are no limitations on how the DAT A PRI MARY data is transmitted to the server terminal 320. For example, the DAT A PRI MARY data may be encapsulated in a frame, such as a control frame or a data frame. Furthermore, the nature of the DAT A PRI MARY data is not a limitation of the invention; it may be a numeric parameter or predetermined text indicating that one of the two terminals 310 or 320 is designated as the primary terminal.

[0221] For example, if the DATA PRI MARY data is the value "0x01" (respectively the value "0x02"), this means that the server terminal 320 (respectively the client terminal 310) is designated as the master terminal.

[0222] The server terminal 320 then receives the said data DAT A PRI MARY during a step 4350 of the process 4000. Said step 4350 is implemented by the MOD RX 320 receiving module equipping the server terminal 320, and is part of the first variant of the second communication process.

[0223] It should be noted that although it is described here that the DATA PRI MARY data is generated by the client terminal 310 and then transmitted to the server terminal 320, nothing excludes the possibility that the server terminal 320 generates the DATA PRI MARY data and transmits it to the client terminal 310.

[0224] In general, the designation of the primary terminal can be based on a given designation criterion. Since client terminal 310 and server terminal 320 are both candidate terminals in this implementation, this designation criterion could, for example, be a rule (e.g., a rule imposed by a service policy) requiring that the primary terminal always be either client terminal 310 or server terminal 320. Thus, even if one of these candidate terminals declares its intention to act as the primary terminal, the outcome of the designation may ultimately depend on the application of such a rule, rendering the declaration ineffective and the other candidate terminal ultimately being designated as the primary terminal.

[0225] Furthermore, although this implementation describes the DAT A PRI MARY data being generated and transmitted after the DATA_I NFO_310 and DATA_I NFO_320 data have been exchanged between terminals 310 and 320, there is no precluding the possibility that the DAT A PRI MARY data could be transmitted jointly with one of the aforementioned DATA_I NFQ_210 and DATA_I NFO_320 data. For example, this data could be included in respective fields of the same message. More specifically, if such a message is used to transmit this data, and if the field dedicated to the DAT A PRI MARY data is empty, this could, for example, mean that a given terminal among the terminals 310 and 320 is automatically designated as the primary terminal. This automatic designation might stem from a rule related to a service policy.

[0226] The first alternatives of the aforementioned first and second communication methods aim more specifically at designating the server terminal 320 as the master terminal. In other words, it is the server terminal 320 that is designated to require the client terminal 310 to use login credentials conforming to certain connection elements.

[0227] Therefore, process 4000 includes a step 4400 of transmission, from the client terminal 310 to the server terminal 320, of a list L ACTIV containing identifiers and / or types of the active slices (the slice type can also be designated by an identifier) ​​to which said client terminal 310 is connected. This step 4400 is implemented by the transmission module. MOD TX 310 equipping the 310 client terminal, and is part of the first variant of the first communication process.

[0228] There are no limitations attached to the way in which said L ACTIV list is transmitted to the server terminal 320. For example, the L ACTIV list can be encapsulated in a frame, for example a control frame or a data frame.

[0229] In this implementation method, and with regard to the elements described above, the L ACTIV list includes the identifiers ID TR 1, ID TR 2 and ID TR 3.

[0230] In practice, the transmission of this L ACTI V list aims to explicitly inform the server terminal 320 of the capabilities of the client terminal 310 to communicate via one or more segments supported by the NET 5G network.

[0231] The server terminal 320 then receives the L ACTIV list during a step 4450 of the process 4000. Once received, the L ACTIV list is stored by the server terminal 320. Said step 4450 is implemented by the MOD RX 320 receiving module equipping the server terminal 320, and is part of the first variant of the second communication process.

[0232] Then, process 4000 includes, for the server terminal 320, a step 4500 of selecting at least one connection element from among the connection elements it possesses. This step 4500 is implemented by a MOD_SELECT_320 selection module equipping the server terminal 320, and is part of the first variant of the second communication process.

[0233] This selection is made from among the ELE CX 1 connection elements, ELE CX 2 that the server terminal 320 has and that are associated with at least one of the active slices TR_5G_1, TR_5G_2, TR_5G_3 identified in the L ACTI V list that it received during step 4450.

[0234] In the present implementation mode, it is considered in a non-limiting manner that the server terminal 320 selects the two connection elements ELE CX 1, ELE CX 2.

[0235] Then, process 4000 includes, for the server terminal 320, a step 4550 of obtaining at least one connection identifier using the connection elements ELE CX 1, ELE CX 2 selected during step 4500. This step 4550 is implemented by a MOD OBT 320 acquisition module installed on the terminal. server 320, and is part of the first variant of the second communication method.

[0236] For the remainder of this description, we consider, without limitation, that the connection element ELE CX 1 is a pattern, and that the connection element ELE CX 2 is a set of given connection identifiers. We further consider that the server terminal 320 obtains a connection identifier ID CX 1 320 using the connection element ELE CX 1 (respectively, a connection identifier ID CX 2 320 using the connection element ELE CX 2).

[0237] In the current implementation method, and in accordance with what was described previously in relation to the first phase: - obtaining said connection identifier ID CX 1 320 involves generating said connection identifier ID CX 1 320 so that it conforms to the pattern corresponding to the connection element ELE CX 1, - obtaining said connection identifier ID CX 2 320 involves a selection of said connection identifier ID CX 2 320 from said set corresponding to the connection element ELE CX 2.

[0238] It is important to note, however, that obtaining a connection identifier that matches a connection element does not necessarily result from generation (in the case of a pattern) or selection (in the case of a set of given connection identifiers). Indeed, there is nothing to preclude the server terminal 320 from already possessing a connection identifier associated with one of the connection elements ELE CX 1 or ELE CX 2. This could result, for example, from a previous implementation of the invention, or from being stored in the server terminal 320's memory during its manufacture.

[0239] The connection identifiers ID CX 1 320, ID CX 2 320 thus constructed are intended to be used for all or part of the traffic emitted by the server terminal 320 and which is authorized to be routed via the TR_5G_1 , TR_5G_2 slices associated with the connection elements ELE CX 1 , ELE CX 2.

[0240] It should be noted that, in this case, two slices (i.e., slices TR_5G_1 and TR_5G_2) can be used for the same communication (due to the selection of connection elements ELE CX 1, ELE CX 2 by the 320 server terminal). However, in its broadest sense, the invention does not preclude the possibility of using a different number of slices, this number being able to be greater than or less than 2 (e.g., in step 4500, the server terminal 320 can select the single connection element ELE CX 1 or ELE CX 2). This number typically depends on the application function that one wishes to exploit.

[0241] For example, a QUIC connection can contain multiple "streams." Therefore, an application function relying on the use of different media (e.g., video, audio, text) can associate different streams for each of these media. Thus, messages from the same communication established over a network supporting network slices can be routed through several slices, each optimized for a specific use.

[0242] In addition, or as an alternative, the number of bandwidth slots used can also depend on a service optimization logic. For example, if two bandwidth slots are configured for routing specific content (e.g., video) within an application function, rules can be established to determine the extent to which each slot should be used.

[0243] Furthermore, the invention also covers configurations in which several connection identifiers can be used for the same slice during the lifetime of the same communication, these different identifiers being used each in turn.

[0244] The 4000 process also includes a 4600 step of transmission, from the server terminal 320 to the client terminal 310, of the connection elements ELE CX 1, ELE CX 2 selected by the server terminal 320 during the 4500 step. Said step 4600 is implemented by the MOD TX 320 transmission module equipping the server terminal 320, and is part of the first variant of the second communication process.

[0245] It should be noted that in addition to the ELE CX 1, ELE CX 2 connection elements, the server terminal 320 can transmit other data to the client terminal 310 during step 4600. For example, specific slice identifiers can also be transmitted, particularly in implementation modes where several "streams" as mentioned above are used at the same time.

[0246] The client terminal 310 then receives the connection elements ELE CX 1, ELE CX 2 during step 4650 of process 4000. Said step 4650 is implemented by the MOD RX 310 receiving module equipping the 310 client terminal, and is part of the first variant of the first communication method.

[0247] Similar to what was described above for the server terminal 320, the process 4000 includes, for the client terminal 310, a step 4700 for obtaining at least one connection identifier using the connection elements ELE CX 1 and ELE CX 2 (since these are the connection elements selected, and therefore required, by the server terminal to communicate in order to exploit the application function). This step 4700 is implemented by a MOD OBT 310 acquisition module installed on the client terminal 310 and is part of the first variant of the first communication process.

[0248] For the rest of the description, we consider in a non-limiting way that the client terminal 310 obtains a disconnection identifier ID CX 1 310 using the disconnection element ELE CX 1 (respectively a disconnection identifier ID CX 2 310 using the connection element ELE CX 2).

[0249] Ultimately, at the end of the third phase, terminals 310 and 320 are able to communicate with each other using the active TR_5G_1 and TR_5G_2 slices, associated with the application function. This is made possible by the connection identifiers ID_CX_1_310, ID_CX_2_310, ID_CX_1_320, and ID_CX_2_320, respectively obtained by the client terminal 310 and the server terminal 320. These identifiers can be inserted into data packets that terminals 310 and 320 wish to exchange via the appropriate slices. The management of such data packet traffic is implemented by the edge nodes of the NET 5G network, including edge node 110, as detailed later.

[0250] Besides the first variants of the said first and second communication methods described above, the invention also covers other variants of the said first and second communication methods.

[0251] Thus, according to another variant, client terminal 310 and server terminal 320 are both candidate terminals. However, unlike what was described for process 4000, client terminal 310 is designated as the primary terminal. In other words, client terminal 310 dictates to server terminal 320 the connection element(s) to be used to generate one or more connection identifiers to be used during exchanges between said terminals. Two terminals are connected via slices supported by the NET 5G network. It should be noted that in this alternative, and because client terminal 310 is the primary terminal, it does not need to transmit to server terminal 320 the list of active slices to which it is connected. In other words, client terminal 310 transmits at least one connection element from its available connection elements to server terminal 320. More specifically, if client terminal 310 wishes to use the application function, it transmits connection element ELE CX 1 and / or connection element ELE CX 2 to the server terminal. Once the transmission is complete, each of terminals 310 and 320 obtains one or more connection identifiers based on the transmitted connection elements, in accordance with provisions similar to those described above in method 4000.

[0252] Furthermore, according to yet another variant, only one of the terminals—either client terminal 310 or server terminal 320—can be a candidate terminal (i.e., only one of said terminals 310 or 320 possesses connection elements when the third phase is initialized). Therefore, this candidate terminal is the one designated as the primary terminal. The data relating to this designation is, for example, generated by the candidate terminal. However, nothing precludes it from being generated by the other terminal, which is not a candidate.

[0253] Fourth phase

[0254] Figure 9 schematically represents a SYS_4 communication system according to a particular embodiment of the invention.

[0255] It is important to note that the NET 5G network shown in Figure 9 is the one resulting from the execution of process 1000 of the first phase. In other words, with regard to this fourth phase, the NET 5G network is configured in a specific way, that is, so that each TR 5GJ slice is associated with an ELE CXJ connection element.

[0256] As illustrated in Figure 9, the SYS_4 system comprises the client terminal 310 and the server terminal 320, whose respective configurations result from the execution of process 4000 of the third phase. In other words, the client terminal 310 (respectively the server terminal 320) possesses the connection identifiers ID CX 1 310, ID CX 2 310 (respectively the connection identifiers ID_CX_1 320, ID CX 2 320).

[0257] Although it is assumed here that the respective configurations of the client terminal 310 and the server terminal 320 result from the execution of process 4000 of the third phase, nothing excludes of course assuming that these configurations result from any other alternative implementation of the third phase, as described previously.

[0258] It should be noted that the provisions according to which the client terminal 310 and the server terminal 320 were subjected to a process conforming to the third phase are not limiting to the invention. Indeed, nothing precludes the possibility that the client terminal 310 (respectively the server terminal 320) acquired one or more login credentials in another way. For example, this or these login credentials may have been written to the memory of the client terminal 310 (respectively the server terminal 320) during its manufacture.

[0259] The SYS_4 system also includes the peripheral node 110 which is aware of the associations between ELE CXJ connection elements and TR 5GJ slices via the TAB 1 table due to the execution of process 1000 of the first phase.

[0260] As mentioned above, the fourth phase involves the exchange of useful data between the two terminals. More specifically, the two terminals, 310 and 320, communicate with each other by exchanging data packets. These data packets travel via one or more network segments supported by the NET 5G network, within the framework of the application function associated with the service subscription taken out by the user of the client terminal 310. This exchange therefore takes place after the two terminals have established communication with each other in order to obtain their connection credentials, as described above in the third phase.

[0261] In order for said fourth phase to be implemented, the read-only memory 113 of the peripheral node 110 stores, in addition to the computer program PROG_116, another program PROG_117 according to the invention, comprising instructions for executing steps of a third communication method according to the invention. The program PROG_117 defines functional modules of the peripheral node 110, which rely on or control the hardware elements 111 to 115 of the peripheral node 110, and which are described in more detail below with reference to different implementation methods. Furthermore, the communication means 115 allow the peripheral node 110 to exchange data with terminals 310, 320 according to all technical characteristics conceivable by the person in the business, such as those already described above.

[0262] Figure 10 represents, in the form of a flowchart, a particular method of implementing a fifth general process 5000 implemented by the SYS_4 system. Said process 5000 encompasses the third communication process according to the invention implemented by the peripheral node 110, as well as communication processes respectively implemented by the terminals 310, 320 and whose execution therefore takes place after the first and second communication processes described in the framework of the third phase have themselves been executed.

[0263] The 5000 process first includes a step 5100 of transmission, by the server terminal 320, of a data packet P DATA 320 to the client terminal 310. This step 5100 is implemented by the MOD TX 320 transmission module equipping the server terminal 320, and is part of the communication process implemented by the server terminal 320 in the context of the fourth phase.

[0264] For the remainder of this description, we will assume, without limitation, that the P DATA 320 data packet contains the ID CX 1 320 obtained by the server terminal 320 during the third phase (and therefore generated using the ELE CX 1 connection element during the third phase). Of course, nothing precludes the possibility that the other ID CX 2 320 could be inserted into the P DATA 320 data packet.

[0265] Furthermore, it should be noted that, in this implementation, it is the server terminal 320 that sends a data packet to the client terminal 310. For this reason, the server terminal 320 (respectively the client terminal 310) can still be referred to as the "sending terminal" (respectively the "receiving terminal"). These provisions are not, however, limiting to the invention, and nothing precludes the possibility of the client terminal 310 sending a data packet to the server terminal 320 (in which case the roles of "sending terminal" and "receiving terminal" are, of course, reversed).

[0266] The peripheral node 110 receives the data packet P DATA 320 during a step 5200 of process 5000. Said step 5200 is implemented by the MOD RX 110 receiving module equipping the peripheral node 110, and is part of the third communication process.

[0267] The 5000 process then includes a step 5300 for evaluating, by the peripheral node 110, a CRIT OONF conformity criterion. This step 5300 is implemented by an evaluation module MOD EVAL 110 equipping the peripheral node 110, and is part of the third communication process.

[0268] The evaluation of said CRIT CONF conformity criterion is a step to determine to what extent such or such slice of the NET 5G network will be used to route the P DATA 320 data packet to the client terminal 310, as detailed later.

[0269] The CRIT CONF compliance criterion is evaluated based on at least the connection identifier ID CX 1 320 contained in the data packet P DATA 320. More specifically, in this implementation, the data packet P DATA 320 also contains a connection identifier associated with the client terminal 310. For illustrative purposes, and for the remainder of this description, the data packet P DATA 320 is considered to also contain the connection identifier ID CX 2 310.

[0270] The fact that the P DATA 320 data packet contains two connection identifiers respectively associated with terminals 310, 320 may, for example, result from a connection identifier exchange procedure that was implemented prior to process 5000.

[0271] In addition, in this implementation method, the evaluation of the CRIT CONF conformity criterion includes a comparison of the values ​​of each first bit belonging respectively to the identifiers ID CX 1 320 and ID CX 2 310 contained in the data packet P DATA 320. It is then considered that the CRIT OONF conformity criterion is satisfied if the values ​​of said first bits are identical.

[0272] For example, suppose that the connection identifier ID CX 1 320 (respectively the connection identifier ID CX 2 310) consists of the following bit sequence: 1110111111 (respectively 1110100001). The conformance criterion is therefore satisfied (same first bit equal to 1). On the other hand, if, for example, the connection identifier ID CX 2 310 consists of the following sequence: 0110100001, the conformance criterion CRIT OONF is not satisfied.

[0273] It should be noted that comparing the values ​​of the first bit of each identifier belonging to ID CX 1 320 and ID CX 2 310 respectively does not limit the invention. In particular, nothing prevents comparing several bits belonging to each of these identifiers and / or comparing bits occupying other positions within the bit sequence forming said identifiers.

[0274] Once the CRIT CONF conformance criterion evaluation has been carried out, the P DATA 320 data packet can be routed to the client terminal 310 using a slice of the NET 5G network, the identity of said slice being dependent on the result of the evaluation step 5300.

[0275] For the remainder of the description, it is assumed, in a non-limiting manner, that the CRIT CONF conformity criterion is satisfied.

[0276] We also take up here the elements introduced as an example during the description of the third phase and according to which the client terminal 310 is connected to the TR_5G_1, TR_5G_2, TR_5G_3 slices which are thus qualified as "active" slices, and that the slices actually associated with the application function intended to be used are the TR_5G_1 and TR_5G_2 slices.

[0277] The 5000 process then includes a step 5400 of determination, by the peripheral node 110, of the connection element, called "useful connection element", associated with the connection identifier ID CX 1 320 associated with the sending terminal (i.e. the server terminal 320) contained in the data packet P DATA 320. Said step 5400 is implemented by a determination module MOD DET 110 equipping the peripheral node 110, and is part of the third communication process.

[0278] As a reminder, the aforementioned ID CX 1 320 was generated from the connection element ELE CX 1, which, in this implementation, corresponds to a pattern. For example, this pattern can correspond to a plurality of consecutive bits within the bit sequence forming the connection identifier ID CX 1 320. For illustrative purposes, returning to the previous example in which the connection identifier ID CX 1 320 consists of the following bit sequence: 11101111 11, this pattern can correspond to the four bits following the first bit of said sequence (i.e., the pattern corresponds to the bit sequence 1101).

[0279] Of course, considering four consecutive bits is not limiting to the invention. More generally, the peripheral node 110 is configured to identify the connection element associated with the connection identifier of the sending terminal contained in the data packet, regardless of whether said connection element is a pattern or a set of given identifiers. This is possible due to the execution of the first phase, and more specifically, the implementation of the reception process by said node 110.

[0280] Subsequently, and insofar as the TR_5G_1 slice associated with the ELE CX 1 connection element is an active slice, the 5000 process then includes a step 5500 of routing, by the edge node 110, of the data packet P DATA 320 to the client terminal 310 using said TR_5G_1 slice. This step 5500 is implemented by a MOD TX 110 transmission module equipping the edge node 110, and is part of the third communication process.

[0281] Finally, the client terminal 310 receives the data packet P DATA 320 during a step 5600 of the process 5000. Said step 5600 is implemented by the MOD RX 310 receiving module equipping the client terminal 310, and is part of the communication process implemented by the client terminal 310 as part of the fourth phase.

[0282] It should be noted that the 5000 process is not limited by the fact that the CRIT OONF compliance criterion is satisfied and that the slice associated with the connection element determined from the identifier contained in the data packet and associated with the sending terminal is an active slice.

[0283] Thus, if the CRIT OONF compliance criterion is met and the slice in question is not an active slice, the data packet can be routed using a slice designated by default (e.g., the TR_5G_3 slice is designated to be used by default).

[0284] Similarly, if the CRIT OONF compliance criterion is not met (for example, because the values ​​of the first bits of the identifiers contained in the data packet differ), the data packet can be routed using a designated default slice (e.g., the TR_5G_3 slice is designated for use by default). Alternatively, the data packet can be routed without using any of the network slices.

[0285] Furthermore, the 5000 method is not limited by the requirement to evaluate a conformance criterion between connection identifiers. For example, it is possible to directly determine (i.e., without performing a conformance test) the connection element associated with one of the identifiers contained in the data packet, and then route the data packet according to provisions similar to those described above, namely, using the slice associated with said connection element if that slice is active, or otherwise using a default slice. Proceeding in this way ensures that traffic routing is always based on a connection element obtained by the sending or receiving terminal, which corresponds to establishing a trust criterion for the latter.

Claims

Claims

1. A method of configuring a network supporting N network slices, N being an integer greater than or equal to 1, said method comprising steps of: - generation (1100) of M connection elements, M being an integer greater than or equal to 1, each connection element being configured to allow obtaining at least one connection identifier intended to be used at the level of a transport and / or application layer during communication via one or more network slices, - association (1200) of at least one connection element to at least one network slice according to a given association criterion, - transmission (1300) of data indicating the associations between connection elements and network slices to a set E of network entities configured to participate in the routing of data packets within the network.

2. Method according to claim 1, in which at least one connection element is a pattern configured to impose, among the sequence of bits forming a connection identifier, the value of at least one bit having a given position within said sequence of bits.

3. Method according to any one of claims 1 to 2, in which the set E of entities comprises at least one of: - a network address allocation server, - a network prefix allocation server, - a router configured to enable a network prefix delegation function, - a network edge node, such as an access router or an ASBR router.

4. Method according to any one of claims 1 to 3, in which a connection element or identifier is an identifier of type "Connection ID" ("CI D") used by the QUI C protocol or the DTLS protocol.

5. A reception method implemented by an entity of a network supporting network slices and configured in accordance with a method according to any one of claims 1 to 4, said reception method comprising a step of receiving (1500) said data indicating the associations between connection elements and network slices.

6. Data processing method implemented by: - a terminal connected to at least one network supporting network slices and configured in accordance with a method according to any one of claims 1 to 4, or - equipment of said at least one network supporting network slices, said data processing method comprising, if implemented by said terminal, steps of: - transmission (2100), to said entity, of a request to obtain at least one connection element, - reception (2400), from said entity, of a response to said request, said response comprising at least one connection element associated with at least one network slice supported by the network, or said data processing method comprising, if implemented by said entity, steps of: - reception (2200), from said terminal, of a request to obtain at least one connection element, - transmission (2300) to said terminal of a response to said request, said response comprising at least one connection element associated with at least one network slice supported by the network.

7. Method according to claim 6, in which the obtaining request comprises at least one parameter corresponding to a slice identifier or to a type of slice to which the terminal is authorized to connect, the response to the request comprising at least one connection element associated with a slice itself associated with said identifier or with a slice of said type.

8. Method according to any one of claims 6 to 7, in which, in the absence in the request to obtain a parameter corresponding to a slice identifier or to a type of slice to which the terminal is authorized to connect, the response to the request comprises at least one connection element associated with at least one slice to which the terminal is authorized to connect.

9. Communication method implemented by a first terminal, called "client terminal", to exchange data with a second terminal, called "server terminal", the client terminal being connected to a network supporting network slices and configured in accordance with a method according to any one of claims 1 to 4, and at least one terminal, called "candidate terminal", among said client terminal and said server terminal being in possession of at least one connection element of said network, said method comprising steps of: - obtaining (4250) data designating a terminal, called “primary terminal”, from among said at least one candidate terminal, - if the client terminal is the primary terminal: • transmission, to the server terminal, of at least one connection element, called “first connection element”, among said at least one connection element that said client terminal has, • obtaining at least one connection identifier using said at least one first connection element, said at least one connection identifier being intended to be used at a transport and / or application layer during communication via one or more network slices, - if the server terminal is the primary terminal: • reception (4650), from the server terminal, of at least one connection element, called “second connection element”, among said at least one connection element that said server terminal has, • obtaining (4700) at least one connection identifier using said at least one second connection element, said at least one connection identifier being intended to be used at a transport and / or application layer during communication via one or more network slices.

10. Communication method implemented by a second terminal, called "server terminal", to exchange data with a first terminal, called "client terminal", the client terminal being connected to a network supporting network slices and configured in accordance with a method according to any one of claims 1 to 4, and at least one terminal, called "candidate terminal", among said client terminal and said server terminal being in possession of at least one connection element of said network, said method comprising steps of: - obtaining (4350) data designating a terminal, called “primary terminal”, from among said at least one candidate terminal, - if the client terminal is the primary terminal: • reception, from the client terminal, of at least one connection element, called “first connection element”, among said at least one connection element that said client terminal has, • obtaining at least one connection identifier using said at least one first connection element, said at least one connection identifier being intended to be used at a transport and / or application layer during communication via one or more network slices, - if the second terminal is the primary terminal: • transmission (4600), to the client terminal, of at least one connection element, called “second connection element”, among said at least one connection element that said server terminal has, • obtaining (4550) at least one connection identifier using said at least one second connection element, said at least one connection identifier being intended to be used at a transport and / or application layer during communication via one or more network slices.

11. A method according to any one of claims 9 to 10, wherein: - if the client terminal or the server terminal is the only candidate terminal, said candidate terminal is designated as the primary terminal, or - if the client terminal and the server terminal are both candidate terminals, the data designating the primary terminal is generated by one of said two candidate terminals based on a given designation criterion.

12. A method according to any one of claims 9 to 11, wherein obtaining at least one connection identifier using at least one connection element comprises: - if said at least one connection element comprises a pattern, a generation of at least one connection identifier in accordance with said pattern, and / or - if said at least one connection element comprises a set of identifiers of given connection, a selection of at least one connection identifier from said set.

13. Method according to any one of claims 9 to 12, in which the client terminal is connected to a set of network slices supported by the network, called "active slices", and: - if the client terminal is the primary terminal, said at least one first connection element is associated with one or more active slices, or - if the server terminal is the primary terminal, a list comprising identifiers and / or types of said active slices is transmitted by the client terminal to the server terminal, said at least one second connection element being selected by the server terminal from said at least one connection element that it possesses and so as to be associated with at least one active slice.

14. Communication method implemented by a node of a network supporting network slices and configured in accordance with a method according to any one of claims 1 to 4, said node belonging to said set E, said communication method comprising steps of: - reception (5200) of a data packet from a terminal, called the “transmitting terminal”, said data packet being intended for another terminal, called the “receiving terminal”, and comprising at least one connection identifier intended to be used at the level of a transport and / or application layer during communication via one or more network slices, - routing (5500) of the data packet to the receiver terminal according to said at least one connection identifier.

15. Method according to claim 14, in which the data packet comprises a connection identifier associated with the sending terminal and another connection identifier associated with the receiving terminal, said method also comprising steps of: - evaluation of a conformity criterion based on said connection identifiers contained in the data packet, and - if the conformity criterion is met: • determination of the connection element, called “useful connection element”, associated with one of said connection identifiers contained in the data packet, • routing of the data packet to the receiving terminal using a network slice determined according to said useful connection element, - if the conformance criterion is not met, routing the data packet to the receiving terminal using a network slice designated by default or without using a network slice supported by the network.

16. Method according to claim 15, in which the evaluation of the conformity criterion comprises a comparison of the values ​​of at least two bits belonging respectively to the connection identifiers of the transmitting terminal and of the receiving terminal contained in the data packet, each of said bits having a given position within the sequence of bits forming the connection identifier to which it belongs, said conformity criterion being satisfied if said values ​​are identical.

17. Method according to any one of claims 15 to 16, in which the receiving terminal is connected to a set of network slices supported by the network, called "active slices", and in which: - if the conformity criterion is satisfied and if the slice associated with said useful connection element is an active slice, the data packet is routed using said network slice associated with said useful connection element, - if the conformance criterion is met and if the slice associated with said useful connection element is not an active slice, the data packet is routed using a network slice designated by default.

18. A method according to claim 14, wherein the receiving terminal is connected to a set of network slices supported by the network, said “active slices”, said method comprising a step of determining the connection element, called “useful connection element”, associated with a connection identifier among said at least one connection identifier contained in the data packet, and: - if the slice associated with said useful connection element is an active slice, the data packet is routed using said network slice associated with said useful connection element, - if the slice associated with said useful connection element is not an active slice, the data packet is routed using a network slice designated by default.

19. Configuration device (130) comprising means configured to implement a configuration method according to any one of claims 1 to 4.

20. Entity (110, 120) of a network supporting network slices comprising means configured to implement: - a receiving method according to claim 5, and - a data processing method according to any one of claims 6 to 8.

21. Terminal (210, 310, 320) comprising means configured to implement: - a data processing method according to any one of claims 6 to 8, as well as: - a communication method according to claim 9 or according to any one of claims 11 to 13 at least combined with claim 9, or - a communication method according to claim 10 or according to any one of claims 11 to 13 at least combined with claim 10.

22. A node (110) of a network supporting network slices and comprising means configured to implement a communication method according to any one of claims 14 to 18.

Images