Network slicing

Abstract

Embodiments of the present disclosure relate to slicing a communication network. In accordance with an example aspect of the present disclosure, there is provided an apparatus configured to: receive, from an access network included in a first cellular network, a first network slice identification of a first network slice accessible via the access network; determining, based on the first network slice identification, that the first network slice is partially served in a core network of the second cellular network; and providing a request to the access network that the device is to be registered on the first network slice.

Description

Technical Field

[0001] The present disclosure relates to slicing communication networks. Background Art

[0002] Network slicing has been used to generate multiple logical cellular communication networks running on the same physical network, where the physical network may include a radio access network and a core network.

[0003] Individual slices can be configured to provide agreed services and service quality, so that the utilization of the underlying physical network infrastructure can be increased. On the other hand, when slices can be obtained from an already existing physical cellular communication network instead of building a new physical network, the capital expenditure of building a new network is significantly reduced. Summary of the invention

[0004] According to some aspects, the subject matter of independent claims is provided. Some embodiments are defined in the dependent claims. The scope of protection sought by various embodiments of the present invention is set forth by the independent claims. The embodiments, examples and features (if any) described in this specification that do not fall within the scope of the independent claims should be interpreted as examples that help understand the various embodiments of the present invention.

[0005] According to a first aspect of the present disclosure, a device is provided, comprising: at least one processing core and at least one memory, the at least one memory storing instructions, which, when executed by the at least one processing core, causes the device to at least: receive a first network slice identifier of a first network slice accessible via an access network included in a first cellular network; determine, based on the first network slice identifier, that the first network slice is partially served in a core network of a second cellular network; and provide a request to the access network for the device to be registered on the first network slice.

[0006] According to a second aspect of the present disclosure, a device is provided, comprising: at least one processing core and at least one memory, the at least one memory storing instructions, which, when executed by the at least one processing core, causes the device to at least: provide a first network slice identifier of a first network slice that can be accessed via the device to a user equipment in a coverage area of ​​a cell controlled by the device, wherein the first network slice identifier indicates that the first network slice is partially served in a core network of a second cellular network, which is different from the first cellular network including the device; and receive a request from the user equipment for the user equipment to be registered on the first network slice.

[0007] According to a third aspect of the present disclosure, a device is provided, comprising: at least one processing core and at least one memory, the at least one memory storing instructions, which, when executed by the at least one processing core, causes the device to at least: receive a request for registering a user device on a first network slice from an access network of a first cellular network, the first network slice using core network resources of a second cellular network and access network resources of the first cellular network, the device being included in the core network of the second cellular network, and determine whether the user device is allowed to enter the first network slice.

[0008] According to a fourth aspect of the present disclosure, a method is provided, comprising: in a device, receiving a first network slice identifier of a first network slice accessible via an access network included in a first cellular network from an access network included in the first cellular network; based on the first network slice identifier, determining that the first network slice is partially served in a core network of a second cellular network; and providing a request to the access network for the device to be registered on the first network slice.

[0009] According to a fifth aspect of the present disclosure, a method is provided, comprising: providing a first network slice identifier of a first network slice that can be accessed via a device to a user equipment in a coverage area of ​​a cell controlled by a device executing the method, wherein the first network slice identifier indicates that the first network slice is partially served in a core network of a second cellular network, which is different from the first cellular network including the device; and receiving a request from the user equipment for the user equipment to be registered on the first network slice.

[0010] According to a sixth aspect of the present disclosure, a method is provided, comprising: receiving a request for registering a user equipment on a first network slice from an access network of a first cellular network, the first network slice using core network resources of a second cellular network and access network resources of the first cellular network, an apparatus for executing the method being included in the core network of the second cellular network, and determining whether the user equipment is allowed to enter the first network slice.

[0011] According to a seventh aspect of the present disclosure, a device is provided, comprising: at least one processing core and at least one memory, the at least one memory storing instructions, which, when executed by the at least one processing core, causes the device to at least: determine a network slice to be served and deployed in an access network of a first cellular network and a core network of a second cellular network; and configure the network slice to be active in the access network of the first cellular network and the core network of the second cellular network.

[0012] According to an eighth aspect of the present disclosure, a device is provided, comprising components for: in the device, receiving a first network slice identifier of a first network slice accessible via an access network included in a first cellular network; based on the first network slice identifier, determining that the first network slice is partially served in a core network of a second cellular network; and providing a request to the access network for the device to be registered on the first network slice.

