Radio network node, managing node, core network node, system and methods performed therein

Abstract

According to some embodiments herein a method performed by a radio network node (120) for handling communication in a communication network. The radio network node (120) requests from a core network node (19), for information relating to an admission of a UE (10) to a network slice and / or a slice service. The radio network node (120) receives the requested information from the core network node (19).

Description

[0001] RADIO NETWORK NODE, MANAGING NODE, CORE NETWORK NODE, SYSTEM AND METHODS PERFORMED THEREIN

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a system, a radio network node, a core network node, a managing node, and methods performed therein for communication. Furthermore, a computer program and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to admission to a network slice or service of a network slice comprised in a communication network.

[0004] BACKGROUND

[0005] In a typical communication network, user equipments (UE), also known as wireless communication devices, mobile stations, stations (STA) and / or wireless devices, communicate via a Radio Access Network (RAN) with one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cell areas, with each service area or cell area being served by radio network node such as an access node e.g. a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node. The radio network node communicates over a downlink (DL) to the UE and the UE communicates over an uplink (UL) to the radio network node.

[0006] A Universal Mobile Telecommunications System (UMTS) is a third generation telecommunications network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and / or High-Speed Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and UTRAN specifically, and investigate enhanced data rate and radio capacity. In some RANs, e.g., as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) ora base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.

[0007] Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP and this work continues in the coming 3GPP releases, such as 5G networks for example New Radio (NR). The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network. As such, the RAN of an EPS has an architecture comprising radio network nodes connected directly to one or more core networks.

[0008] With the emerging 5G technologies such as new radio (NR), focus is on a set of features such as the use of very many transmit- and receive-antenna elements that make it possible to utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions. NR is connected to the 5G Core Network (5GC) which comprises a number of Network Functions (NF) such as Session Management Function (SMF), Access Management Function (AMF), Authentication Service Function (AUSF), Policy Control Function (PCF), Unified Data Manager (UDM), Network Repository Function (NRF), Network Exposure Function (NEF), just to mention some. In the 5GC, NFs can discover other NFs by using a discovery service provided by the NRF.

[0009] A key function of 5G Core network is to allow for flexibility in network service creation, making use of different network functions suitable for the offered service in a specific network slice, e.g., Evolved Mobile Broadband (MBB), Massive Machine Type Communication (MTC), Critical MTC, Enterprise, etc.

[0010] Slicing may also be used to isolate different services in an operator’s network. The goal of the network slice selection mechanism is therefore to direct a UE to the correct network slice as early as possible and to avoid re-direction from one network slice to another, which breaks the isolation between the network slices.

[0011] A network slice is a logical network serving a defined business purpose or customer, consisting of all required network resources end-to-end. This means that anetwork slice may consist of all Network Functions and both Control Plane and User Plane required to provide given service or services. Some functions may be shared, i.e., the same network function may be in multiple network slices, but a network slice may comprise all network functions and may not be just a subset.

[0012] The current working assumption is that there will be one shared or dedicated RAN infrastructure that will connect to several CN instances, with one or more shared NFs, interfacing the RAN, plus additional CN functions, which may be dedicated for a network slice. Network services supported on some specific network slices, defined by a Single Network Slice Selection Assistance Information (S-NSSAI), may be configured and preferably used in dedicated frequency layers. To have a more efficient way of signaling to UEs what network slices are configured on some frequency layer, one or more Network Slice Access Groups (NSAG) are introduced. The NSAG may be associated with a priority and that priority may be used by a UE to reselect to a specific frequency layer where some NSAG is configured and / or supported.

[0013] A UE may request over the non access stratum (NAS) protocol the use of a network slice identified by an S-NSSAI or the UE may request for one or more network slices to be registered by signaling the Registered NSSAI over NAS to the network.

[0014] TS 23.501 v.19.2.1 describes the following with regards to such a UE request: Start of excerpt from TS 23.501 v.19.2.1 :

[0015] When providing a Requested NSSAI to the network upon registration, the UE in a given public land mobile network (PLMN) only includes and uses S-NSSAIs applying to this PLMN. The mapping of S-NSSAIs of the Requested NSSAI to home (H) PLMN S-NSSAIs may also be provided, see clause 5.15.4.1.2 for when this is needed. The S-NSSAIs in the Requested NSSAI are part of the Configured and / or Allowed NSSAIs applicable for this PLMN, when they are available. If the UE has received NSSRG information together with the Configured NSSAI, it only includes in the Requested NSSAI S-NSSAIs that all share a common network slice simultaneous registered group (NSSRG). If the UE has stored Pending NSSAI and the UE is still interested in the Pending NSSAI then all the S-NSSAIs in the Requested NSSAI and the Pending S-NSSAI shall share a common NSSRG. If no Configured NSSAI and Allowed NSSAI for the PLMN are available, the S-NSSAIs in the Requested NSSAI correspond to the Default Configured NSSAI, if configured in the UE. Upon successful completion of a UE's Registration procedure over an Access Type, the UE obtains from the AMF an Allowed NSSAI or Partially Allowed NSSAI for this Access Type, which includes one or more S-NSSAIs and, if needed (see clause 5.15.4.1.2 for when this is needed), their mapping to the HPLMN S-NSSAIs. These S-NSSAIs are valid for the current Registration Area and Access Type provided by the AMF the UE has registered with and can be used simultaneously by the UE (up to the maximum number of simultaneous Network Slice instances or PDU Sessions).

[0016] The UE might also obtain from the AMF, one or more rejected S-NSSAIs with cause and validity of rejection. An S-NSSAI may be rejected:

[0017] for the entire PLMN;

[0018] for the current Registration Area; or

[0019] partially in the current Registration Area. Such S-NSSAI rejected partially in the current Registration area is associated with a list of tracking areas (TA) where the S-NSSAI is not supported.

[0020] The AMF may also reject the use of an S-NSSAI due to congestion as described in clause 5.19.7.4.

[0021] While the UE remains RM-REGISTERED in the PLMN and regardless of the Access Type, the UE shall not re-attempt to register to an S-NSSAI rejected for the entire PLMN until this rejected S-NSSAI is deleted as specified below.

[0022] End of excerpt from TS 23.501 v.19.2.1.

[0023] As it can be seen from the above, the UE may be denied or rejected a request to access a network slice by means of receiving a Rejected S-NSSAI.

[0024] If an S-NSSAI is allowed to be used for the UE, the CN may trigger resource allocation at the RAN for a protocol data unit (PDU) Session associated with such S-NSSAI. However, such resource allocation may not be admitted by the RAN because the network slice is not available in the area where the request was made. This implies that, in such area, the network slice has zero resources allocated in the corresponding cells.

[0025] Self-Organizing Networks (SON) is a collection of functions for automatic configuration, optimization, and / or healing of networks. The aim of the SON framework is to perform routine maintenance and optimization where necessary without additional configuration. To enable this functionality, multiple reports are defined and collected from the UE. Some relevant ones are introduced in the following:

[0026] Random Access (RA) report.

[0027] A RA report is generated by the UE upon performing a random-access procedure. The UE may perform such RA procedure to perform statechanges from RRCJdle to RRC_Connected. The LIE may also perform random access while performing a handover. A UE may log up to 08 RA reports in the memory and may transmit them to network upon reception of network request.

[0028] Connection establishment failure (CEF) report.

[0029] A CEF report is generated by the UE upon failure to perform a connection establishment from RRCJdle to RRC_Connected state. A UE may log up to 04 CEF reports and may transmit them to network upon reception of network request.

[0030] Mobility History Information (MHI) report

[0031] A MHI report comprises visited primary cell (PCell) and primary secondary cell (PSCell) information and a time a UE stayed in those cells. A UE capable of generating MHI reports logs these pieces of information in both RRCJdle and RRC_Connected state. According to current standard, the UE may log up to 16 PCell and 16 PSCell information.

[0032] Minimization of Drive tests (MDT) was standardized for NR in Rel-16 to reduce the amount of drive tests performed manually. It is a UE assisted framework where network measurements are collected by both IDLE / INACTIVE and radio resource control (RRC) Connected UE(s) in order to aid the network in gathering valuable information. It has been specified for both LTE and NR in TS 37.320 v18.3.0.

[0033] In general, there are two types of MDT measurement logging, i.e., Logged MDT and Immediate MDT.

[0034] Immediate MDT comprises collection of measurements from an RRC_Connected UE. Measurements for Immediate MDT purposes may be performed by RAN and the UE. There are a number of measurements, denoted as M1-M9, which are specified for RAN measurements and UE measurements. For the UE measurements, the MDT configuration is based on the existing RRC measurement procedures for configuration and reporting with some extensions for location information. Further details may be found in TS 37.320 v.18.3.0.SUMMARY

[0035] As part of developing embodiments herein one or more issues have been identified. In 5G, network slices may be uniformly available across a Registration Area (RA), or the network slices may be available within a whole Tracking Area (TA) within a RA, or the network slices may be available at a specific cell within the RA.

[0036] As explained above, although a network slice may be supported at a given cell, the cell may have no resources allocated to the network slice. This mechanism where a network slice is supported in a cell, but has no resources allocated, allows the operator to deploy network slices in the network for specific geographical locations that do not necessarily map to TA coverage areas, e.g., shopping mall, and / or stadium.

[0037] However, configuring a perfect match between the coverage of the cells in which a network slice is supported and available and the geographical areas where the users should have access to the services provided by a network slice is challenging in some cases and creates mismatches. As a consequence, and to enable observability of such mismatches between network slice availability areas and areas where network slice services are needed, it is important to understand from which geographical areas UEs may request to access services over a certain network slice, and if the network slice deployment must be changed to satisfy such requests.

[0038] For example, an operator is providing services over a certain network slice for an enterprise customer such that the employees of the enterprise customer can access network slice services, i.e., an enterprise slice, for work-related purposes. The users may request access to the network slice services while working from the office premises of their employer but also while working remotely from home. While configuring a good overlap between the network slice coverage and the customer’s office premises is rather easy, it may be difficult to configure a good slice coverage overlapping with the remote working location of each employee.

[0039] If the UE is in a cell and the UE requests for a service or services mapped to network slices which are unavailable, the UE gets a rejection from the network and if the UE receives a respective rejection for all requested network slices, the UE may be forced back to RRC IDLE state. However, the list of rejected or accepted network slice information is transferred between the AMF and UE(s) over NAS messages. Hence, the radio network node is unaware of the problem faced by the UE or UEs.An object of embodiments herein is to provide a mechanism for enabling communication, such as managing network slices and / or services related to a network slice, in a communication network in an efficient manner.

[0040] According to an aspect the object is achieved by providing a method performed by a radio network node for handling communication such as usage of a slice service in a communication network. The radio network node requests for information from a core network node. The information relates to an admission of a LIE to a network slice and / or a slice service. The radio network node receives from the core network node, the requested information for the LIE. Thus, the radio network node may fetch NAS level LIE slice service requests information from the core network node.

[0041] According to another aspect the object is achieved by providing a method performed by a core network node for handling communication such as usage of a slice service in a communication network. The core network node receives from a radio network node, a request for information of a LIE. The information relates to an admission of a UE to a network slice and / or a slice service. The core network node transmits to the radio network node, the requested information for the UE.

[0042] According to yet another aspect the object is achieved by providing a method performed by a managing node for handling communication such as usage of a service in a communication network. The managing node receives from a radio network node information for a UE. The information relates to an admission of a UE to a network slice and / or a slice service. The managing node further performs an operation taking the information into account.

[0043] It is furthermore provided herein a computer program comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out any of the methods herein, as performed by the managing node, the core network node, or the radio network node, respectively. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the managing node, the core network node, or the radio network node, respectively.

[0044] According to yet another aspect the object is achieved, according to embodiments herein, by providing a radio network node, a managing node, and a core network node configured to perform the methods herein, respectively.

[0045] Thus, according to an aspect the object is achieved by providing a radio network node for handling communication such as usage of a slice service in a communicationnetwork. The radio network node is configured to request for information from a core network node. The information relates to an admission of a LIE to a network slice and / or a slice service. The radio network node is configured to receive from the core network node, the requested information for the UE.

[0046] According to another aspect the object is achieved by providing a core network node for handling communication such as usage of a slice service in a communication network. The core network node is configured to receive from a radio network node, a request for information of a UE. The information relates to an admission of a UE to a network slice and / or a slice service. The core network node is configured to transmit to the radio network node, the requested information for the UE.

[0047] According to yet another aspect the object is achieved by providing a managing node for handling communication such as usage of a service in a communication network. The managing node is configured to receive from a radio network node information for a UE. The information relates to an admission of a UE to a network slice and / or a slice service. The managing node is configured to perform an operation taking the information into account.

[0048] An essence of embodiments herein is the interaction between OAM, being an example of the managing node, RAN and Core network entities to fetch the information, also referred to as NAS level UE slice service requests information, from the core network. Embodiments are not dependent on the UE. Some embodiments further outline how the radio network node may utilize the information to optimize its performance.

