Communication, management and discovery methods, and devices configured to carry out said methods

Abstract

The invention relates to a method for communicating with a control device (2) in a cellular communication network (NW), the control device being configured to manage application entities (4,5,6) in the network offering services in the network and maintain a profile of these application entities, the method comprising a step of registering a profile in control device, said profile comprising information representative of current deployment conditions of at least one network cell managed by a base station of the network.

Description

Description Title of the invention: Methods of communication, management and discovery, and devices configured to implement these methods Prior art

[0001] The invention belongs to the general field of telecommunications.

[0002] It relates more particularly to the provision of information enabling the improvement of certain functionalities implemented by entities of a cellular communication network. The invention has a preferred but non-limiting application in the context of a cellular communication system or network based on a 5G core network (or 5GC for "5G Core network" in English) defined by the 3GPP standard. In this context, it makes it possible in particular to improve the functionalities implemented by the access and mobility management entity also referred to as AMF (for "Access and Mobility management Function" in English).

[0003] As described in particular in the 3GPP TS 23.501 document entitled "Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 17)", V17.4.0, March 2022, the AMF entity provides various functionalities in a 5G core network such as, for example, the management of the registration of user equipment (or UE for "User Equipment" in English), their connection to the network and their reachability, the management of the mobility of the UEs, authentication and authorization of access to the network, etc.

[0004] When a UE registers with the network, the AMF allocates it a set called a "TAI-list" of identifiers for so-called tracking areas or TAs, each TA comprising one or more cells of the cellular network. Such a TAI-list (TAI meaning "TA Identity" in English) defines the registration area or RA (for "Registration Area" in English). The RA of the UE, which can therefore comprise one or more cells of the cellular network, makes it possible to locate this UE, in particular when it is in standby (or "idle" in English). Indeed, when the network receives a data packet intended for a UE in standby, it sends one or more paging messages in the area defined by its RA. Although in standby, the UE remains listening for paging messages, and when it detects a paging message concerning it, it switches to connected mode and can thus receive the data packet intended for it.

[0005] Furthermore, when a UE enters a cell, it compares the TAI broadcast by the base station managing this cell with the TAIs present in its RA. If the TAI broadcast by the base station is not contained in the RA allocated to it, the UE triggers a registration procedure with the network to inform it of its new location, in other words of the TA it has just entered. The network then allocates a new RA to the UE (i.e. a new TAI-list) containing the TA reported by the UE.

[0006] These procedures make it easy to locate a UE while limiting the signaling exchanged on the network.

[0007] The 3GPP standard does not strictly speaking provide an optimal way to allocate an RA (in other words a TAI-list) to a UE. The AMF can use various information provided by the base stations such as their TAIs, the TAs to which they belong or the network slices they support. However, as highlighted in document S2-2104656 entitled "Some Network slicing topics proposals for rel-18", presented by Nokia and Nokia Shanghai Bell at the 3GPP SA WG2 #145E meeting in May 2021, the 3GPP standard does not currently define a means allowing the AMF to have information concerning in particular the topology of the base stations or their geographical coverage. However, to allocate a relevant RA to a UE taking into account its behavior, particularly in terms of mobility (speed, direction of movement, etc.), it is not sufficient to know which TAs support a given network slice. It is also important to know the adjacency relationships between cells: for example, TAs may be adjacent geographically speaking but not necessarily from a logical point of view (e.g. presence of a physical obstacle between the TAs preventing a UE from moving from one to the other).

[0008] Document S2-2104656 proposes to study this topic within the framework of Release 18 without, however, providing a solution at this stage. Statement of the invention

[0009] The invention meets this need by proposing a method of communication with a control device of a cellular communication network, configured to manage application entities of the network offering services in the network and maintain a profile of these application entities. This method comprises a step of recording a profile with the control device comprising information representative of current deployment conditions of at least one cell of the network managed by a base station of the network.

[0010] Correlatively, the invention also proposes an entity of a cellular communication network comprising a registration module configured to register a profile with a network control device, managing application entities of the network offering services in the network and maintaining a profile of these application entities, said profile recorded by the registration module comprising information representative of current deployment conditions of at least one cell of the network managed by a base station of the network.

[0011] For the purposes of the invention, an application entity is an entity configured to implement one or more processing logics determined in the network such as an entity offering and / or consuming one or more network services. Such an entity may be located in the access network or in the core network (also called the core network or "Core Network" in English), and thus, by means of the services it offers, implement one or more network functionalities, such as for example the functionalities of a network function or NF (for "Network Function" in English) such as an AMF function or an SMF (for "Session Management Function" in English), the functionalities of a base station, etc. It may be a physical or virtual entity, such as for example a virtual instance of a network function or a hardware device hosting such a network function or network function instance.

[0012] In the example of a 5G network defined by the 3GPP standard, a control device managing such application entities and maintaining their profiles is typically a network function NRF (for "Network Repository Function") which, in the current state of the art, manages the profiles of the network functions (or network function instances) of the core network. Each profile associated with an application entity and stored by the NRF function comprises a plurality of attributes likely to be used by other entities of the network wishing to consume the services of the application entity in question, and characterizing in particular its operational state (e.g. its availability, its load, etc.), its characteristics (e.g. its identity, the type of NF function it implements, how to reach it, etc.), the services it offers, the resources it manages, etc.

[0013] The invention therefore proposes, in order to make information representative of the current deployment conditions of the network cells (such as the adjacency relationships of the cells mentioned above) easily accessible to the application entities of the network (and in particular of the core network), to record this information at the level of a network control device (such as an NRF function of a 5G network) already managing profiles of application entities of the network. In other words, the profiles already stored by the control device and relating to the application entities Network profiles are supplemented by other profiles containing information related to the actual deployment of network cells. Various levels of granularity can be considered for these other profiles, namely a profile for each cell in the network or a profile for each base station managing at least one cell in the network.

[0014] Advantageously, storing in a profile maintained by such a control device information representative of current deployment conditions of the network cells facilitates the management and updating, if necessary, of this information, as well as access to it by other network entities which can use existing procedures (standardized or not) to access the profiles of the network application entities to access these other profiles. The invention can thus be implemented by relying on network signaling interfaces already present (network control plane or "Control Plane" in English), such as for example interfaces standardized by the 3GPP standard (e.g. an application programming interface or API (for "Applicative Programming Interface" in English)), in particular when the control device hosts an NRF network function.It does not require the development of an additional management layer, which would make the system more complex and limit the dynamic nature of information exchanges, for example in the event of a change in deployment conditions (e.g. linked to an automatic reconfiguration of a base station and the modification of neighborhood information that may result from this).

[0015] Thanks to the information made available by the invention, the quality of the decisions taken in the network, and in particular in the core network, can be improved. By information representative of current deployment conditions of a cell, we mean information which reflects the real conditions in which the cell is deployed at the time considered. Different types of information are concerned. For example, at least one said information representative of current deployment conditions relates to: a layout of the cell in a network architecture (e.g. coverage, radio neighborhood), a geographic environment of the cell, a type of deployment of the cell, a configuration of at least one antenna of the cell, at least one infrastructure covered by the cell (e.g. road, railway, building, etc.), and / or a state of the cell (e.g.cell load, load at each network slice, number of active users, uplink (UL) or downlink (DL) throughput, congestion indicators, alarm status, security status, etc.).

[0016] This information is dynamic and likely to change over time, typically due to a reconfiguration of the base stations, the appearance of new infrastructures, the extinction of certain cells (e.g. small cells planned for capacity reasons, during periods when the network is little used such as at night, in order to reduce the energy consumption of the network), etc. Such information is, with the exception of certain information relating to the state of the cell, not known today to the base stations: the base station is not aware of the actual deployment context of the cells that it manages, it only has radio parameters that it uses to manage the quality of the radio links, maintain communications using measurements that it carries out and / or that are reported by the UEs and / or broadcast cell selection / reselection parameters to the UEs.This type of information is not currently used by base stations in the processing entrusted to them. As for information relating to the state of the cell and / or the base station, it is not shared with other entities, whether UEs, other base stations in the cellular network or network functions in the core network.

[0017] Knowledge of the actual deployment of network cells can be used to improve the efficiency of the procedures implemented in the network, whether in the core network or in the access network, and incidentally the resulting quality of service. For example, the mobility predictions of a UE made by a Network Data Analytics Function (NWDAF) in a 5G network can be facilitated and made more accurate if it is known that the UE is moving on a main road axis (e.g., the NWDAF function can give a higher probability to the positions of the UE located on this road axis). According to another example, information on the congestion of a cell or the average throughput achieved in UL and / or DL ​​can influence the quality of service predictions, and the decisions taken from these predictions.According to yet another example, if we consider a context in which a base station can query the control device to access information on current conditions of deployment of the cells of the network, such information can be useful to it in deciding on a transfer between cells (or "handover" in English) and the terms of this transfer (typically the target base station towards which to trigger this transfer). Of course, these examples of exploitation of the invention are given for illustrative purposes only.

