Method for managing communications in a communication network implementing at least one mobile intermediate device, and corresponding system and computer program

Description

Title of the invention: Method for managing communications in a communications network implementing at least one intermediate mobile device, system and corresponding computer program.

[0001] 1. Field of the invention

The field of the invention is that of telecommunications.

[0003] More specifically, the invention relates to downlink communications, between mobile intermediate equipment (for example a satellite, an airplane, a balloon, a drone, a high altitude platform HIBS (“High Altitude Platform Station”) , etc.) and at least one user equipment item (or UE for “User Equipment”, for example of the “smartphone” type, laptop computer, connected TV, etc.).

[0004] By way of example, the invention applies to satellite mobile telephone networks.

[0005] It can in particular, but not exclusively, apply to cellular systems based on an access technology of the OFDMA type (in English “Orthogonal Frequency-Division Multiple Access”), such as LTE-A (in English “ Long Term Evolution - Advanced) or 5G. The invention can also be applied to satellite systems onboard a non-cellular mobile network.

[0006] 2. Prior Art

[0007] Unlike previous generations, 5G proposes dividing the radio access network (RAN, in English “Radio Access Network”) into functional blocks, independent of the physical network elements. These are mainly the following functions: a remote radio unit RU (in English “Remote Unit”), a distributed radio processing and scheduling unit DU (in English “Distribution Unit”) and a centralized unit towards the core network CU (in English “Centralized Unit”). Several variants of distribution of these functions, called “splits” have been proposed, according to the objectives of concentration of the functions of the RAN.

[0008] It is nevertheless necessary to find a compromise between the benefits of centralization and the cost of the additional links induced by the distribution of these functions over several physical network elements, in particular the links between the DU and RU functions. Indeed, each split has a speed and latency constraint.

[0009] The [Fig.l] presents a family of "splits" called intra physical layer known from the state of the art (variants 8, 7.1, 7.2 and 7.3), where CN corresponds to the heart of the network (in English " Core Network”), BH to the link between the core network and the CU function (“Backhaul”), MH the link between the CU and DU functions (“Midhaul”) and FH the link between the DU units and RU (English “Fronthaul”). According to this family, the ENC coding/DEC decoding, PUNCT puncturing/DE-PUNCT de-puncturing operations can be implemented by the DU function. MOD modulation / DEMOD demodulation, RE-MAP resource element mapping and RE-DEMAP de-mapping, and IFFT / FFT transformation operations can be implemented by the RU function.

This family of intra physical layer "splits" is particularly studied, thanks to the benefits of radio cooperation between cells which would make it possible to reduce interference and increase user throughput (beamforming, joint transmission - in English "joint transmission", multipaths - in English "multi-paths", etc).

[0011] The [Fig.2] illustrates the interfaces between the virtualized network functions CU, DU and RU.

[0012] The F1 interface between the CU and DU functions, also called HLS (in English “Higher Layer Split”), is specified in part by the 3GPP. The O-RAN standardization alliance has in particular defined deployment scenarios in which the F1 interface is fully interoperable.

[0013] The F2 interface between the DU and RU functions, also called LLS (in English "Lower Layer Split") or "Open FrontHaul", is an open interface (unlike a CPRI type interface (in English “Common Public Radio Interface”) conventionally used between a base station and its antennas). It is also specified by 3GGP, in particular for variant 7.2.

[0014] At the same time, and in order in particular to improve radio coverage in certain geographical areas, 5G network architectures based on the use of non-terrestrial equipment for radio access ("Non Terrestrial Network") , such as satellites, planes or even balloons, have been proposed.

[0015] The [Fig.3] illustrates an example of satellite RAN, implementing two satellites S ATI and SAT2. Each of these satellites generates at least one radio beam, also called a spot. The terrestrial geographic zone covered by this radio beam corresponds to a radio cell, benefiting from radio coverage. It can therefore be considered that a satellite emulates a radio cell. Such a radio cell is called RaF hereafter, for Emulated Fixed Terrestrial RAN. In particular, such a radio cell can be associated with at least one cell identifier.

According to this example, a user equipment UE can connect to a server S, for example a web server, via the radio network RAN ​​comprising the satellite S ATI which embeds the RU and DU functions according to the architecture illustrated. , and a terrestrial station GW 1 (in English “terrestrial gateway”) which embeds the CU function, managed for example by a network operations center NoC (in English “Network Operations Center”) which brings together the operator of the mobile network MNO (in English “Mobile Network Operator”) and the operator of the satellite network SNO (in English “Satellite Network Operator”). The routers between different communication networks (regional network, national network for example) between the earth station GW 1 and the server S are illustrated by an “X”.

[0017] Different satellite RAN architectures can be implemented:

[0018] 1. "Nothing onboard", ie the various functions are implemented by terrestrial equipment:

To. the DU function and the RU function are co-located in the ground station, and the CU function in a data center (“data center”) remote from the MNO,

b. the DU function and the CU function are co-located in a data center remote from the MNO, and the RU function co-located with the ground station,

2. "RU onboard": ie the RU function is implemented by the satellite:

To. the DU function and the CU function are distant, and the RU function located in the satellite,

b. the DU function is co-located with the ground station, the CU function is remote, and the RU function is located in the satellite,

3. "RU+DU onboard", ie the RU and DU functions are implemented by the satellite:

To. the RU and DU functions are located in the satellite, the CU function is remote,

b. the RU and DU functions are located in the satellite, the CU function is co-located with the ground station,

4. “RU+DU+CU onboard” ie the RU, DU and CU functions are implemented by the satellite:

To. the RU, DU and CU functions are located in the satellite,

b. the RU, DU, CU and UPF functions (in English "User Plane

Function”) are located in the satellite.

More generally, all or part of the virtualized functions (RU, DU, CU) of the satellite RAN can be distributed over one or more satellites of a constellation and one or more ground stations. Compared to a terrestrial RAN radio access network, the satellite RAN involves at least one additional radio connection, for example of the e-CPRI type, in order to connect the satellite to the terrestrial station then to the core of the mobile network, or even more when the virtualized functions are distributed over several satellites, with the use of ISL links (for “Inter Satellite Link”) between satellites.

Whatever the configuration chosen, the distance between these virtualized functions (and consequently the latency) must be minimized to meet the deadlines established for 5G. In particular, the latency between the RU function and the DU function must be less than one millisecond. In other words, when the DU function is also located in space (like the RU function), the system is less sensitive to the latency between the satellite and the earth station, at least with regard to the mobile radio processing.

[0021] Similarly, the CU function can also be placed in the constellation of satellites, in the ground station or even in equipment of a remote data center.

[0022] It is also noted that the ability of a satellite to emulate a terrestrial 5G cell is limited. Indeed, due to the distance between the satellite and the user equipment (for example 500 km for a satellite RAN instead of 5 km for a terrestrial RAN) and/or the angle of the radio beam emulating the radio cell, the size of the emulated cell is very large (for example 50km in diameter for a RaF radio cell emulated by a satellite RAN instead of 5km in diameter for a terrestrial cell associated with a terrestrial antenna).

[0023] However, certain applications, for example commercial Web applications, require the downloading and processing of a large volume of data when initializing the connection between the user equipment and the data server. Similarly, the exchange of certificates (for example during “handshakes” of the TLS or QUIC protocols) requires a high throughput when initializing the connection.

[0024] There is therefore a need to provide a minimum throughput to user equipment at the start of a connection, in particular when they are present in a cell emulated by a satellite RAN, or more generally emulated by mobile intermediate equipment (ie separate from a land fixed station) between the user equipment and a data server.

3. Disclosure of the Invention

The invention proposes a solution that does not have all the drawbacks of the prior art, in the form of a method for managing communications in a communications network implementing at least one mobile intermediate device generating at at least one radio beam covering a terrestrial geographical area, called a radio cell.

According to the invention, such a method implements the following steps, for a data stream of said at least one radio beam:

obtaining the number of individual phases, each associated with a target bit rate in said stream, for transmissions from said mobile intermediate equipment to said radio cell, detecting a start of connection of a first user equipment, present in said radio cell, with a first data server, via said mobile intermediate equipment, • if an individual phase is available for said flow: transmission of connection start data from said first data server, between said mobile intermediate equipment and said first user equipment, at the target rate of the individual phase, up to a stopping criterion, • if no individual phase is available for said stream: transmission of connection start data from said first data server, between said mobile intermediate equipment and said first user equipment, at a rate lower than said target rate.

By individual phase is meant here a set of radio resources of the data stream of the radio beam, used for transmissions between the mobile intermediate equipment and the radio cell, making it possible to achieve a target bit rate. More generally, if the flow has N individual phases (N>1), this means that it has radio resources available for transmissions between the mobile intermediate equipment and the radio cell making it possible to reach N target bit rates. For example, two users present in the radio cell can simultaneously receive the data stream carrying on the one hand connection start data at a first target rate coming from the first data server, and on the other hand start data connection at a second target rate from a second data server. Target rates may be different.

The invention thus proposes to estimate the capacity of a radio cell emulated by a radio beam, ie the number of user equipment items that can simultaneously receive data with a target rate, corresponding to the number of individual phases of the flow of data. In this way, on each new connection of a user equipment, it is possible to check whether an individual phase is available, and if so, to transmit the connection start data on the individual phase of the flow, ie with the target rate of the individual phase.

The proposed solution thus makes it possible, according to at least one embodiment, to improve the quality of the user experience by accelerating the start of connections.

The rest of the radio bandwidth, not used by the individual phase or phases, can be used by the connections of the other user equipment, in particular for the transmission of connection “tracking” data.

[0033] The proposed solution thus makes it possible, according to at least one embodiment, to effectively use all of the radio bandwidth.

For example, when a user device connects to a Web application, it is possible to provide from the start of the connection a target bit rate If of around 8 Mbps (i.e. a volume V_f of 2 Megabytes of data during a duration If of 2 seconds) in order to support interactions at a sufficiently high rate to maintain the attention and the confidence of the users.

For the rest of the connection, the required bit rate depends on the uses and the activity of the user. It is often less given the reuse of data downloaded at the start of connections by the Web application (CSS, javascript libraries, cached images, etc.), and the data processing time (for example the concentration of user's attention on the current page). Thus, the transmission of data between the mobile intermediate equipment and the user equipment can take place at the target bit rate of the individual phase up to a stopping criterion, then at a bit rate lower than the target bit rate.

In particular, these different steps can be implemented by the same equipment (for example equipment managed by the operator of the intermediate equipment or equipment managed by the operator of the user equipment). As a variant, due to the virtualization of certain functions, these steps can be implemented by different equipment (for example the steps for obtaining the number of individual phases and detecting the start of a connection can be implemented by at least one device managed by the operator of the user device, and the steps of transmission by at least one device managed by the operator of the intermediate device).

According to a particular embodiment, the number of individual phases of the flow of the radio beam is defined from at least one parameter belonging to the group comprising:

[0038] · said target rate D ·, · a transmission power P of said mobile intermediate equipment, · a propagation factor K between said mobile intermediate equipment and said radio cell, or at least one user equipment present in said radio cell, • a VF bandwidth of said mobile intermediate equipment, • an aperture angle of the transmit antenna^To said mobile intermediate equipment, • a distance d between said mobile intermediate equipment and said radio cell, or at least one user equipment present in said radio cell, • a number of interfering radio beams NB between said mobile intermediate equipment and at least one other cell radio, • a thermal noise N th, • the variance, or standard deviation, of the masking effect (in English “shadowing”)^σ, • a non-coverage probability Pout.

The capacity of a radio cell therefore depends on the characteristics of the radio beam generated by the intermediate equipment.

[0040] In particular, such intermediate equipment is mobile, ie separate from a fixed ground station. It is for example terrestrial equipment or non-terrestrial equipment, such as a satellite, an airplane, a balloon, a drone, an HIBS etc.

Such intermediate equipment is also called access equipment, in that it can be connected directly to user equipment (ie without passing through a fixed terrestrial antenna).

According to a particular embodiment, the number of individual phases of the flow is equal to the integer part of the capacitance C of the radio beam generated by the mobile intermediate equipment:

[0043]

[0044]

[0045]

[0046]

[0047]

[0048]

C= + ---) io¹⁰ +n_b with :

b = oQ^I(P_mt) +m

Q(u) = m = 10log_aJ

Ν_Λ ).

