Method and apparatus for adaptive communication session management

Abstract

Described is a network entity (100, 301, 505, 806) in a mobile communication network (300), the network entity configured for modification of one or more adaptive communication session configurations comprising one or more data sessions, the network entity being configured to: receive (1401) a request for modification of an adaptive communication session configuration associated with a user equipment, UE (200, 501, 801), and / or an application implemented by the UE, wherein the request comprises an indication specifying a requirement for a change to a new communication session configuration from a current communication session configuration; and determine (1402), based on an association of dynamic session configuration information, whether the UE and / or the application is / are subject to modification of the adaptive communication session configuration. This may allow the network entity to support communication session management in an efficient and scalable way and in an adaptive and real-time manner.

Description

[0001] METHOD AND APPARATUS FOR ADAPTIVE COMMUNICATION SESSION MANAGEMENT

[0002] FIELD OF THE INVENTION

[0003] Embodiments of the present disclosure relate to mobile communication networks, in particular a core network architecture solution, specifically session management enhancement, to enable adaptive session configuration and modification of a user equipment (UE) for achieving sustainable and flexible network services.

[0004] BACKGROUND

[0005] The capabilities of future mobile communication networks are expected to include sustainability in terms of energy efficiency, low power consumption technologies, reducing greenhouse gas emissions and appropriate use of resources to address climate change and contribute towards the achievement of current and future sustainable development goals. 5G-Advanced (5G-A) systems have already specified the preliminary work on sustainability aspects, such as how the network can expose the consumed energy or power consumption to the third party or other network entities and how the network can perform energy saving.

[0006] Capabilities such as reliability and latency are expected to support higher performance compared to previous mobile communication systems. In general, the higher performance requiring services may require higher resources and energy consumption compared to the lower performance requiring services. Hence, it is important that these capabilities can be achieved, while fulfilling the sustainability targets, without compromising each other.

[0007] In 5G or 5G-A mobile communication systems, the triggering options for protocol data unit (PDU) session (i.e., data session) modification are specified in 3GPP specification TS23. 501 - System architecture for the 5G System (5GS); Stage 2: Release 19; V19.2.0 and in 3GPP specification: TS23. 502 - Procedures for the 5G System (5GS); Stage 2; Release 19, V19.2.0.

[0008] 5G also defined the modification of reliable communication mechanisms by the notification of analytics output, as described in 3GPP specification TS23. 288 - Architecture enhancements for 5G System (5GS) to support network data analytics services; Release 19, vl 9.2.0, and defines a multi-access PDU session (MA-PDU session) to support access traffic steering, switching and splitting (ATSSS) where a single PDU session can have user plane resources simultaneously on two different access networks, such as 3GPP Access (for example, next generation radio access network (NG-RAN)) and Non-3GPP Access (for example, WiF i). The ATSSS feature allows ATSSS rules, for example how the device / UE should utilize the 3GPP or non-3GPP access network for sending uplink traffic or how the user plane function (UPF) in the network determines which access network should be used for which traffic flow in downlink traffic without redundant mechanisms.

[0009] It may be desirable to dynamically or adaptively modify communication sessions in such mobile communication network implementations.

[0010] SUMMARY

[0011] According to a first aspect, there is provided a network entity in a mobile communication network configured for modification of one or more adaptive communication session configurations, wherein the one or more adaptive communication session configurations comprise one or more data sessions, wherein the network entity is configured to: receive a request for modification of an adaptive communication session configuration associated with a user equipment, UE, and / or an applicationimplemented by the UE, wherein the request for modification of the adaptive communication session configuration comprises an indication specifying a requirement for a change to a new communication session configuration from a current communication session configuration; and determine, based on an association of dynamic session configuration information, whether the UE and / or the application is / are subject to modification of the adaptive communication session configuration.

[0012] This may allow the network entity to support communication session management in an efficient and scalable way in terms of resources and in an adaptive and real-time manner in terms of new session configuration requirements.

[0013] The network entity may be part of a subnetwork of the mobile communication network. The subnetwork may be a core network of the mobile communication network. The network entity may be a core network entity. This may allow the network entity to be used for session management enhancement.

[0014] The association of dynamic session configuration information may be stored at the network entity or at a memory accessible by the network entity. The dynamic session configuration information may comprise a dynamic session indication for the UE and / or the application. This may allow the network entity to associate the indication with the UE and / or application.

[0015] The network entity may be configured to, if the UE and / or the application is subject to modification of the adaptive communication session configuration, modify the current communication session configuration to the new communication session configuration, wherein the new communication session configuration comprises one or more different data sessions (compared to the data session(s) of the current communication session configuration) for the UE and / or an application service associated with the application. The network entity may be configured to determine, based on an association of dynamic session configuration information, that the UE and / or the application is / are subject to modification of the adaptive communication session configuration and modify the current communication session configuration to the new communication session configuration.

[0016] The network entity may be configured to receive a dynamic session indication, the dynamic session indication being associated with the UE and / or on the application implemented by one or more UEs. The dynamic session indication may comprise an indication of a requirement at the user equipment and / or the application for adaptive communication session modification. This may allow the network entity to be informed that the UE and / or application require adaptive session configuration and modification.

[0017] The network entity may be configured to determine the dynamic session configuration information by associating the dynamic session indication with the UE and / or the application.

[0018] The network entity may be configured to receive one or more dynamic session indications, the or each dynamic session indication being associated with one or more UEs and / or one or more applications implemented by one or more of the UEs, the or each dynamic session indication comprising a requirement at the respective UE(s) and / or application(s) for adaptive communication session modification. This may allow the network entity to be informed of which UEs and / or applications require adaptive session configuration and modification.

[0019] The network entity may be configured to determine the dynamic session configuration information by associating the one or more dynamic session indications with its respective one or more UEs and / or one or more applications, optionally with the respective current session configuration of the respective user equipment and / or application service(s). This may allow the network entity to determine whether the respective UE or the application is subject to adaptive session configuration and if yes(i.e. if the UE or application is subject to adaptive session configuration), how to modify new session configuration by comparing the current session configuration information.

[0020] The network entity may be configured to receive the one or more dynamic session indications from another network entity in the mobile communication network or from an application network entity in the mobile communication network. The one or more dynamic session indications may be provided to the network entity during a registration procedure and / or a session establishment procedure, or during application-related or user-related policy data provisioning. This may allow the flexible options of dynamic session indication to be provided with other data and / or as part of the procedures occurring between the UE and the mobile communication network.

[0021] The dynamic session indication for the one or more UEs or the application or the application service may be configured or stored as part of user subscription data or application-related policy data and wherein the network entity is configured to support the dynamic session configuration information for adaptive session modification of the one or more UEs and / or the application. This may allow the dynamic session indication to be configured as part of other processes and stored in the network. Hence, the network entity or other network entity can get this information to check whether the respective UE or application is subject to the adaptive session configuration.

[0022] The dynamic session indication may be a binary value, a scalar value or one or more strings. In the example of binary value with 1 bit, the indication of the binary value “1” may represent that the UE or the application is subject to adaptive session configuration or the status of adaptive session modification is “active” while the binary value “0” may represent that the UE or the application is not subject to adaptive session configuration or the status of adaptive session modification is “inactive”. In another example of scalar values with up to N values, e.g., N=6, the values, for example {“eMBB”, “URLLC”, “MIoT”, “V2X”, “HMTC”, “HDLLC”} are defined for the application associated with six network slice types, requiring adaptive session configuration and modification. Another example of string based indication is the value “adaptive session” for the respective UE or application provided in the configuration or request to the network or the network entity. This may conveniently allow the DS indication to be provided to the network in different formats.

[0023] The request for modification of an adaptive communication session configuration may include one or more of the following: one or more dynamic session indications for one or more UEs, one or more UE identifiers, area of service information, one or more application related identifications, the current communication session configuration and new communication session configuration information for one or more UEs, wherein the new communication session information comprises the new communication session configuration and / or requirements of the new communication session configuration of the UE and / or application. The new communication session configuration may include one or more of the E2E path information (i.e., data session information) of the identifications of Network Slice (e.g., S-NSSAI or NSI-ID), the access node information and potentially the expected resources needed for each E2E path, the session management related information, the User Plane related information and the identification of the Data Network (DN). The requirements of the new communication session configuration may include the target performance (e.g., QoS, reliability) of the new session configuration. An example of data session is a protocol data unit, PDU, session defined in 3GPP. This may allow the network entity to identify the UE or application requiring adaptive session configuration and to obtain appropriate information for configuring the UE.

[0024] When the UE is configured to the new communication session configuration from the current communication session configuration, the network entity may be configured to update the dynamic session configuration information to associate the new communication session configuration with the UE. This may allow storage of real-time updated information of the new communication session configuration to be associated with the UE.The network entity may be configured to modify the current communication session configuration of the user equipment according to one or more of the following: (i) addition of one or more new data sessions into the current communication session configuration (ii) removing of one or more of existing data sessions from the current communication session configuration (iii) allocation and / or activation of one or more of pre-configured sessions into the current communication session configuration (iv) de-allocation and / or de-activation of one or more of pre-configured sessions from the current communication session configuration. This may allow the current communication session configuration to be modified to a new communication session configuration that is different to the current communication session configuration with efficient modification.

