Dynamic slice selection and session management

The method addresses the inflexibility of existing network slicing by dynamically propagating slice characteristics across peer-to-peer communications, enhancing user experience and enabling consistent performance in applications like AR and VR.

WO2026233539A1PCT designated stage Publication Date: 2026-11-12TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/EP2025/062367
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-06
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing network slicing technologies in 5G networks lack flexibility and consistency in selecting and managing network slices, particularly in complex communication scenarios with diverse application requirements and user profiles, leading to sub-optimal performance in peer-to-peer communications.

Method used

A method for dynamic slice selection and session management that propagates the network slice characteristics chosen by the originating party to the called party, ensuring consistent application across all participants in a peer-to-peer communication.

Benefits of technology

Ensures enhanced user experience and end-to-end service alignment by consistently applying network slice characteristics like latency and bandwidth, enabling advanced use cases such as AR and VR scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure EP2025062367_12112026_PF_FP_ABST
    Figure EP2025062367_12112026_PF_FP_ABST
Patent Text Reader

Abstract

There is provided a method for dynamic slice selection and session management performed by a first network function (302) in an originating side of a communication network. The method comprises obtaining a slice type indicator (308) associated with a selected communication slice for an initiating UE (300) as part of a session initiation. The method also comprises transmitting the slice type indicator (308) to a receiving side of the communication network, wherein the transmitted slice type indicator is intended to be used for selecting a communication slice at the receiving side of the communication network. There is also provided a method for slice selection and session management performed by a second network function (304) at a receiving side of a communication network.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] DYNAMIC SLICE SELECTION AND SESSION MANAGEMENT

[0002] TECHNICAL FIELD

[0003] Embodiments presented herein relate to methods, system, a first network function, a second network function and computer program products for dynamic slice selection and session management in a telecommunications network.

[0004] BACKGROUND

[0005] The evolution of 5th Generation (5G) networks has introduced the concept of network slicing, a transformative technology that allows for the creation of multiple virtualized and independent logical networks within a single physical infrastructure. Each network slice can be tailored to meet the specific requirements of different applications and services, offering unparalleled flexibility and efficiency.

[0006] Traditionally, network slicing involved predefined configurations and operator-driven policies.

[0007] In the context of two-way communication, such as voice calls or interactive data sessions, the characteristics of the required network slice are often provisioned using a default (for e.g. Enhanced Mobile Broadband (eMBB)) network slice. This default slice provides a general-purpose, high-bandwidth communication channel suitable for a wide range of applications.

[0008] Fig 1 illustrates a general diagram showing two-way communication (e.g., a call or a data session) between a calling party (via a User Equipment (UE 1), UE 10) and a called Party (via a User Equipment (UE 2), UE 20) utilizing slice information currently executed as part of the Prior Art.

[0009] The communication happens in two phases (leaps); the first leap where UE 10 initiates communication via a slice supported by operator 1 and second leap where communication reaches UE 20 via a slice supported by operator 2. However, how the network slice is chosen differs between the two leaps. The first leap allows more dynamic, user-driven slice selection but the second leap is based on static, operator-controlled slice selection.As illustrated in Figure 1, the determination of the network slice in the initial phase, or "first leap," of a two-party based transaction is often governed by the UE Route Selection Policy (URSP) configured in the calling party's User Equipment (UE), UE 10 and the policies defined in a network function, for example in a Policy Control Function (PCF). This allows for a degree of user or application-driven control over the initial session setup.

[0010] According to Fig 1, slices available in the first leap (operator 1’s network) are:

[0011] eMBB - Enhanced Mobile Broadband (e.g., for video streaming or high-data- rate applications)

[0012] URLLC - Ultra-Reliable Low-Latency Communication (e.g., for industrial automation or telemedicine)

[0013] mMTC - Massive Machine Type Communication (e.g., for loT sensors and telemetry)

[0014] Multimedia - Possibly for general multimedia traffic like video or voice However, in the subsequent phase, or "second leap," of the two-party transaction, the network slice selection is typically controlled by static mapping based on operator policies for connecting the session to the called party’s UE, UE 20. This approach enables the network operator to maintain control over resource allocation and ensure optimal network performance for the return path of the communication. In Fig 1, the slices available in the second leap (operator 2’s network) are:

[0015] eMBB - For high-speed data

[0016] Urgency - Possibly for emergency or critical communication services

[0017] mMTC - For machine-type communications

[0018] The operator 2 predefines one of these slices to complete the two-way communication session in the second leap. While these advancements offer significant benefits in terms of flexibility and resource utilization, there remains a need for further optimization and refinement in the dynamic selection and management of network slices, particularly in complex communication scenarios involving diverse application requirements and user profiles.SUMMARY

