Session management nodes, access and mobility nodes, UE, policy control node and methods in a wireless communications network

Abstract

A method performed by a first session management node (111) for handling DS in a wireless communication network (100) is provided. The first session management node 5 (111) receives a first session context establishment request for establishing a DS session. The first session context establishment request comprises a first SUPI and a DS correlation ID. The first SUPI is associated with a first access. The first session management node (111) establishes a context for the DS session using the first SUPI, the DS correlation ID and a first DS SUPI. The first DS SUPI indicates a second SUPI 10 associated with the UE (121). The first session management node (111) requests a policy control node (113) to establish a policy association to be established. The request comprises the first SUPI and the first DS SUPI. The first session management node (111) receives a third session context establishment request for establishing the DS session. The third session context establishment request comprises the second SUPI and the DS 15 correlation ID. The second SUPI is associated with a second access different from first access. The first session management node (111) updates the context for the DS session using the second SUPI, the DS correlation ID and a second DS SUPI. The first session management node (111) updates the policy association by sending a policy association establishment request to a policy control node (113). The request comprising the second 20 SUPI and the second DS SUPI.

Description

[0001] SESSION MANAGEMENT NODES, ACCESS AND MOBILITY NODES, UE, POLICY

[0002] CONTROL NODE AND METHODS IN A WIRELESS COMMUNICATIONS NETWORK

[0003] TECHNICAL FIELD

[0004] Embodiments herein relate to a server node, client nodes and methods performed therein regarding wireless communication. Furthermore, a computer program product and a computer-readable storage medium are also provided herein. Especially, embodiments herein relate to handling or enabling communication, such as managing data delivery, in a communication network.

[0005] BACKGROUND

[0006] In a typical wireless communication network, wireless devices, also known as wireless communication devices, mobile stations, stations (STA) and / or User Equipment (UE), communicate via a Wide Area Network or a Local Area Network such as a Wi-Fi network or a cellular network comprising a Radio Access Network (RAN) part and a Core Network (CN) part. The RAN covers a geographical area which is divided into service areas or cell areas, which may also be referred to as a beam or a beam group, with each service area or cell area being served by a radio network node such as a radio access node e.g., a Wi-Fi access point, a Base Station (BS) or a radio base station (RBS), which in some networks may also be denoted, for example, a Base Station (BS), a NodeB, eNodeB (eNB), or gNodeB (gNB) as denoted in Fifth Generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by the radio network node. The radio network node communicates over an air interface operating on a radio frequency with the wireless devices within the range of the radio network node.

[0007] 3rd Generation Partnership Project (3GPP) is the standardization body for specifying the standards for the cellular system evolution, e.g., including 3G, 4G, 5G and the future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E- UTRA) and Evolved Packet System (EPS) have been completed within the 3GPP. In 4G also called a Fourth Generation (4G) network, EPS is core network and E-UTRA is radio access network. In 5G, 5GC is core network, NR is radio access network. As a continued network evolution, the new release of 3GPP specifies a 5G network also referred to as 5G New Radio (NR) and 5G Core (5GC).

[0008] Frequency bands for 5G NR are being separated into two different frequency ranges, Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 comprises sub-6 GHz frequency bands. Some of these bands are bands traditionally used by legacy standards but have been extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. FR2 comprises frequency bands from 24.25 GHz to 52.6 GHz. Bands in this millimeter wave range have shorter range but higher available bandwidth than bands in the FR1.

[0009] Multi-antenna techniques may significantly increase the data rates and reliability of a wireless communication system. For a wireless connection between a single user, such as UE, and a base station (BS), the performance is in particular improved if both the transmitter and the receiver are equipped with multiple antennas, which results in a Multiple-Input Multiple-Output (MIMO) communication channel. This may be referred to as Single-User (SU)-MIMO. In the scenario where MIMO techniques is used for the wireless connection between multiple users and the base station, MIMO enables the users to communicate with the base station simultaneously using the same time-frequency resources by spatially separating the users, which increases further the cell capacity. This may be referred to as Multi-User (MU)-MIMO. Note that MU-MIMO may benefit when each UE only has one antenna. The cell capacity can be increased linearly with respect to the number of antennas at the BS side. Due to that, more and more antennas are employed in BS. Such systems and / or related techniques are commonly referred to as massive MIMO.

[0010] In addition to faster peak Internet connection speeds, 5G planning aims at higher capacity than current 4G, allowing higher number of mobile broadband users per area unit, and allowing consumption of higher or unlimited data quantities in gigabyte per month and user. This would make it feasible for a large portion of the population to stream high-definition media many hours per day with their mobile devices, when out of reach of Wi-Fi hotspots. 5G research and development also aims at improved support of machine to machine communication, also known as the Internet of things, aiming at lower cost, lower battery consumption and lower latency than 4G equipment.

[0011] Currently, a UE can simultaneously be connected to the 5G system using one Non-3GPP and one 3GPP access using Access Traffic Steering, Switching and Splitting (ATSSS). For the non-roaming case the architecture is given in 3GPP TS 23.501 v18.3.0, section 4.2.10, and shown in Figure 1 which illustrates non-roaming and roaming with local breakout architecture for ATSSS support.

[0012] To establish user plane resources for a Multi Access (MA) Packet Data Unit (PDU) session, the Policy Control Function (PCF) generates Policy Control and Charging (PCC) rules comprising MA PDU session control, see clause 6.3 in 3GPP TS 23.503 v18.3.0. The Session Management Function (SMF) provides MA ATSSS rules to the UE and establishes N4 rules to the User Plane Function (UPF). The N4 rules contain Multi-access rules (MARs) that each point to two Forwarding Action Rules (FARs), see clause 5.8.5.8 in 3GPP TS 23.501 V18.3.0.

[0013] Connecting a DualSteer device to two 3GPP access is an study item in Rel 19 under the topic of dual steering (DS). It is required that the User registers to the two accesses with two different Subscription Permanent Identifiers (SUPI) that are connected to the same subscription. A DualSteer device is a device supporting traffic steering and switching of user data, e.g., for different services, across two 3GPP access networks. It may be a single UE or two separate UEs in a single device. In the latter case, each UE is handling one SUPI. Minimum interruption should occur with switching the accesses. Stage 1 requirements for the DualSteer study have been agreed in 3GPP document S1- 233371.

[0014] SUMMARY

[0015] As part of developing embodiments herein a problem was identified by the inventor and will first be discussed.

[0016] Currently there are dual-SIM devices that may connect through two 3GPP accesses via two SUPIs. 3GPP Technical Specification Group and System Aspects 2 (3GPP TSG SA2) has also done enhancements to support such devices in the Multi- USIM (MUSIM) work item. However, it is assumed that each SUPI / SIM is used to access a specific service / operator, and there is no support for aggregating traffic over the two 3GPP accesses or switching traffic between them. This is what is to be studied in the new 3GPP SA2 study. The challenges are:

[0017] 1 . How to establish PDU sessions towards PDU session anchor (PSA) using two accesses with two different SUPIs

[0018] 2. As mentioned, the two SUPIs may be handled by two UEs in the DualSteer device. These two UEs may not be able to generate a common PDU session ID and this may be challenging in establishing a PDU session towards the common anchor UPF.

[0019] 3. Considering both SUPIs are connected to the same subscriber, how to handle the subscription data

[0020] 4. How the PCC, ATSSS, and N4 rules should change to support connection to DN through two different accesses with two SUPIs. An object of embodiments herein is, thus, to provide a mechanism that simplifies the DS handling and improves the performance of the wireless communication network.

[0021] According to an aspect of embodiments herein, the object is achieved by a method performed by a first session management node for handling Dual Steering (DS) in a wireless communication network.

[0022] The first session management node receives a first session context establishment request for establishing a DS session. The first session context establishment request comprises a first Subscription Permanent Identifier (SUPI) associated with a User Equipment (UE) and a DS correlation identity (ID). The first SUPI is associated with a first access.

[0023] The first session management node establishes a context for the DS session using the first SUPI, the DS correlation ID and a first DS SUPI associated with the first SUPI and / or the UE. The first DS SUPI indicates a second SUPI associated with the UE.

[0024] The first session management node requests a policy association to be established by sending a policy association establishment request to a policy control node. The request comprises the first SUPI and the first DS SUPI.

[0025] The first session management node receives a third session context establishment request for establishing the DS session. The third session context establishment request comprises the second SUPI associated with the UE, the DS correlation identity ID and optionally an ID of a DS session associated with the first SUPI. The second SUPI is associated with second access different from first access,

[0026] The first session management node updates the context for the DS session using the second SUPI, the DS correlation ID and a second DS SUPI associated with the second SUPI and / or the UE.

[0027] The first session management node updates the policy association by sending a policy association modification request to a policy control node. The request comprises the second SUPI and the second DS SUPI.

[0028] According to another aspect of embodiments herein, the object is achieved by a method performed by a first access and mobility node for handling DS in a wireless communication network.

[0029] The first access and mobility node receives a first session establishment request from a UE. The first session establishment request comprises a first SUPI associated with the UE and a DS correlation ID. The first SUPI is associated with a first access.

[0030] The first access and mobility node selects a first session management node. The first access and mobility node sends a first session context establishment request to a selected first session management node. The first session context establishment request comprises the first SUPI and the DS correlation ID. The DS correlation ID is comprised in a mobility management (MM) part of the request and in a session management (SM) container of the request.

[0031] According to another aspect of embodiments herein, the object is achieved by a method performed by a second access and mobility node for handling DS in a wireless communication network.

[0032] The second access and mobility node receives a second session establishment request from a UE. The second session establishment request comprises a second SUPI associated with the UE and the DS correlation ID. The second SUPI is associated with a second access. The DS correlation ID is comprised in an MM part of the request and in an SM container of the request.

[0033] The second access and mobility node selects session management node. The selected session management node is a first session management node selected for the DS session by a first access and mobility node.

[0034] The second access and mobility node sends a session context establishment request to the selected session management node. The session context establishment request comprises the second SUPI, the DS correlation ID and optionally the ID of the DS session related to the first SUPI.

[0035] According to another aspect of embodiments herein, the object is achieved by a method performed by a UE for handling DS in a wireless communication network.

[0036] The UE sends a first session establishment request to a first access and mobility node. The first session establishment request comprises a first SUPI associated with the UE and a DS correlation ID. The first SUPI is associated with a first access. The DS correlation ID is comprised in an first part of the request and in a second part of the request.

[0037] The UE sends a second session establishment request to a second access and mobility node. The second session establishment request comprises a second SUPI associated with the UE and the DS correlation ID. The second SUPI is associated with a second access different from the first access. The DS correlation ID is comprised in an first part of the request and in a second part of the request.

[0038] According to another aspect of embodiments herein, the object is achieved by a method performed by a policy control node for handling DS in a wireless communication network. The policy control node establishes a policy association with a first session management node for a DS session by receiving a request from the first session management node. The request comprising a first SUPI and a first DS SUPI. The establishing comprises creating one or more policy rules, taking the first SUPI and the and the first DS SUPI into account.

[0039] The policy control node provides the one or more policy rules for the DS session to the first session management node.

[0040] The policy control node updates the policy association with the first session management node for the DS session by receiving a request from the first session management node. The request comprises a second SUPI and a second DS SUPI. The updating comprises updating the one or more policy rules, taking the second SUPI and the and the second DS SUPI into account.

[0041] The policy control node provides the one or more policy rules for the DS session to the first session management node.

[0042] According to another aspect of embodiments herein, the object is achieved by a first session management node configured to handle DS in a wireless communication network.

[0043] The first session management node is further configured to receive a first session context establishment request for establishing a DS session. The first session context establishment request adapted to comprise a first SUPI associated with a UE and a DS correlation ID. The first SUPI is adapted to be associated with a first access.

[0044] The first session management node is further configured to establish a context for the DS session using the first SUPI, the DS correlation ID and a first DS SUPI associated with the first SUPI and / or the UE. The first DS SUPI adapted to indicate a second SUPI associated with the UE.

[0045] The first session management node is further configured to request a policy association to be established by sending a policy association establishment request to a policy control node. The request adapted to comprise the first SUPI and the first DS SUPI.

[0046] The first session management node is further configured to receive a third session context establishment request for establishing the DS session. The third session context establishment request adapted to comprise the second SUPI associated with the UE and the DS correlation ID. The second SUPI is adapted to be associated with second access different from first access. The first session management node is further configured to update the context for the DS session using the second SUPI, the DS correlation ID and a second DS SUPI adapted to be associated with the second SUPI and / or the UE.

[0047] The first session management node is further configured to update the policy association by sending a policy association modification request to a policy control node. The request adapted to comprise the second SUPI and the second DS SUPI.

[0048] According to another aspect of embodiments herein, the object is achieved by a first access and mobility node configured to handle DS in a wireless communication network.

[0049] The first access and mobility node is further configured to receive a first session establishment request from a UE. The first session establishment request is adapted to comprise a first SUPI associated with the UE and a DS correlation ID. The first SUPI is adapted to be associated with a first access. The DS correlation ID is adapted to be comprised in a MM part of the request and in a SM container of the request.

[0050] The first access and mobility node is further configured to select a first session management node.

[0051] The first access and mobility node is further configured to send a first session context establishment request to the selected first session management node. The first session context establishment request adapted to comprise the first SUPI and the DS correlation ID.

[0052] According to another aspect of embodiments herein, the object is achieved by a second access and mobility node configured to handle DS in a wireless communication network.

