Wireless terminal, base station, and method

Abstract

To provide a wireless terminal and a base station for a communication system that supports network slicing.SOLUTION: In a mobile telecommunication system 1, a user equipment 3 includes means for receiving system information including information associated with supported slice types, and means for performing cell selection or initial access procedures for slices indicated in the information. The slice types include operator common types and operator specific types. The operator common types include enhanced mobile broadband (eMBB), critical communication for high reliability and low latency, and large-scale communication for Internet of Things (IoT).SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a radio access network in a cellular or wireless telecommunications network, and more particularly to the sharing of a radio access network by multiple operators, although not exclusively. The present invention is particularly, but not exclusively, related to radio telecommunications networks implemented in accordance with various standards defined by the Third Generation Partnership Project (3GPP). For example, the present invention relates to Long Term Evolution (LTE) networks, LTE-Advanced (LTE-A) networks, related LTE / LTE-A extensions and developments, and more recently developed communication technologies beyond LTE / LTE-A, such as those referred to as "5G", "Next Generation" (NG), or "New Radio" (NR).

Background Art

[0002] Deployment scenarios for radio access network (RAN) sharing are known, and methods and capabilities for facilitating the implementation of these scenarios have been introduced in the standards since Release 5 of the Third Generation Partnership Project (3GPP).

[0003] Traditionally, RAN sharing provides a way for network operators (network operators, service providers) to reduce their capital investment requirements and / or expand the areas covered by cellular communication services when setting up a wireless telecommunications network. Each operator does not need to provide their own base stations and related equipment for each cell of the network, and an operator sharing another operator's RAN can provide their services in the areas provided by other operators without investing in their own base stations at that location.

[0004] Also, by reducing the number of base stations that need to be provided and operated (reducing CAPEX), the sharing operator can reduce the ongoing operating costs (OPEX). In fact, since each base station may consume a large amount of power during operation, the power requirement can be significantly reduced by reducing the number of base stations in operation, which can also be regarded as environmentally friendly.

[0005] Typically, RAN sharing by operators is a fixed long-term contract for each operator to obtain some access to the RAN of other operators. RAN sharing is particularly advantageous in areas where operators have underutilized cell capacity because it can share this spare capacity without affecting the ongoing service provision of the original operator. Furthermore, RAN sharing eliminates the need for each operator to provide expensive capacity in remote areas that are likely to be underutilized, and may be useful in some countries to ensure that the services provided by operators reach a certain percentage of the population, which can be specified by license conditions.

[0006] The terms "5G" and "New Radio" (NR) refer to evolving communication technologies expected to support various applications and services such as Machine Type Communications (MTC), Internet of Things (IoT) communications, vehicle communications and autonomous vehicles (V2V / V2X), high-resolution video streaming, and smart city services. Thus, 5G / NR technologies are expected to enable network access to vertical markets, provide networking services to third parties, and support network sharing to create new business opportunities. Base stations in 5G / NR communication systems are generally referred to as "NR-BS" (New Radio Base Station) or "gNB", and it is understood that they may alternatively be referred to using the term eNB (or 5G / NR eNB) typically associated with LTE base stations.

[0007] In recent years, it has been proposed that the functions of a gNB (referred to herein as "distributed" gNB) be split between one or more Distributed Units (DUs) and a Central Unit (CU), where typically the CU performs higher-level functions to communicate with the next-generation core network (it is understood that either the term "core network" or "core" may be used by those skilled in the art), and the DU performs lower-level functions to communicate via a radio interface with User Equipment (UE) in the vicinity (i.e., within the cell served by the gNB).

[0008] To support such diverse applications and services, mobile network operators must meet the diverse and often conflicting requirements of these applications and handle large amounts of data traffic. For example, some of these applications may have relatively loose service quality (QoS) / quality of experience (QoE) requirements, while some applications may have relatively strict QoS / QoE requirements (e.g., high bandwidth and / or low latency).

[0009] Since it is expensive and not practical to provide dedicated network infrastructure for each type of service or application, network virtualization and "network slicing" are regarded as flexible and cost-effective ways to support and accommodate heterogeneous applications with diverse requirements on a common network infrastructure. Such network slicing is described, for example, in Non-Patent Document 1. Substantially, network slicing represents a logical network with respect to a specific service level agreement (SLA) for a specific tenant. In fact, each slice represents a specific system operation (or a series of operations). Tenants of a network (e.g., a public land mobile network (PLMN)) are wholesale customers of the network. For example, a tenant may be a large enterprise, an intermediary that requires the PLMN to provide access to at least a predefined set of resources, or a specific policy for handling slice subscribers during congestion. Examples of tenants include public safety agencies. Also, tenants may have application-specific requirements. For example, in an enterprise deployment, an enterprise may have a series of manufacturing site devices in a factory and devices related to operations outside the manufacturing site. The enterprise may have a policy of allocating at least 60% of the resources to the operation of the manufacturing site during congestion (regardless of whether it is within the radio access network or the core network), but not always separating the resources.

[0010] More specifically, a network slice (e.g., a "5G slice") can support a communication service of a specific connection type in a specific way of processing the control plane and user plane for that service. In practice, a slice can include a plurality of network functions combined together for a specific use case, technical and / or business model, and settings of a specific radio access technology (RAT). Slices do not necessarily have to include all the same functions, and it is possible that one or more slices lack some functions that are considered essential today. Essentially, the intention is for the slice to provide only the traffic processing required for a given use case, thereby avoiding other unnecessary functions.

[0011] As an example, multiple slices operating simultaneously on the same infrastructure include slices for typical smartphone use, set up by establishing a full-fledged smartphone-specific function distributed across the network. Also, slices supporting automotive use cases can provide all the necessary (and potentially dedicated) functions, including vertical applications required as a result of latency constraints, even when security, reliability, and latency are important, and can be realized at cloud edge nodes. Another slice can support Massive Machine Type devices (IoT devices, e.g., sensors) by providing a basic control plane function configured to use contention-based resource access, for example, omitting any mobility functions. To handle unknown use cases and traffic, there can be other dedicated slices operating in parallel and potentially a general-purpose slice providing basic best-effort connectivity.

[0012] Each network slice is defined by its respective Network Slice Template (NST), which is a logical representation of the network functions and corresponding resource requirements necessary to provide the required telecommunications services and network capabilities. Each template is used to implement an "instance" corresponding to each network slice, called a Network Slice Instance (NSI).

[0013] Therefore, from the perspective of the UE, network slices achieve many beneficial purposes as follows: Provide a specific system operation tailored to specific application needs to a given UE from the perspective of specific control plane operations (e.g., the UE may or may not request mobile terminating procedures, optimal operation of massive machine type communication (MTC), critical communications (CriC), etc.) and user plane operations (e.g., the UE may require a slice that supports header compression); Provide the UE with access to resources, application domains, or tenants assigned to a specific service (e.g., the minimum level of guaranteed resources or total number of subscribers allowed to access the service at any given time).

[0014] So far, in order to support network slicing in the RAN, it is considered necessary to apply many important principles. First of all, for example, the RAN needs to recognize slices. Specifically, the RAN needs to support the differentiated processing of different network slices preconfigured by the operator. In addition, the RAN may support the selection of the RAN part of the network slice by an identifier such as a "slice ID" provided by the user equipment (UE). This identifier clearly identifies one of the network slices (or associated NST) preconfigured in the public land mobile network (PLMN). Similarly, the RAN may support resource management between slices (for example, the implementation of policies between slices according to service level agreements), the differentiation of QoS within slices, and / or the resource separation between slices. In addition, the RAN may also support the RAN selection of core network (CN) entities for the initial routing of uplink messages based on, for example, the received slice ID and the mapping (CN entity, supported slice) in the RAN node. If the slice ID is not received, the RAN may select a CN entity based on a function such as the NAS (Non-Access Stratum) node selection function (NNSF (NAS Node Selection Function)), for example, based on the UE temporary ID.

[0015] Since some slices may be available only in a part of the network, the recognition of the slices supported by the base stations in the cells of the adjacent base stations can be beneficial for the inter-frequency mobility of UEs in the connected mode. It is assumed that the slice configuration does not change within the registration area of the UE.

[0016] The RAN and CN are responsible for processing service requests for slices that may or may not be available within a given area. The permission or rejection of access to a slice may depend on factors such as the support for such a slice, the availability of resources, and the support for services requested by other slices.

Prior Art Documents

Non-Patent Documents

[0017]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0018] However, the inventors have found that some problems may occur when not all slice types are available at each base station (e.g., due to local load or hardware limitations).

[0019] For example, in a sliced RAN, a Mobility Management Entity (MME) or a similar NG-core network function may inappropriately set the paging / tracking area for a UE to include cells of a base station where the slice type supported by a given UE is not available, thereby making paging inefficient. Similarly, the MME (or a similar NG-core network function) may inappropriately set roaming and access restrictions.