[0019] The present application addresses limitations in existing systems for managing network slice selection in peer-to-peer communications, particularly in scenarios with stringent requirements such as real-time gaming using Augmented Reality (AR) and Virtual Reality (VR). In such cases, while one communicating party may select a network slice with desirable characteristics (e.g., lowest latency), those characteristics are not consistently applied to other parties involved in the communication. Current implementations often rely on operators defining static mappings between slices for the initial and subsequent phases of a communication session. This approach introduces inflexibility and may not guarantee that all parties benefit from the optimal network slice.

[0020] To overcome these limitations, a method is proposed to propagate the network slice characteristics chosen by the originating party or the calling party to the called party. This ensures that the desired network slice characteristics are consistently applied across all participants in a peer-to-peer communication.

[0021] According to a first aspect there is presented a method for dynamic slice selection and session management performed by a first network function in an originating side of a communication network. The method comprises obtaining a slice type indicator associated with a selected communication slice for an initiating UE as part of a session initiation. The method also comprises transmitting the slice type indicator to a receiving side of the communication network, wherein the transmitted slice type indicator is intended to be used for selecting a communication slice at the receiving side of the communication network.

[0022] According to a second aspect there is presented a method wherein the selected communication slice is selected from a plurality of available slice based on one or more service characteristics.

[0023] According to a third aspect there is presented a method for slice selection and session management performed by a second network function at a receiving side of a communication network. The method comprises receiving information associated with a slice type indicator, wherein the slice type indicator is associated with a selected communication slice for an initiating UE as part of a session initiation.

[0024] Further the method comprises determining whether a receiving UE is entitled toaccess a communication slice indicated by the slice type indicator and establishing a communication session between the initiating and receiving UE based on the above determination.

[0025] According to a fourth aspect there is presented a method, which further comprises inferring one or more service characteristics associated with the received slice type indicator at the receiving side of the communication network.

[0026] According to a fifth aspect there is presented a method, wherein determining whether a receiving UE is entitled to access the communication slice further comprises checking associated policies for permitting usage of the communication slice by the receiving UE.

[0027] According to a sixth aspect there is presented a method, wherein determining whether the receiving UE is entitled to access the communication slice indicated by the slice type indicator further comprises checking the availability of the slice indicated by the slice indicator.

[0028] According to a seventh aspect there is presented a first network function for slice selection and session management in an originating side of a communication network. The first network function comprising processing circuitry and a memory storing instructions, wherein the instructions are such that they, when executed by the processing circuitry, cause the first network function to obtain a slice type indicator associated with a selected communication slice for an initiating UE as part of a session initiation. The first network function is also configured to transmit the slice type indicator to a receiving side of the communication network, wherein the transmitted slice type indicator is intended to be used for selecting a communication slice at the receiving side of the communication network.

[0029] According to an eighth aspect there is presented a computer program product for handling slice selection and session management in a first network function in an originating side of a communication network. The computer program product comprises a non-transitory computer-readable medium having computer-executable instructions stored thereon, the instructions when executed by processing circuitry, causing the processing circuitry to obtain a slice type indicator associated with a selected communication slice for an initiating UE as part of a session initiation. The instructions when executed by processing circuitry, causing the processing circuitryto transmit the slice type indicator to a receiving side of the communication network, wherein the transmitted slice type indicator is intended to be used for selecting a communication slice at the receiving side of the communication network.

[0030] According to a ninth aspect there is presented a second network function for slice selection and session management in a receiving side of a communication network. The second network function comprising processing circuitry and a memory storing instructions, wherein the instructions are such that they, when executed by the processing circuitry, cause the second network function to receive information associated with a slice type indicator, wherein the slice type indicator is associated to a selected communication slice for an initiating UE as part of a session initiation. The instructions are such that they, when executed by the processing circuitry, cause the second network function to determine whether a receiving UE is entitled to access a communication slice indicated by the slice type indicator and establish a communication session between the initiating and receiving UE based on the above determination.

[0031] According to a tenth aspect there is presented a computer program product for handling slice selection and session management in a second network function in a receiving side of a communication network. The computer program product comprises a non-transitory computer-readable medium having computer-executable instructions stored thereon, the instructions, when executed by processing circuitry, causing the processing circuitry to receive information associated with a slice type indicator, wherein the slice type indicator is associated to a selected communication slice for an initiating UE as part of a session initiation. The instructions, when executed by processing circuitry, causing the processing circuitry to determine whether a receiving UE is entitled to access a communication slice indicated by the slice type indicator; and establish a communication session between the initiating and receiving UE based on the above determination.