[0053] The second access and mobility node is further configured to receive a second session establishment request from a UE. The second session establishment request is adapted to comprise a second SUPI associated with the UE and a DS correlation ID. The second SUPI is adapted to be associated with a second access. The DS correlation ID is adapted to be comprised in a MM part of the request and in a SM container of the request.

[0054] The second access and mobility node is further configured to select a session management node. The selected session management node is adapted to be a first session management node selected for the DS session by a first access and mobility node.

[0055] The second access and mobility node is further configured to send a session context establishment request to the selected session management node. The session context establishment request is adapted to comprise the second SUPI and the DS correlation ID.

[0056] According to another aspect of embodiments herein, the object is achieved by a UE configured to handle DS in a wireless communication network.

[0057] The UE is further configured to send a first session establishment request to a first access and mobility node. The first session establishment request is adapted to comprise a first SUPI associated with the UE and a DS correlation ID. The first SUPI is adapted to be associated with a first access. The DS correlation ID is adapted to be comprised in an first part of the request and in a second part of the request.

[0058] The UE is further configured to send a second session establishment request to a second access and mobility node. The second session establishment request is adapted to comprise a second SUPI associated with the UE and the DS correlation ID. The second SUPI is associated with a second access different from the first access. The DS correlation ID is adapted to be comprised in a first part of the request and in a second part of the request.

[0059] According to another aspect of embodiments herein, the object is achieved by a policy control node configured to handle DS in a wireless communication network.

[0060] The policy control node is further configured to establish a policy association with a first session management node for a DS session by receiving a request from the first session management node. The request is adapted to comprise a first SUPI and a first DS SUPI. The establishing is adapted to comprise to create one or more policy rules, taking the first SUPI and the and the first DS SUPI into account.

[0061] The policy control node is further configured to provide the one or more policy rules for the DS session to the first session management node.

[0062] The policy control node is further configured to update the policy association with the first session management node for the DS session by receiving a request from the first session management node. The request adapted to comprise a second SUPI and a second DS SUPI. The updating is adapted to comprise to update the one or more policy rules, taking the second SUPI and the and the second DS SUPI into account.

[0063] The policy control node is further configured to provide the one or more policy rules for the DS session to the first session management node.

[0064] According to another aspect of embodiments herein, the object is achieved by a user data node for handling DS in a wireless communication network.

[0065] The user data node provides subscription data associated with a first Subscription Permanent Identifier, SUPI, and / or a UE to a first session management node. The subscription data comprises a first DS Subscription Permanent Identifier, SUPI, indicating a second SUPI associated with the UE.

[0066] The user data node registers the DS session by receiving a registration message indicating a DS correlation identity, ID, from the first session management node.

[0067] According to another aspect of embodiments herein, the object is achieved by a user data node configured to handle DS in a wireless communication network.

[0068] The user data node is further configured to provide subscription data associated with a first Subscription Permanent Identifier, SUPI, and / or the UE (121) to a first session management node. The subscription data is adapted to comprise a first DS SUPI indicating a second SUPI associated with the UE.

[0069] The user data node is further configured to register the DS session by receiving a registration message indicating a DS correlation identity, ID, from the first session management node.

[0070] BRIEF DESCRIPTION OF THE DRAWINGS

[0071] Examples of embodiments herein are described in more detail with reference to attached drawings in which:

[0072] Figure 1 a schematic block diagram according to prior art.

[0073] Figure 2 a schematic block diagram according to embodiments herein.

[0074] Figure 3 a schematic block diagram according to embodiments herein.

[0075] Figure 4 a schematic block diagram according to embodiments herein.

[0076] Figure 5 a schematic block diagram according to embodiments herein.

[0077] Figure 6 a schematic block diagram according to prior art. overview of a wireless communication network according to embodiments herein.

[0078] Figure 7 is a flowchart depicting embodiments of a method in a first session management node.

[0079] Figure 8 is a flowchart depicting embodiments of a method in a second session management node.

[0080] Figure 9 is a flowchart depicting embodiments of a method in a first access and mobility node.

[0081] Figure 10 is a flowchart depicting embodiments of a method in a second access and mobility node.

[0082] Figure 11 is a flowchart depicting embodiments of a method in a UE. Figure 12a is a flowchart depicting embodiments of a method in a policy control node.

[0083] Figure 12b is a flowchart depicting embodiments of a method in a user data node.

[0084] Figure 13 is a signaling diagram according to embodiments herein.

[0085] Figure 14 is a signaling diagram according to embodiments herein.

[0086] Figure 15 is a schematic block diagram according to embodiments herein.

[0087] Figure 16 is a schematic block diagram according to embodiments herein.

[0088] Figure 17 is a schematic block diagram according to embodiments herein.

[0089] Figure 18 is a schematic block diagram according to embodiments herein.

[0090] Figure 19 is a signaling diagram according to embodiments herein.

[0091] Figure 20 is a signaling diagram according to embodiments herein.

[0092] Figure 21 is a schematic block diagram illustrating embodiments of a first session management node.

[0093] Figure 22 is a schematic block diagram illustrating embodiments of a second session management node.

[0094] Figure 23 is a schematic block diagram illustrating embodiments of a first access and mobility node.

[0095] Figure 24 is a schematic block diagram illustrating embodiments of a second access and mobility node.

[0096] Figure 25 is a schematic block diagram illustrating embodiments of a UE.

[0097] Figure 26a is a schematic block diagram illustrating embodiments of a policy and control node.

[0098] Figure 26b is a schematic block diagram illustrating embodiments of a user data node.

[0099] Figure 27 shows an example of a communication system QQ100 in accordance with some embodiments.

[0100] Figure 28 shows a UE QQ200 in accordance with some embodiments.

[0101] Figure 29 shows a network node QQ300 in accordance with some embodiments.

[0102] Figure 30 is a block diagram illustrating a virtualization environment QQ400 in which functions implemented by some embodiments may be virtualized.

[0103] DETAILED DESCRIPTION

[0104] Embodiments herein is based on providing a common anchor, such as a UPF, and SMF inside the 5GC for the DS traffic from both 3GPP access networks. Non-roaming and roaming architectures are shown in Figures 2-4. Figure 2 shows a non-roaming dual steering architecture. Figure 3 shows a dual steering architecture with roaming in one access. Figure 4 shows a dual steering architecture with roaming in both accesses with common Visited Public Land Mobile Network (VPLMN). Figure 5 shows a dual steering architecture with roaming in both accesses with two different VPLMNs.

[0105] Embodiments herein may have no Access and Mobility Function (AMF) impact, also referred to as Alternative 1 , and limited AMF impact, also referred to as Alternative 2.

[0106] The alternative 1 may have the advantage that in the roaming case, the VPLMN does not need to support Dual Steering and only the Home PLMN (HPLMN) should support it, but it introduces some limitations such as: homogeneous implementation of the DS feature is assumed.

[0107] For each alternative different aspects are considered, namely registration, policy, subscription information, and session management.

[0108] Registration: UE and Network include their capability / support for dual steering during registration.

[0109] Policy: UE Route Selection Policy (URSP), PCC, and ATSSS rules should be enhanced to support DS. Also the PCC rules should be updated every time one of the PLMNs or access type changes.

[0110] Subscription and UE context data in UDM: The following new fields are added in UDM:

[0111] DS SUPI is added in the session management subscription and also access and mobility subscription data for both SUPI1 (containing SUPI2) and SUPI2 (containing SUPI1).

[0112] DS Correlation identity (ID), is used to connect two PDU session requests and is added to UE context in SMF data in UDM / UDR.

[0113] Embodiments herein may provide methods and signaling to establish a connection to a Data Network (DN) with two 3GPP accesses and two SUPIs. Further, embodiments herein may provide new parameters in the UE subscription data, namely, DS SUPI, and new parameters in the UE context in UDM (DS Correlation ID). Yet further, embodiments herein may provide a new field in the PCC and ATSSS rules, namely Access descriptor and may also require enhancement in URSP rules.

[0114] Embodiments herein aim to handle connection from UE(s) in a DualSteer device, such as a UE, to the DN using two 3GPP accesses. They use a simple architecture including a single UPF, e.g., as PDU Session Anchor (PSA), and single SMF which makes the task of PDU session establishment easier to handle. Embodiments herein may have no zero impact or limited impact to the AMF.

[0115] Embodiments herein may use a separate field in the SM and MM subscription data (i.e., DS SUPI), instead of an internal group ID. Group IDs are independently managed objects and therefore more costly to operate. Furthermore, embodiments herein discusses the details of policy and user plane management introducing new fields in PCC, and ATSSS rules.

[0116] Embodiments herein may provide the advantage of a more efficient and simplified mechanism for DS handling and improves the performance of the wireless communication network.

[0117] Embodiments herein relate to wireless communication networks in general. Figure 6 is a schematic overview depicting a wireless communication network 100. The wireless communication network 100 comprises one or more RANs and one or more CNs. The wireless communication network 100 may use one or a number of different technologies. Embodiments herein relate to recent technology trends that are of particular interest in a NR context, however, embodiments are also applicable in further developments of existing wireless communications systems such as e.g. 6G, LTE or WCDMA.