[0018] It should be noted that other information relating to the cell, in addition to the information of current deployment conditions of the cell, may be registered in the profile with the control device, such as for example static configuration information of the cell such as: an identity of the cell; and / or a frequency band allocated to the cell; and / or at least one radio access technology associated with the cell; etc. or other information more related to the operational functioning of the network such as for example the TA membership of a cell.

[0019] This list is not exhaustive of course, and it is possible to consider enriching the profile of the cell or the base station with other information, such as for example with information relating to the base station, already known and shared by the latter in the state of the art, such as its identity, the list of TAs and / or slices that it supports, or information relating to a state of the base station (e.g. load level, congestion level), etc.

[0020] As mentioned above, the invention is particularly applicable in the context of a 5G network. However, it can be used in other contexts.

[0021] Indeed, some players in the telecommunications sector are anticipating for the 6 èmegeneration of mobile networks (also more commonly called 6G), a blurring of the boundaries between access network(s) and core network. In this perspective, network architectures based on control plane signaling interfaces can offer significant advantages, making it possible to access internal contexts specific to virtualized network equipment / functions. The invention can therefore easily be applied in such a context as well.

[0022] In a particular embodiment, the information relating to the deployment conditions of the cells is recorded with the control device directly by the base stations managing these cells. The invention therefore also relates to a base station of a cellular communication network hosting an entity according to the invention, said information relating to at least one cell managed by said base station.

[0023] In this embodiment, some or all of the information relating to the current deployment conditions of the network cells may be configured at the base stations by the network operator (e.g., as unstructured metadata (e.g., XML, JSON, YAML, etc. formats) in a standardized or network operator-specific data repository) or be acquired or determined by the base stations themselves.

[0024] Thus, the communication method, when implemented by the base station, may comprise a step of evaluating at least part of said information before recording it with the control device.

[0025] By way of illustration, it may be envisaged that the base station evaluates the geographical extent of the coverage area of ​​a cell from the geographical positions of the UEs served by it, these positions being able to be provided by satellite positioning modules (e.g. GPS (for "Global Positioning System" in English), GNSS (for "Global Navigation Satellite Systems" in English)) equipping the UEs or deduced by the base station from information which it has on these UEs such as their speed or an observed difference in arrival time (or OTDOA for "Observed Time Difference of Arrival" in English)).

[0026] Alternatively, the communication method, when implemented by the base station, may comprise a step of obtaining, from a radio planning system adapted to the network, at least part of said information before recording it with the control device.

[0027] A radio planning system can typically provide information on the type of deployment envisaged for the cell: in a dense, suburban or rural area, in line of sight (LOS for "Line Of Sight" in English) or not (NLOS for "Non Light Of Sight" in English), event-based or temporary deployment, configuration of the cell (e.g. macro, micro or pico cell), configuration of the cell's antennas (e.g. distributed antenna system or DAS (for "Distributed Antenna System" in English), etc. It can also provide information on the infrastructures covered by the cell, for example if it is deployed to cover a road, a waterway, a port, a railway, a station, and if necessary identify the infrastructures in question.

[0028] In a particular embodiment, the information relating to the deployment conditions of the cells is recorded with the control device via an application entity of the network which obtains this information from the base stations. Such an application entity is for example a cellular network access management device such as an AMF network function in the context of a 5G network. The invention therefore also relates to an access management device of a cellular communication network hosting an entity according to the invention.

[0029] In a particular embodiment in which the communication method is implemented by an access management device of the cellular network, the communication method may comprise a step of obtaining at least part of said information from the base station during an association of said base station with said access management device.

[0030] The invention therefore also relates to a base station of a cellular communication network comprising a transmission module configured to transmit to an access management device of the cellular network a profile comprising information representative of current deployment conditions of at least one cell of the network managed by the base station.

[0031] This embodiment has a preferred but non-limiting application when the base station does not support one or more protocols used on the signaling interfaces with the control device; it therefore proposes to go through an intermediate entity of the core network capable of communicating directly with the control device and in particular of recording a profile with this control device.

[0032] Thus, in the example of a 5G network and an NRF function type control device, this embodiment can be advantageous in particular when the base station does not support the HTTP2 protocol allowing the services of the NRF function to be consumed. The invention then proposes to exploit the procedure for associating the base station with the access management device (AMF in the example of the 5G network) to communicate the current deployment information of the cells that it manages to the access management device, then instructing the latter to record this information with the network control device in a profile, in a similar or identical manner to how it registers its own profile with that control device.

[0033] Of course, it is possible to envisage the base station transmitting information on current deployment conditions of the cells it manages at another time, either in a dedicated message exchanged with the access management device, or during another exchange provided for by the standard with this device.

[0034] As mentioned above, the invention relies on recording information on current deployment conditions of network cells in profiles maintained by a network control device. It also relies on making this information on current deployment conditions available by the control device, and on exploiting this information.

[0035] Thus, according to another aspect, the invention relates to a method of management by a control device of a cellular communication network, configured to manage application entities of the network offering services in the network and maintain a profile of these application entities, said method comprising: a step of recording a profile provided by an entity of the cellular network and comprising information representative of current deployment conditions of at least one cell of the cellular network managed by a base station of the network; in response to a discovery request received from a so-called requesting device of the network, a step of transmitting all or part of said profile to said requesting device.

[0036] Correlatively, the invention also relates to a device for controlling a cellular communication network configured to manage application entities of the network offering services in the network and maintain a profile of these application entities, said control device comprising: a recording module, configured to record a profile provided by an entity of the cellular network, said profile comprising information representative of current deployment conditions of at least one cell of the cellular network managed by a base station of the network; and a response module, configured to transmit in response to a discovery request received from a so-called requesting device of the network, all or part of said profile to said requesting device.

[0037] As mentioned above, the profile may be provided to the control device by the base station or by an intermediate network entity such as a cellular network access management device (e.g. AMF function).

[0038] The management method and the control device benefit from the same advantages cited above as the communication method and the entity according to the invention.

[0039] In a particular embodiment, the management method comprises: a step of updating at least one said item of information in said profile; and a step of notifying said at least one updated item of information to said requesting device.

[0040] This notification may be made following a request from the requesting device, or spontaneously, for example when the requesting device has subscribed to a service from the control device for notification of changes affecting said profile.

[0041] This embodiment makes it possible to keep the application entities of the network using the information on cell deployment conditions informed of any changes in these conditions.

[0042] According to yet another aspect, the invention relates to a method of discovery by a so-called requesting device of a cellular communication network, said method comprising: a step of sending a discovery request to a network control device configured to manage application entities of the network proposing services in the network and maintaining a profile of these application entities, said discovery request relating to at least one cell managed by a base station of the cellular network; a step of receiving a response to said discovery request comprising information representative of current deployment conditions of said at least one cell stored in a profile maintained by the control device; and a step of using all or part of said information received when providing a functionality implemented by the requesting device in the network.

[0043] Correlatively, the invention also relates to a so-called requesting device of a cellular communication network comprising: a sending module configured to send a discovery request to a network control device managing application entities of the network proposing services in the network and maintaining a profile of these application entities, said discovery request relating to at least one cell managed by a base station of the cellular network; a receiving module, configured to receive a response to said discovery request comprising information representative of current deployment conditions of said at least one cell stored in a profile maintained by the control device; and a use module, configured to use all or part of said information received when providing a functionality implemented by the requesting device in the network.

[0044] The discovery method and the requesting device benefit from the same advantages mentioned above as the communication method, the management method, the entity and the control device according to the invention. It is noted that it may be a device of the core network, such as for example a device hosting a network function (or an instance of a network function), or a device of the access network, such as for example a base station.

[0045] In a particular embodiment, the communication, management and discovery methods are implemented by a computer.

[0046] The invention also relates to a computer program on a recording medium, this program being capable of being implemented in a computer or more generally in an entity in accordance with the invention and comprising instructions adapted to the implementation of a communication method as described above.

[0047] The invention also relates to a computer program on a recording medium, this program being capable of being implemented in a computer or more generally in a control device in accordance with the invention and comprising instructions adapted to the implementation of a management method as described above.

[0048] The invention also relates to a computer program on a recording medium, this program being capable of being implemented in a computer or more generally in a requesting device in accordance with the invention and comprising instructions adapted to the implementation of a discovery method as described above.

[0049] Each of these programs may use any programming language, and may be in the form of source code, object code, or code intermediate between source code and object code, such as in a partially compiled form, or in any other desirable form.

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

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

[0052] On the other hand, the information or recording medium may be a transmissible medium such as an electrical or optical signal, which may be conveyed via an electrical or optical cable, by radio link, by wireless optical link or by other means.

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

[0054] Alternatively, the information or recording medium may be an integrated circuit in which a program is incorporated, the circuit being adapted to execute or to be used in the execution of the communication, management and discovery methods according to the invention.