[0013] According to a ninth aspect of the present disclosure, a device is provided, comprising components for: providing a first network slice identifier of a first network slice that can be accessed via the device to a user equipment in a coverage area of ​​a cell controlled by the device executing the method, wherein the first network slice identifier indicates that the first network slice is partially served in a core network of a second cellular network, which is different from the first cellular network including the device; and receiving a request from the user equipment that the user equipment is to be registered on the first network slice.

[0014] According to the tenth aspect of the present disclosure, a device is provided, comprising components for: receiving a request for registering a user equipment on a first network slice from an access network of a first cellular network, the first network slice using core network resources of a second cellular network and access network resources of the first cellular network, the device for executing the method being included in the core network of the second cellular network, and determining whether the user equipment is allowed to enter the first network slice.

[0015] According to the eleventh aspect of the present disclosure, a non-transitory computer-readable medium is provided, having a set of computer-readable instructions stored thereon, which, when executed by at least one processor, causes the device to at least: receive a first network slice identifier of a first network slice accessible via an access network included in a first cellular network; based on the first network slice identifier, determine that the first network slice is partially served in a core network of a second cellular network; and provide a request to the access network for the device to be registered on the first network slice.

[0016] According to the twelfth aspect of the present disclosure, a non-transitory computer-readable medium is provided, having a set of computer-readable instructions stored thereon, which, when executed by at least one processor, causes the device to at least: provide a first network slice identifier of a first network slice that can be accessed via the device to a user equipment in a coverage area of ​​a cell controlled by the device, wherein the first network slice identifier indicates that the first network slice is partially served in a core network of a second cellular network, which is different from the first cellular network including the device; and receive a request from the user equipment that the user equipment is to be registered on the first network slice.

[0017] According to the thirteenth aspect of the present disclosure, a non-transitory computer-readable medium is provided, having a set of computer-readable instructions stored thereon, which, when executed by at least one processor, causes the device to at least: receive a request for registering a user equipment on a first network slice from an access network of a first cellular network, the first network slice using core network resources of a second cellular network and access network resources of the first cellular network, the device being included in the core network of the second cellular network, and determine whether to allow the user equipment to enter the first network slice. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1A illustrates example systems in accordance with at least some embodiments of the present invention;

[0019] Figure 1B illustrates example systems in accordance with at least some embodiments of the present invention;

[0020] Figure 2A illustrates example slice identifiers in accordance with at least some embodiments of the present invention;

[0021] Figure 2B illustrates a signaling diagram according to at least some embodiments of the present invention;

[0022] Figure 3 illustrates example devices capable of supporting at least some embodiments of the present invention;

[0023] Figure 4 illustrates signaling in accordance with at least some embodiments of the present invention, and

[0024] Figure 5 is a flow chart of a method according to at least some embodiments of the present invention. DETAILED DESCRIPTION

[0025] Disclosed herein is a method of configuring and using network slicing to enable the network slice to use resources of two different cellular networks, such as an access network of a first cellular network, and a core network of a second cellular network. Such a slice is referred to herein as a core shared slice, and can be used to enable cellular communications in a situation where, for example, the core network of the first cellular network has become disabled to the extent that it is unable to provide core network functions to a traditional network slice served by the access network of the first cellular network. For example, the core network may become disabled to such an extent due to a natural disaster or a network security breach.

[0026] Figure 1AAn example system according to at least some embodiments of the present invention is illustrated. User equipment UE 101 can access one or more cellular networks. UE 101 may include any suitable user equipment type, such as a mobile phone, a feature phone, a smart phone, a laptop computer, a tablet computer, an IoT node, a machine type communication node, a connected car connection module, or a personal medical device device, as examples. Figure 1A A first cellular network 110 and a second cellular network 120 are illustrated. A cellular network may also be referred to as an operator network, and a cellular network may be identified by a public land mobile network identifier PLMN identifier. Such a PLMN ID may include, for example, a mobile country code MCC and a mobile network code MNC.

[0027] The first cellular network 110 includes an access network 112, which may be, for example, a radio access network RAN. The RAN may include a plurality of base stations, even hundreds or thousands of base stations, although for simplicity, the RAN is not shown in FIG. Figure 1A A single base station is illustrated in FIG. In the case where the access network is not a RAN, it may be based on optical communication or wire-based communication, wherein the access nodes may have, for example, sockets for wire-based communication, and then the network may be referred to as a fixed access network rather than a cellular network. As far as the RAN is concerned, in addition to the base stations, the RAN may also include nodes such as base station controllers or RAN intelligent controllers RIC. Furthermore, the first cellular network 110 includes a transport network 114, which connects the access network 112 to a core network 116 of the first cellular network 110. In principle, the transport network 114 may be any communication device that enables communication of data and control information between the access network 112 and the core network 116.