[0049] Embodiments herein create visibility in the radio network node and the managing node regarding UEs receiving NAS slice rejection or rejections. The radio network node may re-direct one or more UEs to a different cell where network slice access is available through Idle mode cell reselection or handover. Furthermore, since slice deployment is controlled by the managing node, creating an observability for the managing node would enable the managing node to change or optimize slice deployment. Furthermore, the embodiments herein may enable less service interruption at the UE side. Thus, embodiments herein enable communication, such as enabling service related to a network slice, in the communication network in an efficient manner.

[0050] BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Embodiments will now be described in more detail in relation to the enclosed drawings, in which:Fig. 1 is a schematic overview depicting a communication network according to embodiments herein;

[0052] Fig. 2A is a combined flowchart and signaling scheme according to embodiments herein;

[0053] Fig. 2B is a combined flowchart and signaling scheme according to embodiments herein;

[0054] Fig. 3A is a flowchart depicting a method performed by a UE according to embodiments herein;

[0055] Fig. 3B is a flowchart depicting a method performed by a radio network node according to embodiments herein;

[0056] Fig. 3C is a flowchart depicting a method performed by a managing node according to embodiments herein;

[0057] Fig. 4A is a flowchart depicting a method performed by a UE according to embodiments herein;

[0058] Fig. 4B is a flowchart depicting a method performed by a radio network node according to embodiments herein;

[0059] Fig. 4C is a flowchart depicting a method performed by a managing node according to embodiments herein;

[0060] Fig. 5A is a flowchart depicting a method performed by a radio network node according to embodiments herein;

[0061] Fig. 5B is a flowchart depicting a method performed by a core network node according to embodiments herein;

[0062] Fig. 5C is a flowchart depicting a method performed by a managing node according to embodiments herein

[0063] Fig. 6 is a block diagram depicting a UE according to embodiments herein; Fig. 7 is a block diagram depicting a radio network node according to embodiments herein;

[0064] Fig. 8 is a block diagram depicting a managing node according to embodiments herein;

[0065] Fig. 9 is a block diagram depicting a core network node according to embodiments herein;

[0066] Fig. 10 shows an example of a communication system 15100 in accordance with some embodiments;

[0067] Fig. 11 shows a communication system 15200 in accordance with some

[0068] embodiments;Fig. 12 shows a LIE 15300 in accordance with some embodiments;

[0069] Fig. 13 is a block diagram of a network node 15400 in accordance with various aspects described herein; and

[0070] Fig. 14 is a block diagram illustrating a virtualization environment 15500 in which functions implemented by some embodiments may be virtualized.

[0071] DETAILED DESCRIPTION

[0072] Embodiments herein relate to communication networks in general. Fig. 1 is a schematic overview depicting a communication network 1. The communication network 1 comprises a wireless communication network comprising one or more RANs and one or more CNs. The communication network 1 may use a number of different technologies, such as Wi-Fi, Long Term Evolution (LTE), LTE-Advanced, NR, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / Enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations. Embodiments herein relate to recent technology trends that are of particular interest in a 5G context, however, embodiments are applicable also in further development of the existing communication systems such as e.g. WCDMA and LTE or, or upcoming technologies, for example, for 6G RAN nodes.

[0073] In the communication network 1 , wireless devices e.g. a user equipment (UE) 10 such as a mobile station, a non-access point (non-AP) STA, a STA, a wireless device and / or a wireless terminal, communicate via one or more Access Networks (AN), e.g. RAN, to one or more core networks (CN). It should be understood by those skilled in the art that “UE” is a non-limiting term which means any terminal, wireless communication terminal, internet of things (loT) capable device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node, e.g., smart phone, smart watch, smart glasses, vehicle, laptop, mobile phone, sensor, relay, mobile tablets or even a base station communicating within a cell.

[0074] The communication network 1 comprises a first radio network node 12 providing radio coverage over a geographical area, a first service area or first cell 11 , of a first radio access technology (RAT), such as 6G, NR, LTE, UMTS, Wi-Fi or similar. The first radio network node 12 may be a radio access network node such as radio network controller or an access point such as a wireless local area network (WLAN) access point or an Access Point Station (AP STA), an access controller, a base station, e.g. a radio base station such as a NodeB, an eNodeB, a gNodeB (gNB), a base transceiver station, Access PointBase Station, base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of serving a UE within the service area served by the first radio network node 12 depending e.g. on the first radio access technology and terminology used. The first radio network node 12 may be denoted as serving RAN node, serving node, source node, or just radio network node 12.

[0075] The communication network 1 comprises a second radio network node 13 providing radio coverage over a geographical area, a second service area, or second cell 14, of a second RAT, such as 6G, NR, LTE, UMTS, Wi-Fi or similar. The second radio network node 13 may be a radio access network node such as radio network controller or an access point such as a wireless local area network (WLAN) access point or an Access Point Station (AP ST A), an access controller, a base station, e.g. a radio base station such as a NodeB, an eNodeB, a gNodeB (gNB), a base transceiver station, Access Point Base Station, base station router, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit capable of serving a UE within the service area served by the second radio network node 13 depending e.g. on the second radio access technology and terminology used. The second radio network node 13 may be denoted as target RAN node, neighboring node, target node or radio network node.

[0076] It should be noted that the communication network 1 comprises a core network (CN) and / or RAN that are virtually network sliced into a number of slices also referred to as network slices, each network slice or RAN / core network slice supports a type of UEs and / or a type of services i.e. each network slice supports a different set of functionalities. Network slicing introduces the possibility that the network slices are used for different services and use cases and these services and use cases may introduce differences in the functionality supported in the different network slices. Each network slice may comprise one or more network nodes or elements of network nodes providing the services and / or functionalities for the respective network slice. Each slice may comprise one or more network nodes. For example, a first network slice for, e.g., massive MTC devices may comprise a first network node 16. A second network slice for, e.g., critical MTC devices may comprise a second network node 17. A third network slice for, e.g., MBB devices may comprise a third network node 18. Each network slice supports a set of functionalities out of a total set of functionalities in the communication network. E.g. the first network node 13 supports a first set of functionalities out of the total set of functionalities in the communication network 1. The first set of functionalities is separated from a different set of functionalities out of the total set of functionalities in the communication network 1. E.g., the first set of functionalities being associated withMassive MTC devices is separated or logically separated from a second set of functionalities of the second network slice. Examples herein may cover any of the referenced network nodes. The first set of functionalities may use one or more resources in a core network and / or a RAN of the communication network, which one or more resources are separated from other resources used by a different set of functionalities, i.e., different network slices, out of the total set of functionalities in the communication network 1. The resources may then be dedicated or virtually dedicated for each set of functionalities or network slice. Thus, the first network node 16 is separated from other network nodes supporting a second set of functionalities out of the total set of functionalities in the communication network. Separated as used herein means physical separated wherein the network nodes may be executed on different hardware platforms and therefore using different resources of the hardware, and logically separated wherein the network nodes may be executed on a same hardware platform and use different resources such as memory parts or resources of processor capacity but may also use some same resources of the hardware e.g. a single physical network node may be partitioned into multiple virtual network nodes.

[0077] A managing node 15 such as an OAM node (or just OAM) and / or trace collection entity (TCE) may be comprised in the communication network 1. The managing node 15 may configure a radio network node 120, such as the first radio network node 12 and / or the second radio network node 13, to log and / or report MDT related information.

[0078] The managing node 15 may further communicate with a core network node 19 such as an AMF, Mobile Management Entity (MME) or similar.

[0079] Embodiments herein propose multiple solutions to create visibility in the RAN nodes and OAM nodes for service requests. Such visibility consists of but not limited to LIE requested S-NSSAI related information, NAS rejected S-NSSAI information etc. The information requested, according to embodiments herein, may thus be related to an admission of the UE 10 to a network slice and / or a slice service. For example, the information may be for one or more rejected NSSAIs for the UE 10.

[0080] Solution-3:

[0081] Solution-3 is a network-based solution involving RAN, i.e., the radio network node 120, the Core network, such as an AMF, and the managing node 15 such as an OAM system. Thus, according to embodiments herein, dependency on the UE 10 is avoided. The RAN may request for NAS level UE slice service requests information from the AMF. Upon reception of the information, the radio network node 120 may enhance the information with additional information and may forward to the managing node 15.Furthermore, according to some embodiments herein, the radio network node 120 may steer the UE 10 to one or more cells where the UE 10 would be able to get the requested one or more slice services. Thus, the radio network node 120 may minimize service rejections received by the UE 10.

[0082] An advantage with embodiments herein is to create visibility in the radio network node 120 and the managing node 15 (such as OAM) regarding UE receiving NAS slice rejection or other related slice information, such as acceptance or slice service. The radio network node 120 may re-direct the UE 10 to a different cell where slice access is available through Idle mode cell reselection or handover. Furthermore, since slice deployment is controlled by the managing node 15, creating an observability for the managing node 15 would enable the managing node 15 to change or optimize slice deployment.

[0083] Furthermore, the solution enables less service interruption at the UE side.

[0084] Solution-1 :

[0085] An essence of solution-1 is the indication to UE to log NAS level UE slice service requests information into an MDT report and forward it to network. The solution-1 outlines different methods of transmitting such indication to the UE 10 along with different conditions when UE should log them.

[0086] Solution-1 consists of configuring the UE 10 with an indication to log NAS level UE slice service requests information (NAS slice rejection information or some other information) in the memory and collection of the information using the MDT framework. Ther radio network node 120 may configure the UE with an additional MDT configuration of the indication and utilize current MDT framework or a new framework to collect the information from UE 10.

[0087] On the network side, the managing node 15 such as the OAM utilizes the current trace framework to enable such configuration by the RAN such as radio network node 120.

[0088] Solution-2:

[0089] An essence of the solution-2 is UE logging NAS level UE slice service requests information in SON reports or a new report. Some embodiments outline interaction between network and UE to log and fetch such reports from the UE.

[0090] On the network side, the essence is the interaction between the managing node such as operation, administration and management (OAM), and RAN. Differentembodiments describe such interaction. Some embodiments further outline how the network can utilize these reports for optimization of network performance.

[0091] Solution-2 consists of utilizing existing SON reports such as MHI, RA, CEF report or creating a new SON report to collect NAS level UE slice service requests information (NAS slice rejection or some other slice related information). In this solution, no explicit indication from the network is expected as the UE is mandated to collect them according to standard. Once the UE 10 collects such slice related information, different embodiments of the solution outlines how it indicates the availability to network. Network may fetch the report from the UE 10 using current standard procedures.

[0092] This solution further details the interaction between OAM and RAN, i.e., radio network node 120. The OAM system may utilize the trace framework to indicate the necessity of the information. The RAN may collect the reports from the UE 10 and forwards to OAM. However, the counters created by OAM system can also be utilized. In this case, the OAM creates counters in the RAN nodes and the latter upon fetching the reports from the UE, updates the counter according to OAM settings and received reports.

[0093] Furthermore, the solution outlines some action that can be performed by the RAN to steer the UE 10 in cells where it would be able to get the requested services. Thus, RAN node minimizes the service rejections received by the UE 10.

[0094] Radio network node and RAN node are used interchangeably herein. A nonlimiting example of a radio network node or a RAN node may be any of: eNB, gNB, gNB-central unit (CU), gNB-CU-control plane (CP), gNB-CU-user plane (UP), gNB-distributed unit (DU).

[0095] The term wireless terminal / device and UE are interchangeable and refers to any device capable of being served / used by a network node, e.g. the radio network node 120.

[0096] Embodiments may be applicable for virtual RAN (vRAN) slice as well as virtual core (vCORE) slices.

[0097] The description of the methods herein applies to Radio Access Networks supporting network slicing. Without loss of generality, the descriptions are detailed by taking a 5G system into account. However, the methods can be applied to any system supporting network slicing.

[0098] In the remaining parts the term network node is used to specify any of the following entities: a logical node, a function, a system.

[0099] In this description the term “list of network slices” is used. This term not only indicates a list of network slice identifiers NSSAIs, but it can also refer to one or moreNSAG IDs, namely Network Slice Access Stratum Group identifier, representing a group of slices.

[0100] It should be noted that a slice is available in a coverage area if the slice is supported by the cell serving the area and if resources for the slice are available to serve services associated to the slice. On the other hand, a network slice may be supported within a cell, but not be available because no resources are available for the slices.

[0101] In this description the term “admission control failure” refers to cases where the RAN node in charge of assigning resources for traffic bearers decides not to allocate resources to a given bearer. For “bearer” it is intended any means to instruct the RAN of the establishment of data channels to serve services at the UE, namely a “bearer” could be a PDU Session, a quality of service (QoS) Flow, a data radio bearer (DRB) and similar.