[0025] The network entity may be configured to trigger enforcement for the modification of the current communication session configuration to the new communication session configuration to a core network entity and / or a radio access network entity of the network. This may allow the trigger of the new session modification to be enforced by the network entity.

[0026] One or more of the current communication session configuration and the new communication session configuration may comprise multiple data sessions. The new communication session configuration may have a different number of data sessions and / or a different configuration of end to end (E2E) path(s) to the current communication session configuration. This may allow the current communication session configuration to be modified to a new communication session configuration that is different to the current communication session configuration that may be more suitable for the requirements of the UE or application.

[0027] The network entity may be configured to receive the request for modification of an adaptive communication session configuration from a core network entity of the mobile communication network, and / or an application function of the mobile communication mobile communication network via a policy entity of the network. This may allow the network entity to fulfil the adaptive session modification for the UE based on the network decision or based on the decision or requirements of the application.

[0028] The network entity may be configured to determine the new communication session configuration. This may allow the network entity to provide the new communication session configuration to the UE, in addition to the handling of the request and trigger for the enforcement of adaptive session modification.

[0029] The network entity may be configured to receive application-related and / or user-related policy information from a policy entity of the network and determine the modification of communication session configurations in dependence on the policy information. This may allow the current communication session to be modified in accordance with the policy information.

[0030] According to another aspect, there is provided a user equipment, UE, configured for communication with a mobile communication network and being configured to implement an adaptive communication session configuration, the user equipment and / or an application implemented by the user equipment being associated with a dynamic session indication, the dynamic session indication specifying a requirement at the user equipment and / or the application for adaptive communication session modification, wherein the user equipment is configured to provide the dynamic session indication to the mobile communication network.

[0031] This may allow the UE to indicate to the mobile communication network that it has a requirement for adaptive communication session modification so that the network can take steps to modify the adaptive communication session configuration.

[0032] The UE may be configured to, in response to an indication from a network entity of the mobile communication network, modify a current communication session configuration to a new communication session configuration comprising one or more differentdata sessions for the UE. This may allow the current communication session configuration to be modified to a new configuration that is more suitable for requirements of the UE, application or network.

[0033] According to another aspect, there is provided a method for implementation at a network entity in a mobile communication network, the network entity configured for modification of one or more adaptive communication session configurations, wherein the one or more adaptive communication session configurations comprise one or more data sessions, the method comprising: receiving a request for modification of an adaptive communication session configuration associated with a user equipment, UE, and / or an application implemented by the UE, wherein the request for modification of the adaptive communication session configuration comprises an indication specifying a requirement for a change to a new communication session configuration from a current communication session configuration; and determining, based on an association of dynamic session configuration information, whether the UE and / or the application is / are subject to modification of the adaptive communication session configuration.

[0034] This method may allow a network entity to support session management in an efficient and scalable way in terms of resources and in an adaptive and real-time manner in terms of new session configuration requirements.

[0035] If the UE and / or the application is / are subject to the modification of the adaptive communication session configuration, the method may comprise modifying a current communication session configuration to a new communication session configuration comprising one or more different data sessions for the UE and / or an application service associated with the application. This may allow the current communication session configuration to be modified to a new configuration that is more suitable for adaptively and real-time actions requirements of the UE, application or network.

[0036] According to a further aspect, there is provided a method for implementation at a UE, the UE being configured for communication with a mobile communication network and being configured to implement an adaptive communication session configuration, the UE and / or an application implemented by the UE being associated with a respective dynamic session indication, the dynamic session indication specifying a requirement at the UE and / or application for adaptive communication session modification, the method comprising providing the dynamic session indication to the mobile communication network. This method may allow the UE to indicate to the network that it has a requirement for adaptive communication session modification so that the network can take steps to modify the adaptive communication session configuration.

[0037] The method may comprise, in response to an indication from a network entity of the mobile communication network, modifying a current communication session configuration to a new communication session configuration comprising one or more different data sessions for the UE and / or an application service associated with the application. This may allow the current communication session configuration to be modified to a new configuration that is more suitable for requirements of the UE, application or network.

[0038] One or more of the following additional features are also possible in the above implementations.

[0039] The one or more data sessions may comprise one or more protocol data unit (PDU) sessions.

[0040] The association of the dynamic session configuration information for a respective dynamic session indication and the one or more of the UEs and / or the application may be in the form of a mapping table. This may allow the information to be conveniently associated with the one or more UEs.When the UE is configured to the new communication session configuration from the current communication session configuration, the network entity may be configured to update the mapping table to associate the new communication session configuration with the UE. This may allow the dynamic session configuration information to be updated.

[0041] The dynamic session indication may be provided to the mobile communication network during a registration procedure. The network entity may be configured to activate an adaptive session configuration of the UE and map adaptive session information with a UE identifier corresponding to the UE. This may allow the adaptive session information for particular user equipment to be retrieved.

[0042] The dynamic session indication may be provided to the mobile communication network during a session establishment procedure and the network entity may be configured to activate an adaptive session configuration of the UE and map adaptive session information with one or more data session identifiers. This may allow the activation of the adaptive session modification for the UE when the trigger request for the adaptive communication session modification for the UE is received.

[0043] The dynamic session indication may be provided to the mobile communication network in application-related data, for example by the application function via the policy entity or function. The network entity may be configured to activate an adaptive session configuration of the UE for the respective application and policy and map adaptive session information with an application identifier. This may allow the application requirement for the adaptive session activation to one or more UEs implementing the respective applications.

[0044] The network entity may be configured to associate the dynamic session indication with the one or more UEs and / or the application in the mapping table and determine whether the UE and / or the application has an associated dynamic session indication in dependence on the mapping table and / or an additional mapping of pre-configured sessions. This may be a convenient implementation for storing this information.

[0045] The triggering condition for adaptive session modification may occur (that is, the request for adaptive session modification may be sent) when the current session configuration of the UE or an application associated with the UE or the network does not fulfil one or more performance requirements, operating conditions or network conditions to perform a communication or computing service. This may allow the adaptive session modification to be triggered as determined by such conditions.

[0046] The network entity may be in the mobile communication network. The mobile communication network may be a 3GPP network. The network entity may be a Session Management Function or Policy Management Function or Network Data Analytics Function of the mobile communication network.

[0047] The network entity may be configured to support the feature of changing a UE’ s current session configuration to a new session configuration, where the changing to a new session configuration happens during the operation of the UE’s current session configuration.

[0048] According to a further aspect, there is provided a mobile communication network comprising a network entity having any of the features described herein, the mobile communication network being configured to communicate with a UE having any of the features described herein.

[0049] According to a further aspect, there is provided one or more computer programs for instructing a computer comprising one or more processors to implement the methods above.According to a further aspect, there is provided a data carrier storing in non-transitory form the one or more computer programs above.

[0050] BRIEF DESCRIPTION OF THE FIGURES

[0051] Embodiments of the invention will be described with reference to the accompanying drawings:

[0052] Figure 1 schematically illustrates an example of a network entity and some of its associated components;

[0053] Figure 2 schematically illustrates an example of a UE and some of its associated components;

[0054] Figure 3 schematically illustrates an example of an adaptive session configuration procedure;

[0055] Figure 4 schematically illustrates an example of an adaptive session modification procedure;

[0056] Figure 5 illustrates subscription data-based dynamic session (DS) indication provisioning during a registration procedure; Figure 6 illustrates subscription data-based DS indication provisioning during a session establishment procedure;

[0057] Figure 7 illustrates application data-based DS indication configuration and provisioning;

[0058] Figure 8 illustrates an exemplary procedure for adaptive session modification trigger with the complete information of new session configuration;

[0059] Figure 9 illustrates an exemplary procedure of adaptive session modification trigger with the requirements of new session configuration;

[0060] Figure 10 illustrates an exemplary procedure of the enforcement of the adaptive session modification of the UE with respect to Option A described herein;

[0061] Figure 11 illustrates an exemplary procedure of the enforcement of the adaptive session modification of the UE with respect to Option B described herein;

[0062] Figure 12 illustrates provisioning of the DS indication for adaptive session configuration and modification in mobile communication network;

[0063] Figure 13 illustrates adaptive session management (ASM) triggers for a UE or application associated to UEs in a mobile communication network;

[0064] Figure 14 shows the steps of an exemplary method for implementation at a network entity;

[0065] Figure 15 shows the steps of an exemplary method for implementation at a UE.

[0066] DETAILED DESCRIPTION

[0067] A mobile communication network comprises an Access Network (AN), which may be a Radio Access Network (RAN) and a Core Network (CN). The (R)AN handles the wireless aspects, while the CN handles the control signalling. The traffic from a UE is transmitted over the User Plane (UP) through RAN and CN entities UPF.

[0068] Embodiments of the invention may be applied in any mobile communication system, such as, but not limited to, 3GPP The described approaches may also be implemented in different communication networks that are currently available or developed in the future. The network may comprise a plurality of network entities (NEs). The NEs may be network function (NFs), which may be software-based. The NEs may alternatively be network apparatus (hardware-based).