[0020] Also, in connected mode mobility, following the decision to hand over a UE to a target base station simply based on signal strength, the target base station may attempt to use core network control plane and / or user plane functions that are inappropriate for the slice currently being used by the UE. Further, for on-demand system information at the target base station, all of the system information required by the UE to support that slice may not be available.

[0021] There are also many other problems that have not yet been considered or recognized that need to be addressed to provide a functional slicing mechanism.

[0022] Therefore, it is understood that there are many problems that need to be addressed in order to make significant progress towards providing a fully functional and efficient slicing mechanism.

[0023] The present invention aims to provide an apparatus and a related method that at least partially contribute to the provision of a practical slicing mechanism by addressing one or more of these problems.

[0024] Despite the above-recognized problems, the inventors have found that progress can be made towards a practical slicing mechanism by addressing some problems that have not yet been considered.

Means for Solving the Problems

[0025] In one aspect of the present invention, there is provided a communication apparatus for a communication system that supports network slicing, the communication apparatus comprising a controller and a transceiver, the controller being configured to generate a message including slice support information indicating at least one slice support capability of the communication apparatus and to control the transceiver to transmit the message to a node of a core network.

[0026] In another aspect of the present invention, there is provided a core node for a core network of a communication system that supports network slicing, the core node comprising a controller and a transceiver, wherein the controller controls the transceiver to receive from a communication device a message including slice support information indicating at least one slice support capability of the communication device, and is configured to set information stored in the core node based on the slice support information.

[0027] In another aspect of the present invention, there is provided a communication device for a communication system that supports network slicing, the communication device comprising a controller and a transceiver, wherein the controller controls the transceiver to receive from another communication device a message including slice support information related to at least one slice supported by the at least one communication device as part of a handover procedure for the at least one communication device, and is configured to set the communication device to support the communication of the at least one communication device based on the slice support information by at least one of selection of an appropriate slice-specific core network function based on the slice support information and activation of slice-specific on-demand system information based on the slice support information.

[0028] In another aspect of the present invention, there is provided a communication device for a communication system that supports network slicing, the communication device comprising a controller and a transceiver, wherein the controller transmits a message to set the communication device to perform measurements on at least one neighboring cell of another communication device that supports a slice used by the communication device, controls the transceiver to receive at least one associated measurement report from the communication device, and is configured to select a target for handover based on the at least one associated measurement report.

[0029] In another aspect of the present invention, there is provided a communication device for a communication system supporting network slicing, comprising a controller and a transceiver. The controller controls the transceiver to receive, from another communication device, a message including slice support information related to at least one slice supported by the at least one communication device, as part of a procedure for setting up dual connectivity for the at least one communication device, and is configured to set up the communication device for dual connectivity based on the slice support information.

[0030] In another aspect of the present invention, there is provided a communication device for a communication system supporting network slicing, comprising a controller and a transceiver. The controller controls the transceiver to receive, from at least one communication device, a connection re-establishment message including slice support information related to at least one slice supported by the at least one communication device, as part of a connection re-establishment procedure, and is configured to set up the communication device to support re-establishment of a connection with the communication device based on the slice support information.

[0031] In another aspect of the present invention, there is provided a communication device for a communication system supporting network slicing, comprising a controller and a transceiver. The controller is configured to control the transceiver to transmit, to a communication device, a connection re-establishment message including slice support information related to at least one slice supported by the communication device, as part of a connection re-establishment procedure.

[0032] In another aspect of the present invention, there is provided a communication device for a communication system that supports network slicing, the communication device comprising a controller and a transceiver, the controller being configured to control the transceiver to receive from a core node at least one message for at least one communication device, the at least one message including slice support information related to at least one slice used by the at least one communication device, and to configure the communication device to support communication of the at least one communication device based on the slice support information.

[0033] In another aspect of the present invention, there is provided a method executed by a communication device in a communication system, the method comprising generating a message including slice support information indicating at least one slice support capability of the communication device, and transmitting the message to a node of a core network.

[0034] In another aspect of the present invention, there is provided a method executed by a core node in a core network of a communication system that supports network slicing, the method comprising receiving from a communication device a message including slice support information indicating at least one slice support capability of the communication device, and configuring information stored in the core node based on the slice support information.

[0035] In another aspect of the present invention, there is provided a method performed by a communication device in a communication system supporting network slicing, the method including receiving, from another communication device, a message including slice support information related to at least one slice supported by the at least one communication device as part of a handover procedure for the at least one communication device, and configuring the communication device to support communication of the at least one communication device based on the slice support information by performing at least one of selection of an appropriate slice-specific core network function based on the slice support information and activation of slice-specific on-demand system information based on the slice support information.

[0036] In another aspect of the present invention, there is provided a method performed by a communication device in a communication system supporting network slicing, the method including transmitting a message for configuring a communication device to perform measurements on at least one neighboring cell of at least one other communication device supporting a slice used by the communication device, receiving at least one associated measurement report from the communication device, and selecting a target for handover based on the at least one associated measurement report.

[0037] In another aspect of the present invention, there is provided a method for a communication device in a communication system supporting network slicing, the method including receiving, from another communication device, a message including slice support information related to at least one slice supported by the at least one communication device as part of a procedure for configuring dual connectivity for the at least one communication device, and configuring the communication device for dual connectivity based on the slice support information.

[0038] In another aspect of the present invention, there is provided a method performed by a communication device in a communication system supporting network slicing, the method comprising receiving, from at least one communication device, a connection re-establishment message including slice support information related to at least one slice supported by the at least one communication device as part of a connection re-establishment procedure, and configuring the communication device to support re-establishment of a connection with the communication device based on the slice support information.

[0039] In another aspect of the present invention, there is provided a method performed by a communication device in a communication system supporting network slicing, the method comprising transmitting, to a communication apparatus, a connection re-establishment message including slice support information related to at least one slice supported by the communication device as part of a connection re-establishment procedure.

[0040] In another aspect of the present invention, there is provided a method performed by a communication device in a communication system supporting network slicing, the method comprising receiving, from a core node, at least one message for at least one communication device, the at least one message including slice support information related to at least one slice used by the at least one communication device, and configuring the communication device to support communication of the at least one communication device based on the slice support information.

[0041] Aspects of the present invention extend to computer program products, such as computer-readable storage media storing operational instructions for programming a corresponding system, method, and programmable processor or system to perform the methods described in the above aspects and the realizable methods described above or in the claims, and / or for programming a computer appropriately adapted to provide an apparatus as claimed in any of the claims.

[0042] Each feature disclosed in this specification (including the terms in the claims) and / or shown in the drawings can be incorporated into the present invention independently (or in combination) with other disclosed and / or shown features. In particular, without limitation, any feature of any claim dependent on a particular independent claim can be introduced into that independent claim in any combination or individually.

[0043] Although specific hardware devices having specific physical structures (e.g., a controller and transceiver circuits) are disclosed for performing the various procedures described herein, each step of the methods described herein and / or forming part of the claims can be implemented by any suitable means for performing that step. Accordingly, each method aspect of the present invention has a corresponding apparatus aspect that includes the respective means for performing each step of that method aspect.

[0044] Hereinafter, embodiments of the present invention will be described by way of example with reference to the following accompanying drawings.

Brief Description of the Drawings

[0045]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

DETAILED DESCRIPTION OF THE INVENTION

[0046] Summary Figure 1 schematically shows a mobile (cellular) telecommunications system 1 in which a plurality of network slices 2 with different configurations are defined. Through the mobile telecommunications system 1, a network operator provides cellular services to different tenants based on their service level agreements (SLAs). It is understood that with the tenant concept, the network operator can distinguish the requirements of different customers and provide customized services using one or more slices. In this example, the mobile telecommunications system 1 operates as a next-generation (“5G”) system, but it is understood that many of the features described with reference to this example are widely applicable to other communication systems. The base stations 5 each form a part of the associated radio access network (RAN) to enable the user equipment (UE) 3 (such as mobile phones / smartphones 3-1, 3-2, 3-3, MTC / IoT devices (not shown), and / or other mobile or fixed-position communication devices) to connect to their network and receive one or more associated services.

[0047] Figure 1 shows what appears to be a “whole network” slice, but it is understood that this is for illustrative purposes only. The core can have its own slice and can have a radio access network RAN. Similarly, the control plane (CP (Control Plane)) and the user plane (UP (User Plane)) can have completely different slices. Depending on standardization and the policies of the cellular operator, the mapping from the RAN slice to the core slice may vary.

[0048] In this example, each UE 3 has its communication services provided by at least one tenant that has its own unique tenant ID. Thus, with the tenant and slice concepts, the network operator can provide communication services using one or more types of network slices 2 according to the communication requirements of each tenant.

[0049] The Multi-Dimensional Descriptor (MDD) is set in each UE3 and represents at least the tenant ID of the tenant to which it belongs and the service descriptor / slice type that they have the right to use (which is partially managed by the tenant ID). The service descriptor / slice type may include standardized values and / or operator-specific values. The MDD is essentially a matrix that indicates, in each of its rows, the slices 2 that the UE3 can access or request an address for (thus, if there is a single slice, the MDD is a vector). The rows in the MDD are called MDD vectors. The MDD vector has the purpose of combining the identification of a tenant (identified by the tenant ID component) and the network operation for the target network service (identified by the slice type component. For example, enhanced Mobile Broadband (eMBB) service, Critical Communications (CriC), massive Machine Type Communications (mMTC), or other operations that can be operator-specific).