[0055] According to another aspect, the invention relates to a system in a cellular communication network comprising: at least one base station managing at least one cell of the network; at least one entity of the network according to the invention; a control device according to the invention; and at least one requesting device according to the invention.

[0056] In a particular embodiment, the network entity is hosted by the base station.

[0057] In another embodiment, the network entity is hosted by a network access management device and the base station is in accordance with the invention.

[0058] It may also be envisaged, in other embodiments, that the communication, management and discovery methods, and the entity, control device, requesting device and system according to the invention have in combination all or part of the aforementioned characteristics. Brief description of the drawings

[0059] Other characteristics and advantages of the present invention will emerge from the description given below, with reference to the appended drawings which illustrate an exemplary embodiment thereof without any limiting character. In the figures: [Fig. 1] Figure 1 represents, in its environment, a system in a network according to the invention, in a first embodiment; [Fig. 2] Figure 2 schematically represents the hardware architecture of a computer capable of hosting an entity, a control device and a requesting device according to the invention; [Fig. 3] Figure 3 represents the functional modules of an entity, a base station, a control device and a requesting device according to the invention, in the first embodiment; [Fig. 4] Figure 4 illustrates, in a first example of application, the steps of the communication, management and discovery methods implemented by the system of Figure 1 in the first embodiment; [Fig. 5] Figure 5 illustrates, in a second application example, the steps of the communication, management and discovery methods implemented by the system of Figure 1 in the first embodiment; [Fig. 6] Figure 6 represents, in its environment, a system in a network according to the invention, in a second embodiment; [Fig. 7] Figure 7 represents the functional modules of an entity, an access management device, a control device and a requesting device according to the invention, in the second embodiment; [Fig. 8] Figure 8 illustrates the steps of the communication, management and discovery processes implemented by the system of Figure 6 in the second embodiment. Description of the invention

[0060] Figure 1 represents a system 1 in a cellular communication NW network, according to the invention, in a first embodiment of the invention. The NW network is here a 5G network as defined by the 3GPP standard, managed by an operator OP, the NW network comprising at least one access network AN and a core network CN.

[0061] As is known per se, the CN core network relies on a plurality of network functions or NF (network application entities within the meaning of the invention) offering various services and implementing various functionalities in the CN core network, such as for example an AMF function managing access to the network and the mobility of UEs attached to the network, an SMF function managing the sessions established in the network, an NRF function maintaining the profiles of the NF functions of the network, an NWDAF function for data collection and network prediction, etc. One or more instances of each of the NF functions of the CN core network can be deployed to ensure the operational functioning of the latter.

[0062] To access the services offered by the NW network, a user equipment or UE 2 connects to the core network CN via the access network AN, and more particularly a gNB 3 base station of this access network. There is no limitation on the nature of the UE 2: it can be a smartphone, a laptop, a tablet, an object, a machine or a connected vehicle, etc.

[0063] In a manner known per se, each gNB base station (and in particular base station 3) is configured to manage one or more cells of the NW network. By "cell" is meant here a "unitary" geographical area of ​​the NW network to which is associated a cell identifier (or "NR Cell Identity" in English) designating it uniquely, and transmission parameters (e.g. a frequency band). It should be noted that the same transmission parameters can be used simultaneously by several cells of the network duly distributed to limit interference. In the example of Figure 1, it is assumed that base station 3 is a tri-sector gNB and thus manages three cells of the network C1, C2 and C3 corresponding respectively to the three sectors covered by base station 3.

[0064] There are no limitations on the type of base stations considered for the AN network. Fixed and / or mobile base stations can be considered (for example, embedded in a vehicle, in a drone or more generally in any system likely to move).

[0065] As mentioned above, the 5G context which has just been described is not limiting in itself; the invention can in fact be applied to other networks, such as for example a 6G network, a proprietary network, etc.

[0066] According to the invention, the system 1 comprises: at least one base station gNB managing at least one cell of the NW network, namely the base station 3 managing the cells C1, C2 and C3 of the NW network; at least one requesting device, according to the invention, namely in the first embodiment described here, the instance 4 of network function AMF, the instance 5 of network function SMF and the instance 6 of network function NWDAF. Of course, these examples are given only for illustrative purposes, and other entities of the NW network, in particular other network functions or instances of network functions of the core network CN or base stations of the access network AN may be requesting devices within the meaning of the invention; at least one entity 7 of the NW network according to the invention. In the first embodiment illustrated in FIG. 1, the entity 7 is hosted in the base station 3.However, as detailed later with reference to a second embodiment of the invention, the entity 7 may be hosted in other entities of the NW network, and in particular in a device hosting a network function of the CN core network, such as for example in the device hosting the AMF network function instance 4; a device 8 for controlling the NW network, in accordance with the invention, managing various application entities of the network and maintaining a profile of each of them. This control device 8 is, in the context of the 5G network envisaged here, a device hosting an NRF network function (also referred to as NRF device 8 in the following), which in a manner known per se, manages the NF function instances of the CN core network and maintains a profile of each of these instances, generally noted here NFPROF. Each NFPROF profile is associated with an NF function instance. and stored by the NRF function comprises a plurality of attributes likely to be used by other entities of the CN core network wishing to consume the services of the instance in question, and characterizing in particular its operational state (e.g. its availability, its load, etc.), its characteristics (e.g. its identity, the type of NF function that it implements, how to reach it, etc.), the services that it offers, the resources that it manages, etc. In accordance with the invention, and as detailed further below, the NRF device 8 also maintains a profile noted gNBPROF for each of the gNB base stations of the NW network (or at least some of them), or in an alternative embodiment, a profile noted CelIPROF for each of the cells of the NW network managed by all or some of the gNB base stations of the network. The choice of one or other of the options (one profile per base station or one profile per cell) is left to the operator OP of the NW network.In the remainder of the description, the NRF device 8 maintains a gNBPROF profile per gNB base station of the AN access network.

[0067] It should be noted that the system 1 may comprise a plurality of control devices 8 according to the invention, each control device 8 being configured to manage at least part of the network functions of the core network CN and maintain the profiles of at least part of the base stations of the access network AN or the profiles of the cells managed by said at least part of the base stations.

[0068] In the first embodiment described here, the NRF device 8, the entity 7 (and the base station 3 hosting it) and the requesting devices 4, 5 and 6 have the hardware architecture of a computer 9 as shown in FIG. 2, or are hosted by the computer 9.

[0069] The computer 9 comprises in particular a processor 10, a random access memory 11, a read-only memory 12, a non-volatile memory 13, and communication means 14 allowing in particular the NRF device 8, the entity 7 hosted by the base station 3 and the instances 4, 5 and 6 of the system 1 to communicate with each other, as well as with devices of the core network CN and / or more generally of the cellular network NW, or with entities external to the network, such as for example with a radio planning system 15 adapted to the NW network (e.g. that used by the operator OP of the NW network to deploy its network).

[0070] The non-volatile memory 13 of the computer 9 constitutes a recording medium in accordance with the invention, readable by the processor 10 and on which one or more computer programs in accordance with the invention are recorded.

[0071] More specifically, the non-volatile memory 13 of the computer 9 comprises, when it is the NRF device 8 or when it hosts the NRF device 8, a recording of a computer program PROG1, comprising instructions defining the main steps of a management method according to the invention.

[0072] This program PROG1 defines the functional modules of a control device according to the invention (such as the NRF device 8 in the first embodiment described here), which rely on or control the hardware elements 10 to 14 of the computer 9 mentioned above. These modules include in particular, as illustrated in FIG. 3: a profile recording module 8A, configured to record, for example in the non-volatile memory 13, the NFPROF profiles of the application entities of the CN core network, and more particularly instances of network functions of the CN core network (e.g.instances of AMF function 4, SMF function 5 and NWDAF function 6), but also, in accordance with the invention, to record the gNBPROF profiles of the base stations of the NW cellular network (and more particularly of the AN access network of the NW cellular network), each gNBPROF profile associated with a gNB base station of the NW network comprising, for each cell managed by the base station in question, information representative of the current deployment conditions of this cell. As mentioned previously, in an alternative embodiment, the recording module 8A is configured to record a CelIPROF profile for each cell managed by. a gNB base station of the AN network, each CelIPROF profile being associated with a cell comprising information representative of the current deployment conditions of this cell. In the first embodiment described here, the gNBPROF profiles of the base stations of the AN network are provided to the registration module 8A by the base stations themselves; and a response module 8B, configured to transmit, in response to a discovery request REQ received from a device of the NW network (for example one of the requesting devices hosting the instances 4, 5 and 6) relating to at least one search criterion CRU, all or part of the profiles recorded by the registration module 8A in the non-volatile memory 13, and which are associated with entities of the NW network meeting the search criterion CRIT indicated in the discovery request.For example, the CRU criterion relates to at least one cell of the NW network, and the response module 8B is configured to respond to the received discovery request by providing it with all or part of the CelIPROF profile(s) corresponding to the CRU criterion.