[0028] The radio access network may be based on a suitable cellular standard, such as Wideband Code Division Multiple Access WCDMA, Long Term Evolution LTE, or fifth generation 5G (also known as New Radio NR). In addition, 5G Advanced may be used. These example cellular standards are managed and published by the Third Generation Partnership Project 3GPP.

[0029] The core network 116 includes a plurality of core network nodes, of which core network nodes 116A, 116B, and 116C are shown as examples. Figure 1AOf course, the number of core network nodes can be more than three. Core network nodes can be logical nodes, meaning that they are arranged to run on one or more physical computing substrates, so that one or more logical core network nodes can run on the same physical computing substrate. Examples of core network nodes include user plane function UPF, network open function NEF, policy control function PCF, unified data management UDM, application function AF, access and mobility function AMF, authentication server function AUSF, session management function SMF, service communication agent SCP, network slice selection function NSSF.

[0030] UPF provides interconnection between mobile infrastructure and data network DN, and provides encapsulation and decapsulation of tunnel protocols. Among other functions, NEF also provides secure network service opening to third-party applications through application programming interface API. PCF can determine the resources and services that can be used to support connected devices. UDM can store subscription information and long-term security credentials of subscribers used for authentication. AF provides service or application related information to network function service consumers. AMF is a control plane function that handles connection and mobility management tasks. The task of AUSF may be to be responsible for the security process of subscriber identity module SIM authentication. SMF can be responsible for interacting with the decoupled data plane; creating, updating and removing protocol data unit PDU sessions; and managing session contexts with user plane functions UPF. For example, SCP can forward service requests to the repository function. Finally, NSSF can be configured to select a network slice instance and determine the allowed network slice selection auxiliary information NSSAI.

[0031] Typically, both cellular networks 110, 120 may be configured to separately provide multiple conventional network slices. In other words, the cellular network 110 may be configured with multiple network slices, each of which is served by the access network 112 and the core network 116 of the cellular network 110. Similarly, the cellular network 120 may be configured with multiple network slices, each of which is served by the access network 122 and the core network 126 of the cellular network 120. A UE (such as UE 101) may access a slice of the cellular network 110 via the access network 112, and the UE may access a slice of the cellular network 120 via the access network 122. Such slices may be used to enhance the utilization of physical hardware in the cellular network and to enable the introduction of separately managed logical networks in the form of slices without installing separate network hardware. The cellular networks 110, 120 may have a roaming agreement so that their respective subscribers can connect via each other's cellular networks. When connecting via a cellular network that is not the UE's home network, the UE is said to be roaming.

[0032] The access network may be configured to provide information to the UE about which network slices are accessible via the access network, for example by broadcasting in their respective cells. In other words, the UE may receive information, such as identifiers, of network slices to which the UE may connect using the access network providing the information. For example, such notification may occur in a system information block (SIB) broadcast by a base station in a cell under its control. The UE may then select from the slices indicated as accessible and request to be registered on the selected slice, or more than one slice.

[0033] exist Figure 1A In the embodiment of the present invention, it is worth noting that the transport network 114 is configured with a communication interface to the core network 126, and the transport network 124 is configured with a communication interface to the core network 116. The core networks 116, 126 may be separately configured with gateways to enable communication between them and other networks. For example, a base station in the RAN may be configured to initialize not only a connection to the core network of the same cellular network that includes the RAN, but also a connection to the core network of another cellular network. For example, (multiple) base stations may be configured to initialize connections to the core networks of those cellular networks in response to a core failure, whose operators have configured means for daring to open core shared slices, as defined below.

[0034] Figure 1B 1 illustrates an example system according to at least some embodiments of the present invention. Figure 1A The same structure in . Figure 1B The situation shown in Figure 1A The difference between the situation in is that the core network 116 of the first cellular network 110 has been disabled, for example, due to a network attack, a natural disaster, or a deliberate shutdown. In this case, the UE can still obtain connectivity via the access network 112 if the network slice configured to be served by the access network resources of the access network 112 and the core network resources of the core network 126 is available. In other words, the network slice can access and use the core network 126 via the access network 112. Further, the network slice is configured to be served by the access network of the first cellular network 110 and the core network of the second cellular network 120. Such a network slice can be referred to as a core shared slice (CSS). In principle, even if the access network 122 is unavailable in addition to the core network 116, the slice served by the access network 112 and the core network 126 can be accessed via the access network 112. The RANs in operation can exchange telemetry data, measurement results, and alarm data to facilitate UE roaming from one RAN to another RAN in a core failure scenario.