[0102] Fig. 2A is a combined flowchart and signaling scheme according to some embodiments herein exemplifying one embodiment herein.

[0103] Action 201. The managing node 15, such as an OAM, may configure, directly or via a ON node, the radio network node 120 with a configuration for reporting MDT indicating to the radio network node 120 to log NAS level UE slice service requests information such as MDT information.

[0104] Action 202. The radio network node 120 may transmit an indication such as a configuration to the UE 10 to configure the UE 10 with the indication to log NAS level UE slice service requests information into an MDT report and forward the NAS level UE slice service requests information to a network node such as the radio network node 120. The indication may be received from the network node along with one or more conditions defining when UE is to log the NAS level UE slice service requests information. Thus, the UE may log and / or send information indicating, where a network slice or a network slice service was requested by the UE, that such request resulted in a rejection.

[0105] Action 203. The UE 10 logs the NAS level UE slice service requests information as being configured by the indication, alternatively, the UE 10 may be mandated to collect the NAS level UE slice service requests information according to standard. Once the UE 10 collects such slice related information, different embodiments outline how it indicates the availability to network.

[0106] Action 204. The UE 10 may report the NAS level UE slice service requests information to the radio network node 120. The UE 10 may report information indicating, where a network slice or a network slice service was requested by the UE, that such request resulted in a rejection. For example, the UE 10 may report to the RAN, upon radionetwork node request, events where a network slice or a network slice service was requested by the UE while under the coverage of the radio network node’s cells and where such requests resulted in a rejection by the Core Network (Non Access Stratum network level rejection).

[0107] Action 205. The radio network node 120 may log and / or store information relating to admission to a network slice and / or slice service, such as the NAS level UE slice service requests information. The NAS level UE slice service requests information may comprise a cause indication in case of non-admission.

[0108] Action 206. The radio network node 120 may send, to the managing node 15, the information related to the admission to a network slice and / or slice service such as the NAS level UE slice service requests information. For example, the radio network node 120 may log and / or send in an MDT trace one or more instances of resource allocation for a PDU Session associated to an S-NSSAI that were not admitted. The MDT trace comprises an indication for differentiating between a case where the admission failure was due to lack of slice availability, and a case where the admission failure was due to exhaustion of resources for the network slice.

[0109] Action 207. The managing node 15 may perform an operation taking the information into account. For example, the managing node 15 may update slice information such as network slice support and network slice availability based on the received information.

[0110] Fig. 2B is a combined flowchart and signaling scheme according to some embodiments herein performed in a system.

[0111] Action 211. The managing node 15, such as an OAM, may configure, directly or via a CN node, the radio network node 120 with a configuration for reporting MDT indicating to the radio network node 120 to log information such as MDT information.

[0112] Action 212. The radio network node 120 requests the core network node 19, for information relating to an admission of the UE 10 to a network slice and / or a slice service.

[0113] Action 213. The core network node 19 transmits the requested information to the radio network node 120.

[0114] Action 214. The radio network node 120 may take into account the information when configuring one or more parameters of a cell selection that is slice based.

[0115] Action 215. Alternatively, or additionally, the radio network node 120 may forward the information to the managing node 15.Action 216. The managing node 15 may perform an operation taking the information into account. For example, the managing node 15 may update slice information such as network slice support and network slice availability based on the received information.

[0116] SOLUTION 1

[0117] The method actions performed by the UE 10 for handling communication such as network slices and / or services in the communication network according to embodiments will now be described with reference to a flowchart depicted in Fig. 3A. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features.

[0118] Action 301. The UE 10 obtains an indication of configuration for logging and / or sending NAS level UE slice service requests information to the radio network node 120. The indication may be received from the radio network node 120 and / or be preconfigured. For example, while the UE 10 in RRC Idle state performs random access procedure to the radio network node 120 to transition to RRC Connected state, the UE 10 may receive from the radio network node 120 configuration data for configuring the UE to collect rejected slice information.

[0119] Action 302. The UE 10 may perform an admission procedure to the network slice or a service of the network slice. The UE 10 may request a network slice or a network slice service. The request may be rejected.

[0120] Action 303. The UE 10 logs and / or sends NAS level UE slice service requests information to the radio network node 120, such as information indicating, where a network slice or a network slice service was requested by the UE, that such request resulted in a rejection. For example, the UE 10 may report to the radio network node 120, upon radio network node request, events where a network slice or a network slice service was requested by the UE 10 while under the coverage of the radio network node’s cells and where such request resulted in a rejection by the Core Network, such as a Non Access Stratum network level rejection.

[0121] UE Embodiments:

[0122] In the main embodiment of this solution 1 , while a UE in RRC Idle state performs random access procedure to a network node (e.g., a gNB) to transition to RRC Connected state, the network node (e.g., the gNB) configures the UE to collect rejected slice information. Upon collection of the rejected slice(s) information, UE reports it to gNB.In an embodiment, the radio network node 120 provides the LIE with a first indication that configures / instructs the UE to log NAS slice rejection information in memory. Example of the information could be S-NSSAIs included in the Rejected NSSAI, or S-NSSAIs for which services were rejected at NAS level. A gNB can provide UE with this indication in msg4 (contention resolution) of RA procedure.

[0123] In one embodiment a network node (e.g., a gNB) sends an RRC message (e.g. an RRCSetup message) to a UE comprising an indication (e.g., a flag) that instructs the UE to log NAS related information concerning the access to a network slice.

[0124] Logging NAS related information can be one or more of:

[0125] - logging events where the UE triggers a service request for one or more network slice. As part of this, the UE may log the S-NSSAI of each slice for which a service request has been signaled

[0126] - logging failures / rejections to request a service for one or more network slices.

[0127] As part of this, the UE may log the S-NSSAI of each slice for which a service request has been signaled,

[0128] - logging events where the UE triggers a service request for a specific (e.g., default) network slice. As part of this, the RAN may configure the UE with the network slice identifier for which the events need to be logged,

[0129] - logging failures / rejections to request a service for a specific (e.g., default) network slice. As part of this, the RAN may configure the UE with the network slice identifier for which the events need to be logged,

[0130] - logging events where the UE triggers a service request for any network slice, - logging failures / rejections to request a service for any network slices.

[0131] With the configuration received, the UE 10 is tasked to collect the events listed above that are consequence of a service request performed by the UE at the time of accessing the network, i.e. when the UE moves from RRCJdle / lnactive to RRC_Connected, as well as the events listed above that may occur as a consequence of service requests triggered while the UE is in RRC_Connected. In this example, the first indication may be transmitted by the network as part of RRC connection setup procedure, e.g. within the RRC Connection Setup message, or as part of the RRC Resume procedure, or as part of MAC control element transmitted by the network during the random-access procedure, e.g. in the Random access response MAC control element.

[0132] In another embodiment, the gNB configures the UE with immediate MDT configuration to store the rejected slice information. Immediate MDT configuration maybe configured to the UE at the same time when the first indication is provided to the UE or at a later stage. In an alternative, the first indication is considered as the immediate MDT configuration. In the latter case, the first indication may be transmitted once the UE is in connected mode, e.g. as part of a radio measurement reporting configuration.

[0133] In a depending embodiment, if the first indication received by the UE is different from the immediate MDT configuration, the first indication will task the UE to log the events listed above for service requests performed by the UE at the time of accessing the network, i.e. when the UE moves from RRCJdle / lnactive to RRC_Connected, while the Immediate MDT configuration tasks the UE to log the events listed above that may occur as a consequence of service requests triggered while the UE is in RRC_Connected.

[0134] In a depending embodiment, if the first indication is considered as the immediate MDT configuration, such configuration is used to task the UE to collect the events listed above that are consequence of a service request performed by the UE at the time of accessing the network, i.e. when the UE moves from RRCJdle / lnactive to RRC_Connected, as well as the events listed above that may occur as a consequence of service requests triggered while the UE is in RRC_Connected.

[0135] In another embodiment, if the first indication is used to task the UE to collect the events listed above when the UE moves from RRCJdle / lnactive to RRC_Connected, the said first indication is transmitted as part of a logged MDT measurement configuration which is transmitted to the UE while in RRC connected mode prior to enter RRCJDLE or RRCJnactive stated. In this case, the UE keeps the said first indication configuration while in RRCJDLE / INACTIVE, and it logs the events listed above when the UE moves again from RRCJdle / lnactive to RRC_Connected.

[0136] Once the UE has logged the events and information configured by the RAN, the UE sends the logged information to a serving gNB as part of a current standardized message or a new message. For example:

[0137] • If gNB configures the UE with immediate MDT configuration in a RRCReconfiguration message, UE may include logged event information in the corresponding RRCReconfiguration complete message.

[0138] • If gNB configures the UE with logged MDT configuration in an RRCReconfiguration message, UE may include logged event information in the RRCReconfiguration complete message transmitted after moving from RRCJdle / lnactive to RRC_Connected.• On the other hand, in another option, the UE 10 may store the logged information in a new UE report, such as a Service Failure Report (SFR), or a Non Access Stratum, NAS, Failure Report (NFR), or similar and may send it to the network using UElnformationResponse message upon reception of a corresponding UElnformationRequest message from the network.

[0139] o gNB may send the UElnformationRequest message upon reception of an availability indication from the UE where the UE includes this availability information as part of UEAssistancelnformation message. o In order for the network (e.g., a gNB towards which the UE attempts to connect from RRC Idle, or from RRC Inactive state, including a gNB that differs from the gNB serving the UE when it earlier on transitioned from RRC Connected to RRC Idle or from RRC Inactive to RRC Idle) to know the availability of the information associated to the events listed above, the UE may signal in several different messages the availability of such information, e.g. in any RRC complete message, or such as RRCReconfigurationComplete, RRCResumeComplete, or RRC Reestablishment complete etc.

[0140] In one embodiment, the UE 10 logs the configured information only for RRC Idle to RRC Connected state transitions. This behavior may have been configured explicitly by the network, or the UE 10 is instructed to do so by standard specification.

[0141] In one embodiment, the UE logs configured information for RRC Idle to RRC Connected state transitions and for mobility in RRC Connected state. This behavior may have been configured explicitly by the network, or the UE is instructed to do so by standard specification.

[0142] In one embodiment, if the UE is tasked to log configured information for RRC Idle to RRC Connected state transitions, the first indication is transmitted as part of a logged MDT measurement configuration. In another embodiment if the UE is tasked to log configured information for mobility in RRC Connected state, or more in general whenever a service request is initiated when the UE is already in RRC_CONNECTED mode, the first indication is transmitted as part of an immediate MDT measurement configuration, or radio measurement reporting configuration.

[0143] The method actions performed by the radio network node 120 for handling communication such as network slices and / or services, in the communication networkaccording to embodiments will now be described with reference to a flowchart depicted in Fig. 3B. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features.

[0144] Action 311. The radio network node 120 may receive, from the managing node 15 or a CN node, a configuration for reporting MDT indicating to the radio network node 120 to log information such as MDT information. Additionally, or alternatively, configuration may comprise a request for the radio network node 120 to configure the UE 10 with measurements and logs for the events in which the UE requests over NAS to be registered to the network slice or to access a service for the network slice, but the CN rejects the UE to access such network slice.

[0145] Action 312. The radio network node 120 transmits the indication to the UE 10 of configuration for logging and / or sending NAS level UE slice service requests information to the radio network node 120. The radio network node 120 may transmit request to the UE 10 to configure the UE 10 to log and / or send information for the events in which the UE requests over NAS to be registered to the network slice or to access a service for the network slice. The radio network node 120 may provide the UE with this indication in msg4 (contention resolution) of RA procedure.

[0146] Action 313. The radio network node 120 receives the NAS level UE slice service requests information from the UE 10. The radio network node 12 may receive report information indicating, where a network slice or a network slice service was requested by the UE. For example, the radio network node 120 may receive a report from the UE 10, upon radio network node request, events where the network slice or the network slice service was requested by the UE 10 while under the coverage of the radio network node’s cells and where such request resulted in a rejection by the Core Network, such as a Non Access Stratum network level rejection.

[0147] Action 314. The radio network node 120 may further send report information relating to admission to the network slice and / or the slice service to the managing node 15.

[0148] The method actions performed by the managing node 15 for handling communication such as network slices and / or services, in the communication network according to embodiments will now be described with reference to a flowchart depicted in Fig. 3C. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features.Action 321. The managing node 15 may transmit to the radio network node 120, the configuration for reporting MDT indicating to the radio network node 120 to log information such as MDT information. The managing node 15 may transmit a request to the radio network node 120 to collect such information. Such request might be included in an MDT configuration.

[0149] Action 322. The managing node 15 may receive report information relating to admission to the network slice and / or the slice service from the radio network node 12.

[0150] Action 323. The managing node 15 may perform an operation taking the report information into account.

[0151] Network Embodiments:

[0152] In network side, multiple network entities (nodes) can be involved. These entities in coordination enables collection of the configured slice information from the UE.

[0153] In an embodiment, OAM sends a request to gNB to collect such information. Such request might be included in an MDT configuration. Upon reception of the request, gNB sends any of the indication, the immediate MDT configuration or both to the UE. Such a request from OAM can for example be sent via existing trace mechanisms.

[0154] SOLUTION 2

[0155] The method actions performed by the UE 10 for handling communication such as network slices and / or services in the communication network according to embodiments will now be described with reference to a flowchart depicted in Fig. 4A. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features.

[0156] Action 401. The UE 10 obtains configuration to configure the UE 10 to log information related to slice service access (e.g. related to slice rejection at NAS level), also referred to as NAS level UE slice service requests information, as additional information into existing SON report(s) such as the mobility history information (MHI) report or the Random Access (RA) report or the Connection Establishment Failure (CEF) report. The configuration may be received from the radio network node 120 and / or be preconfigured. For example, while the UE 10 in RRC Idle state performs random access procedure to the radio network node 120 to transition to RRC Connected state, the UE 10receives from the radio network node 120 configuration data for configuring the LIE to collect information.

[0157] Action 402. The LIE 10 may perform an admission procedure to the network slice or a service of the network slice. The LIE 10 may request a network slice or a network slice service.

[0158] Action 403. The LIE may log and / or send information related to slice service access (e.g. related to slice rejection at NAS level), also referred to as NAS level UE slice service requests information, as additional information into existing SON report.

[0159] UE Embodiments:

[0160] In an embodiment of this solution, the UE 10 is configured to log new information related to slice service access (e.g. related to slice rejection at NAS level) as an additional information into existing SON report(s) such as the mobility history information (MHI) report or the Random Access (RA) report or the Connection Establishment Failure (CEF) report.

[0161] Similar to Solution 1 , the events to be logged by the UE for solution 2 may be: events where the UE triggers a service request for one or more network slice. As part of this, the UE may log the S-NSSAI of each slice for which a service request has been signaled

[0162] failures / rejections to request a service for one or more network slices. As part of this, the UE may log the S-NSSAI of each slice for which a service request has been signaled,

[0163] events where the UE triggers a service request for a specific (e.g., default) network slice. As part of this, the RAN may configure the UE with the network slice identifier for which the events need to be logged,

[0164] failures / rejections to request a service for a specific (e.g., default) network slice. As part of this, the RAN may configure the UE with the network slice identifier for which the events need to be logged,

[0165] events where the UE triggers a service request for any network slice, failures / rejections to request a service for any network slices.

[0166] In one embodiment (collection option 1), the UE logs slice information only for RRC ldle / RRC_lnactive to RRC Connected state transitions. This behavior may have been configured explicitly by the network, or the UE is instructed to do so by standard specification.In one embodiment (collection option 2), the UE logs slice information collected at mobility events in RRC Connected state. This behavior may have been configured explicitly by the network, or the UE is instructed to do so by standard specification.

[0167] In one embodiment (collection option 3), the UE logs slice information collected at any NAS level service request triggered while in RRC_Connected. This behavior may have been configured explicitly by the network, or the UE is instructed to do so by standard specification.

[0168] The three collection option methods can be configured / carried out by the UE separately or in combination one with the other. For example, the UE could be configured to log slice information for slice service requests occurring at RRCJdle to RRC_Connected transitions and during RRC_Connected mode.

[0169] Upon logging of one or more of the events above using the collection options, e.g., slice rejection from the network or NAS layer, UE stores the information in one or more SON report, such as in the MHI under the PCell information, in RA report, in CEF report or in a new UE report, such as a Service Failure Report (SFR), or a Non Access Stratum, NAS, Failure Report (NFR), or similar. Upon collection of the SON report(s), such as the MHI, RA report, CEF report, or the new report from the UE, network can gather the slice information per cell.

[0170] A UE capable of logging such information indicates the capability to network and thus network is aware of the UEs from which it should collect MHI, RA report, CEF report or the new report in order to fetch rejected slice information.

[0171] In an embodiment, UE indicates to a network node (e.g., gNB), e.g., in the UECapabilitylnformation RRC message, the capability of storing Non-Access Stratum (NAS) related information, including information that can be used by the RAN (or for RAN optimization purposes), such as rejected slice information, and the network node stores such information in the UE context.

[0172] In another embodiment, UE indicates that it has rejected slice information available, or that is has stored rejected slice information, or that it has available / stored slice information as part of a given SON report. For instance, the UE sends to the network an indication, together with the indication that a certain SON report is available, indicating that the SON report contains rejected slice information. For example, if the UE stored the rejected slice information as part of the MHI report, the UE sends to the network an indication that it has available rejected slice information in the MHI report along with the indication of availability of the MHI report.In another embodiment, LIE indicates the network regarding availability of a new report, such as a Service Failure Report (SFR), or a Non-Access Stratum, NAS, Failure Report (NFR) using a RRC message. Examples of such message can be RRCSetupComplete, RRCReconfigurationComplete, RRCResestablishmentComplete, UEAssistancelnformation messages.

[0173] The method actions performed by the radio network node 120 for handling communication such as network slices and / or services, in the communication network according to embodiments will now be described with reference to a flowchart depicted in Fig. 4B. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features.

[0174] Action 411. The radio network node 120 may receive a trace indication from the managing node 15, which trace indication sets / initiates a trace to collect slice information from the RAN node 120. The radio network node 120 may receive, from the managing node 15 or a CN node, the configuration for reporting MDT indicating to the radio network node 120 to log information such as MDT information. Additionally, or alternatively, configuration may comprise a request for the radio network node 120 to configure the UE 10 with measurements and logs for the events in which the UE requests over NAS to be registered to the network slice or to access a service for the network slice, but the CN rejects the UE to access such network slice.

[0175] Action 412. The radio network node may select suitable UEs that may report slice information and collect the CEF, MHI or RA report from the UEs and forwards the CEF, MHI or RA report information to the OAM. The radio network node 120 may transmit configuration to the UE 10 to configure the UE 10 to log and / or send information for the events in which the UE requests over NAS to be registered to the network slice or to access a service for the network slice.

[0176] Action 413. The radio network node 12 may request and receive report information such as the CEF, MHI or RA report from the UEs. The report may comprise information indicating, where a network slice or a network slice service was requested by the UE, that such request resulted in a rejection. For example, the radio network node 120 may receive a report from the UE 10, upon radio network node request, events where the network slice or the network slice service was requested by the UE 10 while under the coverage of the radio network node’s cells and where such request resulted in a rejection by the Core Network, such as a Non Access Stratum network level rejection.Action 414. The radio network node 120 collects the SON report such as the CEF, MHI or RA report from one or more UEs and forwards the CEF MHI or RA report information to the managing node 15. For example, the radio network node 120 may log and / or send information relating to admission to the network slice and / or the slice service, wherein the information comprises a cause indication in case of non-admission.

[0177] The method actions performed by the managing node 15, such as an OAM or a TCE, for handling communication such as network slices and / or services, in the communication network according to embodiments will now be described with reference to a flowchart depicted in Fig. 4C. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features.

[0178] Action 421. The managing node 15 sets / initiates a trace to collect slice information from the RAN node 120. The managing node 15 may thus transmit a configuration to one or more radio network nodes, directly or via a CN node, such as the radio network node 120, wherein the configuration is for the radio network node 120 to log and / or send information relating to admission to the network slice and / or the slice service. The configuration may be for reporting MDT indicating to the radio network node 120 to log information such as MDT information. Additionally, or alternatively, the managing node 15 may include as part of the MDT configuration a request for the radio network node 120 to configure the LIE 10 with measurements and logs for the events in which the LIE requests over NAS to be registered to a network slice or to access a service for a given network slice, but the CN rejects the UE to access such network slice.

[0179] Action 422. The managing node 15 receives from the radio network node 120 the CEF report, MHI report and / or RA report information. The information may be related to the admission to a network slice and / or slice service, wherein the information comprises a cause indication in case of non-admission.

[0180] Action 423. The managing node 15 may perform an operation taking the report information into account. For example, the managing node 15 may update slice information such as network slice support and network slice availability based on the received information.

[0181] Network Embodiments:

[0182] The main embodiment at the network side of the solution describes the communication between the OAM 15 and RAN 120. If the OAM is interested in collecting slice information concerning slice service requests from the UE 10, it can set / initiate atrace to collect slice information from the RAN node 120. The RAN node selects the suitable UEs that may report rejected slice information and collects the MHI or RA report from the UEs and forwards the MHI or RA report information to the OAM.

[0183] In an alternative, OAM creates a counter in the RAN node to collect slice information. The RAN node extracts the rejected slice information from the collected MHI,RA report, CEF report or a new report and sends an aggregated report to the OAM.

[0184] In one embodiment, a network node, upon receiving from a UE a report (e.g., an MHI report) containing rejected slice information, it increments a counter to monitor the number (or the frequency over time) of UEs attempting to transition from RRC Idle to RRC Connected and using a certain network slice and the attempt is rejected due to no resources allocated to the network slice.

[0185] In one embodiment, upon mobility from a source cell of the first network node to a target cell of a second network node, and, upon receiving from the second network node an indication, indicating a mobility failure towards the cell of the second network node due to problems of slice service request at NAS level, the first network node and / or the second network node increments a counter to monitor the number (or the frequency over time) of UEs using the network slice in the source cell of the first network node, and for which a failure in mobility to the target cell of the second network node is detected due to problems of slice service request at NAS level. The first network node and the second network node can be the same node.

[0186] In an embodiment, the OAM sets / configures a cell level counter; hence, the gNB sends a list of S-NSSAI with one or more of the following information per S-NSSAI:

[0187] number of events where the UE triggers a service request towards the S-NSSAI,

[0188] number of failures / rejections to request a service for the S-NSSAI, Additionally, the gNB may log and signal to the OAM (upon explicit configuration from the OAM, or without such configuration), one or more of the following information:

[0189] number of events where the UE triggers a service request towards any network slice,

[0190] number of failures / rejections to request a service for any network slices.

[0191] In another embodiment, the OAM sets / configures a gNB level counter; hence, the gNB sends a list of the S-NSSAI of the rejected slices and the number of times it was rejected where the histogram information of the rejected slices may have following granularities:• The histogram can be made over a time duration aggregating all cells.

[0192] • The histogram can be made over a time duration for each cell. Hence the number of slice rejection is counted per cell per S-NSSAI over an aggregated number of UEs.

[0193] The same histogram above may be configured by the OAM and signaled by the RAN for slice service request events that completed successfully.

[0194] In a dependent embodiment, regardless of if OAM configures cell level or gNB level counter, the gNB receiving the MHI or RA report from the LIE, upon extracting the cell information, if any cell belongs to a different gNB, forwards the part of the MHI or RA report to the respective gNB over the Xn interface. The receiving gNB, may in turn, use this information to populate the counter if configured by the OAM.

[0195] In an alternative embodiment, regardless of if OAM configures cell level or gNB level counter, the gNB receiving the MHI or RA report from the LIE, upon extracting the cell information, if any cell belongs to a different gNB, discards part of the MHI or RA report belonging to the different gNB.

[0196] In one embodiment, a network node receives from one or more LIE slice service request information (included in an already defined SON report, such as a MHI report, or an RA report, or a CEF report, or in a newly defined UE report) and takes the information into account to configure (or reconfigure) slice-based cell (re)selection parameters.

[0197] In one case, the network node assigns the lowest priority (or decreases the priority) to the rejected slice(s) to penalize the rejected slice(s) in the slice-based cell reselection process executed by the UE(s).

[0198] In another case, the network node removes the slice(s) corresponding to the rejected slice(s) in the configuration parameters sent to the UE(s) in the slice-based cell reselection process.

[0199] The priority can be provided to the UE(s) via RRC parameters a RRCRelease message or in System Information Block(s)), and can be for instance:

[0200] the value of the priority for NR frequency when a given NSAG ID is used to set the frequency priority (e.g., RRC parameter nsag-CellReselectionPriority)

[0201] - the value of the fractional priority added to the above priority for NR frequency for a given NSAG ID, when the NSAG ID is used to set the frequency priority (e.g., RRC parameter nsag-CellReselectionSubPriority).

[0202] In one embodiment, a network node determines / optimizes mobility related parameters associated to a network slice based on the number of mobility attempts and / orthe number of failures in mobility attempts towards a cell where the network slice has no resources available.

[0203] In one embodiment, a first network node obtains the information of failures in mobility of one or more UEs from the first network node to a second network node due to problems of slice service request at NAS level and determines to apply (or update) mobility related parameters associated to the network slice, to avoid / penalize mobility from the first network node towards the target cell of the second network node. For instance, the first network node configures (or reconfigures) an offset to be applied in case of mobility towards the cell of the second network node where the network slice has no resources available. The first network node may send the offset to the second network node.