[0073] In the first embodiment described here of an NRF 8 device as defined by the 3GPP standard, the registration modules 8A and 8B for response respectively use the logic of the Nnrf_NFManagement and Nnrf_NFDiscovery services described in the 3GPP documents TS 23.502 entitled “Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2; (Release 17)”, V17.4.0, March 2022, and TS 29.510 entitled “Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3; (Release 17)”, V17.5.0, March 2022 (with the necessary adjustments for the implementation of the invention detailed later).

[0074] The operation of the modules 8A and 8B of the NRF device 8 is described in more detail later with reference to the steps of the management method according to the invention.

[0075] Furthermore, the non-volatile memory 13 of the computer 9 comprises, when it is the base station 3 hosting the entity 7 or when it hosts the base station 3, a recording of a computer program PROG2, comprising instructions defining the main steps of a communication method according to the invention.

[0076] This program PROG2 defines the functional modules of an entity 7 according to the invention (and of the base station 3 hosting the entity 7, in the first embodiment, or of an access management device in the second embodiment as described further below), which rely on or control the hardware elements 10 to 14 of the computer 9 cited above. These modules include in particular, as illustrated in FIG. 3, a recording module 7A configured to record here the profile gNBPROF(3) of the base station 3 with the NRF device 8.As mentioned previously, in an alternative embodiment, the module 7A can be configured to record with the NRF device 8 the CelIPROF profile of each cell managed by the base station 3, i.e. the profiles CellPROF(Cl) of the cell Cl, CellPROF(C2) of the cell C2 and CellPROF(C3) of the cell C3, each profile of a cell comprising information representative of the current deployment conditions of this cell.

[0077] The operation of the module 7A of the entity 7 hosted by the base station 3 is described in more detail later with reference to the steps of the communication method according to the invention.

[0078] Finally, the non-volatile memory 13 of the computer 9 comprises, when it is a requesting device or when it hosts such a requesting device, a recording of a computer program PROG3, comprising instructions defining the main steps of a discovery method according to the invention.

[0079] This PROG3 program defines the functional modules of a requesting device according to the invention (such as the AMF 4, SMF 5 and NWDAF 6 instances in the first embodiment described here), which rely on or control the hardware elements 10 to 14 of the computer 9 cited previously. These modules include in particular, as illustrated in Figure 3: a sending module 16A configured to send a discovery request to the NRF device 8. This discovery request relates to at least one search criterion CRIT, for example on at least one cell of the NW network managed by a base station of the cellular network; a receiving module 16B, configured to receive a response to the discovery request.If the search criterion CRIT indicated in the discovery request relates to at least one cell of the NW network, then the response received from the NRF device 8 comprises information representative of current deployment conditions of said at least one cell stored in said at least one gNBPROF profile of said at least one base station managing said at least one cell, maintained by the NRF device 8; and a usage module 16C, configured to use all or part of said received information, for example when providing a functionality implemented by the requesting device in the NW network. For example, if the requesting device is the AMF instance 4, the module 16C can use the deployment conditions information provided by the NRF device 8 to determine the RA of a UE.In another illustrative example, if the requesting device is the SMF instance 5, the module 16C may use the deployment condition information provided by the NRF device 8 to determine certain parameters of a session with a UE. In yet another example, if the requesting device is the NWDAF instance 6, the module 16C may use the deployment condition information provided by the NRF device 8 to improve its predictions about a UE.

[0080] The operation of the modules 16A to 16C of the requesting device according to the invention is described in more detail later with reference to the steps of the discovery method according to the invention.

[0081] We will now describe, with reference to figure 4 which illustrates a first example of application of the invention, the main steps of the communication, management and discovery methods according to the invention when they are implemented respectively in the first embodiment of the invention, by the base station 3 hosting the entity 7, by the NRF device 8, and by the AMF 4 and SMF 5 instances.