[0050] Services are provided to each tenant's respective UE3 via one or more base stations 5-1, 5-2 of the telecommunication system 1. As understood by those skilled in the art, each base station 5 operates one or more cells 6-1, 6-2, 6-3 that can communicate between the base station 5 and the UE3 using an appropriate radio access technology such as, for example, Evolved Universal Terrestrial Radio Access (E-UTRA) technology.

[0051] Each UE3 may provide respective Network Slice Selection Assistance Information (NSSAI) consisting of a set of parameters such as network slice type ID, service type, and UE capabilities to the network (i.e., via gNB5) to permit selection of an appropriate set of the RAN (e.g., base station 5) and the core network part (e.g., appropriate core network function 7) of the network slice instance (NSI) for that UE.

[0052] The base station is configured to operate according to next-generation (5G) standards and, in this example, includes non-distributed gNB5-1 and distributed gNB5-2. As seen in FIG. 1, the distributed gNB5-2 in this example includes a central unit (CU) 5-2b and a plurality of distributed units (DUs) 5-2a each providing service to at least one associated cell.

[0053] Although a base station of the "gNB" type is described in this example, it is understood that many of its functions can be extended to other base stations or similar devices to provide wireless access to UEs3 such as mobile (cellular) phones / smartphones, MTC / IoT devices, and / or other mobile or fixed-location communication devices.

[0054] gNB 5 is connected via a related core network having a plurality of logical core network nodes 7 for supporting communications in the telecommunication system 1. The core network nodes 7 in this example implement, among other functions, at least one control plane (CP) function 7-1, at least one user plane (UP) function 7-2, at least one network slice selection function (SSF) 7-4, and several other functions 7-n such as an access management function (AMF) and a session management function (SMF). Also, in this example, one of the core network nodes 7 may implement a mobility management function 7-3 that provides a mobility management function corresponding to, for example, an LTE mobility management entity (MME). Note that although separate functions with specific names are described for illustrative purposes, the corresponding functions may be implemented separately or in combination by one or more appropriate core network nodes 7 that use dedicated circuitry and / or software instructions for controlling the associated processor. For example, the slice selection function 7-4 may be implemented as part of any appropriate core network node 7 such as the core node 7 that implements the mobility management function 7-3.

[0055] In this example, the user plane function 7-2 comprises at least one, typically multiple, so-called terminating user plane functions (TUPF) to terminate user plane traffic and interface with the data network. As additional background art, 3GPP technical report (TR) 23.799 V0.7.0 introduces the concept of a TUPF which is a logical network node substantially coupled to one or more cells (gNB). It is assumed that an appropriate protocol data unit (PDU) session is provided between the TUPF and each connected UE3 (i.e., the UE served by the base station coupled to that TUPF).