[0204] In one embodiment of this solution, the methods described above, where it is mentioned that the OAM configures the RAN with information tasking the RAN to collect slice service request information, are also supported without the need of the OAM to configure the RAN. Namely, the RAN is able to configure the UE to collect the statistics concerning slice service request events, or the UE is able to collect them without any configuration needed. Once the statistics are logged, the RAN may report such statistics, as described in the embodiments above, to the OAM. The RAN may use the statistics to optimize slice related processes, such as per slice resource allocation, slice-based mobility actions.

[0205] SOLUTION 3

[0206] The method actions performed by the radio network node 120 for handling communication such as network slices and / or services, in the communication network according to embodiments will now be described with reference to a flowchart depicted in Fig. 5A. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features.

[0207] Action 501. The radio network node 120 may receive, from the managing node 15 or a CN node, the configuration for reporting MDT indicating to the radio network node 120 to log information such as MDT information.

[0208] Action 502. The radio network node 120 requests from the core network node 19, for information relating to the admission of the UE 10 to a network slice and / or a slice service. The requested information may comprise NAS Rejected NSSAI Information for the UE. The radio network node 120 may request for NAS level UE slice service requests information (such as rejected S-NSSAI) from the core network node 19. The radio networknode 120 may add a request indication in an Information Element in an INITIAL LIE MESSAGE or in an UPLINK NAS TRANSPORT message. The Information Element may be comprised in a RAN CONFIGURATION UPDATE. The request indication may be for requesting for the information. The radio network node 120 may request the information by subscribing to receive the information for one or more UEs served by the radio network node 120.

[0209] Action 503. The radio network node 120 receives the requested information from the core network node 19. The radio network node 120 may receive the NAS level UE slice service requests information (such as rejected S-NSSAI) from the core network node 19. The information may indicate rejected S-NSSAI for the UE 10.

[0210] Action 504. The radio network node 120 may add additional information for forwarding to the managing node 15. The additional information may comprise one or more of the following:

[0211] ■ cell information for a cell from which the UE 10 has initiated an admission request;

[0212] ■ if available, a geographical position of the UE 10 when the UE 10 initiated the admission request; and

[0213] ■ a time when the admission request was initiated by the UE 10 and / or received by the radio network node.

[0214] Action 505. The radio network node 120 may forward the information to the managing node 15. The radio network node 120 may forward the NAS level UE slice service requests information (such as rejected S-NSSAI) to the managing node 15. The radio network node 120 may transmit in an MDT trace one or more instances of resource allocation for a PDU Session associated to an S-NSSAI that were not admitted. The radio network node 120 may forward the added additional information.

[0215] Action 506. The radio network node 120 may take into account the information when configuring one or more parameters of a cell selection that is slice based. The radio network node 120 may re-direct one or more UEs to a different cell where network slice access is available through Idle mode cell reselection or handover. Configuring the one or more parameters may comprise assigning a lowest priority level, or decreasing a priority for a network slice or a slice service being rejected; and / or removing the network slice or the slice service being rejected in the cell selection. As example, the radio network node 120 may remove the network slice or slices corresponding to the one or more rejected slices in the one or more parameters sent to the UE 10 in a slice-based cell reselectionprocess. The priority value may be provided to the UE 10 via RRC parameter in a RRCRelease message or in SIB. The priority value may comprise:

[0216] • a value of a priority for NR frequency when a given NSAG ID is used to set the frequency priority, e.g., RRC parameter nsag-CellReselectionPriority; and / or • a value of a fractional priority added to the above priority for NR frequency for a given NSAG ID, when the NSAG ID is used to set the frequency priority (e.g., RRC parameter nsag-CellReselectionSubPriority).

[0217] The radio network node 120 may optimize one or more mobility related parameters associated to a network slice based on a number of mobility attempts and / or a number of failures in mobility attempts towards a cell where the network slice has no resources available.

[0218] The method actions performed by the core network node 19, such as an AMF, for handling communication, such as network slices and / or services, in the communication network according to embodiments will now be described with reference to a flowchart depicted in Fig.5B. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features.

[0219] Action 511. The core network node 19 receives the request from the radio network node 120, requesting for the information relating to the admission of the UE 10 to a network slice and / or a slice service. The requested information may comprise NAS Rejected NSSAI Information for the UE 10. The core network node 19 may receive from the radio network node 120 request for NAS level UE slice service requests information for the UE 10 (such as rejected S-NSSAI). The request may be comprised in an Information Element in an INITIAL UE MESSAGE or in an UPLINK NAS TRANSPORT message. The request may comprise subscription to receive the information for one or more UEs served by the radio network node.

[0220] Action 512. The core network node 19 transmits to the radio network node 120 the requested information for the UE 10. The information may indicate rejected S-NSSAI for the UE 10. The core network node 19 may transmit to the radio network node 120 the NAS level UE slice service requests information (such as rejected S-NSSAI) for the UE 10. The requested information may be transmitted in an INITIAL CONTEXT SETUP REQUEST.

[0221] The method actions performed by the managing node 15, such as an OAM or a TCE, for handling communication, such as network slices and / or services, in thecommunication network according to embodiments will now be described with reference to a flowchart depicted in Fig. 5C. The actions do not have to be taken in the order stated below but may be taken in any suitable order. Dashed boxes indicate optional features.

[0222] Action 521. The managing node 15 may transmit the configuration for reporting MDT indicating to the radio network node 120 to log information such as MDT information. The managing node 15 may set / initiate a trace to collect slice information from the RAN node 120.

[0223] Action 522. The managing node 15 receives from the radio network node 120, the information for the LIE 10. The information relates to the admission of the LIE 10 to a network slice and / or a slice service. The managing node 15 may receive from the radio network node 120 the NAS level LIE slice service requests information (such as rejected S-NSSAI) for the LIE 10. The information may comprise a cause indication in case of nonadmission. For example, the managing node 15 may receive in an MDT trace one or more instances of resource allocation for a PDU Session associated to an S-NSSAI that were not admitted. The information may indicate rejected S-NSSAI for the LIE 10. The information may further comprise additional information, wherein the additional information comprises one or more of the following:

[0224] ■ cell information for the cell from which the LIE 10 has initiated the admission request;

[0225] ■ if available, the geographical position of the UE 10 when the UE 10 initiated the admission request; and

[0226] ■ the time when the admission request was initiated by the UE 10 and / or received by the radio network node.

[0227] Action 523. The managing node 15 performs an operation taking the information into account. For example, the managing node 15 may update slice information such as network slice support and network slice availability based on the received information. The managing node may collect and analyze statistics of received information before updating the slice information.

[0228] In one embodiment, the radio network node 120, such as a gNB, may request the information such as NAS level UE slice service requests information, e.g., one or more rejected S-NSSAI, from the core network node 19, such as an AMF. For doing so the radio network node 120 may add an Information Element in the INITIAL UE MESSAGE or in the UPLINK NAS TRANSPORT message to request from the core network node 19 the reporting of NAS rejected slice service requests for this specific UE 10. Below, examplesare shown as italic and underlined for the case where the radio network node 120 requests for rejected NSSAI information.

[0229] INITIAL UE MESSAGE

[0230] This message is sent by the radio network node 120, such as a NG-RAN node, to 5 transfer the initial layer 3 message to the core network node 19, such as an AMF, over the NG interface.

[0231] Direction: NG-RAN node to AMF

[0232]

[0233]

[0234]

[0235] In another variant of this embodiment, the radio network node 120 may use a configuration message such as RAN CONFIGURATION UPDATE message to request the 5 core network node 19 to implicitly report the NAS rejected slice service requests for all the UEs for which, subsequently, an INITIAL UE MESSAGE will be sent from the radio network node 120 to the core network node 19.

[0236] RAN CONFIGURATION UPDATE, excerpt from 3GPP TS 38.413 V18.4.0 (2024- 10 12).

[0237] This message is sent by the radio network node 120, such as NG-RAN node, to transfer updated application layer information for an NG-control plan (NG-C) interface instance.Direction: NG-RAN node to AMF

[0238] > <

[0239] >

[0240] > <

[0241]

[0242] > <

[0243]

[0244]

[0245]

[0246] In response to the request from the radio network node 120, the core network node 19 may use the INITIAL CONTEXT SETUP REQUEST or the UE CONTEXT 5 MODIFICATION REQUEST or the DOWNLINK NAS TRANSPORT message to inform the radio network node 120 about the slice service requests that were rejected at NAS level for a given UE.INITIAL CONTEXT SETUP REQUEST, excerpt from 3GPP TS 38.413 V18.4.0 (2024-12).

[0247] This message is sent by the core network node 19 to request the setup of a UE context.

[0248] Direction: AMF to NG-RAN node

[0249] > <

[0250] >

[0251]

[0252]

[0253]

[0254]

[0255]

[0256]

[0257]

[0258]

[0259]

[0260] After receiving from the core network node 19, the list of slice service requests rejected by the NAS layer for the given LIE 10, the radio network node 120 may enrich this information before reporting it to the managing node 15. The following list of information elements is a non-exhaustive list of elements that the radio network node 120 may add to a NAS rejected slice service request:

[0261] the cell information for the cell from which the LIE 10 has initiated the request, - if available, the UE geographical position when it initiated the request,

[0262] - the time when the slice service request was initiated by the UE 10 and / or received by the gNB,

[0263] The radio network node 120 may create a subscription to the core network node 19 to receive NAS level UE slice service request information (such as rejected S-NSSAI) for all UEs served by the radio network node 120. The core network node 19 may send the information for each individual UEs. The radio network node 120 may then utilize the information, or forward the information to the managing node 15.

[0264] The radio network node 120 may, upon reception of the information from the core network node 19, take the information into account to configure (or reconfigure) slicebased cell (re)selection parameters.

[0265] The radio network node 120 may assign the lowest priority (or decreases the priority) to the rejected slice(s) to penalize the rejected slice(s) in the slice-based cell reselection process executed by the UE 10.The radio network node 120 may remove the network slice or network slices corresponding to the rejected network slice or slices in the configuration parameters sent to the UE 10 in the slice-based cell reselection process.

[0266] The priority may be provided to the UE 10 via one or more RRC parameters in a RRCRelease message or in a System Information Block, and may be for instance:

[0267] a value of the priority for NR frequency when a given NSAG ID is used to set the frequency priority, e.g., RRC parameter nsag-CellReselectionPriority,

[0268] - a value of the fractional priority added to the above priority for NR frequency for a given NSAG ID, when the NSAG ID is used to set the frequency priority, e.g., RRC parameter nsag-CellReselectionSubPriority.

[0269] The radio network node 120 may determine and / or optimize mobility related parameters associated to a network slice based on the number of mobility attempts and / or the number of failures in mobility attempts towards a cell where the network slice has no resources available.

[0270] Fig. 6 shows a block diagram depicting the UE 10 for handling communication in the communication network such as usage of the network slice, or enabling communication / service of the UE 10, in the communication network.

[0271] The UE 10 may comprise processing circuitry 601 , e.g. one or more processors, configured to perform the methods herein.

[0272] The UE 10 and / or the processing circuitry 601 may be configured to obtain the indication of configuration for logging and / or sending NAS level UE slice service requests information to the radio network node 120. The indication may be received from the radio network node 120 and / or be preconfigured. For example, while the UE 10 in RRC Idle state performs random access procedure to the radio network node 120 to transition to RRC Connected state, the UE 10 and / or the processing circuitry 601 may be configured receive from the radio network node 120 the configuration data for configuring the UE to collect rejected slice information.

[0273] The UE 10 and / or the processing circuitry 601 may be configured to perform the admission procedure to the network slice or a service of the network slice. The UE 10 and / or the processing circuitry 601 may be configured to request the network slice or the network slice service. The request may be rejected.

[0274] The UE 10 and / or the processing circuitry 601 may be configured to log and / or send the NAS level UE slice service requests information to the radio network node 120, such as information indicating, where a network slice or a network slice service wasrequested by the UE, that such request resulted in a rejection. For example, the UE 10 and / or the processing circuitry 601 may be configured to report to the radio network node 120, upon radio network node request, the events where a network slice or a network slice service was requested by the UE 10 while under the coverage of the radio network node’s cells and where such request resulted in a rejection by the Core Network, such as a Non Access Stratum network level rejection.

[0275] The UE 10 and / or the processing circuitry 601 may be configured to obtain the configuration to configure the UE 10 to log information related to slice service access (e.g. related to slice rejection at NAS level), also referred to as NAS level UE slice service requests information, as additional information into existing SON report(s) such as the mobility history information (MHI) report or the Random Access (RA) report or the Connection Establishment Failure (CEF) report. The configuration may be received from the radio network node 120 and / or be preconfigured.