[0118] In the wireless communication network 100, a user equipment (UE) 121, such as a mobile station, a wireless device, a non-access point (non-AP) STA, a STA, and / or a wireless terminal, is communicating via, e.g., one or more Access Networks (AN), e.g., RAN, to one or more CNs. It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, wireless communications terminal or device, user equipment, narrowband (NB)- internet of things (loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node, e.g., smart phone, laptop, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a network node within an area served by the network node. The UE 121 may also be referred to as a DualSteer device comprising two UEs independently accessing the wireless communication network 100.

[0119] The wireless communication network 100 comprises a radio network node 101 , e.g., an access node, an access controller, a base station, e.g. a radio base station such as a gNodeB (gNB), an evolved Node B (eNB, eNode B), a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a stand-alone access point, or any other network unit or node capable of communicating with a UE within a service area 11 , such as a cell, served by the radio network node 101 depending e.g., on a radio access technology and terminology used. The service area 11 may also be referred to as a cell, a beam or a beam group of a first radio access technology (RAT), such as 6G, 5G, LTE, Wi-Fi, or similar. The radio network node 101 may be associated with a first Public Land Mobile Network (PLMN) and / or a first NonPublic Network (NPN).

[0120] The wireless communication network 100 further comprises a first session management node 111 , a second session management node 112, a policy control node

[0121] 113, a user data node 114, a user plane node 115, a first access and mobility node 116 and a second access and mobility node 117. The first session management node 111 , the second session management node 112, the policy control node 113, the user data node

[0122] 114, the user plane node 115, the first access and mobility node 116 and the second access and mobility node 117 may be located in the CN. The session management nodes 111 , 112 may e.g., comprise an SMF. The policy control node 113 may e.g., be a PCC. The user data node 114 may e.g., be a UDM. The user plane node 115 may e.g., be a UPF. The first and second access and mobility nodes 116, 117 may e.g., be an AMF. It should be understood that these nodes may be separated nodes or co-located nodes.

[0123] Methods herein may be performed by the first session management node 111 , the second session management node 112, the policy control node 113, the first access and mobility node 116 and the second access and mobility node 117. As an alternative, a Distributed Node (DN) and functionality, e.g. comprised in the cloud 190 as shown in Figure 6, may be used for performing or partly performing the methods herein.

[0124] A method according to embodiments herein will now be described from the view of the first session management node 111 , together with Figure 7. Figure 7 depicts example embodiments of a method performed by the first session management node 111 for handling DS in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 7.

[0125] Action 701

[0126] The first session management node 111 receives a first session context establishment request for establishing a DS session. The first session context establishment request comprising a first SUPI associated with the UE 121 and a DS correlation ID. The first SUPI is associated with a first access. The DS correlation ID may, as mentioned above, be used to connect, such as associate, sessions or session requests, such as PDU sessions or PDU session requests. The DS correlation ID may e.g., be added to UE context in SMF data in UDM / UDR, such as the user data node 114. Thus, the DS correlation ID may identify the DS session, and / or correlate a first session and a second session in the DS session.

[0127] In some embodiments, the first session context establishment request comprises a request type parameter indicating request type initial request. In other words, the first session context establishment request may indicate that the request is an initial request, such as that this is the first session context establishment request in a DS session establishment procedure.

[0128] In some embodiment, the first session management node 111 receives the first session context establishment request is received from the first access and mobility node 116.

[0129] Action 702

[0130] The first session management node 111 establishes a context for the DS session using the first SUPI, the DS correlation ID and a first DS SUPI associated with the first SUPI and / or the UE 121. The first DS SUPI indicates a second SUPI associated with the UE 121.

[0131] The first DS SUPI may indicate the second SUPI associated with the UE 121 .

[0132] In some embodiments, the first session management node 111 obtains the first DS SUPI associated with the first SUPI and / or the UE 121 . The first session management node 111 may obtain the first DS SUPI from the user data node 114. The first session management node 111 may e.g., obtain the first DS SUPI from the user data node 114 by sending a request indicating the first SUPI, and receiving a response comprising the first DS SUPI.

[0133] Action 703

[0134] The first session management node 111 requests a policy association to be established by sending a policy association establishment request to a policy control node 113. The request comprises the first SUPI and the first DS SUPI.

[0135] The policy association request may enable the policy control node 113 to generate, such as create or establish, one or more policy rules for the DS session.

[0136] In some embodiments, the first session management node 111 obtains, such as receives, the one or more policy rules for the DS session from the policy control node 113.

[0137] Action 704 In some embodiments, the first session management node 111 registers the DS session in the user data node 114 by sending a registration message indicating the DS correlation ID to the user data node 114.

[0138] In some embodiments, the registration further registers the DS correlation ID in a UE context associated with the UE 121 in the user data node 114.

[0139] Action 705

[0140] The first session management node 111 receives a third session context establishment request for establishing the DS session. The third session context establishment request comprises the second SUPI associated with the UE 121 , the DS correlation ID and optionally an ID of the DS session associated with the first SUPI. The second SUPI is associated with second access different from first access.

[0141] Action 706

[0142] The first session management node 111 updates the context for the DS session using the second SUPI, the DS correlation ID and a second DS SUPI associated with the second SUPI and / or the UE 121.

[0143] Action 707

[0144] The first session management node 111 updates the policy association by sending a policy association modification request to a policy control node 113. The request comprises the second SUPI and the second DS SUPI.

[0145] In some embodiments, the first session management node 111 obtains, such as receives, the one or more updated policy rules for the DS session from the policy control node 113.

[0146] Establishing 702 the context for the DS session may comprise any one or more of the following:

[0147] The first session management node 111 may obtain the first DS SUPI associated with the first SUPI and / or the UE 121. The first DS SUPI indicates the second SUPI associated with the UE 121 .

[0148] The first session management node 111 may associate the DS session to the first SUPI and the first DS SUPI.

[0149] The first session management node 111 may establish a policy association with the policy control node 113 for the DS session by sending a request to the policy control node 113. The request comprising the first SUPI and the first DS SUPI. In response the request, the first session management node 111 may receive one or more policy rules from the policy control node 113. The first session management node 111 may establish an N4 session with the user plane function 115.

[0150] The first session management node 111 may register the DS session in the user data node 114 indicating the DS correlation ID to the user data node 114.

[0151] Updating 704 the context for the DS session may comprise any one or more of the following:

[0152] The first session management node 111 may obtain the second DS SUPI associated with the second SUPI and / or the UE 121. The second DS SUPI indicates the first SUPI associated with the UE 121 .

[0153] The first session management node 111 may update the policy association for the DS session by requesting an update to the established policy association from the policy control node 113. The request comprises the second DS SUPI and the second SUPI.

[0154] The first session management node 111 may update the N4 session by establishing a tunnel between the user plane node 115 and the second access.

[0155] A method according to embodiments herein will now be described from the view of the second session management node 112, together with Figure 8. Figure 8 depicts example embodiments of a method performed by the second session management node 111 for handling DS in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 8.

[0156] Action 801

[0157] The second session management node 111 receives, from the second access and mobility node 117, a second session context establishment request for establishing a DS session. The second session context establishment request comprises a second SUPI associated with the 121 , a DS correlation ID and optionally an ID of a DS session related to a first SUPI associated with the UE 121 or a parameter indicating that a PDU session related to the first SUPI has been established. The second SUPI is associated with a second access.

[0158] Action 802

[0159] The second session management node 111 obtains, using the DS correlation ID and the second DS SUPI, an ID of the first session management node 111 related to the DS session associated with the second DS SUPI. The second DS SUPI is associated with the second SUPI and / or the UE 121 . The second DS SUPI indicates the first SUPI associated with the UE 121 . Obtaining the ID of the first session management node 111 may comprise obtaining the second DS SUPI associated with the second SUPI and / or the UE 121. The second DS SUPI indicates the first SUPI associated with the UE 121 .

[0160] Action 803

[0161] The second session management node 111 requests the DS session to be redirected to the first session management node 111 by sending a redirection message to the second access and mobility node 117. The redirection message comprises the ID of the first session management node 111.

[0162] A method according to embodiments herein will now be described from the view of the first access and mobility node 116, together with Figure 9. Figure 9 depicts example embodiments of a method performed by the first access and mobility node 116 for handling DS in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 9.

[0163] Action 901

[0164] The first access and mobility node 116 receives a first session establishment request from the UE 121 . The first session establishment request comprises a first SUPI associated with the UE 121 and a DS correlation ID. The first SUPI is associated with a first access. In some embodiments, the DS correlation ID is comprised in an mobility management (MM) part of the request and in a session management (SM) container of the request.

[0165] In some embodiments, the first session establishment request is a DS session establishment request. The DS session establishment request indicates that a session management node supporting DS is to be selected. The first session management request may indicate that it is a DS session establishment request by the inclusion of the DS correlation ID in the MM part of the request. That the first session establishment request is DS session establishment request may indicate that a session management node supporting DS is to be selected.

[0166] In some embodiments, the first session establishment request comprises a request type parameter indicating request type initial request. In other words, the first session establishment request may indicate that the request is an initial request, such as that this is the first session establishment request in a DS session establishment procedure.

[0167] Action 902 The first access and mobility node 116 selects a first session management node

[0168] 111.

[0169] In some embodiments, selecting the first session management node 111 comprises selecting a session management node supporting DS. The access and mobility node 116 may know which session management nodes that supports DS, e.g., by signalling between the first access and mobility node 116 and session management nodes, and / or by configuration.

[0170] Action 903

[0171] The first access and mobility node 116 sends a first session context establishment request to the selected first session management node 111. The first session context establishment request comprising the first SUPI and the DS correlation ID.

[0172] The first access and mobility node 116 may receive a response from the first session management node 111. The response may indicate that the context has been established. In some examples, the response comprises at least some of the one or more policy rules.

[0173] The first access and mobility node 116 receives 901 a first session establishment request from the UE 121 . The first session establishment request comprises a first SUPI associated with the UE 121 and a DS correlation ID. The first SUPI is associated with a first access.

[0174] The first access and mobility node 116 selects 902 a first session management node 111.

[0175] The first access and mobility node 116 sends 903 a first session context establishment request to the selected first session management node 111. The first session context establishment request comprising the first SUPI and the DS correlation ID.

[0176] Selecting the first session management node 111 may comprise selecting a session management node supporting DS.

[0177] A method according to embodiments herein will now be described from the view of the second access and mobility node 117, together with Figure 10. Figure 10 depicts example embodiments of a method performed by the second access and mobility node 117 for handling DS in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 10.

[0178] Action 1001 The second access and mobility node 117 receives a second session establishment request from the UE 121. The second session establishment request comprises a second SUPI associated with the UE 121 and the DS correlation ID, and optionally an ID of a DS session related to the first SUPI associated with the UE 121 or a parameter indicating that a PDU session related to the first SUPI has been established. The second SUPI is associated with a second access. The DS correlation ID is comprised in an MM part of the request and in an SM container of the request.

[0179] In some embodiments, the second session establishment further comprises an ID of a DS session related to the first SUPI associated with the UE 121 .

[0180] In some embodiments, the second session establishment request comprises a request type parameter indicating request type existing request. In other words, the second session establishment request may indicate that the request is a subsequent request, such as that this is the second session establishment request in a DS session establishment procedure. This may e.g., enable the second access and mobility node 117 to know that session should be part of DS session where a first session has already been established.

[0181] Action 1002

[0182] The second access and mobility node 117 selects a session management node. The selected session management node is the first session management node 111 selected for the DS session by a first access and mobility node 116.

[0183] In some embodiments, selecting the first session management node 111 further comprises subscription data for the UE 121. The subscription data comprises the second DS SUPI. The second DS SUPI indicates the first SUPI associated with the UE 121. The second access and mobility node 117 may further obtain a list of sessions for the UE 121 based on the first SUPI. The list of sessions comprises the DS session. The DS session may be indicated by the correlation ID. The list of sessions may further comprise the ID of the session management node managing the respective sessions.

[0184] In some embodiments, selecting the first session management node 111 further comprises obtaining an identity of the first session management node 111 using the list of sessions and the DS correlation ID. Thus, the DS correlation ID allows the second access and mobility node 117 to select the first session management node 111 , i.e., the same session management node selected by the first access and mobility node 116.

[0185] Action 1003

[0186] The second access and mobility node 117 sends a session context establishment request, such as the third session context establishment request, to the selected first session management node 111. The session context establishment request comprises the second SUPI and the DS correlation ID.

[0187] In some embodiments, the third session context establishment request further comprises the ID of the DS session related to the first SUPI.

[0188] The second access and mobility node 117 receives 1001 a second session establishment request from the UE 121. The second session establishment request comprises a second SUPI associated with the UE 121 , a DS correlation ID and optionally an ID of a DS session related to a first SUPI associated with the UE 121 . The second SUPI is associated with a second access.

[0189] The second access and mobility node 117 selects 1002 session management node 111 , 112. The selected session management node 111 , 112 is any one out of the first session management node 111 or the second session management node 112.

[0190] The second access and mobility node 117 sends 1003 a session context establishment request to a selected session management node 111 , 112. The session context establishment request comprises the second SUPI, the DS correlation ID and optionally the ID of the DS session related to the first SUPI.

[0191] Sending 1003 the session context establishment request may comprise sending the second context establishment request to the second session management node 112, or sending the third session context establishment request to the first session management node 111.

[0192] In some embodiments, selecting 1002 the session management node 111 , 112 comprises obtaining 802, using the second DS SUPI, indicated in subscription data, , an ID of the first session management node 111 related to the DS session associated with the second DS SUPI. The second DS SUPI is associated with the second SUPI and / or the UE 121 . The second DS SUPI indicates the first SUPI associated with the UE 121 .

[0193] A method according to embodiments herein will now be described from the view of the UE 121 , together with Figure 11. Figure 11 depicts example embodiments of a method performed by the UE 121 for handling DS in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 11 .

[0194] Action 1101

[0195] The UE 121 sends a first session establishment request to the first access and mobility node 116. The first session establishment request comprises the first SUPI associated with the UE 121 and the DS correlation ID. The first SUPI is associated with the first access. The DS correlation ID is comprised in an first part of the request and in a second part of the request.

[0196] In some embodiments, the first part of the request comprises an MM part of the message, and the second part comprises an SM container.

[0197] The DS correlation ID may, as mentioned above, be used to connect, such as associate, sessions or session requests, such as PDU sessions or PDU session requests. The DS correlation ID may e.g., be added to UE context in SMF data in UDM / UDR, such as the user data node 114. Thus, the DS correlation ID may identify the DS session, and / or correlate a first session and a second session in the DS session.

[0198] In some embodiments, the first session establishment request is a DS session establishment request. The DS session establishment request indicates that a session management node supporting DS is to be selected.

[0199] In some embodiments, the first session establishment request comprises a request type parameter indicating request type initial request. In other words, the first session establishment request may indicate that the request is an initial request, such as that this is the first session establishment request in a DS session establishment procedure.

[0200] Action 1102

[0201] The UE 121 sends a second session establishment request to the second access and mobility node 117. The second session establishment request comprises the second SUPI associated with the UE 121 and a DS correlation ID. The second SUPI is associated with a second access different from the first access. , wherein the DS correlation ID is comprised, such as contained or included, in a first part of the request and in a second part of the request.

[0202] In some embodiments, the first part of the request comprises an MM part of the message, and the second part comprises an SM container.

[0203] In some embodiments, the second session establishment request comprises a request type parameter indicating request type existing session, such as existing PDU session. In other words, the second session establishment request may indicate that the request is a subsequent request, such as that this is the second session establishment request in a DS session establishment procedure. This may e.g., enable the second access and mobility node 117 to know that the session should be part of DS session where a first session has already been established.

[0204] The UE 121 sends 1101 a first session establishment request to the first access and mobility node 116. The first session establishment request comprises the first SUPI associated with the UE 121 and a DS correlation ID. The first SUPI is associated with a first access.

[0205] The UE 121 sends 1102 a second session establishment request to the second access and mobility node 117. The second session establishment request comprises a second SUPI associated with the UE 121 , a DS correlation ID and optionally an ID of the DS session related to the first SUPI. The second SUPI is associated with a second access different from the first access.

[0206] A method according to embodiments herein will now be described from the view of the policy control node 113, together with Figure 12a. Figure 12a depicts example embodiments of a method performed by the policy control node 113 for handling DS in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 12a.

[0207] Action 1201

[0208] The policy control node 113 establishes a policy association with the first session management node 111 for a DS session by receiving a request from the first session management node 111. The request comprising a first SUPI and a first DS SUPI. The establishing comprises creating one or more policy rules, taking the first SUPI and the and the first DS SUPI into account.

[0209] In some embodiments, the one or more policy rules comprises any one or more out of a URSP rule, a PCC rule and an ATSSS rule.

[0210] In some embodiments, the URSP rule comprises a DS indication, the PCC rule comprises an access descriptor, which access descriptor indicates an access type, such as the first access, and / or the ATSSS rule comprises an access descriptor, which access descriptor indicates an access type, such as the first access.

[0211] Action 1202

[0212] The policy control node 113 provides the one or more policy rules for the DS session to the first session management node 111.

[0213] The policy node 113 may e.g., provide the one or more policy rules to the first session management node 111 by sending the one or more policy rules to the first session management node 111.

[0214] Action 1203

[0215] The policy control node 113 updates the policy association with the first session management node 111 for the DS session by receiving a request, such as policy association modification request, from the first session management node 111. The request comprises the second SUPI and the second DS SUPI. The updating comprises updating the one or more policy rules, taking the second SUPI and the and the second DS SUPI into account.

[0216] In some embodiments, updating the policy association comprises updating any one or more of the URSP rule, PCC rule and ATSSS rule.

[0217] In some embodiments, updating the PCC rule and / or ATSS rule comprises adding an access type, such as the second access, associated with the second SUPI.

[0218] Action 1204

[0219] The policy control node 113 provides 1204 the one or more policy rules for the DS session to the first session management node 111.

[0220] The policy node 113 may e.g., provide the one or more updated policy rules to the first session management node 111 by sending the one or more updated policy rules to the first session management node 111.

[0221] The policy control node 113 establishes 1201 a policy association with the first session management node 111 for a DS session by receiving a request from the first session management node 111. The request comprising a first SUPI and a first DS SUPI. The establishing comprises creating one or more policy rules, taking the first SUPI and the and the first DS SUPI into account,

[0222] The policy control node 113 provides 1202 the one or more policy rules for the DS session to the first session management node 111.

[0223] The policy control node 113 updates 1203 the policy association with the first session management node 111 for the DS session by receiving a request from the first session management node 111. The request comprises the second SUPI and the second DS SUPI. The updating comprises updating the one or more policy rules, taking the second SUPI and the and the second DS SUPI into account.

[0224] The policy control node 113 provides 1204 the one or more policy rules for the DS session to the first session management node 111.

[0225] A method according to embodiments herein will now be described from the view of the user data node 114, together with Figure 12b. Figure 12b depicts example embodiments of a method performed by the user data node 114 for handling DS in the wireless communication network 100. The method comprises the following actions, which actions may be taken in any suitable order. Actions that are optional are presented in dashed boxes in Figure 12b. Action 1301

[0226] The user data node 114 provides subscription data associated with the first SUPI and / or the UE 121 to the first session management node 111. The subscription data comprises the first DS SUPI indicating the second SUPI associated with the UE 121 .

[0227] In some embodiments, providing the subscription data comprises receiving a request from the first session management node 111 and sending the subscription data to the first session management node 111. The request comprises the first SUPI associated with the UE 121.

[0228] In some embodiments, the subscription data comprises session management subscription data associated with the first SUPI and / or the UE 121. The subscription data comprises the first SUPI and the first DS SUPI.

[0229] Action 1302

[0230] The user data node 114 registers the DS session by receiving a registration message indicating the DS correlation ID from the first session management node 111.

[0231] In some embodiments, registering the DS session comprises registering the DS correlation ID in a UE context associated with the first SUPI and / or the UE 121. Registering the DS session may further comprise associating the DS session with the DS correlation ID.

[0232] Action 1303

[0233] In some embodiments, the user data node 114 provides subscription data and a list of sessions for the UE 121 to a second access and mobility node 117 or the second session management node 112. The subscription data comprises the second DS SUPI associated with the second SUPI and / or the UE 121. The second DS SUPI indicates the first SUPI associated with the UE 121 . The list of sessions is provided based on the first SUPI.

[0234] In some embodiments, providing the subscription data for the UE (121) comprises receiving a request from the first access and mobility node 117 or the second session management node 112 to obtain the subscription data and sending the subscription data to the second access and mobility node 117 or the second session management node 112. The request comprises the second SUPI. Providing the list of sessions comprises receiving a request from the second access and mobility node 117 and sending the list of sessions to the second access and mobility node 117 or the second session management node 112. The request for the list of sessions comprises the first SUPI. In some embodiments, the subscription data provided to the second access and mobility node 117 comprises access and mobility subscription data associated with the second SUPI and / or the UE 121.

[0235] In some embodiments, the subscription data provided to the second session management node 112 comprises session management subscription data associated with the second SUPI and / or the UE 121.

[0236] Action 1304

[0237] In some embodiments, the user data node 114 provides subscription data associated with the second SUPI and / or the UE 121 to the first session management node 111. The subscription data comprises the second DS SUPI indicating the first SUPI associated with the UE 121 .

[0238] In some embodiments, providing the subscription data comprises receiving a request from the first session management node 111 and sending the subscription data to the first session management node 111. The request comprises the second SUPI associated with the UE 121 .

[0239] In some embodiments, the subscription data comprises session management subscription data associated with the second SUPI and / or the UE 121. The subscription data comprises the second SUPI and the second DS SUPI.

[0240] Embodiments herein such as the embodiments mentioned above will now be further described and exemplified. The text below is applicable to embodiments herein and may be combined with any suitable embodiment described above.

[0241] Different aspects of the subject matter will be further explained in different sections, namely registration, policy and session management.

[0242] Registration

[0243] Alt 1: No AMF impact: There is no impact on the registration procedure.

[0244] Alt 2: Limited AMF impact: The AMF may indicate, e.g., visited, network’s support for DS PDU session using a new parameter, Support for DS, in the initial Registration Accept message to a UE in step 21 of Figure 4.2.2.2.2-1 of 3GPP TS 23.502 v18.3.0.

[0245] Policy

[0246] This section applies for both alternatives, Alt 1 and Alt 2 above. URSP Rules’. To support establishment of a DS PDU session, the URSP rules for DS are extended. Specifically, the Access Type preference in Route Selection Descriptor is extended to include a Dual Steering indication.

[0247] PCC rules’. For DS, the Study scope excludes data splitting, and therefore, the allowed steering modes are Active-Standby and Smallest Delay (steering mode for data splitting (Active-Active) may be added in the future). For the Active-Standby mode, the Access type and connected PLMNs may be important. Therefore, the MA PDU session Control part of the PCC rules is enhanced as follows, and shown in underlined italic in table 2.7.1.2-1 below: - A new field Access descriptor is added to PCC rules, which includes a 4-tuples

[0248] (Access 1 -type, Access1-PLMN-ID, Access2-type, Access2-PLMN-ID), identifying Accessl and Access2. The access type maybe one of the following: T-NR, GEO, LEO, LTE, non-3GPP, other.

[0249] - The fields charging / monitoring key for Non-3GPP access is extended to include charging / monitoring key for Access2.

[0250] Table 2.7.1.2-1 : Enhancement on the PCC rule for Dual Steering

[0251] The PCF should subscribe to changes of RAT, Access Type, and PLMN to SMF for both SUPI1 and SUPI2 and it may update the PCC rules based on the notifications.

[0252] ATSSS Rules’. To enforce DS policies in the UL direction, the ATSSS rules are enhanced with a new Access Descriptor parameter. This is the same 4-tuple as described in Table 6.1.Y.1.4-1 and guides the DS device to identify which one of the accesses is Accessl and which one is Access2, and is shown in Table 2.7.1.2-2 in underlined italic below.

[0253] Tab e 2.7.1.2-2: ATSSS rule structure to support DS

[0254] N4 Rules (re-using current standards): The same mechanism for MA PDU session can be implemented for DS PDU session, i.e., the SMF generates two FARs that direct the traffic to the two accesses and one MAR that points to one of the FARs depending on whether the Active path is chosen for downlink traffic or the standby one (in the Active- Standby mode).

[0255] Based on the impact on AMF two alternatives are considered for creating DS PDU session. Alt1: No AMF impact

[0256] The steps below are shown in Figure 13.

[0257] Steps 1 : UE1 registers to 5GC through AMF1 using SUPI1 and receives DS URSP rules.

[0258] Step 2. UE1 sends PDU Session Establishment request with Request Type initial request, using SUPI1 and includes in the N1 SM container a new parameter, DS Correlation ID. The DS Correlation ID is generated by the DS device and should uniquely identify the DS PDU Session across both UEs.

[0259] Step 3. The AMF selects the SMF1 according to the current specifications. Here, homogenous implementation of the DS is assumed for all SMFs that support the requested DNN / S-NSSAI. Therefore, AMF does not take into consideration the capability of SMF to support DS.

[0260] Step 4: AMF sends a Nsmf_PDUSession_CreateSMContext request to the SMF1 .

[0261] Step 5. SMF1 retrieves the SM subscription data from the User Data Management (UDM) which includes a new parameter, DS SUPI containing SUPI2. SMF associates the DS PDU session to both SUPI1 and SUPI2.

[0262] Step 6. SMF1 establishes a SM Policy Association and in addition to SUPI1 includes the DS SUPI (SUPI2) in the request. The PCF associates the SM policy association to both SUPI1 and SUPI2. The PCF provides the PCC rules for DS PDU session.

[0263] Step 7. The SMF1 establishes an N4 session with the UPF. SMF generates N4 rules similarly as for a MA PDU Session.

[0264] Step 8. SMF Registers the PDU Session with UDM. In addition, it registers the DS Correlation ID as new field in the UE context in SMF data.

[0265] Step 9: If the DS device is not already registered with SUPI2 through a second access, it registers in this step and receives DS URSP rules.

[0266] Editor's note: How step 9 is triggered is assumed to be addressed by other solutions.

[0267] Step 10: This step is the same as step 2 with a new parameter in SM container. Existing DS PDU, which indicates that the PDU session for SUPI1 has been already created. The DualSteer device sends the same DS Correlation ID and the same DNN / S- NSSAI as in step 2.

[0268] Step 11 . AMF2 selects an SMF (SMF2) based on current mechanisms.

[0269] Step 12. AMF sends a Nsmf_PDUSession_CreateSMContext request to the SMF2. In this step, SMF2 checks if there exist a PDU Session corresponding to SUPI2 and the DS Correlation ID. If yes, then steps 13-16 are skipped (SMF2 and SMF1 are the same).

[0270] Step 13. SMF2 obtains the subscription data for SUPI2, which includes DS SUPI (containing SUPI1).

[0271] Step 14: SMF uses SUPI1 to get the list of PDU Sessions from UDM and then using DS Correlation ID obtains the SMF ID of SMF1 .

[0272] Step 15: SMF sends a redirection response to AMF and provides SMF1 ID

[0273] Step 16-: Similarly as in Step 4.

[0274] Step 17: Similarly as in Step 5

[0275] Step 18: SMF triggers SM policy association update request to update the policy information for the PDU Session and includes DS SUPI (SUPI1). PCF may modify the PCC rules based on the access type and PLMN of the SUPI2.

[0276] Step 19: SMF modifies the N4 rules so that an additional N3 / N9 tunnel is established between the second access and the UPF.

[0277] Step 20. The same as steps 11-21 of figure 4.3.2.2.1-1 of 3GPP TS 23.502 v18.3.0, with the difference that in step 16c the SMF includes DS Correlation ID in the registration of the PDU session as in step 8.

[0278] Alt2: Limited AMP impact

[0279] The steps below are shown in Figure 14.

[0280] Step 1 : UE1 registers to 5GC through AMF1 using SUPI1 and receives DS URSP rules.

[0281] Step 2: UE1 sends a PDU Session Establishment Request of type initial request and includes the DS Correlation ID in the MM part of the NAS message, as well as in the SM container.

[0282] Step 3: AMF selects an SMF that supports the DS functionality.

[0283] Step 4: See steps 4-9 described above with reference to Figure 13.

[0284] Step 5: UE2 sends a PDU Session Establishment Request of type Existing PDU Session and includes the DS Correlation ID in the MM part of the NAS message, as well as in the SM container. There is no need for Existing DS PDU parameter since existing PDU session is chosen for the request type.

[0285] • Step 6: AMF2 uses the DS SUPI field in the Access and Mobility Subsciption data to discover SUPI1 and uses it to get the list of PDU Sessions from UDM1 . Then by using DS Correlation ID it obtains the SMF ID of SMF1 .

[0286] • Step 7: See steps 16-20 described above with reference to Figure 13. The SMF redirection steps (steps 12-15) are skipped since AMF2 selects SMF1 directly.

[0287] As an embodiment, in the PDU Session Establishment request above, a new request type, DS Session request may be used.

[0288] Proposed changes to ??

[0289] 6 Solutions

[0290] 6.0 Mapping of Solutions to Key Issues, changes in underlined italic.

[0291] Table 6.0-1 : Mapping of DualSteer Solutions to Key Issues

[0292] Table 6.0-2: Mapping of ATSSS_Ph4 Solutions to Key Issues

[0293] 6.1 .Y Solution # 1 .Y: Supporting dual-steer connection via ATSSS

[0294] 6.1.Y.1 Overall Description

[0295] 6.1.Y.1.1 Introduction

[0296] The proposed solution is based on the following principles: • The impact to AMF is either zero or minimal. This enables the DS functionality when only the HPLMN supports the DS functionality and the VPLMN can either remain unchanged or need to make minimal enhancements to the AMF. Here, we propose two alternatives: o Alt 1 : No AMF impact: this alternative is based on SMF redirection and needs homogeneous implementation of SMFs that support DS for a DNN / S-NSSAI. o Alt2: Limited AMF impact: this alternative enables non-homogeneous implementation of SMFs that support DS.

[0297] • The solution treats the two SUPIs identically, e.g., either of two SUPIs can be used to first register or request the PDU session establishment.

[0298] • The solution considerers the DS device to act as either one or two UEs towards the network but does not discuss the UE architecture. The requirements on the DS device are listed in the impact section.

[0299] • The traffic switching and steering is based on ATSSS functionality with a common SMF and UPF.

[0300] • UPF treats the DS PDU session in the same manner as an MA PDU session. However, establishment and management of the DS PDU Session is different than that of the MA PDU session.

[0301] 6.1.Y.1.2 Architectures

[0302] This solution is based on providing a common anchor (UPF) and SMF inside the 5GC for the DS traffic from both 3GPP access networks. Non-roaming and roaming architectures are shown below.

[0303] Figure 15 shows a non-roaming dual steering architecture

[0304] Figure 16 shows a dual steering architecture with roaming in one access

[0305] Figure 17 shows a dual steering architecture with roaming in both accesses with common VPLMN

[0306] Figure 18 shows a dual steering architecture with roaming in both accesses with two different VPLMNs 6.1.Y.1.3 Registration

[0307] Alt 1 : No AMF impact: It has no impact on the registration procedure.

[0308] Alt 2: Limited AMF impact: The AMF may indicate (visited) network’s support for DS PDU session in the initial Registration Accept message to UE.

[0309] 6.1.Y.1.4 Policy

[0310] URSP Rules: To support establishment of DS PDU session, the URSP rules are extended. Specifically, the Access Type preference in Route Selection Descriptor is extended to include a Dual Steering indication.

[0311] PCC rules: Considering that data splitting is not supported, the allowed steering modes are Active-Standby and Smallest Delay. For the Active-Standby mode, the Access type and connected PLMNs can be important. Therefore, the MA PDU session Control part of the PCC rules is enhanced as follows:

[0312] - A new field Access descriptor is added to PCC rules, which includes a 4-tuples (Access 1 -type, Access'! -PLMN-ID, Access2-type, Access2-PLMN-ID), identifying Access'! and Access2. The access type may be one of the following: T-NR, GEO, LEO, LTE, non-3GPP, other.

[0313] - The fields charging / monitoring key for Non-3GPP access is extended to include charging / monitoring key for Access2.

[0314] Table 6.1.Y.1.4-1 : Enhancement on the PCC rule for Dual Steering

[0315] The PCF should subscribe to changes of RAT, Access Type, and PLMN to SMF for both SUPI1 and SUPI2 and it may update the PCC rules based on the notifications.

[0316] ATSSS Rules: To enforce DS policies in the UL direction, the ATSSS rules are enhanced with a new Access Descriptor parameter. This is the same 4-tuple as described in Table 6.1.Y.1.4-1 and guides the DS device to identify which one of the accesses is Accessl and which one is Access2.

[0317] Table 6.1.Y.1.4-2: ATSSS rule structure to support DS

[0318] N4 Rules: The same mechanism for MA PDU session can be implemented for DS PDU session, i.e., the SMF generates two FARs that direct the traffic to the two accesses and one MAR that points to one of the FARs depending on whether the Active path is chosen for downlink traffic or the standby one (in the Active-Standby mode).

[0319] Note: how to guide DS device to connect to additional 3GPP access is assumed to be covered by other solution

[0320] 6.1. Y.1.5 Subscription and UE context data in UDM / UDR The connection between the two SUPIs is maintained in UDM. For this purpose, a new field, DS SUPI, is added in the Session Management Subscription Data for both SUPI1 (containing SUPI2) and SUPI2 (containing SUPI1). In addition, for alternative 2, the same field is also added to the Access and Mobility Subscription Data for both SUPIs.

[0321] A new parameter, DS Correlation ID, which is used to connect two PDU session requests (see clause 6.1 .Y.1 .7) is added to UE context in SMF data in UDM / UDR. How these new parameters are used is described on the procedures below. 6.1. Y.1.6 Session management

[0322] This solution is based on creating a DS PDU session that is anchored in a common UPF and managed by a common SMF. To achive this:

[0323] • Two separate PDU session Establishment requests are sent by the UE (one for each SUPI).

[0324] • In the PDU session Establishment requests, UEs provides a new parameter (DS Correlation ID) to enable identifying which two PDU session requests correspond to the same DS PDU session.

[0325] • Both AMFs select the same (H-)SMF. To achieve these two alternatives are presented: o Alt1 : No AMF impact: Selection of common SMF is done via HPTT redirect, request by the SMF. o Alt2: Limited AMF impact: Selection of common SMF is done via DS Correlation ID matching by AMF

[0326] 6.1.Y.2 Procedure

[0327] 6.1.Y.2.1 Session management

[0328] Based on the impact on AMF two alternatives are considered for creating DS PDU session.

[0329] Note: in this section we consider two separate UDMs to manage the subscription data of SUPI1 and SUPI2, however, as an alternative, since both UDMs belong to the HPLMN, it can be assumed that the subscription data of both SUPIs are managed in a single UDM.

[0330] Alt1: No AMF impact:

[0331] Figure 19 shows Dual steering PDU Session Establishment according to Alt1

[0332] Steps 1 : UE1 registers to 5GC through AMF1 using SUPI1 and receives DS URSP rules. Step 2. UE1 sends PDU Session Establishment request with Request Type initial request, using SUPI1 and includes in the N1 SM container a new parameter, DS Correlation ID. The DS Correlation ID is generated by the DS device and should uniquely identify the DS PDU Session across both UEs. Step 3. The AMF selects the SMF1 according to the current specifications. Here, homogenous implementation of the DS is assumed for all SMFs that support the requested DNN / S-NSSAI. Therefore, AMF does not take into consideration the capability of SMF to support DS.

[0333] Step 4: AMF sends a Nsmf_PDUSession_CreateSMContext request to the SMF 1 .

[0334] Step 5. SMF1 retrieves the SM subscription data from UDM which includes a new parameter, DS SUPI containing SUPI2. SMF associates the DS PDU session to both SUPI1 and SUPI2.

[0335] Step 6. SMF1 establishes a SM Policy Association and in addition to SUPI1 includes the DS SUPI (SUPI2) in the request. The PCF associates the SM policy association to both SUPI1 and SUPI2.. The PCF provides the PCC rules for DS PDU session.

[0336] Step 7. The SMF1 establishes an N4 session with the UPF. SMF generates N4 rules similarly as for a MA PDU Session.

[0337] Step 8. SMF Registers the PDU Session with UDM. In addition, it includes the DS Correlation ID as new parameter in the registration request.

[0338] Step 9: If the DS device is not already registered with SUPI2 through a second access, it registers in this step and receives DS URSP rules.

[0339] Editor's note: How step 9 is triggered is assumed to be addressed by other solutions.

[0340] Step 10: This step is the same as step 2 with a new parameter in SM container, Existing DS PDU, which indicates that the PDU session for SUPI1 has been already created. . The DualSteer device sends the same DS Correlation ID and the same DNN / S-NSSAI as in step 2.

[0341] Step 11 . AMF2 selects an SMF (SMF2) based on current mechanisms.

[0342] Step 12. AMF sends a Nsmf_PDUSession_CreateSMContext request to the SMF2. In this step, SMF2 checks if there exist a PDU Session corresponding to SUPI2 and the DS Correlation ID. If yes, then steps 13-16 are skipped (SMF2 and SMF1 are the same).

[0343] Step 13. SMF2 obtains the subscription data for SUPI2, which includes DS SUPI (containing SUPI1).

[0344] Step 14: SMF2 uses SUPI1 to get the list of PDU Sessions from UDM and then using DS Correlation ID obtains the SMF ID of SMF1 .

[0345] Step 15: SMF sends a redirection response to AMF and provides SMF1 ID Step 16-: Same as Step 4.

[0346] Step 17: Similarly as in step 5. Step 18: SMF triggers SM policy association update request to update the policy information for the PDU Session and includes DS SUPI (SUPI1). PCF may modify the PCC rules based on the access type and PLMN of the SUPI2.

[0347] Step 19: SMF modifies the N4 rules so that an additional N3 / N9 tunnel is established between the second access and the UPF.

[0348] Step 20. The same as steps 11-21 of figure 4.3.2.2.1-1 of TS 23.502 [4], with the difference that in step 16c the SMF includes DS Correlation ID in the registration of the PDU session as in step 8.

[0349] Alt2: Limited AMF impact:

[0350] Figure 20 shows Dual steering PDU Session Establishment according to Alt2

[0351] • Stepl : UE1 registers to 5GC through AMF1 using SUPI1 and receives DS URSP rules.

[0352] • Step2: UE1 sends a PDU Session Establishment Request of type initial request and includes the DS Correlation ID in the MM part of the NAS message, as well as in the SM container.

[0353] • Step 3: AMF selects an SMF that supports the DS functionality.

[0354] • Step 5: UE2 sends a PDU Session Establishment Request of type Existing PDU Session and includes the DS Correlation ID in the MM part of the NAS message, as well as in the SM container. There is no need for Existing DS PDU parameter since existing PDU session is chosen for the request type.

[0355] • Step 6: AMF2 uses the DS SUPI filed in the Access and Mobility Subscription data to discover SUPI1 and gets the UE context in SMF data for SUPI1 from UDM and selects SMF1 based on DS Correlation ID.

[0356] • Step 7: The SMF redirection steps (steps 12-15) are skipped since AMF2 selects SMF1 directly.

[0357] 6.1. Y.2.2 Interworking with EPS:

[0358] To enable interworking with EPS the same mechanism as in Figure 6.1 .Y.2.1-1 are followed with the following differences: • In addition to registering the PDU Session for SUPI1 in step 8 of Figure 6.1 .Y.2.1- 1 , SMF1 +PGW-C1 registers the PDU Session for SUPI2 in HSS.

[0359] • In Step 11 of Figure 6.1.Y.2.1-1 , the MME selects SMF1+PGW-C1 directly according to current specification since the PDU Session is registered for SUPI2 with the same DNN / APN. Therefore, the SMF redirection steps in Alt1 (steps 12- 15) are skipped.

[0360] 6.1.Y.4lmpacts

[0361] DS device: Should register with two separate SUPIs, should handle the ATSSS functionality (steering and switching) across two PDU session associated with two SUPIs. Should be able to provide a unique DS correlation ID in the N1 SM container in the PDU Session Establishment requests for both SUPIs.

[0362] AMF: No impact for Alt1. For Alt2: Selecting SMF with DS capability, Selecting SMF based on DS Correaltion ID. S Providing indication of support for DS PDU session in initial Registration Accept message.

[0363] UPF: No impact. Existing support for MA PDU Sessions is re-used.

[0364] SMF: Invoking HTTP redirect upon receiving a PDU Session Establishment request (Alt1). Creating N4 rules and ATSSS rules for DS PDU session.

[0365] UDM / UDR: Adding a new parameter, DS SUPI, to UE SM subscription data. Adding a new parameter to PDU Session context, DS Correlation ID.

[0366] PCF: Creating PCC rules with DualSteer information.

[0367] To perform the method actions above, the first session management node 111 , configured to handle DS in the wireless communication network 100. The first session management node 111 may comprise an arrangement depicted in Figure 21.

[0368] The first session management node 111 may comprise an input and output interface 2100 configured to communicate with each other. The input and output interface2100 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown). The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 2110 of a processing circuitry in the first session management node 111 depicted in Figure 11 , together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first session management node 111. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first session management node 111.

[0369] The first session management node 111 and or the processor 2110 is e.g., configured to handle DS, in the wireless communication network (100).

[0370] The first session management node 111 and / or processor 2110 is configured to receive a first session context establishment request for establishing a DS session. The first session context establishment request comprises a first SUPI associated with the UE 121 and a DS correlation ID. The first SUPI is associated with a first access.

[0371] The first session management node 111 and or the processor 2110 is configured to establish a context for the DS session using the first SUPI, the DS correlation ID and a first DS SUPI associated with the first SUPI and / or the UE 121. The first DS SUPI indicating a second SUPI associated with the UE 121.

[0372] The first session management node 111 and / or processor 2110 is configured to request a policy association to be established by sending a policy association establishment request to a policy control node 113. The request is adapted to comprise the first SUPI and the first DS SUPI.

[0373] The first session management node 111 and or the processor 2110 is configured to receive a third session context establishment request for establishing the DS session, the third session context establishment request comprising the second SUPI associated with the UE (121) and the DS correlation ID and optionally an ID of a DS session associated with the first SUPI. The second SUPI is associated with a second access different from first access.

[0374] The first session management node 111 and or the processor 2110 is configured to update the context for the DS session using the second SUPI, the DS correlation ID and a second DS SUPI associated with the second SUPI and / or the UE (121). The first session management node 111 and / or processor 2110 is configured to update the policy association by sending a policy association modification request to a policy control node 113. The request is adapted to comprise the second SUPI and the second DS SUPI.

[0375] In some embodiments, the first DS SUPI is adapted to indicate the second SUPI, and the second DS SUPI is adapted to indicate the first SUPI.

[0376] In some embodiments, the DS correlation ID is adapted to identify the DS session.

[0377] In some embodiments, the first session context establishment request is adapted to comprise a request type parameter indicating request type initial request.

[0378] In some embodiments, to establish the context is adapted to comprise to obtain subscription data for the UE 121. The subscription data is adapted to comprise the DS SUPI.

[0379] In some embodiments, to establish the context is adapted to comprise to associate the DS session with the first SUPI and the second SUPI indicated in the DS SUPI.

[0380] In some embodiments, the first session management node 111 and / or processor 2110 is configured to register the DS session in a user data node 114 by sending a registration message indicating the DS correlation ID to the user data node 114.

[0381] In some embodiments, the registration is further adapted to register the DS correlation ID in a UE context associated with the UE (121) in the user data node (114).

[0382] The first session management node 111 may further comprise respective a memory 2120 comprising one or more memory units. The memory 2120 comprises instructions executable by the processor 2110 in the first session management node 111.

[0383] The memory 2120 is arranged to be used to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, flows, policies, session SUPIs, IDs and applications to perform the methods herein when being executed in the first session management node 111.

[0384] In some embodiments, a computer program 2130 comprises instructions, which when executed by the at least one processor 2110, cause the at least one processor 2110 of the first session management node 111 to perform the actions above.

[0385] In some embodiments, a respective carrier 2140 comprises the respective computer program 2130, wherein the carrier 2140 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0386] Thus, embodiments herein may disclose the first session management node 111 configured to handle DS in the wireless communications network 100. The first session management node 111 comprises the processor 2110 and the memory 2120, said memory 2120 comprising instructions executable by said processor 2110 whereby said first session management node 111 is operative to perform any of the methods herein.