[0082] It is assumed here that, following its activation by the operator OP of the NW cellular network and its start-up, the base station 3 registers its profile gNBPROF(3) with the NRF device 8 (step E10), via its registration module 7A. As mentioned previously, in accordance with the invention, the profile gNBPROF(3) contains, for each cell C1, C2, C3 managed by the base station 3, information INFO_CURR representative of the current deployment conditions of these cells. This information INFO_CURR reflects the actual deployment of the NW network at a given time, i.e., the geographical areas and infrastructures covered by the cells, the topology of the network architecture (e.g. adjacency between cells), etc. They are dynamic in the sense that they can evolve over time, depending on the decisions taken by the operator OP of the NW network or autonomously by the base stations (e.g. reconfiguration of certain base stations, etc.), the movement of base stations (especially when they are mobile), the switching off of certain cells (for example to limit the network's energy consumption), the appearance of new infrastructures (e.g. roads, buildings, etc.), etc.

[0083] Thus, for example, the INFO_CURR information may include all or part of the following information: information relating to the arrangement of the cell in the network architecture, such as the logical or radio neighborhood of the cells (for example in the form of the identity of the neighboring cells of said cell); information relating to the geographical environment of the cell such as the geographical area covered by the cell (expressed for example from the coordinates (latitude and longitude) of the center of the cell and its radius, or from a polygonal spatial pattern using the same type of coordinates or via a reference to a coverage map, etc.); information relating to the type of cell deployment, such as indoor / outdoor deployment, line-of-sight (LOS) or indirect line-of-sight (NLOS), in a white, dense, suburban or rural area, for coverage or capacity purposes, in support of a private network, infrastructure or critical vertical, event / temporary deployment, deployment configuration (e.g. macro / small / pico cell, or cell managed by a base station on board a high-altitude platform, a drone or a satellite, etc.); information relating to a configuration of at least one antenna of the cell such as the position and orientation of this antenna (latitude, longitude, altitude, height above ground, azimuth, inclination), the deployment of a distributed antenna system (or DAS); information relating to at least one infrastructure covered by the cell, for example a road axis, a railway, a waterway, one or more buildings, an industrial zone, etc. (expressed for example in the form of the identity of the infrastructure in question); information relating to the state of the cell, such as the load or load level (e.g. low, medium, high) of the cell, the load or load level of the cell at the level of each network slice, the number of active users in the cell, the uplink (UL) or downlink (DL) throughput, congestion indicators (e.g.radio resource utilization rate, number of packets in queue), a fault state or alarm level, a security status (e.g. jamming detection, detection of Man In The Middle attacks, fake base stations, distributed denial of service (DDoS), compromise by botnets), etc.

[0084] This list is of course not exhaustive and other information representative of common cell deployment conditions may be contained in the profiles. In addition, profiles may contain other INFO_SUPP information, such as static cell configuration information, such as: a cell identity; a frequency band used by the cell; at least one radio access technology associated with the cell (e.g. GERAN, UTRA, E-UTRA, NR); etc.

[0085] It should be noted that it is possible that some of this information, which is static today in the context of 5G networks, may become more dynamic in a later version (or "Release" in English) of these networks or in another context.

[0086] The gNBPROF(3) profile of the base station 3 may further contain INFO_gNB information relating to the base station 3 such as its identity (for example in the form of a “Global RAN Node ID” identifier), the list of TAs and / or slices that it supports, information representative of its state (e.g. load or load level, number of users using the base station), etc.

[0087] The profile gNBPROF(3) is stored for example in the non-volatile memory 13 of the base station 3. It should be noted that the information INFO_CURR, INFO_SUPP and / or INFO_gNB may have been configured at the base station 3 by the network operator OP (via means known per se and not described here), or be obtained or discovered dynamically by the base station 3.

[0088] For example, the base station 3 can evaluate some of this information itself, such as the geographical area covered by each of the cells C1, C2 and C3. For this purpose, it can in particular use the geographical location of the UEs which are attached to the cell in question, this location being able to be sent by satellite positioning modules (or PNT for “Positioning Navigation and Timing Service” in English) such as GPS or GNSS modules equipping the UEs or being able to be calculated by the base station 3 from the TDOA information and speeds available to it on the UEs. Thanks to the location of the UEs and knowledge of the cells serving each of these UEs, the base station 3 can establish a “map” of the UEs and deduce the coverage limits of each cell.

[0089] According to another example, particularly well suited in the case of a mobile base station 3 equipped with a PNT receiver and a compass, the base station 3 can evaluate the position and orientation of the antennas serving the cells that it manages from the positions returned by its PNT receiver and the indications provided by its compass.

[0090] According to yet another example, the base station 3 can determine the identity of the neighboring cells of each cell that it manages by using the ANR (Automatic Neighbor Relation) functionality of the SON (Self-Organizing Networks) technology designed in a manner known per se to allow self-configuration, self-operation and self-optimization of the equipment of a cellular communication network.

[0091] According to another example, base station 3 can deduce information relating to the state of the cell from its own state: for example, if base station 3 encounters an overload problem typically caused by the limitation of its processing capacities, this will have repercussions on the state of the cells that it manages which will themselves be in an overloaded state.

[0092] In addition, the base station 3 has, in a manner known per se, information on the use of network resources. From this information, it can detect a state (or level) of congestion of the cells that it manages. Such congestion is likely to affect different types of resources used by the cell, such as radio resources or PRB (for "Physical Resource Block" in English), buffer memories (or buffers in English) or even radio channels (e.g. traffic, signaling or paging channels), and occurs when 100% of the resources in question are used (e.g. 100% of the buffers are full). To detect such a state, various advanced indicators of congestion can be monitored such as, for example, a percentage of resource use that approaches a critical threshold, an increase in delays or packet losses observed on the cell, etc. These indicators can be considered among the INFO_CURR information.

[0093] The base station 3 can also obtain some of the information from third-party entities, for example from entities of the NW network or from external entities. In particular, it can be envisaged that the base station 3 is configured to communicate with the radio planning system 15 adapted to the NW network, and obtain certain information from this radio planning system, such as for example the information relating to the type of deployment of the cells C1, C2 and C3 that it manages, the identity of the infrastructures covered by each of these cells, or even the information relating to the deployment configuration of these cells.

[0094] The base station 3 may also have knowledge of some of this information because it uses it to implement the processing for which it is responsible (e.g., identity of neighboring cells, frequency band used by each cell or access network technology implemented in each cell), or because it is configured to broadcast this information on the NW network (e.g., identity of the cells it manages, list of TAs and / or network slices it supports).

[0095] The nature of the information INFO_CURR, and where applicable INFO_SUPP and INFO_gNB, contained in the profile gNBPROF(3) of base station 3 can be defined by default at the level of base station 3 (and more precisely of entity 7), for example by the operator of the NW network, or by a management platform also known as an OAM platform (for “Operations, Administration and Maintenance” in English).

[0096] To register the gNBPROF profile of the base station 3 with the NRF device 8, in the first embodiment described here, the registration module 7A uses the Nnrf_NFManagement_NFRegister service defined in the 3GPP TS 23.502 and TS 29.510 documents cited above, adapted for the purposes of the invention. More specifically, the service registration request Nnrf_NFManagement_NFRegister (message “Nnrf_NFManagement_NFRegister Request”), usually used by the NF functions of the core network CN to register their respective NFPROF profiles with the NRF device 8, is adapted to be used by the base station 3 (and more particularly by the registration module 7A of the entity 7 hosted by the base station 3) to register its gNBPROF(3) profile. This adaptation consists of modifying the request so that it contains in the gNBPROF(3) profile, for each cell C1, C2 and C3 managed by the base station 3, the INFO_CURR information, and where appropriate the INFO_SUPP and INFO_gNB information. Such an adaptation is obvious to those skilled in the art and is not described further here.

[0097] Upon receipt of the registration request from the base station 3, the NRF device 8, via its registration module 8A, stores the profile gNBPROF(3) for example in its non-volatile memory 13 (step E20).

[0098] Then it sends via its registration module 8A a confirmation message (message “Nnrf_NFManagement_NFRegister Response”) of the registration of the profile gNBPROF(3) to the base station 3 using the service Nnrf_NFManagement_NFRegister, in a similar or identical manner to what it does when registering the profile of an NF function (step E30).

[0099] It is now assumed that when it detects the activation of a new base station (namely here of the base station 3), the AMF instance 4 interrogates the NRF device 8 to obtain information on the cells of the NW network managed by this new base station 3 located in its service area (in other words, in the TAs that the AMF instance 4 serves) (step E40). For this purpose, in the first embodiment described here, the sending module 16A of the AMF instance 4 uses the Nnrf_NFManagement_NFDiscovery service defined in the 3GPP documents TS 23.502 and TS 29.510 cited previously, adapted for the needs of the invention.More specifically, the sending module 16A of the AMF instance 4 sends to the NRF device 8 a discovery request (message “Nnrf_NFManagement_NFDiscovery Request”) as defined by the Nnrf_NFManagement_NFDiscovery service indicating as search criteria the identity of the newly detected base station 3 and the TAs served by the AMF instance 4.

[0100] It is noted that as a variant, this interrogation of the NRF device 8 by the AMF instance 4 can occur at times other than in reaction to the activation of the base station 3. Thus, for example, this interrogation can be triggered when the AMF instance 4 detects that it needs information concerning a UE that it manages.

[0101] Upon receipt of the discovery request from the AMF instance 4, the NRF device 8 consults the profiles recorded in its non-volatile memory 13, selects the candidate base stations matching the search criteria indicated in the discovery request (the base station 3 in the example considered here), and responds to the AMF instance 4 via its response module 8B using the Nnrf_NFManagement_NFDiscovery service (step E50). According to the invention, the response (message “Nnrf_NFManagement_NFDiscovery Response”) sent by the response module 8B comprises all or part of the gNBPROF(3) profile of the base station 3. In particular, for each cell managed by the base station 3, the response sent by the response module 8B comprises all or part of the INFO_CURR information, and where appropriate all or part of the INFO_SUPP and INFO_gNB information, associated with this cell and contained in the gNBPROF(3) profile.It is noted that sending only part of the gNBPROF(3) profile of the base station 3 may result from limitations specified in the search criteria CRIT indicated in the discovery request, but also from a configuration of the NRF device 8 (for example, the NRF device 8 may be configured to provide such types of information to such type of application entity).

[0102] Upon receipt of this response by its reception module 16B, the AMF instance 4 extracts the information contained in the response and stores it, for example, in its non-volatile memory 13. The AMF instance 4 deduces from the information it has received on the cells managed by the base station 3 forming part of the TAs it serves, indications on these TAs (for example, their topology, the adjacency relationships between these TAs, the type of deployment applied in these TAs, etc.) (step E60).

[0103] It is noted that other factors may trigger the sending of a discovery request by the AMF instance 4 to the NRF device 8. For example, such a discovery request may be sent when the AMF instance 4 is put into service by the operator OP of the NW network (and of the core network CN), in which case the discovery request may relate to the cells covered by several base stations of the NW network if this proves relevant (typically if several base stations serve the service area of ​​the AMF instance 4 or are discovered by the AMF instance when it is put into service).

[0104] It is now assumed that the UE 2 registers with the core network CN via the base station 3 (step E70). In a manner known per se, the registration request of the UE 2 ("Registration Request") is transmitted to an AMF instance, for example here to the AMF instance 4. If the registration request of the UE 2 is accepted, the AMF instance 4 then determines its registration area RA (step E80). During this determination (functionality implemented by the AMF instance 4 within the meaning of the invention), the module 16C for using the AMF instance 4 can advantageously use, thanks to the invention, the indications obtained during step E60, which allows it to constitute an RA adapted to the context in which the UE 2 is located.For example, the usage module 16C may include in the RA of the UE 2 TAs adjacent to the TA of the cell used by the UE 2 for recording (cell C1 in the example illustrated in Figure 1), or TAs which cover the same infrastructure (for example the same railway). Of course, this example is given for illustrative purposes only and is not limiting in itself.

[0105] Note that steps E40 to E60 may be implemented as described before step E70 or after.

[0106] The other steps of the UE 2 registration procedure are the same or similar to the steps described in 3GPP TS 23.502 in section 4.2.2.2.2, and are not detailed further here.

[0107] The AMF instance 4 sends the registration confirmation to the UE 2 (“Registration Accept”), including in this confirmation the RA that it has just determined (step E90).

[0108] Following its registration, the UE 2 requests the establishment of a session (“PDU Session Establishment Request”) (step E100). The AMF instance 4 via which the request passes can determine in a manner known per se the SMF instance which will manage this session (the SMF instance 5 in the example envisaged here), or use the information received during step E60 on the cell C1 to which the UE 2 is attached to identify this instance (represented in a single step E100 in FIG. 4). For example, it is possible to consider determining by learning correlations between the type of deployment of the cells and session characteristics (e.g. duration, throughput), and selecting, taking into account these correlations, the SMF instance most suited to managing the session required by the UE 2.

[0109] Upon receipt of the session establishment request, the SMF instance 5, via its sending module 16A, in turn queries the NRF device 8 to obtain information on the cell C1 to which the UE 2 is attached (step E1 10). For this purpose, as described previously for the AMF instance 4, the sending module 16A of the SMF instance 5 uses the Nnrf_NFManagement_NFDiscovery service defined in the 3GPP documents TS 23.502 and TS 29.510 adapted for the purposes of the invention. More specifically, the sending module 16A of the SMF instance 5 sends to the NRF device 8 a discovery request (message “Nnrf_NFManagement_NFDiscovery Request”) as defined by the Nnrf_NFManagement_NFDiscovery service indicating as search criterion the identity of the cell Cl used by the UE 2 to access the network.

[0110] Upon receipt of the discovery request from the SMF instance 5, the NRF device 8 consults the profiles stored in its non-volatile memory 13, identifies the profile gNBPROF(3) of the base station 3 managing the cell C1 indicated in the discovery request, and responds to the SMF instance 5 via its response module 8B using the Nnrf_NFManagement_NFDiscovery service (step E120). According to the invention, the response (message “Nnrf_NFManagement_NFDiscovery Response”) sent by the response module 8B includes all or part of the information contained in the gNBPROF(3) profile associated with the cell C1, and in particular, all or part of the INFO_CURR information relating to this cell.

[0111] The response is received by the module 16B for receiving the SMF instance 5, then the module 16C for using the SMF instance 5 uses the information received on the cell C1 to establish the session required by the UE 2 (functionality implemented by the SMF instance 5 within the meaning of the invention) (step E130). More particularly here, the module 16C for using the SMF instance 5 uses this information to optimally determine certain parameters of the session, for example the network function(s) of the user plane or UPF (for “User Plane Function” in English) which will route the data. This can be done, as described previously, by exploiting correlations established between the types of deployment of the cells and session characteristics such as in particular the throughput. Of course, this example is given only for illustrative purposes and is not limiting in itself.

[0112] The other steps in the UE 2 session establishment procedure are the same or similar to the steps described in 3GPP TS 23.502 in section 4.3.2.2.1, and are not detailed further here.

[0113] The SMF 5 instance then confirms the establishment of the session with the UE 2 (“PDU Session Establishment Accept”) (step E140).

[0114] In the above, the AMF 4 and SMF 5 devices each in turn interrogated the NRF 8 device to obtain information on current deployment conditions of the cells of the NW network and used this information to implement the functionalities assigned to them in steps E80, E100 and E130. Of course, these hypotheses are not limiting in themselves, and it can be envisaged that such information is required and used only for a reduced number of these steps (typically only one or two of these steps).

[0115] In the first embodiment described here, the Nnrf_NFManagement_NFRegister and Nnrf_NFManagement_NFDiscovery services defined by the 3GPP standard for exchanges between the NF functions and the NRF function of the core network have been preferentially used and adapted to manage the exchanges between the base station 3 and the NRF function 8 on the one hand (registration of the profile of the base station, or of the cells) and between the NRF function 8 and the NF consumer functions 4, 5 on the other hand (discovery of the information contained in the profile of the base station or of the cells). In another embodiment, it is possible to envisage proceeding differently, in particular to use messages dedicated to the invention allowing the base station 3 to register its profile (or the profile of the cells that it manages) with the NRF device 8 and the NF functions of the core network to access the information on the cells stored in this profile (or these profiles).

[0116] Furthermore, it is possible to envisage recording the profiles of the base stations of the NW network containing the information on current deployment conditions of the cells with another entity of the NW network (control device within the meaning of the invention) than the NRF device 8, for example an entity responsible for managing application entities of the AN access network (including in particular the base stations of the AN access network) and maintaining profiles for these application entities, said other entity being able to be accessible via an API or any other type of interface.

[0117] Furthermore, in the first embodiment described here, if the base station 3 detects a change in the information representative of the current deployment conditions of one or more cells that it manages, it updates, via its registration module 7A, its gNBPROF(3) profile with the NRF device 8 using the Nnrf_NFManagement_NFRegister service defined by the 3GPP standard in documents TS 23.501 and TS 29.510, adapted for the purposes of the invention to include the information representative of the updated current deployment conditions. to this update of the gNBPROF(3) profile, in the same way as is done for the information contained in the profiles of the NF functions stored by the NRF 8 device, the NRF 8 device notifies the “consumer” NF functions having subscribed to the notifications of updating the profile of the base station 3 or of the information relating to one or more cells managed by the base station 3, and provides them with the information representative of the current deployment conditions of the cells having evolved corresponding to their subscription. The same procedure is applied when cell profiles are registered with the NRF 8 device.

[0118] Figure 5 illustrates a second example of application of the invention according to the first embodiment in which the steps of the communication method are implemented by the base station 3 hosting the entity 7, the steps of the management method are implemented by the NRF device 8, and the steps of the discovery method are implemented by the NWDAF instance 6.

[0119] Following its activation by the operator OP of the cellular network NW and its start-up, the base station 3 registers its gNBPROF(3) profile with the NRF device 8, via its registration module 7A using the Nnrf_NFManagement_NFRegister service adapted for the needs of the invention (message “Nnrf_NFManagement_NFRegister Request”) (step F10). It should be noted that such registration can also take place following the modification of all or part of the information contained in the gNBPROF(3) profile.

[0120] Upon receipt of the registration request from the base station 3, the NRF device 8, via its registration module 8A, stores the profile gNBPROF(3) for example in its non-volatile memory 13 (step F20).

[0121] Then it sends via its registration module 8A a confirmation message (message "Nnrf_NFManagement_NFRegister Response") of the registration of the profile gNBPROF(3) to the base station 3 using the service Nnrf_NFManagement_NFRegister, in a similar or identical manner to what it does when registering the profile of an NF function (step F30).

[0122] It is now assumed that the UE 2 registers with the core network CN via the base station 3 (step F40). In a manner known per se, the registration request of the UE 2 (“Registration Request”) is transmitted to the AMF instance 4 to which this UE is attached.

[0123] Steps F10, F20, F30 and F40 are identical respectively to steps E10, E20, E30 and E70 described previously with reference to figure 4, and are not repeated in detail here.

[0124] In the second embodiment described here, it is assumed that upon receipt of the registration request from the UE 2, the AMF instance 4 requests from the NWDAF instance 6 predictions / statistics and more particularly predictions on the mobility of the UE 2 (message "Nnwdaf_AnalyticsInfo Request") (step F50). For this purpose, in the first embodiment described here, it uses the Nnwdaf_AnalyticsInfo service described in the documents 3GPP TS 23.288 entitled "Architecture Enhancements for 5G system (5GS) to support network data analytics services (Release 17)", V17.4.0, March 2022, and TS 28.520 entitled "Technical Specification Group Core Network and Terminals; 5G System; Network Data Analytics Services; Stage 3; (Release 17)", V17.6.0, March 2022.Note that this request can be made in the form of a simple “Nnwdaf_AnalyticsInfo Request” as described here, or alternatively in the form of a subscription using the Nnwdaf_Analytics Subscription service as described in the previously cited TS 23.288 and TS 29.520 documents.

[0125] Upon receipt of the forecast request from the AMF instance 4, the NWDAF instance 6 collects the INPUT_DATA data necessary for calculating the requested forecasts, as described in the document TS 23.288 in paragraph 6.7.2.4. In addition, the NWDAF instance 6 queries, via its sending module 16A, the NRF device 8 to obtain information on the cell of the NW network used by the UE 2. The identifier of the cell used by the UE 2 (Cl in the example considered here) can be obtained by the NWDAF instance 6 for example from the INPUT_DATA data that it has collected.

[0126] To query the NRF device 8, the sending module 16A of the NWDAF instance 6 sends a discovery request (message “Nnrf_NFManagement_NFDiscovery Request”) to the NRF device 8 (step F60), in a similar or identical manner to what was previously described in step E110 for the SMF instance 5 with reference to figure 4. More specifically, the discovery request as defined by the Nnrf_NFManagement_NFDiscovery service indicates in the present case as search criterion the identity of the cell Cl used by the UE 2 to access the network.

[0127] Upon receipt of the discovery request from the NWDAF instance 6, the NRF device 8 consults the profiles stored in its non-volatile memory 13, identifies the gNBPROF(3) profile of the base station 3 managing the cell C1 indicated in the discovery request, and responds to the NWDAF instance 6 via its response module 8B using the Nnrf_NFManagement_NFDiscovery service (step F70). According to the invention, the response (message “Nnrf_NFManagement_NFDiscovery Response”) sent by the response module 8B comprises all or part of the information contained in the gNBPROF(3) profile associated with the cell C1, and in particular, all or part of the INFO_CURR information relating to this cell.

[0128] The response from the NRF device 8 is received by the reception module 16B of the NWDAF instance 6. The NWDAF instance 6, via its usage module 16C, then establishes the forecasts requested by the AMF instance 4 (functionality implemented by the NWDAF instance 6 within the meaning of the invention), using on the one hand the collected INPUT_DATA data, but also here all or part of the information received from the NRF device 8 on the cell C1, and in particular all or part of the INFO_CURR information on current deployment conditions of the cell C1 received from the NRF device 8 (step F80). For example, the forecasts of the NWDAF instance 6 may be influenced by the type of deployment of the cell C1 and in particular the fact that it is deployed in support of a given infrastructure such as a highway: the future positions of the UE 2 located on this highway will then have a higher probability.Of course, this example is given for illustrative purposes only and is not limiting in itself.

[0129] It should be noted that the steps F60 to F80 just described may be repeated and / or executed at other times. For example, the NWDAF instance 6 may observe the movement of the UE 2 for a certain period and query the NRF device 8 for each of the cells visited by the UE 2 in order to obtain more reliable predictions. This is possible in particular when the device requesting the predictions / statistics from the NWDAF instance 6 does not need an immediate response from the latter.

[0130] The module 16C for using the NWDAF instance 6 transmits the forecasts thus established to the AMF instance 4 (message “Nnwdaf_AnalyticsInfo Response”) (step F90), which uses them to establish the RA of the UE 2 in a manner known to those skilled in the art and not described in detail here (step F100). For example, the RA may contain all the TAs containing the future positions of the UE 2 predicted by the NWDAF instance 6. Of course, this example is given only for illustrative purposes and is not limiting in itself.

[0131] The other steps of the UE 2 registration procedure are the same or similar to the steps described in 3GPP TS 23.502 in section 4.2.2.2.2, and are not detailed further here.

[0132] The AMF instance 4 sends the registration confirmation to the UE 2 (“Registration Accept”), including in this confirmation the RA that it has just determined (step F110).

[0133] Following its registration, the UE 2 requests the establishment of a session (“PDU Session Establishment Request”) (step F120). The AMF instance 4 via which the request passes can select the SMF instance 5 which will manage this session in a conventional manner, as provided for by the 3GPP standard, possibly using the predictions received during step F90 to select the SMF instance 5.

[0134] Upon receipt of the session establishment request, the SMF instance 5 requests the NWDAF instance 6 for predictions / statistics on the UE 2, such as predictions on the communi- communications of UE 2 (message "Nnwdaf_AnalyticsInfo Request") (step F130). As previously described for the AMF instance 4 in step F50, the SMF instance 5 uses for this purpose, in the first embodiment described here, the Nnwdaf_AnalyticsInfo service described in the 3GPP documents TS 23.288 and TS 28.520. Steps F60 and F70 can be repeated if necessary by the NWDAF instance 6 (not shown in FIG. 5). This may be the case in particular when the NWDAF instance 6 is requested to produce predictions / statistics of different types, such as here, by the AMF instance 4 to establish forecasts on the mobility of the UE 2 and by the SMF instance 5 to establish forecasts on the communications of the UE 2, the discovery requests addressed to the NRF device 8 then being able to relate to different search criteria.

[0135] The NWDAF instance 6, via its usage module 16C, then establishes the forecasts requested by the SMF instance 5 (functionality implemented by the NWDAF instance 6 within the meaning of the invention) using on the one hand the INPUT_DATA data that it has collected, but also all or part of the information provided by the NRF device 8 on the cell Cl used by the UE 2 to access the network, and in particular all or part of the INFO_CURR information on current deployment conditions of the cell Cl (step F140).

[0136] The module 16C for using the NWDAF instance 6 transmits the forecasts thus established to the SMF instance 5 (message “Nnwdaf_AnalyticsInfo Response”) (step F150), which uses them to establish the session required by the UE 2 (step F160). For example, the module 16C for using the SMF instance 5 uses these forecasts to optimally determine certain parameters of the session, such as the network function(s) of the user plane or UPF (for “User Plane Function” in English) which will route the data. For example, depending on the flow rates of the communications of the UE 2 provided by the NWDAF instance 6, the SMF instance 5 can select a UPF function optimized to process a high flow rate or, on the contrary, sporadic communications. Of course, this example is given only for illustrative purposes and is not limiting in itself.

[0137] The SMF 5 instance then confirms the establishment of the session with the UE 2 (“PDU Session Establishment Accept”) (step F170).

[0138] It should be noted that the remarks made previously regarding the possibility of using other messages than those defined by the Nnrf_NFManagement_NFRegister and Nnrf_NFManagement_NFDiscovery services of the 3GPP standard, of updating certain information of the profile of the base station 3 or of the cells of the NW network, of querying and exploiting the information of current deployment conditions of the cells only during certain stages, and of considering another control device than the NRF device 8 (for example a control device managing application entities of the access network AN such as the base stations) also apply in the context of this second illustrative example.

[0139] Furthermore, the two illustrative examples which have just been presented are not limiting in themselves, and the invention can be applied in other contexts, and involve other application entities of the core network CN (for example other network functions) and / or of the access network AN (for example other base stations). In particular, it is possible to envisage as another requesting device, a base station of the network AN which uses the information of current deployment conditions of the cells of the network NW to decide on a transfer or “handover” between two cells for a UE attached to this base station, and to determine the modalities of this handover (in particular the target cell). For example, if it is determined that a UE is moving on a railway track (e.g.via the predictions made by a network function NWDAF), the base station could, thanks to the INFO_CURR information obtained from the NRF 8 device, select among the candidate neighbor cells (which are configured at the base station), only those that cover the railway in question on which the UE is moving, as potential targets for the UE handover. It should be noted that the APIs currently defined by the 3GPP standard do not allow a gNB base station to interrogate an NRF device; therefore, this would need to be adapted. API (which would not pose any difficulty to the person skilled in the art) or to provide an interface allowing the base station to query the NRF device to obtain the INFO_CURR information that interests it.

[0140] In the first embodiment which has just been described, the base station 3 hosts the entity 7, and itself registers with the NRF device 8 its profile gNBPROF(3) or the profile CelIPROF of the cells C1, C2 and C3 which it manages. What has just been described with reference to the base station 3 is implemented by all or some of the base stations of the NW network.

[0141] We will now consider with reference to Figure 6 a second embodiment of the invention in which the entity 7 is hosted in an application entity of the core network CN and more precisely in a device hosting a network function, namely an AMF instance (network access management device within the meaning of the invention). The same references as those used in Figures 1 to 3 are used for the elements which are identical to the first embodiment and for which the characteristics detailed in the first embodiment apply in the second embodiment.

[0142] Thus, Figure 6 represents a system 1 in a cellular communication NW network, according to the second embodiment of the invention. The NW network is, as previously described with reference to the first embodiment, a 5G network as defined by the 3GPP standard, managed by an operator OP, and comprising at least one access network AN and a core network CN.

[0143] To access the services offered by the NW network, the UE 2 connects to the core network CN via the access network AN, and more particularly a gNB base station 3' of this access network. The gNB base station 3' is configured to manage one or more cells of the NW network; in the example envisaged here, the base station 3' is a tri-sector gNB managing three cells of the network C1, C2 and C3.

[0144] The CN core network is based on several network functions as described previously for the first embodiment, and in particular on instances 4' of AMF network function, 5 of SMF network function and 6 of NWDAF network function.

[0145] In accordance with the invention, the system 1' comprises: at least one base station gNB managing at least one cell of the NW network, in accordance with the invention, namely the base station 3' managing the cells C1, C2 and C3 of the NW network; at least one requesting device, in accordance with the invention, namely in the example illustrated in FIG. 6, the NWDAF instance 6. Of course, this example is given only for illustrative purposes, and other entities of the NW network, in particular other network functions or instances of network functions of the core network CN may be requesting devices within the meaning of the invention; at least one entity 7 of the NW network in accordance with the invention. In the second embodiment, the entity 7 is hosted by the AMF instance 4' (access management device within the meaning of the invention); and a device 8 for controlling the NW network, in accordance with the invention, as described in the first embodiment of the invention.

[0146] Figure 7 represents the distribution in the different elements of the system 1' of the functional modules 8A-8B, 7A, and 16A to 16C defined respectively by the programs PROG1, PROG2 and PROG3, described previously for the first embodiment. The characteristics of these modules remain the same for the second embodiment except that the entity 7 (and therefore the recording module 7A) is now hosted in a network function instance of the core network CN, namely in the AMF instance 4'. It should be noted that the AMF instance 4' can also be a requesting device within the meaning of the invention in the second embodiment and host modules 16A-16C (not shown, however, in Figure 7).

[0147] We will now describe, with reference to figure 8 which illustrates an example of application of the invention in the second embodiment, the main steps of the communication, management and discovery methods implemented respectively by the AMF instance 4' hosting the entity 7, by the NRF device 8, and by the NWDAF instance 6. It should be noted that the second embodiment is particularly well suited when the base station 3' does not support the protocol(s) making it possible to consume the services of the AMF instance 4' or of the NRF device 8 (HTTP2 protocol in particular in the example of a 5G network defined by the 3GPP standard).

[0148] Following its activation by the operator OP of the cellular network NW, the base station 3' triggers an association procedure with the AMF instance 4' designated to manage the base station 3' (step G10). For this purpose, in the second embodiment described here, the base station 3' executes the "NG Setup" procedure described in the document 3GPP TS 38.413 entitled "Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP); (Release 17)", V17.0.0, April 2022, in paragraph 8.7.1. However, in accordance with the invention, during this procedure, the base station 3' enriches the association message ("NG SETUP Request" message) sent to the AMF instance 4' with its gNBPROF(3') profile.As described in the first embodiment of the invention, the profile gNBPROF(3') contains for each cell C1, C2, C3 managed by the base station 3', information INFO_CURR representative of the current deployment conditions of these cells, and possibly additional information INFO_SUPP and INFO_gNB relating to the base station 3'. The information INFO_CURR, INFO_SUPP and INFO_gNB considered in the second embodiment is identical to that considered in the first embodiment and is not described again in detail here. The same applies to the way in which the base station 3' obtains this information (operator configuration, evaluation by it, or obtaining from third-party entities such as a radio planning system adapted to the NW network).

[0149] Furthermore, as in the first embodiment, it can be envisaged that instead of transmitting its gNBPROF(3') profile to the AMF instance 4', the base station 3' transmits a CelIPROF profile for each of the cells C1, C2 and C3 that it manages.

[0150] The AMF instance 4' extracts the profile gNBPROF(3') transmitted by the base station 3' and stores it for example in its non-volatile memory 13. It finalizes the association procedure with the base station 3' as described in document 38.413 (step G20 and message "NG SETUP Response").

[0151] Following receipt of the gNBPROF(3') profile from the base station 3', the AMF instance 4', via its registration module 7A, registers the gNBPROF(3') profile with the NRF device 8 (step G30).

[0152] For this purpose, in the second embodiment described here, the registration module 7A of the AMF instance 4' uses the Nnrf_NFManagement_NFRegister service defined in the 3GPP TS 23.502 and TS 29.510 documents cited above, adapted for the purposes of the invention. More specifically, the registration request of the Nnrf_NFManagement_NFRegister service (message "Nnrf_NFManagement_NFRegister Request"), usually used by the NF functions of the CN core network to register their respective NFPROF profiles with the NRF device 8, is adapted to be used by the AMF instance 4' (and more particularly by the registration module 7A of the entity 7 hosted by the AMF instance 4') to register the gNBPROF(3') profile of the base station 3'.The request "Nnrf_NFManagement_NFRegister Request" is therefore modified to, although being sent by the AMF instance 4', contain the profile gNBPROF(3') of the base station 3' which includes, for each cell C1, C2 and C3 managed by the base station 3', the information INFO_CURR, and where appropriate the information INFO_SUPP and INFO_gNB. Such an adaptation would not pose any difficulty to the person skilled in the art and is not described further here.

[0153] Upon receipt of the registration request from the AMF instance 4', the NRF device 8, via its registration module 8A, stores the profile gNBPROF(3'), for example in its non-volatile memory 13 (step G40). Thus, at the end of this step, the NRF device 8 has in its non-volatile memory 13 not only the profiles of the NF functions of the core network CN, but also the profile of the base station 3' (as well as other base stations of the network NW, the profiles of these other stations basic having been recorded by the AMF 4' instance if they are attached to this instance or by other AMF instances of the core network having proceeded in a similar or identical manner).