[0056] To enable a particular UE3 to know as early as possible whether the tenant ID and / or slice type permitted by that UE are supported within a particular cell, information identifying the supported tenant ID, slice type (per tenant ID), and TUPF7-2 is broadcast by the corresponding gNB5 in system information (e.g., system information block "SIB" such as LTE's SIB2). The UE3 can then listen for the relevant SIB for the purpose of checking whether a given cell supports a particular desired tenant ID, slice type per tenant ID, and / or TUPF. Support for a particular desired tenant ID, slice type per tenant ID, and / or TUPF can be checked based on MDD, UE capabilities, and / or USIM configuration. When the UE3 identifies, based on the system information broadcast by the gNB5, that its desired tenant ID, slice type per tenant ID, and TUPF are supported by cell 6, the UE3 can then camp on cell 6 for any of a variety of different purposes (e.g., for an initial access procedure or to request a service).

[0057] Therefore, gNB5 can dynamically change the tenant ID, slice type per tenant ID, and / or TUPF supported in a specific cell 6 (e.g., based on operator requirements, demand, etc.), and UE3 can identify whether its permitted tenant ID and / or slice type is supported within that cell 6.

[0058] System Information (SI) includes minimum system information (e.g., a subset of system information blocks (SIBs) such as Master Information Block (MIB), SIB1, SIB2, and SIB14) that carries a "minimum" set of information elements (e.g., elements necessary for cell selection support, acquisition of other system information (OSI), or access to the cell). System information also includes OSI that includes all system information within other SIBs that are normally available in a telecommunication system. The minimum system information is transmitted periodically, while OSI may be broadcast periodically or broadcast / unicast on demand.

[0059] Preferably, in an exemplary method described in more detail later, the telecommunication system shown in FIG. 1 provides some procedures that can be executed between a base station 5 of the type shown in the telecommunication system of FIG. 1 and a core network 7 to support paging areas and / or efficient configuration of roaming and access restrictions.

[0060] Preferably, in an exemplary manner described in more detail later, the telecommunications system shown in FIG. 1 also provides several procedures that can be executed between different types of base stations 5 shown in the telecommunications system of FIG. 1 for connected mode mobility, setup of dual mode connectivity, and support of connection reestablishment, in the context of network slicing.

[0061] Preferably, in an exemplary manner described in more detail later, the telecommunications system shown in FIG. 1 also provides several procedures that can be executed between a base station of the type shown in the telecommunications system of FIG. 1 and the core network 7 to support setup and modification of UE context, connected mode mobility, efficient paging, and slice selection.

[0062] User Equipment FIG. 2 is a block diagram showing the main components of a user equipment 3 (such as a mobile phone) shown in FIG. 1. As shown, the UE 3 has a transceiver circuit 231 operable to transmit signals to and receive signals from a base station 5 (such as a gNB, for example) via one or more antennas 233. Although not necessarily shown in FIG. 2, the UE 3 may of course have all the normal functionality of a conventional UE 3 (such as a user interface 235, etc.), which may be provided by any one or any combination of hardware, software, and firmware as required. The UE 3 has a controller 237 for controlling the operation of the user equipment 3.

[0063] The controller 237 is connected to a memory 239 and coupled to the transceiver circuit 231. For example, software may be pre-installed in the memory 239 and / or downloaded via a telecommunications network or from a removable data storage device (RMD).

[0064] In this example, the controller 237 is configured to control the overall operation of the UE 3 by program instructions or software instructions stored in the memory 239. As shown, these software instructions include, among other things, an operating system 241, a communication control module 243, a slice / tenant information module 245, a radio resource control (RRC) entity 247, a media access control (MAC) entity 249, a physical layer (PHY) entity 251, a non-access stratum (NAS) module 252, and a measurement module 253.

[0065] The memory 239 also includes configuration information 255 used by the UE 3 for communication and control purposes. Typically, this information includes, among other things, a multi-dimensional descriptor (MDD) (if set for the UE 3), information identifying the communication and other capabilities of the UE, and information identifying how to configure a subscriber identity module (SIM), such as a universal SIM (USIM), for example.

[0066] The communication control module 243 is operable to control the communication between the UE 3 and the base station 5 shown in FIG. 1. The communication control module 243 also controls separate flows of uplink data and control data to be transmitted to the base station 5, and controls the reception of downlink data and control data transmitted by the base station 5. The communication control module 243 is responsible for, for example, some management of the UE in idle and connected mode procedures such as cell (re)selection, camping on a cell, listening for system information, and random access channel (RACH) procedures.

[0067] The slice / tenant information module 245 is responsible for managing and maintaining information that identifies the tenant to which the UE 3 belongs and information that identifies the slice / slice type that can be used by the UE 3.

[0068] The RRC entity 247 is responsible for controlling the RRC layer function of the UE 3 (under the overall control of the communication control module 243). The MAC entity 249 is responsible for controlling the MAC layer function of the UE 3 (under the overall control of the communication control module 243). The PHY entity 251 is responsible for controlling the physical layer function of the UE 3 (under the overall control of the communication control module 243). The NAS module 252 is responsible for controlling the NAS function of the UE 3 (under the overall control of the communication control module 243).

[0069] The measurement module 253 processes the execution of measurements of the communication state (such as the power and quality of the received signal) in the serving cell and adjacent cells (for example, based on measurement configurations and control information received from the base station 5). The measurement module 253 also generates a measurement report associated for transmission to the base station 5.

[0070] Non-Distributed Base Station (gNB) FIG. 3 is a block diagram showing the main components of a non - distributed gNB 5 - 1 of the type shown in FIG. 1. As shown, the gNB 5 - 1 is operable to transmit signals to and receive signals from the UE 3 via one or more antennas 353, and to transmit signals to and receive signals from the functions of the core network 7 and / or other gNBs 5 via a network interface 355, and includes a transceiver circuit 351. The network interface 355 typically includes an interface such as S1 for communicating with the core network and a gNB - to - gNB interface (e.g., such as X2) for communicating with other gNBs. A controller 357 controls the operation of the transceiver circuit 351 according to software stored in a memory 359. The software includes, among other things, an operating system 361, a communication control module 363, and a network slice / tenant management module 364.

[0071] The communication control module 363 is operable to control the communication between gNB 5-1 and UE 3, and between gNB 5-1 and other network entities connected thereto. The communication control module 363 also controls separate flows of uplink and downlink user traffic and control data received from and transmitted to communication devices served by gNB 5-1, including, for example, control data for managing the operation of UE 3. The communication control module 363 is responsible for controlling procedures such as, for example, measurement control / configuration information, communication of system information (on-demand and periodic), the gNB part in random access channel (RACH) procedures. The communication control module 363 is also responsible for managing the gNB part in setting up, configuring, and reconfiguring the gNB-to-gNB interface with adjacent gNBs, and in setting up, configuring, and reconfiguring the gNB-to-core network interface with core network node 7 (such as mobility management function 7-3). The communication control module 363 is also responsible for managing the gNB part in handovers (both gNB-to-gNB interface-based and gNB-to-core network interface-based), including, for example, handover decision, target selection, etc. (when applicable). The communication control module 363 is also responsible for managing the gNB part in UE context setup and change procedures, dual connectivity (such as operation as master or secondary gNB, addition and management of secondary gNBs, etc.), connection (re)establishment procedures with UE 3, and paging procedures.

[0072] The network slice / tenant management module 364 is operable to store and manage configuration data 365 for defining various radio access network (RAN) slices available via gNB 5-1 for each service / tenant.

[0073] Distributed Base Station (gNB) FIG. 4 is a block diagram showing the main components of the distributed gNB 5-2 of the type shown in FIG. 1. As shown, the gNB 5-2 includes a distributed unit 5-2a and a central unit 5-2b. Each unit 5-2a, 5-2b includes transceiver circuits 451a, 451b, respectively. The transceiver circuit 451a of the distributed unit 5-2a is operable to transmit signals to and receive signals from the UE 3 via one or more antennas 453a, and to transmit signals to and receive signals from the central unit 5-2b via the interface 454a.

[0074] The transceiver circuit 451b of the central unit 5-2b is operable to transmit signals to and receive signals from the functions of the core network 7 and / or other gNBs 5 via the network interface 456b. The network interface 456b typically includes an interface such as S1 for communicating with the core network and a gNB-to-gNB interface (e.g., such as X2) for communicating with other gNBs. The transceiver circuit 451b of the central unit 5-2b is also operable to transmit signals to and receive signals from one or more distributed units 5-2b via the interface 454b.

[0075] Each unit 5-2a, 5-2b includes respective controllers 457a, 457b that control the operation of the corresponding transceiver circuits 451a, 451b according to software stored in the respective memories 459a and 459b of the distributed unit 5-2a and the central unit 5-2b. The software of each unit includes, among other things, respective operating systems 461a, 461b, respective communication control modules 463a, 463b, respective network slice / tenant management modules 464a, 464b, and respective DU / CU function split management modules 467a, 467b.

[0076] Each communication control module 463a, 463b is operable to control the communication of the corresponding unit 5-2a, 5-2b, including communication from one unit to the other unit. The communication control module 463a of the distributed unit 5-2a controls the communication between the distributed unit 5-2a and the UE3, and the communication control module 463b of the central unit 5-2b controls the communication between the central unit 5-2b and other network entities connected to the gNB5-2.

[0077] The communication control modules 463a and 463b also control, respectively, the parts operated by the distributed unit 5-2a and the central unit 5-2b in the uplink and downlink user traffic and control data flows for transmitting to a communication device that receives services from the gNB5-2 and includes, for example, control data for managing the operation of the UE3. Each of the communication control modules 463a and 463b is responsible for controlling, respectively, the parts operated by the distributed unit 5-2a and the central unit 5-2b in procedures such as measurement control / configuration information, communication of system information (on-demand and periodic), the part of the gNB in the random access channel (RACH) procedure. Each of the communication control modules 463a and 463b is also responsible for controlling, respectively, the parts operated by the distributed unit 5-2a and the central unit 5-2b in the setup, configuration, and reconfiguration of the gNB-to-gNB interface with an adjacent gNB and in the management of the gNB part in the setup, configuration, and reconfiguration of the gNB-to-core network interface with the core network node 7 (such as the mobility management function 7-3). Each of the communication control modules 463a and 463b is also responsible for controlling, respectively, the parts operated by the distributed unit 5-2a and the central unit 5-2b in the management of the gNB part in the handover, including, for example, handover decision (when applicable), target selection, etc. Each of the communication control modules 463a and 463b is also responsible for controlling the parts operated by the distributed unit 5-2a and the central unit 5-2b in the management of the gNB part in the UE context setup and change procedures, dual connectivity (such as operation as a master or secondary gNB, addition and management of a secondary gNB, etc.), (re)establishment procedure of the connection with the UE3, and paging procedure.

[0078] Each network slice / tenant management module 464a, 464b is operable to execute respective portions operated by the distributed unit 5-2a and the central unit 5-2b in storing and managing configuration data for defining various radio access network (RAN) slices available via the gNB 5-2 for each service / tenant.

[0079] Each DU / CU function split management module 467a, 467b is responsible for respective portions operated by the distributed unit 5-2a and the central unit 5-2b in managing, configuring, and reconfiguring the function split between the distributed unit 5-2a and the central unit 5-2b.

[0080] Mobility Management Function FIG. 5 is a block diagram showing the main components of the core node 7 that provides the mobility management function 7-3 (e.g., a mobility management entity (MME)). The core node 7-3 includes a transceiver circuit 571 operable to transmit signals to and receive signals from the gNB 5 and / or other nodes (e.g., other core nodes providing other core network functions) via the network interface 575. The controller 577 controls the operation of the transceiver circuit 571 according to software stored in the memory 579. The software includes, among other things, an operating system 581, a communication control module 583, and a mobility management module 584.

[0081] The communication control module 583 is operable to control direct and / or indirect communication between the core node 7-3 and other network entities (e.g., the gNB 5 and other core nodes 7 providing other core network functions) connected to the core node 7-3 (either directly or indirectly).

[0082] The mobility management module 584 is responsible for providing the mobility management function of the core node 7, including, for example, the control of the radio access network, paging of idle mode UEs, bearer activation / deactivation functions, and the selection of an appropriate core node 7 (e.g., serving gateway and / or TUPF) for the UE 3 at initial attach and handover with core node relocation. It is also responsible for user authentication, non-access stratum (NAS) signaling termination, generation and allocation of temporary identification for the UE, and other functions.

[0083] Slice Selection Function FIG. 6 is a block diagram showing the main components of the core node 7 that provides the slice selection function 7-4. The core node 7-4 includes a transceiver circuit 671 operable to transmit signals to and receive signals from the gNB 5 and / or other nodes (e.g., other core nodes providing other core network functions) via a network interface 675. A controller 677 controls the operation of the transceiver circuit 671 according to software stored in a memory 679. The software includes, among other things, an operating system 681, a communication control module 683, and a slice selection management module 684.

[0084] The communication control module 683 is operable to control direct and / or indirect communication between the core node 7-4 and other network entities (e.g., the gNB 5 and other core nodes 7 providing other core network functions) connected (directly or indirectly) to the core node 7-4.

[0085] The slice selection management module 684 is responsible for providing the slice selection related functions of the core node 7-4, including, for example, selecting an appropriate slice for the UE 3 in response to an initial attach request and / or a new session establishment request of the UE.

[0086] Other Functions Although not described in detail, other core network functions (e.g., AMF and SMF) can be implemented in a manner similar to that shown in FIGS. 5 and 6 by means of an appropriate transceiver circuit for transmitting signals to and receiving signals from gNB5 and / or other nodes (e.g., other core nodes 7 providing other core network functions), and a controller for controlling the operation of the transceiver circuit according to software stored in a memory. The software typically includes, among other things, an operating system, a communication control module, and other modules specific to the functionality of that core network function.

[0087] In the above description, the mobile phone, UE3, gNB5, and core network node 7 implementing the core network function have been described as having several individual modules for ease of understanding. These modules may be provided in this way for a particular application, but, for example, in other applications, such as when an existing system is modified to implement the present invention, or in a system designed from the outset with the features of the present invention in mind, these modules may be incorporated into the overall operating system or code, and thus may not be recognizable as individual entities. Also, these modules may be implemented in software, hardware, firmware, or a combination thereof.

[0088] Here, by way of mere example, several procedures will be described, which may be implemented to help provide an efficient slicing mechanism having several advantages. It is understood that each of these procedures may provide a technical benefit independently when implemented alone, or any combination of these procedures may be implemented together.

[0089] Paging Area and Roaming and Access Restriction Settings FIG. 7 shows procedures that can be executed between a base station of the type shown in the telecommunication system of FIG. 1 and a core network node 7 (e.g., mobility management function 7-3) in the context of network slicing to support efficient setting of paging areas and / or roaming and access restrictions.

[0090] In the procedure of FIG. 7, the core network node 7 obtains information for assisting in setting the paging area and / or handover restriction list from the gNB5. This information includes information for identifying the tracking area and / or paging area (e.g., tracking area code (TAC) and / or RAN paging area code), information for identifying the hardware capabilities, and / or information for identifying the list of NSTs supported by the gNB5. From this information, the core network node 7 can identify slice support and set the paging area and / or roaming and access restrictions according to the UE, taking into account the UE capabilities, SLA regarding slice support, and tenant type.

[0091] In the procedure of FIG. 7(a), the information for assisting in setting the paging area and / or handover restriction list is obtained during the gNB-core network interface setup procedure (e.g., S1 setup procedure or NG-C setup procedure). Specifically, the gNB5 provides that information to the core network node 7 by means of an Interface Setup Request (e.g., S1 setup request or NG-C setup request) at S700. The core network node 7 sets the interface accordingly and, upon successful setup of the interface, responds at S702 with an appropriate Interface Setup Response message.

[0092] Preferably, the details of the RAN-core slice mapping can be provided by the core network node 7 (e.g., AMF / mobility management function) in the interface setup response message. This slice mapping information may be used by the base station 5 when implementing a NAS (Non-Access Stratum) node selection function or a similar process to select one or more specific CN nodes to which the Initial NAS Signalling message is routed.

[0093] In the procedure of FIG. 7(b), information for assisting in setting the paging area and / or the handover restriction list is obtained during the base station configuration update procedure (e.g., eNB / gNB / NR-BS setup procedure). Specifically, the gNB 5 provides that information to the core network node 7 by means of an eNB / gNB / NR-BS configuration update message at S704. The core network node 7 updates the eNB / gNB / NR-BS configuration accordingly, and upon successful update of the eNB / gNB / NR-BS configuration, responds at S706 with an appropriate eNB / gNB / NR-BS configuration update acknowledge message, which may include details of the core-RAN slice mapping as required.

[0094] Regardless of how the core network node 7 obtains that information, the core network function 7 can set the paging area for a given UE 3 based on the supported slice types of the UE 3 and the gNB 5 from which that information is received (as shown at S708).

[0095] In order to optimize paging so that paging is performed only within a cell that supports the slice type supported by the paged UE3, when a paging message (for example, as shown in S710) is sent to the gNB5 within the tracking area associated with the paged UE, the paging message (Paging Request) can include assistance data for a paging information element (IE (Information Element)) that identifies the cell to be paged (and / or may not be). (For example, in a recommended cell IE or a similar IE). Thus, as shown, the information can preferably be provided as part of the assistance data for paging passed from the core network entity (for example, the mobility management function / MME) to the base station (eNB / gNB) in the paging request.

[0096] Regardless of how the core network node 7 obtains the information, the core network function 7 can also set a handover restriction list for a given UE3 to identify a forbidden tracking area, a location area, and / or a cell. The setting may be based on the service level contract of the UE, the UE capabilities, the UE3 from which the information is received, and the slice type supported by the gNB5. (As shown in S712).

[0097] As shown in S714, once set, a handover restriction list for a given UE3 can be sent in an Initial Context Setup Request message from core network node 7 to the gNB5 to which the UE3 is connected during the initial context setup procedure for that UE3. As shown in S714, once set, a handover restriction list for a given UE3 can also be sent in a handover request message from core network node 7 to the gNB5 to which the UE is handing over (e.g., the target gNB) during a handover procedure (e.g., a gNB-core network interface-based handover procedure).

[0098] To be complete, it is understood that the Operations, Administration and Management (OAM) function can also set the availability of a network of a slice type configured to permit UE registration.

[0099] As shown in S716, the core network node 7 can also set one or more Allowed Cell Lists (ACL) based on the eNB / gNB capability information regarding the slice support information collected via the above-described signaling mechanism (or OAM-based configuration). Specifically, the core network node 7 (e.g., the Mobility Management Function / AMF) can set an ACL for each UE 3 for each tracking area and / or for each RAN routing area based on the UE capability, the SLA requirements regarding slice support, and the tenant ID. The set ACL may be included in the Initial Context Setup Request message sent by the core network node 7 (e.g., at the time of a service request and / or a Tracking Area Update (TAU)). Preferably, when setting for each TA and / or RAN routing area, the number of cells included in the ACL is limited. Thus, the UE 3 can camp on the cells identified by the corresponding ACL, avoiding or at least minimizing the need to broadcast the slice type and tenant type supported by each base station.

[0100] FIG. 8 shows, by way of example, how a Handover Restriction List can be configured at the Cell Granularity Level (i.e., not at the TA granularity level), based on the slice type supported by the cell, gNB5 and / or tracking area, UE SLA and / or UE capabilities, to enable handover to be restricted. Specifically, the handover restriction list is set to include a Forbidden Cell-List 800 in the form of a list of base station / cell identifiers (such as a global eNB ID (or equivalent gNB ID) with a related list of, for example, E-UTRAN cell global identifiers (or equivalent 5G / NG cell identifiers)).

[0101] Therefore, preferably, when a handover is requested, the source gNB5 (e.g., the gNB providing service to UE3) can select a target gNB based at least in part on the Forbidden Cell-List 800 within the handover restriction list.

[0102] In a legacy LTE system, from the perspective of the MME, all eNBs are the same, and it is understood that this will change when slicing is adopted. Setting the handover restriction list at the cell level granularity (as opposed to access restrictions at the TA level) beneficially enables the differences between gNBs caused by slicing to be understood and taken into account within the system by the gNBs.

[0103] Support for Connected Mode Mobility (Based on gNB-to-gNB Interface) FIG. 9 shows procedures that can be performed between a base station 5 of the type shown in the telecommunications system of FIG. 1 and a user equipment 3 to support gNB-to-gNB interface-based mobility in the context of network slicing.

[0104] In the example of Figure 9, the (source) gNB (A) uses an appropriate Measurement Control message transmitted at S900 to configure the UE3 to perform appropriate Neighbour Cell Measurements on neighbouring gNBs such as gNB (B) (and possibly the serving gNB). It is understood that the source base station can limit the number of target candidates to those that support the slice of interest for the UE in question for measurement purposes. The source can collect the target hardware and slice support capabilities by exchanging such information at X2 / Xn setup or during periodic eNB configuration updates. At S901, the UE3 performs the configured measurements and reports the measurements by means of at least one Measurement Report message at S902. It is understood that this mechanism can be extended to enable gNB5 to acquire and exchange neighbouring gNB information for any supported tenant / slice type and / or for any Hardware / Frequency-Specific Slice.

[0105] Next, gNB (A) makes a handover decision. In this example, as shown in S904, gNB (A) simply selects a target gNB (e.g., gNB (B)) based on the measurement results of signal strength. However, by restricting the number of target candidates to those that support the slices of interest to the UE in question, the selected target will be a gNB that supports the preferred slice type. Once the decision is made, in S906, gNB (A) sends a handover request to the selected target gNB (B) 5. This handover request message preferably includes slice usage information that identifies the slice type used by UE 3. In this example, the slice usage information includes a slice identifier (which may also be referred to as a "slice type identifier") that represents a specific NST for each slice in use. The slice usage information may also include other information such as information that identifies one or more next-generation core network control plane functions (NG-C CP NF) (e.g., by an appropriate common control network function (CCNF) ID). As shown in FIG. 9, the identified core network functions may include one or more AMFs (identified, for example, by an AMF ID), information that identifies one or more SMFs (identified, for example, by an SMF ID), and / or one or more user plane functions (identified by a UPF ID) that are associated with the slice (e.g., if the AMF, SMF, and UPF are slice-specific). Preferably, the handover request message also includes the relevant MDD (i.e., tenant ID and / or slice type) and / or network slice selection assistance information (NSSAI) that includes, for example, UE capabilities, service types related to the slice, and services requested in some cases. The handover request message also includes information that identifies the target gNB 5 (gNB (B) in this example) and / or the target cell.

[0106] Preferably, in S908, the target gNB5 (gNB (B)) uses the received information to select slice-specific control plane and user plane network functions (e.g., the correct CCNF). This may be subject to target-based admission control for a given UE, taking into account its SLA requirements and current load. Preferably, when on-demand system information is enabled, in S910, the target gNB5 (gNB (B)) also uses the received information to identify whether it is necessary to make slice-specific system information available, and if so, enables (switches on) that slice-specific system information.

[0107] In S912, gNB (B)5 responds to the handover request message with a handover acknowledge message (typically including the handover command sent by the source gNB (A)5 to UE3 to initiate the handover).

[0108] For the remainder of the handover process, it can proceed according to procedures well known to those skilled in the art (e.g., in S914), and for the sake of brevity, will not be described in detail.

[0109] Figure 10 shows, by way of example, how a Handover Request message can be configured to provide the use of slices and related information. Specifically, as seen at 1000 in Figure 10, the Handover Request message includes an MDD information element (IE) that includes an MDD vector for UE3 to enable UE3 to identify the customer type, tenant ID, and service level agreement, a UE Temporary Identifier IE that includes information for identifying UE3 (typically specific to a particular AMF and / or gNB), and a Slice Usage List IE. The Slice Usage List IE includes, for each slice used by UE3, a respective Slice Type (NST) ID IE that provides a slice ID representing the associated NST of that slice, and a respective NG-C CP NF ID information element (e.g., identifying the appropriate Common Control Network Function (CCNF) ID) that includes an identifier for each associated network function related to that slice (e.g., AMF ID, SMF ID, and / or UPF ID).

[0110] Furthermore, as shown in Figure 10, the Handover Request can include a Quality of Service (QoS) Flow ID information element that identifies the associated traffic flow related to a particular quality of service (QoS), e.g., including downlink forwarding information and information identifying the uplink GPRS Tunnelling Protocol (GTP) tunnel endpoint for the QoS flow. The slice ID can indicate coarse-granular QoS, but the QoS indication preferably provides a fine-granular QoS indication that can be obtained from the MDD.

[0111] Therefore, preferably, the target gNB5 can accurately know which slice type UE3 is using among the ones that the UE has joined, and thus, based on the relevant SLA, can beneficially determine what communication operations UE3 requires for the slice that the UE has joined and uses, and thus can select the core network functions 7 accordingly (e.g., slice-specific SMF, AMF, UPF, and / or common control plane functions) (which may be affected by local permission control and network-wide policies in terms of how to handle UEs belonging to a given tenant ID). Furthermore, this enables the adoption of common or slice-specific authentication procedures.

[0112] The presence of the slice ID and MDD in the handover request message also provides improved permission control and load management. This is made possible because by providing the MDD and slice ID information, the network can determine at a given time (e.g., when the SLA has the most restrictions) how many UEs of a particular tenant can access a particular slice.

[0113] Support for Dual Connectivity FIG. 11 shows procedures that can be executed between base stations 5 of the type shown in the telecommunication system of FIG. 1 to support dual connectivity in the context of network slicing. Here, a so-called "master" base station (MeNB / MgNB) provides overall control and a subset of the communication support for UE3 (e.g., control plane communication and / or some user plane communication), and a so-called "secondary" base station (SeNB / SgNB) provides other communication support for the UE (e.g., some / all of the user plane communication).

[0114] As seen in the example of FIG. 11, at S1100, in order to request the gNB (B) 5 to allocate resources for dual connectivity operation for a specific UE, a message (in this example, a SeNB / SgNB Addition Request message) is sent from the first base station 5 (in this example, gNB (A)) to the second base station 5 (in this example, gNB (B)). This message substantially requests the setup of a dual connectivity for a specific UE, where gNB (A) 5 is set as the master gNB and gNB (B) 5 is set as the secondary gNB.

[0115] The SeNB / SgNB Addition Request message includes slice usage information that identifies the slice type used by UE3. In this example, the slice usage information includes a slice identifier (which may sometimes be referred to as a "slice type identifier") that represents a specific NST for each slice in use. The slice usage information may also include other information such as information that identifies one or more next-generation core network control plane functions (NG-C CP NFs) (e.g., by an appropriate common control network function (CCNF) ID). As shown in FIG. 11, the identified core network functions may include one or more AMFs (e.g., identified by an AMF ID), information that identifies one or more SMFs (e.g., identified by an SMF ID), and / or one or more user plane functions (e.g., identified by a UPF ID) that are associated with the slice (e.g., if the AMF, SMF, and UPF are slice-specific). Preferably, the SeNB / SgNB Addition Request message also includes the relevant MDD (i.e., tenant ID and / or slice type) and / or network slice selection assistance information (NSSAI) that includes, for example, UE capability information, service types related to the slice, and services requested in some cases.

[0116] Preferably, gNB (B) 5 sets up dual connectivity using the received information to select, for example, a slice-specific user plane network function and the like.

[0117] In S1102, gNB (B) 5 responds to the SeNB / SgNB addition request message with an appropriate positive response message (for example, a SeNB / SgNB addition request acknowledge message).

[0118] Support for Connection Reestablishment FIG. 12 shows procedures that can be executed between a base station 5 of the type shown in the telecommunication system of FIG. 1 and a user equipment 3 to support connection reestablishment.

[0119] As seen in the example of FIG. 12, in S1200, a message (in this example, an RRC connection reestablishment request message) is transmitted from UE3 to the base station 5 to reestablish the connection. In S1202, the base station 5 responds with an appropriate message (for example, an RRC connection reestablishment message). To complete the reestablishment of the connection, UE3 transmits an appropriate completion message (RRC connection reestablishment complete in the figure).

[0120] The RRC connection reestablishment request (FIG. 12(a)) or the RRC connection reestablishment complete message (FIG. 12(b)) may include a slice identifier (which may be transmitted together with or form part of the network slice selection assistance information (NSSAI)) and an associated tenant ID (which may form part of the MDD vector).

[0121] Therefore, preferably, the base station 5 can re - establish the requested connection using the received information.

[0122] FIG. 13 shows, at 1300, by way of example, how an RRC connection re - establishment request message can be configured to provide a slice identifier and a related tenant ID when the RRC connection re - establishment request (Connection Reestablishment Request) is extended to include slice and tenant - specific information.

[0123] Base Station-Core Network Procedures FIGS. 14 and 15 show, in the context of network slicing, some procedures that can be executed between the base station 5 and the core network node 7 of the telecommunication system of FIG. 1 to support various communication processes.

[0124] FIG. 14(a) shows procedures that can be executed via a base station 5 - to - core network node 7 interface (e.g., an interface such as S1 or the NG - C interface) to support the setup of an initial UE context.

[0125] As seen in FIG. 14(a), when a context needs to be set up for UE3, the core network node 7 (e.g., the mobility management function 7 - 3 or other CN functions described herein) starts the context setup procedure by transmitting an appropriate message (in this example, an initial context setup request message) to the base station 5 at S1400.

[0126] The initial context setup request message includes slice usage information that identifies the slice type used by UE3. In this example, the slice usage information includes slice identifiers (which may also be referred to as "slice type identifiers") that represent a specific NST for each slice in use. The slice usage information may also include other information such as information that identifies one or more next-generation core network control plane functions (NG-C CP NFs) (e.g., by an appropriate common control network function (CCNF) ID). As shown, the identified core network functions may include one or more AMFs (e.g., identified by an AMF ID), information that identifies one or more SMFs (e.g., identified by an SMF ID), and / or one or more user plane functions (e.g., identified by a UPF ID) that are associated with the slice (e.g., if the AMF, SMF, and UPF are slice-specific). Preferably, the initial context setup request message also includes the associated MDD (i.e., tenant ID and / or slice type) and / or network slice selection assistance information (NSSAI) that includes, for example, UE capability information, service types related to the slice, and services requested in some cases.

[0127] The base station 5 uses the slice usage and other related information provided in the initial context setup request message for the setup of the initial context of UE3 and responds in S1402 with an appropriately formatted response message (in this example, an Initial Context Setup response message).

[0128] Figure 14(b) shows procedures that may be performed via a base station 5 to core network node 7 interface (e.g., an interface such as S1 or an NG-C interface) to support changes to the UE context.

[0129] As shown in Fig. 14(b), when the context needs to be changed for UE3, the core network node 7 (e.g., the mobility management function 7-3 or other CN functions described herein) starts the context change procedure in S1404 by sending an appropriate message (in this example, a UE Context Modification Request message) to the base station 5.

[0130] The UE Context Modification Request message includes slice usage information that identifies the slice type used by UE3. In this example, the slice usage information includes a slice identifier (which may also be referred to as a "slice type identifier") that represents a specific NST for each slice in use. The slice usage information may also include other information such as information that identifies one or more next-generation core network control plane functions (NG-C CP NFs) (e.g., by an appropriate common control network function (CCNF) ID). As shown, the identified core network functions may include one or more AMFs (e.g., identified by an AMF ID), information that identifies one or more SMFs (e.g., identified by an SMF ID), and / or one or more user plane functions (e.g., identified by a UPF ID) that are associated with the slice (e.g., if the AMF, SMF, and UPF are slice-specific). Preferably, the UE Context Modification Request message also includes the associated MDD (i.e., the tenant ID and / or slice type) and / or network slice selection assistance information (NSSAI) that includes, for example, UE capability information, service types related to the slice, and services requested in some cases.

[0131] The base station 5 uses the slice usage and other related information provided in the UE context change request message in the change of the UE context for the UE 3, and in S1406, responds with an appropriately formatted response message (in this example, a UE context change response (Context Modification Response) message).

[0132] FIG. 14(c) shows procedures that can be executed via a base station 5 to core network node 7 interface (e.g., an interface such as S1 or an NG-C interface) to support a RAN-CN interface-based handover (e.g., a handover such as S1).

[0133] As seen in FIG. 14(c), when a handover is requested for the UE, the core network node 7 (e.g., the mobility management function 7-3 or other CN functions described herein) requests a handover to the base station 5 (i.e., the selected target gNB) by transmitting an appropriate message (in this example, a handover request message) to the base station 5 in S1408.

[0134] The handover request message includes slice usage information that identifies the slice type used by UE3. In this example, the slice usage information includes a slice identifier (which may sometimes be referred to as a "slice type identifier") that represents a specific NST for each slice in use. The slice usage information may also include other information such as information that identifies one or more next-generation core network control plane functions (NG-C CP NFs) (e.g., by an appropriate common control network function (CCNF) ID). As shown, the identified core network functions may include one or more AMFs (e.g., identified by an AMF ID), information that identifies one or more SMFs (e.g., identified by an SMF ID), and / or one or more user plane functions (e.g., identified by a UPF ID) that are associated with the slice (e.g., if the AMF, SMF, and UPF are slice-specific). Preferably, the handover request message also includes the associated MDD (i.e., tenant ID and / or slice type) and / or network slice selection assistance information (NSSAI) that includes, for example, UE capability information, service types related to the slice, and services requested in some cases.

[0135] In the handover process (e.g., the method described with reference to FIG. 9 by selecting appropriate core network UP and CP functions and / or activating system information as needed), the base station 5 uses the slice usage and other related information provided in the handover request message and responds in S1410 with an appropriately formatted response message (in this example, a Handover Acknowledge message).

[0136] FIG. 14(d) shows procedures that may be performed via a base station-to-core network node 7 interface (e.g., an interface such as S1 or an NG-C interface) to support a gNB-gNB interface-based handover (e.g., a handover such as X2).

[0137] As shown in FIG. 14(d), at S1412, during the gNB-gNB interface-based handover of UE3 (e.g., as described generally with reference to FIG. 9), the base station 5 (i.e., the selected target gNB) sends a Path Switch Request message to the core network node 7 (e.g., the mobility management function 7-3 or other CN functions described herein) during the handover process (e.g., during the procedure represented by S914 in FIG. 9). The core network node 7 responds at S1414 by sending a Path Switch Acknowledge message to the base station 5.

[0138] The Path Switch Acknowledge message includes slice usage information that identifies the slice type used by UE3. In this example, the slice usage information includes a slice identifier (also referred to as a "slice type identifier") that represents a specific NST for each slice in use. The slice usage information may also include other information such as information that identifies one or more next-generation core network control plane functions (NG-C CP NFs) (e.g., by an appropriate common control network function (CCNF) ID). As shown, the identified core network functions may include information that identifies one or more AMFs (e.g., identified by an AMF ID), one or more SMFs (e.g., identified by an SMF ID), and / or one or more user plane functions (e.g., identified by a UPF ID) associated with the slice (e.g., if the AMF, SMF, and UPF are slice-specific). Preferably, the Path Switch Acknowledge message also includes the associated MDD (i.e., the tenant ID and / or slice type) and / or network slice selection assistance information (NSSAI) that includes, for example, UE capability information, service types related to the slice, and services requested in some cases.

[0139] As described with reference to FIG. 9, the provision of slice usage and other related information provided in the path switch positive response message may be performed by adding the information or replacing the information in the handover request message.

[0140] In the handover process (e.g., in the manner described with reference to FIG. 9 by selecting appropriate core network UP and CP functions and / or activating system information as necessary), the base station 5 uses the slice usage and other related information provided in the path switch positive response message.

[0141] FIG. 14(e) shows procedures that can be executed via a base station-to-core network interface (e.g., an interface such as S1 or the NG-C interface) to support paging procedures.

[0142] As seen in FIG. 14(e), when paging is required to contact UE3, the core network node 7 (e.g., the mobility management function 7-3 or other CN functions described herein) causes the base station 5 to perform paging for UE3 in the cell supporting the required slice and tenant ID indicating that the base station 5 is operational by transmitting an appropriate message (in this example, a paging message) to the base station 5 at S1416.

[0143] The paging message includes slice usage information that identifies the slice type(s) used by the UE3 (to be paged and / or paging). In this example, the slice usage information includes a slice identifier (which may also be referred to as a "slice type identifier") that represents a particular NST for each slice in use. The slice usage information may also include other information such as information that identifies one or more next generation core network control plane functions (NG-C CP NFs) (e.g., by an appropriate common control network function (CCNF) ID). As shown, the identified core network functions may include information that identifies one or more AMFs (e.g., identified by an AMF ID), information that identifies one or more SMFs (e.g., identified by an SMF ID), and / or one or more user plane functions (e.g., identified by a UPF ID) that are associated with the slice (e.g., if the AMF, SMF, and UPF are slice specific). Preferably, the paging message also includes the associated MDD (i.e., tenant ID and / or slice type) and / or network slice selection assistance information (NSSAI) that includes, for example, UE capability information, service types associated with the slice, and services requested in some cases.

[0144] FIG. 15 is a simplified sequence diagram showing slice update procedures that may be performed between the base station 5 and the core network node 7 of the telecommunication system of FIG. 1 in the context of network slicing.

[0145] In the procedure of FIG. 15, a core network node (e.g., a mobility management function, AMF, SMF, etc.) uses a dedicated "slice update" procedure to provide the slice ID and / or tenant ID to the base station 5 (e.g., the target gNB before and after movement).

[0146] As seen in the example of FIG. 15, at S1500, an appropriate message (in this example, a Slice Update Request message) is sent from core network node 7 to base station 5. The slice update request includes a slice identifier (which may be sent together with or form part of the Network Slice Selection Assistance Information (NSSAI)) and an associated tenant ID (which may form part of the MDD vector). At S1502, base station 5 responds with an appropriate message (e.g., a Slice Update Response message).

[0147] Preferably, base station 5 can use the received information to make appropriate decisions (e.g., selection of appropriate core network functions for the UE's slice and / or activation of appropriate on-demand system information).

[0148] Further Information Figures 16 to 20 are provided as background to assist in understanding how slicing can be implemented in a telecommunications network. In this regard, FIG. 16 shows how different slices / slice types can be supported by different base stations. FIG. 17 shows a possible configuration of some possible Slice Specific Core Network Functions and the interfaces / reference points between them (i.e., represented by the "NG*" labels in the figure). FIG. 18 is a simplified schematic diagram showing how "m" slice types and Z UEs for "n" tenants can be supported via a radio access network (RAN) and a core network (CN). FIG. 19 is a simplified schematic diagram showing how slices for different UEs communicating via a given RAN can have different sets of Slice Specific Core Network Functions and / or Common Control Plane Network Functions. FIG. 20 is a simplified sequence diagram showing typical connection procedures that can be performed within a network with a Slice Selection Function (SSF).

[0149] Changes and Alternatives A number of detailed exemplary embodiments have been described as above. As will be understood by those skilled in the art, many changes and alternatives can be made to the above embodiments while benefiting from the invention embodied therein. For illustrative purposes, only some of these alternatives and changes are described here.

[0150] In the above exemplary embodiments, several software modules for implementing a user equipment, a base station, and / or core network functions, etc. have been described. As will be understood by those skilled in the art, such software modules may be provided in a compiled or non-compiled form, and may be supplied to corresponding hardware as signals on a computer network or on a recording medium. Further, the functions executed by some or all of this software may be executed using one or more dedicated hardware circuits. However, the use of software modules is preferably such that it facilitates the updating of the corresponding hardware to update its functionality. Similarly, although a transceiver circuit has been used in the above embodiments, at least some of the functions of the transceiver circuit can be executed by software.

[0151] For example, although the functions of the core network are described as logical functions, it is understood that they may be implemented using one or more computer processing devices having one or more hardware computer processors programmed using appropriate software instructions to provide the required logical functions (e.g., one or more computer processors forming part of the controller described with reference to FIGS. 5 and 6). Further, it is understood that all or part of these functions may be implemented in hardware as a dedicated circuit using one or more dedicated integrated circuits such as, for example, an application specific integrated circuit (ASIC).

[0152] Similarly, the functions of the user equipment and the base station (gNB) are typically implemented using one or more computer processing devices having one or more hardware computer processors programmed with appropriate software instructions to provide the necessary functions (e.g., one or more computer processors forming part of the controller described with reference to FIGS. 2, 3, and 4). Further, it is understood that all or part of this functionality may be implemented in hardware as a dedicated circuit using one or more application specific integrated circuits (ASICs) for example.

[0153] It is understood that the controllers referred to in the description of the UE, gNB, and core network nodes / functions (i.e., with reference to FIGS. 2 to 7) may include any suitable controller such as, for example, an analog or digital controller. Each controller may comprise, for example, (but not limited to) one or more hardware-implemented computer processors, microprocessors, central processing units (CPUs), arithmetic logic units (ALUs), input / output (IO) circuits, internal memory / cache (program and / or data), processing registers, communication buses (e.g., control, data, and / or address buses), direct memory access (DMA) functionality, hardware or software implemented counters, pointers, and / or timers, and / or any other suitable form of processing circuitry including the like.

[0154] Although FIG. 1 shows a whole network slice for the purpose of explanation, since the core can have its own slice, it is understood that the radio access network (RAN) can also do so. Similarly, the control plane (CP) and the user plane (UP) can have completely different slices. Depending on standardization and the policies of cellular operators, the mapping from the RAN slice to the core slice may be different.

[0155] In addition, a tenant may be a wholesale customer, which is a wireless communication service provider that does not have its own wireless network infrastructure through which MVNOs / MOLOs (such as Mobile Virtual Network Operators (MVNOs) and Mobile Other Licensed Operators (MOLOs)) provide services to customers. However, a tenant does not necessarily have to be an MVNO / MOLO. A tenant may also be an enterprise customer such as a multinational company, a fleet of vehicles, an emergency service and / or a security service (such as a security company). Each tenant may have different requirements regarding which slice type to use based on a service level agreement. With the concept of tenants, mobile network operators can distinguish different customer requirements and provide customized services using one or more slices.

[0156] Although different devices are described as having a transceiver circuit for the purpose of communicating (i.e., transmitting / receiving) data with other devices / devices, it is understood that the transceiver function may also be implemented by software executed on a corresponding hardware controller for communicating messages and / or information between different respective functions co-located on the same physical device.

[0157] It is understood that, alternatively or additionally, TUPF or at least one additional TUPF can be co-located with the access network (e.g., to enable the stationary UE scenario).

[0158] It is understood that the term "Participating Operator" may be used instead of the term "tenant".

[0159] In the above exemplary embodiments, a telecommunication system operating according to 3GPP standards has been described. However, as will be understood by those skilled in the art, the techniques described herein can be employed in communication systems operating according to other standard specifications, in particular, any orthogonal frequency-division multiplexing (OFDM)-based system such as WiMAX (Worldwide Interoperability for Microwave Access).

[0160] In summary, it has been described that a communication device comprises a controller and a transceiver, and the controller is configured to generate a message including slice support information indicating at least one slice support capability of the communication device and to control the transceiver to transmit the message to a node of a core network.

[0161] The slice support information includes hardware capability information from which the slice support information can be obtained. The slice support information may include information identifying at least one network slice template (NST) related to at least one slice supported by the communication device. The slice support information may include information (e.g., at least one of a tracking area code and a radio access network (RAN) paging area) identifying at least one area that is an area where the communication device is located and where the communication device can be paged. The controller may operate to terminate the message as part of an interface establishment procedure (e.g., an S1 or NG-C setup procedure) via a core network to base station interface. The message may be an interface setup request message (e.g., an S1 or NG-C setup message) for a core network to base station interface. The controller may be configured to transmit the message for the communication device via a core network to base station interface as part of a configuration update procedure (e.g., an eNB, gNB, or NR-BS configuration procedure). The message may be a configuration update message (e.g., an eNB, gNB, or NR-BS configuration update message).

[0162] The core node is also described as including a controller and a transceiver, the controller controlling the transceiver to receive from the communication device a message including slice support information indicating at least one slice support capability of the communication device and being configured to set information stored in the core node based on the slice support information.

[0163] When setting the information stored in the core node, the controller may be configured to set at least one access control list (ACL) based on the slice support information. The controller may be configured to control the transceiver to transmit at least one ACL (for example, in an initial context setup request message) to the communication device or another communication device. When setting the information stored in the core node, the controller may be configured to set a paging area based on the slice support information. The controller may be configured to control the transceiver to transmit a paging message (for example, a paging request) including information for identifying cells in the paging area set for the communication device to the communication device or another communication device. The information for identifying cells in the set paging area may be provided in the assistance data for the paging information element of the paging message. When setting the information stored in the core node, the controller may be configured to set a handover restriction list based on the slice support information to identify cells where handover is restricted at the cell level granularity. The controller may be configured to control the transceiver to transmit the handover restriction list (for example, in at least one of an initial context setup request message and a core network to base station interface based handover request message) to the communication device or another communication device. The core node may be configured to execute at least one of a mobility management function (for example, a mobility management entity), an access management function (AMF), and a session management function (SMF).

[0164] The communication device also comprises a controller and a transceiver, the controller controlling the transceiver to receive, from another communication device, a message comprising slice support information related to at least one slice supported by the at least one communication device, as part of a handover procedure for the at least one communication device, and the communication device being configured to be set up to support the communication of the at least one communication device based on the slice support information by at least one of a selection of an appropriate slice-specific core network function based on the slice support information and an activation (switch on) of slice-specific on-demand system information based on the slice support information is described.

[0165] The slice support information may include slice usage information identifying at least one slice (and / or at least one network slice template of the slice) used by the at least one communication device. The slice support information may include information identifying at least one tenant and / or corresponding slice type associated with the at least one communication device (e.g., at least one multi-dimensional descriptor (MDD) vector). The slice support information may include information identifying at least one core network function (e.g., access management function (AMF), session management function (SMF), and / or user plane function) associated with at least one slice used by the at least one communication device. The slice support information may include network slice selection assistance information (NSSAI) associated with at least one slice used by the at least one communication device.

[0166] The communication device also includes a controller and a transceiver. The controller is configured to control the transceiver to receive, from another communication device, a message including slice support information related to at least one slice supported by at least one communication device as part of a procedure for setting up dual connectivity, and to configure the communication device for dual connectivity based on the slice support information.

[0167] The message may include a secondary base station addition request (e.g., SeNB / SgNB addition request) message.

[0168] The communication device includes a controller and a transceiver. The controller is configured to control the transceiver to receive, from at least one communication device, a connection re-establishment message including slice support information related to at least one slice supported by the at least one communication as part of a connection re-establishment procedure, and to configure the communication device to support re-establishment of the connection with the communication device based on the slice support information.

[0169] The connection re-establishment message may include at least one of a connection re-establishment request message and a connection re-establishment completion message.

[0170] The communication device also includes a controller and a transceiver. The controller is configured to control the transceiver to transmit, as part of a connection re-establishment procedure, a connection re-establishment message including slice support information related to at least one slice supported by the communication device to the communication device.

[0171] The communication device also includes a controller and a transceiver. The controller is configured to control the transceiver to receive from a core node at least one message for at least one communication device, the at least one message including slice support information related to at least one slice used by the at least one communication device, and to configure the communication device to support the communication of the at least one communication device based on the slice support information.

[0172] The at least one message including the slice support information may be received as part of at least one of an initial context setup procedure, a user equipment (UE) context change procedure, a core network to base station interface based handover procedure, a base station to base station interface based handover procedure, a paging procedure, and a slice update procedure. The at least one message may include at least one of an initial context setup request message, a user equipment (UE) context change request message, a core network to base station interface based handover request message, a path switch request positive response message, a paging message, and a slice update request message. The controller may be configured to configure the communication device to support the communication of the at least one communication device based on the slice support information by at least one of selecting an appropriate slice specific core network function based on the slice support information and activating slice specific on-demand system information based on the slice support information.

[0173] In the above example, a mobile phone-based telecommunication system was described. As would be understood by those skilled in the art, the technology described herein can be applied in any communication system. In general, a base station and a mobile phone can be regarded as communication nodes or communication devices that communicate with each other. Other communication nodes or communication devices may include access points and user devices such as, for example, personal digital assistants, laptop computers, web browsers, and the like.

[0174] Various other modifications will be apparent to those skilled in the art and are not described in further detail herein.

[0175] This application claims priority based on UK Patent Application No. 1700270.0 filed on January 6, 2017 and UK Patent Application No. 1700505.9 filed on January 11, 2017, the entire disclosures of which are incorporated herein by reference.

Claims

1. means for receiving system information including information associated with the type of slice supported; means for performing cell selection or initial access procedures for the slice indicated by the information; comprising; the type of the slice is operator common type, and operator specific type including; the operator common type is enhanced mobile broadband (eMBB), critical communication for high reliability and low latency, and massive communication for Internet of Things (IoT) including, a wireless terminal.

2. means for transmitting system information including information associated with the type of slice supported to a wireless terminal; means for performing cell selection or initial access procedures for the slice indicated by the information; comprising; the type of the slice is operator common type, and operator specific type including; the operator common type is enhanced mobile broadband (eMBB), critical communication for high reliability and low latency, and massive communication for Internet of Things (IoT) including, a base station.

3. receiving system information including information associated with the type of slice supported; performing cell selection or initial access procedures for the slice indicated by the information; including; the type of the slice is operator common type, and operator specific type including; the operator common type is enhanced mobile broadband (eMBB), critical communication for high reliability and low latency, and massive communication for Internet of Things (IoT) including, a method in a wireless terminal.

4. transmitting system information including information associated with the type of slice supported to a wireless terminal; controlling cell selection or initial access procedures for the slice indicated by the information; including; the type of the slice is operator common type, and operator specific type including; the operator common type is Enhanced mobile broadband (eMBB), critical communications for high reliability and low latency, and massive communications for the Internet of Things (IoT) including a method at a base station.

Images