NETWORK SLICE MANAGEMENT

Abstract

A method of managing network traffic in a telecommunications network, the telecommunications network having a plurality of network slices and a User Equipment (UE), wherein the UE is 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, redirecting the network communication to the second network slice whilst the UE remains registered with the first network slice.

Claims

1. A method of managing network traffic in a telecommunications network, the telecommunications network having a plurality of network slices and a User Equipment (UE), wherein the UE is 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, redirecting the network communication to the second network slice whilst the UE remains allocated to the first network slice.

2. A method according to claim 1, wherein the network communication is redirected to the second network slice before being received by the first network slice.

3. A method according to claim 1, wherein the step of identifying the second network slice is performed in response to identifying a lack of suitability of the first network slice.

4. A method according to claim 1, wherein the first network slice is suitable to process the network communication if it has, or will have, sufficient excess available processing resources to process the network communication.

5. A method according to claim 1, wherein the first network slice is suitable to process the network communication if the first network slice has, or will have, a number of concurrent users that is below a threshold.

6. A method according to claim 1, wherein the first network slice is suitable to process the network communication if network performance of the first network slice is, or will be, beyond a threshold.

7. A method according to claim 1, wherein the first network slice is suitable to process the network communication if an absence of any ongoing and/or future reconfiguration of the first network slice is identified.

8. A method according to claim 7, wherein the reconfiguration is a: re-starting; scaling; closing; and/or opening of the first network slice.

9. A method according to claim 1, wherein identifying a lack of suitability of the first network to process the network communication triggers the first network slice to reconfigure.

10. A method according to claim 1, wherein the step of identifying the second network slice is performed in response to identifying a lack of suitability of the first network to process the network communication.

11. A method according to claim 1, wherein 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.

12. A method according to claim 1, wherein 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.

13. A method according to claim 1, wherein the first and the second network slices remain operational during, at least, the steps of monitoring, identifying and redirecting.

14. A method according to claim 1, wherein the network communication is redirected to at least one function, but not to all functions, of the second network slice.

15. A method according to claim 14, wherein the network communication is redirected to a User Plane Function (UPF) of the second network slice.

16. A method according to claim 1, further comprising the steps of: continuing to monitor the suitability of the first network slice to process the network communication after redirecting the network communication to the second network slice; and in response to identifying that the first network slice is suitable to process the network communication, ceasing to redirect the network communication to the second network slice.

17. A method according to claim 1, wherein the second network slice has substantially the same configuration as the first network slice, when the first network slice is suitable for processing the network communication.

18. A method according to claim 1, wherein the network performance of the second network slice is no worse than the network performance of the first network slice, when the first network slice is suitable for processing the network communication.

19. A method according to claim 1, wherein the first network slice is a network slice that is preferred by the telecommunications network over the second network slice for processing the network communication, when the first network slice is suitable for handling the network communication.

20. A method according to claim 1, wherein 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.

21. A method according to claim 1, wherein a single given network slice of the telecommunications network is, in a first iteration of the method, the first network slice and, in a second iteration of the method, is the second network slice.

22. A method according to claim 1, wherein redirecting the network communication to the second network slice is implemented in a core of the telecommunications network.

23. A method according to claim 1, wherein the telecommunications network is a mobile cellular network.

24. A method according to claim 1, wherein the telecommunications network is a fixed-line network.

25. A telecommunications network for managing network traffic, the telecommunications network comprising: a first network slice and a second network slice, 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 suitable for processing the network communication; and a controller for redirecting the network communication to the second network slice, whilst the UE remains allocated to the first network slice, in response to identifying a lack of suitability of the first network slice to process the network communication.

26. A telecommunications network according to claim 25, wherein the processor and the controller are arranged in a core of the telecommunications network.

27. 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 method according to claim 1.

Description

[0038] The invention extends to a method of managing network traffic 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:

[0039] FIG. 1 shows a schematic diagram of an exemplary telecommunications network;

[0040] FIG. 2 shows a portion of the network; and

[0041] FIGS. 3, 4 and 5 outline processes for managing network slices within the network.

SPECIFIC DESCRIPTION

[0042] FIG. 1 is a schematic diagram of an exemplary telecommunications network 100.

[0043] 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.

[0044] The network 100 operates in accordance with, for example, 5G technology. Accordingly, in this example, the core network 125 comprises the following functional components: [0045] Network Slice Selection Function (NSSF) 130; [0046] AUthentication Server Function (AUSF) 135; [0047] Unified Data Management (UDM) 140; [0048] Access and mobility Management Function (AMF) 145; [0049] Session Management Function (SMF) 150; [0050] Policy Control function (PCF) 155; [0051] Application Function (AF) 160; [0052] User Plane Function (UPF) 165; and [0053] Data Network (DN) 175.

[0054] 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.

[0055] The aforementioned functional components are configured to redirect network traffic internally amongst network slices when a given network slice is temporarily unsuitable for processing a given network communication.

[0056] In more detail, FIG. 2 illustrates the components of the core network 125 that are responsible for redirecting network traffic amongst network slices.

[0057] 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 triggers reconfiguration of the network slices 220, and in particular triggers redirection of network communications amongst the network slices 220. A network slice orchestrator (not shown) effects the (re-)configuration (e.g. triggered by the NSM) of 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.

[0058] 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 (e.g. the number of UEs that are simultaneously allocated to a given network slice); and/or performance metrics (including, for example, latency, bandwidth, jitter, error rate and/or round-trip delay time).

[0059] In the normal course of operation of the network, the UE is allocated 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.