[0035] The cellular networks 110, 120 may be configured to implement a CSS as a response to one of their core networks becoming unavailable. For example, the cellular networks may be configured to provision a CSS based on the access network 112 and the core network 126 as a response to the core network 116 becoming unavailable; and / or provision a CSS based on the access network 122 and the core network 116 as a response to the core network 126 becoming unavailable. Thus, the CSS may be run dynamically as a response to a failure condition. In some embodiments, a protocol for generating a CSS may be automatically generated by automatic negotiation between the two cellular networks. The automatic negotiation may determine settings and configurations for the CSS, which may then be automatically created or configured by an administrator. The automatic negotiation may involve a statically or dynamically generated CSS. The automatic negotiation may be performed by an operations support system OSS and / or a base station system BSS of the respective network.

[0036] The subscriber databases of the core network may be implemented in a fail-safe manner, enabling access to them even if their core network becomes unavailable to serve subscribers. For example, such fail-safe operation may include mirroring to another site and / or redundant network access. In some embodiments, the subscriber database from the UE's home network is used for authentication to the CSS even if the core network of the home network is unavailable.

[0037] Figure 2A An example slice identifier according to at least some embodiments of the present invention is illustrated. Network slice selection assistance information NSSAI may be used as a slice identifier. The identifier may include two parts, a slice service type SST 210, and a slice distinguisher SD 220. For example, SST and SD may be concatenated together to form a slice identifier.

[0038] The slice identifier can indicate that the identified slice is a CSS by defining the value of SST as a core shared type slice. For example, the SST can be 8 bits long, which enables the indication of many different slice types. Slice types other than CSS can also be indicated by SST, including high-performance machine type communication slices, mobile broadband type slices, and ultra-low latency communication slices. In these solutions, the UE can be configured to determine that the slice is a CSS by determining that the SST value in the slice identifier is a core shared type value.

[0039] As an alternative or supplement to indicating that a slice is a CSS in the SST, a value or value range for indicating that the slice is a CSS may be reserved in the SD. In these solutions, the UE may be configured to determine that the slice is a CSS by determining that the SD value in the slice identifier is a CSS type value SD, or is included in a CSS type value range in the SD. For example, the SD may be 24 bits long, providing ample opportunity to reserve a range or separate value for indicating a CSS type slice. There may be multiple core shared slice types for different purposes, and corresponding core shared type SD values ​​or value ranges, as will be discussed below.

[0040] In some embodiments, a slice identifier may be able to indicate more than one type of CSS, with different CSSs having different parameters. For example, in a natural disaster scenario, a first CSS type may be reserved for first responders, which allows higher bandwidth to enable video calls for telemedicine purposes, while a second CSS type may be targeted at the general public, allowing lower bandwidth, or even only text messaging communications, to save scarce communications bandwidth. In other words, different CSS types may be configured to allow different kinds of communication types. Communication types may include text only, text and audio, or text, audio, and video.

[0041] CSSs can be deployed statically so that they are already available even when all core networks are available, or they can be deployed dynamically, for example in response to a failure or overload of a core network. The service level agreement SLA and / or service level specification SLS settings of the CSS can be shared among the operators participating in the cellular network. Therefore, they can understand the characteristics of the CSS. For example, the maximum number of UEs is an attribute that can be set for the CSS, and the two operators can set a common value for it. The network slice management function NSMF can determine to deploy network slices served by the access network of the first cellular network and the core network of the second cellular network, and configure the network slices as active in the access network of the first cellular network and the core network of the second cellular network.

[0042] The respective operators of the cellular networks participating in the CSS can configure their core network nodes: UDM, AMF, SMF, UPF and NSSF when they deploy the CSS, so that these core network nodes can identify and support (multiple) CSS slice identifiers during operation. The core network nodes UDM, AMF, SMF, UPF and NSSF can be configured to supply runtime services to the CSS in the following manner. The UDM can access shared subscription data from a shared database. This will allow the UDM to verify the UE subscription from another operator. The AMF can identify the CSS and work with the UDM to allow UEs from other operators to pass the registration. The SMF can establish a packet data unit PDU session and check the subscription data from the shared database. The UPF can host the user plane data connection. To achieve this, the base station in the RAN can be configured to connect to the core network of each cellular network. For example, the base station can be connected to the AMF in each core network of the two participating core networks. The base stations of the RAN can determine whether the core network of their own cellular network becomes unavailable and responsively recommend that the UE use the CSS to access connectivity. Such a recommendation can be provided as a broadcast indication, such as broadcast in (multiple) system information blocks SIB.

[0043] Figure 2B The diagram shows a signaling diagram according to at least some embodiments of the present invention. From left to right on the vertical axis are the management layers MGMT, UDM, AMF, SMF, RAN, and finally UE. Time advances from top to bottom. Figure 2B The signaling flow causes the establishment of CSS.