[0069] A radio node is any node which may reside in the RAN of a mobile network which is capable of transmitting and / or receiving radio signals.

[0070] Figures 1 and 2 show examples of a network entity 100 of a mobile communication network and a UE 200 respectively. The network entity 100 may be the adaptive session management (ASM) entity described herein. Entities 101, 201 are computingentities. Entities 102, 202 are command and control entities. These entities are logical entities. In practice they may each be provided by one or more physical devices such as servers and data stores, and the functions of two or more of the entities may be provided by a single physical device. In some implementations, the network entity 100 may be cloud-based. Each physical device implementing an entity may comprise a processor and / or a memory. The network entity and / or the UE may also comprise a transceiver for transmitting and receiving data. The memory stores in a non-transient way code that is executable by the processor to implement the respective entity in the manner described herein. Therefore, the methods may be deployed in multiple ways, for example in the cloud or alternatively in dedicated hardware.

[0071] A UE may be a handheld device, in-vehicle device, wearable device, computing device, or other processing device connected to a wireless modem that have a wireless communication function. The UE may also be a mobile station (MS), a subscriber unit, a cellular phone, a smart phone, a wireless data card, or a personal digital assistant (PDA) computer, a tablet computer, a wireless modem (modem), a handheld device (handset), a laptop computer, a machine type communication (MIC) terminal, a label, and the like.

[0072] In next generation telecommunication systems, a UE or application implemented by or associated with a UE may require new features of dynamic or adaptiveness of multi-session modification in real-time and in an efficient manner. For example, an industrial human-robot interaction or collaboration scenario with Hyper Reliable and Low Latency Communication (HRLLC), a robot UE may require dynamic data sessions modification of a robot when the reliability of the communication service changes over time due to task adaptation or operational condition at the factory. In another example, using Integrated Sensing and Communication (ISAC), an internet of things (loT) device may require adaptive data sessions to modify the various bandwidth requirements for sensing data transmission or computing in the user plane (UP) or future data plane (DP) of the mobile communication network in real-time with efficient resource and energy consumption. An example of the data session of the UE is a PDU session to provide UE application related data transmission such as HRLLC or ISAC. Another example of the data session of the UE is to provide sensing data transmission for the data management by the network. In this example, the sensing data of the data session may or may not be related to the UE’s application.

[0073] Embodiments of the invention are related to the CN architecture solution in a mobile communication network, specifically session management enhancement, to enable adaptive session modification of a UE for achieving efficient resource utilization, flexible session management and real-time session modification. This may allow for both sustainable and flexible network services.

[0074] Herein, dynamic or adaptive sessions modification of a UE’s current session configuration (that is, the session currently being implemented by the UE) in the UP or future DP of the mobile communication network is described which may comprise multiple data sessions according to the real-time performance requirements of the network or application. The current session configuration of a UE can be modified by adapting UP resources in real-time with respect to the performance targets such as reliability, latency and / or bandwidth of the services. The described adaptive session management features can allow for multisession configuration of one or more UEs and are able to adapt to a new multi-session configuration during an operational phase according to the requirements of the services or performance. The dynamic session configuration can enable the realtime requirements of the change of UE’s current session configuration to a new session configuration based on the performance targets of the services.

[0075] As will be described in the following, a dynamic session (DS) indication for the UE or application implemented by or associated with one or more UEs is used, including how to configure the DS indication with the network and how to provision the DS indication to the corresponding network entities. In addition, the associated dynamic session modification procedures such as triggers and enforcements are described.Some further features of the adaptive session management, control and enforcement approach described herein include the following:

[0076] Adaptive session configuration is used to identify how a session can be configured with a session adaptive feature, how this feature can be provisioned and used in session modification and which network entities can be configured with this feature. The key functionalities of this feature include identifying adaptive session configuration with DS indication, configuration of the DS indication and provisioning of the DS indication.

[0077] An overview of the adaptive session configuration procedure is schematically illustrated in Figure 3. In this implementation, in a mobile communication network 300, an ASM entity 301 receives a configuration of the DS indication for a UE or application (App) from one or more application functions (AFs) or NFs, collectively shown at 302. The ASM entity 301 associates the UE or application with the DS indication and, optionally, the current session configuration. This association of dynamic session configuration information is used to determine whether and how to provide support if the UE or the application requests the flexible session modification from changing the UE’s current session configuration to a new session configuration. This information may be stored in the form of a mapping table.

[0078] Adaptive session modification specifies procedures of how adaptive session modification can be triggered and how the enforcement can be performed by the network. The key mechanisms of this feature include procedures of adaptive session modification trigger and procedures of adaptive session modification enforcement. The adaptive session modification procedure is schematically illustrated in Figure 4. In this implementation, the ASM entity 301 receives a request for adaptive session modification from the AF / NF s 302. The request may include the DS indication and other information (for example, as described in 855 of Figure 8, described later). The ASM entity 301 determines whether the UE or application is subject to adaptive session modification. This may be performed by determining whether the UE or application has an associated DS indication. This may be determined based on the association of dynamic session configuration information stored in the mapping table, which may be determined in part 2 of the adaptive session configuration. If the ASM entity determines that the UE or application is subject to adaptive session modification, the ASM entity 301 can perform an ASM enforcement procedure (for example, as described in Figure 10 later). The ASM enforcement may in some implementations be determined in dependence on a policy provided by a policy entity 303 of the network. The ASM entity 301 determined the new session configuration. The new session configuration may be determined in dependence on the policy received from the policy entity 303. The ASM enforcement is then triggered with a CN NF or RAN entity 304 of the mobile communication network 300, where one or more data sessions may be established, released, activated or de-activated accordingly with the determined new session configuration. The association of the UE or application and the new session configuration can then be updated, for example by updating the association information in the mapping table stored by the ASM entity 301.

[0079] Adaptive session enforcement mechanisms describe potential enabling mechanisms for the enforcement of adaptive session modifications, in particular, how to achieve new session configuration(s) of the UE in real-time and faster mechanisms.

[0080] The above features will now be described in more detail.

[0081] Adaptive communication session configuration

[0082] The adaptive communication session configuration (which is generally referred to herein as an adaptive session configuration for brevity) is defined to enable the functionality of changing a UE’s current communication session configuration to a new communication session configuration (which are generally referred to herein as a current session configuration and new sessionconfiguration respectively for brevity), for example based on the dynamic service requirements or varying performance of the communication. The changing of a UE’s current session configuration to a new session configuration can happen during the operation of the UE’s current session configuration. The UE’s current session configuration or the UE’s new session configuration includes one or more data sessions, for example PDU sessions, where the data sessions from the UE’s current session configuration are not exactly the same as the data sessions from the UE’s new session configuration, for example in terms of the number of PDU sessions and / or the configurations of PDU sessions (such as E2E UP paths). Note that a subset of E2E UP paths configuration from the UE’s current session configuration may still be a part of the UE’s new session configuration.

[0083] The UE may be associated with an application and / or an application service. For example, the UE may implement an application for vehicle to everything (V2X). For example, where the UE is an in-vehicle device, the application may be V2X where application services are remote driving, autonomous driving, etc. The DS indication can be associated with an application V2X (i.e., all V2X application services) or a particular application service (such as remote driving). An application may be associated with one or more UEs.

[0084] (i) DS indication

[0085] To configure the adaptive communication session for a UE, the network can check which UEs or applications require this adaptive session feature. A DS indication can be used to indicate the support of adaptive session configuration and modification for one or more data sessions in UP paths (for example, PDU sessions) requirements of one or more UEs or applications associated with one or more UEs. The same feature is used for the DS indication for the adaptive session configuration and modification for one or more data sessions in DP. The DS indication is a conditional feature of the session management, such that it is used if the UEs or applications require adaptive session configuration. In addition, the DS indication is used to indicate whether a UE requires (i.e. is subject to) the adaptive session configuration and modification or not.

[0086] The DS indication may be a binary value or scalar (or weighted) value. An example of DS indication includes a flag which indicates that the (potential) requirement of adaptive sessions functionality for a UE (or group of UEs) or an application or a service (for example, Al computing service). In another example of binary value with 1 bit, the indication of the binary value “1” may indicate that the UE or the application is subject to adaptive session configuration or the status of adaptive session modification is “active”, while the binary value “0” may indicate that the UE or the application is not subject to adaptive session configuration or the status of adaptive session modification is “inactive”. Examples of scalar DS indications include multiple flags or values indicating the requirements of adaptive sessions functionality for one or more services such as communication services and Al computing services. In another example of scalar values with up to N values, e.g., N=6, the values, for example {“eMBB”, “URLLC”, “MIoT”, “V2X”, “HMTC”, “HDLLC”} are defined for the application associated with six network slice types, requiring adaptive session configuration and modification. The DS indication may comprise one or more information strings. For example the string value “adaptive session” associated with the respective UE or application can be provided for the adaptive session configuration or in the request of adaptive communication session modification.

[0087] (ii) Configuration of the DS indication