[0387] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.

[0388] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0389] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0390] To perform the method actions above, the second session management node 112, configured to handle DS in the wireless communication network 100. The second session management node 112 may comprise an arrangement depicted in Figure 22.

[0391] The second session management node 112 may comprise an input and output interface 2200 configured to communicate with each other. The input and output interface 2200 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0392] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 2210 of a processing circuitry in the second session management node 112 depicted in Figure 11 , together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the second session management node 112. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the second session management node 112.

[0393] The second session management node 112 and or the processor 2210 is e.g., configured to handle DS in the wireless communication network (100).

[0394] The second session management node 112 and or the processor 2210 is configured to receive, from a second access and mobility node (117), a second session context establishment request for establishing a DS session. The second session context establishment request comprising a second SUPI associated with the UE (121), a DS correlation ID and optionally an ID of a DS session related to a first SUPI associated with the UE (121). The second SUPI is associated with a second access.

[0395] The second session management node 112 and or the processor 2210 is configured to obtain, using the DS correlation ID and a second DS SUPI, an ID of a first session management node (111) related to a DS session associated with the second DS SUPI. The second DS SUPI is associated with the second SUPI and / or the UE (121). The second DS SUPI indicates the first SUPI associated with the UE (121). The second session management node 112 and or the processor 2210 is configured to request the DS session to be redirected to the first session management node (111) by sending a redirection message to the second access and mobility node (117). The redirection message comprising the ID of the first session management node (111).