[0032] According to an eleventh aspect there is presented a method for slice selection and session management in a communication network. At an originating side of the communication network, the method comprises obtaining a slice type indicator associated with a selected communication slice for an initiating UE as part of a session initiation and transmitting the slice type indicator to a receiving side of thecommunication network. At the receiving side of the communication network, the method comprises receiving, at a receiving UE, the transmitted slice type indicator. The method further comprises determining whether the receiving UE is entitled to access the communication slice indicated by the slice type indicator and establishing a communication session between the initiating and receiving UE based on the above determination.

[0033] According to a twelfth aspect there is presented a system for slice selection and session management in a communication network. The system comprises a first network function at an originating side of the communication network, the first function adapted to obtain a slice type indicator associated to a selected communication slice for an initiating UE as part of a session initiation and transmit the slice type indicator to a receiving side of the communication network. The system further comprises a second network function at the receiving side of the communication network, the second function adapted to receive, for a receiving UE, the transmitted slice type indicator. The system further is adapted to determine whether the receiving UE is entitled to access the communication slice indicated by the slice type indicator and establish a communication session between the initiating and receiving UE based on the above determination.

[0034] Advantageously, these aspects guarantee enhanced user experience. The consistent application of network slice characteristics, such as latency and bandwidth, across all communicating parties provides an enhanced and more uniform user experience.

[0035] Advantageously, these aspects ensures that the selected network slice type is consistently and automatically enforced across both the initiating and receiving ends of a multi-user communication session, enabling end-to-end service alignment.

[0036] Advantageously, these aspects enable advanced use cases. The invention facilitates new use cases involving direct interaction between communicating parties, particularly in applications with stringent network requirements, such as AR and VR scenarios.

[0037] Other objectives, features and advantages of the enclosed embodiments will be apparent from the following detailed disclosure, from the attached dependent claims as well as from the drawings.Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise herein. All references to "a / an / the element, function, apparatus, component, means, module, step, etc." are to be interpreted openly as referring to at least one instance of the element, function, apparatus, component, means, module, step, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated.

[0038] BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The inventive concept is now described, by way of example, with reference to the accompanying drawings, in which:

[0040] Fig 1 illustrates a general diagram showing two-way communication between a calling party and a called Party utilizing slice information currently executed as part of the Prior Art;

[0041] Fig 2a is a flowchart illustrating a method for dynamic slice selection and session management performed by a first network function in an originating side of a communication network;

[0042] Fig 2b is a flowchart illustrating a method for slice selection and session management performed by a second network function at a receiving side of a communication network;

[0043] Fig 3 is a block diagram illustrating a system for slice selection and session management in a communication network;

[0044] Fig 4 is a signal flow diagram illustrating method performed by the system for slice selection and session management in a communication network;

[0045] Fig 5 is a flowchart illustrating method performed at the second network function according to an embodiment;

[0046] Fig 6 is a schematic diagram showing structural units of a first network function according to an embodiment;Fig 7 is a schematic diagram showing structural units of a second network function according to an embodiment; and

[0047] Fig. 8 shows one example of a computer program product according to an embodiment.

[0048] DETAILED DESCRIPTION

[0049] The inventive concept will now be described more fully hereinafter with reference to the accompanying drawings, in which certain embodiments of the inventive concept are shown. This inventive concept may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example so that this disclosure will be thorough and complete, and will fully convey the scope of the inventive concept to those skilled in the art. Like numbers refer to like elements throughout the description. Any step or feature illustrated by dashed lines should be regarded as optional.

[0050] To capture the broad spectrum of use cases and to simplify the understanding, primarily two types of Network Functions (NF) are introduced in our explanations, i.e. a first network function and a second network function. Practically these network functions could be but are not limited to any of an AMF (Access and Mobility Management Function), SMF (Session Management Function), UPF (User Plane Function), UDF (Unified Data Repository), PCF (Policy Control Function), NSSF (Network Slice Selection Function), NRF (Network Repository Function), CHF (Charging Function), MB-SMF (Multicast / Broadcast Session Management Function), SMSF (Short Message Service Function), Network Exposure Function (NEF) etc.

[0051] Fig 2a is a flowchart illustrating a method for dynamic slice selection and session management performed by a first network function in an originating side of a communication network. This flowchart outlines a simple but effective two-step process. First, acquiring the relevant slice type for the UE during session setup. Then, forwarding this information to assist in proper slice selection on the other end of the network.Step S102: Obtain Slice Type Indicator

