GB2622768A

GB2622768A - A system for handling data within a mobile data network

Info

Publication number: GB2622768A
Application number: GB2211957.2A
Authority: GB
Inventors: Offei Nyanteh Andrews
Original assignee: Awtg Ltd
Current assignee: Awtg Ltd
Priority date: 2022-08-16
Filing date: 2022-08-16
Publication date: 2024-04-03
Also published as: GB202211957D0; WO2024037989A1

Abstract

A system comprising a core network, such as a 5G core network, in a cloud and a multiplicity of cell sites, at least one of the multiplicity of cell sites having an edge computer (MEC) nearby, the core network provided with a multiplicity of network functions (NFs), at least one of the NFs packaged as a virtual network function (VNF) or a containerised cloud-native network function (CNF), clones or provisions an existing VNF or CNF on to said MEC. If one or more licences are in use at the target NF, the target NF may be cloned; if all the licences of the target NF are available, it may be provisioned. An AI algorithm may assess if the current licences of an existing NF at the MEC are sufficient and determines whether a further NF should be provisioned to ensure capacity to meet expected demand. Each licence may be sufficient for a single UE request such as a handshake or handover. The network function may preferably be an AMF or UPF. The system monitors the number of incoming requests from UEs and alerts the core network when that number reaches a threshold.

Description

A SYSTEM FOR HANDLING DATA WITHIN A MOBILE DATA NETWORK The present invention relates to a system for handling data within a mobile data network; and to a system for enhancing a user experience in a mobile data network.

The internet has become a vital part of life for everyone. Users expect an ever-improving level of service, requiring a consistent, high-speed service with no drop out in connection. Service level provided by a wired service, such as ADSL, DSL across copper wire and optical fibre provide a fast consistent service, generally with a high bandwidth, low latency, low levels of drop-out and few contention ratio issues. Users now require a mobile service to be just as stable.

The architecture of networks to provide connection for mobile devices is evolving rapidly. 5G is the latest main currently used standard for mobile data networks. The 5G standard has built upon previous standards, such as 4G and 3G, from which Service Based Architectures (SBA) has emerged, which enables Communications Service Providers (CSPs) and Mobile Network Operators (MN05) to automate their business processes, operations, and services. Digitalization and automation of CSPs/MNOs operating models continues to evolve services as they aim to provide dynamic self-service networks which have the capability to self-configure services and to scale network resources up and down as needed on the fly by harnessing the potential of 5G; yet telecom networks traditionally are designed to manage traffic and congestion at peak times.

Demand for specific uses from users varies considerably throughout the day, week and months, depending on a number of factors. For example, a weekend festival may place an usually high demand on a particular part of -2-the network, such as a single or handful of cell sites, for one weekend in a year. Demand for mobile data in a holiday destination may increase dramatically over a two-month period in summer. A national celebration may place a large strain on a part of a network, such as a single or handful of cell sites, in the centre of a city around significant national monuments for a few hours. The demand may be for data related services or for voice calls. Voice calls are increasingly being made over Voice Over VOIP systems, although voice calls remain popular. It is not just users demand for stable connection, but any internet connected equipment which the users bring with them, such as an internet connected car which may require specific requirements such as updating engine management software, notifying location and uploading other parameters of the car. Furthermore, any IoT device which the user has brought with them, which requires Internet connection at times without the user being aware. These examples may cause network traffic congestions due to the network subscribers, resources and application demand particularly, but not exclusively, when initiating a service or request, sometimes referred to as handshaking and also with handover.