[0276] The UE 10 and / or the processing circuitry 601 may be configured to log and / or send information related to slice service access (e.g. related to slice rejection at NAS level), also referred to as NAS level UE slice service requests information, as additional information into existing SON report.

[0277] The UE 10 may further comprise a memory 605. The memory comprises one or more units to be used to store data on, such as indications, configuration, signal strengths or qualities, indications, slice information, NAS level UE slice service requests information, values, scheduling information, timers, applications to perform the methods disclosed herein when being executed, and similar. The UE 10 comprises a communication interface 606 comprising transmitter, receiver, transceiver and / or one or more antennas. Thus, it is herein provided the UE for handling communication in a communication network, wherein the UE comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said UE is operative to perform any of the methods herein.

[0278] The methods according to the embodiments described herein for the UE 10 are respectively implemented by means of, e.g., a computer program product 607 or a computer program product, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the UE 10. The computer program product 607 may be stored on a computer-readable storage medium 608, e.g. a universal serial bus (USB) stick, a disc or similar. The computer-readable storage medium 608, having stored thereon the computer program product, may comprise the instructions which, whenexecuted on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the LIE 10. In some embodiments, the computer-readable storage medium may be a non-transitory or transitory computer-readable storage medium.

[0279] Fig. 7 shows a block diagram depicting the radio network node 120 for handling communication in the communication network.

[0280] The radio network node 120 may comprise processing circuitry 701 , e.g., one or more processors, configured to perform the methods herein.

[0281] The radio network node 120 and / or the processing circuitry 701 is configured to request from the core network node 19, for the information relating to the admission of the UE 10 to a network slice and / or a slice service. The requested information may comprise NAS Rejected NSSAI Information. The radio network node 120 and / or the processing circuitry 701 may be configured to request for NAS level UE slice service requests information (such as rejected S-NSSAI) from the core network node 19. The radio network node 120 and / or the processing circuitry 701 may be configured to add the request indication in the Information Element in the INITIAL UE MESSAGE or in the UPLINK NAS TRANSPORT message. The Information Element may be comprised in a RAN CONFIGURATION UPDATE. The request indication may be for requesting for the information. The radio network node 120 and / or the processing circuitry 701 may be configured to request for the information by subscribing to receive the information for one or more UEs served by the radio network node 120.

[0282] The radio network node 120 and / or the processing circuitry 701 is configured to receive the requested information from the core network node 19. The radio network node 120 and / or the processing circuitry 701 may be configured to receive the NAS level UE slice service requests information (such as rejected S-NSSAI) from the core network node 19. The information may indicate rejected S-NSSAI for the UE (10).

[0283] The radio network node 120 and / or the processing circuitry 701 may be configured to add the additional information for forwarding to the managing node 15. The additional information may comprise one or more of the following:

[0284] ■ cell information for a cell from which the UE 10 has initiated the admission request;

[0285] ■ if available, a geographical position of the UE 10 when the UE 10 initiated the admission request; and■ a time when the admission request was initiated by the UE 10 and / or received by the radio network node.

[0286] The radio network node 120 and / or the processing circuitry 701 may be configured to forward the information to the managing node 15. The radio network node 120 and / or the processing circuitry 701 may be configured to forward the NAS level UE slice service requests information (such as rejected S-NSSAI) to the managing node 15. The radio network node 120 and / or the processing circuitry 701 may be configured to transmit in an MDT trace one or more instances of resource allocation for a PDU Session associated to an S-NSSAI that were not admitted.

[0287] The radio network node 120 and / or the processing circuitry 701 may be configured to take into account the information when configuring one or more parameters of a cell selection that is slice based. The radio network node 120 and / or the processing circuitry 701 may be configured to re-direct one or more UEs to a different cell where network slice access is available through Idle mode cell reselection or handover. Configuring the one or more parameters may comprise assigning a lowest priority level, or decreasing a priority for a network slice or a slice service being rejected; and / or removing the network slice or the slice service being rejected in the cell selection. The radio network node 120 and / or the processing circuitry 701 may be configured to optimize one or more mobility related parameters associated to a network slice based on a number of mobility attempts and / or a number of failures in mobility attempts towards a cell where the network slice has no resources available.

[0288] The radio network node 120 and / or the processing circuitry 701 may be configured to receive, from the managing node 15 or a CN node, the configuration for reporting MDT indicating to the radio network node 120 to log information such as MDT information. Additionally, or alternatively, configuration may comprise the request for the radio network node 120 to configure the UE 10 with measurements and logs for the events in which the UE requests over NAS to be registered to the network slice or to access a service for the network slice, but the CN rejects the UE to access such network slice.

[0289] The radio network node 120 and / or the processing circuitry 701 may be configured to transmit the indication to the UE 10 of configuration for logging and / or sending NAS level UE slice service requests information to the radio network node 120. The radio network node 120 may transmit the request to the UE 10 to configure the UE 10 to log and / or send information for the events in which the UE requests over NAS to be registered to the network slice or to access a service for the network slice. The radionetwork node 120 and / or the processing circuitry 701 may be configured to provide the LIE with this indication in msg4 (contention resolution) of RA procedure.

[0290] The radio network node 120 and / or the processing circuitry 701 may be configured to receive the NAS level LIE slice service requests information from the LIE 10. The radio network node 120 and / or the processing circuitry 701 may be configured to receive report information indicating, where the network slice or the network slice service was requested by the UE. For example, the radio network node 120 and / or the processing circuitry 701 may be configured to receive the report from the UE 10, upon radio network node request, events where the network slice or the network slice service was requested by the UE 10 while under the coverage of the radio network node’s cells and where such request resulted in a rejection by the Core Network, such as a Non Access Stratum network level rejection.

[0291] The radio network node 120 and / or the processing circuitry 701 may be configured to send report information relating to admission to the network slice and / or the slice service to the managing node 15.

[0292] The radio network node 120 and / or the processing circuitry 701 may be configured to receive the trace indication from the managing node 15, which trace indication sets / initiates the trace to collect slice information from the RAN node 120.

[0293] The radio network node 120 and / or the processing circuitry 701 may be configured to select suitable UEs that may report slice information and collect the CEF, MHI or RA report from the UEs and forwards the CEF, MHI or RA report information to the OAM. The radio network node 120 and / or the processing circuitry 701 may be configured to transmit configuration to the UE 10 to configure the UE 10 to log and / or send information for the events in which the UE requests over NAS to be registered to the network slice or to access a service for the network slice.

[0294] The radio network node 120 and / or the processing circuitry 701 may be configured to request and receive report information such as the CEF, MHI or RA report from the UEs. The report may comprise information indicating, where a network slice or a network slice service was requested by the UE, that such request resulted in a rejection. For example, the radio network node 120 and / or the processing circuitry 701 may be configured to receive the report from the UE 10, upon radio network node request, events where the network slice or the network slice service was requested by the UE 10 while under the coverage of the radio network node’s cells and where such request resulted in a rejection by the Core Network, such as a Non Access Stratum network level rejection.The radio network node 120 and / or the processing circuitry 701 may be configured to collect the SON report such as the CEF, MHI or RA report from one or more UEs and forwards the CEF MHI or RA report information to the managing node 15. For example, the radio network node 120 and / or the processing circuitry 701 may be configured to log and / or send information relating to admission to the network slice and / or the slice service, wherein the information comprises a cause indication in case of non-admission.

[0295] The radio network node 120 and / or the processing circuitry 701 may be configured to receive, from the managing node 15 or a CN node, the configuration for reporting MDT indicating to the radio network node 120 to log information such as MDT information.

[0296] The radio network node 120 further comprises a memory 705. The memory comprises one or more units to be used to store data on, such as indications, slice information, signal strengths or qualities, resource information, information, NAS level LIE slice service requests information, indications, configuration, values, scheduling information, timers, applications to perform the methods disclosed herein when being executed, and similar. The radio network node 120 comprises a communication interface 706 comprising transmitter, receiver, transceiver and / or one or more antennas. Thus, it is herein provided the radio network node 120 for handling communication in a communication network, wherein the radio network node 120 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said radio network node 120 is operative to perform any of the methods herein.

[0297] The methods according to the embodiments described herein for the radio network node 120 are respectively implemented by means of, e.g., a computer program product 707 or a computer program product, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the radio network node 120. The computer program product 707 may be stored on a computer-readable storage medium 708, e.g., a universal serial bus (USB) stick, a disc or similar. The computer-readable storage medium 708, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the radio network node 120. In some embodiments, the computer-readable storage medium may be a non-transitory or transitory computer-readable storage medium.Fig. 8 shows a block diagram depicting the managing node 15, such as an OAM or a TCE, for handling communication in the communication network.

[0298] The managing node 15 may comprise processing circuitry 801, e.g., one or more processors, configured to perform the methods herein.

[0299] The managing node 15 and / or processing circuitry 801 is configured to receive from the radio network node 120, the information for the LIE 10. The information relates to the admission of the UE 10 to a network slice and / or a slice service. The managing node 15 and / or processing circuitry 801 may be configured to receive from the radio network node 120 the NAS level UE slice service requests information (such as rejected S-NSSAI) for the UE 10. The information may comprise a cause indication in case of non-admission. For example, the managing node 15 and / or processing circuitry 801 may be configured to receive in the MDT trace one or more instances of resource allocation for a PDU Session associated to an S-NSSAI that were not admitted. The information may indicate rejected S-NSSAI for the UE 10. The information may further comprise additional information, wherein the additional information comprises one or more of the following:

[0300] ■ cell information for the cell from which the UE 10 has initiated the admission request;

[0301] ■ if available, the geographical position of the UE 10 when the UE 10 initiated the admission request; and

[0302] ■ the time when the admission request was initiated by the UE 10 and / or received by the radio network node.

[0303] The managing node 15 and / or processing circuitry 801 is configured to perform the operation taking the information into account. For example, the managing node 15 and / or processing circuitry 801 may be configured to update slice information such as network slice support and network slice availability based on the received information.

[0304] The managing node 15 and / or processing circuitry 801 may be configured to transmit to the radio network node 120, the configuration for reporting MDT indicating to the radio network node 120 to log information such as MDT information. The managing node 15 and / or processing circuitry 801 may be configured to transmit the request to the radio network node 120 to collect such information. Such request might be included in an MDT configuration.

[0305] The managing node 15 and / or processing circuitry 801 may be configured to receive the report information relating to admission to the network slice and / or the slice service from the radio network node 120.The managing node 15 and / or processing circuitry 801 may be configured to set / initiate the trace to collect slice information from the RAN node 120. The managing node 15 and / or processing circuitry 801 may be configured to transmit the configuration to one or more radio network nodes, directly or via a CN node, such as the radio network node 120, wherein the configuration is for the radio network node 120 to log and / or send information relating to admission to the network slice and / or the slice service. The configuration may be for reporting MDT indicating to the radio network node 120 to log information such as MDT information. Additionally, or alternatively, the managing node 15 and / or processing circuitry 801 may be configured to include as part of the MDT configuration the request for the radio network node 120 to configure the LIE 10 with measurements and logs for the events in which the LIE requests over NAS to be registered to a network slice or to access a service for a given network slice, but the CN rejects the UE to access such network slice.

[0306] The managing node 15 and / or processing circuitry 801 may be configured to receive from the radio network node 120 the CEF report, MHI report and / or RA report information. The information may be related to the admission to a network slice and / or slice service, wherein the information comprises a cause indication in case of nonadmission.

[0307] The managing node 15 and / or processing circuitry 801 may be configured to perform the operation taking the report information into account. For example, the managing node 15 and / or processing circuitry 801 may be configured to update slice information such as network slice support and network slice availability based on the received information.

[0308] The managing node 15 and / or processing circuitry 801 may be configured to transmit the configuration for reporting MDT indicating to the radio network node 120 to log information such as MDT information.

[0309] The managing node 15 further comprises a memory 805. The memory comprises one or more units to be used to store data on, such as indications, slice information, NAS level UE slice service requests information, signal strengths or qualities, resource information, information, indications, configuration, values, scheduling information, timers, applications to perform the methods disclosed herein when being executed, and similar. The managing node 15 comprises a communication interface 806 comprising transmitter, receiver, transceiver and / or one or more antennas. Thus, it is herein provided the managing node 15 for handling communication in a communication network, wherein the managing node 15 comprises processing circuitry and a memory, said memorycomprising instructions executable by said processing circuitry whereby said managing node 15 is operative to perform any of the methods herein.

[0310] The methods according to the embodiments described herein for the managing node 15 are respectively implemented by means of, e.g., a computer program product 807 or a computer program product, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the managing node 15. The computer program product 807 may be stored on a computer-readable storage medium 808, e.g., a universal serial bus (USB) stick, a disc or similar. The computer-readable storage medium 808, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the managing node 15. In some embodiments, the computer-readable storage medium may be a non-transitory or transitory computer-readable storage medium.

[0311] Fig. 9 shows a block diagram depicting the core network node 19, such as an AMF, for handling communication in the communication network.