[0052] The first network function, located on the originating side of the communication network, obtains a slice type indicator. This indicator is associated with a selected communication slice that is intended for use by an initiating User Equipment (UE). The slice type indicator is obtained as part of session initiation for the UE.

[0053] Step S104: Transmit Slice Type Indicator

[0054] The first network function then transmits the slice type indicator to the receiving side of the communication network. This transmission is intended to enable the receiving side to use the slice type indicator for selecting a suitable communication slice for further handling of the session.

[0055] Fig 2b is a flowchart illustrating a method for slice selection and session management performed by a second network function at a receiving side of a communication network.

[0056] Step S202: Receive Slice Type Indicator Information

[0057] The second network function (at the receiving side) receives information associated with a slice type indicator. This indicator corresponds to a selected communication slice for an initiating User Equipment (UE). The information is received as part of a session initiation process.

[0058] The second network function infers one or more service characteristics associated with the received slice type indicator. These inferred characteristics may comprise requirements like latency, bandwidth, reliability, or application-specific needs (e.g., real-time gaming, video conferencing, loT telemetry). This step helps the receiving side to understand the service intent behind the selected slice.

[0059] Step S204: Determine Receiving UE Entitlement

[0060] The second network function determines whether the receiving UE is entitled to access the communication slice indicated by the received slice type indicator. This includes checking associated policies, such as subscription data, access rights, or operator-defined rules, to verify if the receiving UE is permitted to use the slice.Additionally, the function checks the availability of the indicated slice— i.e., whether the slice is currently deployed, active, and capable of handling the incoming session for the receiving UE. This step ensures proper authorization and compatibility with the selected slice.

[0061] Step S206: Establish Communication Session

[0062] Based on the entitlement determination in step S204, and if entitlement and availability checks succeed, the network function establishes a communication session between the initiating UE and the receiving UE using the appropriate communication slice which is based on the slice type indicator. This ensures end-to-end service alignment based on the selected slice characteristics.

[0063] Although Fig. 2a and Fig. 2b show different sides (originating and receiving), the two methods closely interact to provide a seamless end-to-end communication system.

[0064] This can be explained by a practical example. In certain emergency healthcare scenarios, a medical professional, such as Doctor Mr. X, may initiate a real-time communication session, such as a video call, with a patient, Mrs. Y, using a communication application. The underlying communication infrastructure may leverage network slicing, wherein multiple virtualized and isolated network segments (i.e., network slices) are provisioned to support differing service requirements, such as latency, throughput, or reliability.

[0065] At the originating end (i.e., Doctor X’s device or application), the application may trigger a selection mechanism to identify and utilize the network slice offering optimal performance characteristics— e.g., the slice with the lowest latency and highest reliability. This selection may be performed dynamically based on the nature of the application or service requirements, enabling the originating party to utilize a best-in-class network slice.

[0066] However, when the communication session request reaches the terminating end (i.e., the patient’s device), the network slice configured by default by the operator may not reflect the quality-of-service (QoS) requirements appropriate for the session. This can lead to sub-optimal performance at the receiving side, particularly in criticalscenarios such as telemedicine emergencies, where high-quality, low-latency communication is essential.

[0067] To address the aforementioned challenge, the present solution proposes that a first network function associated with the originating side (Doctor X) enforces a best-in-class network slice selection at the terminating side (Patient Y). Upon initiation of the communication session, the selected network slice at the originating side is communicated to the terminating network.

[0068] A second network function at the terminating side receives this information and based on enforcement instructions or policies, overrides the default network slice configuration provisioned by the operator. The second network function then aligns the terminating side to operate on the same or an equivalent high-performance network slice as selected by the originating side.

[0069] As a result, the network session benefits from an end-to-end (E2E) quality-of-service alignment, wherein both ends of the communication utilize a network slice with best-in-class characteristics suitable for emergency services or other latency-sensitive applications.

[0070] Fig 3 is a block diagram illustrating a system for slice selection and session management in a communication network. Initiating User Equipment (UE) 300 is the device initiating the communication session, e.g., a smartphone, loT device, etc. First Network Function 302 resides on the originating side of the communication network and is responsible for obtaining a Slice Type Indicator 308 associated with a selected communication slice. The selected slice is determined based on service requirements of the initiating UE. First Network Function 302 then transmits the slice type indicator to the receiving side to assist in session alignment. Slice Type Indicator 308 is a slice identifier passed from the originating to receiving side. It indicates the selected communication slice suitable for the initiating UE’s service characteristics.

[0071] Examples of slice types:

[0072] eMBB 310 - Enhanced Mobile Broadband (e.g., for video streaming or high- data-rate applications).URLLC 312 - Ultra-Reliable Low-Latency Communication (e.g., for industrial automation or telemedicine).

[0073] mMTC 314 - Massive Machine Type Communication (e.g., for loT sensors and telemetry).

[0074] Second Network Function 304 is located on the receiving side of the network. It is responsible for receiving the slice type indicator passed from the originating side. It also determines whether the receiving UE 306 is entitled to access the slice indicated by the slice type indicator 308. This may involve policy checks and slice availability checks. Finally, it is responsible for establishing the communication session if all conditions are met. Receiving User Equipment (UE) 306 is the target device for the session, which receives communication from the initiating UE.

[0075] The connection flow through the system work like this. The initiating UE 300 starts a communication session. The first network function 302 selects an appropriate communication slice (e.g., eMBB, URLLC, mMTC) based on the initiating UE's needs. A slice type indicator 308 corresponding to the selected slice is obtained and transmitted to the second network function 304 on the receiving side. The second network function 304 receives the slice type indicator and checks if the receiving UE 306 is authorized and capable of using the indicated slice. If conditions are satisfied, the communication session is established between the initiating UE 300 and receiving UE 306 using the selected slice which corresponds to the slice type indicator 308.

[0076] In cases where the receiving UE is not subscribed to the indicated slice type or the network provider does not support the slice, the session gracefully defaults to a standard slice type, ensuring uninterrupted connectivity.

[0077] Fig 4 is a signal flow diagram illustrating method performed by the system for slice selection and session management in a communication network

[0078] Step S410: PDU Session Request

[0079] The Initiating UE 402 sends a PDU session request to the First Network Function 404. This initiates the procedure for setting up a new session and may include service-related requirements.Step S412: PDU Session Accept

[0080] In response, the First Network Function 404 accepts the session request and responds to the Initiating UE 402 with a PDU session accept message. This step confirms that the session can be established on the originating side.

[0081] Step S414: PDU Session with selected Slice

[0082] The Initiating UE 402 provides PDU session information with the selected slice to the First Network Function 404. This slice reflects the type of communication slice suitable for the session (e.g., eMBB, URLLC, mMTC), based on service characteristics.

[0083] Step S416: Pass PDU Session Info with Slice Type Indicator

[0084] The First Network Function 404 selects a communication slice (e.g., eMBB, URLLC, mMTC) based on the initiating UE's service characteristics. It obtains or generates a corresponding slice type indicator and includes it in the PDU session information. This PDU session info with the slice type indicator is passed to the Second Network Function 406 on the receiving side.

[0085] Step S418: Pass / Forward PDU Session Info to Receiving UE

[0086] The Second Network Function 406 forwards the PDU session information, including the received slice type indicator, to the Receiving UE 408. This prepares the receiving side for the potential communication session.

[0087] Step S420: Determine UE Entitlement for Slice Access

[0088] The Second Network Function 406 now evaluates whether the Receiving UE 408 is entitled to access the communication slice indicated by the slice type indicator. This may involve policy checks to ensure the UE has the necessary rights or subscription. This may also include slice availability checks to verify that the slice is active and usable for the session.

[0089] Step S422: Session EstablishmentIf the entitlement and availability checks are successful, the Second Network Function 406 proceeds to establish the communication session between the Initiating UE 402 and the Receiving UE 408. The session is established using the selected slice, ensuring service alignment across both ends.

[0090] In a representative use case, consider two professional fencing players, Mr. Z and Ms. W, who are scheduled to compete in a virtual fencing match as part of a global e-sports tournament. Due to international travel advisories, physical attendance is not possible, and the match is to be conducted through an immersive Augmented Reality (AR) / Virtual Reality (VR) gaming platform.

[0091] Mr. Z resides in Canada and is connected to a first network operator, while Ms. W, located in China, is subscribed to a different network operator. Despite being on disparate operator infrastructures, the tournament organizers require that both players experience identical network performance characteristics, such that network performance does not bias the outcome of the game.

[0092] To address this, both players initiate a session using their AR / VR equipment. Upon session initiation by Mr. Z (the initiating party), the originating network function determines a network slice optimized for real-time, low-latency, and high-throughput requirements necessary for AR / VR-based competitive gaming. The selected network slice, which may correspond to an eMBB (enhanced Mobile Broadband) slice with ultra-low latency tuning, is associated with a corresponding slice type indicator.