Amongst others, in the 5G standard, the entire network is split up into clouds, both private and public. Each cloud has a core network paid for and maintained by an operator. The core network, such as a 5G Core (5GC) has a number of network functions each provided with a fixed number of licences. A typical core network may cost an operator $50,000 per year and may service up to 100,000 users. A number of network functions are required to authenticate a user to ensure the user is fully paid up and able to access the network through the operator. This is generally referred to as handshaking to authenticate subscribers and user equipment: a PDU establishment. The above described localised areas of high demand 5 need to be managed to make full use of their potential of limited local resources to meet the users' expectations. In accordance with the present invention, there is provided a system for handling data in a mobile data network, the system comprising a core network in a cloud and a multiplicity of cell sites, at least one of the multiplicity of cell sites having an edge computer nearby, the core network provided with a multiplicity of Network Functions, at least one of the Network Functions packaged as a Virtual Network Function (VNF) or a Cloud-native Network Function (CNF), and wherein said at least one of the Network Functions packaged as a Virtual Network Function (VNF) or a Cloud-native Network Function (CNF) is provided with a number of licences characterised in that if one or more licences is in use, and said at least one of said Network Functions packaged as a Virtual Network Function or Cloud-native Network Function (CNF) is desired on said edge computer, said at least one of said Network Functions packaged as a Virtual Network Function or Cloud-native Network Function (CNF) is cloned on to said edge computer.

Optionally or alternatively, if no licences are in use, and said at least one of said Network Functions packaged as a Virtual Network Function or Cloud-native Network Function (CNF) is desired on said edge computer, said at least one of said Network Functions packaged as a Virtual Network Function or Cloud-native Network Function (CNF) is provisioned on to said edge computer. -4 -

Each licence may be sufficient for a single User Equipment request, such as a handshake or handover within air-communication range of the cell site. The mobile data network may be a 5G network.

Optionally, the Network Function is at least one of: AMP, SMF, UPF, NRF, UDM, PCF, AUSF, AF, NEF.

The edge computer is generally either within the cell site, at the foot of a mast of a cell site, within a control box or control room of the cell site, within an integrated antenna or within a short direct distance of the cell site such as 10km, preferably within lkm and most preferably within 250m. The edge computer may be hard wired to the transmitter-receiver unit on the cell site or may use a wireless connection.

The present invention also provides a system for handling data in a mobile data network, the system comprising a core network in a cloud and a multiplicity of cell sites, at least one of the multiplicity of cell sites having an edge computer nearby, the core network provided with a multiplicity of Network Functions, at least one Network Function having a determined number of licences on said edge computer, at least one of the Network Functions packaged as a Virtual Network Function (VNF) or a Cloud-native Network Function (CNF), characterised in that a computer program is executed having instructions that when executed monitors the number of incoming requests (nIR) from User Equipment, each incoming-request expected to utilise at least one licence of said determined number of licences, the computer program having a threshold number, upon said threshold number being reached, the computer program sending an alert to the core network.

There are many types of Network Functions and many of -5-then can be VNF or CNFs, such as User Plane Function (UPF) and Access and Mobility Management function (AMF) network functions. There may be multiple numbers of each type of network function within each core network within the cloud, each provided with a set number of licences. For example, there may be ten AMFs available in each core network, each of which is provided with twenty licences. Each of network function may be located in the core network, and each may have some or all their licences available. As another example, there may be twenty UPFs available in each core network, each of which is provided with twenty licences.

Optionally, the alert comprises the step of finding another Network Function of the same type, and thus may not know the number of licences available. Optionally, the alert comprises the step of finding another Network Function of the same type having at least one available licence. Optionally, the alert comprises the step of finding another Network Function of the same type having all its licences available. Optionally, the alert comprises the step of requesting another network function, such as an NRF, which may be in the core network, for a location of the same type of Network Function. Optionally, the system further comprises the step of checking the Network Function for availability to provision on to the edge computer. Optionally, the system further comprises the step of not checking the Network Function for availability to provision on to the edge computer, simply trying and if the located network function can not be provisioned, defaulting to cloning the located network function.

Optionally, the computer program comprises the further step of provisioning the located network function from the core network to the edge computer. Optionally, the step of -6-provisioning occurs upon meeting a second threshold. Optionally, if the check reveals the Network Function is not able to be provisioned because there is at least one licence in use, the Network Function is cloned to the edge computer.

Optionally, the alert comprises the step of finding a determined number of network functions of the same type. If the computer program knows or is told by a register, such as the NRF, that all network functions of this type are provided with a fixed number of licences, say twenty licences, then the computer program will determine the number of network functions to provision and/or clone to the edge computer.