KPd²

The decimal part of the capacity C corresponds to the remaining bit rate for the transmissions outside the individual phase or phases, called “tracking”.

The solution proposed according to this embodiment thus makes it possible to simply determine the distribution of the radio resources of the stream, between the individual phase(s) and the rest of the stream. The distribution according to this embodiment is done by an integer division and a modulo.

For example, the criterion for stopping a transmission at the target rate of an individual phase belongs to the group comprising:

[0051] a given period Tj (for example of the order of 2 to 4 seconds), • a given volume Vj (for example of the order of 2 to 4 megabytes), • an end of connection of said first user equipment with said first data server, • detection of a start of connection of a second user equipment, present in said radio cell, to a second data server having priority with respect to said first data server.

[0052] Thus, it is possible to release an individual phase of the flow after the start of the connection, since the “continuation of connection” generally requires a bit rate lower than the “start of connection”. The release of an individual phase of the flow allows another user equipment to benefit from the target bit rate at the start of the connection (or the first user equipment to benefit from the target bit rate at the start of the connection for a new connection).

Thus, according to the proposed solution, the “established” connections (also called “connection pursuit”) do not capture all the radio bandwidth, and radio resources remain available for new connections.

This point is important because end-to-end connection congestion checks are becoming more and more aggressive and pre-empt a maximum of bandwidth to the detriment of new connections.

According to a particular embodiment, the criterion for stopping a transmission at the target rate of an individual phase depends on a type of service or on the domain requested.

Thus, if the service or domain requested is of the video type, for example, the time allocated for the individual phase may be longer, for example of the order of 4 to 10 seconds, or the volume of data allocated for the individual phase may be greater, for example of the order of 4 to 10 megabytes.

It is also possible to release an individual phase of the stream if a user device wishes to establish a connection with an emergency service.

According to a particular embodiment, the step for obtaining the number of individual phases is updated:

periodically, or • following a modification of a parameter of said mobile intermediate equipment, or • following a modification of a parameter of the radio beam generated by the mobile intermediate equipment, or • following a modification of said criterion stop.

The number of individual phases of the stream can thus be adjusted dynamically, in particular asynchronously. For example, the number of individual phases can be increased following a need of the 5G core network due to saturation or an incident on a terrestrial cell belonging to the geographical terrestrial zone covered by the radio beam.

According to a particular embodiment, the step of detecting a start of connection implements the detection of an exchange of connection securing data between said first user equipment and said first data server.