[0396] The second session management node 112 may further comprise respective a memory 2220 comprising one or more memory units. The memory 2220 comprises instructions executable by the processor 2210 in the second session management node 112.

[0397] The memory 2220 is arranged to be used to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, flows, policies, session SUPIs, IDs and applications to perform the methods herein when being executed in the second session management node 112.

[0398] In some embodiments, a computer program 2230 comprises instructions, which when executed by the at least one processor 2210, cause the at least one processor 2210 of the second session management node 112 to perform the actions above.

[0399] In some embodiments, a respective carrier 2240 comprises the respective computer program 2230, wherein the carrier 2240 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0400] Thus, embodiments herein may disclose the second session management node 112 configured to handle DS in the wireless communications network 100. The second session management node 112 comprises the processor 2210 and the memory 2220, said memory 2220 comprising instructions executable by said processor 2210 whereby said second session management node 112 is operative to perform any of the methods herein.

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

[0402] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0403] To perform the method actions above, the first access and mobility node 116, configured to handle DS in the wireless communication network 100. The first access and mobility node 116 may comprise an arrangement depicted in Figure 23.

[0404] The first access and mobility node 116 may comprise an input and output interface 2300 configured to communicate with each other. The input and output interface 2300 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0405] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 2310 of a processing circuitry in the first access and mobility node 116 depicted in Figure 23, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the first access and mobility node 116. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the first access and mobility node 116.