[0312] The core network node 19 may comprise processing circuitry 901 , e.g., one or more processors, configured to perform the methods herein.

[0313] The core network node 19 and / or the processing circuitry 901 is configured to receive the request from the radio network node 120, requesting for information relating to the admission of the UE 10 to a network slice and / or a slice service. The requested information may comprise NAS Rejected NSSAI Information. The core network node 19 and / or the processing circuitry 901 may be configured to receive from the radio network node 120 request for NAS level UE slice service requests information for the UE 10 (such as rejected S-NSSAI). The request may be comprised in an Information Element in an INITIAL UE MESSAGE or in an UPLINK NAS TRANSPORT message. The request may comprise subscription to receive the information for one or more UEs served by the radio network node.

[0314] The core network node 19 and / or the processing circuitry 901 is configured to transmit to the radio network node 120 the requested information for the UE 10. The information may indicate rejected S-NSSAI for the UE 10. The core network node 19 and / or the processing circuitry 901 may be configured to transmit to the radio network node 120 the NAS level UE slice service requests information (such as rejected S-NSSAI)for the LIE 10. The requested information may be transmitted in an INITIAL CONTEXT SETUP REQUEST.

[0315] The core network node 19 further comprises a memory 905. The memory comprises one or more units to be used to store data on, such as indications, slice information, signal strengths or qualities, resource information, the NAS level UE slice service requests information, information, indications, configuration, values, scheduling information, timers, applications to perform the methods disclosed herein when being executed, and similar. The core network node 19 comprises a communication interface 906 comprising transmitter, receiver, transceiver and / or one or more antennas. Thus, it is herein provided the core network node 19 for handling communication in a communication network, wherein the core network node 19 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said core network node 19 is operative to perform any of the methods herein.

[0316] The methods according to the embodiments described herein for the core network node 19 are respectively implemented by means of, e.g., a computer program product 907 or a computer program product, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the core network node 19. The computer program product 907 may be stored on a computer-readable storage medium 908, e.g., a universal serial bus (USB) stick, a disc or similar. The computer-readable storage medium 908, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the core network node 19. In some embodiments, the computer-readable storage medium may be a non-transitory or transitory computer-readable storage medium.

[0317] In some embodiments a more general term “network node” is used and it can correspond to any type of radio network node or any network node, which communicates with a wireless device and / or with another network node. Examples of network nodes are NodeB, Master eNB, Secondary eNB, a network node belonging to Master cell group (MCG) or Secondary Cell Group (SCG), base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), corenetwork node e.g. Mobility Switching Centre (MSC), Mobile Management Entity (MME) etc., Operation and Maintenance (O&M), Operation Support System (OSS), SelfOrganizing Network (SON), positioning node e.g. Evolved Serving Mobile Location Centre (E-SMLC), Minimizing Drive Test (MDT), etc.

[0318] In some embodiments, the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and / or with another UE in a cellular or mobile communication system. Examples of UE are target device, device-to-device (D2D) UE, proximity capable UE (aka ProSe UE), machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.

[0319] The embodiments are described for 5G. However the embodiments are applicable to any RAT or multi-RAT systems, where the UE receives and / or transmit signals (e.g. data) e.g. LTE, LTE FDD / TDD, WCDMA / HSPA, GSM / GERAN, Wi Fi, WLAN, CDMA2000 etc.

[0320] Signaling herein may generally comprise one or more symbols and / or signals and / or messages. A signal may comprise and / or represent one or more bits, which may be modulated into a common modulated signal. An indication may represent signaling, and / or be implemented as a signal, or as a plurality of signals. One or more signals may be included in and / or represented by a message. Signaling, in particular control signaling, may comprise a plurality of signals and / or messages, which may be transmitted on different carriers and / or be associated to different acknowledgement signaling processes, e.g. representing and / or pertaining to one or more such processes. An indication may comprise signaling and / or a plurality of signals and / or messages and / or may be comprised therein, which may be transmitted on different carriers and / or be associated to different acknowledgement signaling processes, e.g. representing and / or pertaining to one or more such processes.

[0321] As will be readily understood by those familiar with communications design, functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0322] Fig. 10 shows an example of a communication system 15100 in accordance with some embodiments.

[0323] In the example, the communication system 15100 includes a telecommunications network 15102 that includes an access network 15104, such as a radio access network (RAN), and a core network 15106, which includes one or more core network nodes 15108 such as the CN node 19. The access network 15104 includes one or more access network nodes or base stations of various types, access network nodes 15110A and 15110B are depicted (which may be collectively referred to as network nodes 15110 or the radio network node 120), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 15104 may include more than one access network technology. The network nodes 15110 of access network 15104 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 15112A, 15112B, 15112C, and 15112D (one or more of which may be generally referred to as UEs 15112 or UE 10) to the core network 15106 over one or more wireless connections.

[0324] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 15102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 15102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implementone or more functionalities of any network node in the telecommunications network 15102, including one or more access network nodes 15110 and / or core network nodes 15108.

[0325] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0326] The network nodes 15110 facilitate direct or indirect connection of one or more UEs 15112 to the core network 15106 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 15100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 15100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0327] The UEs 15112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 15110 and other communication devices. Similarly, the network nodes 15108, 15110 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 15102) with the UEs15112 and / or with other network nodes or equipment in the telecommunications network 15102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 15102. More specifically, UEs 15112 may send messages, data, and / or other signals to network nodes 15108, 15110 or other elements of the telecommunications network 15102 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 15108, 15110 may send messages, data, and other signals to UEs 151122, other network nodes 15108, 15110, and other devices in telecommunications network 15102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 15112 by transmitting the message to an access network node 15110 that will then transmit the message to the intended UE 15112. Similarly, a core network node 108 may receive a particular message from a UE 15112 by receiving the message from an access network node 15110 that itself received the message from the UE 15112.

[0328] In the depicted example, the core network 15106 connects elements of the access network 15104 (e.g., one or more of the network nodes 15110) to one or more host computing systems, such as host 15116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 15106 includes one or more core network nodes (e.g., core network node 15108) of various types, one or more of which may be generally referred to as network nodes 15108. Network nodes 15108 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 15108. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0329] The host 15116 may be under the ownership or control of a service provider other than an operator or provider of the access network 15104 and / or the telecommunicationsnetwork 15102. The host 15116 may be operated by the service provider or on behalf of the service provider. The host 15116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0330] As a whole, the communication system 15100 of Fig. 10 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 15100 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 15100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 15100 supporting different standards, protocols, or rule sets.

[0331] As one example, in certain embodiments, access network 15104 may contain some access network nodes 15110 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 15110 support (or the same access network nodes 15110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 15102 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0332] Telecommunications network 15102 may support network slicing to provide different logical networks to different devices that are connected to thetelecommunications network 15102. For example, the telecommunications network 15102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0333] In some examples, one or more of the UEs 15112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 15104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 15104. Additionally, a UE may be configured for operating in single-or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0334] In the example, the hub 15114 communicates with the access network 15104 to facilitate indirect communication between one or more UEs (e.g., UE 15112C and / or 15112D) and network nodes (e.g., network node 15110B). In some examples, the hub 15114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 15114 may be a broadband router enabling access to the core network 15106 for the UEs. As another example, the hub 15114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 15110, or by executable code, script, process, or other instructions in the hub 15114.

[0335] As another example, the hub 15114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 15114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 15114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 15114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 15114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0336] The hub 15114 may have a constant / persistent or intermittent connection to the network node 15110B. The hub 15114 may also allow for a different communicationscheme and / or schedule between the hub 15114 and UEs (e.g., UE 15112C and / or 15112D), and between the hub 15114 and the core network 15106. In other examples, the hub 15114 is connected to the core network 15106 and / or one or more UEs via a wired connection. Moreover, the hub 15114 may be configured to connect to an M2M service provider over the access network 15104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 15110 while still connected via the hub 15114 via a wired or wireless connection. In some embodiments, the hub 15114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 15110B. In other embodiments, the hub 15114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 15110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0337] Fig. 11 is another example of a communication system 15200 according to some embodiments. As used herein, the communication system 15200 includes multiple access points (APs) 15210 (with four exemplary APs 15210A, 15210B, 15210C, and 15210D being depicted) and multiple wireless devices, referred to in the context of communication system 15200 as stations (STAs) 15212 (referred to individually as STA 15212A, STA 15212B, STA 15212C, STA 15212D, and STA 15212E). STA 15212A is served by AP 15210A in a first basic service set (BSS) 15220A. STA 15210B and STA 15210C are served by AP 15210B in a second BSS, BSS 15220B. STA 15212D is served by AP 15210C in a third BSS, BSS 15220C. STA 15212E is served by AP 15210D in a fourth BSS, BSS 15220D. Stations 15212 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 15212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0338] Each of STAs 15212 may connect through a radio link to one of APs 15210. For example, depending on location or channel conditions experienced by a given STA 15212, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0339] Each AP 15210 may provide data connectivity to STAs 15212 connected to a particular AP 15210. As illustrated, APs 15210 may be connected to a data network 15230. In this way, APs 15210 may also provide data connectivity between STAs 15212 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 15212 and its serving AP 15210 may be used for providing various kinds of services to STA 15212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 15212 and / or on a device linked to STA 15212. Byway of example, Fig. 11 illustrates an application service platform 15232 provided in data network 15230. The application(s) executed on STA 15212 and / or on one or more other devices linked to STA 15212 may use the radio link for data communication with one or more other STA 15212 and / or the application service platform 15232, thereby enabling utilization of the corresponding service(s) at STA 15212.

[0340] Fig. 12 shows a wireless device 15300 being an example of the LIE 10, which may be configured to operate in communication system 15100 of Fig. 10 or in communication system 15200 of Fig. 11. The wireless device 15300 may be alternatively referred to the LIE 10 just as a LIE 15300, like a LIE 15112 within the context of communication system 15100, or as a station (STA) 15300 or as a non-access-point station (non-AP STA) 15300, like a STA 15212 within the context of the communication system 15200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.A wireless device 15300 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 15300 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 15300 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 15300 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0341] In particular embodiments, wireless device 15300 includes processing circuitry 15302 that is operatively coupled via a bus 15304 to an input / output interface 15306, a power source 15308, a memory 15310, a communication interface 15312, and / or any other component, or any combination thereof. Certain embodiments of wireless device 15300 may include all or a subset of the components shown in Fig. 12. The level of integration between the components may vary from one embodiment of wireless device 15300 to another. In general, in a particular embodiment of wireless device 15300, processing circuitry 15302, input / output interface 15306, power source 15308, memory 15310, and communication interface 15312 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 15300. Further, certain embodiments of wireless devices 15300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0342] The processing circuitry 15302 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 15310. The processing circuitry 15302 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 15302 may include multiple central processing units (CPUs).In the example, the input / output interface 15306 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 15300. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0343] In some embodiments, the power source 15308 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 15308 may further include power circuitry for delivering power from the power source 15308 itself, and / or an external power source, to the various parts of wireless device 15300 via input circuitry or an interface such as an electrical power cable. Power source 15308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 15300 to which power is supplied.

[0344] The memory 15310 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 15310 includes one or more programs 15314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 15316. The memory 15310 may store, for use by wireless device 15300, any of a variety of various operating systems or combinations of operating systems.

[0345] The memory 15310 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive,external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a IISIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 15310 may allow wireless device 15300 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 15310, which may be or comprise a device-readable storage medium.

[0346] The processing circuitry 15302 may be configured to communicate with an access network or other network via or using the communication interface 15312. The communication interface 15312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 15322. The communication interface 15312 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 15318 and / or a receiver 15320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 15318 and receiver 15320 may be coupled to one or more antennas (e.g., antenna 15322) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0347] In the illustrated embodiment, communication functions of the communication interface 15312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.

[0348] Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS,WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QIIIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0349] In particular embodiments, wireless device 15300 may provide an output of data captured via a sensor, through its communication interface 15312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 15300 can be communicated through a wireless connection to a network node via another wireless device 15300. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0350] As another example, wireless device 15300 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 15300 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0351] Wireless device 15300, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Nonlimiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 15300 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other componentsas described in relation to the example embodiment of wireless device 15300 shown in Fig. 12.

[0352] As yet another specific example, in an loT scenario, wireless device 15300 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 15300 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 15300 may implement the 3GPP NB-loT standard. In other scenarios, wireless device 15300 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0353] In practice, any number of wireless devices 15300 may be used together with respect to a single use case. For example, a first wireless device 15300 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 15300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 15300 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 15300 can also include more than one of the functionalities described above. For example, wireless device 15300 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0354] Fig. 13 shows a network node 15400, being example of the radio network node 120, the core network node 19 and the managing node 15, in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 15400 may be configured to operate in communication system 15100 of Fig. 10, like network nodes 15108 or 15110, or in communication system 15200 of Fig. 11 , like an AP 15210 or a station 15212. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., 0-Rll, O-DU, O-CU).