According to a particular embodiment, the detection of a start of connection comprises:

[0063] the identification of connection start data, from at least one marker inserted by an RRC (Radio Resource Control) type module in at least one data packet from said first server of data, • the insertion of connection start data into said individual phase available for said stream by a MAC (Medium Access Layer) type module.

According to this embodiment, the proposed solution thus encourages the exposure of the end-to-end signaling of the connections.

According to a particular embodiment, the method implements the storage of information relating to said at least one individual phase in an individual phase management table.

[0066] In particular, only the information relating to the individual phase(s) is stored in a table. In this way, the size of the stored data is small.

The invention also relates to a communication management system in a communication network implementing at least one mobile intermediate device generating at least one radio beam covering a terrestrial geographical area, called a radio cell.

According to the invention, such equipment comprises, for a data stream of said at least one radio beam:

[0069] · a module for obtaining the number of individual phases each associated with a target rate in said flow, for transmissions from said mobile intermediate equipment to said radio cell, · a module for detecting a start of connection of a first user equipment, present in said radio cell, with a first data server, via said mobile intermediate equipment, • a connection start data transmission module from said first data server, between said mobile intermediate equipment and said first user equipment, at the target rate of the individual phase, up to a stop criterion, activated if a individual phase is available for said stream, • a connection start data transmission module from said first data server, between said mobile intermediate equipment and said first user equipment, at a rate lower than said target rate, activated if no individual phase is available for said flow.

For example, such a system comprises one or more items of equipment managed by the operator of the intermediate equipment (for example the satellite operator) and/or the operator of the user equipment.

These different modules can in particular be co-located or remote. For example, the modules for obtaining the number of individual phases and for detecting a start of connection belong to at least one device managed by the operator of the user device, and the transmission modules belong to at least one device managed by the operator of the intermediate equipment. According to another example, certain modules can be located on different satellites.

According to other embodiments, these different modules correspond to functional blocks, which can be co-located or remote.

The invention also relates to one or more computer programs comprising instructions for the implementation of a communications management method as described above when this or these programs are executed by at least one processor.

[0074] 4. List of Figures

Other characteristics and advantages of the invention will appear more clearly on reading the following description of a particular embodiment, given by way of a simple illustrative and non-limiting example, and the appended drawings, among which:

[0076] - the [Fig.l], introduced in the prior art part, illustrates the virtualization of the functions of a radio access network according to the 5G standard;

[0077] - [Fig.2], also introduced in the prior art part, illustrates the interfaces between the various virtualized functions of a radio access network according to the 5G standard;

[0078] - the [Fig.3], also introduced in the prior art part, presents an example of radio access network architecture comprising a satellite;

[0079] - [Fig.4] presents the main steps implemented by the communication management method according to a particular embodiment of the invention;

[0080] - [Fig.5] shows the main steps implemented when a user device seeks to connect to a server, via the mobile intermediate device;

[0081] - [Fig.6] illustrates an example of radio access network architecture comprising a satellite according to one embodiment of the invention;

[0082] - [Fig.7] illustrates the messages exchanged between the various entities of the radio access network according to [Fig.6];

[0083] - [Fig.8] shows the simplified structure of at least one piece of equipment of a communication management system according to a particular embodiment.

[0084] 5. Description of a particular embodiment

[0085] 5.1 General principle

The invention is placed in the context of a communication network implementing mobile intermediate transmission equipment (ie at least one radio antenna which moves, for example a satellite, an airplane, a balloon, a drone , a HIBS, etc.), and proposes a solution to improve the communications via the mobile intermediate equipment of transmission.

The general principle of the invention is based on the estimation of the number of individual phases available in the data stream of the radio beam generated by the intermediate mobile transmission equipment and emulating a radio cell, and on the allocation of an individual phase at the start of the connection (if an individual phase is available) allowing data to be transmitted at a desired bit rate (known as the target bit rate) at the start of the connection. The proposed solution thus makes it possible to accelerate the start of connections.

The [Fig.4] illustrates the main steps for the management of communications in a communication network implementing at least one user equipment and at least one mobile intermediate equipment.

We consider a mobile intermediate device generating a radio beam “illuminating” a radio cell, also called RaF. The data stream of the radio beam transmitted by the mobile intermediate equipment is received by all the user equipment present in the radio cell. Such a stream can therefore carry data intended for the various user equipments, in the form of a multiplex.

During a first step 41, the number of individual phases is obtained, each associated with a target rate in the stream, to be used for transmissions from the mobile intermediate equipment to the radio cell.

[0091] During a second step 42, it is detected that a first user equipment, present in the radio cell, connects with a first data server, via the mobile intermediate equipment.

It is then checked (43) whether an individual phase is available (ie whether radio resources for transmission at the target bit rate are available).

If an individual phase is available for the stream (431): the connection start data coming from the first data server can be transmitted, between the mobile intermediate equipment and the first user equipment, at the target bit rate of the individual phase, up to a stopping criterion.

For example, the stopping criterion belongs to the group comprising:

[0095] · a given period T · a given volume Vf · an end of connection of the first user equipment with the first data server, · a detection of a start of connection of a second user equipment, present in the radio cell , to a second data server which takes priority over said first data server, etc.;

If no individual phase is available for the stream (432): the connection start data from the first data server can be transmitted, between the mobile intermediate equipment and the first user equipment, to a rate lower than the target rate of the individual phase.

In this way, the radio bandwidth is used efficiently, by reserving part of the bandwidth for the start of the connection and the rest of the bandwidth for the continuation of the connections.

It is thus possible to serve one or more connections at the same time, for example at a rate Dj for a new connection and D<Di for a continued connection, using the entire radio bandwidth. If we consider Xtot radio resources for the transmission of data in the stream of the radio beam, we have = ^IND_i⁺ XRES

[0099] with:

[0100] Ci the number of individual phases,

[0101] Xjnd i '^{his name}ber of radio resources making it possible to reach a target bit rate Dj (ie used during the individual phase);

[0102] Xres 1θ number of remaining radio resources.

It is noted that the various steps presented above can be implemented by the mobile intermediate equipment or by equipment managed by the operator of the mobile intermediate equipment. However, due to the virtualization of certain functions, certain steps could be implemented by non-mobile equipment, for example a fixed earth station.

[0104] 5.2 Description of a particular embodiment

An example of implementation of the invention is presented below.

It is considered for example that the mobile intermediate equipment is a satellite, managed by a satellite network operator SNO. Such a satellite is called an access satellite, in that it can connect directly to user equipment.

The SNO, for example the OSS (“Operations Support System”), configures a satellite RAN.

For example, a satellite can generate one or more radio beams, also called spots. The characteristics of the satellite, or the radio beams of the satellite, can be defined from different parameters:

<td>Setting</td><td>Definition</td>

<td>P</td><td>spot emission power</td>

<td>K</td><td>frequency-dependent propagation factor</td>

<td>W</td><td>bandwidth (MHz) of the spot</td>

<td>D</td><td>^v with Di the target rate (Mbits/s) of an individual phase flow</td>

<td>NB</td><td>number of interfering spots</td>

<td>σ</td><td>shadowing standard deviation (dB)</td>

<td>nth,</td><td>thermal noise at the receiver (constant)</td>

<td>d</td><td>satellite - receiver distance</td>

<td>To</td><td>aperture angle of spot transmitting antenna, typically 2 to 5 degrees</td>