Optionally, the threshold is a fixed pre-determined number. Optionally, the second threshold is a fixed pre-determined number. Optionally, the threshold and/or second threshold is related to the number of determined number of licences of the Network Function on said edge computer. Optionally, the threshold and/or second threshold is dynamic. Optionally, the threshold is determined by an Al algorithm.

Optionally, the computer program is executed on a processor located within the cell site. Optionally, the computer program is executed on a processor located within the edge computer.

Optionally, the computer program comprises an algorithm to remove the cloned network functions from the edge computer upon the number of incoming requests (nIR) falling below a threshold. Optionally, the computer program comprises an algorithm to move a provisioned network function from the edge computer to a different location upon the number of incoming requests (nIR) falling below a -7-threshold. The different location may be to a different edge computer or to a location on in the core network. The different location may be provided by a register network function, interrogated or requested by the algorithm.

The present invention also provides a system for enhancing a user experience in a mobile data network, the system comprising a core network in a cloud and a multiplicity of cell sites, at least one of the multiplicity of cell sites having an edge computer nearby, the core network provided with a multiplicity of Network Functions, at least one Network Function having a determined number of licences on said edge computer, at least one of the Network Functions packaged as a Virtual Network Function (VNF) or a CNF, characterised in that a computer program is executed having instructions to apply an Al algorithm to assess if a further Network Function should be provisioned or cloned to the edge computer to ensure capacity to meet expected demand.

The present invention also provides a system for enhancing a user experience in a mobile data network, the system comprising a core network in a cloud and a multiplicity of cell sites, at least one of the multiplicity of cell sites having an edge computer nearby, the core network provided with a multiplicity of Network Functions, at least one of the Network Functions packaged as a Virtual Network Function (VNF) or a CNF, characterised in that the Network Function packaged as a Virtual Network Function or Cloud-native Network Function (CNF) is cloned to on to said edge computer. -8-

For a better understanding of the present invention, reference will now be made, by way of example, to the accompanying drawings, in which: Figure 1 is a schematic view showing a typical architecture of at least a part of a known 5G network; Figure 2 is a schematic view of a system of the present invention showing steps in a method of handling data within the network; Figure 3 is a schematic view of a computer system on 10 which a computer program of the present invention is stored and executed; Figure 4 is a first flow diagram of the computer program of the invention showing how the steps shown in Figure 2 are actioned; Figure 4A is a second flow diagram of the computer program of the system of the invention; Figure 5 is a schematic view of the system shown in Figure 2 showing further steps in a method of handling data within the network; Figure 6 is a schematic view of the system shown in Figure 5 showing yet further steps in a method of handling data within the network; and Figure 7 is a schematic view of the system shown in Figure 6 showing yet further step in a method of handling data within the network.

Referring to Figure 1 there is shown a typical architecture of at least a part of a known 5G network, generally identified by reference numeral 1. The network 1 comprises a core network 2 in cloud 3, proving data transfer to a plurality of cell sites distributed over a vast geographical area forming a Radio Access Network (RAN) (only one cell site 4 shown). The cell site 4 provides two- -9-way wireless communication with User Equipment WE) 5 in a particular location. Cell site 4 comprises a lattice tower 6, a transceiver 7 mounted on the lattice tower 6 and an antenna 8 connected to the transceiver 7. The transceiver 7 and antenna 8 may be integrated into one unit and may alternatively be mounted on a pole, on a building or to any other suitable structure (not shown). The transceiver 7 may be a gNB (Next Generation NodeB) suitable for handling 5G data. The transceiver 7 is typically hard wired to a computer forming part of the cloud 3 or linked by a further transceiver (not shown) to a further cell site (not shown) forming part of the cloud 3.

5G can be implemented in low-band, mid-band or high-band. Low-band 5G uses a similar frequency range to 4G of 600-900MHz, giving download data speed transfer of 30 to 250Mbit/s. Low-band cell sites have a range and coverage area similar to 4G cell sites. Mid-band 5G uses microwaves of 1.7 to 4.7GHz, allowing speeds of 100-900 Mbit/s, with each cell site providing service up to several kilometres in radius. Although rolling hills and foliage may absorb the signals and thus reduce the service area, which is of a particular note with high-band signals. High-band uses millimetre-wave 24GHz up to 54GHz. Buildings tend to reflect high band signals.