[0154] The NRF device 8 then sends via its registration module 8A a confirmation message (message “Nnrf_NFManagement_NFRegister Response”) of the registration of the profile gNBPROF(3') of the base station 3' to the AMF instance 4', using the service Nnrf_NFManagement_NFRegister, in a similar or identical manner to what it does when registering the profile of an NF function (step G50).

[0155] It is now assumed that the UE 2 registers with the core network CN via the base station 3', and more particularly with the AMF instance 4' (step G60). Step G60, then the series of steps G70 to G190 which follow, are identical respectively to steps F40 then F50 to F170 described with reference to FIG. 5 and are not detailed again here.

[0156] It should be noted that the remarks made previously regarding the possibility of using messages other than those defined by the Nnrf_NFManagement_NFRegister and Nnrf_NFManagement_NFDiscovery services of the 3GPP standard or of updating certain information of the profile of the base station 3 or of the cells of the NW network also apply in the context of this second embodiment. Furthermore, the illustrative example which has just been presented is not limiting in itself, and the invention can be applied in other contexts, and involve other application entities of the CN core network (for example other network functions). Furthermore, what has just been described with reference to the gNBPROF(3') profile of the base station can be applied to the CelIPROF profile of each cell managed by the base station 3'.

[0157] In both embodiments described, the NW network is a 5G network as defined by the 3GPP standard. However, as mentioned above, the invention is not limited to this context and can be applied to other networks, for example to a 6G network or to a proprietary network.

Claims

Claims

1. Method of communicating with a control device (2) of a cellular communication network (NW), configured to manage application entities (4, 4', 5, 6) of the network offering services in the network and maintain a profile of these application entities, the method comprising a step (E10, F10, G30) of recording a profile with the control device, this profile comprising information (INFO_CURR) representative of current deployment conditions of at least one cell of the network managed by a base station of the network.

2. A communication method according to claim 1 wherein said profile is a profile (gNBPROF(3),gNBPROF(3')) of the base station or a profile of said at least one cell.

3. A communication method according to claim 1 or 2, implemented by said base station (3), and further comprising a step of evaluating at least part of said information before recording it with the control device.

4. Communication method according to any one of claims 1 to 3, implemented by said base station (3), and further comprising a step of obtaining, from a radio planning system (15) adapted to the network, at least part of said information before recording it with the control device.

5. Communication method according to claim 1 or 2, implemented by a device (4') for managing access to the cellular network, and comprising a step (G 10) of obtaining at least part of said information from the base station during an association of said base station with said access management device.

6. Method of management by a control device (8) of a cellular communication network, configured to manage application entities of the network offering services in the network and maintain a profile of these application entities, said method comprising: - a step (E10, F10, G50) of recording a profile provided by an entity of the cellular network and comprising information representative of current deployment conditions of at least one cell of the cellular network managed by a base station of the network; and - in response to a discovery request received from a so-called requesting device of the network, a step (E50, E120, F70, G90) of transmitting all or part of said profile to said requesting device.

7. Management method according to claim 6 wherein said profile is provided to the control device (8) by said base station (3) or by a device (4') for managing access to the cellular network.

8. A management method according to claim 6 or 7 further comprising: - a step of updating at least one of said information in said profile; and - a step of notifying said at least one updated piece of information to said requesting device.

9. Method according to any one of claims 1 to 8 in which at least one said information (INFO_CURR) representative of current deployment conditions relates to a layout of the cell in a network architecture, to a geographical environment of the cell, to a configuration of at least one antenna of the cell, to a type of deployment of the cell, to at least one infrastructure covered by the cell, and / or to a state of the cell.

10. A method according to any one of claims 1 to 9 wherein said profile further comprises: - a cell identity; and / or - a frequency band allocated to the cell; and / or - at least one radio access technology associated with the cell.

11. Method for discovery by a so-called requesting device (4,5,6) of a cellular communication network, said method comprising: - a step (E40, E110, F60, G80) of sending a discovery request to a network control device configured to manage application entities of the network offering services in the network and maintaining a profile of these application entities, said discovery request relating to at least one cell managed by a base station of the cellular network; - a step (E50, E120, F70, G90) of receiving a response to said discovery request comprising information representative of current deployment conditions of said at least one cell stored in a profile maintained by the control device; and - a step (E60, E130, F80, G100) of using all or part of said information received during the provision of a functionality implemented by the requesting device in the network.

12. Entity (7) of a cellular communication network comprising a registration module (7A) configured to register a profile with a network control device managing application entities of the network offering services in the network and maintaining a profile of these application entities, said profile recorded by the registration module comprising information representative of current deployment conditions of at least one cell of the network managed by a base station of the network.

13. Base station (3) of a cellular communication network hosting an entity (7) according to claim 12, said information relating to at least one cell of the network managed by said base station.

14. Device (4') for managing access to a cellular communication network hosting an entity (7) according to claim 12.

15. Device (8) for controlling a cellular communication network configured to manage application entities of the network offering services in the network and maintain a profile of these application entities, said control device comprising: - a recording module (8A), configured to record a profile provided by an entity of the cellular network, said profile comprising information representative of current deployment conditions of at least one cell of the cellular network managed by a base station of the network; and - a response module (8B), configured to transmit in response to a discovery request received from a so-called requesting device of the network, all or part of said profile to said requesting device.

16. Device (4,5,6) said to be requesting a cellular communication network comprising: - a sending module (16A) configured to send a discovery request to a network control device managing application entities of the network offering services in the network and maintaining a profile of these application entities, said discovery request relating to at least one cell managed by a base station of the cellular network; - a receiving module (16B), configured to receive a response to said discovery request comprising information representative of current deployment conditions of said at least one cell stored in a profile maintained by the control device; and - a usage module (16C), configured to use all or part of said information received when providing a functionality implemented by the requesting device in the network.

17. System (1,1') in a cellular communication network comprising: - at least one base station (3,3') managing at least one cell of the network; - at least one entity (7) of the network according to claim 12; and - a control device (8) according to claim 15; and - at least one requesting device (4,5,6) according to claim 16.

Images