[0406] The first access and mobility node 116 and / or processor 2310 is configured to receive a first session establishment request from the UE 121 . The first session establishment request comprises a first SUPI associated with the UE 121 and a DS correlation ID. The first SUPI is associated with a first access. The DS correlation ID is comprised in an MM part of the request and in an SM container of the request.

[0407] The first access and mobility node 116 and / or processor 2310 is configured to select a first session management node 111.

[0408] The first access and mobility node 116 and / or processor 2310 is configured to send a first session context establishment request to a selected first session management node 111. The first session context establishment request is adapted to comprise the first SUPI and the DS correlation ID.

[0409] In some embodiments, to select the first session management node 111 is adapted to comprise to select a session management node supporting DS.

[0410] In some embodiments, the first session establishment request is a DS session establishment request. The DS session establishment request indicates that a session management node supporting DS is to be selected.

[0411] The first access and mobility node 116 may further comprise respective a memory 2320 comprising one or more memory units. The memory 2320 comprises instructions executable by the processor 2310 in the first access and mobility node 116.

[0412] The memory 2320 is arranged to be used to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, flows, policies, session SUPIs, IDs and applications to perform the methods herein when being executed in the first access and mobility node 116.

[0413] In some embodiments, a computer program 2330 comprises instructions, which when executed by the at least one processor 2310, cause the at least one processor 2310 of the first access and mobility node 116 to perform the actions above. In some embodiments, a respective carrier 2340 comprises the respective computer program 2330, wherein the carrier 2340 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0414] Thus, embodiments herein may disclose the first access and mobility node 116 configured to handle DS in the wireless communications network 100. The first access and mobility node 116 comprises the processor 2310 and the memory 2320, said memory 2320 comprising instructions executable by said processor 2310 whereby said first access and mobility node 116 is operative to perform any of the methods herein.

[0415] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.

[0416] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0417] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0418] To perform the method actions above, the second access and mobility node 117, configured to handle DS in the wireless communication network 100. The second access and mobility node 117 may comprise an arrangement depicted in Figure 24.

[0419] The second access and mobility node 117 may comprise an input and output interface 2400 configured to communicate with each other. The input and output interface 2400 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0420] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 2410 of a processing circuitry in the second access and mobility node 117 depicted in Figure 24, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the second access and mobility node 117. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the second access and mobility node 117.

[0421] The second access and mobility node 117 and / or processor 2410 is configured to receive a second session establishment request from the UE 121. The second session establishment request is adapted to comprise a second SUPI associated with the UE 121 and a DS correlation ID. The second SUPI is associated with a second access. The DS correlation ID is adapted to be comprised in an MM part of the request and in an SM container of the request.

[0422] The second access and mobility node 117 and / or processor 2410 is configured to select session management node. The selected session management node is adapted to be a first session management node 111 selected for the DS session by a first access and mobility node 116.

[0423] The second access and mobility node 117 and / or processor 2410 is configured to send a session context establishment request to the selected first session management node 111. The session context establishment request comprises the second SUPI and the DS correlation ID.

[0424] In some embodiments, the first session management node 111 is selected based on a second DS SUPI and the DS correlation ID.

[0425] In some embodiments, to select the first session management node 111 is further adapted to comprise to obtain subscription data for the UE 121. The subscription data is adapted to comprise the second DS SUPI. The second DS SUPI is adapted to indicate a first SUPI associated with the UE 121 .

[0426] In some embodiments, to select the first session management node 111 is further adapted to comprise to obtain a list of sessions for the UE 121 based on the first SUPI.

[0427] In some embodiments, to select the first session management node 111 is further adapted to comprise to obtain an identity of the first session management node 111 using the list of sessions and the DS correlation ID.

[0428] The second access and mobility node 117 may further comprise respective a memory 2420 comprising one or more memory units. The memory 2420 comprises instructions executable by the processor 2410 in the second access and mobility node 117.

[0429] The memory 2420 is arranged to be used to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, flows, policies, session SUPIs, IDs and applications to perform the methods herein when being executed in the second access and mobility node 117.

[0430] In some embodiments, a computer program 2430 comprises instructions, which when executed by the at least one processor 2410, cause the at least one processor 2410 of the second access and mobility node 117 to perform the actions above.

[0431] In some embodiments, a respective carrier 2440 comprises the respective computer program 2430, wherein the carrier 2440 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0432] Thus, embodiments herein may disclose the second access and mobility node 117 configured to handle DS in the wireless communications network 100. The second access and mobility node 117 comprises the processor 2410 and the memory 2420, said memory 2420 comprising instructions executable by said processor 2410 whereby said second access and mobility node 117 is operative to perform any of the methods herein.

[0433] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.

[0434] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0435] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure. To perform the method actions above, the UE 121 , configured to handle DS in the wireless communication network 100. The UE 121 may comprise an arrangement depicted in Figure 25.

[0436] The UE 121 may comprise an input and output interface 2500 configured to communicate with each other. The input and output interface 2500 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0437] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 2510 of a processing circuitry in the UE 121 depicted in Figure 25, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the UE 121 . One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the UE 121.

[0438] The UE 121 and / or processor 2510 is configured to send a first session establishment request to a first access and mobility node 116. The first session establishment request comprises a first SUPI associated with the UE 121 and a DS correlation ID. The first SUPI is associated with a first access. The DS correlation ID is adapted to be comprised in an first part of the request and in a second part of the request.

[0439] The UE 121 and / or processor 2510 is configured to send a second session establishment request to a second access and mobility node 117. The second session establishment request comprises a second SUPI associated with the UE 121 and a DS correlation ID. The second SUPI is associated with a second access different from the first access. The DS correlation ID is adapted to be comprised in a first part of the request and in a second part of the request

[0440] In some embodiments, the first part of the request comprises an MM, part of the message, and the second part comprises a session management container.

[0441] In some embodiments, the DS correlation ID is adapted to be used to correlate a first and a second session of a DS session. In some embodiments, the first session establishment request is adapted to comprise request type initial request, and the second session establishment request is adapted to comprise request type existing session.

[0442] The UE 121 may further comprise respective a memory 2520 comprising one or more memory units. The memory 2520 comprises instructions executable by the processor 2510 in the UE 121.

[0443] The memory 2520 is arranged to be used to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, flows, policies, session SUPIs, IDs and applications to perform the methods herein when being executed in the UE 121.

[0444] In some embodiments, a computer program 2530 comprises instructions, which when executed by the at least one processor 2510, cause the at least one processor 2510 of the UE 121 to perform the actions above.

[0445] In some embodiments, a respective carrier 2540 comprises the respective computer program 2530, wherein the carrier 2540 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0446] Thus, embodiments herein may disclose the UE 121 configured to handle DS in the wireless communications network 100. The UE 121 comprises the processor 2510 and the memory 2520, said memory 2520 comprising instructions executable by said processor 2510 whereby said UE 121 is operative to perform any of the methods herein.

[0447] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.

[0448] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0449] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0450] To perform the method actions above, the policy control node 113, configured to handle DS in the wireless communication network 100. The policy control node 113 may comprise an arrangement depicted in Figure 26a.

[0451] The policy control node 113 may comprise an input and output interface 2600 configured to communicate with each other. The input and output interface 2600 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0452] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 2610 of a processing circuitry in the policy control node 113 depicted in Figure 26a, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the policy control node 113. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the policy control node 113.

[0453] The policy control node 113 and / or processor 2610 is configured to establish a policy association with a first session management node 111 for a DS session by receiving a request from the first session management node 111. The request is adapted to comprise a first SUPI and a first DS SUPI. The establishing is adapted to comprise to create one or more policy rules, taking the first SUPI and the and the first DS SUPI into account.

[0454] The policy control node 113 and / or processor 2610 is configured to provide the one or more policy rules for the DS session to the first session management node 111.

[0455] The policy control node 113 and / or processor 2610 is configured to update the policy association with the first session management node 111 for the DS session by receiving a request from the first session management node 111. The request is adapted to comprise a second SUPI and a second DS SUPI. The updating is adapted to comprise to update the one or more policy rules, taking the second SUPI and the and the second DS SUPI into account.

[0456] The policy control node 113 and / or processor 2610 is configured to provide the one or more policy rules for the DS session to the first session management node 111.

[0457] In some embodiments, the one or more policy rules is adapted to comprise any one or more out of a URSP rule, a PCC rule, and an ATSSS rule.

[0458] In some embodiments, any one or more out of the URSP rule comprises a DS indication, the PCC rule comprises an access descriptor, which access descriptor indicates an access type, and the ATSSS rule comprises an access descriptor, which access descriptor indicates an access type.

[0459] In some embodiments, to update the policy association is adapted to comprises to update any one or more of the URSP rule, PCC rule and ATSSS rule.

[0460] In some embodiments, to update the PCC rule and / or ATSS rule is adapted to comprise to add an access type associated with the second SUPI.

[0461] The policy control node 113 may further comprise respective a memory 2620 comprising one or more memory units. The memory 2620 comprises instructions executable by the processor 2610 in the policy control node 113.

[0462] The memory 2620 is arranged to be used to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, flows, policies, session SUPIs, IDs and applications to perform the methods herein when being executed in the policy control node 113. In some embodiments, a computer program 2630 comprises instructions, which when executed by the at least one processor 2610, cause the at least one processor 2610 of the policy control node 113 to perform the actions above.

[0463] In some embodiments, a respective carrier 2640 comprises the respective computer program 2630, wherein the carrier 2640 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0464] Thus, embodiments herein may disclose the policy control node 113 configured to handle DS in the wireless communications network 100. The policy control node 113 comprises the processor 2610 and the memory 2620, said memory 2620 comprising instructions executable by said processor 2610 whereby said policy control node 113 is operative to perform any of the methods herein.

[0465] As will be readily understood by those familiar with communications design, that functions means or modules may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a radio network node, for example.

[0466] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random-access memory for storing software and / or program or application data, and non-volatile memory. Other hardware, conventional and / or custom, may also be included. Designers of communications receivers will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0467] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0468] To perform the method actions above, the user data node 114, configured to handle DS in the wireless communication network 100. The user data node 114 may comprise an arrangement depicted in Figure 26b.

[0469] The user data node 114 may comprise an input and output interface 2700 configured to communicate with each other. The input and output interface 2700 may comprise a receiver, e.g. wired and / or wireless, (not shown) and a transmitter, e.g. wired and / or wireless, (not shown).