In 5G, "air latency" i.e. the time it takes for data to get from the cell site 4 to the user equipment 5 is of the order of 8 to 12 milliseconds. The latency from the cell site 4 to a server in the core network 2 must be added to the "air latency". The latency to the server in the core network 2 may be a further 30ms. Multi-access Edge Servers (MEC) close to the cell site 4 can reduce latency to 10 to 20ms. The latency is much higher during handshakes and -10-handovers; ranging from 50 to 500 milliseconds depending on the type of handshake or handover. Reducing handshake and handover latency is an ongoing area of research and development. Network traffic congestion in core network 2 is reduced by caching content at the network edge.

A Service Based Architecture (SBA) provides a framework for providing various Network Functions (NFs) in the Core Network 2. Network Functions include: Access and Mobility Management function (AMF) 10: termination of Non-Access Stratum (NAS) signalling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management.

Session Management function (SMF) 11: session management (session establishment, modification, release), User Equipment IP address allocation & management, DHCP functions, termination of NAS signalling related to session management, DL data notification, traffic steering configuration for User Plane Function (UPF) for proper traffic routing.

User Plane Function (UPF) 12: packet routing & forwarding, packet inspection, QoS handling, acts as external PDU session point of interconnect to Data Network (DN) 20, and is an anchor point for intra-& inter-RAT mobility. As in any handover case, there is a source cell in the RAN and a target cell in the RAN (within the same radio access in the case of Intra-RAT and in a different RAN in the case of Inter-RAT handover).

Policy Control Function (PCF) 13: unified policy framework, providing policy rules to CP functions, access subscription information for policy decisions in UDR. -11-

Unified Data Management (UDM) 14: generation of Authentication and Key Agreement (AKA) credentials, user identification handling, access authorization, subscription management.

Authentication Server Function (AUSF) 15 acts as an authentication server.

