Patent Application
20220039002
The present invention relates to a method of, and to a telecommunications network for, managing allocation of a User Equipment (UE) to a network slice.
Network slicing is a method of virtualising a network so as to create multiple logical networks within a single physical network. This is typically undertaken to offer differentiated service models, which might include varying performance and/or stability characteristics within a network, and it is supported by the fact that network slices are isolated from one another other during operation. As a result, high traffic or a large number of users on one slice is unable negatively to affect other network slices.
For example, network slices may be configured to provide specialised functions, including: exclusively serving emergency services (which demands, at least, reliability); enhanced Mobile Broadband (eMBB); and Massive Machine Type Communications (MMTC).
A network will adapt network slices to suit network conditions and to optimise utilisation of individual network slices. To ensure constant availability of resources as network slices' resources are consumed, scaling occurs. If a network slice reaches a threshold utilisation the creation of additional slice resources may be triggered so as to cope with high network loads; this is typically achieved by ‘scaling up’ or by ‘scaling out’ a network slice.
The allocation of new processing resources to a network slice (via scaling) can take a matter of minutes, and typically around 2 to 10 minutes. However, during such scaling, network slices are particularly susceptible to additional loads. As a result, new users may be prevented from accessing the network or network congestion may be experienced by users.
It is an aim of the present invention at least to alleviate some of the aforementioned problems.
According to a first aspect of the present invention, there is provided a method of managing allocation of a User Equipment (UE) to a network slice of a telecommunications network, the telecommunications network having a plurality of network slices, wherein the UE is—optionally, initially—allocated to a first network slice for processing a network communication from the UE, the method comprising the steps of: monitoring a suitability of the first network slice to process the network communication; identifying a second network slice that is suitable for processing the network communication; and in response to identifying a lack of suitability of the first network slice to process the network communication, registering the UE with the second network slice prior to registering the UE with the first network slice. Optionally, the telecommunications network has a plurality of UEs. In this way, the UE may instead be registered with the second network slice.
Optionally, said monitoring is performed whilst the UE is allocated to the first and/or second network slice.
Optionally, the UE is only registered with the second network slice. Optionally, the UE is registered with the second network slice so as to utilise only constituent functions of the second network slice (e.g. an Access and mobility Management Function and a User Planer Function), and therefore not to utilise constituent functions of the first network slice.
As used herein, “prior to registering”, in the context of the UE registering with the first network slice, preferably connotes a time before the first network slice performs any processing associated with the UE. Alternatively, “prior to registering” may connote a time before the first network slice: generates any communications bound for the UE; processes part, but not all, of the network communication; or performs any processing of payload data from the UE.
As used herein, the term “allocated” with reference to the allocation of the UE to the first network slice, preferably connotes the identification or selection of the first network slice as a suitable network slice with which to register the UE, but where the UE has not yet registered with the first network slice.
Optionally, the network communication is: a data packet; a part thereof; a plurality of data packets; and/or a data session. The network communication may be an attach request or may follow an attach request.
Advantageously, the aforementioned method may improve the management of network processing resources so as to prevent overloading of a network slice and to prevent a new UE—that is yet to register with a network slice—from experiencing network congestion as a result.
Preferably, the method further comprises the step of preventing the UE from first registering with the first network slice. More preferably, the UE is prevented from registering with the first network slice in response to determining a lack of suitability of the first network slice.
Preferably, the first (and/or second) network slice is suitable to process the network communication if the first (and/or second) network slice has, or will have, sufficient excess available processing resources to process the network communication. The method may therefore further comprise the step of determining the processing resources available on the first and/or second network slice/s.
Preferably, the first (and/or second) network slice is suitable to process the network communication if the first (and/or second) network slice has, or will have, a number of concurrent users that is below a threshold. The method may therefore further comprise the step of determining the number of concurrent users on the first and/or second network slice/s.
Preferably, the first (and/or second) network slice is suitable to process the network communication if the first (and/or second) network slice has a network performance that is, or will be, beyond (or above) a threshold. The method may therefore further comprise the step of determining the network performance of the first and/or second network slice/s. The network performance may be determined by measuring: latency, jitter, bandwidth, packet error rate and/or Round-Trip Time (RTT). The network performance threshold may be dependent on the type of network communication.
Preferably, the first (and/or second) network slice is suitable to process the network communication if an absence of any ongoing and/or future reconfiguration associated with the first (and/or second) network slice is identified. The method may therefore further comprise the step of identifying ongoing and/or (scheduled) future reconfiguration of the first and/or second network slice/s. Optionally, the reconfiguration is a: re-starting; scaling (up, down and/or out); closing; and/or opening of the first network slice.
Optionally, identifying the first (and/or second) network slice as being unsuitable to process the network communication triggers the first network slice to reconfigure.
Preferably, identifying the second network slice is performed in response to identifying the first network slice as being unsuitable.
Preferably, the network communication would cause, if processed by the first network slice, or does cause, the first network slice to become unsuitable for processing the network communication. Optionally, the registration of the UE to the first network slice would cause the first network slice to become unsuitable for processing the network communication. In which case, the network communication may cause re-configuration of the first network slice.
Preferably, the method further comprises the steps of: continuing to monitor the suitability of the first network slice to process the network communication after the UE has been registered to the second network slice; and in response to identifying that the first network slice is suitable to process the network communication, unregistering the UE from the second network slice and subsequently registering the UE with the first network slice.
Preferably, the second network slice has substantially the same configuration and/or network performance as the first network slice, when the first network slice is suitable for processing the network communication. The second network slice may therefore be configured for the same purpose as the first network slice, wherein the purposes may be a specialised function, such as eMBB, emergency services communications, Ultra Reliable, Low Latency Communications (URLLCs), etc. Optionally, the second network slice is a network slice that has the closest matching configuration and/or network performance to that of the first network slice. Optionally, the second network slice is identified in dependence on the amount of excess processing resources available and similarity of configuration to the first network slice.
Preferably, the second network slice is configured to process the network communication in a manner that is no worse than the first network slice, when the first network slice is suitable for processing the network communication; more preferably, this is when: network efficiency (cost, or other resource); network performance; Quality of Service; and/or Quality of Experience associated with processing the network communication are no worse.
Optionally, the first network slice is a network slice that is most preferred by the telecommunications network for processing the network communication, when the first network slice is suitable for handling said network communication. Optionally, the first network slice is a network slice that is preferred over the second network slice by the telecommunications network for processing the network communication, when the first network slice is suitable for handling said network communication. Preference of a network slice by the network may be dependent on: network efficiency (cost, or other resource); network performance metrics; Quality of Service; and/or Quality of Experience.
Preferably, identifying the second network slice further comprises the steps of: measuring network performance of the second network slice; and assessing whether the network performance surpasses a threshold. Alternatively, the second network slice may be preselected.
A single given network slice of the telecommunications network may be (simultaneously or sequentially) the first network slice in a first iteration of the method and the second network slice in a second iteration of the method.
The telecommunications network may be a mobile cellular network and/or a fixed-line network.
According to another aspect of the invention, there is provided a telecommunications network for managing allocation of a User Equipment (UE) to a network slice, the telecommunication network comprising: a first network slice and a second network slice (provided, for example, by a processor), and the UE being allocated to the first network slice for processing a network communication from the UE; a processor for monitoring a suitability of the first network slice to process the network communication and for identifying a second network slice that is (or will be, once the UE is registered) suitable for processing the network communication; and a controller for registering the UE with the second network slice prior to registering the UE with the first network slice in response to identifying a lack of suitability of the first network slice to process the network communication. Optionally, the processor and the controller are arranged in a core of the telecommunications network.
According to yet another aspect of the invention, there is provided a computer-readable storage medium comprising instructions that, when executed by a processor associated with a telecommunications network, causes the telecommunication network to perform the aforesaid method.
The invention extends to any novel aspects or features described and/or illustrated herein. The invention extends to methods and/or apparatus substantially as herein described and/or as illustrated with reference to the accompanying drawings. The invention also provides a computer program and a computer program product for carrying out any of the methods described herein and/or for embodying any of the apparatus features described herein, and a computer readable medium having stored thereon a program for carrying out any of the methods described herein and/or for embodying any of the apparatus features described herein.
The invention also provides a signal embodying a computer program for carrying out any of the methods described herein and/or for embodying any of the apparatus features described herein, a method of transmitting such a signal, and a computer product having an operating system which supports a computer program for carrying out any of the methods described herein and/or for embodying any of the apparatus features described herein.
Any apparatus feature as described herein may also be provided as a method feature, and vice versa. As used herein, means plus function features may be expressed alternatively in terms of their corresponding structure, such as a suitably programmed processor and associated memory.
Any feature in one aspect of the invention may be applied to other aspects of the invention, in any appropriate combination. In particular, method aspects may be applied to apparatus aspects, and vice versa. Furthermore, any, some and/or all features in one aspect can be applied to any, some and/or all features in any other aspect, in any appropriate combination. It should also be appreciated that particular combinations of the various features described and defined in any aspects of the invention can be implemented and/or supplied and/or used independently.
In this specification the word ‘or’ can be interpreted in the exclusive or inclusive sense unless stated otherwise.
Furthermore, features implemented in hardware may generally be implemented in software, and vice versa. Any reference to software and hardware features herein should be construed accordingly.
The invention extends to a method of managing allocation of a User Equipment (UE) to a network slice and a telecommunications network as described herein and/or substantially as illustrated with reference to the accompanying drawings. The present invention is now described, purely by way of example, with reference to the accompanying diagrammatic drawings, in which:
The network 100 is shown as a mobile cellular network comprising User Equipment (UE) 110 (e.g. in the form of a mobile cellular device, laptop or tablet) that is configured to utilise the telecommunications network 100 by accessing a Radio Access Network (RAN) 115, as provided by RAN access points 120 (e.g. in the form of a macro-, micro-, pico- or femto-cell site). In turn, the RAN access points 120 are connected to a core network 125.
The network 100 operates in accordance with, for example, 5G technology. Accordingly, in this example, the core network 125 comprises the following functional components:
By means of the aforementioned functional components of the core network 125, the network 100 provides and manages a plurality of network slices. In particular, the NSSF 130 is configured to identify and to select a suitable network slice for the UE 110, and then to communicate that selection in order to help ensure that the UE is registered with the selected network slice.
In more detail,
Within the network core 125, there is provided a Network Slice Manager (NSM) 210-1, which is in communication with the User Plane Function (UPF) 165 for network slices 220. The NSM configures the network slices 220 so as to manage the processing resources of the network slices, and therefore to fulfil the demands of services utilising the network slices.
As part of the NSM 210-1, an Assurance Function (AsFn) 210-2 is provided that ascertains the performance of network slices 220; that is, whether individual network slices are operating and are performing sufficiently. For example, the AsFn measures: processing unit consumption; number of concurrent users; and/or performance metrics (including, for example, latency, bandwidth, jitter, error rate and/or round-trip time).
In the normal course of operation of the network, the UE is assigned to, and registered with, a primary network slice 220-1. The primary network slice 220-1 is the most preferred network slice, when performing as required, for processing network communications from a given UE, and it is selected, not least, in dependence on: a prescribed selection; the type of UE; the type of network communication from the UE; time; and/or the service agreement between the mobile network operator of the core network 125 and the UE.
The NSM 210-1 receives from—and/or retrieves from a database 230 populated by—the AsFn 210-2 data regarding the operation and performance of the primary network slice 220-1. If the primary network slice 220-1 is not suitable for processing a network communication from the UE, then the UE is assigned to an alternative—partner—network slice 220-2.
At a given moment, the identified primary network slice 220-1 may not be suitable for processing a network communication from the UE. This may be for a variety of reasons, including: an existing processing capacity breach; an insufficiency of excess available processing resources to process the network communication; downtime in the network slice; scaling (out, up and/or down) of the primary network slice in order to increase processing resources of the network slice; creation or restarting of the primary network slice without it yet fully operating; removal of the primary network slice; and/or other reconfiguring of the primary network slice. Accordingly, a determination 320 is made whether the primary network slice is (or will be, within an acceptable period of time, for example by the time that the UE is registered) suitable for processing the network communication from the UE 110; this is determined by the AsFn.
If it is ascertained that the primary network slice 220-1 is not operating or performing sufficiently 330 (e.g. because it is scaling, as triggered by the NSM), this is communicated to the NSSF (e.g. from the AsFn, or by having the NSSF access the database 230), and the NSSF 130 prevents the UE 110 from registering with the primary network slice 220-1. In effect, the NSM thereby prevents the primary network slice 220-1 from having to process the network communication, and the partner network slice lends its processing resources to assist the primary network slice. As a result, the primary network slice is protected (for example, if it is overloaded and/or scaling) and prevents or helps reduce network congestion as experienced by the UE 100 and/or by existing UEs already registered with the primary network slice 220-1.
In this eventuality 330, the NSSF 130 identifies the partner network slice 220-2 for the UE. Once identified, and its suitability (current or expected) to handle the network communication from the UE 110 has been confirmed by the AsFn 210-2, the UE is then instructed to register with the partner network slice 220-2, and subsequently does so 340.
In the event that it is determined that the primary network slice is (or will be) suitable for processing the network communication, then the UE is permitted to register with the primary network slice 350.
After the UE has registered with the partner network slice 220-2 in step 340, the process 300 then repeats to evaluate anew whether the primary network slice is now (or now will be) suitable for processing the (ongoing) network communication. If so, then the UE registers with the primary network slice 350, otherwise the UE remains registered to the partner network slice 220-2 in step 340.
It will be appreciated that the partner network slice is available to change with each loop of the process 300, since a previously-identified partner network slice may no longer be suitable to process a subsequent network communication. Accordingly, a primary network slice may become a partner network slice, and vice versa, over different iterations of process 300.
In a first signalling process 410, the UE 100 sends a network communication to the network 100 via the RAN 120. The AMF 145 receives and processes the network communication in order to establish a connection with the UE; this is performed, for example as outlined in the 3rd Generation Partnership Project (3GGP) Technical Specification 23.502, version 15.2.0, section 4.3.2.2, the contents of which are hereby incorporated by reference.
Once the UE has attached to the network 100, and a Protocol Data Unit (PDU) session has been established, the NSSF identifies the primary network slice. Where it is established (by the AsFn 210-2) that the primary network slice is not suitable for handling network communications from the UE, the NSSF identifies the partner network slice and triggers the AMF to instruct the UE instead to attach to the partner network slice 420. Under these circumstances, the UE is prevented from registering with the primary network slice.
The AMF instructs the UE to attach to the partner network slice 430, and once the UE has done so, the UE registers with the partner network slice 440 to establish a Protocol Data Unit (PDU) session with the partner network slice (again, as per 3GGP Technical Specification 23.502, version 15.2.0, section 4.3.2.2).
After the UE is registered with the partner network slice, the AsFn 210-2 continues to monitor the suitability of the primary network slice. Once the AsFn identifies that the primary network slice is suitable for handling the network communication, the NSSF triggers the AMF to instruct the UE to detach from the partner network slice and then to attach to the primary network slice 450. The AMF proceeds accordingly 460, and the UE attaches to the primary network slice 460 thereby to establish a PDU session (again, as per 3GGP Technical Specification 23.502, version 15.2.0, section 4.3.2.2).
In a first step, slice scaling (up, down or out) of the primary network slice is identified (responsively or anticipatorily) 510. The network 100 then queries whether the UE is already connected to the primary network slice 515. If so, the UE is allowed to remain on the primary network slice in order to help reduce disruption to the scaling primary network slice 520. If not, and the UE is a new UE, the network further queries whether the UE is active and responsive 525. If not, for network efficiency, the UE is ignored 530, and query 525 is repeated to identify whether the UE subsequently becomes active (e.g. by using a UPF resource).
If the UE is active and responsive, the NSSF identifies a suitable partner network slice for the UE 535, and the AMF instructs the UE to attach to the identified partner network slice 540, thereby registering the UE with the partner network slice 545.
Steps 510 to 545 all occur whilst the primary network slice has been triggered to scale and/or is currently scaling. Once the primary network slice has scaled 550, the network queries whether the primary network slice 560 is suitable for handling the UE (as performed by the AsFn). If not, the UE remains attached to the partner network slice (until the UE is disconnected or de-registers) 565. If so, the NSSF is informed of the availability of the primary network slice and therefore triggers the AMF to register the UE with the primary network slice 570.
When identifying a partner network slice, the NSSF identifies a network slice that is a most appropriate alternative to the primary network slice; that is, a network slice having the same—or a substantially similar—configuration and performance, including in relation to: latency; jitter; bandwidth; availability of processing resources; Quality of Service; Service Level Agreement; type/specialisation of network slice (e.g. Ultra-Reliable Low-Latency Communications, Mobile Broadband and enhanced, and Massive Machine Type Communications); and services available on a given network slice (e.g. Voice-over-WiFi® calling).
In order to maintain a minimum standard of service, rules governing the selection of the partner network slice are utilised, including restrictions that the partner network slice performs no worse than the primary network slice (when it is deemed to be operating as required, for example by the AsFn).
The network 100 shown in, and described with reference to,
In one alternative, the UPF 165 associated with the network slices 220 alerts the NSM 210-1 and/or the AsFn 210-2 when the first network slice is no longer suitable.
In one example, the partner network slice is identified for a specific primary network slice (and therefore applies to all UEs that would register with a given primary network slice). In another example, the partner network slice is identified for a specific UE (that is, on a ‘per-UE’ basis).
It will be appreciated that reverting the UE to the primary network slice from the partner network slice is optional, and in certain circumstances it may be preferable to retain the UE on the partner network slice, not least to reduce the processing overhead of re-registering the UE.
Each feature disclosed in the description, and (where appropriate) the claims and drawings may be provided independently or in any appropriate combination.
Reference numerals appearing in the claims are by way of illustration only and shall have no limiting effect on the scope of the claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 18197290.2 | Sep 2018 | EP | regional |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/EP2019/072807 | 8/27/2019 | WO | 00 |