[0044] In stage 230, the management layer receives a request to deploy a CSS. For example, the request may originate from a human administrator or an automatic trigger, such as a request in response to a core network failure. In stage 240, the management layer deploys the requested CSS type slice based on parameters pre-configured or negotiated in response to the message of stage 230. These parameters may include, for example, slice coverage area (e.g., in cells), maximum number of UEs, isolation requirements, and maximum bandwidth. In stage 250, the management layer configures core network functions (such as AMF, SMF, UPF) to serve the new CSS. For example, this can be triggered by configuring the AMF to configure other core network nodes.

[0045] In stage 260, the management layer configures the RAN of the cellular network to serve the new CSS. This includes providing the slice identifier of the CSS to RAN nodes (such as base stations). In response, in stage 270, the base stations will begin indicating the slice identifier to UEs in cells controlled by these base stations as identifiers of slices accessible via the respective base stations. The provisioning of stage 270 may be broadcast, such as in (multiple) SIBs, where broadcast means a wireless transmission that is not addressed to a specific receiving node.

[0046] In a normal network, the RAN broadcasts the PLMN ID of the cellular network. The core network nodes of the cellular network are associated with the PLMN ID of the cellular network. Therefore, the PLMN ID broadcast by the RAN matches the core network elements used (such as AMF and UDM). In the CSS case, the RAN is connected to two different core networks, and the RAN can broadcast the PLMN IDs of the two cellular networks so that the UE is fully aware of the situation. Two operators may seek to share RAN resources, so the RAN broadcasts the PLMNs it can support, and the UE subscription data identifies the preferred PLMN ID, such as the home PLMN ID.

[0047] Three example scenarios are presented. First, the UE may register in cellular network 120 with the RAN broadcasting the PLMN of cellular network 120. Then, the core network of cellular network 120 fails. The CSS slice here may have core resources from cellular network 110 AMF and cellular network 120 UDM, and use the PLMN ID of cellular network 110 while using the RAN of cellular network 120. It may use cellular network 110 AMF and cellular network 120 UDM.

[0048] Second, the UE may register with the cellular network 120 RAN network, and a base station in the cellular network 120 RAN network broadcasts the PLMN ID of the cellular network 120. Then, a core network failure occurs in the cellular network 120. The RAN may utilize the PLMN ID of the cellular network 110 to switch to the PLMN ID of the broadcast cellular network 110, and the CSS slice may use core resources from both the cellular network 110 and the cellular network 120 UDM.

[0049] Third, the UE may register with the cellular network 120 RAN network, and the base station broadcasts the PLMN ID of the cellular network 120. Then, the core network of the cellular network 120 fails. The CSS may use the service network name SNN for authentication and key generation. The SN name SNN identifies the CSS instance and is defined using the CSS identifier. The CSS identifier may be used by both the cellular network 110 and 120 AMF, and the cellular network 120 UDM. The SN name may be a concatenation of a service code and a service network identifier SN Id. The SNN identifies the service PLMN or an independent NPN.

[0050] Regarding security features, if the 5G authentication algorithm is used, it must be enabled in the UDM. In the 5G AKA authentication algorithm, a new SNN identifier needs to be configured to the UE to access the CSS slice. The SNN is used in 5G as an input to the key generation algorithm. In terms of signaling, the SNN specific to the CSS slice is transmitted in the authentication request from the AMF to the AUSF and in the authentication request from the AUSF to the UDM.

[0051] Figure 3 An example apparatus capable of supporting at least some embodiments of the present invention is illustrated. Illustrated is a device 300, which may include, for example, a mobile communication device such as Figure 1A or Figure 1B UE 101. Alternatively, in applicable parts, device 300 may correspond to an access node (such as a base station), or to a device running a core network node. Included in device 300 is a processor 310, which may include, for example, a single-core or multi-core processor, wherein a single-core processor includes one processing core and a multi-core processor includes more than one processing core. In general, processor 310 may include a control device. Processor 310 may include more than one processor. When processor 310 includes more than one processor, device 300 may be a distributed device in which the processing of tasks occurs in more than one physical unit. Processor 310 may be a control device. The processing core may include, for example, a Cortex-A8 processing core manufactured by ARM Holdings, or a Zen processing core designed by Advanced Micro Devices Corporation. Processor 310 may include at least one Qualcomm Snapdragon and / or Intel Atom processor. Processor 310 may include at least one application-specific integrated circuit ASIC. Processor 310 may include at least one field programmable gate array FPGA. Processor 310 may be a means for performing method steps, such as receiving, determining, providing, and requesting, in device 300. Processor 310 may be configured, at least in part, by computer instructions to perform actions.