Application Function (Al') 16: application influence on traffic routing, accessing NEF, interaction with policy framework for policy control.

Network Exposure function (NEF) 17: exposure of capabilities and events, secure provision of information from external application to 3GPP network, translation of internal/external information.

NF Repository function (NRF) 18: service discovery function, maintains NF profile and available NF instances.

Network Slice Selection Function (NSSF) 19: selecting of the Network Slice instances to serve the UE, determining the allowed Network Slice Selection Assistance Information (NSSAI), determining the AMP set to be used to serve the 20 UE.

When a User Equipment 5 sends a PDU session establishment request message, the message transits from the User Equipment 5 to the transceiver 7 and on to the AMP 10 in the cloud 3. This message contains a DNN and 5-NSSAI. The AMP 10 queries the NRF 18 for an available SMF 11. The query request contains the DNN, type of the requester NF, requested Public Land Mobile Network (PLMN), target Network File System (NFS) name, S-NSSAI, target NF type and additional information. If all the SMFs registered on the NRF support, the NSMF PDU Session Service, the NRF selects an available SMF 11 based on the DNN and S-NSSAI in the request and returns the SMF IP address and endpoint -12-information about the NSMF PDU Session Service to the AMF 10. The AMF 10 then invokes the NSMF PDU Session Service of the SMF 11 to establish a PDU Session. The SMF 11 initiates an N4 session establishment procedure towards the selected UPF. The SMF 11 notifies the AMF 10 of the N2 session management information and the Ni session management information. The AMF 10 sends an N2 PDU Session Request to the (Radio) Access Network ((R)AN) to request the (R)AN to allocate an N3 tunnel access network address and radio resources. The (R)AN forwards the PDU Session establishment response to the User Equipment 5. The PDU Session is established.

Referring to Figure 2, there is shown a system in accordance with the present invention, generally identified by reference numeral 100. The system 100 is generally referred to herein as NFOps (Network Functions Operations) and generally describes Autonomous Network Functions Operations. The inventor observed that a number of Network Functions are highly mobile. Similar features to those shown in Figure 1 are identified with the same reference numbers in the one-hundred series. The system 100 comprises a core network 102 comprising various Network Functions, such as AMF 110, SNP 111, UPF 112, NRF 118, UDM 114 and may further comprise a number of other Network Functions, such as PCF, AUSF, AF, NEF (not shown). The operator pays a yearly amount for the core network 102. Each Network Function is supplied with a set number of licences. For instance, there are four AMFs 110,110a,110b,110c in the core network 102, each having twenty licences. As mentioned above, a Multi-access Edge Server (MEC) 130, 130', 130" is physically located near each of the cell sites 104, 104' 104". Each MEC 130, 130', -13- 130" can be provisioned with Network Functions to reduce the distance data flows travel in handling a request from UEs, reducing or potentially eliminating the number data flows all of the way into the core network 2. By reducing the physical distance the request has to travel, latency is improved, improving the user experience. As shown, an AMF 100x,110y,110z each having five licences are provisioned on respective MEC 130, 130' 130". When demand at one cell site 104' is five UEs or less, the system works well, with all UEs able to take advantage of the short distance from UE to access the AMF 110y on the MEC 130'. However, when demand exceeds five UEs, the large number of UEs have to fight for the five AMF licences available on the MEC 130'. An unsuccessful PDU establishment may result in a handshake or handover between source and target MECs.

The inventor has observed that it would be ideal to have all of the Network Functions on the MEC 130, 131, 132 to reduce latency and improve the user experience, so that all demand, even from a large number of UEs would be serviced. However, this requires all Network Functions to sit in the MEC 130, 130', 130" each having sufficient licences available to service all UEs placing requests, which would be expensive and impractical; indeed some of the Network Functions have to remain in the core 2.

Accordingly, a Network Function provisioned on MEC 130 may have five licences, thus at any one time, the cell site 104 could only service five requests from UEs. Such requests may be handshakes or handovers. If, for example, a festival is taking place that weekend located in range of cell site 104, requests from say 20 UEs at any one time may be made via cell site 104. Five of the UEs requests would be fighting to be serviced by the Network Function -14-on the MEC 130 and the remainder would be pushed on to finding an available Network Function in the core network 2, increasing latency and reducing the likelihood of a good user experience.

The system 100 includes a computer 200, which as shown in Figure 2 generally comprises a computer processor 201 and associated memory storage 202, bus 205 with connection to the internet 207 and keyboard 203 and mouse 204 computer script is stored optional I/O devices such as and visual display unit 206. A within the memory storage 202 and executed on processor 201 to carry out the steps shown in flow diagram of Figure 4. The computer 200 is preferably located within each of the MEC 130, 130' 130" or within each of the cell sites 104,104'104", but may be located anywhere in the core network 102 or the cloud 103 or in another cloud.

As shown in incoming requests engine 301. As an the flow diagram 300, the number of (nIR) from UEs is monitored by an Al example, the Al engine 301 comprises a computer program which monitors in real time the number of incoming requests (nIR) from UEs, the computer program comprises an algorithm which compares the number with a threshold number (nT). The threshold number (nT) may be related to the maximum number of licences provided with a particular Network Function available on the respective MEC 130,130'130". In this example, the network function AMF 110z is available on MEC 130". The AMF 110z has a maximum of five licences and the threshold number is predetermined and set within the Al engine 301 as three.

When the number of incoming requests (nIR) reaches the threshold of three, an alert is sent to the core network 2. The alert 302 may comprise a sub-routine to find the -15-same type of Network Function provided with twenty licences, in this case an AMP 110. This step may be carried by interrogating NRF 118, which is located in the core network 102. THE NRF 118 lets the computer program know that there is an AMP 110c of twenty licences in the core network 2. If the AMP 110c is completely free (i.e. no licences are in use) in the core network 2, the AMP 110z is available and the script comprises a further sub-routine to provision the AMP 110z on to the NEC 130", i.e. the AMP 110z is moved to the NEC 130" when the number of incoming requests (nIR) meets a second threshold. In this case, the second threshold is predetermined as four. The NEC 130" is now capable of handling up to 25 simultaneous requests from UEs from AMP 110z and AMP 110c'.

The Al engine 301 monitors in real time the number of incoming requests (nIR) from UEs and compares the number with a threshold number (nT) which is related to the maximum number of licences provided with a particular Network Function available on the NEC 130, for example AMP 110x. The AMP Network Function 110x has a maximum of five licences and the threshold number is predetermined and set within the Al engine 301 as three. When the number of incoming requests (nIR) reaches the threshold of three, an alert 302 is sent to the core network 2. The alert 302 may comprise a sub-routine to find the same type of Network Function, in this case an AMP 110. This step may again be carried by interrogating NRF 118, which is located in the core network 102. The NRE 118 lets the computer program know there is an AMP 110b of twenty licences in the core network 2. However, some of the licences of AMP 110 are in use, so the AMP 110 can not be provisioned on to NEC 130. In which case, when the second threshold meets four, the -16-AMF 1101, is cloned to MEC 130 as a Cloned AMP (C-AMP) 110b'. The C-AMF 110 provides a residual number of licences i.e. if four licences of the twenty licences of the AMP 110 are in use at the time of cloning, the C-Neil 110b' will 5 provide sixteen licences at the MEC 130. The step of cloning may be considered as copying and pasting the AMP 110b from the core network 2 to the MEC 130. The MEC 130 is now capable of handling up to 21 requests from UEs simultaneously between AMP 110z and AMP 110c'. The step of 10 cloning may be considered as copying and pasting the AMP 110b from the core network 102 to the MEC 130.

The Network Functions are generally either Virtual Network Functions (VNFs) or Containerised Network Functions (CNFs). Virtual Network Functions (VNFs) are software applications that deliver network functions such as directory services, routers, firewalls, load balancers, and more. They are deployed as virtual machines (VMs) and have often been the next step for telecommunications providers in their digital transformation from the physical network functions (PNFs) of legacy network appliances on proprietary hardware. Cloud-native "Containerised" Network Functions (CNFs) are designed and implemented to run inside containers. This containerization of network architecture components makes it possible to run a variety of services on the same cluster and more easily on-board already decomposed applications, while dynamically directing network traffic to the correct pods. Thus CNFs and most VNFs are generally packaged so that they can be cloned in one package, without need for additional software to enable them to run and fully function. A CNFs are containerized microservices which may communicate with one another via standardized RESTful APIs. -17-

By using the Al engine 301, licences become available on the MEC 130 generally before UE requests exceed the original number of five AMF licences available on the NEC 130, 130". The step of provisioning AMF 110c on to MEC 130" and cloning AMF 110b to MEC 130 takes in the order of 5 to 10ms.

As shown in the flow diagram 400 in Figure 4A, the Al engine 301 continues to monitor the number of incoming requests (nIR)from UEs. The Al engine 301 continues to note the number of incoming requests (nIR) from UEs and compares the number with the threshold number (nT) which is related to the maximum number of licences provided with the original Network Function available on the NEC 130". As shown in Figure 5, NEC 130" has two Network Functions AMF 110z providing five licences and AMF 110c' providing twenty licences. The original Network Function AMF 110z has five licences and the second threshold number is set within the Al engine 301 as four. The Al engine 301 monitors the number of incoming requests (nIR) and when that number goes below the second threshold (nST) of four, an alert is sent to the core network 2, which requests the NRF 118 for a location for the unwanted Network Function AMF 110c'. In this case, the NRF 118 requests the AMP 110c' is moved to NEC 130'. It should be noted that the NRF 118 may alternatively request the AMF 110c' to be returned to the core network 102.

The Al engine 301 continues to monitor the number of incoming requests (nIR) from UEs. The Al engine 301 continues to note the number of incoming requests (nIR) from UEs and compares the number with the threshold number (nT) which is related to the maximum number of licences provided with the original Network Function available on -18-the NEC 130. As shown in Figure 6, NEC 130 has two Network Functions AMF 110x providing five licences and cloned AMF 110b' providing sixteen licences. The original Network Function AMF 110x has five licences and the threshold number is set within the Al engine 301 as three. The At Engine continues to monitor the number of incoming requests (nIR) and when the threshold of three is met, the cloned AMF 110b' is deleted from the NEC 130, as shown in Figure 7. The step of deleting the cloned AMF 110b' frees the sixteen residual allowing the AMF 110b in the core network to offer sixteen more licences.

There are particular Network Functions which are more likely to be needed on the edge computer (NEC) 130,130',130'", which include UPF and AMF. Network Functions which are less likely to be needed on an edge computer (NEC) 130,130',130" include NRF, AUSF and UDM.

In the case of an AMF network function, the AMF is only used for a few milliseconds for each request, such as a handshake. So it is possible the provisioned AMF 110c' or cloned AMF 110x will only stay on their respective NEC 130", 130 for a few milliseconds, but may stay on their respective NEC 130", 130 for considerably longer if number of incoming request (nIR) stay high, above the relevant threshold.

It should be noted that upon meeting the threshold, the Al engine may be provided with an algorithm that specifies the same type of network function with a different number of licences, such as forty. In this case, in response, the NRF 118 may give a location for two AMFs, each having a maximum of twenty licences. This different number of licences may be predetermined and stored in the computer program of the Al engine, or may be dynamic. Upon -19-the second threshold being met, the computer program comprises an algorithm to provision and/or clone two network functions (in this case AMFs) to the NEC 130,130'130".

It should be noted that the threshold and the second threshold could be the same number, in which case, the step of alerting is actioned immediately upon meeting the threshold and the step of provisioning and/or cloning is carried out immediately thereafter.

It is envisaged that the threshold and second threshold and the number of licences requested in response to meeting the threshold may be predetermined and may be stored in the Al engine. It is also envisaged that the threshold and second threshold are changeable, so that in certain environments, an operator or another program provided with an algorithm can change the predetermined threshold and second threshold. It is also envisaged that the threshold and second threshold are dynamic, varying on other factors noted by the Al Engine 301, such as the location of the cell site. For example, if the cell site is located in a village with a yearly festival, the number of licences when the threshold is met may be set at a high number such as sixty.

The NFOps system disclosed herein integrates attributes of cloud network functions, microservices and Al (AIOPS) to enable dynamic and autonomous mobility of network functions and their resources. This mobility of NFs could be random or organised. In particular, NFOPs integrates, the encapsulation attributes of network functions (VNFs/CNFs), the modularization attributes of microservices, application scheduling and continuous update attributes of Al (AIOPS)and service discovery -20-attributes of cloud-native networks in a single solution. The NFOps system is however, configured to instantiate and initiate one or a series of prompt dynamic and autonomous movements/flow of NFs to and from the core 5 network to the MEC, and to any other elements/components relevant to the process in an end-to-end service-based network setup.

The 5G Core (5GC) network establishes secure and reliable connectivity between the access Network (AN) and end-user equipment/device (UE). It comprises virtualized and or containerised software-based network functions (or services) which have capabilities to authenticate subscribers and devices, apply personalised defined rules (policies) and manage the mobility of the devices before routing the traffic to operator services or the Internet.

The service-based properties of the 5G Core makes it possible for it to be instantiated within Multi-Access Edge Computing (MEC) cloud infrastructures. -21-

Claims

CLAIMS1. A system for handling data in a mobile data network, the system comprising a core network (102) in a cloud (103) and a multiplicity of cell sites (104,104'104"), at least one of the multiplicity of cell sites (104) having an edge computer (MEC,130,130',130") nearby, the core network provided with a multiplicity of Network Functions (110120), at least one of the Network Functions packaged as a Virtual Network Function (VNF) or a Cloud-native Network Function (CNF), and wherein said at least one of the Network Functions packaged as a Virtual Network Function (VNF) or a Cloud-native Network Function (CNF) is provided with a number of licences characterised in that if one or more licences is in use, and said at least one of said 15 Network Functions packaged as a Virtual Network Function or Cloud-native Network Function (CNF) is desired on said edge computer, said at least one of said Network Functions packaged as a Virtual Network Function or Cloud-native Network Function (CNF) is cloned on to said edge computer.
2. A system as claimed in Claim 1, wherein if no licences are in use, and said at least one of said Network Functions packaged as a Virtual Network Function or Cloud-native Network Function (CNF) is desired on said edge computer, said at least one of said Network Functions packaged as a Virtual Network Function or Cloud-native Network Function (CNF) is provisioned on to said edge computer.
3. A system as claimed in Claim 1 or 2, wherein the core network (102) forms part of a 5G network.
4. A system as claimed in any preceding claim wherein each licence is sufficient for a single User Equipment request, such as a handshake or handover.
5. A system as claimed in any preceding claim, wherein -22-the Network Function is at least one of: AMF (110), SMF (111), UPF (112), NRF (118), UDM (114), PCF, AUSF, Al', NEF.
6. A system for handling data in a mobile data network, the system comprising a core network (102) in a cloud (103) and a multiplicity of cell sites (104,104'104"), at least one of the multiplicity of cell sites (104) having an edge computer (MEC,130,130',130") nearby, the core network provided with a multiplicity of Network Functions (110120), at least one Network Function having a determined number of licences on said edge computer, at least one of the Network Functions packaged as a Virtual Network Function (VNF) or a Cloud-native Network Function (CNF), characterised in that a computer program is executed having instructions that when executed monitors the number of incoming requests (nIR) from User Equipment, each incoming request expected to utilise at least one licence of said determined number of licences, the computer program having a threshold number (nT), upon said threshold number being reached, the computer program sending an alert to the core network.
7. A system as claimed in Claim 6, wherein the alert comprises the step of locating another Network Function of the same type.
8. A system as claimed in Claim 6, wherein the alert comprises the step of requesting another network function for a location of the same type of Network Function.
9. A system as claimed in Claim 7 or 8, further comprising the step of attempting to provision the located network function to the edge computer.
10. A system as claimed in Claim 9 wherein, if the attempt is unsuccessful, cloning the located network function to the edge computer. -23-
11. A system as claimed in Claim 9, wherein the step of attempting to provision occurs upon meeting a second threshold.
12. A system as claimed in any one of Claims 9 to 11, further comprising the step of locating a determined number of network functions of the same type.
13. A system as claimed in Claim 12, wherein the computer program will determine the number of network functions to provision and/or clone to the edge computer.
14. A system as claimed in any one of Claims 9 to 13, wherein the threshold is a fixed pre-determined number.
15. A system as claimed in any one of Claims 9 to 14, wherein the computer program is executed on a computer processor located within the cell site.
16. A system as claimed in any one of Claims 9 to 15, wherein the computer program is executed on a computer processor located within the edge computer.
17. A system as claimed in any one of Claims 9 to 16, wherein the computer program comprises an algorithm to remove a cloned network function from the edge computer upon the number of incoming requests (nIR) falling below a threshold.
18. A system as claimed in Claim 17, wherein the computer program comprises an algorithm to move a provisioned network function from the edge computer to a different location upon the number of incoming requests (nIR) falling below a threshold.
19. A system for enhancing a user experience in a mobile data network, the system comprising a core network (102) 30 in a cloud (103) and a multiplicity of cell sites (104,104'104"), at least one of the multiplicity of cell sites (104) having an edge computer (NEC,130,131,132) -24-nearby, the core network provided with a multiplicity of Network Functions (110-120), at least one Network Function having a determined number of licences on said edge computer, at least one of the Network Functions packaged as a Virtual Network Function (VNF) or a CNF, characterised in that a computer program is executed having instructions to apply an Al algorithm to assess if a further Network Function should be provisioned or cloned to the edge computer to ensure capacity to meet expected demand.
20. A system for enhancing a user experience in a mobile data network, the system comprising a core network in a cloud and a multiplicity of cell sites, at least one of the multiplicity of cell sites having an edge computer nearby, the core network provided with a multiplicity of Network Functions, at least one of the Network Functions packaged as a Virtual Network Function (VNF) or a CNF, characterised in that the Network Function packaged as a Virtual Network Function or Cloud-native Network Function (CNF) is cloned to on to said edge computer.