Methods, apparatuses, and systems for creation of network slices in a communication network

Abstract

A core network (CN) network function (NF) receiving, from an application function (AF), a request to create a slice, the request comprising first slice configuration information; responsive to a deter

Description

Field The present specification relates to apparatus, methods, and / or computer programs for facilitating the creation of network slices, including temporary network slices in a communication network. Background Network slicing can be used in communication networks (e.g., in 5G mobile networks) to create independent and dedicated virtual sub-networks on the same computing infrastructure, for instance, where respective dedicated virtual sub-networks (which are generally referred to as network slices) provide services that have different requirements on latency, reliability, throughput and mobility. To enable a subscriber of an operator of a communication network (e.g., user equipment (UE) associated with the subscriber of a communication network) to access a particular network slice, the following process may be followed. The particular network slice may be assumed to be present in the communication network. The subscriber may then initiate the request to subscribe to the particular network slice. This can be performed by the subscriber contacting the operator of the communication network (e.g., through the operator's call centre). Then, via one or more back-office operations, the identifier of a particular network slice (e.g., single - network slice selection assistance information (S-NSSAI) of the particular network slice) can be added to the subscriber's subscription information (e.g., subscriber data) stored in the unified data management (UDM) of the communication network. The subscriber can then request to access the respective network slice when a user equipment associated with the subscriber sends a request to the communication network (e.g., a 5G mobile network) to establish a protocol data unit (PDU) session within which the said identifier for the respective network slice is provided. This process can result in significant resources of the communication network being consumed (e.g., time, computational resources required for the communications between the various entities (e.g., the operator, network management entity, NFs of a core network of the communication network, radio access network (RAN) nodes of a radio access network of the communication network, subscribers and / or UEs associated with subscribers)), as well as requiring expert knowledge from the individual entities involved. Further, there is no defined method by which network slices that were created can be removed, and hence a network slice that was created remains available to UEs even after expiration of the network slice's intended lifetime. This can result in the consumption of significant resources of the communication network. Even if, in some situations, it is possible to remove a network slice, doing so may again require a manual process which may take some time to complete and / or otherwise consume significant resources, as well as again requiring expert knowledge from the individual entities involved in the removal of a network slice. Summary In a first aspect, this specification describes a communication device comprising means for: receiving, from an access network node, a broadcast comprising network slice configuration information associated with a network slice instantiated by a core network based on a request from an application function; and initiating, based on the network slice configuration information, establishment of a communication session within the network slice identified by a slice identifier. In a second aspect, this specification describes a communication device comprising means for: receiving, from a core network, a non-access stratum signalling comprising network slice configuration information associated with a network slice instantiated by the core network based on a request from an application function; and initiating, based on the network slice configuration information, a communication session within the network slice. In a third aspect, this specification describes a system for a core network, the system comprising a first network function for management and orchestration of network slices, the first network function configured for: receiving, from an application function, AF, a request to create a network slice, the request comprising first network slice configuration information; responsive to a determination that one or more trigger conditions for instantiating the network slice are satisfied, causing the network slice to be instantiated based on the first network slice configuration information; and sending, to a second network function for access and mobility management, second network slice configuration information associated with the network slice to be provided by the second network function to an access network node for broadcast to one or more user equipments, UEs, to enable the one or more UEs to initiate establishment of a communication session within the network slice, the second network slice configuration information comprising an identifier associated with the network slice. In a fourth aspect, this specification describes an apparatus comprising an application function configured for: sending, to a network function of a core network, a request to create and / or instantiate a network slice, the request comprising network slice configuration information to cause the network function to respectively create and / or instantiate a network slice based on the network slice configuration information; and receiving, from the network function, a response to the request, the response comprising an indication that the network slice has been created and / or instantiated respectively. In a fifth aspect, this specification describes a method comprising receiving, from an access network node, a broadcast comprising network slice configuration information associated with a network slice instantiated by a core network based on a request from an application function; and initiating, based on the network slice configuration information, establishment of a communication session within the network slice. In a sixth aspect, this specification describes a method comprising receiving, from a core network, a non-access stratum signalling comprising network slice configuration information associated with a network slice instantiated by the core network based on a request from an application function; and initiating, based on the network slice configuration information, establishment of a communication session within the network slice. In a seventh aspect, this specification describes a method comprising receiving, from an AF a request to create a network slice, the request comprising first network slice configuration information; responsive to a determination that one or more trigger conditions for instantiating the network slice are satisfied, causing the network slice to be instantiated based on the first network slice configuration information; and sending, to a second network function for access and mobility management, second network slice configuration information associated with the network slice to be provided by the second network function to an access network node for broadcast to one or more UEs to enable the one or more UEs to initiate a communication session within the network slice, the second network slice configuration information comprising an identifier associated with the network slice. In an eighth aspect, this specification describes a method comprising sending, to a network function of a core network, a request to create and / or instantiate a network slice, the request comprising network slice configuration information to cause the network function to respectively create and / or instantiate a network slice based on the network slice configuration information; and receiving, from the network function, a response to the request, the response comprising an indication that the network slice has been created and / or instantiated respectively. In a ninth aspect, this specification describes computer-readable instructions which, when executed by a computing apparatus, cause the computing apparatus to perform (at least) any method as described herein (including the method of the fifth to eighth aspects described above). In a tenth aspect, this specification describes a computer-readable medium (such as a non-transitory computer-readable medium comprising program instructions stored thereon for performing (at least) any method described herein (including the methods of the fifth to eighth aspects described above)). In an eleventh aspect, this specification describes an apparatus comprising: at least one processor; and at least one memory including computer program code which, when executed by the at least one processor, causes the apparatus to perform (at least) any method as described herein (including the method of the fifth to eighth aspects described above). In a twelfth aspect, this specification describes an apparatus comprising: at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, causes the apparatus to perform (at least) any method as described herein (including the method of the fifth to eighth aspects described above). In a thirteenth aspect, this specification describes a computer program comprising instructions which, when executed by an apparatus, cause the apparatus to perform (at least) any method as described herein (including the method of the fifth to eighth aspects described above). Brief description of the drawings Example embodiments will now be described, by way on non-limiting examples, with reference to the following schematic drawings, in which: FIG. 1 is a high-level block diagram depicting some entities of a communication network in accordance with an example embodiment; FIGS. 2A to 3B depict procedures in accordance with various example embodiments; FIGs. 4A and 4B are flowcharts depicting methods performed in accordance with example embodiments; FIG. 5 is a flowchart depicting a method performed in accordance with an example embodiment; FIG. 6 is a flowchart depicting a method performed in accordance with an example embodiment; FIG. 7 is a schematic diagram depicting components of one or more of the example embodiments described previously; and FIG. 8 depicts a tangible media for storing computer-readable code which, when run by a computer, may perform methods according to example embodiments described herein. Detailed description The scope of protection sought for various implementations of the subject matter disclosed herein is set out by the independent claims. The features of the subject matter described herein, if any, described in the specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various implementations of the subject matter described herein. In the description and drawings, like reference numerals refer to like elements throughout. In the following, different exemplifying embodiments will be described using, as an example of a communication network to which the embodiments may be applied, and, in particular, a communication network comprising an access network and a core network. The access network may be a radio access network, such as a next generation radio access network (NG-RAN), without restricting the embodiments to such radio access networks. It will be appreciated that, for a person skilled in the art, the access network described herein may also be other kind of access networks, such as a Wi-Fi network that is connected to the core network via an interworking entity. The communication network (e.g., the access network and the core network) may operate in accordance with a radio access technology standardized by 3GPP, such as long-term evolution (LTE, otherwise known as E-UTRA), new radio or 5G, and future radio access technologies, such as 6G. Implementations described herein relate to facilitating the creation and utilisation of network slices, including temporary network slices, in a communication network. In particular, some implementations described herein enable a core network of a communication network (e.g., a 5G core network operating according to 3GPP standards for new radio) (or a network function of the core network configured to instantiate and de-instantiate network slices, such as a network slice selection function (NSSF)) to create and / or instantiate a network slice based on a request to create and / or instantiate a network slice received from an application function (AF)) hosted and running on a server (e.g., an application server). The AF may be a trusted application function or an untrusted application function that communicates with the NSFF via a network exposure function (NEF). The core network can advertise the network slice that has been created and / or instantiated to one or more UEs. In some implementations, the network slice can be a temporary network slice. For instance, the network slice can be de-instantiated by the core network (e.g., after a specified time duration has elapsed). Some implementations described herein enable a AF to request the creation and / or instantiation of a network slice (e.g., a temporary network slice). Some implementations described herein enable a UE to use the network slice (e.g., the temporary network slice) advertised by the core network. In some implementations, the request to create and / or instantiate the network slice (e.g., the temporary network slice) can include network slice configuration information (which may be referred to as first network slice configuration information). For instance, the network slice configuration information can be indicative of one or more characteristics of the network slice to be created and / or instantiated. The network slice configuration information can include an identifier of the network slice that is created and / or instantiated (generally referred to herein as network slice identifier), a coverage area for the network slice (e.g., an area the network slice is available, a quality of service (QoS) for the network slice (e.g., a QoS for services provided by the network slice), an indication of UEs allowed to use the network slice (e.g., an identifier of a group of UEs that is allowed to use the network slice (generally referred to as a UE Group identifier (ID)), and a tracking area identity (TAI). In some implementations, the request can include one or more trigger conditions for the instantiation and / or de-instantiation of the network slice (e.g., a temporary network slice). For instance, the trigger conditions can include a time to instantiate and / or deinstantiate the network slice, a duration that the network slice be available, a load on the capacity of the communication network, an indication of a particular signal to be monitored (e.g., an emergency signal), etc. The core network can then accept or reject the request (e.g., based on the network slice configuration information, the availability of resources of the core network, and / or an authorisation status of the request). A network slice identifier (e.g., a single network slice selection assistance information (S-NSSAI)) can also be associated with the network slice. In some implementations, the core network can modify one or more of the characteristics specified in the network slice configuration information (e.g., a latency for the network slice, a maximum uplink data rate and / or a maximum downlink data rate for data traffic communicated within a network slice, a data loss for the network slice, etc.). For instance, the modification may be based on the availability of resources of the communication network. In some implementations, the core network (e.g., the NSSF) can instantiate the network slice based on the one or more trigger conditions for instantiation of a network slice (referred to herein as instantiation trigger conditions) being satisfied (e.g., an instantiation time occurring, a delay expiring, a load on the capacity of the communication network being met, an indication of a particular signal to be monitored being received (e.g., an emergency signal), etc). Instantiation of a network slice can refer to a process by which an already created network slice is made operational. In other words, a network slice which has been instantiated can be used by UEs to request establishment of a PDU session within the instantiated network slice. In some implementations, the core network can instantiate the network slice based on receipt of the request. For instance, the request may be a request to instantiate the network slice received from the AF. Instantiating the network slice can involve providing instantiated network slice data (otherwise known as second network slice configuration information) to one or more network functions of the core network (e.g., a unified data management (UDM), access and mobility management function (AMF), etc). The instantiated network slice data can include, for instance, at least some of the network slice configuration information provided in the request, the network slice identifier generated by the core network and associated with the network slice, etc. In some implementations, the instantiated network slice can be advertised by the core network to the UEs via one or more network functions (e.g., using the AMF). In some implementations, the core network can cause an access network to advertise the instantiated network slice. The instantiated network slice can be advertised by broadcasting at least some of the instantiated network slice data (e.g., at least some of the network slice configuration information provided in the request, the network slice identifier generated by the core network, etc). In some implementations, the network slice is broadcast to all UEs within range of the NG-RAN node (or e.g., is broadcast within a tracking area identified by the TAI and / or coverage area for the network slice specified in the request from the AF). In some implementations, the network slice is broadcast only to selected UEs (e.g., only UEs associated with a UE Group ID specified in the request). This may be performed by advertising the network slice via different system information blocks (SIBs). For instance, a first SIB (SIB 1) can be broadcast to all UEs, whereas other SIBs can be sent to specific UEs on-demand. The UE(s) can then receive the instantiated network slice data. In some implementations, the UE(s) can receive the slice data sent by the one or more network functions. In some implementations, the UE can then establish a connection using the network slice (e.g., to an external network with which the core network manages connections), using the received slice data. This may be based, for instance, on a selection of the network slice at the UE (e.g., by a subscriber). The external network may be, for instance, a data network (DN) (e.g., providing service provider services, internet access, 3rd party services, etc.). It will be understood that the connection process can be performed in any suitable way. In some implementations, the network slice can de-instantiated. This can be triggered based on one or more trigger conditions being satisfied (e.g., a time to de-instantiate occurring, a duration expiring, a load on the capacity of the communication network being met, an indication of a particular signal to be monitored being received (e.g., an emergency signal), etc). Additionally or alternatively, the network slice can be deinstantiated based on a request being received (e.g., from the AF) to de-instantiate the network slice. De-instantiating the network slice can involve providing deinstantiated network slice data (which may identify the network slice and may, for instance, be similar to the instantiated network slice data) to one or more network functions (e.g., the UDM, the AMF, etc). This may cause resources allocated to the network slice to be de-allocated. Additionally or alternatively, the core network can notify the NG-RAN node and / or the UE (e.g., via the NG-RAN node or directly via the AMF) that the network slice has been de-instantiated. In this way, implementations described herein can provide the ability to orchestrate, dimension, and instantiate a network slice. Implementations described herein can also provide the ability to indicate to subscribers the availability of such slices, their attributes and time / area boundaries. In addition, implementations described herein can provide the ability to add subscribers to such network slices, and offer the corresponding service using a relatively simple and standardized process. In other words, implementations described herein allow operators to dynamically create network slices end to end, and then "push" the relevant services to subscribers using standardised signalling. As a result, network slices can be provided in a manner which is standardized, automated, and convenient. As such, the time, effort, and administrative burden required to provide network slices can be reduced (e.g., as compared to a more manual process to make network slices available for subscribers). Furthermore, the computational resources, the resources consumed in initially providing network slices to subscribers can be reduced. This can thus enable a greater number of network slices to be provided given the same infrastructure and resources, and in a more dynamic manner. Furthermore, according to implementations described herein, network slices can be quickly and easily removed. As such, the computational resources, time, effort, and administrative burden required to remove network slices can be reduced. Resources which would otherwise be consumed by the network slice being maintained after its intended lifetime has expired (e.g., as a result of a slower, more manual process to remove the network slice being used) can also be conserved. In addition, network slices that have specific lifetimes and / or areas of applicability are facilitated. In other words, a more granular dimensioning as to the network slice configuration (e.g., in terms of validity conditions, such as time and area) can be provided. Furthermore, the implementations described herein can enable the use of network slices in various applications. For instance, temporary network slices can be particularly useful for applications such as weekend events (e.g., a concert), where subscribers may upload videos on to social media; business or conference events, where subscribers may require particular network requirements for demonstrations, etc. As described herein, in some implementations, network slices can be created by the core network based on receipt of the request (e.g., from the AF) and the information included in the request. The conditions for the network slice instantiation and / or deinstantiation can be indicated in the request (e.g., a time the slice should be instantiated, a duration which the slice should be available for, etc). In other words, the conditions can be added to the definition of the network slice. In this way, slice creation can be defined based on standardised signals (e.g., according to 3GPP standards), and reservation of network slice resources needs to be made only during this time, making network slice support more resource efficient within the network. Furthermore, as described herein, in some implementations, network slices can be created outside of the core network (e.g., and outside of 3GPP standards). For instance, the network slice could be created as part of operator back-office operations, and then instantiated and / or de-instantiated on request (e.g., from the AF) as described herein. In this way, the core network need not monitor the conditions for instantiation and / or de-instantiation itself, and computational resources that would be consumed in doing so by the core network (e.g., processor time of one or more processors of the core network, memory available to the core network, etc.) can be conserved. In some implementations, the computational resources of the core network may be relatively limited. As such, by conserving these computational resources of the core network, the core network can allocate these computational resources for other purposes (e.g., providing more network slices, managing connections for more UEs, etc.). It will be appreciated that, whilst various operations of a core network are described herein, these operations may be performed by one or more network functions of a core network. For instance, in some implementations, some or all of these operations may be performed by an NSSF. In some implementations, some or all of these functions may be performed by other network functions of a core network, such as an AMF, or an NEF. Turning to FIG. 1, various entities of a communication network 100 in accordance with an example embodiment are depicted. As depicted in FIG. 1, example communication network 100 includes a core network 110, radio access network (NG-RAN) node 130), a user equipment (UE) 140, and a data network (DN) 160. As further depicted in FIG. 1, the core network 110 includes one or more network functions (NFs), including NSSF 112, UDM 114, NEF, 116, AMF 118, AF 120, and UPF 122. Core network 110 can be, for instance, a 5G core network. The core network 110 can include a set of NFs. Each NF can provide services to other NFs (e.g., via servicebased interfaces implemented as application programming interfaces (APIs)). The NFs may be virtualized network functions. For instance, in some implementations, the NFs may be provided by a cloud computing system. Alternatively, the NFs may be provided together by an apparatus (e.g., a computing devices) or one or more other NFs, or may be provided by different apparatuses (e.g., computing devices). Although a number of NFs are described herein, it will be appreciated that the core network 110 can include some, all, or none of the NFs described herein, as long as means to perform the operations described herein are provided. In addition, the core network 110 can include other NFs which are not described herein, and these NFs may perform some or all of the operations described herein. As depicted in FIG. 1, the core network 110 may include an AMF 118. The AMF 118 may be responsible for mobility management, including managing registration of UEs with the core network 110. In some implementations, a UE must, during registration with the core network (e.g., the AMF 118), receive authorisation to use services provided by the core network 110. For instance, when a UE is registering with the AMF 118, the AMF 118 may be responsible for selecting an authentication server function (AUSF), a UDM 114, and a policy control function (PCF). The AMF 118 can also be responsible for selecting a SMF that is responsible for PDU session establishment (e.g., based on the DN, subscription information, network slice information, etc). Additionally or alternatively, the AMF 118 can be responsible for connection management (e.g., establishing and releasing a control plane signalling connection between the UE 140 and the AMF 118 across the N1 interface). The control plane signalling connection across the N1 interface can allow non access stratum (NAS) messages to be exchanged between the UE 140 and the AMF 180 (e.g., for registration, authentication, PDU session establishment, etc.). The N1 interface may involve the NG-RAN node 130, however, messages transmitted using the N1 interface are transmitted transparently (e.g., without being processed by the NG-RAN node 130). Additionally or alternatively, the AMF 118 can be responsible for handling next generation application protocol (NGAP) signalling which is transferred between the AMF 118 and the NG-RAN node 130 (e.g., via the N2 interface). This can be used, for instance, for PDU session management procedures (e.g., to setup, modify, and release radio resources at the NG-RAN node 130 and the UE 140). The core network 110 may include a UDM 114. The UDM 114 can manage subscriber data of subscribers. The subscriber data of subscribers can be stored locally within the UDM 114 and / or stored within a unified data repository (UDR) (e.g., to enable multiple UDMs to access the subscriber data). The UDM 114 can interact with a AUSF during authentication of a UE. For instance, the UDM 114 can receive an identifier of the UE from the AUSF, determine an authentication method based on the subscriber's subscription profile, and respond to the AUSF with an authentication vector. The AUSF can allow the UE to authenticate itself with the core network 110, e.g., verify that the subscriber is genuine and authorised to access the core network 110. The UDM 114 can interact with the AMF 118 during a registration procedure. For instance, the UDM 114 can access an AMF identity for the UE that is registering with the AMF 114, and provide the AMF 118 associated with the AMF identity with subscription data of the subscriber associated with the UE (including e.g. access and mobility subscription data) to support selection of a session management function (SMF). The UDM 114 can interact with the SMF during PDU session establishment. For instance, the UDM 114 can store a PDU session identity, SMF information, and / or data network (DN) information. The UDM 114 can provide the SMF with subscription information (e.g., PDU type, etc). Additionally or alternatively, the UDM 114 can provide updates to the AMF 118 and / or SMF if subscriber data is changed. The core network 110 can include a NSSF 112. The NSSF 112 can perform network slice selection during the UE registration procedure (e.g., based on a request from the AMF 120). For instance, the NSSF 112 can verify that a UE is subscribed to one or more network slices (e.g., as indicated by S-NSSAIs), select one or more network slices to serve the UE, and identify a set of candidate AMFs which can be used to serve the UE. The core network 110 may include a NEF 116. The NEF 116 can provide information regarding the capability of NFs within the core network 110 to external NFs. In other words, the NEF 116 can expose certain NF capabilities. Additionally or alternatively, other NFs can report specific events to the NEF 116, and the NEF 116 can then provide reports of those events to other NFs. For instance, a first NF can provide, to the NEF 116, a request to subscribe to be notified of a specific event at a second NF. The NEF 116 can then subscribe to receive reports from the second NF each time the specific event occurs at the second NF. Once the subscription is established at the second NF, the second NF can provide reports to the NEF 116, which can then be forwarded by the NEF 116 to the first NF. The core network 110 may include an AF 120. However, in some implementations, the AF 120 may be provided external to the core network 110 (e.g., by third party servers). The AF 120 can be hosted on an application server and provides specific services (e.g., a video streaming service, etc.) to the UE 140. The AF 120 can access the core network 110 directly (when the AF 120 is included in the core network 110 (e.g., is a trusted AF)) or via NEF 116 (e.g., if the AF external to the core network 110, is from a third party and is not trusted by the core network 110). The core network may include UPF 122. The UPF 122 can provide a data connection from the UE 140 to DN 160 (e.g., via NG-RAN node 130). In other words, the UPF 122 can route and forward uplink packets from the UE 140 (and via NG-RAN node 130) to the DN 160 and downlink packets from the DN 160 to the UE 140 (and via NG-RAN node 130). The UPF 122 can serve a particular network slice. In this way, the UE 122 (once it is has been provided with access to the particular network slice by the core network 110) can be provided with connectivity to the DN 160 within the particular network slice. The UPF 122 can be controlled by the SMF. The DN 160 can provide, for instance, service provider services, internet access, 3rd party services, etc. As depicted in FIG. 1, the communication network 100 includes a NG-RAN node 130. For instance, the NG-RAN node can include a new radio (NR) base station (otherwise known as gNodeB), an enhanced or NG eNodeB, an eNodeB, and / or a NodeB. Although the NG-RAN node 130 is shown in FIG. 1, it will be appreciated that the UE 140 may access the core network 110 via an access network (AN) and an interworking function (not shown). The access network may be any suitable access network, for example, a wireless local area network (WLAN) using Wi-Fi, etc. As depicted in FIG. 1, the communication network includes UE 140. The UE 140 (also called communication device, user device, user terminal, terminal device) illustrates one type of an apparatus to which resources on the air interface are allocated and assigned, and thus any feature described herein with a UE may be implemented with a corresponding apparatus.. The UE 140 typically refers to a portable computing device that include wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (mobile phone), smartphone, personal digital assistant (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and / or touch screen computer, tablet, game console, notebook, and multimedia device. It should be appreciated that the UE 140 may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network. The UE 140 may also be a device having capability to operate in Internet of Things (loT) network which is a scenario in which objects are provided with the ability to transfer data over the loT network without requiring human-to-human or human-to-computer interaction. In some applications, the UE 140 may comprise a small portable device with radio parts (such as a watch, earphones or eyeglasses) whereby some or all computation is carried out in a cloud computing system. The UE 140 (or in some embodiments a layer 3 relay node) is configured to perform one or more of UE functionalities. The UE 140 may also be called a subscriber unit, mobile station, remote terminal, access terminal, or user terminal just to mention but a few names or apparatuses. It will be appreciated that FIG. 1 depicts examples of a simplified communication network 100 only showing some of the network functions of the core network 110, all being logical units, whose implementation may differ from what is shown. Furthermore, some of the connections shown in FIG. 1 are logical connections; however, the actual physical connections may be different. It is also apparent to a person skilled in the art that the communication network 100 may comprise also other functions and structures than those shown in FIG. 1. The embodiments are not, however, restricted to the communication network 100 given as an example but a person skilled in the art may apply the solution to other communication networks provided with necessary properties. For instance, although the entities of the communication network 100 in FIG. 1 (e.g., the core network 110, the UE 140, the NG-RAN node 130, and the DN 160) have been depicted as single entities, different units, processors and / or memory units (not all shown in FIG. 1) may be implemented. As described herein, the communication network 100 of FIG. 1 can be used in the creation, instantiation, provision and utilisation of network slices. For instance, FIGs. 2A to 3B relate to example operations which may be performed by one or more of the entities of the communication network 100 in furtherance of this purpose. Turning to FIG. 2A, a procedure 200 for creation of a network slice (e.g., a temporary network slice) in accordance with an example embodiment is depicted. In this example, the network slice is created by the core network 110. The network slice can be created in response to a request to create a network slice (e.g., received from AF 120). In this way, network slice creation can be performed using standardised (e.g., 3GPP defined) procedures. The conditions (e.g., one or more trigger conditions) for the instantiation and / or deinstantiation of a network slice can be configured as part of the network slice creation. The monitoring of these conditions can be monitored by the core network 110 (e.g., by NSSF 112). For instance, the conditions for instantiation of a network slice can include an instantiation time (e.g., a time the network slice is to be instantiated) and an availability duration (e.g., a period of time the instantiated network slice is to be available). Prior to operation S2.1, resources of the core network 110 (or of any NF thereof) are not allocated for the network slice. As depicted in FIG. 2A, at operation S2.1, various NFs can subscribe to be notified of network slice instantiation. For instance, the AMF 118, the UDM 114 and / or the NSSF 112 can subscribe (e.g., via the NEF 116) to be notified of instantiation of a network slice (generally referred to herein as network slice instantiation). As such, responsive to the network slice being instantiated, the various NFs can be provided with a notification of the instantiation of the network slice (e.g., by the NEF). At operation S2.2, the AF 120 provides (e.g., sends) a network slice creation request (e.g., to the NSSF 112). The network slice creation request can be indicative of a request to create a network slice. The network slice creation request can include, for instance, network slice configuration information for configuring a new network slice to be created (otherwise known as first network slice configuration information). For instance, the network slice configuration information can include information indicative of a coverage area, a QoS for a service provided by the network slice, one or more instantiation and / or de-instantiation trigger conditions (e.g., a slice instantiation time and / or duration, etc.), a tracking area identifier (TAI), a UE group ID, use cases to be supported, priority, etc. In some implementations, the AF 120 can provide the request network slice creation request to the NEF 116. The NEF 116 can provide a first level of authentication for the request network slice creation request. The NEF 116 can additionally or alternatively translate and / or map the request network slice creation request into a subsequent network slice creation request to be provided to the NSSF 112. The NEF 116 can provide the network slice creation request or the subsequent network slice creation request to the NSSF 112. The network slice creation request can be provided (e.g., by the AF 120 to NEF 116, by the NEF 116 to the NSSF 112) using service operations. For instance, the request can be issued from the AF 120 to the NEF 116 via an NEF_Slice_Create service operation or an Nnef_Slice_Create service operation. At operation S2.3, the core network 110 (e.g., using NSSF 112) authorises the creation of a new network slice. For instance, a second level of authentication for the network slice creation request may be performed. Additionally or alternatively, a determination can be made that there are sufficient resources (e.g., computing resources, network resources, storage resources, etc.) available to allocate to the new network slice (e.g., for the network slice configuration information provided in the network slice creation request). In some implementations, the network slice configuration information which is authorised for the network slice can be modified from the network slice configuration information included in the request (e.g., based on the available resources in the core network 110). An identifier for the network slice can also be associated with the network slice (e.g., a slice ID, S-NSSAI, etc). In some implementations, the network slice creation request can be rejected (e.g., based on the authentication being failed, insufficient available resources for creation of the network slice, etc). At operation S2.4, the core network 110 (e.g., NSSF 112) provides a response to the network slice creation request, where the response is indicative of the status of the creation of the new slice. For instance, the response can be indicative of a confirmation that the new slice has been created and / or that creation of the new network slice has been authorised. In some implementations, if the network slice creation request is rejected (or not authorized), the response can be indicative of the network slice creation request being rejected (or not authorized). The response can include, for instance, an identifier associated with the new network slice that has been created (e.g., S-NSSAI, slice ID, etc.). For instance, responsive to the authorization of the network slice creation request, the NSSF 112 can provide the response to the NEF 116. The NEF 116 can translate and / or map the response so that the translated or mapped response is suitable for receipt by the AF 120. The NEF 116 can then provide the (translated and / or mapped) response to the AF 120. At operation S2.5, the core network 110 (e.g., NSSF 112) can determine that one or more network slice instantiation trigger conditions are satisfied. For instance, the one or more network slice instantiation trigger conditions can include a network slice instantiation time. The core network 110 (e.g., NSSF 112) can monitor for the occurrence of the network slice instantiation time. When it is determined that the network slice instantiation time has occurred, the network slice can be instantiated by the core network 110. For instance, the NSSF 112 can instantiate the network slice with other NFs (e.g., UDM 114, AMF 118, etc), and NG-RAN node 130 using the assigned S-NSSAI and / or slice ID. At operation S2.6, responsive to operation S2.5, the NSSF 112 provides data for the instantiated network slice (otherwise known as second network slice configuration information) to the UDM 114. For instance, the data for the instantiated network slice may include at least some of the network slice configuration information included in the network slice creation request, and / or an identifier associated with the network slice. At operation S2.7, the NSSF 112 can request the AMF 118 announce the instantiated network slice (as well as any other available network slices) to UEs that are registered with the communication network For instance, the request can be provided to the AMF 118 using an Namf_SliceBroadcast service operation. The request can also include the network slice data for the instantiated network slice (which may be similar to the network slice data for the instantiated network slice, or second network slice configuration information, provided to the UDM 114 at operation S2.6) to the AMF 118. For instance, the network slice data for the instantiated network slice (generally referred to herein as instantiated network slice data) can include an identifier associated with the network slice (e.g., S-NSSAI). In some implementations, the AMF 118 can forward the request to NG-RAN node 130, including any instantiated network slice data (otherwise termed network slice configuration information, which may include, e.g., an identifier associated with the network slice), at operation S2.8. For instance, the request can be provided to the NG-RAN node 130 using NGAP signalling. Responsively, the NG-RAN node 130 can broadcast information regarding the newly instantiated network slice, e.g., for receipt by one or more UEs 140. For instance, information regarding the newly instantiated network slice can include some or all of the instantiated network slice data received in the request from the core network 110 (e.g., from AMF 118). For instance, the NG-RAN node 130 can broadcast attributes of the network slice (e.g., QoS, etc.), information relating to the availability of the network slice (e.g., time of service, etc.), etc. The NG-RAN node 130 can broadcast the information regarding the newly instantiated network slice in the tracking area identified by a TAI and / or coverage area indicated by the instantiated network slice data. The information regarding the newly instantiated network slice can be broadcast over the new radio (NR) Uu interface. At least some of the information can be provided as a system information block (SIB) message. For instance, a SIB can be broadcast which includes an identifier associated with the network slice (e.g., S-NSSAI). Additionally or alternatively, at operation S2.8, the core network 110 (e.g., the AMF 118) can provide the information regarding the newly instantiated network slice (as well as information about any other available network slices) for receipt by the one or more UEs 140. For instance, the core network 110 can provide the information in Non-Access Stratum (NAS) signalling. The information regarding the newly instantiated network slice can be provided from the core network 110 via an N1 interface. In some implementations, the information regarding the newly instantiated network slice is broadcast to all UEs within range (or e.g., in the specified tracking area identified by a TAI or coverage area). Alternatively, the information regarding the newly instantiated network slice may be broadcast only to select UEs (e.g., as specified by the instantiated network slice data, only those UEs registered to receive the network slice data of the newly instantiated network slice, etc). The UE 140 can receive the information regarding the newly instantiated network slice broadcast by the core network 110 and / or NG-RAN node 130. The UE 140 can then store and process the information such that the UE 140 can be aware of the available network slices (including the newly instantiated network slice), as well as any network slice configuration information (e.g., which was included in the information broadcast by the NG-RAN node) associated with the available network slice(s). For instance, in some implementations, upon receiving the UE 140, the UE 140 can subscribe to the network slice. For instance, the UE 140 (e.g., using universal subscriber identity module (USIM)) can maintain a list of subscribed network slices. The list can then be updated when the broadcasted network slice configuration information is received by the UE 140, when the network slice is selected and / or at another time when the network slice network slice is otherwise accepted. As operation S2.9, the network slice is selected at the UE 140. For instance, based on the network slice information stored at the UE 140, the network slice can be selected (e.g., from among a plurality of available network slices). For instance, network slice information can be provided to a user of the UE 140 (e.g., via a display of the UE 140). The user can then provide an indication of the network slice to be selected (e.g., via a touch input). Additionally or alternatively, the network slice can be selected "automatically" based on, for instance, the network slice information satisfying one or more conditions, context information (e.g., current time, date, location data, calendar event information, etc.), user preferences, historical usage information, etc. At operation S2.10, the UE 140 requests that a communication session be established (e.g., responsive to the selection of the network slice) between the UE 140 and the core network 110 (e.g., a UPF of the network slice). For instance, the request can include an identifier of the network slice (e.g., the S-NSSAI). To request that a communication session be established, the UE 140 may send a PDU session establishment request that includes the S-NSSAI of the selected network slice to the core network 110 (e.g., the AMF 118). The PDU session establishment request can be sent in NAS signalling . At operation S2.ll, the core network 110 (e.g., using the AMF 118) provides a request to the NG-RAN node 130 to establish a communication session with the UE 140 (e.g., with an external network) for the network slice. For instance, the core network 110 (e.g., the AMF 118) can provide an initial context setup request to the NG-RAN node. The initial context setup request can be sent in a NGAP message. The initial context setup request can include an identifier of the communication session for the network slice (e.g., an identifier of a PDU session (generally referred to herein a PDU session ID). In some implementations, the initial context setup request can be sent in response to the UE 140 being authenticated by the core network 110 (e.g., by the UDM 114 and / or NSSF 112). At operation S2.12, the UE 140 communicates with the core network 110 using a communication session established within the network slice. For instance, the communication session can be a PDU session. In some implementations, the core network 110 may perform secondary authentication and / or authorization of the UE 140 e.g., prior to the establishment of the communication session. Turning to FIG. 2B, a procedure for de-instantiation of a network slice (e.g., a temporary network slice) 210 in accordance with an example embodiment is depicted. At operation S2.13, it is determined (e.g., by the core network 110, or the NSSF 112 thereof) that one or more network slice de-instantiation conditions are satisfied (e.g., as specified in the network slice creation request). For instance, it may be determined that a duration for the network slice being available has expired and / or that a de-instantiation time has occurred. At operation S2.14, the network slice is de-instantiated (e.g., responsive to the determination at operation S2.13). For instance, de-instantiated network slice data can be sent to the UDM 114 (e.g., by the NSSF). The de-instantiated network slice data can include an identifier associated with the network slice (e.g., the S-NSSAI). For instance, the de-instantiated network slice data can be similar to the instantiated network slice data described in relation to operations S2.6 to S2.8. This can cause the information stored at the UDM 114 to be updated to reflect that the network slice has been de-instantiated. At operation S2.15, a request for the core network 110 to stop broadcasting information associated with the network slice is provided to the AMF 118. Similarly to above, the request can include de-instantiated slice data (e.g., including an identifier associated with the network slice). The request may be similar, for instance, to the request described in relation to operation S2.7. However, rather than relating to a request to broadcast the information, the request of operation S2.15 relates to a request for stopping the broadcasting of the network slice information. At operation S2.16, the core network 110 can cause the information associated with the network slice to stop being broadcast. For instance, the AMF 118 can forward the request to the NG-RAN node 130 to stop broadcasting information associated with the network slice. Additionally or alternatively, the request may be indicative of a request for the removal of the network slice. The request can include de-instantiated network slice data (including e.g., an identifier associated with the network slice). In some implementations, the core network 110 can send a de-instantiation message to the UE 140. This can be performed, for instance, in a similar manner as described in relation to operation S2.8. Upon receipt of the de-instantiation message, the UE 140 can update the network slice information stored at the UE. For instance, the list of subscribed network slices stored at the UE 140 (e.g., at the USIM) can be updated. For instance, information relating to the network slice can be removed from storage. At operation S2.17, as a result of the previous operations, the identifier of the network slice is removed from the network and the UE. Turning to FIG. 3A, a procedure 300 in accordance with an example embodiment is depicted. As depicted in FIG. 3A, at operation S3.1, the network slice is created. The network slice can be created in any suitable manner, and need not be created in a procedure defined by any particular standard specification (e.g., 3GPP standards). For instance, the network slice can be configured in the network using operator defined mechanisms (e.g., outside of 3GPP signalling). At operation S3.2, various NFs can subscribe to be notified when a network slice is instantiated. For instance, this may be performed in a similar manner as described in relation to operation S2.1. At operation S3.3, a network slice instantiation request is received. For instance, the AF 120 can provide the request to the NSSF 112 (e.g., via the NEF 116). The network slice instantiation request can be indicative of a request to instantiate a network slice. The request to instantiate a network slice can include, for instance, network slice configuration information for a new network slice that is requested to be instantiated (otherwise known as first network slice configuration information). For instance, the network slice configuration information can include information indicative of a coverage area for the network slice, a QoS for the network slice, a tracking area identifier TAI of a tracking area for the network slice, an identifier of a UE group (UE group ID) that includes UE that are to access the network slice, use cases to be supported, priority, etc. In some implementations, the AF 120 can provide the request to the NEF 116. The NEF 116 can provide a first level of authentication for the request. The NEF 116 can additionally or alternatively translate and / or map the request into a subsequent request to be provided to the NSSF 112. The NEF 116 can provide the request to the NSSF 112. The request can be issued (e.g., between the AF 120, NEF 116, and NSSF 112) using application programming interface operations. At operation S3.4, the core network 110 (or e.g., the NSSF 112 thereof) authorises instantiation of the new network slice. This can be performed in a similar manner as described in relation to S2.3. At operation S3.5, the core network 110 (or e.g., the NSSF 112 thereof) sends a response message (e.g., to the AF 120). This can be performed in a similar manner as described in relation to S2.4. At operations S3.6 through to S3.12, the core network 110 (or e.g., the NSSF 112 and AMF 118 thereof) instantiates the network slice, advertises the network slice, and a communication session with the UE 140 (e.g., and an external network) using the network slice is established. These operations can be performed in a similar manner as described in relation to operations S2.6 to S2.12. However, rather than the network slice being instantiated based on one or more instantiation trigger conditions (e.g., set out in the request) being satisfied, instantiation of the network slice in FIG. 3A can be triggered (e.g., by the AF) based on the receipt of the network slice instantiation request. In this way, the instantiation trigger conditions can be monitored outside of the core network 110 (e.g., and outside of the 3GPP network). As such, resources which would otherwise be consumed in the monitoring of the instantiation trigger conditions (e.g., by the core network 110, or one or more NFs thereof, which may be limited) can therefore be conserved. Turning to FIG. 3B, a procedure 310 in accordance with an example embodiment is depicted. At operation S3.13, a network slice de-instantiation request can be received. For instance, the AF 120 can provide the network slice de-instantiation request to the NSSF 112 (e.g., via the NEF 116). The network slice de-instantiation request can be indicative of a request for the network slice to be de-instantiated. The network slice de-instantiation request can include an identifier associated with the network slice. At operation S3.14, the NSSF 112 provides de-instantiated network slice data to the UDM 114. This may be performed in a similar manner as described in relation to operation S2.14. At operation S3.15, the NSSF 112 requests the AMF 118 to stop broadcasting information associated with the network slice. This may be performed in a similar manner as described in relation to operation S3.15. At operation S3.16, the NSSF 112 provides a response message to the AF 120 (e.g., via the NEF 116). The response message can be indicative of the network slice de-instantiation request being accepted and / or actioned. At operation S3.17, the core network 110 (e.g., using the AMF 118) forwards the request to the NG-RAN node 130 and in some implementations, provides a de-instantiation message to the UE 140. This can be performed in a similar manner as described in relation to operation S2.16. At operation S3.18, as a result of the previous operations, the network slice is removed from the network and the UE 140. In this way, the monitoring of de-instantiation trigger conditions can additionally or alternatively be monitored outside of the core network 110 (e.g., and outside of the 3GPP network). Resources which would otherwise be consumed in the monitoring of the de-instantiation trigger conditions (e.g., by the core network 110, or one or more NFs thereof) can therefore be conserved. Turning to FIG. 4A, a method 400 performed in accordance with an example embodiment is depicted. The method 400 of FIG 4A may be performed, for instance, by a communication device, such as a UE (e.g., the UE 140 of FIGs. 1 to FIG. 3B). At operation S4.1, the method 400 includes receiving, from an access network node (e.g., the NG-RAN node 130 of FIG. 1), a broadcast comprising network slice configuration information associated with a network slice instantiated by a core network (e.g., the core network 110 of FIG. 1) based on a request from an application function. The network slice can be, for instance, a temporary network slice, as described herein. In some implementations, the network slice configuration information comprises a network slice identifier associated with the network slice, such as a S-NSSAI or a slice ID. Additionally or alternatively, the network slice configuration information can comprise one or more of: an area in which the network slice is available, a quality of service for the network slice, and timing information associated with the network slice, the timing information indicating a time when the network slice will be available and / or a duration the network slice will be available. In some implementations, the network slice configuration information is received in a system information block, SIB. At operation S4.2, the method 400 includes initiating, based on the network slice configuration information, a communication session within the network slice. In some implementations, initiating the communication session within the network slice can include sending, to the core network, a request to establish a communication session within the network slice, the request comprising the network slice identifier. In some implementations, the method 400 can further include receiving, from the access network node, a message indicating that the network slice has been deinstantiated. In some of these implementations, the method 400 can further include deleting, based on the message, the network slice configuration information associated with the network slice stored at the communication device. Turning now to FIG. 4B, a method 410 performed in accordance with an example embodiment is depicted. The method 410 of FIG 4B may be performed, for instance, by a communication device, such as a UE (e.g., the UE 140 of FIGs. 1 to FIG. 3B). At operation S4.3, the method 410 includes receiving, from a core network (e.g., the core network 110 of FIG. 1), a message comprising network slice configuration information associated with a network slice instantiated by the core network based on a request from an application function. The message may, for instance, be a NAS message. At operation S4.4, the method 410 includes initiating, based on the network slice configuration information, a communication session within the network slice. Turning to FIG. 5, a method 500 performed in accordance with an example embodiment is depicted. The method 500 may be performed by a first network function of a core network for management and orchestration of network slices, such as the NSSF 112 of core network 110 of FIGs. 1 to 3B. At operation S5.1, the method 500 includes receiving, from an AF, a request to create a network slice, the request comprising first network slice configuration information. In some implementations, the method 500 further includes authorising, based on the first network slice configuration information, creation of the network slice. In some of these implementations, the method 500 further includes sending, to the application function, a response to the request, the response comprising an indication that the creation of the network slice is authorised, and an identifier of the network slice instantiated by the first network function. At operation S5.2, the method 500 includes, responsive to a determination that one or more trigger conditions for instantiating the network slice are satisfied, causing the network slice to be instantiated based on the first network slice configuration information. In some implementations, the first network slice configuration may include one or more trigger conditions for instantiating and / or de-instantiating the network slice. For instance, the one or more trigger conditions for instantiating the network slice can include a time the network slice is to be instantiated. In some implementations, the request is indicative of a request to instantiate the network slice. As such, the one or more trigger conditions can be satisfied based on the request being received. At operation S5.3, the method 500 includes sending, to a second network function for access and mobility management, second network slice configuration information associated with the network slice to be provided by the second network function to an access network node for broadcast to one or more UEs to enable the one or more UEs to initiate a communication session within the network slice, the second network slice configuration information comprising an identifier associated with the network slice. In some implementations, the method 500 can include, in response to a determination that one or more trigger conditions for de-instantiating the network slice are satisfied, causing the network slice to be de-instantiated. The method 500 can further include sending, to the second network function, a message indicative of the network slice being de-instantiated to cause the broadcasting of the second network slice configuration information for receipt by the one or more UEs to be stopped. In some implementations, the second network function is configured for sending, to the access network node, the second network slice configuration information to cause the access network node to broadcast the second network slice configuration information to the one or more UEs and to store the second network slice configuration information at the access network node. The second network function can be further configured for causing the access network node to broadcast the second network slice configuration information in a system information block, SIB. Additionally or alternatively, the second network function can be configured for causing the access network node to broadcast the second network slice configuration information in an area specified in the first slice network configuration information. Additionally or alternatively, the second network function can be configured for receiving, from a UE of the one or more UEs, a request to establish a communication session within the network slice, the request comprising a network slice identifier associated with the network slice included in the second network slice configuration information. Turning to FIG. 6, a method 600 performed in accordance with an example embodiment is depicted. The method 600 may be performed by an apparatus comprising an application function, such as the AF 120 of FIGs. 1 to 3B. At operation S6.1, the method 600 includes sending, to a network function of a core network, a request to create and / or instantiate a network slice, the request comprising network slice configuration information which causes the network function to respectively create and / or instantiate a network slice based on the network slice configuration information. The network slice configuration information may comprise one or more of: an area in which the network slice is to be available, a quality of service for the network slice, and timing information for when the network slice will be available. At operation S6.2, the method 600 includes receiving, from the network function, a response to the request, the response comprising an indication that the network slice has been created and / or instantiated respectively. The response may further comprise an identifier associated with the network slice (e.g., a network slice ID, an S-NSSAI, etc.). Turning to FIG. 7, components of one or more of the example embodiments described previously is depicted, which hereafter are referred to generically as a processing system 700. The processing system 700 may, for example, be the apparatus referred to in the claims below. The processing system 700 may have a processor 702, a memory 704 closely coupled to the processor 702 and comprised of a RAM 714 and a ROM 712, and, optionally, a user input 710 and a display 718. The processing system 700 may comprise one or more network / apparatus interfaces 708 for connection to a network / apparatus, e.g., a modem which may be wired or wireless. The network / apparatus interface 708 may also operate as a connection to other apparatus such as device / apparatus which is not network side apparatus. Thus, direct connection between devices / apparatus without network participation is possible. The processor 702 is connected to each of the other components in order to control operation thereof. The memory 704 may comprise a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD). The ROM 712 of the memory 704 stores, amongst other things, an operating system 715 and may store software applications 716. The RAM 714 of the memory 704 is used by the processor 702 for the temporary storage of data. The operating system 715 may contain code which, when executed by the processor implements aspects of the algorithms and sequences described above. Note that in the case of small device / apparatus the memory can be most suitable for small size usage i.e., not always a hard disk drive (HDD) or a solid-state drive (SSD) is used. The processor 702 may take any suitable form. For instance, it may be a microcontroller, a plurality of microcontrollers, a processor, or a plurality of processors. The processing system 700 may be a standalone computer, a server, a console, or a network thereof. The processing system 700 and needed structural parts may be all inside device / apparatus such as loT device / apparatus i.e., embedded to very small size. In some example embodiments, the processing system 700 may also be associated with external software applications. These may be applications stored on a remote server device / apparatus and may run partly or exclusively on the remote server device / apparatus. These applications may be termed cloud-hosted applications. The processing system 700 may be in communication with the remote server device / apparatus in order to utilize the software application stored there. FIG. 8 shows a tangible media, in the form of a removable memory unit 810, storing computer-readable code which when run by a computer may perform methods according to example embodiments described above. The removable memory unit 810 may be a memory stick, e.g., a USB memory stick, having internal memory 820 storing the computer-readable code. The internal memory 820 may be accessed by a computer system via a connector 830. Of course, other forms of tangible storage media may be used, as will be readily apparent to those of ordinary skilled in the art. Tangible media can be any device / apparatus capable of storing data / information which data / information can be exchanged between devices / apparatus / network. Embodiments of the present invention may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The software, application logic and / or hardware may reside on memory, or any computer media. In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a "memory" or "computer-readable medium" may be any non-transitory media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. Reference to, where relevant, "computer-readable medium", "computer program product", "tangibly embodied computer program" etc., or a "processor" or "processing circuitry" etc. should be understood to encompass not only computers having differing architectures such as single / multi-processor architectures and sequencers / parallel architectures, but also specialised circuits such as field programmable gate arrays FPGA, application specify circuits ASIC, signal processing devices / apparatus and other devices / apparatus. References to computer program, instructions, code etc. should be understood to express software for a programmable processor firmware such as the programmable content of a hardware device / apparatus as instructions for a processor or configured or configuration settings for a fixed function device / apparatus, gate array, programmable logic device / apparatus, etc. If desired, the different functions discussed herein may be performed in a different order and / or concurrently with each other. Furthermore, if desired, one or more of the above-described functions may be optional or may be combined. Similarly, it will also be appreciated that the flow diagrams and sequences described herein are examples only and that various operations depicted therein may be omitted, reordered and / or combined. It will be appreciated that the above-described example embodiments are purely illustrative and are not limiting on the scope of the invention. Other variations and modifications will be apparent to persons skilled in the art upon reading the present specification. Moreover, the disclosure of the present application should be understood to include any novel features or any novel combination of features either explicitly or implicitly disclosed herein or any generalization thereof and during the prosecution of the present application or of any application derived therefrom, new claims may be formulated to cover any such features and / or combination of such features. Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described example embodiments and / or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims. It is also noted herein that while the above describes various examples, these 5 descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention as defined in the appended claims.

Claims

1. A communication device comprising means for:receiving, from an access network node, a broadcast comprising network slice configuration information associated with a network slice instantiated by a core network based on a request from an application function; andinitiating, based on the network slice configuration information, establishment of a communication session within the network slice.

2. The communication device of claim 1, wherein the network slice configuration information comprises a network slice identifier associated with the network slice.

3. The communication device of claim 2, wherein initiating establishment of the communication session within the network slice comprises:sending, to the core network, a request to establish a communication session within the network slice, the request comprising the network slice identifier.

4. The communication device of any one of claims 1 to 3, wherein the network slice configuration information comprises one or more of: an area in which the network slice is available, a quality of service for the network slice, and timing information associated with the network slice, the timing information indicating a time when the network slice will be available and / or a duration the network slice will be available.

5. The communication device of any one of the preceding claims, wherein the network slice configuration information is received in a system information block, SIB.

6. The communication device of any one of the preceding claims, further comprising means for:receiving, from the access network node, a message indicating that the network slice has been de-instantiated; anddeleting, based on the message, the network slice configuration information associated with the network slice stored at the communication device.

7. The communication device of any one of the preceding claims, wherein the network slice is a temporary network slice.

8. A communication device comprising means for:receiving, from a core network, a message comprising network slice configuration information associated with a network slice instantiated by the core network based on a request from an application function; andinitiating, based on the network slice configuration information, a communication session within the network slice.

9. The communication device of claim 8, wherein the message is a NAS message.

10. A system for a core network, the system comprising a first network function for management and orchestration of network slices, the first network function configured for:receiving, from an application function, AF, a request to create a network slice, the request comprising first network slice configuration information;responsive to a determination that one or more trigger conditions for instantiating the network slice are satisfied, causing the network slice to be instantiated based on the first network slice configuration information; andsending, to a second network function for access and mobility management, second network slice configuration information associated with the network slice to be provided by the second network function to an access network node for broadcast to one or more user equipments, UEs, to enable the one or more UEs to initiate a communication session within the network slice, the second network slice configuration information comprising an identifier associated with the network slice.

11. The system of claim 10, further comprising means for:responsive to receiving the request comprising first network slice configuration information from the application function:authorising, based on the first network slice configuration information, creation of the network slice; andsending, to the application function, a response to the request, the response comprising an indication that the creation of the network slice is authorised, and an identifier of the network slice instantiated by the first network function.

12. The system of claim 10 or claim 11, wherein the first network slice configuration comprises the one or more trigger conditions.

13. The system of any one of claims 10 to 12, wherein the one or more trigger conditions comprise a time the network slice is to be instantiated.

14. The system of claim 11 or claim 12, wherein the request is indicative of a request to instantiate the network slice, and wherein the one or more trigger conditions are satisfied based on the request being received.

15. The system of any one of claims 10 to 14, further comprising means for: in response to a determination that one or more trigger conditions for deinstantiating the network slice are satisfied, causing the network slice to be deinstantiated; andsending, to the second network function, a message indicative of the network slice being de-instantiated to cause the broadcasting of the second network slice configuration information for receipt by the one or more UEs to be stopped.

16. The system of any one of claims 10 to 15, wherein the second network function is configured for:sending, to the access network node, the second network slice configuration information to cause the access network node to broadcast the second network slice configuration information to the one or more UEs and to store the second network slice configuration information at the access network node.

17. The system of claim 16, wherein the second network function is configured for: causing the access network node to broadcast the second network sliceconfiguration information in a system information block, SIB.

18. The system of claim 16 or claim 17, wherein the second network function is configured for:causing the access network node to broadcast the second network slice configuration information in an area specified in the first slice network configuration information.

19. The system of any one of claims 16 to 18, wherein the second network function is further configured for:receiving, from a UE of the one or more UEs, a request to establish a communication session within the network slice, the request comprising a network slice identifier associated with the network slice included in the second network slice configuration information.

20. An apparatus comprising an application function configured for: sending, to a network function of a core network, a request to create and / or instantiate a network slice, the request comprising network slice configuration5 information to cause the network function to respectively create and / or instantiate a network slice based on the network slice configuration information; andreceiving, from the network function, a response to the request, the response comprising an indication that the network slice has been created and / or instantiated respectively.1021. The apparatus of claim 20, wherein the response further comprises an identifier associated with the network slice.

22. The apparatus of claim 20 or claim 21, wherein the network slice configuration 15 information comprises one or more of: an area in which the network slice is to be available, a quality of service for the network slice, and timing information for when the network slice will be available.34

Images