[0052] The processor may include circuitry, or be constructed as one or more circuitry configured to perform the stages of the method according to the embodiments described herein. As used in this application, the term "circuitry" may refer to one or more or all of the following: (a) a hardware circuit implementation only, such as an implementation in analog and / or digital circuitry only; and (b) a combination of hardware circuitry and software, such as (as applicable): (i) a combination of (multiple) analog and / or digital hardware circuits with software / firmware, and (ii) any portion of (multiple) hardware processors (including (multiple) digital signal processors), software and (multiple) memories with software, which work together to enable the device (such as a mobile phone or server) to perform various functions; and (c) (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or parts of (multiple) microprocessors, which require software (e.g., firmware) to operate, but the software may not be present when the operation does not require the software.

[0053] This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of only a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. For example, and if applicable to a particular claim element, the term "circuitry" also covers a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0054] Device 300 may include memory 320. Memory 320 may include random access memory and / or permanent memory. Memory 320 may include at least one RAM chip. Memory 320 may be a computer-readable medium. Memory 320 may include, for example, solid-state, magnetic, optical and / or holographic memory. Memory 320 may be at least partially accessible to processor 310. Memory 320 may be at least partially included in processor 310. Memory 320 may be a component for storing information. Memory 320 may include computer instructions, and processor 310 is configured to execute the computer instructions. When computer instructions configured to cause processor 310 to perform certain actions are stored in memory 320, and device 300 as a whole is configured to run under the direction of processor 310 using computer instructions from memory 320, processor 310 and / or at least one processing core thereof may be considered to be configured to perform the certain actions. Memory 320 may be at least partially included in processor 310. Memory 320 may be at least partially located outside device 300, but accessible to device 300. Memory 320 may be transient or non-transient. As used herein, the term "non-transient" is a limitation on the medium itself (ie, tangible, not a signal), not on the persistence of data storage (eg, RAM vs. ROM).

[0055] The device 300 may include a transmitter 330. The device 300 may include a receiver 340. The transmitter 330 and the receiver 340 may be configured to transmit and receive information according to at least one cellular or non-cellular standard, respectively. The transmitter 330 may include more than one transmitter. The receiver 340 may include more than one receiver. For example, the transmitter 330 and / or the receiver 340 may be configured to operate according to the following items: Global System for Mobile Communications GSM, Wideband Code Division Multiple Access WCDMA, 5G, Long Term Evolution LTE, IS-95, Wireless Local Area Network WLAN, Ethernet and / or World Interoperability for Microwave Access WiMAX standards.

[0056] The device 300 may include a near field communication NFC transceiver 350. The NFC transceiver 350 may support at least one NFC technology, such as NFC, Bluetooth, Wibree, or similar technology.

[0057] The device 300 may include a user interface UI 360. The UI 360 may include at least one of a display, a keyboard, a touch screen, a vibrator arranged to signal the user by vibrating the device 300, a speaker, or a microphone. The user can operate the device 300 via the UI 360, for example, to accept an incoming call, or to configure network slicing parameters.

[0058] The device 300 may include, or be arranged to accept, a user identification module 370. The user identification module 370 may include, for example, a subscriber identification module SIM card installable in the device 300. The user identification module 370 may include a subscription identifying a user of the device 300. The user identification module 370 may include cryptographic information that may be used to verify the identity of the user of the device 300 and / or facilitate encryption of transmitted information and billing of the user of the device 300 for communications effected via the device 300.

[0059] The processor 310 may be equipped with a transmitter arranged to output information from the processor 310 to other devices included in the device 300 via electrical leads inside the device 300. Such a transmitter may include a serial bus transmitter arranged to output information to the memory 320 for storage therein, for example, via at least one electrical lead. As an alternative to the serial bus, the transmitter may include a parallel bus transmitter. Similarly, the processor 310 may include a receiver arranged to receive information in the processor 310 from other devices included in the device 300 via electrical leads inside the device 300. Such a receiver may include a serial bus receiver arranged to receive information from the receiver 340, for example, via at least one electrical lead, for processing in the processor 310. As an alternative to the serial bus, the receiver may include a parallel bus receiver.

[0060] The device 300 may include Figure 3 300. For example, where the device 300 comprises a smartphone, it may comprise at least one digital camera. Some devices 300 may comprise a rear camera and a front camera, wherein the rear camera may be intended for digital photography and the front camera for video telephony. The device 300 may comprise a fingerprint sensor arranged to at least partially authenticate a user of the device 300. In some embodiments, the device 300 lacks at least one of the above-mentioned devices. For example, some devices 300 may lack an NFC transceiver 350 and / or a user identification module 370.