[0355] Network nodes 15400 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on theprovided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 15400 may be a relay node or a relay donor node controlling a relay. Network nodes 15400 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0356] Other examples of network nodes 15400 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operation, administration and management (OAM) nodes such as the managing node 15, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0357] In particular embodiments, network node 15400 includes a processing circuitry 15402, a memory 15404, a communication interface 15406, and a power source 15408. In general, in a particular embodiment of network node 15400, processing circuitry 15402, memory 15404, communication interface 15406, and power source 15408 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 15400.

[0358] The network node 15400 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 15400 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 15400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 15404 or portions of memory 15404 for different RATs) and some components may be reused (e.g., a same antenna 15410 may beshared by different RATs). The network node 15400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 15400, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 15400.

[0359] The processing circuitry 15402 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 15404, to provide network node 15400 functionality.

[0360] In some embodiments, the processing circuitry 15402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 15402 includes one or more of radio frequency (RF) transceiver circuitry 15412 and baseband processing circuitry 15414. In some embodiments, the RF transceiver circuitry 15412 and the baseband processing circuitry 15414 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 15412 and baseband processing circuitry 15414 may be on the same chip or set of chips, boards, or units.

[0361] The memory 15404 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 15402. The memory 15404 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 15402 and utilized by the network node 15400. The memory 15404 may be used to store any calculations made by the processing circuitry 15402 and / or any data received via the communicationinterface 15406. In some embodiments, the processing circuitry 15402 and memory 15404 is integrated.

[0362] The communication interface 15406 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 15406 comprises port(s) / terminal(s) 15416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 15300 may be capable of wireless communication and communication interface 15406 may also include radio front-end circuitry 15418 that may be coupled to, or in certain embodiments a part of, an antenna 15410. Particular embodiments of radio front-end circuitry 15418 include filter(s) 15420 and amplifier(s) 15422. The radio front-end circuitry 15418 may be connected to an antenna 15410 and processing circuitry 15402. The radio front-end circuitry may be configured to condition signals communicated between antenna 15410 and processing circuitry 15402. The radio front-end circuitry 15418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 15418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 15420 and / or amplifiers 15422. The radio signal(s) may then be transmitted via the antenna 15410. Similarly, when receiving data, the antenna 15410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 15418. The digital data may be passed to the processing circuitry 15402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0363] In certain alternative embodiments, network node 15400 may be capable of wireless communication but does not include separate radio front-end circuitry 15418, instead, the processing circuitry 15402 includes radio front-end circuitry and is connected to the antenna 15410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 15412 is part of the communication interface 15406. In still other embodiments, the communication interface 15406 includes one or more ports or terminals 15416, the radio front-end circuitry 15418, and the RF transceiver circuitry 15412, as part of a radio unit (not shown), and the communication interface 15406 communicates with the baseband processing circuitry 15414, which is part of a digital unit (not shown).

[0364] The antenna 15410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 15410 may be coupled to the radio front-end circuitry 15418 and may be any type of antenna capable of transmittingand receiving data and / or signals wirelessly. In certain embodiments, the antenna 15410 is separate from the network node 15400 and connectable to the network node 15400 through one or more interfaces or ports.

[0365] The antenna 15410, communication interface 15406, and / or the processing circuitry 15402 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 15400. Any information, data and / or signals may be received from a LIE, another network node and / or any other network equipment. Similarly, the antenna 15410, the communication interface 15406, and / or the processing circuitry 15402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 15400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0366] The power source 15408 provides power to the various components of network node 15400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 15408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 15400 with power for performing the functionality described herein. For example, the network node 15400 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 15408. As a further example, the power source 15408 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0367] Embodiments of the network node 15400 may include additional components beyond those shown in Fig. 13 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 15400 may include user interface equipment to allow input of information into the network node 15400 and to allow output of information from the network node 15400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 15400.

[0368] Fig. 14 is a block diagram illustrating a virtualization environment 15500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may includevirtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 15500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, LIE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 15500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0369] Applications 15502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0370] Hardware 15504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 15506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 15508A and VM 15508B (which may be collectively referred to as VMs 15508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 15506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 15508.

[0371] The VMs 15508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 15506. Different embodiments of the instance of a virtual appliance 15502 may be implemented on one or more of VMs 15508, and the implementations may be made in different ways.

[0372] Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.In the context of NFV, each of the VMs 15508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, nonvirtualized machine. Each of the VMs 15508, and that part of hardware 15504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 15508 on top of the hardware 15504 and corresponds to an application 15502.

[0373] Hardware 15504 may be implemented in a standalone network node with generic or specific components. Hardware 15504 may implement some functions via virtualization. Alternatively, hardware 15504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 15510, which, among others, oversees lifecycle management of applications 15502. In some embodiments, hardware 15504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 15512 which may alternatively be used for communication between hardware nodes and radio units.

[0374] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physicalcomponents that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0375] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0376] It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

Claims

77CLAIMS1. A method performed by a radio network node (120) for handling communication in a communication network, the method comprising- requesting (502) from a core network node (19), for information relating to an admission of a user equipment, UE, (10) to a network slice and / or a slice service; andreceiving (503) the requested information from the core network node (19).

2. The method according to claim 1 , wherein the information is related to failure of a service request on the network slice.

3. The method according to any of the claims 1-2, wherein the information indicates rejected Single Network Slice Selection Assistance Information, S-NSSAI, for the UE.

4. The method according to any of the claims 1-3, wherein requesting for the information comprises adding a request indication in an Information Element in an INITIAL UE MESSAGE or in an UPLINK NAS TRANSPORT message.

5. The method according to any of the claims 1-4, comprising- forwarding (505) the information to a managing node (15).

6. The method according to claim 5, comprising- adding (504) additional information for forwarding to the managing node (15), wherein the additional information comprises one or more of the following:■ cell information for a cell from which the UE (10) has initiated an admission request;■ if available, a geographical position of the UE (10) when the UE (10) initiated the admission request; and■ a time when the admission request was initiated by the UE (10) and / or received by the radio network node.

787. The method according to any of the claims 1-6, wherein requesting comprises subscribing to receive the information for one or more UEs served by the radio network node.

8. The method according to any of the claims 1-7, wherein the information is taken into account when configuring one or more parameters of a cell selection that is slice based.

9. The method according to claim 8, wherein configuring the one or more parameters comprises assigning a lowest priority level, or decreasing a priority for a network slice or a slice service being rejected; and / or removing the network slice or the slice service being rejected in the cell selection.

10. The method according to any of the claims 1-8, comprising- optimizing (506) one or more mobility related parameters associated to a network slice based on a number of mobility attempts and / or a number of failures in mobility attempts towards a cell where the network slice has no resources available.

11. A method performed by a core network node (19) for handling communication in a communication network, the method comprising:- receiving (511 ) a request from a radio network node (120), requesting for information relating to an admission of a user equipment, UE, (10) to a network slice and / or a slice service; andtransmitting (512) to the radio network node (120) the requested information for the UE (10).

12. The method according to claim 11 , wherein the information is related to failure of a service request on the network slice.

13. The method according to any of the claims 11-12, wherein the information indicates rejected Single Network Slice Selection Assistance Information, S- NSSAI, for the UE (10).

14. The method according to any of the claims 11-13, wherein the request is comprised in an Information Element in an INITIAL UE MESSAGE or in an UPLINK NAS TRANSPORT message.7915. The method according to any of the claims 11-14, wherein the request comprises subscription to receive the information for one or more UEs served by the radio network node.

16. A method performed by a managing node (15) for handling communication in a communication network, the method comprisingreceiving (602) from a radio network node (120), information for a user equipment, LIE, 10, wherein the information relating to an admission of a user equipment, UE, (10) to a network slice and / or a slice service; and - performing (603) an operation taking the information into account.

17. The method according to claim 16, wherein the information is related to failure of a service request on the network slice18. The method according to any of the claims 16-17, the operation comprises updating network slice support and network slice availability based on the received information.

19. The method according to any of the claims 16-18, wherein the information indicates rejected Single Network Slice Selection Assistance Information, S- NSSAI, for the UE (10).

20. The method according to any of the claims 16-19, wherein the information further comprises additional information, wherein the additional information comprises one or more of the following:■ cell information for a cell from which the UE (10) has initiated an admission request;■ if available, a geographical position of the UE (10) when the UE (10) initiated the admission request; and■ a time when the admission request was initiated by the UE (10) and / or received by the radio network node.

21. A computer program comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according80to any of the claims 1-20, as performed by the managing node, the core network node, or the radio network node, respectively.

22. A computer-readable storage medium, having stored thereon a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-20, as performed by the managing node, the core network node, or the radio network node, respectively.

23. A system for handling communication in a communication network, wherein the system comprises a radio network node (120), a core network node (19) and a managing node (19), wherein:the radio network node (120) is configured to request from the core network node (19), for information relating to an admission of a user equipment, UE, (10) to a network slice and / or a slice service; andthe core network node (19) is configured to transmit the requested information to the radio network node (120).

24. A radio network node (120) for handling communication in a communication network, wherein the radio network node is configured to:request from a core network node (19), for information relating to an admission of a user equipment, UE, (10) to a network slice and / or a slice service; and receive the requested information from the core network node (19).

25. The radio network node according to claim 24, wherein the information is related to failure of a service request on the network slice26. The radio network node (120) according to any of the claims 24-25, wherein the information indicates rejected Single Network Slice Selection Assistance Information, S-NSSAI, for the UE (10).

27. The radio network node (120) according to any of the claims 24-26, wherein the radio network node (120) is configured to add a request indication, for requesting the information, in an Information Element in an INITIAL UE MESSAGE or in an UPLINK NAS TRANSPORT message.8128. The radio network node (120) according to any of the claims 24-27, wherein the radio network node is configured toforward the information to a managing node (15).

29. The radio network node (120) according to claim 28, wherein the radio network node (120) is configured toadd additional information for forwarding to the managing node (15), wherein the additional information comprises one or more of the following:■ cell information for a cell from which the LIE (10) has initiated an admission request;■ if available, a geographical position of the UE (10) when the UE (10) initiated the admission request; and■ a time when the admission request was initiated by the UE (10) and / or received by the radio network node.

30. The radio network node (120) according to any of the claims 21-25, wherein the radio network node is configured to subscribe to receive the information for one or more UEs served by the radio network node.

31. The radio network node (120) according to any of the claims 21 -26, wherein the radio network node is configured to take the information into account when configuring one or more parameters of a cell selection that is slice based.

32. The radio network node (120) according to claim 27, wherein configuring the one or more parameters comprises assigning a lowest priority level, or decreasing a priority for a network slice or a slice service being rejected; and / or removing the network slice or the slice service being rejected in the cell selection.

33. The radio network node (120) according to any of the claims 21-28, wherein the radio network node is configured to optimize one or more mobility related parameters associated to a network slice based on a number of mobility attempts and / or a number of failures in mobility attempts towards a cell where the network slice has no resources available.

34. A core network node (19) for handling communication in a communication network, wherein the core network node (19) is configured to:82receive a request from a radio network node (120), requesting for information relating to an admission of a user equipment, UE, (10) to a network slice and / or a slice service; andtransmit to the radio network node (120) the requested information for the UE (10).

35. The core network node (19) according to claim 34, wherein the information is related to failure of a service request on the network slice.

36. The core network node (19) according to any of the claims claim 34-35, wherein the information indicates rejected Single Network Slice Selection Assistance Information, S-NSSAI, for the UE (10).

37. The core network node (19) according to any of the claims 34-36, wherein the request is comprised in an Information Element in an INITIAL UE MESSAGE or in an UPLINK NAS TRANSPORT message.

38. The core network node (19) according to any of the claims 34-37, wherein the request comprises subscription to receive the information for one or more UEs served by the radio network node.

39. A managing node (15) for handling communication in a communication network, wherein the managing node (15) is configured toreceive from a radio network node (120), information for a user equipment, UE, (10), wherein the information relating to an admission of a user equipment, UE, (10) to a network slice and / or a slice service; andperform an operation taking the information into account.

40. The managing node (15) according to claim 39, wherein the information is related to failure of a service request on the network slice.

41. The managing node (15) according to any of the claims 39-40, the operation comprises updating network slice support and network slice availability based on the received information.

42. The managing node (15) according to any of the claims 39-41 , wherein the information indicates rejected Single Network Slice Selection Assistance Information, S-NSSAI, for the LIE (10).

43. The managing node (15) according to any of the claims 39-42, wherein the information further comprises additional information, wherein the additional information comprises one or more of the following:■ cell information for a cell from which the LIE (10) has initiated an admission request;■ if available, a geographical position of the UE (10) when the UE (10) initiated the admission request; and■ a time when the admission request was initiated by the UE (10) and / or received by the radio network node.

Images