[0470] The embodiments herein may be implemented through a respective processor or one or more processors, such as at least one processor 2710 of a processing circuitry in the user data node 114 depicted in Figure 26b, together with computer program code for performing the functions and actions of the embodiments herein. The program code mentioned above may also be provided as a computer program product, for instance in the form of a data carrier carrying computer program code for performing the embodiments herein when being loaded into the user data node 114. One such carrier may be in the form of a CD ROM disc. It is however feasible with other data carriers such as a memory stick. The computer program code may furthermore be provided as pure program code on a server and downloaded to the user data node 114.

[0471] The user data node 114 and / or processor 2710 is configured to provide subscription data associated with a first SUPI and / or a UE 121 to a first session management node 111. The subscription data is adapted to comprise a first DS SUPI indicating a second SUPI associated with the UE 121 .

[0472] The user data node 114 and / or processor 2710 is configured to register a DS session by receiving a registration message indicating a DS correlation ID from the first session management node 111. In some embodiments, to provide the subscription data is adapted to comprise to receive a request from the first session management node 111 , and send the subscription data to the first session management nodel 11 . The request is adapted to comprise the first SUPI associated with the UE 121 .

[0473] In some embodiments, the subscription data is adapted to comprise session management subscription data associated with the first SUPI and / or the UE 121. The subscription data is adapted to comprise the first SUPI and the first DS SUPI.

[0474] In some embodiments, to register the DS session comprises registering the DS correlation ID in the subscription data associated with the first SUPI and / or the UE 121.

[0475] In some embodiments, the user data node 114 and / or processor 2710 may further be configured to provide subscription data and / or a list of sessions for the UE 121 to second access and mobility node 117 or a second session management node 112. The subscription data is adapted to comprise a second DS SUPI associated with the second SUPI and / or the UE 121. The second DS SUPI adapted to indicate the first SUPI.

[0476] In some embodiments, to provide subscription data to the second access and mobility node 117 or the second session management node 112 is adapted to comprise to receive a request from the second access and mobility node 117 or the second session management node 112, and send the subscription data to the second access and mobility node 117 or the second session management node 112. The request is adapted to comprise a second SUPI associated with the UE 121.

[0477] In some embodiments, to provide the list of sessions for the UE 121 to the second access and mobility node 117 or the second session management node 112 is adapted to comprise to receive a request from the second access and mobility node 117 or the second session management node 112, and send the list of sessions to the second access and mobility node 117 or the second session management node 112. The request is adapted to comprise the first SUPI associated with the UE 121 .

[0478] In some embodiments, the subscription data provided to the second access and mobility node 117 is adapted to comprise access and mobility subscription data associated with the second SUPI and / or the UE 121.

[0479] In some embodiments, the subscription data provided to the session management node 112 is adapted to comprise session management subscription data associated with the second SUPI and / or the UE 121.

[0480] In some embodiments, the user data node 114 and / or processor 2710 may further be configured to provide subscription data associated with the second SUPI and / or the UE 121 to the first session management node 111. The subscription data is adapted to comprises the second DS SUPI indicating the first SUPI.

[0481] In some embodiments, to provide the subscription data to the first session management node 111 is adapted to comprise to receive a request from the first session management node 111 and send the subscription data to the first session management node 111. The request is adapted to comprise the second SUPI. The subscription data is adapted to comprise session management subscription data associated with the second SUPI and / or the UE 121.

[0482] The user data node 114 may further comprise respective a memory 2720 comprising one or more memory units. The memory 2720 comprises instructions executable by the processor 2710 in the user data node 114.

[0483] The memory 2720 is arranged to be used to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, flows, policies, session SUPIs, IDs and applications to perform the methods herein when being executed in the user data node 114.

[0484] In some embodiments, a computer program 2730 comprises instructions, which when executed by the at least one processor 2710, cause the at least one processor 2710 of the user data node 114 to perform the actions above.

[0485] In some embodiments, a respective carrier 2740 comprises the respective computer program 2730, wherein the carrier 2740 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0486] Thus, embodiments herein may disclose the user data node 114 configured to handle DS in the wireless communications network 100. The user data node 114 comprises the processor 2710 and the memory 2720, said memory 2720 comprising instructions executable by said processor 2710 whereby said user data node 114 is operative to perform any of the methods herein.

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

[0488] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0489] ADDITIONAL EXPLANATION

[0490] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0491] Figure 27 shows an example of a communication system QQ100 in accordance with some embodiments.

[0492] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0493] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

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

[0495] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.

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

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

[0498] As a whole, the communication system QQ100 of Figure 27 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0499] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

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

[0501] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub QQ114 may be a content source. For example, for a UE that is a VR device, display, loudspeaker, or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

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

[0503] Figure 28 shows a UE QQ200 in accordance with some embodiments. The UE QQ200 presents additional details of some embodiments of the UE QQ112 of Figure 1. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, vehiclemounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0504] A UE may support device-to- device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0505] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 28. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0506] The processing circuitry QQ202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory QQ210. The processing circuitry QQ202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ202 may include multiple central processing units (CPUs).

[0507] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE QQ200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

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

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

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

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

[0512] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0513] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

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

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

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

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

[0518] Figure 29 shows a network node QQ300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O- RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

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

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

[0521] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ300.

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

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

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

[0525] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0526] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0527] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0528] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

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

[0530] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 29 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300. In some embodiments providing a core network node, such as core network node 108 of FIG. QQ1 , some components, such as the radio front-end circuitry QQ318 and the RF transceiver circuitry QQ312 may be omitted.

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

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

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

[0534] The VMs QQ408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ406. Different embodiments of the instance of a virtual appliance QQ402 may be implemented on one or more of VMs QQ408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0535] In the context of NFV, a VM QQ408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs QQ408, and that part of hardware QQ404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs QQ408 on top of the hardware QQ404 and corresponds to the application QQ402.

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

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

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

[0539] When using the word "comprise" or “comprising” it shall be interpreted as nonlimiting, i.e. meaning "consist at least of'.

[0540] The embodiments herein are not limited to the preferred embodiments described above. Various alternatives, modifications and equivalents may be used.

[0541] Abbreviation Explanation

[0542] 5GC 5G Core

[0543] DS Dual steering

[0544] AMF Access & Mobility Management Function

[0545] ATSSS Access Traffic Steering Switching and Splitting

[0546] DS Dual Steering

[0547] FAR Forwarding Action Rule

[0548] MA Multi Access

[0549] MAR Multi Access Rule

[0550] SMF Session Management Function

[0551] PCC Policy Control and Charging

[0552] PDR Packet Detection Rule

[0553] UDM Unified Data Management

[0554] UDR Unified Data Repository

[0555] UPF User Plane Function

Claims

CLAIMS1. A method performed by a first session management node (111) for handling Dual Steering, DS, in a wireless communication network (100), the method comprising: receiving (701) a first session context establishment request for establishing a DS session, the first session context establishment request comprising a first Subscription Permanent Identifier, SUPI, associated with a User Equipment, UE, (121) and a DS correlation identity, ID, wherein the first SUPI is associated with a first access, establishing (702) a context for the DS session using the first SUPI, the DS correlation ID and a first DS SUPI associated with the first SUPI and / or the UE (121), the first DS SUPI indicating a second SUPI associated with the UE (121), requesting (703) a policy association to be established by sending a policy association establishment request to a policy control node (113), the request comprising the first SUPI and the first DS SUPI, receiving (705) a third session context establishment request for establishing the DS session, the third session context establishment request comprising the second SUPI associated with the UE (121) and the DS correlation ID, wherein the second SUPI is associated with second access different from first access, updating (706) the context for the DS session using the second SUPI, the DS correlation ID and a second DS SUPI associated with the second SUPI and / or the UE (121), and updating (707) the policy association by sending a policy association modification request to a policy control node (113), the request comprising the second SUPI and the second DS SUPI.

2. The method according to claim 1 , wherein the first DS SUPI indicates the second SUPI, and wherein the second DS SUPI indicates the first SUPI.

3. The method according to any of claims 1-2, wherein the DS correlation ID identifies the DS session.

4. The method according to any of claims 1-3, wherein the first session context establishment request comprises a request type parameter indicating request type initial request.

5. The method according to any of claims 1-4, wherein establishing (702) the context comprises obtaining subscription data for the UE (121), which subscription data comprises the first DS SUPI, and further associating the DS session with the first SUPI and the second SUPI indicated in the DS SUPI.

6. The method according the any of claims 1-5, wherein the method further comprises: registering (704) the DS session in a user data node (114) by sending a registration message indicating the DS correlation ID to the user data node (114).

7. The method according to claim 6, wherein the registration further registers the DS correlation ID in a UE context associated with the UE (121) in the user data node (114).

8. A method performed by a first access and mobility node (116) for handling Dual Steering, DS, in a wireless communication network (100), the method comprising: receiving (901) a first session establishment request from a User Equipment, UE, (121), wherein the first session establishment request comprises a first Subscription Permanent Identifier, SUPI, associated with the UE (121) and a DS correlation identity, ID, wherein the first SUPI is associated with a first access, wherein the DS correlation ID is comprised in a mobility management, MM, part of the request and in a session management, SM, container of the request, selecting (902) a first session management node (111), sending (903) a first session context establishment request to the selected first session management node (111), the first session context establishment request comprising the first SUPI and the DS correlation ID.

9. The method according to 8, wherein selecting (902) the first session management node (111) comprises selecting a session management node supporting DS.

10. The method according to any of claims 8-9, wherein the first session establishment request is a DS session establishment request, and wherein the DS session establishment request indicates that a session management node supporting DS is to be selected.

11. A method performed by a second access and mobility node (117) e.g., for handling Dual Steering, DS, in a wireless communication network (100), the method comprising: receiving (1001) a second session establishment request from a User Equipment, UE, (121), wherein the second session establishment request comprises a second Subscription Permanent Identifier, SUPI, associated with the UE (121) and a DS correlation identity, ID, wherein the second SUPI is associated with a second access, wherein the DS correlation ID is comprised in a mobility management, MM, part of the request and in a session management, SM, container of the request, selecting (1002) a session management node, wherein the selected session management node is a first session management node (111) selected for the DS session by a first access and mobility node (116), sending (1003) a session context establishment request to the selected session management node (111), wherein the session context establishment request comprises the second SUPI and the DS correlation ID.

12. The method according to claim 11 , wherein the first session management node (111) is selected based on a second DS SUPI and the DS correlation ID.

13. The method according to any of claims 11-12, wherein selecting the first session management node (111) further comprises obtaining subscription data for the UE (121), which subscription data comprises the second DS SUPI, wherein the second DS SUPI indicates a first SUPI associated with the UE (121), and obtaining a list of sessions for the UE (121) based on the first SUPI.

14. The method according to claim 13, wherein selecting the first session management node (111) further comprises obtaining an identity of the first session management node (111) using the list of sessions and the DS correlation ID.

15. A method performed by a User Equipment, UE (121) e.g., for handling Dual Steering, DS, in a wireless communication network (100), the method comprising: sending (1101) a first session establishment request to a first access and mobility node (116), wherein the first session establishment request comprises a first Subscription Permanent Identifier, SUPI, associated with the UE (121) and a DS correlation identity, ID, wherein the first SUPI is associated with a first access, wherein the DS correlation ID is comprised in an first part of the request and in a second part of the request,sending (1102) a second session establishment request to a second access and mobility node (117), wherein the second session establishment request comprises a second SUPI associated with the UE (121) and the DS correlation ID, wherein the second SUPI is associated with a second access different from the first access, wherein the DS correlation ID is comprised in a first part of the request and in a second part of the request.

16. The method according to claim 13, wherein the first part of the request comprises a mobility management, MM, part of the message, and wherein the second part comprises an session management container.

17. The method according to any of claims 13-14, wherein the DS correlation ID is used to correlate a first and a second session of a DS session.

18. The method according to any of claims 15-17, wherein the first session establishment request comprises request type initial request, and wherein the second session establishment request comprises request type existing session.

19. A method performed by a policy control node (113) for handling Dual Steering, DS, in a wireless communication network (100), the method comprising: establishing (1201) a policy association with a first session management node (111) for a DS session by receiving a request from the first session management node (111), the request comprising a first Subscription Permanent Identifier, SUPI, and a first DS SUPI, which establishing comprises creating one or more policy rules, taking the first SUPI and the and the first DS SUPI into account, providing (1202) the one or more policy rules for the DS session to the first session management node (111), updating (1203) the policy association with the first session management node (111) for the DS session by receiving a request from the first session management node (111), the request comprising a second SUPI and a second DS SUPI, which updating comprises updating the one or more policy rules, taking the second SUPI and the and the second DS SUPI into account, providing (1204) the one or more policy rules for the DS session to the first session management node (111).

20. The method according to claim 19, wherein the one or more policy rules comprises any one or more out of:- a user equipment Route Selection Policy, URSP, rule,- a Policy Control and Charging, PCC, rule, and- an Access Traffic Steering, Switching and Splitting, ATSSS, rule.21 . The method according to claim 20, wherein any one or more out of:- the URSP rule comprises a DS indication,- the PCC rule comprises an access descriptor, which access descriptor indicates an access type, and- the ATSSS rule comprises an access descriptor, which access descriptor indicates an access type.

22. The method according to any of claims 20-21 , wherein updating the policy association comprises updating any one or more of the URSP rule, PCC rule and ATSSS rule.

23. The method according to claim 22, wherein updating the PCC rule and / or ATSS rule comprises adding an access type associated with the second SUPI.