[0061] The processor 310, the memory 320, the transmitter 330, the receiver 340, the NFC transceiver 350, the UI 360 and / or the user identification module 370 may be interconnected in a variety of different ways via electrical leads inside the device 300. For example, each of the above devices may be separately connected to a main bus inside the device 300 to allow the devices to exchange information. However, as will be appreciated by those skilled in the art, this is only an example, and depending on the embodiment, various ways of interconnecting at least two of the aforementioned devices may be selected without departing from the scope of the present invention.

[0062] Figure 4The diagram illustrates signaling according to at least some embodiments of the present invention. Figure 2B The vertical axis of Figure 2B As shown in , time progresses from top to bottom.

[0063] In stage 410, the RAN (specifically the base stations therein) broadcasts the PLMN identifier of the cellular network, as well as other indicators. In stage 420, the UE requests to be registered in the cellular network. In stage 430, the AMF configures one (and in some embodiments up to eight) slice identifiers for UE registration access. In response, the UE selects a PLMN or a non-public network NPN for registration in stage 440. In stage 450, based on the selection, the UE requests registration via the RAN. The request for the device to be registered in stage 450 also includes the slice identifier that the UE has selected in stage 440. For example, this can be a CSS. In fact, in the case where the RAN knows that the core network of the cellular network has become unavailable, the RAN can provide the UE with a recommendation to select a CSS.

[0064] In stage 460, the AMF checks whether the slice identifier provided by the UE is valid, and optionally determines whether allowing the UE to join the CSS would violate the maximum number of UEs limit of the CSS. If this is not the case, processing proceeds to stage 470. In stage 470, the AMF obtains subscription data from the UDM. For example, this can be the UDM of the failed core network of the UE's home cellular network. This is possible in the case where subscriber information is stored redundantly to make the subscriber repository of the home network core network resistant to core network failures.

[0065] Subsequently, in stage 480, the AMF obtains the network slice instance NSI identifier and the allowed slice identifiers from the NSSF. In stage 490, a Registration Accept message is provided to the UE via the RAN. The Registration Accept may include an indication of the slice identifiers to which the UE has been admitted, and any mobility restrictions that may be in effect. Likewise, in stage 4100, the AMF provides the allowed slice identifiers to the RAN.

[0066] In stage 4110, the UE requests a PDU session establishment from the RAN. A CSS slice identifier may be provided in this request. In stage 4120, the RAN responsively requests a PDU session establishment from the AMF, which responsively obtains a list of SMF addresses for a given NSI and selects an SMF for the PDU session. In stage 4130, the AMF requests a PDU session creation from the selected SMF, which responsively may check, for example, subscription data, policy and load information, and create a PDU context for the PDU session. In stage 4140, the SMF sends a PDU session establishment accept message to the AMF, which includes a slice identifier of the CSS. Similarly, stage 4150 includes the SMF sending a PDU session establishment accept with a CSS identifier to the UE via the RAN. Subsequently, for example, the UE may request a user plane connection establishment from the UPF.

[0067] Figure 5 is a flow chart of a method according to at least some embodiments of the present invention. The various stages of the method shown may be performed in the UE 101, or in a control device configured to control its functions (when installed therein).

[0068] Stage 510 includes: receiving, in the device, from an access network included in the first cellular network, a first network slice identifier of a first network slice accessible via the access network. Stage 520 includes: determining, based on the first network slice identifier, that the first network slice is partially served in a core network of the second cellular network. Finally, stage 530 includes: providing a request to the access network that the device be registered on the first network slice.

[0069] It should be understood that the disclosed embodiments of the present invention are not limited to the specific structures, processing steps, or materials disclosed herein, but can be extended to equivalents thereof that will be recognized by those of ordinary skill in the relevant art. It should also be understood that the terms used herein are only used for the purpose of describing specific embodiments and are not intended to be limiting.

[0070] References to one embodiment or an embodiment throughout the specification mean that the particular features, structures, characteristics described in conjunction with that embodiment are included in at least one embodiment of the present invention. Therefore, the phrases "in one embodiment" or "in an embodiment" appearing in various places throughout the specification do not necessarily all refer to the same embodiment. When terms (such as, for example, approximately or substantially) are used to reference values, the exact values ​​are also disclosed.

[0071] As used herein, for convenience, multiple projects, structural elements, constituent elements and / or materials can be presented in a public list. However, these lists should be interpreted as each member in the list is individually identified as a separate and unique member. Therefore, in the absence of contrary instructions, any individual member in the list should not be interpreted as the de facto equivalent of any other member in the same list based solely on its presentation in the public group. In addition, various embodiments of the present invention and examples, and the alternatives of its various components can be mentioned in this article. It should be understood that such embodiments, examples and alternatives should not be interpreted as de facto equivalents to each other, but should be considered as separate and autonomous representations of the present invention.