[0109] Table 1: Table of characteristics (parameters) of spots

These parameters can be different for each spot generated by the satellite. In particular, certain parameters may be linked to the physical characteristics of the equipment (satellite in particular), to the characteristics desired by the mobile network operator MNO (for example a reception rate of 5Mbps at the start of the connection for a user equipment, etc.), etc

For example, the parameters P of emission power of the spot, W of bandwidth of the spot can be chosen by the SNO, and the parameter D, corresponding to the target rate of an individual phase can be chosen by the MNO .

Thus, for each spot, TOSS of the SNO collects the various information on the states of the satellite (main states and main characteristics of the propagation) and of the needs (coming for example from the MNOs) and stores them in a table.

An example of a spot state table is given below, for satellites in low orbit at around 500 km:

<td>Spot_ID</td><td>P</td><td>K</td><td>W</td><td>due</td><td>NB</td><td>nth</td><td>d_UE</td>

<td> 1</td><td>45dBm</td><td>5x10^-5</td><td>10MHz</td><td>5 Mbits/ s</td><td> 6</td><td>_1O¹⁰ mW</td><td>500km</td>

<td> 2</td><td>50dBm</td><td>5 x ΙΟ'⁵</td><td>10MHz</td><td>6 Mbits/ s</td><td> 6</td><td>₁₀-¹⁰mW</td><td>600km</td>

<td></td><td>50dBm</td><td>5 χ ΙΟ'⁵</td><td>10MHz</td><td>5 Mbits/ s</td><td> 6</td><td>_1O¹⁰ mW</td><td>700km</td>

<td> 1000</td><td>55dBm</td><td>5 χ ΙΟ'⁵</td><td>10MHz</td><td>5 Mbits/ s</td><td> 6</td><td>_1O¹⁰ mW</td><td>600km</td>

[0114] Table 2: Spot state table

This table can in particular be exchanged between the OSS of the SNO and the satellite.

The number of individual phases of a data stream of a spot can be determined from one or more parameters defined in the tables above.

For example, the number of individual phases of the flux is equal to the integer part of b

10¹⁰ +n_b the capacitance C of the radio beam, such that:

[0118]

[0119]

[0120] with:

b = aQ^AT(P_out) +m^ m - lOlog ί ^2^^{and }0}\ΚΡ(Γ

V-N^D =

In other words, considering a user using a given service with a

[0121] minimum flow constraint D_I (target bit rate), and using a bandwidth W, the proposed solution makes it possible to establish the capacity of a spot using the expression (1) above.

This capacity characterizes the number of user equipments N simultaneously receiving data with the target bit rate Dp. In other words, this expression meets the constraints in terms of minimum bit rate to be achieved by each user equipment.

The capacitance C of the radio beam, at a given instant, notably takes into account:

[0124] · the average value m of the power received by the user equipment, · constraints linked to the environment of the user equipment on the ground, characterized by the standard deviation^σ due to shadowing, at the level of the receiver connected to a given spot. Note that the value of this last parameter can be provided by the MNO for each emulated RAN, • the probability of non-coverage Pout, or “outage” probability. This is the probability that there are not enough radio resources to transmit at the target rate at the time the user equipment connects. In other words, the user equipment has a probability Pout of not being able to connect to the spot with the target rate Dp This value can also be chosen by the MNO.

Indeed, as the spot must provide a service in a given area, with a probability of non-coverage Pout guaranteed by the operator, these constraints have an impact on the determination of the capacity of the spot.

The capacity C can also be expressed in the following form:

[0127] C — C, + _decimal part

The number of connections Ci (ie of individual flow phases) that can receive the target bit rate D is thus obtained._{ under bridge stress for a given duration.

The decimal part of the capacitance C corresponds to the remaining bit rate for transmissions outside the individual phase(s).

The parameters, in particular the probability of non-coverage Pout, can be adjusted to increase the number of individual phases C, when necessary. The probability of non-coverage Pout can in particular be chosen from a list of possible values ​​(10^I; 0.2x10¹ ' etc). This different information can be added to the spot status table.

<td>Spot_ID</td><td>Pout</td><td>This</td><td>Comment</td>

<td> 1</td><td>10^0.2 x 10'¹</td><td> 2</td><td>Pout belonging to an interval allowing to obtain if possible 2 individual phases</td>

<td> 2</td><td>5x10'^2; 2x10²</td><td> 1</td><td>Pout belonging to an interval allowing to obtain a single individual phase</td>

<td></td><td> • » »</td><td></td><td></td>

<td> 1000</td><td>io';o,2x io^-1</td><td></td><td></td>

There are thus several phases in the flow of the radio beam thus generated: at least one individual phase, denoted DebCo, serving the data from the start of each connection, and a so-called "common" phase, denoted ContCo, grouping together the following data existing connections.

As indicated previously, these different phases make it possible in particular to use the radio bandwidth efficiently and to improve the quality of the user experience.

In particular, the number of individual phases can be updated:

[0134] periodically, or • following a modification of a parameter of the mobile intermediate equipment, or • following a modification of a parameter of the radio beam generated by the mobile intermediate equipment, or • following a modification a stopping criterion, • etc.

For example, periodically or asynchronously (on an event, for example, following a need for the 5G core due to saturation or an incident on a terrestrial RAN), the MNO's OSS estimates the number of new connections to be served by the satellite RAN, then determines or updates the various parameters from expression (1) above and the current table of spot states, in particular:

[0136] · the individual phases in use in the connections (ie the number of connections receiving the target rate), · the number of new connections able to receive the target rate D₍ under constraint of Pout for a given duration, corresponding to Cj, • the individual bit rate in Mbps, for example 5 Mbps, • the duration T, of the individual bit rate (ie the duration of an individual phase), in seconds, for example 3 s, • or the individual volume V} (ie the volume of data transmitted in an individual phase), in MB, for example 2.5 MB, • the probability of non-coverage Pout.

These various parameters can also be added to the spot state table.

In particular, the values ​​of Q, T_{ and V} can be dynamically adjusted to optimize statistical multiplexing.

These parameters can in particular be chosen according to the service or the domain of the requested server. For example, a connection to a domain video.example.com may take twice the time T_{ or megabytes Vf compared to default values.

The OSS of the MNO or of the SNO can in particular update these parameters for the existing connections in progress. For example, if a user equipment connects to an emergency service, the OSS can shorten (at least temporarily) the duration T) of an individual phase of an existing connection, to release the individual phase of the existing connection . In this way, the satellite can recover the individual phase for the start of connection of the user equipment with the emergency service.

The OSS of the SNO can in particular communicate this table of states of the spots to the satellite.

The various steps implemented when a user device seeks to connect to a server, via the mobile intermediate device, are described below, in relation to [Fig.5]. These different steps make it possible to generate, at the output of the satellite, a data stream distributed over the whole of the radio cell.

[0143] During a first step 51, an RRC module seeks to detect new connections in the flow of IP packets received at the input of the satellite, based on the connection start signalling, the size, the encoding, packet time signature, IP packet header fields identifying the IP stream (source address, destination address, protocol, source port, destination port, etc.). As a variant, such a step can be implemented by an RLC module (in English “Radio Link Control”), or even MAC.

For example, it is considered that a user device present in the radio cell is trying to connect to a website myexample.com, hosted on a data server. A negotiation phase is conventionally implemented between the user equipment and the data server, via the satellite if a satellite RAN is considered.

For example, when establishing an HTTPS connection, a “Handshake TLS” type process is implemented between the user equipment and the data server, via the satellite. This process includes an unencrypted phase when downloading certificates. The RRC module can thus detect the different phases of the secure connections of the QUIC, TLS, DTLS, EDHOC and similar protocols, and detect the start of an Internet connection.

If the QUIC protocol is considered, the RRC module can identify from the size, the encoding, and/or the presence of a "ClientHello" type message the phases transporting the certificates corresponding to a first connection (QUIC 1-RTT), reconnection phases with resumption of sessions (resumption of the context of the previous connection, called QUIC 0-RTT crypto).

The RRC module can thus detect the start of a new connection.

The RRC module can also classify the packets received (as being to be transmitted on an individual phase or on a common phase) from the start of connection signalling, the size, the encoding, the time signature some packages

If the QUIC or TLS protocol is considered, the RRC module can identify from the presence of a “ClientHello” type message the phases transporting the certificates corresponding to a first connection (QUIC 1-RTT), reconnection phases with resumption of sessions (recovery of the context of the previous connection, called QUIC 0-RTT crypto) and classify the 1-RTT phases to transmit them on an individual phase and the 0-RTT phases to transmit them on a phase common.

[0150] Optionally, to prevent a user device from connecting multiple times with the same server to benefit each time from the individual phase which makes it possible to reach a target throughput (ie "charding" consisting of creating more connections for capture more bandwidth), a connection can be identified at level 3 (source address, destination address, protocol, source port, destination port, etc).

Upon detection of a connection start, the RRC module can transmit a DebCoFlag connection start indicator to the RLC module during a step 521, or directly to the MAC module during a step 522.

According to a first example, such a connection start indicator can be intended for the RLC module. Thus, such a connection start indicator can be inserted in a proprietary header or in place of an unused bit, for example a reserved bit of the QUIC protocol, for example the “spin bit”. In order to allow interoperability, such a connection start indicator can alternatively be inserted in a non-proprietary message, for example the iOAM (“In-situ OAM”) header, an ECN (“Explicit Congestion Notification”) message, etc. .

According to a second example, such a connection start indicator is sent directly to the MAC module.

The detection of such a connection start indicator makes it possible to identify the packets of the IP streams received by the satellite which must be transmitted in the individual phase or phases at the output of the satellite.

Optionally, an end of FinCoFlag connection indicator can be transmitted to the RLC module or to the MAC module. Alternatively, DebCoDuration or DebCoVol volume information can be transmitted to the RLC module or to the MAC module. It is thus possible to mark all the successive packets as being to be transmitted on an individual phase, or only the first and the last packet concerned.

[0156] Still as a variant, the connection start indicator DebCoFlag can be an integer corresponding to DebCoDuration or to DebCoVol.

This FinCoFlag end of connection indicator, or this DebCoDuration or DebCoVol information, can be used to determine when to stop the transmission in the individual phase or phases at the output of the satellite.

According to the first example presented above (connection start indicator intended for the RLC module), if the RLC module receives a DebCoFlag connection start indicator, it can add it (54) in the first frames (or “subframes”) intended for the MAC module, then transmit the first frames with the DebCoFlag connection start flag.

If the connection start flag DebCoFlag is an integer corresponding to the DebCoDuration duration, it can be decremented over time (for example, if DebCoDuration is equal to 5 seconds, the first frame carries the flag 5, the second frame bears the flag 4, ..., the fifth frame bears the flag 1 and the sixth frame bears no flag).

If the DebCoFlag connection start indicator is an integer corresponding to the DebCoVol volume, it can be decremented taking into account the size of each frame.

After this DebCoDuration period, or once this DebCoVol volume has been reached, or upon detection of an indicator of the FinCoFlag end of connection type, the RLC module no longer marks the frames (ie no longer inserts an indicator in the frames ).

According to a particular embodiment, in the absence of radio resources, the RLC module does not transmit the unmarked frames to the MAC module. Alternatively, depending on the type of RLC module (for example "Transparent Mode (TM)", "Unacknowledged Mode (UM)" or "Acknowledged Mode (AM)", as defined for example in the technical specification 3GPP TS 38.322 version 15.3 .0 Release 15), the RLC module does not forward untagged frames to the MAC module. These frames are considered discarded or “garbaged”.

Furthermore, if the RLC module does not receive a DebCoFlag connection start indicator, it can directly transmit the first frames to the MAC module, without marking them.

Upon receipt of the marked frames according to the first example presented above (start of connection indicator intended for the RLC module), the MAC module detects the start of connection indicator inserted into the frames by the RLC module, and transmits (55) the frames in the individual phase of the data stream.

For example, the MAC module identifies the connection start data from at least one marker/indicator inserted by the RRC module in at least one data packet coming from the first data server (first frames). The MAC module can thus insert the connection start data into the individual phase of the radio beam stream.

If the MAC module receives on the one hand unmarked frames from the RLC module and on the other hand the connection start indicator from the RRC module according to the second example presented above (connection start indicator intended directly for the MAC module), it can directly send (55) the frames identified from the start of connection indicator in the individual phase of the data stream.

The MAC module can send the remaining frames in the common phase (ie with a bit rate lower than the target bit rate) if it has resources left.

According to a particular embodiment, in the absence of radio resources, the MAC module does not transmit the remaining frames. These frames are considered discarded or “garbaged”.

In the embodiment described above, it is assumed that the RRC, RLC and MAC modules are co-located in the satellite. As a variant, the RRC module and/or the RLC module can be remote, and in particular located in fixed terrestrial equipment.

By way of example, the generation of a satellite RAN and the implementation of the proposed solution are detailed below in relation to Figures 6 and 7 to provide a minimum throughput to emergency services, for example. .

For example, satellite RANs can be deployed to supplement or replace terrestrial RANs:

[0172] · at night or during off-peak hours to shut down terrestrial antennas and reduce the power consumed and the radiation emitted;

• in the event of a breakdown of a terrestrial RAN;

• to offload a terrestrial RAN during peak hours;

• to perform maintenance on a terrestrial RAN;

• etc.

The example below develops the case of the maintenance of a terrestrial RAN of an MNO. An example of use of the method by an MNO consists in using the capacity of a satellite RAN during a planned maintenance operation of a terrestrial RAN (for example card change, restart, etc.). This operation can be carried out at night during off-peak hours. The satellite RAN must have a minimum capacity sufficient to replace the terrestrial RAN, in particular to provide speed to the emergency services.

We place ourselves in the context of the network of [FIG. 6], according to which a satellite SAT generates a radio beam 61 emulating a radio cell (RaF), in which three user equipment items UE1, UE2 and UE3 are present.

The satellite SAT is connected to the terrestrial network 62 (comprising the satellite network operator SNO and the mobile network operator MNO) via a terrestrial gateway GW. The user equipment UE1, UE2 and UE3 can connect to one or the other of the servers SI, S2 and/or S3 via the satellite SAT.

The [Fig.7] illustrates the messages exchanged between the different entities, according to one embodiment of the invention.

During a first step 71, the OSS of the SNO configures the satellite SAT. For example, the MNO's OSS transmits "bootstrapping" and configuration type messages to the various modules of the SAT satellite (RRC, RLC and MAC in particular).

By way of example, it is considered that the MNO wishes to carry out the maintenance of a RAN whose cell is at the geographical position Pgeo. The 5G core of this MNO requests the creation of a RaF RaF1 (61) whose characteristics are described by an entry of a spot state table, such as table 2 presented above.

It is considered for example that the number of individual phases of the data stream of the spot is equal to 1. The RaF RaF1 therefore implements a single individual phase associated with a target rate. The bit rate not used by the individual phase of the data stream is used by a so-called common phase.

The SNO can thus generate the RaF1 in the satellite with these values.

The SNO can also create an individual phase management table, making it possible to follow the individual phase(s) of the data stream of the RaFl radio beam. Such a management table can also be provided in the spot state table.

During a next step 72, called “control loop”, the MNO collects the various information on the states of the satellite and the needs (for example If VP_oM, etc) and sends them to the SNO. The SNO can in particular determine the capacity of the Raf Rafl from this information.

For example, the OSS/BSS of the 5G core network (MNO) estimates the number of new connections to be served by the satellite RAN then using the capacity calculation analytical processing presented above, and the satellite spot status table and/or the individual phase management table (notably informing it of the number of individual phases in use), it updates:

the number of new connections able to receive the target bit rate Di (ie the number of connections having an individual phase DebCo, corresponding to Cp;

• the individual bit rate D^ in Mbps, for example 5 Mbps;

• the duration Ti of the individual flow, in seconds, for example 3 s;

• or the individual volume Vi, in Mo, for example 2.5 Mo;

• the probability of non-coverage P out.

The MNO can also complete and/or update the individual phase management table with these different values.

It is noted that the values ​​of Di, TV} and Pout can be dynamically adjusted to optimize the statistical multiplexing. This is an adjustment range of each parameter from the nominal value. For example, the step of estimating the number of new connections to be served by the satellite RAN generates five scenarios using analytical processing by playing on the values ​​of D^ Ti, Vf and Pout by varying their values, for example example from 1 to 5% in steps of 1%. For example, it is possible to increase Pout, to tend towards a value of C, of ​​2. The algorithm can seek to approach the value without seeking to reach it.

The satellite and the SNO can update the status table/spot management table with these different values ​​(73).

The individual phase management table contains in particular the control information for the individual phase or phases. It is used to exchange both control information and instances of individual phases.

An example of a table is presented below.

The first line of values ​​indicates the control parameters of an individual phase. The following lines describe the progress of the individual phases.

<td>Flow Rafl</td><td>Number of free individual phases (or instance type)</td><td>Total number of individual phases C, (or used by an instance)</td><td>D, (Mbps)</td><td>T, (s)</td><td>there_you(MB)</td>

<td>Control</td><td> 1</td><td> 1</td><td> 5</td><td> 3</td><td> 3</td>

[0291] Table 3: Individual phase management table

At this stage, the individual phase management table is empty.

It is noted that such an individual phase management table does not necessarily contain information on the common phase. In this way, the size of the management table remains small, and its transmission remains inexpensive. However, in order to facilitate the understanding of the invention, the information on the common phase is specified in the table in the remainder of the description.

Subsequently, in order to show the operation of the method, it is considered that three user equipments (UE1, UE2 and UE3, as illustrated in [FIG. 6]) are connected to the RaFl. As detailed below, depending on the temporal spacing of their connection, they may or may not have an individual phase. Thus, as illustrated in [Fig.6], the user equipment UE1 has the individual phase of the flow for a duration Ti_l, and the user equipment UE3 has the individual phase of the flow for a duration Ti_3, which does not overlap Ti_l. On the other hand, the user equipment UE2 does not have the individual phase.

More specifically, during a step 74, the user equipment UE1 wishes to establish a connection with the server SI. For example, the UEl sends a “ClientHello” type message CHO (“UEl.Cnxl connection end to end starts: ClientHello 1 RTT phase”) to the server SI, and the server responds with a “ServerHello” type message SHO ( “UEl.Cnxl end to end signaling connection: ServerHello”).

As indicated previously, the RRC module can in particular identify the different phases of the secure connections of the QUIC, TLS, DTLS, EDHOC and similar protocols, by detecting the presence of the initial signaling (“handshake”). In particular, the TLS handshake of an HTTPS connection (idem for QUIC and DTLS and EDHOC) includes an unencrypted part in the “ClientHello” message, in particular the so-called 1-RTT phase which includes the downloading of certificates. For QUIC and TLS, the RRC module distinguishes, based on the presence of the "ClientHello" message, the phases transporting the certificates (QUIC 1-RTT phase) from the reconnection phases with resumption of sessions (resumption of the crypto context, called 0-RTT, of the previous connection).

The RRC module can therefore detect a new UE1.CNX1 connection in the IP stream or streams received by the satellite.

LOSS of the SNO or the satellite verifies whether an individual phase is free for the transmission of start-of-connection data from the satellite to the user equipment UE1 by consulting the management table of the individual phases of the spot.

As the number of free individual phases is equal to 1 (cf table 3), this means that an individual phase is available for the flow when the start of the UE1.CNX1 connection is detected. It is therefore possible to transmit the connection start data coming from the data server SI, between the satellite S AT and the user equipment UE1, at the target rate of the individual phase (Di_l = 5 Mbps), up to a stopping criterion (for example for a duration Ti_l=3 s).

<td>Flow Rafl</td><td>Number of free individual phases or instance type</td><td>Total number of individual phases G (or used by an instance)</td><td>Di (Mbps)</td><td>^Ti(s)</td><td>vi (MB)</td>

<td>Control</td><td> 0</td><td> 1</td><td> 5</td><td> 3</td><td> 3</td>

<td>UE1.CN XI</td><td>Individual</td><td> 1</td><td> 5</td><td> 3</td><td> 3</td>

[0200] Table 4: Individual phase management table

[0201] (t = 0 s after start of UE1.CNX1 connection)

[0202] It is assumed that the user equipment UE2 wishes to establish a connection with the server SI or the server S2. For example, the UE2 sends a “ClientHello” type message to the server S2.

The RRC module detects this new UE2.CNX1 connection in the IP streams received by the satellite, for example one second after the start of the UE1.CNX1 connection.

[0204] LOSS of the SNO or the satellite verifies whether an individual phase is free for the transmission of start-of-connection data from the satellite to the user equipment UE2 by consulting the table for managing the individual phases of the spot.

[0205] Since the number of free individual phases is equal to 0 (see table 4), this means that no individual phase is available for the flow. The connection start data originating from the server S2 is therefore transmitted from the satellite SAT to the user equipment UE2 at a rate lower than the target rate of the individual phase. In other words, the packets of the UE2.CNX1 connection are exchanged in the common phase of the stream.

<td>Flow Rafl</td><td>Number of free individual phases or instance type</td><td>Total number of individual phases Ci (or used by an instance)</td><td>Di (Mbps)</td><td>^Ti(s)</td><td>v, (MB)</td>

<td>Control</td><td> 0</td><td> 1</td><td> 5</td><td> 3</td><td> 3</td>

<td>UE1.CN XI</td><td>Individual</td><td> 1</td><td> 5</td><td> 2</td><td> 2</td>

<td>UE2.CN XI</td><td>commmon</td><td> 0</td><td> 0</td><td> 0</td><td> 0</td>

[0206] Table 5: Individual phase management table

[0207] (t = 1 s after the start of the UE1.CNX1 connection)

It is noted that as the user equipment UE2 arrived one second after the user equipment UE1, the time remaining for the connection UE1.CNX1 on the individual phase of the stream is only 2s.

When the stopping criterion for the transmission on the individual phase is reached, the individual phase is released and available for another transmission.

Thus, if we place ourselves 3.5 seconds after the start of the UE1.CNX1 connection (with Ti_l = 3 s), the individual phase used for the transmission of connection start data to the user equipment UE1 is released, and the transmission of data UE1.CNX1 continues on the common phase of the stream, at a rate lower than the target rate Di;

<td>Flow Rafl</td><td>Number of free individual phases or instance type</td><td>Total number of individual phases Cj (or used by an instance)</td><td>D, (Mbps)</td><td>Ti(S)</td><td>vi (MB)</td>

<td>Control</td><td> 1</td><td> 1</td><td> 5</td><td> 3</td><td> 3</td>

<td>UE1.CN XI</td><td>Commmon</td><td> 0</td><td> 0</td><td> 0</td><td> 0</td>

<td>UE2.CN XI</td><td>Commmon</td><td> 0</td><td> 0</td><td> 0</td><td> 0</td>

[0211] Table 6: Individual phase management table

[0212] (t = 3.5 s after the start of the UE1.CNX1 connection)

It is now assumed that the user equipment UE3 wishes to establish a connection with the server S3. For example, the UE3 sends a “ClientHello” type message to the S3 server.

The RRC module detects this new UE3.CNX1 connection in the IP streams received by the satellite, for example 4 seconds after the start of the UE1.CNX1 connection.

[0215] As the number of free individual phases is equal to 1 (see table 6), this means that an individual phase is available for the flow when the start of the connection

UE3.CNX1 is detected. It is therefore possible to transmit the connection start data coming from the data server S3, between the satellite SAT and the user equipment UE3, at the target bit rate of the individual phase (Di_l=5 Mbps), up to a criterion stopping (for example for a duration Ti_3 = 3 s).

<td>Flow Rafl</td><td>Number of free individual phases or instance type</td><td>Total number of individual phases Cj (or used by an instance)</td><td>D, (Mbps)</td><td>^TiU)</td><td>vi (MB)</td>

<td>Control</td><td> 0</td><td> 1</td><td> 5</td><td> 3</td><td> 3</td>

<td>UE1.CN XI</td><td>Commmon</td><td> 0</td><td> 0</td><td> 0</td><td> 0</td>

<td>UE2.CN XI</td><td>Commmon</td><td> 0</td><td> 0</td><td> 0</td><td> 0</td>

<td>UE3.CN XI</td><td>Individual</td><td> 1</td><td> 5</td><td> 3</td><td> 3</td>

Table 7: Individual phase management table (t = 4 s after start of UE1.CNX1 connection)

The RRC module can in particular send an individual connection start signal DebCoFlag to the RLC module, or directly to the MAC module, in a step 75. As indicated previously, such a signal, also called connection start indicator, can be transported from different ways:

• in a proprietary header, • in an unused bit, for example one of the reserved bits of the “spin-bit” of the QUIC protocol, • in a non-proprietary header, for example iOAM, ECN, etc, to increase interoperability, • etc

[0216]

[0217]

[0218]

[0219]

The choice of signal transport depends in particular on the location of the RLC, RRC and MAC blocks, which depends on the “split” chosen and/or on the manufacturers of these blocks. For example, in the case of split eCPRI A or B (3GPP option 1 or 2) and an implementation of the MAC block and of the RRC block by different manufacturers, this signal is preferentially transported in a predetermined manner between these blocks.

In a step 76, such a connection start signal is for example added by the RLC module in the first frames of the packets carrying the connection start data received from the server SI (UEl.Cnxl_data).

[0222] Optionally, a connection end indicator FinCoFlag can be transmitted (77) to the RLC module or to the MAC module. For example, the connection start indicator DebCoFlag and the connection end indicator FinCoFlag are transmitted in separate signals, and mark only the first and the last packet carrying the connection start data received from the server SI. These signals can be sent directly to the MAC module.

As a variant, DebCoDuration or DebCoVol volume information can be transmitted to the RLC module or to the MAC module. The duration information DebCoDuration corresponds in particular to the duration Tf of an individual phase as defined in the individual phase management table. The DebCoVol volume information item corresponds in particular to a volume V i of data to be transmitted in an individual phase as defined in the individual phase management table. For example, the connection start indicator DebCoFlag can be an integer corresponding to the duration information DebCoDuration and therefore decremented over time. As a variant, the DebCoFlag connection start indicator corresponds to the DebCoVol volume information and is therefore decremented with the size of each frame of the accelerated packets.

On reception of the frames, the MAC module verifies the presence of a DebCoFlag connection start signal. If a DebCoFlag connection start signal is detected, it transmits the corresponding data in the individual phase of the stream of the spot (781). Otherwise, it transmits the frames in the common phase of the stream of the spot, if it has radio resources in transmission. Otherwise, the frames can be put in memory (“buffer”) or “poubellized” by the MAC module.

After the DebCoDuration time or the DebCoVol volume, or upon receipt of a FinCoFlag end of connection signal, the RLC module no longer marks the frames (79). The MAC module therefore transmits the frames carrying “connection tracking” data in the common phase of the stream of the spot (782), if it has radio resources in transmission. Otherwise, the frames can be stored in memory (“buffer”) or canned by the MAC module.

As a variant, the RLC module can memorize or “bind” the unmarked frames depending on the type of RLC module (Transparent Mode (TM), Unacknowledged Mode (UM) or Acknowledged Mode (AM)).

If the user equipment UE1 subsequently reconnects to the same server SI, the 0-RTT phase of the QUIC protocol is implemented (UEl.Cnx2 end to end starts: ClientHello 0-RTT phase”). In this case, the MAC module can directly transmit the frames carrying data received from the server S1 in the common phase of the stream of the spot.

[0228] 5.3 Variants

Examples have been described above in which the mobile intermediate equipment is a satellite. Other mobile access equipment can of course be used, for example an airplane, balloon, drone, HIBS, etc.

Similarly, an implementation of the invention has been described when the RRC, RLC and MAC modules are co-located in the mobile intermediate equipment. As a variant, depending on the “split” chosen, certain modules can be located remotely. In this case, the different signals exchanged (start and/or end of connection indicator, tables, etc.) must have a format compatible with the different modules in order to be processed.

More generally, the invention can be implemented in the various architectures described in relation to [Fig.3] (“Nothing on board”, “RU onboard”, “RU+DU onboard”, “RU+ DU+CU onboard”).

[0232] An example has also been presented in which only one individual phase is available. In other embodiments, multiple individual phases may be available.

Returning to the example described above in relation to FIGS. 6 and 7, a few variants are presented below.

According to a particular embodiment, the OSS of the MNO can update certain parameters, in particular for the existing connections in progress on the individual phase.

For example, if the capacity calculation algorithm presented above proposes to shorten the duration T\ of an individual phase to respond to the arrival of several new user equipments in the radio cell, in addition to UE1, then the duration Ί\ J of the current connection UE1.CNX1 can be reduced, for example by 5%, to accept the connection UE2.CNX2 a little earlier in the individual phase.

According to another example, it is possible to give priority to a request to create a connection UE2.CNX2 from an emergency service. In this case, the duration of the connection in progress UE1.CNX1 can be forced by the OSS of the MNO or the SNO, for example to 95%, to accelerate the transition to the common phase of the transmission, in order to immediately accept the UE2.CNX2 connection to the emergency service in the individual phase.

These different examples illustrate that the parameters can be chosen or updated taking into account the service or the domain of the requested server. For example, a connection to a domain video.example.com can obtain twice the time Ti or megabytes Vf at startup.

[0238] This case applies in particular to connections displaying their type of application (such as IETF APN BoF, MASQUE WG) or in the case of cooperation of one of the BSSs with a CDN ("Content Delivery Network") wishing speed up a service.

Furthermore, as indicated above, in the simplest implementation, the RRC module can classify the 1-RTT phases to transmit the corresponding data on an individual phase of the stream, and the 0-RTT phases for the transmit on a common phase.

In a more sophisticated mode, the initial phases of the QUIC 0-RTT connections can also be transmitted on an individual phase of the stream if such an individual phase is available. This individual phase can have different parameters (in particular D ^ Vi and/or T for example with a switchover to the faster common phase (Τ i = 2 s for example). This reduction takes into account the lower need for data at the start of reconnection due to the presence of application data in the cache of the user equipment.

In another embodiment, the CN ("Common Name") or SAN ("Subject Alternative Name") certificate fields can be used by the RRC module or one of the BSSs to identify a CDN partner, a service type or domain name, and associate a custom control with it. Optionally these parameters differ with the service or domain of the requested server.

In a first implementation, the BSS can supply these rules to the RRC module in a personalization table for the individual phases. This implementation allows the classification of the connection as soon as the connection is detected.

For example, in the personalization table below, a connection to a domain video.example.com obtains at startup twice the time T, or megabytes Vj. On the other hand, the domain foo.example.com will still be classified for transmission in the common phase.

[0244] In addition, connections coming from the 192.168.1.0/24 IP subnet or from the samu.example.com domain preempt the connections in progress on the individual phase, without taking the resources of the common phase, with an infinite duration and unlimited volume.

<td>service</td><td>Di (Mbps)</td><td>Ti(s)</td><td>Vi (MB)</td>

<td>video.example.com</td><td> 5</td><td> 6</td><td> 6</td>

<td>foo.example.com</td><td> 0</td><td> 0</td><td> 0</td>

<td>Source-IP 192.168.1.0/24</td><td> 5</td><td> 0</td><td> 0</td>

<td>Source domain samu.example.com</td><td> 10</td><td> 0</td><td> 0</td>

[0245] Table 8: Individual phase customization table

In a second implementation, a “service” column receiving the domain of the connection can be added to the individual phase management table so that the OSS/BSS of the MNO applies these rules to the connections in progress. This implementation allows the classification of the connections in progress after reception of the table of management of the individual phases.

According to this implementation, using tables 5, 6 and 7 presented above, when the RRC module detects the new UE2.CNX1 connection in the IP streams received by the satellite, for example one second after the start of the UE1.CNX1 connection, we have:

<td>Flow Rafl</td><td>Number of free individual phases or instance type</td><td>Total number of individual phases C, (or used by an instance)</td><td>Di (Mbps)</td><td>D, (s)</td><td>v, (MB)</td><td>Service</td>

<td>Control</td><td> 0</td><td> 1</td><td> 5</td><td> 3</td><td> 3</td><td></td>

<td>UE1.CN XI</td><td>Individual</td><td> 1</td><td> 5</td><td> 2</td><td> 2</td><td>video.example.co m</td>

<td>UE2.CN XI</td><td>commmon</td><td> 0</td><td> 0</td><td> 0</td><td> 0</td><td>foo.example.com</td>

[0248] Table 9: Table for managing individual phases after customization, received from

RaFl one second after the start of the UE1.CNX1 connection

<td>Flow Rafl</td><td>Number of free individual phases or instance type</td><td>Total number of individual phases C, (or used by an instance)</td><td>Sun (Mbps)</td><td>You (s)</td><td>vi (MB)</td><td>Service</td>

<td>Control</td><td> 0</td><td> 1</td><td> 5</td><td> 3</td><td> 3</td><td></td>

<td>UE1.CN XI</td><td>individual</td><td> 1</td><td> 5</td><td> 5</td><td> 5</td><td>video.example.co m</td>

<td>UE2.CN XI</td><td>commmon</td><td> 0</td><td> 0</td><td> 0</td><td> 0</td><td>foo. example, com</td>

<td>UE2.CN XI</td><td>commmon</td><td> 0</td><td> 0</td><td> 0</td><td> 0</td><td>foo. example, com</td>

[0249] Table 10: Individual phase management table after customization, sent by the OSS/BSS to the RaFl

When the RRC module detects the new UE3.CNX1 connection in the IP streams received by the satellite, for example 4 seconds after the start of the UE1.CNX1 connection, we have:

<td>Flow Rafl</td><td>Number of free individual phases or instance type</td><td>Total number of individual phases Ci (or used by an instance)</td><td>Sun (Mbps)</td><td>Τι(s)</td><td>Vf (MB)</td><td>service</td>

<td>Control</td><td> 0</td><td> 1</td><td> 5</td><td> 3</td><td> 3</td><td></td>

<td>UE1.CN XI</td><td>individual</td><td> 1</td><td> 5</td><td> 1</td><td> 1</td><td></td>

<td>UE2.CN XI</td><td>commmon</td><td> 0</td><td> 0</td><td> 0</td><td> 0</td><td></td>

<td>UE3.CN XI</td><td>commmon</td><td> 0</td><td> 0</td><td> 0</td><td> 0</td><td></td>

[0251] Table 7: Individual phase management table after customization

It is noted that the transmission with the first user equipment UE1.CNX1 is always in the individual phase of the stream of the spot. On the other hand, the transmission with the third user equipment UE3.CNX1 is in the common phase of the flow, since the number of free individual phases is always at zero.

In particular, the choice of implementation of the above personalization depends on the location of the RRC block of the centralized unit CU. An “embedded” location of the CU (distant from the OSS/BSS) implies the choice of a common mode of transport (a standardization) of the personalization table of the individual phases / table for the management of the individual phases after personalization.

[0254] 5.4 Matching System

Finally, we present the simplified structure of a communication management system according to at least one embodiment described above, comprising modules for obtaining the number of individual phases, for detecting the start of a connection, and transmitting connection start data.

As already indicated, these modules can be co-located within the same equipment (for example equipment managed by the mobile operator or by the satellite operator), or remote.

[0257] According to the example illustrated in [Fig.8], at least one item of equipment of such a system comprises at least one memory 81 comprising a buffer memory, at least one processing unit 82, equipped for example with a machine programmable calculation machine or a dedicated calculation machine, for example a processor P, and controlled by the computer program 83, implementing steps of the communications management method according to at least one embodiment of the invention .

On initialization, the code instructions of the computer program 83 are for example loaded into a RAM memory before being executed by the processor of the processing unit 82.

The processor of the processing unit 82 implements the steps of the communications management method described above, according to the instructions of the computer program 83, to:

obtain a number of individual phases each associated with a target bit rate in said stream, to be used for transmissions from said mobile intermediate equipment to said radio cell, detect a start of connection of a first user equipment, present in said radio cell, with a first data server, via said mobile intermediate equipment, • transmit connection start data from said first data server, between said mobile intermediate equipment and said first user equipment, at the target rate of the individual phase, up to a stop criterion, if an individual phase is available for said flow, or • transmit connection start data from said first data server, between said mobile intermediate equipment and said first user equipment, at a bit rate lower than said target bit rate, if no individual phase is available for said stream.

According to a particular embodiment, these different steps can be implemented by physical or software modules, co-located or remote.