[0060] 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 network traffic from the UE is redirected to an alternative—partner—network slice 220-2; this occurs whilst the UE is registering with the primary network slice 220-1 and/or whilst the UE remains registered with the primary network slice 220-1.

[0061] FIG. 3, outlines in more detail a process 300 by which a network communication is redirected to a partner slice. In a first step 310, a network communication from the UE 110 is received by the network 100. The network communication is, for example, an attach request for attaching to the network. Once the (or part of the) network communication has been received by the network, the NSSF 130 identifies a primary network slice onto which to allocate the UE. Registration of the UE with the primary network slice is subsequently triggered, and registration follows 320.

[0062] 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 330 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.

[0063] If it is ascertained that the primary network slice 220-1 is not operating or performing sufficiently (e.g. because it is scaling), this is communicated to the NSM 210-1 (e.g. from the AsFn, or by having the NSM access the database 230), which in step 340 triggers the NSSF to identify the partner network slice 220-2.

[0064] 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 NSSF communicates the identity of the partner network slice to the NSM, which subsequently instructs the UPF 165 internally to redirect the network communication associated with the UE 110 from the primary network slice to the partner network slice 350.

[0065] 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.

[0066] After the network communication has been redirected to the partner network slice, the process then reiterates to evaluate anew whether the primary network slice is now (or now will be) suitable for processing the (ongoing) network communication 330. If so, then the NSM abolishes the redirection of the network communication and instead routes—as in the normal course of events—the network communication through the primary network slice 360.

[0067] 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.

[0068] FIG. 4 is a diagram illustrating signalling between the UE and the components of the network 100 so as to perform the process 300 as show in, and as described with reference to, FIG. 3.

[0069] 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.

[0070] Once the UE has registered with the network 100, and a Protocol Data Unit (PDU) session is established, the NSSF identifies the primary network slice, onto which the UE is registered. 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 NSM triggers the NSSF to identify the partner network slice and subsequently triggers the UPF 150 to redirect the network communication from the primary network slice to the partner network slice 420 (having been identified by the NSSF).

[0071] Once the AsFn identifies that the primary network slice is suitable for handling the network communication, the NSM triggers the UPF to cease the redirection so as to route the network communication, as normal, through the primary network slice 430.

[0072] Advantageously, and as best shown in FIG. 4, the process of redirecting network communications amongst network slices is transparent to the UE; that is, the UE remains attached to the primary network slice, and so the process requires no further signalling with the UE, thereby reducing signalling overhead within the network (not least, network slice admission control signals between the RAN and the UE).

[0073] The effect of the redirection is to loan processing resources from one network slice to another; this can alternatively be achieved by directly reallocating processing resources between network slices (for example, as outlined in a co-pending patent application filed by this same applicant under Applicant's reference A33738, the contents of which are hereby incorporated by reference). However, redirection of a network communication is less complex to establish—and to revert from—than actual reallocation of processing resources between network slices. In addition, the effective loaning of processing resources by redirecting a network communication as outlined above is more resource-efficient than actual reallocation of processing resources amongst network slices, since only functional resources are ‘loaned’; that is, only a UPF is ‘loaned’ rather than an entire network slice.

[0074] FIG. 5 shows, in more detail, a process 500 by which the network communication from the UE is redirected to the partner network slice when the primary network slice is unsuitable because it is scaling.

[0075] 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), the network further queries whether the UE is active and responsive 525. If not, and the UE is a new UE, it is registered with an alternative network slice (which may be the partner network slice, for example as outlined in a co-pending patent application filed by this same applicant under Applicant's reference A33733, the contents of which are hereby incorporated by reference).

[0076] If the UE is already connected to the primary network slice, but if the UE is not active and responsive, 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).

[0077] If the UE is active and responsive, the NSSF identifies a suitable partner network slice for the UE 535, and the NSM instructs the UPF internally to redirect the network communication of the UE to the identified partner network slice 540, and the redirection is subsequently established 545.

[0078] 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 (and/or the level of utilisation of the network slice decreases as a proportion of its total capacity), the network queries whether the primary network slice is suitable for handling the UE (as performed by the AsFn) 555. If not, the redirection remains until the UE is disconnected or de-registers 565 (or the UE is re-registered with an alternative network slice. If so, the NSM is informed of the suitability of the primary network slice (by the AsFn, and optionally the NSSF) and therefore triggers the UPF to terminate the redirection 565.

[0079] 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).

[0080] 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).

[0081] Alternative and Modifications

[0082] The network 100 shown in, and described with reference to, FIG. 1, is a mobile cellular network. However, it will be appreciated that the aforementioned is available to be implemented as part of any network that utilises network slicing, and more generally as part of any network utilising virtualisation to segregate network resources, including fixed line, local area, and wide area networks. In such examples, the process of managing network resources as described above is performed by functional components of such networks that are analogous to those of the network 100.

[0083] 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.

[0084] The identification of the partner network slice is available to be conducted at any stage in the processes described above, in particular: prior to the UE registering with the primary network slice; after the UE registers with the primary network slice; and/or once the primary network slice is deemed unsuitable for processing the network communication.

[0085] 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).

[0086] It will be appreciated that abolishing the redirection of the network communication to the primary network slice from the partner network slice is optional, and in certain circumstances it may be preferable to retain redirection, not least to reduce the processing overhead of implementing a further redirection.

[0087] Each feature disclosed in the description, and (where appropriate) the claims and drawings may be provided independently or in any appropriate combination.

[0088] Reference numerals appearing in the claims are by way of illustration only and shall have no limiting effect on the scope of the claims.