[0072] In addition, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. In the foregoing description, many specific details (such as examples of length, width, shape, etc.) are provided to provide a thorough understanding of embodiments of the present invention. However, those skilled in the relevant art will recognize that the present invention can be put into practice without one or more specific details, or put into practice using other methods, components, materials, etc. In other cases, known structures, materials, or operations are not shown or described in detail to avoid blurring various aspects of the present invention.

[0073] Although the foregoing examples illustrate the principles of the present invention in one or more specific applications, it will be apparent to those skilled in the art that various modifications may be made to the details of form, use, and implementation without exercising creative ability and without departing from the principles and concepts of the present invention. Therefore, it is not intended that the present invention be limited except by the claims set forth below.

[0074] The verbs "to comprise" and "to include" are used in this document as open limitations, which neither exclude nor require the existence of features not yet recited. Unless explicitly stated otherwise, the features recited in the dependent claims may be freely combined with each other. Furthermore, it should be understood that the use of "a" or "an" (i.e. the singular) throughout this document does not exclude the plural.

[0075] As used herein, “at least one of: ” and “at least one of ” and similar expressions (wherein a list of two or more elements is connected by “and” or “or”) mean at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0076] Industrial Applications

[0077] At least some embodiments of the present invention find industrial application in operating cellular communication networks.

[0078] List of abbreviations

[0079] CSS Core Shared Slices

[0080] SST Slice Service Type

[0081] SD Slice Specifier Reference numerals list

[0082]

Claims

1. A device for slicing a communication network, comprising: at least one processing core and at least one memory storing instructions that, when executed by the at least one processing core, cause the apparatus to at least: - receiving, from an access network included in the first cellular network, a first network slice identifier of a first network slice accessible via the access network; - based on the first network slice identifier, determining that the first network slice is partially served in a core network of a second cellular network, and -Providing a request to the access network that the device be registered on the first network slice.

2. The apparatus according to claim 1, wherein the apparatus is configured to: Based on determining that the first network slice identifier S-NSSAI includes a slice service type SST or a slice differentiator SD, it is determined that the first network slice is at least partially served in the core network of a second cellular network, and the slice service type SST or the slice differentiator SD indicates that the first network slice uses core network resources and access network resources of different cellular networks.

3. The apparatus according to claim 1 or 2, wherein the apparatus is configured to: While the device maintains a registration state on the first network slice, request the device to maintain the registration state on a second network slice from the access network.

4. The apparatus according to claim 1 or 2, wherein the apparatus is configured to: Providing the access request is performed in response to determining that the access network sends an indication to the apparatus.

5. An apparatus according to claim 4, wherein the indication indicates that at least one network slice supported by the access network has become unavailable.

6. An apparatus according to claim 5, wherein the at least one network slice that has become unavailable is configured to use core network resources of the first cellular network.

7. A method for slicing a communication network, comprising: - In the device, receiving, from an access network included in the first cellular network, a first network slice identifier of a first network slice accessible via the access network; - based on the first network slice identifier, determining that the first network slice is partially served in a core network of a second cellular network, and -Providing a request to the access network that the device be registered on the first network slice.

8. The method according to claim 7, wherein the method comprises: Based on determining that the first network slice identifier S-NSSAI includes a slice service type SST or a slice differentiator SD, it is determined that the first network slice is at least partially served in the core network of a second cellular network, and the slice service type SST or the slice differentiator SD indicates that the first network slice uses core network resources and access network resources of different cellular networks.

9. The method according to claim 7 or 8, wherein the method comprises: While the device maintains a registration state on the first network slice, request the device to maintain the registration state on a second network slice from the access network.

10. The method according to claim 7 or 8, wherein the method comprises: Providing the access request is performed in response to determining that the access network sends an indication to the apparatus.

11. The method of claim 10, wherein the indication indicates that at least one network slice supported by the access network has become unavailable.

12. The method of claim 11, wherein the at least one network slice that has become unavailable is configured to use core network resources of the first cellular network.

13. A non-transitory computer readable medium having a set of computer readable instructions stored thereon, which, when executed by at least one processor, causes an apparatus for slicing a communication network to at least: - receiving, from an access network included in the first cellular network, a first network slice identifier of a first network slice accessible via the access network; - based on the first network slice identifier, determining that the first network slice is partially served in a core network of a second cellular network, and -Providing a request to the access network that the device be registered on the first network slice.

Images