24. A method performed by user data node (114) for handling Dual Steering, DS, in a wireless communication network (100), the method comprising: providing (1301) subscription data associated with a first Subscription Permanent Identifier, SUPI, and / or the UE (121) to a first session management node (111), wherein the subscription data comprises a first DS SUPI indicating a second SUPI associated with the UE (121), registering (1302) the DS session by receiving a registration message indicating a DS correlation identity, ID, from the first session management node (111).

25. The method according to claim 24, wherein providing (1301) the subscription data comprises receiving a request from the first session management node (111), and sending the subscription data to the first session management node (111), wherein the request comprises a first SUPI associated with the UE (121).

26. The method according to any of claims 24-25, wherein the subscription data comprises session management subscription data associated with the first SUPI and / or the UE (121), which subscription data comprises the first SUPI and the first DS SUPI.

27. The method according to any of claims 24-26, wherein registering (1302) the DS session comprises registering the DS correlation ID in a UE context associated with the first SUPI and / or the UE (121) and associating the DS session with the DS correlation ID.

28. The method according to any of claims 24-27, wherein the method further comprises: providing (1303) subscription data and / or a list of sessions for the UE (121) to second access and mobility node (117) or a second session management node (112), wherein the subscription data comprises a second DS SUPI associated with the second SUPI and / or the UE (121), the second DS SUPI indicating the first SUPI.

29. The method according to claim 28, wherein providing (1303) subscription data to the second access and mobility node (117) or the second session management node (112) comprises receiving a request from the second access and mobility node (117) or the second session management node (112), and sending the subscription data to the second access and mobility node (117) or the second session management node (112), wherein the request comprises a second SUPI associated with the UE (121).

30. The method according to any of claims 28-29, wherein providing (1303) the list of sessions for the UE (121) to the second access and mobility node (117) or the second session management node (112) comprises receiving a request from the second access and mobility node (117) or the second session management node (112), and sending the list of sessions to the second access and mobility node (117) or the second session management node (112), wherein the request comprises the first SUPI associated with the UE (121).31 . The method according to any of claims 28-30, wherein any one out of:- the subscription data provided to the second access and mobility node (117) comprises access and mobility subscription data associated with the second SUPI and / or the UE (121), or- the subscription data provided to the session management node (112) comprises session management subscription data associated with the second SUPI and / or the UE (121).

32. The method according to any of claims 24-31 , wherein the method further comprises: providing (1304) subscription data subscription data associated with the second SUPI and / or the UE (121) to the first session management node (111), wherein the subscription data comprises the second DS SUPI indicating the first SUPI.

33. The method according to claim 32, wherein providing (1304) subscription data subscription data to the first session management node (111) comprises receiving a request from the first session management node (111) and sending the subscription data to the first session management node (111), wherein the request comprises the second SUPI, and wherein the subscription data comprises session management subscription data associated with the second SUPI and / or the UE (121).

34. A first session management node (111) configured to handle Dual Steering, DS, in a wireless communication network (100), the first session management node (111) further being configured to: receive a first session context establishment request for establishing a DS session, the first session context establishment request adapted to comprise a first Subscription Permanent Identifier, SUPI, associated with a User Equipment, UE, (121) and a DS correlation identity, ID, wherein the first SUPI is adapted to be associated with a first access, establish a context for the DS session using the first SUPI, the DS correlation ID and a first DS SUPI associated with the first SUPI and / or the UE (121), the first DS SUPI adapted to indicate a second SUPI associated with the UE (121), request a policy association to be established by sending a policy association establishment request to a policy control node (113), the request adapted to comprise the first SUPI and the first DS SUPI, receive a third session context establishment request for establishing the DS session, the third session context establishment request adapted to comprise the second SUPI associated with the UE (121) and the DS correlation ID, wherein the second SUPI is adapted to be associated with second access different from first access,update the context for the DS session using the second SUPI, the DS correlation ID and a second DS SUPI adapted to be associated with the second SUPI and / or the UE (121), and update the policy association by sending a policy association modification request to a policy control node (113), the request adapted to comprise the second SUPI and the second DS SUPI.

35. The first session management node (111) according to claim 28, wherein the first DS SUPI is adapted to indicate the second SUPI, and where the second DS SUPI is adapted to indicate the first SUPI.

36. The first session management node (111) according to any of claims 28-29, wherein the DS correlation ID is adapted to identify the DS session.

37. The first session management node (111) according to any of claims 28-30, wherein the first session context establishment request is adapted to comprise a request type parameter indicating request type initial request.

38. The first session management node (111) according to any of claims 28-31 , wherein to establish the context is adapted to comprise to obtain subscription data for the UE (121), which subscription data is adapted to comprise the DS SUPI, and further to associate the DS session with the first SUPI and the second SUPI indicated in the DS SUPI.

39. The first session management node (111) according to any of claims 28-32, wherein the first session management node (111) is further configured to: register the DS session in a user data node (114) by sending a registration message indicating the DS correlation ID to the user data node (114).

40. The first session management node (111) according to claim 33, wherein the registration is further adapted to register the DS correlation ID in a UE context associated with the UE (121) in the user data node (114).

41. A first access and mobility node (116) configured to handle Dual Steering, DS, in a wireless communication network (100), the first access and mobility node (116) further being configured to: receive a first session establishment request from a User Equipment, UE, (121), wherein the first session establishment request is adapted to comprise a first Subscription Permanent Identifier, SUPI, associated with the UE (121) and a DS correlation identity, ID, wherein the first SUPI is adapted to be associated with a first access, wherein the DS correlation ID is adapted to be comprised in a mobility management, MM, part of the request and in a session management, SM, container of the request, select a first session management node (111), send a first session context establishment request to the selected first session management node (111), the first session context establishment request adapted to comprise the first SUPI and the DS correlation ID.

42. The first access and mobility node (116) according to 35, wherein to select the first session management node (111) is adapted to comprise to select a session management node supporting DS.

43. The first access and mobility node (116) according to any of claims 35-36, wherein the first session establishment request is a DS session establishment request, and wherein the DS session establishment request is adapted to indicate that a session management node supporting DS is to be selected.

44. A second access and mobility node (117) configured to handle Dual Steering, DS, in a wireless communication network (100), the second access and mobility node (117) further being configured to: receive a second session establishment request from a User Equipment, UE, (121), wherein the second session establishment request is adapted to comprise a second Subscription Permanent Identifier, SUPI, associated with the UE (121) and a DS correlation identity, ID, wherein the second SUPI is adapted to be associated with a second access, wherein the DS correlation ID is adapted to be comprised in a mobility management, MM, part of the request and in a session management, SM, container of the request,select a session management node, wherein the selected session management node is adapted to be a first session management node (111) selected for the DS session by a first access and mobility node (116), send a session context establishment request to the selected session management node (111), wherein the session context establishment request is adapted to comprise the second SUPI and the DS correlation ID.

45. The second access and mobility node (117) according to claim 38, wherein the first session management node (111) is selected based on a second DS SUPI and the DS correlation ID.

46. The second access and mobility node (117) according to any of claims 38-39, wherein to select the first session management node (111) is further adapted to comprise to obtain subscription data for the UE (121), which subscription data is adapted to comprise the second DS SUPI, wherein the second DS SUPI is adapted to indicate a first SUPI associated with the UE (121), and to obtain a list of sessions for the UE (121) based on the first SUPI.

47. The second access and mobility node (117) according to claim 40, wherein to select the first session management node (111) is further adapted to comprise to obtain an identity of the first session management node (111) using the list of sessions and the DS correlation ID.

48. A User Equipment, UE (121) configured to handle Dual Steering, DS, in a wireless communication network (100), the UE (121) further being configured to: send a first session establishment request to a first access and mobility node (116), wherein the first session establishment request is adapted to comprise a first Subscription Permanent Identifier, SUPI, associated with the UE (121) and a DS correlation identity, ID, wherein the first SUPI is adapted to be associated with a first access, wherein the DS correlation ID is adapted to be comprised in an first part of the request and in a second part of the request, send a second session establishment request to a second access and mobility node (117), wherein the second session establishment request is adapted to comprise a second SUPI associated with the UE (121) and the DS correlation ID, wherein the second SUPI is associated with a second access different from the first access, wherein the DScorrelation ID is adapted to be comprised in a first part of the request and in a second part of the request.

49. The UE (121) according to claim 42, wherein the first part of the request comprises a mobility management, MM, part of the message, and wherein the second part comprises an session management container.

50. The UE (121) according to any of claims 42-43, wherein the DS correlation ID is adapted to be used to correlate a first and a second session of a DS session.51 . The UE (121) according to any of claims 42-44, wherein the first session establishment request is adapted to comprise request type initial request, and wherein the second session establishment request is adapted to comprise request type existing session.

52. A policy control node (113) configured to handle Dual Steering, DS, in a wireless communication network (100), the policy control node (113) further being configured to: establish a policy association with a first session management node (111) for a DS session by receiving a request from the first session management node (111), the request adapted to comprise a first Subscription Permanent Identifier, SUPI, and a first DS SUPI, which establishing is adapted to comprise to create one or more policy rules, taking the first SUPI and the and the first DS SUPI into account, provide the one or more policy rules for the DS session to the first session management node (111), update the policy association with the first session management node (111) for the DS session by receiving a request from the first session management node (111), the request adapted to comprise a second SUPI and a second DS SUPI, which updating is adapted to comprise to update the one or more policy rules, taking the second SUPI and the and the second DS SUPI into account, provide the one or more policy rules for the DS session to the first session management node (111).

53. The policy control node (113) according to claim 46, wherein the one or more policy rules is adapted to comprise any one or more out of:- a user equipment Route Selection Policy, URSP, rule,- a Policy Control and Charging, PCC, rule, and- an Access Traffic Steering, Switching and Splitting, ATSSS, rule.

54. The policy control node (113) according to claim 47, wherein any one or more out of:- the URSP rule comprises a DS indication,- the PCC rule comprises an access descriptor, which access descriptor indicates an access type, and- the ATSSS rule comprises an access descriptor, which access descriptor indicates an access type.

55. The policy control node (113) according to any of claims 47-48, wherein to update the policy association is adapted to comprises to update any one or more of the URSP rule, PCC rule and ATSSS rule.

56. The policy control node (113) according to claim 49, wherein to update the PCC rule and / or ATSS rule is adapted to comprise to add an access type associated with the second SUPI.

57. A user data node (114) configured to handle Dual Steering, DS, in a wireless communication network (100), the user data node further being configured to: provide subscription data associated with a first Subscription Permanent Identifier, SUPI, and / or the UE (121) to a first session management node (111), wherein the subscription data is adapted to comprise a first DS SUPI indicating a second SUPI associated with the UE (121), register the DS session by receiving a registration message indicating a DS correlation identity, ID, from the first session management node (111).

58. The user data node (114) according to claim 51 , wherein to provide the subscription data is adapted to comprise to receive a request from the first session management node (111), and send the subscription data to the first session management node (111), wherein the request is adapted to comprise a first SUPI associated with the UE (121).

59. The user data node (114) according to any of claims 51-52, wherein the subscription data is adapted to comprise session management subscription data associated with the first SUPI and / or the UE (121), which subscription data is adapted to comprise the first SUPI and the first DS SUPI.

60. The user data node (114) according to any of claims 51-53, wherein to register the DS session is adapted to comprise to register the DS correlation ID in a UE context associated with the first SUPI and / or the UE (121) ) and associate the DS session with the DS correlation ID.61 . The user data node (114) according to any of claims 57-60, wherein the user data node (114) is further configured to: provide subscription data and / or a list of sessions for the UE (121) to second access and mobility node (117) or a second session management node (112), wherein the subscription data is adapted to comprise a second DS SUPI associated with the second SUPI and / or the UE (121), the second DS SUPI adapted to indicate the first SUPI.

62. The user data node (114) according to claim 61 , wherein to provide subscription data to the second access and mobility node (117) or the second session management node (112) is adapted to comprise to receive a request from the second access and mobility node (117) or the second session management node (112), and send the subscription data to the second access and mobility node (117) or the second session management node (112), wherein the request is adapted to comprise a second SUPI associated with the UE (121).

63. The user data node (114) according to any of claims 61-62, wherein to provide the list of sessions for the UE (121) to the second access and mobility node (117) or the second session management node (112) is adapted to comprise to receive a request from the second access and mobility node (117) or the second session management node (112), and send the list of sessions to the second access and mobility node (117) or the second session management node (112), wherein the request is adapted to comprise the first SUPI associated with the UE (121).

64. The user data node (114) according to any of claims 61-63, wherein any one out of:- the subscription data provided to the second access and mobility node (117) is adapted to comprise access and mobility subscription data associated with the second SUPI and / or the UE (121), or- the subscription data provided to the session management node (112) is adapted to comprise session management subscription data associated with the second SUPI and / or the UE (121).

65. The user data node (114) according to any of claims 57-64, wherein the user data node (114) is further configured to: provide subscription data associated with the second SUPI and / or the UE (121) to the first session management node (111), wherein the subscription data is adapted to comprises the second DS SUPI indicating the first SUPI.

66. The user data node (114) according to claim 65, wherein to provide the subscription data to the first session management node (111) is adapted to comprise to receive a request from the first session management node (111) and send the subscription data to the first session management node (111), wherein the request is adapted to comprise the second SUPI, and wherein the subscription data is adapted to comprise session management subscription data associated with the second SUPI and / or the UE (121).

67. A computer program comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-33, as performed by the first session management node (111), the first access and mobility node (116), the second access and mobility node (117), the UE (121), the policy control node (113) and the user data node (114), respectively.

68. A carrier comprising the computer program of claim 67, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

Images