[0093] The slice type indicator is then transmitted along with the session setup information to the receiving side. On the receiving side, the network function (e.g., a Session Management Function or equivalent) overrides its default network slice selection policy and enforces the same slice type as indicated by the originating side. This action ensures that both endpoints of the communication session utilize the same class of network slice, thereby enabling End-to-End (E2E) consistency in network performance.

[0094] This dynamic override and harmonization of slice selection allows the tournament sponsor's goal to be achieved: a fair, synchronized, and high-performance AR / VR gaming experience, despite operator and geographical disparities. This scenario illustrates the technical advantage of enabling slice-type indicator propagation andoverride mechanisms across the communication network to enforce consistent quality of service in multi-party immersive applications.

[0095] Fig 5 is a flowchart illustrating a method performed at the second network function according to an embodiment. These steps provide further granularity for step S204 of Fig 2b on how the system verifies whether the receiving UE is entitled to access the communication slice indicated by the slice type indicator.

[0096] Step S502: Check Associated Policies

[0097] The second network function checks policy rules to determine whether the receiving UE is permitted to use the indicated communication slice. These policies may include subscription information, operator-defined access rules, service profiles, authorization databases.

[0098] Step S504: Check Slice Availability

[0099] The network function also checks if the indicated slice is currently available. This includes verifying if the slice is deployed and active, if there is capacity to accommodate the new session or verifying any dynamic network conditions affecting slice availability.

[0100] If both policy and availability checks succeed, the receiving UE is deemed entitled to use the slice. The communication session between the initiating and receiving UEs is established as mentioned in step S206, Fig 2b, using the slice corresponding to the slice type indicator based on the entitlement validation.

[0101] Fig. 6 schematically illustrates, in terms of a number of structural units, the components of a first network function 600 according to an embodiment. The first network function 600 comprises processing circuitry 610. Processing circuitry 610 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 810a (as in Fig. 8), e.g. in the form of a storage medium or memory 630. The processing circuitry 610 may further be provided as at least one Application Specific Integrated Circuit (ASIC), or Field-Programmable Gate Array (FPGA).Particularly, the processing circuitry 610 is configured to cause the first network function 600 to perform a set of operations, or steps, as disclosed above. For example, the storage medium 630 may store the set of operations, and the processing circuitry 610 may be configured to retrieve the set of operations from the storage medium 630 to cause the first network function 600 to perform the set of operations. The set of operations may be provided as a set of executable instructions. Thus, the processing circuitry 610 is thereby arranged to execute methods as herein disclosed.

[0102] The storage medium or memory 630 may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.

[0103] The first network function 600 may further comprise a communications (Comm) interface 620 for communications with other entities, network functions, nodes, and devices, as in Figs. 3 and 4. As such the communications interface 620 may comprise one or more transmitters and receivers, comprising analogue and digital components.

[0104] As mentioned above the first network function 600 for slice selection and session management in an originating side of a communication network comprises processing circuitry 610 and a memory or storage medium 630 storing instructions. The instructions are such that they, when executed by the processing circuitry 610, cause the first network function to obtain a slice type indicator associated with a selected communication slice for an initiating UE as part of a session initiation. The execution of instructions by the processing circuitry 610 also causes the first network function 600 to transmit the slice type indicator to a receiving side of the communication network via a communications interface 620, wherein the transmitted slice type indicator is intended to be used for selecting a communication slice at the receiving side of the communication network.

[0105] The processing circuitry 610 controls the general operation of the first network function 600 e.g. by sending data and control signals to the communications interface 620 and the storage medium 630, by receiving data and reports from the communications interface 620, and by retrieving data and instructions from the storage medium 630. The processing circuitry also comprises of a selector 615, to select a communication slice from a plurality of available slice based on one or more service characteristics. Other components, as well as the related functionality, of thefirst network function 600 are omitted in order not to obscure the concepts presented herein.