[0088] The DS indication can be configured as a part of the subscription data and / or a part of the application related data and / or a part of the policy related data. If the DS indication is a part of the subscription data, it is indicated that the UE is subject to adaptive session configuration and the network shall support the adaptive session modification of the UE (i.e., changing one session configuration to new session configuration during an operation phase). If the DS indication is a part of the application related data, it is indicated that the application is subject to the requirements of adaptive session configuration, hence, the networkshall support the adaptive session modification to the UEs requested to the application. If the DS indication is a part of the policy related data, it can be indicated that the network shall support the session management (SM) policy dedicated to the adaptive session modification for the corresponding UE(s) or application. The DS indication can be configured as a new Information name for the above-mentioned options. Table 1 shows an example of the data set (and subset) (i.e., subscription data (Sub.n data), Application data (App.n data) and Policy data, data key (and sub key) with corresponding information name to configure the DS indication.

[0089] Table 1: Exemplary configuration options of the DS indication.

[0090] "

[0091]

[0092]

[0093] (iii) Provisioning of the DS indication

[0094] If one or more UEs require or is / are subject to adaptive session configuration, the network can retrieve, store and provision the DS indication during the initial registration or data session (for example PDU session) establishment of the UE.

[0095] In the subscription data-based option for providing the DS indication, two exemplary procedures will now be described.

[0096] The first procedure of DS indication retrieval and configuration by the network during the registration procedure of the UE is presented in Figure 5, which shows a communication flow for subscription data-based DS indication provisioning during aregistration procedure. In this example, a UE 501 communicates with a mobile communication network comprising a registration management entity 502, one or more CN entities 503, a subscription data repository 504 and an ASM entity 505.

[0097] In step 1, as indicated at 551, the network (specifically the registration management entity 502 and the CN entities 503) receives a registration request from the UE 501 with the input parameters. In this example, the input parameters are the UE identification (UE ID) and the identification of the network slice (S-NSSAI).

[0098] In step 2, as indicated at 552, the core network entities 503 check and retrieve whether the UE 501 is subject to the adaptive session configuration during the authentication of the UE with the subscription data repository 504.

[0099] In step 3, as indicated at 553, if the UE 501 is associated with a DS indication, a core network entity 503 activates the dynamic session configuration of the UE together with the ASM entity 505 handling of adaptive session management.

[0100] In step 4, as indicated at 554, the AMS entity 505 activates the adaptive session configuration for the UE 501 and maps this with the UE identification.

[0101] The second procedure of DS indication retrieval and configuration by the network during session establishment of the UE is presented in Figure 6, which shows a communication flow for subscription data-based DS indication provisioning during a session establishment procedure. In this example, the mobile communication network further comprises a session management entity or function (SMF) 506. In this example, step 2 and step 5 are optional.

[0102] In step 1, as indicated at 601, the network (specifically, the CN entities 503 and session management entity 506) receives a session establishment request with the input parameters. In this example, the input parameters comprise the UE ID, the S-NSSAI and optionally the identification of the application (App-ID).

[0103] Step 2, as indicated at 602, is an optional step if the CN entity 503 has already retrieved the DS indication during the registration of the UE 101. Otherwise, the step 2 from Figure 5 can be applied.

[0104] In step 3, as indicated at 603, the CN entity 503 and the session management entity 506 check or update the adaptive session configuration activation of the UE 501 or application.

[0105] In step 4a, as indicated at 604a, when the PDU session identification is available, the session management entity 506 provides this to the ASM entity 505 to map the adaptive session configuration of the UE 501 with the current session configuration. The message further includes the identification of the UE, application and the DS indication.

[0106] In step 4b, as indicated at 604b, the ASM entity 505 adds or updates the adaptive session configuration of the UE and maps this with the UE identification with the received PDU session identification(s).

[0107] In step 5a, as indicated at 605a, optionally, the adaptive session related policy (i.e. , DS policy) is provisioned to the ASM entity 505 by the core network entity 503. In step 5b, as indicated at 605b, if step 5a is executed, the received DS policy of the UE 501 or application is stored at the ASM entity 505.

[0108] In the application related data-based option, the procedure of DS indication configuration can be performed by an application function (AF) 507 and the retrieval and storage by the network is presented in Figure 7, which shows a communication flow for application related data-based DS indication configuration and provisioning.At step 1, as indicated at 701, the CN entity 503 receives the adaptive session configuration request with the input parameters. In this example, the input parameters comprise the App-ID, the DS indication for the application and optionally the UE IDs.

[0109] At step 2, as indicated at 702, the CN entity 503 configures and stores the received information of adaptive session configuration from the AF 507.

[0110] At step 3, as indicated at 703, the CN entity 503 activates the dynamic session configuration with the ASM entity 505 for the application with the identification of the application and DS indication and optionally the associated UE identifications.

[0111] At step 4, as indicated at 704, the ASM entity 505 activates the adaptive session configuration for the application and maps this with the associated UE identifications if provided by the CN entity.

[0112] Adaptive communication session modification

[0113] The following section covers the procedures of adaptive session modification triggering to the ASM entity with different options for the triggering condition. The adaptive session modification can be triggered when, for example, the current session configuration of the UE or application associated to the UE does not fulfil the performance requirements such as latency or bandwidth or reliability or accuracy of the data communication or computing services or communication services. The terms data communication, computing services and communication services are interchangeable. The adaptive session modification may be triggered by one or more network entities.

[0114] Two procedures of adaptive session modifications are described below, namely, (i) adaptive session modification trigger and (ii) adaptive session enforcement.

[0115] (i) Procedures of adaptive communication session modification trigger

[0116] The adaptive session modification triggering may include, but is not limited to, the following conditions:

[0117] 1. A change of Operational Conditions (OC), for example at a factory floor which affect the communication service requirements or the performance of the communication service.

[0118] 2. A change of network conditions, which affect the performance of the communication service.

[0119] 3. An application’s requirements which affect the communication service requirements or the performance of the communication service.

[0120] It is assumed that the triggering request to the ASM entity may include one or more of the DS indication, UE-ID, App-ID, the current session configuration of the UE, the new session configuration and / or the related information of the new session configuration and area information.

[0121] After receiving the triggering request, the ASM entity checks the DS indication of the associated UE from the received request. If a DS indication is not included in the request, the DS indication is checked by retrieving and / or provisioning from / to the corresponding network entities or is retrieved from the mapping stored at the ASM entity using the data key SUPI (i.e., the identification of the UE) or application ID. The request may include the current session configuration of the UE and the related information for the new session configuration of the UE. Optionally, the area information of the UE is provided to support the determination of new session configuration.Two exemplary options are considered below for the related information of the new session configuration.

[0122] Option A: the related information of the new session configuration of the UE is the details information of the new session configuration involving the information of the data sessions (i.e., E2E UP paths) for the UE. The E2E UP path or the E2E path information includes the identifications of Network Slice (e.g., S-NSSAI or NSI-ID), the access node information and potentially the expected resources needed for each E2E path, the session management related information, the User Plane related information and the identification of the Data Network.

[0123] Option B: the related information of the new session configuration of the UE is the requirements of the services, hence, the ASM entity determines the information of the E2E UP paths based on the requirements of the service received. The requirements of the new communication session configuration may include the target performance (e.g., QoS, reliability) of the new session configuration.

[0124] The procedure of the adaptive session modification trigger is presented in Figure 8, which shows a communication flow for an exemplary procedure of adaptive session modification trigger with the complete information of the new session configuration. In this example, a UE 801 communicates with a mobile communication network comprising a radio access network (RAN) 802, one or more control plane (CP) network functions (NFs) 803, a CP NF 804, one or more user plane (UP) NFs 805, an ASM entity 806, a policy entity 807 and a subscription data repository 808. The ASM entity 806 may receive the trigger request for the adaptive session modification from a CN entity directly (Option A.1 ) or via the policy entity 807 (Option A.2).

[0125] In these examples, as shown at 851, to perform the adaptive session modification, it is assumed that the UE has already established sessions, has already activated with adaptive session configuration and mapped the UE and the PDU sessions (i.e., data sessions) with the DS indication.

[0126] For Option A (for both Options A.1 and A.2), as shown at 852, it is assumed that the network has already determined a new session configuration of the UE before the trigger of the adaptive session configuration request to the ASM entity.

[0127] For Option A.1 , as shown at 853:

[0128] In a step 1.1 , as indicated at 854, before the ASM trigger request arrives, it is assumed that ASM policy is provisioned to the AMS entity 806 by the policy entity 807.

[0129] In a step 1.2, as indicated at 855, a CP NF 804 of the core network (i.e. a core network entity) triggers a request for adaptive session modification to the ASM entity 806. The request includes the DS indication, UE-ID, the new session configuration information and optionally the identification of an application and the current session configuration of the UE.

[0130] For option A.2, as shown at 856:

[0131] In a step 2.1, as indicated at 857, a CP NF 804 of the core network (i.e. a core network entity) triggers a request for an ASM policy to the policy entity 807. The request includes the DS indication, UE-ID, the new session configuration information and optionally the identification of an application and the current session configuration of the UE.

[0132] In a step 2.2, as indicated at 858, the policy entity 807 determines and updates ASM policy for the requested UE and / or the application.

[0133] In a step 2.3, as indicated at 859, based on the policy decision, the ASM trigger request is sent to the ASM entity 806 for the enforcement of the adaptive communication session. The request includes the ASM policy and the information received from step 2.2.For Option B, it is assumed that the network is aware of the requirements for the new session configuration. For example, the network may provide the required reliability level of the UE, the required bandwidth requirement of the UE, and / or the required latency of the service for the UE. The network may not be aware of the complete information of a new session configuration of the UE such as the E2E UP paths achieving the requirements for the new session configuration.

[0134] An exemplary procedure of the adaptive session modification trigger is presented in Figure 9, which shows a communication flow for a procedure of adaptive session modification trigger with the requirements of new session configuration. In this example, the network further comprises an AF 808.

[0135] The ASM entity 806 may receive the trigger request for the adaptive session modification either from a CN entity directly or via the policy entity 807 (Option B.1) or from the AF (Option B.2).

[0136] As shown at 901, the network first performs in session establishment procedure and DS configuration, as described above. The ASM entity 806 maps AS information with the PDU session at 902.

[0137] For Option B.l, as shown generally at 903, it is assumed that the network triggers ASM for each particular UE with the new session configuration requirements. One example of new session configuration requirements comprises the new target reliability level of the UE.

[0138] In a step 1.1 , as indicated at 904, a CP NF 804 of the core network (i.e. a core network entity) triggers a request for the adaptive session modification of the UE 801 to the ASM entity 806 directly (or via the policy entity 807). The request includes the DS indication, UE-ID, the new session configuration requirements and optionally the identification of the application and the current session configuration of the UE.

[0139] Step 1.2, as indicated at 905, is an optional step, for example if the policy decision for the UE is already provided or updated at the ASM entity 806. Otherwise, the ASM entity 806 can interact with the policy entity 807 to provide ASM policy to the ASM entity 806 for the requested UE.

[0140] For Option B.2, shown generally at 906, it is assumed that the network triggers ASM for a group of UEs using a particular application with the new session configuration requirements with respect to the application requirement. Examples of new session configuration requirements are the new reliability requirements of the application, the new bandwidth requirements of the application and / or the new latency requirements of the application.

[0141] In a step 2.1, as indicated at 907, the AF 809 triggers a request for the adaptive session modification of an application to the policy entity 807. The request includes the DS indication, the identification of the application, the new session configuration requirements and optionally the identifications of the UEs.

[0142] In a step 2.2, as indicated at 908, the policy entity 807 determines and updates an ASM policy for the requested application.

[0143] In a step 2.3, as indicated at 909, based on the policy decision, the policy entity 807 sends ASM trigger request to the ASM entity 806 for the modification of the adaptive session of the UEs currently running on the requested application. The request includes the ASM policy and the information received from step 2.2.

[0144] (ii) Procedures of adaptive communication session modification enforcementUpon receiving an adaptive session modification triggering request, the ASM entity can perform the modification of the UE’s current session configuration to the new session configuration.

[0145] The enforcement of the new session configuration of the UE may require one or more of the following steps by the ASM entity:

[0146] Check that the complete information of the new session configuration is provided. If the new session configuration requirement is provided, the requirements are checked against the current session configuration and a new session configuration is determined. The determination of a new session configuration may be based on one or more preconfigured session(s) (i.e., each pre-configured session comprises one or more E2E UP paths) according to the requirements of the new session configuration and the provided performance of the pre-configured session(s). The pre-configured session comprises one or more data session (e.g., PDU sessions) achieving a particular performance target (e.g., reliability target, latency target, etc) which are already established and are ready to activate or deactivate for the respective UE. The list of pre-configured sessions and the status (e.g., available or unavailable) and the association information to the UE may be kept in the pre-configured sessions information mapping table.

[0147] Compare the difference between the current session configuration and the new session configuration to determine whether new data session(s) shall be paired and / or the existing data session(s) shall be released.

[0148] Enforce the new session configuration by pairing of new established data session(s) and / or by removing of the existing data session(s) of the UE and / or updating of the pre-configured PDU session(s) with the UE.

[0149] An exemplary procedure of the enforcement of the adaptive session modification of the UE according to Option A is presented in Figure 10, which shows a communication flow for an exemplary procedure of the enforcement of the adaptive session modification of the UE with respect to Option A.

[0150] In this example, the network comprises a RAN #1 802a, RAN #2 802b, an access and mobility management function (AMF) #1 810a, an AMF #2 810b, a UP entity 1 805a and a UP entity 2 805b.

[0151] As indicated at 1001, Figure 10 shows the enforcement of adaptive session modification according to the ASM trigger options A.l and A.2 from Figure 8. In this option, the trigger request includes the complete information of the new session configuration, hence the ASM entity is aware of new E2E UP paths information to perform the enforcement of the new session configuration.

[0152] In a step 1, as indicated at 1002, when the request for the ASM trigger is received, the ASM entity 806 checks the provided new session configuration information. Optionally, the ASM entity 806 checks with the policy entity 807 for the ASM policy decision or updates.

[0153] In a step 2, as indicated at 1003, based on the received new session configuration, the ASM entity 806 determines whether new PDU session(s) (i.e., data session(s)) need to be established and / or the existing PDU session(s) need to be released.

[0154] As indicated generally at 1004, for each new PDU session(s) establishment, the steps 3-7 can be executed by the network during the adaptive session modification of the UE.

[0155] 3. The ASM entity 806 determines the UP path establishment based on the received E2E UP paths information in the trigger request. The ASM entity 806 sends a UP establishment request (e.g., N4 Session request defined in 5G) to the corresponding UP entity (e.g., UP Entity #2) with the DS indication for the UE.

[0156] 4. To establish the E2E UP path of the UE, the ASM entity 806 sends the E2E UP path information to the corresponding CN entity (e.g., AMF defined in 5G) to interact with the corresponding access node. The request from the ASM entity 806 to theAMF (e.g., AMF #2) includes the information of Access node (e.g., RAN identification, Area information, RAN resource information), the UP entity (e.g., the identification of UP entity).

[0157] 5. Upon receiving the E2E path establishment from the ASM entity 806, the AMF #2 810b forwards it to the corresponding RAN node (e.g., RAN #2 802b) to establish the radio link of the E2E UP path towards the UE (e.g., N2 PDU session establishment defined in 5G). The information received from the ASM entity (including radio resources information) is forwarded to the RAN node to establish the radio link. The RAN node (e.g., RAN #2802b) provides the response to the AMF entity (e.g., AMF#2810b) for the radio link establishment of the E2E UP path (i.e., from UE to the provided UP entity via the RAN node (e.g., RAN #2802b).

[0158] 6. Based on the response from the RAN node (e.g., RAN #2802b), the AMF (e.g., AMF #2810b) provides the response to the ASM entity 806. The response message may indicate whether the request for the establishment of E2E UP path is successful or failed.

[0159] 7. If the response to the request for the establishment of E2E UP path is successful, the ASM entity 806 can update the adaptive session configuration of the UE. This may include the pairing of the new PDU session configuration with the current session configuration of the UE 801. After successful establishment of E2E UP path, the DL / UL data can be transmitted over the UP path.

[0160] As shown generally at 1005, for each existing PDU session(s) release, the steps 8-12 can be executed by the network during the adaptive session modification of the UE.

[0161] 8. The ASM entity 806 determines a UP path release of the current PDU session based on the received E2E UP paths information in the trigger request. The ASM entity 806 sends UP release request (e.g., N4 Session termination request defined in 5G) to the corresponding UP entity (e.g., UP Entity #1) with the DS indication for the UE 801.

[0162] 9. To release the E2E UP path of the UE, the ASM entity 806 sends the E2E UP path information to the corresponding core network entity (e.g., AMF defined in 5G) to interact with the corresponding access node. The request from the ASM entity to the AMF (e.g., AMF #1810a) includes the information of access node (e.g., RAN identification, Area information, PDU session identification) and optionally the UP entity information (e.g., the identification of UP entity #1 805a).

[0163] 10. Upon receiving the E2E path establishment from the ASM entity 806, the AMF #1 810a forwards it to the corresponding RAN node (e.g., RAN #1 802a) to release the radio link resources of the E2E UP path towards the UE (e.g., N2 PDU session release defined in 5G). The information received from the ASM entity is forwarded to the RAN node to release the radio link. The RAN node (e.g., RAN #2802b) provides the response to the AMF entity (e.g., AMF#1 810a) for the radio link release of the E2E UP path (i.e., from UE to the provided UP entity via the RAN node (e.g., RAN #1 802a).

[0164] 11. Based on the response from the RAN node (e.g., RAN #1 802a), the AMF (e.g., AMF #1 810a) provides the response to the ASM entity 806. The response message can indicate whether the request for the release of E2E UP path is successful or failed.

[0165] 12. If the response to the request for the release of E2E UP path is successful, the ASM entity 806 can update the adaptive session configuration of the UE 801. It includes the removing of the existing PDU session from the current session configuration of the UE.

[0166] An exemplary procedure of the enforcement of the adaptive session modification of the UE according to Option B is presented in Figure 11, which shows a communication flow for an exemplary procedure of the enforcement of the adaptive session modification of the UE with respect to Option B. In this example, the network comprises a CP entity # 1 803a and a CP entity #2803b.

[0167] As indicated at 1101 , F igure 11 shows the enforcement of adaptive session modification according to the ASM trigger options B.l andB.2 described above with reference to Figure 9. In this option, the trigger request includes the requirements information of the new session configuration, hence the ASM entity 806 is not aware of new E2E UP paths information of the UE. In thisoption, the ASM entity 806 determines the UP path selection from the pre-configured sessions to perform the enforcement of the new session configuration. It is assumed that the pre-configured PDU sessions are already established and can be associated or de-associated to the E in real-time.

[0168] Step 1, as indicated at 1102, is the same as Step 1 described above with reference to Figure 10.

[0169] In a step 2, as indicated at 1102, based on the received new session configuration requirements, the ASM entity 806 determines the new session configuration using the available pre-configured sessions. After determination of new session configuration, the ASM entity determines whether the pre-configured session(s) need to be activated and associated for the UE and / or the existing PDU session(s) need to be released and / or the existing pre-configured session(s) need to be de-activated for the UE.

[0170] As shown generally at 1105, for each new pre-configured session(s) association to the UE, the steps 3-7 are executed by the network during the adaptive session modification of the UE.

[0171] 3. The ASM entity 806 determines the pre-configured UP path activation and association to the UE 801 based on the determined E2E UP paths information from Step 2. The ASM entity 806 sends a UP activation request (e.g., N4 Session modification request defined in 5G) to the corresponding UP entity (e.g., UP Entity #2 805a) with the DS indication of the UE 401.

[0172] 4. To activate the E2E UP path of the UE, the ASM entity sends the E2E UP path information (e.g., PDU session ID) and the identification of the UE to the corresponding core network entity (e.g., AMF defined in 5G) to interact with the corresponding Access node.

[0173] 5. Upon receiving the pre-configured UP path activation and association to the UE from the ASM entity, the CP entity AMF #2 forwards it to the corresponding RAN node (e.g., RAN #2) to activate the pre-configured UP path towards the UE (e.g., N2 PDU Session modification defined in 5G). After activation and association to the UE, the RAN node (e.g., RAN #2) provides the response to the AMF entity (e.g., AMF#2) for the activation of the pre-defined E2E UP path (i.e., from UE to the provided UP entity via the RAN node (e.g., RAN #2).

[0174] 6. Based on the response from the RAN node (e.g., RAN #2), the AMF (e.g., AMF #2) provides the response to the ASM entity. The response message indicates the request for the activation of pre-defined E2E UP path is successful or failed.

[0175] 7. If the response to the request for the activation and modification of pre-configured E2E UP Path is successful, the ASM entity 806 updates the adaptive session configuration of the UE to the new session configuration. It may also cause the pairing of new PDU session with the current session configuration of the UE and the updates of pre-configured session mapping to the UE 801. After successful activation and association of E2E UP path, the DL / UL data can be transmitted over the UP path.

[0176] As shown generally at 1105, for each existing PDU session(s) release, the steps 8-12 from Figure 10 are the same and applied by the network during the adaptive session modification of the UE. For each existing data session in the pre-configured session(s) deactivation, the following steps are executed by the network during the adaptive session modification of the UE.

[0177] 8. The ASM entity 806 determines a pre-configured UP path modification (i.e., to deactivate the existing pre-configured PDU session for the UE) based on the E2E UP paths information from step 2. The ASM entity 406 sends a UP modification request (e.g., N4 session modification request defined in 5G) to the corresponding UP entity (e.g., UP Entity #1) with the DS indication of the UE.

[0178] 9. To deactivate the existing pre-configured E2E UP path of the UE, the ASM entity 406 sends the E2E UP Path information (e.g., pre-defined PDU session identification) to the corresponding CN entity (e.g., AMF defined in 5G) to interact with the corresponding access node.

[0179] 10. Upon receiving the pre-configured E2E path deactivation from the ASM entity 806, the CP entity AMF #1 forwards it to the corresponding RAN node (e.g., RAN #1) to deactivate the radio link resources of the E2E UP path towards the UE (e.g., N2 PDU session modification defined in 5G). Basically, the information received from the ASM entity is forwarded to theRAN node to deactivate the radio part of the pre-configured PDU session for the UE. The RAN node (e.g., RAN #2) provides the response to the AMF entity (e.g., AMF# 1) whether the modification of the existing pre-defined PDU session is successful or not.

[0180] 11. Based on the response from the RAN node (e.g., RAN #1), the AMF (e.g., AMF #1) provides the response to the ASM entity 806. The response message indicates the request for the deactivation of pre-configured E2E UP Path from the UE is successful or failed.

[0181] 12. If the response to the request for the deactivation of E2E UP Path from the UE 801 is successful, the ASM updates the adaptive session configuration of the UE 801. It includes removing of the existing pre-defined PDU session from the current session configuration of the UE. In addition, the ASM may update the mapping table of pre-configured sessions, for example to update that the status of the pre-configured session has changed from unavailable to available for other UEs and the association with the UE is removed.

[0182] The new session configuration may have a different number of data (for example, PDU) sessions and / or a different configuration of end to end paths to the current session configuration. The modification of the current communication session configuration of the UE to form the new session configuration may be performed according to one or more of the following: (i) the addition of one or more new data sessions into the current communication session configuration (ii) removing of one or more of existing data sessions from the current communication session configuration (iii) allocation and / or activation of one or more of pre-configured sessions into the current communication session configuration (iv) de-allocation and / or de-activation of one or more of pre-configured sessions from the current communication session configuration. An example of a new multisession configuration can include dynamically pairing (or removing) of one or more PDU sessions (i.e., data sessions) to (or from) the current multi-session configuration of the UE.

[0183] Adaptive communication session enforcement mechanisms

[0184] In the following, two exemplary enforcement mechanisms to support the adaptive session modification are described. In a first mechanism, the configuration of new E2E UP paths information for the UE achieving the new requirements is already determined by the network (e.g., supported by other dedicated network entity) for the enforcement of adaptive session modification of the UE. In a second mechanism, the configuration of new E2E UP paths information for the UE achieving the new requirements is not available when the adaptive session modification request is triggered. The network is aware of the new requirements of the session configuration for the UE.

[0185] In the first mechanism, the ASM entity may use the ASM mapping table with the data key (e.g., SUPI, DS indication and / or PDU session identification) to check the status and session configuration of the UE. The ASM entity can compare the difference between the current session configuration and the new session configuration to determine for the enforcement whether new PDU session(s) can be paired and / or the existing PDU session(s) can be released. Some examples of an enabling mechanism for providing a new session configuration of UEs for achieving new reliability requirements can be seen in WO 2024 / 146687 Al.

[0186] Some exemplary benefits of this first mechanism are efficient resource utilization and fast enforcement by in-advanced prediction and UP paths computation. The associated cost for in-advanced prediction and UP path computation is expected, but the reduction of communication resources usage is significantly lower compared to the static session configuration.

[0187] In the second mechanism, the ASM entity is aware of the new requirements of the adaptive session configuration and determines UP paths achieving the new requirements of the UE and / or the application associated with the UE. To achieve fast and realtime enforcement of adaptive sessions modification, the pre-configured connectivity or PDU session(s) are available for a UEor an application associated with one or more UEs. The pre-configured PDU sessions(s) are identified to achieve different level of target performance of the services. Based on the requirements or prediction, it is assumed that the network can decide the specific number of pre-configured and established connectivity or PDU session(s) for UEs and applications of the UEs in time granularity. If the requirements of a pre-configured session are fulfilled with the new session requirements of the UE, the preconfigured session comprising one or more data session is allocated and activated to the UE. If the UE is no longer needed to use the pre-configured session(s) (e.g., the new requirements are triggered), the pre-defined session is deactivated from the UE and available for the other UEs. An example of how to support the pre-configured sessions with respect to the different reliability level can be seen in WO 2024 / 146687 Al . For the selection of pre-configured sessions, the ASM entity can use an additional filter such as area information to select the pre-configured sessions for the UE or application associated to the UE.

[0188] Some exemplary benefits of this second mechanism are fast modification and enforcement of adaptive sessions. By enabling activation and deactivation functionalities for pre-configured session(s) and shared by multiple UEs (i.e., one UE at a time), the adaptive session modification can be enforced immediately when it is needed.

[0189] (i) Adaptive communication session information

[0190] An example of the internal logic of the ASM entity to store and update (i) the ASM information of the UE and (ii) the preconfigured sessions for the UEs will now be described.

[0191] To store and update the ASM information of the UE, a mapping table of ASM information may be used for the UE or application subject to the adaptive session configuration. Some non-limiting examples of information included in the mapping table is below:

[0192] Identification of the UE

[0193] Identification of the adaptive sessions of the UE

[0194] Identification of the data session(s) of the UE’s current session configuration

[0195] Identification of the data session(s) of the UE’s new session configuration

[0196] Identification of the pre-configured session(s)

[0197] Identification of the application

[0198] The current session configuration, optionally with the list of data sessions associated to the adaptive session, the E2E UP path information of each data session

[0199] The new session configuration, optionally with the list of data sessions associated to the adaptive session, the E2E UP path information of each data session

[0200] Optionally, the information of pre-configured sessions

[0201] To store and update the pre-configured sessions for the UEs, the mapping table can be identified and may include the following non-limiting information:

[0202] Identification of the pre-configured session. (Note that each pre-configured session comprises one or more data sessions. An example of data session is a PDU session.)

[0203] Identifications of one or more data sessions associated with the pre-configured session

[0204] Target level of performance matrices and values of each pre-configured session

[0205] Availability information indicating whether the pre-configured sessions is available or in used by a UE

[0206] One example of an ASM information mapping table is illustrated in Table 2 below. In this example, the ASM information is based on per UE granularity. The same can be applied to the application granularity.Table 2: Example of ASM information mapping table.

[0207]

[0208] An example of pre-configured sessions information is illustrated in Table 3 below. In this example, the pre-configured sessions are configured with respect to the reliability requirements. For the other performance matrices, the same can be applied. Each pre-configured session comprises one or more PDU session.

[0209] Table 3: Example of pre-configured connectivity / sessions information mapping table.

[0210]

[0211] Some exemplary embodiments of the presented invention are further described below for (i) adaptive session identification (ii) adaptive session configuration and (ii) adaptive session information provided in the adaptive session modification.

[0212] A first embodiment is related to the adaptive session identification, where a DS indication is used to identify adaptive session feature and management of a UE. The DS indication can be configured as subscription data or application data and / or policy data to provision the network entities such as the ASM entity to perform adaptive session configuration and modification. Examples of the configuration of the DS indication and related information name is defined in Table 1 above.A further embodiment is related to the adaptive session configuration, in particular, how the system can retrieve the DS indication for adaptive session configuration and modification during the registration procedure, session establishment procedure and / or application provided data. Figure 12 illustrates a communication flow for the provisioning of the DS indication for adaptive session configuration and modification in a mobile communication network. In this example, the network further comprises a registration management entity 811. CN entities are shown at 812. A session management entity is shown at 813.

[0213] The network first performs DS indication provisioning for the UE 801. As shown at 1201, the network may perform DS indication provisioning for the UE 801 in a registration procedure, as described above with reference to Figure 5. Alternatively, as shown at 1202, the DS indication provisioning of the UE may be performed during a session management procedure at session management entity 813, as described above with reference to Figure 6. In another example, the DS indication provisioning of an application may be performed by the AF 809, as described above with reference to Figure 7. A request for dynamic session configuration by the AF 809 is shown at 1203 and can be performed as described above.

[0214] In another embodiment, Figure 13 shows ASM triggers for a UE or an application associated with one or more UEs. At 1301, session establishment and DS configuration procedures are performed, using any of the approaches described above. At 1302, the ASM entity 806 maps the DS information with the current PDU session information.

[0215] As shown at 1303, this embodiment may be performed, for example, in combination with the procedure of adaptive session modification trigger Option A with the complete information of new session configuration, as described in F igure 8. As shown at 1304, it may alternatively be performed in combination with the procedure of adaptive session modification trigger Option B with the requirements of new session configuration described in Figure 9.

[0216] In another embodiment, the procedure of adaptive session modification enforcement according to Option A may be performed with the complete information of new session configuration, as described above with reference to Figure 10.

[0217] In a further embodiment, the procedure of adaptive session modification enforcement Option B may be performed with the requirements of new session configuration, as described above with reference to Figure 11.

[0218] In summary, the ASM network entity described herein can be implemented in a communication network or subnetwork to support adaptive session configuration for UEs or applications, where the DS indication is identified to detect and track the adaptive session configuration of a UE or an application and to perform adaptive session modification. An advantageous effect of this feature in 5G-A or future systems is that the system can support session management with efficient and scalable in terms of resources and adaptive and real-time in terms of new session configuration requirements.

[0219] The DS indication can be used to identify adaptive session configuration and to perform the adaptive session modification of the UE or application associated to the UEs. An exemplary advantageous effect of this feature is that the system can support adaptive session management with efficient and scalable in terms of resources. Furthermore, the system can support adaptive and real-time session modification in terms of new requirements of the services.

[0220] The ASM network entity can further support adaptive session modification of a UE or an application to perform the enforcement of new sessions configuration from the current session configuration. An advantageous effect of this feature in 5G-A or future systems is that the system can support adaptive session modification with adaptive and real-time in terms of new session modification requirements.The ASM network entity can further support pre-configured connectivity or sessions with respect to different levels of requirements of the services to enable adaptive sessions of the UE or application associated to the UEs, with selection of Reliable Connectivity for a UE. An advantageous effect of this feature is that a 5G-A or future system can be given the ability to provide a fast and real-time modification of new adaptive sessions enforcement.

[0221] Interfaces, procedures, and information exchanged related to the adaptive session configuration, the trigger of adaptive session modification, and the enforcement of new adaptive session can support session management efficiently and with scalability in terms of resources. Furthermore, the system can support adaptive and real-time in terms of new session configuration and modification requirements.

[0222] Figure 14 shows exemplary steps of a method for implementation at a network entity, such as the ASM entity described herein. The network entity is part of a mobile communication network configured for modification of one or more adaptive communication session configurations of respective one or more UEs and / or an application, wherein the one or more adaptive communication session configuration comprising one or more data sessions. At step 1401, the method comprises receiving a request for modification of an adaptive communication session configuration associated with a user equipment, UE, and / or an application implemented by the UE, wherein the request for modification of the adaptive communication session configuration comprises an indication specifying a requirement for a change to a new communication session configuration from a current communication session configuration. At step 1402, the method comprises determining, based on an association of dynamic session configuration information, whether the UE and / or the application is / are subject to modification of the adaptive communication session configuration.

[0223] Figure 15 shows exemplary steps of a method for implementation at a UE. The UE is configured for communication with a mobile communication network and is configured to implement an adaptive communication session configuration, the UE and / or an application implemented by the UE being associated with a respective dynamic session indication, the dynamic session indication specifying a requirement at the UE and / or the application for adaptive communication session modification. At step 1501, the method comprises providing a dynamic session indication to the mobile communication network (for example, to a network entity of the mobile communication network).

[0224] The approach described herein can highlight efficient network resource and energy usage for communication or computing services, for example by targeting sustainability capability and fulfilling the capabilities of the (hyper) high-performance requirements of the services such as reliability, latency and throughput.

[0225] Embodiments of the invention may be implemented as a CN feature for the mobile communication network. In particular, to support session management enhancement for the mobile communication network. The described solutions allow session management with adaptive, real-time, faster and efficient features.

[0226] The ASM entity can support adaptive sessions configuration and adaptive multi-sessions modification features that allows the change of a UE’s current communication session configuration to a new communication session configuration in real-time and using efficient mechanisms.

[0227] The adaptive session configuration feature identifies the functionalities of the adaptive session, the adaptive session indication and the procedures of adaptive session configuration and provisioning of the UE or application by the network.

[0228] The adaptive session modification feature includes the procedures of how the network supports the adaptive session modification triggers and the enforcement of a new adaptive session configuration for a UE or application associated with theUE. In addition, the mechanisms of new adaptive session configuration are proposed if the network is aware of the new adaptive session requirements.

[0229] The method and procedures of the adaptive session configuration and modification of the UE or application can be applicable for a 5G-A system or a future generation communication system to support the services or communication services requiring adaptive sessions in real-time, fast configuration and sustainable mechanisms in terms of resource and energy efficiency.

[0230] With the DS indication feature, the system can support session management in an efficient, scalable (in terms of resources) and adaptive (in terms of new session configuration requirements) way.

[0231] With ASM mechanisms, the system can support dynamic session enforcement with an efficient and faster mechanism (for example., without releasing the current session(s) to re-establish new session(s) according to simple enhancement of 5G mechanisms) to achieve requirements, such as dynamic reliability requirements.

[0232] The mobile communication network can advantageously support dynamic sessions configuration and dynamic multi-sessions modification to adapt new session configuration of one or more UEs according to target performance matrices in real-time, using a resource- and energy-efficient mechanism. This can allow the network to identify adaptive session management, control and enforcement to enable the change of UE’s current session configuration to a new session configuration in real time and with resource and energy efficiency with respect to the performance requirements of the communication or computation services.

[0233] PDU session modifications in the prior art for 5G / 5G-A systems are generally related to modify an existing single PDU session scenario and are not suitable for application for multiple PDU sessions modifications of the UE in real-time network management and control. Redundant transmission with dual connectivity in the prior art can support multi PDU sessions configuration (i.e., two PDU sessions). However, the dual connectivity mechanism supports only static session configuration with no additional PDU session modification feature. After establishing two PDU sessions for a UE, this session configuration is fixed and cannot be adapted in real-time during the operation of the services. On the other hand, the prior art solution does not cover the functionalities to establish or release one or more PDU sessions of the UE’s current session configuration automatically during the operation of the current session configuration and in a real-time manner. Analytics support on redundant transmission addresses when to activate or deactivate redundant transmission at N3 / N9 tunnels in QoS flow level. However, this prior art is based on one PDU session scenario and highlights the activation and de-activation of QoS flows which is different with multiple PDU sessions configuration. Similarly, the prior art MA-PDU session has a feature to switch between different accesses (e.g., 3GPP Access and non-3GPP Access) based on the ATSSS rules but the end-to-end user plane connectivity is based on a single PDU session. The switching of one access technology to another access technology is different with adapting multiple access links involving multiple PDU sessions configuration.

[0234] Alternative solutions, such as 5G based pure re-configuration of sessions (i.e., release the current session(s) configuration and re-establish new session(s)) are inefficient in terms of reconfiguration delays, signaling overheads, unnecessary modifications and associated energy consumption in sessions release and re-establishment of PDU session(s).

[0235] The technical solutions described herein are related to the enhancement of session management or new connectivity features for use cases such as in dynamic reliability requiring communication services and HRLLC. The following other scenarios may also require dynamic session configuration and modification feature to adapt the service or performance requirements.Immersive communication scenarios, including extended reality, haptic communication and holographic communication generally require high data rates, low latency and high reliability. The challenges of these requirements might be avoided by enhanced immersive communication with adaptive sessions configuration and modification to achieve the expected performance while reducing resource and energy consumption of the network.

[0236] In ubiquitous connectivity scenarios, dynamicity of connectivity among UEs and Network components is expected, hence adaptive session connectivity requiring different performance metrics, such as delay, bandwidth, or reliability will be benefits using adaptive session configuration and modification features.

[0237] In integrated sensing and communication scenarios, it is expected that adaptive sessions with varying bandwidth requirements for sensing data transmission or Al computing are beneficial feature to support real-time and efficient resource and energy consumption of the network.

[0238] Other applications are also possible.

[0239] The disclosure discloses in isolation each individual feature described herein and any combination of two or more such features, to the extent that such features or combinations are capable of being carried out based on the specification as a whole in the light of the common general knowledge of a person skilled in the art, irrespective of whether such features or combinations of features solve any problems disclosed herein. The aspects of the invention may consist of any such individual feature or combination of features. In view of the foregoing description, it will be evident to a person skilled in the art that various modifications may be made within the scope of the invention.

Claims

CLAIMS1. A network entity (100, 301, 505, 806) in a mobile communication network (300), the network entity configured for modification of one or more adaptive communication session configurations, wherein the one or more adaptive communication session configurations comprise one or more data sessions, wherein the network entity is configured to:receive ( 1401 ) a request for modification of an adaptive communication session configuration associated with a user equipment, UE (200, 501, 801), and / or an application implemented by the UE, wherein the request for modification of the adaptive communication session configuration comprises an indication specifying a requirement for a change to a new communication session configuration from a current communication session configuration; anddetermine (1402), based on an association of dynamic session configuration information, whether the UE and / or the application is / are subject to modification of the adaptive communication session configuration.

2. The network entity (100, 301, 505, 806) as claimed in claim 1, wherein the network entity is configured to, if the UE (200, 501, 801) and / or the application is / are subject to modification of the adaptive communication session configuration, modify the current communication session configuration to the new communication session configuration, wherein the new communication session configuration comprises one or more different data sessions for the UE (200, 501, 801) and / or an application service associated with the application.

3. The network entity (100, 301, 505, 806) as claimed in claim 1 or claim 2, wherein the network entity is configured to receive a dynamic session indication, the dynamic session indication being associated with the UE (200, 501, 801) and / or the application, the dynamic session indication comprising an indication of a requirement at the UE (200, 501, 801) and / or the application for adaptive communication session modification.

4. The network entity (100, 301, 505, 806) as claimed in claim 3, wherein the network entity is configured to determine the dynamic session configuration information by associating the dynamic session indication with the UE (200, 501, 801) and / or the application.

5. The network entity (100, 301, 505, 806) as claimed in claim 3 or claim 4, wherein the network entity is configured to receive the dynamic session indication from another network entity in the mobile communication network (300) or from an application network entity in the mobile communication network (300), wherein the dynamic session indication is provided to the network entity during a registration procedure and / or a session establishment procedure, or during application-related or user-related policy data provisioning.

6. The network entity (100, 301, 505, 806) as claimed in any of claims 3 to 5, wherein the dynamic session indication is configured as part of user subscription data or application-related policy data and wherein the network entity is configured to support the dynamic session configuration information for adaptive session modification of the UE (200, 501, 801) and / or the application.

7. The network entity (100, 301, 505, 806) as claimed in any of claims 3 to 6, wherein the dynamic session indication is a binary value, a scalar value or one or more strings.

8. The network entity (100, 301, 505, 806) as claimed in any preceding claim, wherein the request for modification of an adaptive communication session configuration includes one or more of the following: one or more dynamic session indications for one or more UEs, one or more UE identifiers and new session configuration information for one or more UEs, area of service information, one or more application related identifications, the current communication session configuration and new27communication session configuration information, wherein the new communication session information comprises the new communication session configuration and / or requirements of the new communication session configuration of the UE (200, 501, 801) and / or application.

9. The network entity (100, 301, 505, 806) as claimed in any preceding claim, wherein when the UE (200, 501, 801) is configured to the new communication session configuration from the current communication session configuration, the network entity (100, 301, 505, 806) is configured to update the dynamic session configuration information to associate the new communication session configuration with the UE (200, 501, 801).

10. The network entity (100, 301, 505, 806) as claimed in any preceding claim, wherein the network entity is configured to modify the current communication session configuration of the UE (200, 501, 801) according to one or more of the following: (i) addition of one or more new data sessions into the current communication session configuration (ii) removing of one or more of existing data sessions from the current communication session configuration (iii) allocation and / or activation of one or more of pre-configured sessions into the current communication session configuration (iv) de-allocation and / or de-activation of one or more of pre-configured sessions from the current communication session configuration.

11. The network entity (100, 301, 505, 806) as claimed in any preceding claim, wherein the network entity is configured to trigger enforcement for the modification of the current communication session configuration to the new communication session configuration to a core network entity (503, 812) and / or a radio access network entity (304, 802, 802a, 802b) of the mobile communication network (300).

12. The network entity (100, 301, 505, 806) as claimed in any preceding claim, wherein one or more of the current communication session configuration and the new communication session configuration comprise multiple data sessions, where the new communication session configuration has a different number of data sessions and / or a different configuration of end to end paths to the current communication session configuration.

13. The network entity (100, 301, 505, 806) as claimed in any preceding claim, wherein the network entity is configured to receive the request for modification of an adaptive communication session configuration from a core network entity (503, 812) of the mobile communication network (300), and / or an application function (507, 809) of the mobile communication network (300) via a policy entity (303, 807) of the mobile communication network (300).

14. The network entity (100, 301, 505, 806) as claimed in any preceding claim, wherein the network entity is configured to determine the new communication session configuration.

15. The network entity (100, 301, 505, 806) as claimed in any preceding claim, wherein the network entity is configured to receive application-related and / or user-related policy information from a policy entity (303, 807) of the mobile communication network (300) and determine the modification of the current communication session configuration in dependence on the policy information.

16. A user equipment, UE (200, 501, 801), configured for communication with a mobile communication network (300), theUE being configured to implement an adaptive communication session configuration, the UE and / or an application implemented by the UE being associated with a dynamic session indication, the dynamic session indication specifying a requirement at the UE and / or the application for adaptive communication session modification, wherein the UE is configured to provide (1501) the dynamic session indication to the mobile communication network (300).

17. The UE (200, 501, 801) as claimed in claim 16, wherein the UE is configured to, in response to an indication from a network entity (100, 301, 505, 806) of the mobile communication network (300), modify a current communication session configuration to a new communication session configuration comprising one or more different data sessions for the UE (200, 501 , 801 ).

18. A method (1400) for implementation at a network entity (100, 301, 505, 806) in a mobile communication network (300), the network entity configured for modification of one or more adaptive communication session configurations, wherein the one or more adaptive communication session configurations comprise one or more data sessions, the method comprising:receiving (1401) a request for modification of an adaptive communication session configuration associated with a user equipment, UE (200, 501, 801), and / or an application implemented by theUE, wherein the request for modification of the adaptive communication session configuration comprises an indication specifying a requirement for a change to a new communication session configuration from a current communication session configuration; anddetermining (1402), based on an association of dynamic session configuration information, whether the UE and / or the application is / are subject to modification of the adaptive communication session configuration.

19. A method (1500) for implementation at a user equipment, UE (200, 501 , 801 ), configured for communication with a mobile communication network (300), the UE being configured to implement an adaptive communication session configuration, the UE and / or an application implemented by the UE being associated with a respective dynamic session indication, the dynamic session indication specifying a requirement at the UE and / or the application for adaptive communication session modification, the method comprising providing (1501) the dynamic session indication to the mobile communication network.

20. The method (1500) as claimed in claim 19, wherein the method (1500) further comprises, in response to an indication from a network entity (100, 301, 505, 806) of the mobile communication network (300), modifying a current communication session configuration to a new communication session configuration comprising one or more different data sessions for the UE (200, 501, 801).

Images