[0106] Fig. 7 schematically illustrates, in terms of a number of structural units, the components of a second network function 700 according to an embodiment. The second network function 700 comprises processing circuitry 710. Processing circuitry 710 is provided using any combination of one or more of a suitable central processing unit (CPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions stored in a computer program product 810b (as in Fig. 8), e.g. in the form of a storage medium or memory 730. The processing circuitry 710 may further be provided as at least one ASIC, or FPGA.

[0107] Particularly, the processing circuitry 710 is configured to cause the second network function 700 to perform a set of operations, or steps, as disclosed above. For example, the storage medium 730 may store the set of operations, and the processing circuitry 710 maybe configured to retrieve the set of operations from the storage medium 730 to cause the second network function 700 to perform the set of operations. The set of operations may be provided as a set of executable instructions. Thus, the processing circuitry 710 is thereby arranged to execute methods as herein disclosed.

[0108] The storage medium or memory 730 may also comprise persistent storage, which, for example, can be any single one or combination of magnetic memory, optical memory, solid state memory or even remotely mounted memory.

[0109] The second network function 700 may further comprise a communications (Comm) interface 720 for communications with other entities, functions, nodes, and devices, as in Figs. 3 and 4. As such the communications interface 720 may comprise one or more transmitters and receivers, comprising analogue and digital components.

[0110] As explained above the second network function 700 for slice selection and session management in a receiving side of a communication network comprises processing circuitry 710 and a memory 730 storing instructions. The instructions are such that they, when executed by the processing circuitry 710, cause the second network function 700 to receive information associated with a slice type indicator, wherein the slice type indicator is associated to a selected communication slice for an initiatingUE as part of a session initiation. The execution of instructions by the processing circuitry 710 also causes the second network function 700 to determine whether a receiving UE is entitled to access a communication slice indicated by the slice type indicator and establish a communication session between the initiating and receiving UE based on the above determination.

[0111] The processing circuitry 710 controls the general operation of the second network function 700 e.g. by sending data and control signals to the communications interface 720 and the storage medium 730, by receiving data and reports from the communications interface 720, and by retrieving data and instructions from the storage medium 730. The processing circuitry 710 also comprises of a detector 715, which determine whether a receiving UE is entitled to access a communication slice indicated by the slice type indicator. Other components, as well as the related functionality, of the second node 700 are omitted in order not to obscure the concepts presented herein.

[0112] Fig. 8 shows one example of a computer program product 810a, 810b, comprising computer readable means 830. On this computer readable means 830, a computer program 820a can be stored, which computer program 820a can cause the processing circuitry 610 of the first network function 600 and thereto operatively coupled entities and devices, such as the communications interface 620, the storage medium 630 and selector 615 to execute methods according to embodiments described herein. The computer program 820a and / or computer program product 810a may thus provide means for performing any steps of the first network function 600 as herein disclosed.

[0113] On this computer readable means 830, a computer program 820b can be stored, which computer program 820b can cause the processing circuitry 710 of a second network function 700 and thereto operatively coupled entities and devices, such as the communications interface 720, the storage medium 730 and detector 715, to execute methods according to embodiments described herein. The computer program 820b and / or computer program product 810b may thus provide means for performing any steps of the second network function 700 as herein disclosed.

[0114] In the example of Fig. 8, the computer program product 810a, 810b, is illustrated as an optical disc, such as a CD (compact disc) or a DVD (digital versatile disc) or a Blu-Ray disc. The computer program product 810a, 810b could also be embodied as a memory, such as a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or an electrically erasable programmable read-only memory (EEPROM) and more particularly as a non-volatile storage medium of a device in an external memory such as a USB (Universal Serial Bus) memory or a Flash memory, such as a compact Flash memory. Thus, while the computer program 820a, 820b is here schematically shown as a track on the depicted optical disk, the computer program 820a, 820b can be stored in any way which is suitable for the computer program product 810a, 810b.

[0115] The inventive concept has mainly been described above with reference to a few embodiments. However, as is readily appreciated by a person skilled in the art, other embodiments than the ones disclosed above are equally possible within the scope of the inventive concept, as defined by the appended patent claims.

Claims

CLAIMS1. A method for dynamic slice selection and session management performed by a first network function (302) in an originating side of a communication network, the method comprising:obtaining a slice type indicator (308) associated with a selected communication slice for an initiating UE (300) as part of a session initiation; andtransmitting the slice type indicator (308) to a receiving side of the communication network, wherein the transmitted slice type indicator (308) is intended to be used for selecting a communication slice at the receiving side of the communication network.

2. The method of claim 1 wherein the selected communication slice is selected from a plurality of available slice based on one or more service characteristics.

3. A method for slice selection and session management performed by a second network function (304) at a receiving side of a communication network, the method comprising:receiving information associated with a slice type indicator (308), wherein the slice type indicator is associated with a selected communication slice for an initiating UE (300) as part of a session initiation;determining whether a receiving UE (306) is entitled to access a communication slice indicated by the slice type indicator; andestablishing a communication session between the initiating and receiving UE based on the above determination.

4. The method of claims 3 further comprises inferring one or more service characteristics associated with the received slice type indicator at the receiving side of the communication network.

5. The method of claim 3 or 4 wherein determining whether a receiving UE (306) is entitled to access the communication slice further comprises checking associated policies for permitting usage of the communication slice by the receiving UE (306).

6. The method of claim 3 wherein determining whether the receiving UE (306) is entitled to access the communication slice indicated by the slice type indicator further comprises checking the availability of the slice indicated by the slice indicator.

7. A first network function (302, 600) for slice selection and session management in an originating side of a communication network, the first network function comprising processing circuitry (610) and a memory (630) storing instructions, wherein the instructions are such that they, when executed by the processing circuitry, cause the first network function to:obtain a slice type indicator (308) associated with a selected communication slice for an initiating UE as part of a session initiation; andtransmit the slice type indicator (308) to a receiving side of the communication network, wherein the transmitted slice type indicator (308) is intended to be used for selecting a communication slice at the receiving side of the communication network.

8. The first network function (302, 600) of claim 7 wherein the selected communication slice is selected from a plurality of available slice based on one or more service characteristics.

9. A computer program product (810a) for handling slice selection and session management in a first network function (302, 600) in an originating side of a communication network, the computer program product (810a) comprising:a non-transitory computer-readable medium having computer-executable instructions stored thereon, the instructions, when executed by processing circuitry (610), causing the processing circuitry to:obtain a slice type indicator (308) associated with a selected communication slice for an initiating UE (300) as part of a session initiation; andtransmit the slice type indicator (308) to a receiving side of the communication network, wherein the transmitted slice type indicator is intended to be used for selecting a communication slice at the receiving side of the communication network.

10. A second network function (304, 700) for slice selection and session management in a receiving side of a communication network, the second network function comprising processing circuitry (710) and a memory (730) storing instructions, wherein the instructions are such that they, when executed by the processing circuitry (710), cause the second network function to:receive information associated with a slice type indicator (308), wherein the slice type indicator is associated to a selected communication slice for an initiating UE (300) as part of a session initiation;determine whether a receiving UE (306) is entitled to access a communication slice indicated by the slice type indicator; andestablish a communication session between the initiating and receiving UE based on the above determination.

11. The second network function (304, 700) of claim 10 wherein the network function is further adapted to infer one or more service characteristics associated with the received slice type indicator at the receiving side of the communication network.

12. The second network function (304, 700) of claim 10 wherein the network function is further adapted to check associated policies for permitting usage of the communication slice by the receiving UE (306).

13. The second network function (304, 700) of claim 10 wherein the network function is further adapted to check the availability of the slice indicated by the slice indicator.

14. A computer program product (810b) for handling slice selection and session management in a second network function (304, 700) in a receiving side of a communication network, the computer program product (810b) comprising:a non-transitory computer-readable medium having computer-executable instructions stored thereon, the instructions, when executed by processing circuitry (710), causing the processing circuitry to:receive information associated with a slice type indicator (308), wherein the slice type indicator is associated to a selected communication slice for an initiating UE (300) as part of a session initiation;determine whether a receiving UE (306) is entitled to access a communication slice indicated by the slice type indicator (308); andestablish a communication session between the initiating and receiving UE based on the above determination.

15. A method for slice selection and session management in a communication network comprising:at an originating side of the communication network:obtaining a slice type indicator (308) associated with a selected communication slice for an initiating UE (300) as part of a session initiation;transmitting the slice type indicator to a receiving side of the communication network;at the receiving side of the communication network:receiving, at a receiving UE (306), the transmitted slice type indicator (308);determining whether the receiving UE (306) is entitled to access the communication slice indicated by the slice type indicator (308); and establishing a communication session between the initiating and receiving UE based on the above determination.

16. The method of claim 15 wherein the selected communication slice is selected at an originating side of the communication network from a plurality of available slice based on one or more service characteristics.

17. The method of claims 15 to 16 further comprises inferring the one or more service characteristics associated with the received slice type indicator (308) at the receiving side of the communication network.

18. The method of claim 15 wherein determining whether the receiving UE (306) is entitled to access the communication slice further comprises checking associated policies for permitting usage of the communication slice by the receiving UE (306).

19. The method of claim 15 wherein determining whether the receiving UE (306) is entitled to access the communication slice further comprises checking the availability of the slice indicated by the slice indicator.

20. A system for slice selection and session management in a communication network comprising:a first network function (302) at an originating side of the communication network, the first function adapted to :obtain a slice type indicator (308) associated to a selected communication slice for an initiating UE (300) as part of a session initiation;transmit the slice type indicator to a receiving side of the communication network;a second network function (304) at the receiving side of the communication network, the second function adapted to:receive, for a receiving UE (306), the transmitted slice type indicator;determine whether the receiving UE (306) is entitled to access the communication slice indicated by the slice type indicator (308); and establish a communication session between the initiating and receiving UE based on the above determination.