Session management node, access and mobility node, ue, policy control node and methods in a wireless communication network

Abstract

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

Description

Technical Field

[0001] The embodiments described herein relate to server nodes, client nodes, and methods for wireless communication executed therein. Furthermore, a computer program product and a computer-readable storage medium are also provided herein. In particular, the embodiments described herein relate to processing or enabling communication (such as managing data delivery) in a communication network. Background Technology

[0002] In a typical wireless communication network, wireless devices, also known as wireless communication equipment, mobile stations, stations (STAs), and / or user equipment (UEs), communicate via wide area networks or local area networks (such as Wi-Fi networks) or cellular networks comprising a radio access network (RAN) portion and a core network (CN) portion. RAN coverage is a geographical area divided into service areas or cell areas, which may also be referred to as beams or beam groups, where each service area or cell area is served by a radio network node, such as a radio access node (e.g., a Wi-Fi access point, base station (BS), or radio base station (RBS)), which in some networks may also be represented as, for example, a base station (BS), NodeB, eNodeB (eNB), or gNodeB (gNB) as represented in fifth-generation (5G) telecommunications. A service area or cell area is a geographical area where radio coverage is provided by radio network nodes. Radio network nodes communicate with wireless devices within their range via an air interface operating on radio frequency.

[0003] The 3rd Generation Partnership Project (3GPP) is a standards organization that defines the standards used for the evolution of cellular systems, including 3G, 4G, 5G, and future evolutions. Specifications for Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet System (EPS) have been finalized within 3GPP. In 4G (also known as fourth-generation (4G)) networks, EPS is the core network and E-UTRA is the radio access network. In 5G, 5GC is the core network and NR is the radio access network. As part of ongoing network evolution, new versions of 3GPP define 5G networks, also known as 5G New Radio (NR) and 5G Core (5GC).

[0004] The frequency bands used for 5G NR are divided into two distinct frequency ranges: Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 includes bands below 6 GHz. Some of these bands are traditionally used by legacy standards but have been expanded to cover potential new spectrum supply from 410 MHz to 7125 MHz. FR2 includes bands from 24.25 GHz to 52.6 GHz. Compared to the bands in FR1, this millimeter-wave range offers a shorter range but higher available bandwidth.

[0005] Multi-antenna technology can significantly improve the data rate and reliability of wireless communication systems. For wireless connections between a single user (such as a UE) and a base station (BS), performance is particularly improved if both the transmitter and receiver are equipped with multiple antennas (resulting in a Multiple-Input Multiple-Output (MIMO) communication channel). This can be referred to as single-user (SU) MIMO. In scenarios where MIMO technology is used for wireless connections between multiple users and base stations, MIMO further increases cell capacity by spatially separating users, allowing them to communicate with the base station simultaneously using the same time-frequency resources. This can be referred to as multi-user (MU) MIMO. Note that MU-MIMO can be beneficial when each UE has only one antenna. Cell capacity can be increased linearly relative to the number of antennas on the BS side. For this reason, more and more antennas are being adopted in the BS. Such systems and / or related technologies are often referred to as massive MIMO.

[0006] In addition to faster peak internet connection speeds, 5G plans aim for greater capacity than current 4G, allowing for a higher number of mobile broadband users per unit area and enabling higher or unlimited gigabytes of data consumption per user per month. This will make it feasible for most of the population to stream high-definition media for many hours a day using their mobile devices when Wi-Fi hotspots are unavailable. 5G research and development also aims to support improvements in machine-to-machine communication (also known as the Internet of Things), with the goal of lower cost, lower battery consumption, and lower latency compared to 4G devices.

[0007] Currently, UEs can use Access Service Bootstrapping, Handover, and Split (ATSSS) to simultaneously connect to a 5G system using one non-3GPP access and one 3GPP access. For non-roaming scenarios, the architecture is given in Section 4.2.10 of 3GPP TS 23.501 v18.3.0, and... Figure 1 As shown in the figure, Figure 1 The diagram illustrates non-roaming and roaming architectures with local routing for ATSSS support.

[0008] To establish user plane resources for multiple access (MA) packet data unit (PDU) sessions, the policy control function (PCF) generates policy control and charging (PCC) rules that include MA PDU session control, see section 6.3 of 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 multiple access rules (MARs), each MAR pointing to two forwarding action rules (FARs), see section 5.8.5.8 of 3GPP TS 23.501 v18.3.0.

[0009] Connecting a DualSteer device to two 3GPP access networks is a research project under the DualSteer (DS) topic in Release 19 (Rel 19). The requirement is that a user registers with both access networks using two different Subscription Permanent Identifiers (SUPIs) connected to the same subscription. A dual-steer device is a device that supports service bootstrapping and handover of user data (e.g., for different services) across two 3GPP access networks. It can be a single UE or two separate UEs within a single device. In the latter case, each UE is processing one SUPI. Minimal disruption should occur during access handover. The Phase 1 requirements for dual-steer research have been agreed upon in 3GPP document S1-233371. Summary of the Invention

[0010] As part of the development of the embodiments described herein, a problem was discovered by the inventors and will be discussed first.

[0011] Currently, dual-SIM devices exist that can connect via two SUPIs through two 3GPP access points. The 3GPP Technical Specification Group and System Aspect 2 (3GPP TSG SA2) have also been enhanced to support such devices in the Multiple USIM (MUSIM) work project. However, this assumes that each SUPI / SIM is used to access a specific service / operator, and does not support service aggregation on the two 3GPP access points or service switching between them. This is what needs to be investigated in the new 3GPP SA2 research. The challenge is:

[0012] 1. How to establish a PDU session using two access points with two different SUPIs to a PDU session anchor (PSA)?

[0013] 2. As mentioned, the two SUPIs can be handled by two UEs in a dual-boot device. These two UEs may not be able to generate a common PDU session ID, which may pose challenges in establishing a PDU session with the common anchor point UPF.

[0014] 3. Considering that both SUPIs are connected to the same subscriber, how should subscription data be handled?

[0015] 4. How should the PCC, ATSSS, and N4 rules be changed to support two different access connections to the DN with two SUPIs?

[0016] Therefore, the purpose of the embodiments described herein is to provide a mechanism for simplifying DS processing and improving the performance of wireless communication networks.

[0017] According to one aspect of the embodiments herein, this objective is achieved by a method for processing dual bootstrapping (DS) in a wireless communication network, performed by a first session management node.

[0018] The first session management node receives a first session context establishment request for establishing a DS session. The first session context establishment request includes a first subscription permanent identifier (SUPI) and a DS association identifier (ID) associated with the user equipment (UE). The first SUPI is associated with the first access.

[0019] The first session management node uses the first SUPI, the DS association ID, and the first DS SUPI associated with the first SUPI and / or the UE to establish a context for the DS session. The first DS SUPI indicates the second SUPI associated with the UE.

[0020] The first session management node requests the establishment of a policy association by sending a policy association establishment request to the policy control node. This request includes the first SUPI and the first DS SUPI.

[0021] The first session management node receives a third session context establishment request for establishing a DS session. The third session context establishment request includes a second SUPI associated with the UE, a DS association identifier ID, and optionally an ID of the DS session associated with the first SUPI. The second SUPI is associated with a second access point different from the first access point.

[0022] The first session management node uses the second SUPI, the DS association ID, and the second DS SUPI associated with the second SUPI and / or the UE to update the context used for the DS session.

[0023] The first session management node updates policy associations by sending a policy association modification request to the policy control node. This request includes the second SUPI and the second DS SUPI.

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

[0025] The first access and mobility node receives a first session establishment request from the UE. The first session establishment request includes a first SUPI associated with the UE and a DS association ID. The first SUPI is associated with the first access.

[0026] The first access and mobility node selects the first session management node.

[0027] The first access and mobility node sends a first session context establishment request to the selected first session management node. The first session context establishment request includes a first SUPI and a DS association ID. The DS association ID is included in the mobility management (MM) portion of the request and the session management (SM) container of the request.

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

[0029] The second access and mobility node receives a second session establishment request from the UE. The second session establishment request includes a second SUPI associated with the UE and a DS association ID. The second SUPI is associated with the second access. The DS association ID is included in the MM portion of the request and the SM container of the request.

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

[0031] The second access and mobility node sends a session context establishment request to the selected session management node. The session context establishment request includes the second SUPI, the DS association ID, and optionally the ID of the DS session associated with the first SUPI.

[0032] According to another aspect of the embodiments herein, this objective is achieved by a method performed by the UE for processing DS in a wireless communication network.

[0033] The UE sends a first session establishment request to the first access and mobility node. The first session establishment request includes a first SUPI associated with the UE and a DS association ID. The first SUPI is associated with the first access. The DS association ID is included in the first part and the second part of the request.

[0034] The UE sends a second session establishment request to the second access and mobility node. The second session establishment request includes a second SUPI associated with the UE and a DS association ID. The second SUPI is associated with a second access that is different from the first access. The DS association ID is included in both the first and second parts of the request.

[0035] According to another aspect of the embodiments herein, this objective is achieved by a method for processing DS in a wireless communication network, executed by a policy control node.

[0036] The policy control node establishes a policy association with the first session management node for a DS session by receiving a request from the first session management node. This request includes a first SUPI and a first DS SUPI. The establishment involves creating one or more policy rules by considering the first SUPI and the first DS SUPI.

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

[0038] The policy control node updates its policy association with the first session management node for a DS session by receiving a request from the first session management node. This request includes a second SUPI and a second DS SUPI. The update involves updating one or more policy rules by taking the second SUPI and the second DS SUPI into account.

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

[0040] According to another aspect of the embodiments herein, this objective is achieved by a first session management node configured to process a DS in a wireless communication network.

[0041] The first session management node is also configured to receive a first session context establishment request for establishing a DS session. The first session context establishment request is adapted to include a first SUPI associated with the UE and a DS association ID. The first SUPI is adapted to be associated with a first access.

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

[0043] The first session management node is also configured to request the establishment of a policy association by sending a policy association establishment request to the policy control node. This request is suitable for including both the first SUPI and the first DS SUPI.

[0044] The first session management node is also configured to receive a third session context establishment request for establishing a DS session. The third session context establishment request is adapted to include a second SUPI associated with the UE and a DS association ID. The second SUPI is adapted to be associated with a second access point different from the first access point.

[0045] The first session management node is also configured to update the context for the DS session using the second SUPI, the DS association ID, and the second DS SUPI suitable for association with the second SUPI and / or the UE.

[0046] The first session management node is also configured to update policy associations by sending a policy association modification request to the policy control node. This request is suitable for including the second SUPI and the second DS SUPI.

[0047] According to another aspect of the embodiments herein, this objective is achieved by being configured to process the first access and mobility node of a DS in a wireless communication network.

[0048] The first access and mobility node is also configured to receive a first session establishment request from the UE. The first session establishment request is adapted to include a first SUPI and a DS association ID associated with the UE. The first SUPI is adapted to be associated with the first access. The DS association ID is adapted to be included in the MM portion of the request and the SM container of the request.

[0049] The first access and mobility node is also configured to select the first session management node.

[0050] The first access and mobility node is also configured to send a first session context establishment request to the selected first session management node. The first session context establishment request is adapted to include the first SUPI and DS association ID.

[0051] According to another aspect of the embodiments herein, this objective is achieved by a second access and mobility node configured to process a DS in a wireless communication network.

[0052] The second access and mobility node is also configured to receive a second session establishment request from the UE. The second session establishment request is adapted to include a second SUPI and a DS association ID associated with the UE. The second SUPI is adapted to be associated with the second access. The DS association ID is adapted to be included in the MM portion of the request and the SM container of the request.

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

[0054] The second access and mobility node is also configured to send a session context establishment request to the selected session management node. The session context establishment request is adapted to include the second SUPI and DS association ID.

[0055] According to another aspect of the embodiments herein, this objective is achieved by a UE configured to process a DS in a wireless communication network.

[0056] The UE is also configured to send a first session establishment request to a first access and mobility node. The first session establishment request is adapted to include a first SUPI and a DS association ID associated with the UE. The first SUPI is adapted to be associated with the first access. The DS association ID is adapted to be included in both the first and second parts of the request.

[0057] The UE is also configured to send a second session establishment request to a second access and mobility node. The second session establishment request is adapted to include a second SUPI and a DS association ID associated with the UE. The second SUPI is associated with a second access that is different from the first access. The DS association ID is adapted to be included in both the first and second parts of the request.

[0058] According to another aspect of the embodiments herein, this objective is achieved by a policy control node configured to process DS in a wireless communication network.

[0059] The policy control node is also configured to establish a policy association with the first session management node for a DS session by receiving a request from the first session management node. This request is suitable to include a first SUPI and a first DS SUPI. The establishment is suitable to include creating one or more policy rules by taking into account the first SUPI and the first DS SUPI.

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

[0061] The policy control node is also configured to update the policy association with the first session management node for a DS session by receiving a request from the first session management node. This request may include a second SUPI and a second DS SUPI. The update may include updating one or more policy rules by taking into account the second SUPI and the second DS SUPI.

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

[0063] According to another aspect of the embodiments described herein, this objective is achieved by a user data node used for processing a DS in a wireless communication network.

[0064] The user data node provides the first session management node with subscription data associated with the first subscription permanent identifier SUPI and / or the UE. The subscription data includes the first DS subscription permanent identifier SUPI, which indicates the second SUPI associated with the UE.

[0065] User data nodes register a DS session by receiving a registration message from the first session management node that indicates the DS associated identifier ID.

[0066] According to another aspect of the embodiments described herein, this objective is achieved by a user data node configured to process a DS in a wireless communication network.

[0067] The user data node is also configured to provide subscription data associated with the first subscription permanent identifier SUPI and / or the UE (121) to the first session management node. The subscription data is adapted to include a first DSSUPI indicating a second SUPI associated with the UE.

[0068] The user data node is also configured to register a DS session by receiving a registration message from the first session management node that indicates the DS associated identifier ID. Attached Figure Description

[0069] Examples of embodiments described herein are described in more detail with reference to the accompanying drawings, in which:

[0070] Figure 1 It is a schematic block diagram based on existing technology.

[0071] Figure 2 These are schematic block diagrams based on embodiments described herein.

[0072] Figure 3 These are schematic block diagrams based on embodiments described herein.

[0073] Figure 4 These are schematic block diagrams based on embodiments described herein.

[0074] Figure 5 These are schematic block diagrams based on embodiments described herein.

[0075] Figure 6 This is a schematic block diagram based on the prior art. It provides an overview of a wireless communication network according to embodiments herein.

[0076] Figure 7 This is a flowchart depicting an embodiment of the method in the first session management node.

[0077] Figure 8 This is a flowchart depicting an embodiment of the method in the second session management node.

[0078] Figure 9 This is a flowchart depicting an embodiment of the method in the first access and mobility node.

[0079] Figure 10 This is a flowchart depicting an embodiment of the method in the second access and mobility node.

[0080] Figure 11 This is a flowchart depicting an embodiment of a method in a UE.

[0081] Figure 12a This is a flowchart depicting an embodiment of a method in a policy control node.

[0082] Figure 12b This is a flowchart depicting an embodiment of a method in a user data node.

[0083] Figure 13 This is a signaling diagram based on the embodiments described herein.

[0084] Figure 14 This is a signaling diagram based on the embodiments described herein.

[0085] Figure 15 These are schematic block diagrams based on embodiments described herein.

[0086] Figure 16 These are schematic block diagrams based on embodiments described herein.

[0087] Figure 17 These are schematic block diagrams based on embodiments described herein.

[0088] Figure 18 These are schematic block diagrams based on embodiments described herein.

[0089] Figure 19 This is a signaling diagram based on the embodiments described herein.

[0090] Figure 20 This is a signaling diagram based on the embodiments described herein.

[0091] Figure 21 This is a schematic block diagram illustrating an embodiment of the first session management node.

[0092] Figure 22 This is a schematic block diagram illustrating an embodiment of the second session management node.

[0093] Figure 23 This is a schematic block diagram illustrating an embodiment of the first access and mobility node.

[0094] Figure 24 This is a schematic block diagram illustrating an embodiment of the second access and mobility node.

[0095] Figure 25 This is a schematic block diagram illustrating an embodiment of the UE.

[0096] Figure 26a This is a schematic block diagram illustrating an embodiment of the strategy and control node.

[0097] Figure 26b This is a schematic block diagram illustrating an embodiment of a user data node.

[0098] Figure 27 An example of a communication system QQ100 according to some embodiments is shown.

[0099] Figure 28 The UE QQ200 is shown according to some embodiments.

[0100] Figure 29 A network node QQ300 is shown according to some embodiments.

[0101] Figure 30 This is a block diagram of a virtualized environment QQ400 in which the functions implemented by some embodiments can be virtualized. Detailed Implementation

[0102] The embodiments described in this paper are based on providing a common anchor, such as UPF and SMF, for DS services from two 3GPP access networks within 5GC. Non-roaming and roaming architectures are discussed. Figure 2-4 As shown in the image. Figure 2 This demonstrates a non-roaming dual-boot architecture. Figure 3 This illustrates a dual-boot architecture with roaming in an access point. Figure 4 This illustrates a dual-boot architecture with roaming in both access points and a common accessed public land mobile network (VPLMN). Figure 5 This illustrates a dual-boot architecture with different VPLMNs that have roaming in both access points.

[0103] The embodiments described herein may have: no access and mobility function (AMF) impact, also known as Alternative 1; and limited AMF impact, also known as Alternative 2.

[0104] Alternative 1 has the following advantages: in the case of roaming, VPLMN does not need to support dual guidance, and only the home PLMN (HPLMN) should support it, but it introduces some limitations, such as: assuming a homogeneous implementation of DS features.

[0105] For each alternative, different aspects were considered, namely registration, policies, subscription information, and session management.

[0106] Registration: During registration, the UE and network include their dual-boot capabilities / support.

[0107] Policy: UE routing policy (URSP), PCC, and ATSSS rules should be enhanced to support DS. Furthermore, the PCC rules should be updated each time either the PLMN or the access type changes.

[0108] Subscription and UE context data in UDM: The following new fields have been added to UDM:

[0109] -DS SUPI is added to the session management subscription, and access and mobility subscription data for both SUPI1 (containing SUPI2) and SUPI2 (containing SUPI1) are also added.

[0110] The -DS association identifier (ID) is used to connect two PDU session requests and is added to the UE context in the SMF data in the UDM / UDR.

[0111] The embodiments described herein can provide methods and signaling for establishing a connection to a data network (DN) using two 3GPP access points and two SUPIs. Furthermore, the embodiments described herein can provide new parameters in the UE subscription data, namely DSSUPI, and new parameters in the UE context in the UDM (DS Association ID). Additionally, the embodiments described herein can provide new fields in the PCC and ATSSS rules, namely the access descriptor, and may also require enhancements in the URSP rules.

[0112] The embodiments described herein are designed to address connections from one or more UEs (such as UEs) in a dual-booting device to a DN using two 3GPP access points. They employ a simple architecture comprising, for example, a single UPF as a PDU session anchor (PSA) and a single SMF, which simplifies the task of PDU session establishment. The embodiments described herein may have no (zero) impact or limited impact on the AMF.

[0113] The embodiments in this document can use a separate field (i.e., DS SUPI) in the SM and MM subscription data, instead of the internal group ID. Group IDs are independently managed objects and are therefore more costly to manage. Furthermore, the embodiments in this document discuss the strategies for introducing new fields into PCC and ATSSS rules and the details of user plane management.

[0114] The embodiments described herein can provide the advantages of a more efficient and simplified mechanism for DS processing and improve the performance of wireless communication networks.

[0115] The embodiments described herein generally relate to wireless communication networks. Figure 6 This is a schematic overview depicting a wireless communication network 100. The wireless communication network 100 includes one or more RANs and one or more CNs. The wireless communication network 100 may use one or more different technologies. The embodiments in this document relate to recent technology trends of particular interest in the NR context; however, the embodiments are also applicable to further developments of existing wireless communication systems, such as 6G, LTE, or WCDMA.

[0116] In wireless communication network 100, user equipment (UE) 121, such as mobile stations, wireless devices, non-access point (non-AP) STAs, STAs, and / or wireless terminals, is communicating with one or more CNs via, for example, one or more access networks (ANs) (e.g., RANs). Those skilled in the art will understand that "UE" is a non-limiting term, referring to any terminal, wireless communication terminal or device, user equipment, narrowband (NB)-Internet of Things (IoT) device, machine-type communication (MTC) device, device-to-device (D2D) terminal or node, such as a smartphone, laptop, mobile phone, sensor, repeater, mobile tablet, or even a small base station capable of communicating with network nodes within an area using radio communication services. UE 121 may also be referred to as a dual-boot device, comprising two UEs independently accessing wireless communication network 100.

[0117] Depending on the radio access technology and terminology used, for example, the wireless communication network 100 includes radio network nodes 101, such as access nodes, access controllers, base stations (e.g., radio base stations, such as gNodeB (gNB), evolved NodeB (eNB, eNode B), NodeB), base transceiver stations, radio remote units, access point base stations, base station routers, wireless local area network (WLAN) access points or access point stations (AP STAs), stand-alone access points, or any other network element or node capable of communicating with a UE within a service area 11 (such as a cell) served by the radio network node 101. The service area 11 may also be referred to as a cell, beam, or beam group of a first radio access technology (RAT) (such as 6G, 5G, LTE, Wi-Fi, or similar technologies). Radio network node 101 may be associated with a first public terrestrial mobile network (PLMN) and / or a first non-public network (NPN).

[0118] The wireless communication network 100 also includes a first session management node 111, a second session management node 112, a policy control node 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 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 a CN. Session management nodes 111 and 112 may, for example, include an SMF. Policy control node 113 may, for example, be a PCC. User data node 114 may, for example, be a UDM. User plane node 115 may, for example, be a UPF. The first and second access and mobility nodes 116 and 117 may, for example, be AMFs. It should be understood that these nodes may be separate nodes or co-located nodes.

[0119] The methods described herein can be executed by a first session management node 111, a second session management node 112, a policy control node 113, a first access and mobility node 116, and a second access and mobility node 117. Alternatively, distributed nodes (DNs) and functions (e.g., included in...) Figure 6 The cloud shown in 190 can be used to perform or partially perform the methods described herein.

[0120] Now we will combine Figure 7 The method according to the embodiments herein is described from the perspective of the first session management node 111. Figure 7 An example embodiment of a method for processing a DS in a wireless communication network 100, performed by a first session management node 111, is depicted. The method includes actions that can be taken in any suitable order. Optional actions are described below. Figure 7 It is presented in a dashed box.

[0121] Action 701

[0122] The first session management node 111 receives a first session context establishment request for establishing a DS session. The first session context establishment request includes a first SUPI associated with UE 121 and a DS association ID. The first SUPI is associated with the first access.

[0123] As mentioned above, the DS association ID can be used to connect (such as associate) sessions or session requests, such as PDU sessions or PDU session requests. The DS association ID can, for example, be added to the UE context in the SMF data within the UDM / UDR (such as User Data Node 114). Therefore, the DS association ID can identify a DS session and / or associate the first and second sessions within a DS session.

[0124] In some embodiments, the first session context establishment request includes a request type parameter indicating that the request type is an initial request. In other words, the first session context establishment request can indicate that the request is an initial request, such as this being the first session context establishment request in the DS session establishment process.

[0125] In some embodiments, the first session management node 111 receives a first session context establishment request from the first access and mobility node 116.

[0126] Action 702

[0127] The first session management node 111 uses the first SUPI, the DS association ID, and the first DS SUPI associated with the first SUPI and / or UE 121 to establish a context for the DS session. The first DS SUPI indicates the second SUPI associated with UE 121.

[0128] The first DS SUPI can indicate the second SUPI associated with UE 121.

[0129] In some embodiments, the first session management node 111 obtains a first DS SUPI associated with the first SUPI and / or 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 obtain the first DS SUPI from the user data node 114, for example, by sending a request indicating the first SUPI and receiving a response including the first DS SUPI.

[0130] Action 703

[0131] The first session management node 111 requests the establishment of a policy association by sending a policy association establishment request to the policy control node 113. This request includes a first SUPI and a first DS SUPI.

[0132] Policy association requests enable policy control node 113 to generate (such as create or establish) one or more policy rules for DS sessions.

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

[0134] Action 704

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

[0136] In some embodiments, registration also registers the DS association ID in the UE context associated with UE 121 in user data node 114.

[0137] Action 705

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

[0139] Action 706

[0140] The first session management node 111 uses the second SUPI, the DS association ID, and the second DS SUPI associated with the second SUPI and / or UE 121 to update the context for the DS session.

[0141] Action 707

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

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

[0144] Establishing a 702 context for a DS session can include any one or more of the following:

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

[0146] The first session management node 111 can associate the DS session with the first SUPI and the first DS SUPI.

[0147] The first session management node 111 can establish a policy association with the policy control node 113 for the DS session by sending a request to the policy control node 113. This request includes a first SUPI and a first DS SUPI. In response to this request, the first session management node 111 can receive one or more policy rules from the policy control node 113.

[0148] The first session management node 111 can establish an N4 session with the user plane function 115.

[0149] The first session management node 111 can register a DS session in the user data node 114 and indicate the DS association ID to the user data node 114.

[0150] Update 704 The context used for a DS session can include any one or more of the following:

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

[0152] The first session management node 111 can update the policy associations used for the DS session by requesting an update to the established policy associations from the policy control node 113. This request includes the second DS SUPI and the second SUPI.

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

[0154] Now we will combine Figure 8 The method according to the embodiments herein is described from the perspective of the second session management node 112. Figure 8 An example embodiment of a method for processing a DS in a wireless communication network 100, performed by a second session management node 111, is depicted. The method includes actions that can be taken in any suitable order. Optional actions are described below. Figure 8 It is presented in a dashed box.

[0155] Action 801

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

[0157] Action 802

[0158] The second session management node 111 uses the DS association ID and the second DS SUPI to obtain the ID of the first session management node 111 associated with the DS session associated with the second DS SUPI. The second DS SUPI is associated with the second SUPI and / or UE 121. The second DS SUPI indicates the first SUPI associated with UE 121.

[0159] Obtaining the ID of the first session management node 111 may include obtaining the second DS SUPI associated with the second SUPI and / or UE 121. The second DS SUPI indicates the first SUPI associated with UE 121.

[0160] Action 803

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

[0162] Now we will combine Figure 9 The method according to the embodiments herein is described from the perspective of the first access and mobility node 116. Figure 9 An example embodiment of a method for processing a DS in a wireless communication network 100, performed by a first access and mobility node 116, is depicted. The method includes actions that can be taken in any suitable order. Optional actions are described below. Figure 9 It is presented in a dashed box.

[0163] Action 901

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

[0165] In some embodiments, the first session establishment request is a DS session establishment request. A DS session establishment request indicates that a DS-enabled session management node will be selected. A first session management request can indicate that it is a DS session establishment request by including the DS association ID in the MM portion of the request. The fact that the first session establishment request is a DS session establishment request can indicate that a DS-enabled session management node will be selected.

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

[0167] Action 902

[0168] The first access and mobility node 116 selects the first session management node 111.

[0169] In some embodiments, selecting the first session management node 111 includes selecting a session management node that supports DS. The access and mobility node 116 may know which session management nodes support DS, for example, through signaling between the first access and mobility node 116 and the session management node and / or through 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 includes a first SUPI and a DS association ID.

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

[0173] The first access and mobility node 116 receives a 901 First Session Establishment Request from UE 121. The First Session Establishment Request includes a first SUPI and a DS association ID associated with UE 121. The first SUPI is associated with the first access.

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

[0175] The first access and mobility node 116 sends a 903 First Session Context Establishment Request to the selected first session management node 111. The First Session Context Establishment Request includes the first SUPI and DS association ID.

[0176] Selecting the first session management node 111 may include selecting a session management node that supports DS.

[0177] Now we will combine Figure 10 The method according to the embodiments herein is described from the perspective of the second access and mobility node 117. Figure 10 An example embodiment of a method for processing DS in a wireless communication network 100, performed by a second access and mobility node 117, is depicted. The method includes actions that can be taken in any suitable order. Optional actions are described below. Figure 10 It is presented in a dashed box.

[0178] Action 1001

[0179] The second access and mobility node 117 receives a second session establishment request from UE 121. The second session establishment request includes a second SUPI and DS association ID associated with UE 121, and optionally, the ID of the DS session associated with the first SUPI associated with UE 121, or a parameter indicating that a PDU session associated with the first SUPI has been established. The second SUPI is associated with the second access. The DS association ID is included in the MM portion and the SM container of the request.

[0180] In some embodiments, the second session establishment also includes the ID of the DS session associated with the first SUPI associated with UE 121.

[0181] In some embodiments, the second session establishment request includes a request type parameter indicating the type of the request as an existing request. In other words, the second session establishment request can indicate that the request is a subsequent request, such as this being the second session establishment request in the DS session establishment process. This can, for example, enable the second access and mobility node 117 to know that the session should be part of a DS session in which the first session has already been established.

[0182] Action 1002

[0183] 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 by the first access and mobility node 116 for the DS session.

[0184] In some embodiments, selecting the first session management node 111 further includes subscription data for UE 121. The subscription data includes a second DS SUPI. The second DS SUPI indicates the first SUPI associated with UE 121. The second access and mobility node 117 can also obtain a list of sessions for UE 121 based on the first SUPI. The session list includes DS sessions. DS sessions may be indicated by an associated ID. The session list may also include the ID of the session management node managing each session.

[0185] In some embodiments, selecting the first session management node 111 further includes using a session list and a DS association ID to obtain an identifier for the first session management node 111. Therefore, the DS association 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.

[0186] Action 1003

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

[0188] In some embodiments, the third session context establishment request may also include the ID of the DS session associated with the first SUPI.

[0189] The second access and mobility node 117 receives a second session establishment request (1001) from UE 121. The second session establishment request includes a second SUPI associated with UE 121, a DS association ID, and optionally, the ID of a DS session associated with a first SUPI associated with UE 121. The second SUPI is associated with the second access.

[0190] The second access and mobility node 117 selects session management nodes 111 and 112. The selected session management nodes 111 and 112 are either the first session management node 110 or the second session management node 112.

[0191] The second access and mobility node 117 sends a session context establishment request (1003) to the selected session management nodes 111 and 112. The session context establishment request includes the second SUPI, the DS association ID, and optionally the ID of the DS session associated with the first SUPI.

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

[0193] In some embodiments, selecting session management nodes 1002 111, 112 includes using a second DS SUPI indicated in the subscription data to obtain the ID of the first session management node 111 associated with the DS session associated with the second DS SUPI. The second DS SUPI is associated with the second SUPI and / or UE 121. The second DS SUPI indicates the first SUPI associated with UE 121.

[0194] Now we will combine Figure 11 The method according to the embodiments herein is described from the perspective of UE 121. Figure 11 An example embodiment of a method for processing DS in a wireless communication network 100, performed by UE 121, is depicted. The method includes actions that can be taken in any suitable order. Optional actions are described below. Figure 11 It is presented in a dashed box.

[0195] Action 1101

[0196] UE 121 sends a first session establishment request to the first access and mobility node 116. The first session establishment request includes a first SUPI and a DS association ID associated with UE 121. The first SUPI is associated with the first access. The DS association ID is included in the first part and the second part of the request.

[0197] In some embodiments, the first part of the request includes the MM portion of the message, and the second part includes the SM container.

[0198] As mentioned above, the DS association ID can be used to connect (such as associate) sessions or session requests, such as PDU sessions or PDU session requests. The DS association ID can, for example, be added to the UE context in the SMF data within the UDM / UDR (such as User Data Node 114). Therefore, the DS association ID can identify a DS session and / or associate the first and second sessions within a DS session.

[0199] 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 will be selected.

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

[0201] Action 1102

[0202] UE 121 sends a second session establishment request to the second access and mobility node 117. The second session establishment request includes a second SUPI and a DS association ID associated with UE 121. The second SUPI is associated with a second access that is different from the first access, wherein the DS association ID is included (such as being contained or included) in the first part and the second part of the request.

[0203] In some embodiments, the first part of the request includes the MM portion of the message, and the second part includes the SM container.

[0204] In some embodiments, the second session establishment request includes a request type parameter indicating the type of the request as an existing session (such as an existing PDU session). In other words, the second session establishment request can indicate that the request is a subsequent request, such as this being the second session establishment request in the DS session establishment process. This can, for example, enable the second access and mobility node 117 to know that the session should be part of a DS session in which the first session has already been established.

[0205] UE 121 sends a 1101 First Session Establishment Request to the First Access and Mobility Node 116. The First Session Establishment Request includes a First SUPI and a DS Association ID associated with UE 121. The First SUPI is associated with the First Access.

[0206] UE 121 sends a second session establishment request (1102) to the second access and mobility node 117. The second session establishment request includes a second SUPI associated with UE 121, a DS association ID, and an optional ID of the DS session associated with the first SUPI. The second SUPI is associated with a second access that is different from the first access.

[0207] Now we will combine Figure 12a The method according to the embodiments herein is described from the perspective of policy control node 113. Figure 12a An example embodiment of a method for processing DS in a wireless communication network 100, executed by a policy control node 113, is depicted. The method includes actions that can be taken in any suitable order. Optional actions are described below. Figure 12a It is presented in a dashed box.

[0208] Action 1201

[0209] Policy control node 113 establishes a policy association with first session management node 111 for a DS session by receiving a request from first session management node 111. This request includes a first SUPI and a first DS SUPI. The establishment involves creating one or more policy rules by considering the first SUPI and the first DS SUPI.

[0210] In some embodiments, one or more policy rules include any one or more of URSP rules, PCC rules, and ATSSS rules.

[0211] In some embodiments, the URSP rule includes a DS indication, the PCC rule includes an access descriptor indicating an access type (such as first access), and / or the ATSSS rule includes an access descriptor indicating an access type (such as first access).

[0212] Action 1202

[0213] Policy control node 113 provides one or more policy rules for DS sessions to first session management node 111.

[0214] Policy node 113 may provide one or more policy rules to first session management node 111, for example, by sending one or more policy rules to first session management node 111.

[0215] Action 1203

[0216] Policy control node 113 updates the policy association with first session management node 111 for the DS session by receiving requests (such as policy association modification requests) from first session management node 111. The request includes a second SUPI and a second DSSUPI. The update involves updating one or more policy rules by taking into account the second SUPI and the second DSSUPI.

[0217] In some embodiments, the update policy association includes any one or more of the update URSP rule, PCC rule, and ATSSS rule.

[0218] In some embodiments, updating PCC rules and / or ATSS rules includes adding an access type (such as a second access) associated with the second SUPI.

[0219] Action 1204

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

[0221] Policy node 113 may provide one or more updated policy rules to first session management node 111, for example, by sending one or more updated policy rules to first session management node 111.

[0222] Policy control node 113 establishes a policy association between itself and first session management node 111 for DS session 1201 by receiving a request from first session management node 111. This request includes a first SUPI and a first DS SUPI. The establishment involves creating one or more policy rules by considering the first SUPI and the first DS SUPI.

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

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

[0225] Policy control node 113 provides one or more policy rules for DS sessions to first session management node 111.

[0226] Now we will combine Figure 12b The method according to the embodiments herein is described from the perspective of user data node 114. Figure 12bAn example embodiment of a method for processing DS in a wireless communication network 100, performed by a user data node 114, is depicted. The method includes actions that can be taken in any suitable order. Optional actions are described below. Figure 12b It is presented in a dashed box.

[0227] Action 1301

[0228] User data node 114 provides subscription data associated with the first SUPI and / or UE 121 to the first session management node 111. The subscription data includes a first DS SUPI indicating a second SUPI associated with UE 121.

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

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

[0231] Action 1302

[0232] User data node 114 registers a DS session by receiving a registration message indicating the DS association ID from the first session management node 111.

[0233] In some embodiments, registering a DS session includes registering a DS association ID in the UE context associated with the first SUPI and / or UE 121. Registering a DS session may also include associating the DS session with the DS association ID.

[0234] Action 1303

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

[0236] In some embodiments, providing subscription data for the UE (121) includes receiving a request for obtaining subscription data from a first access and mobility node 117 or a 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. The request includes a second SUPI. Providing a session list includes receiving a request from the second access and mobility node 117, and sending a session list to the second access and mobility node 117 or the second session management node 112. The request for the session list includes a first SUPI.

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

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

[0239] Action 1304

[0240] In some embodiments, user data node 114 provides subscription data associated with a second SUPI and / or UE 121 to a first session management node 111. The subscription data includes a second DSSUPI indicating a first SUPI associated with UE 121.

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

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

[0243] The embodiments described herein, such as those mentioned above, will now be further described and illustrated. The following text applies to the embodiments described herein and may be combined with any suitable embodiments described above.

[0244] Different aspects of this topic will be explained further in different sections, namely registration, policies, and session management.

[0245] register

[0246] Alt 1 (Alternative 1): No AMF impact: No impact on the registration process.

[0247] Alt 2 (Alternative 2): Limited AMF impact: in 3GPP TS 23.502 v18.3.0 Figure 4 In step 21 of .2.2.2.2-1, the AMF may use the new parameter “Support for DS” in the initial registration acceptance message to the UE to indicate, for example, the accessed network’s support for the DS PDU session.

[0248] Strategy

[0249] This section applies to the two alternatives mentioned above, Alt 1 and Alt 2.

[0250] URSP Rules: To support the establishment of DS PDU sessions, the URSP rules for DS have been extended. Specifically, the access type preference in the routing descriptor has been extended to include a dual-booting indication.

[0251] PCC Rules: For DS, the scope of study does not include data segmentation, and therefore, the permitted bootstrapping modes are Active-Standby and Minimal Delay (the bootstrapping mode (Active-Active) for data segmentation may be added in the future). For Active-Standby mode, the access type and the connected PLMN may be important. Therefore, the MAPDU session control section of the PCC rules is enhanced as follows, and is shown in underlined italics in Table 2.7.1.2-1 below:

[0252] A new field, Access Descriptor, has been added to the PCC rule. It consists of a 4-tuple (Access1-Type, Access1-PLMN-ID, Access2-Type, Access2-PLMN-ID) that identifies Access1 and Access2. The Access Type can be one of the following: T-NR, GEO, LEO, LTE, Non-3GPP, or Other.

[0253] - The field billing / monitoring key for non-3GPP access has been expanded to include the billing / monitoring key for access 2.

[0254] Table 2.7.1.2-1: Enhancements to PCC rules for dual-booting

[0255]

[0256] The PCF should subscribe to changes in RAT, access type, and PLMN from the SMF for SUPI1 and SUPI2, and it can update PCC rules based on notifications.

[0257] ATSSS Rule: To implement the DS policy in the UL direction, the ATSSS rule is enhanced with new access descriptor parameters. This is the same 4-tuple described in Table 6.1.Y.1.4-1, which guides the DS device to identify which of the accesses is access 1 and which is access 2, and is shown in underlined italics in Table 2.7.1.2-2 below.

[0258] Table 2.7.1.2-2: ATSSS rule structure for supporting DS

[0259]

[0260] N4 rule (reuse of current standard): The same mechanism used for MA PDU sessions can be implemented for DS PDU sessions, i.e., SMF generates two FARs that direct services to two access points, and one MAR that points to one of the FARs depending on whether the active or standby path is selected for downlink services (in active-standby mode).

[0261] Based on the impact on AMF, two alternatives were considered for creating DS PDU sessions.

[0262] Alternative Option 1: No AMF Impact

[0263] The following steps are in Figure 13 As shown in the image.

[0264] Step 1: UE1 uses SUPI1 to register with 5GC via AMF1 and receive DS URSP rules.

[0265] Step 2. UE1 sends a PDU session establishment request with an initial request type using SUPI1, and includes a new parameter DS association ID in the N1SM container. The DS association ID is generated by the DS device and should uniquely identify the DSPDU session across the two UEs.

[0266] Step 3. AMF selects SMF1 according to the current specification. Here, all SMFs supporting the requested DNN / S-NSSAI assume isomorphic implementations of DS. Therefore, AMF does not consider the ability of SMFs to support DS.

[0267] Step 4: AMF sends an Nsmf_PDUSession_CreateSMContext (Nsmf_PDU session_createSM context) request to SMF1.

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

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

[0270] Step 7. SMF1 establishes an N4 session with UPF. N4 rules are generated similarly to those in the SMF and MA PDU sessions.

[0271] Step 8. The SMF registers the PDU session with the UDM. Additionally, it registers the DS association ID as a new field in the UE context within the SMF data.

[0272] Step 9: If the DS device has not yet been registered using SUPI2 via the second access, it registers and receives DS URSP rules in this step.

[0273] Editor's Note: How step 9 is triggered is assumed to be solved by other solutions.

[0274] Step 10: This step is the same as Step 2, but with new parameters in the SM container. An existing DS PDU indicates that a PDU session for SUPI1 has been created. The dual-boot device sends the same DS association ID and the same DNN / S-NSSAI as in Step 2.

[0275] Step 11. AMF2 selects SMF (SMF2) based on the current mechanism.

[0276] Step 12. AMF sends an Nsmf_PDUSession_CreateSMContext (Nsmf_PDU Session_CreateSMContext) request to SMF2. In this step, SMF2 checks if a PDU session corresponding to the SUPI2 and DS association ID exists. If so, steps 13-16 are skipped (the same applies to SMF2 and SMF1).

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

[0278] Step 14: SMF uses SUPI1 to obtain a list of PDU sessions from UDM, and then uses DS associated ID to obtain the SMF ID of SMF1.

[0279] Step 15: SMF sends a redirect response to AMF and provides the SMF1 ID.

[0280] Step 16: Similar to step 4.

[0281] Step 17: Similar to step 5.

[0282] Step 18: The SMF triggers an SM policy association update request to update the policy information used for the PDU session, including DSSUPI (SUPI1). The PCF can modify the PCC rules based on the access type and PLMN of SUPI2.

[0283] Step 19: The SMF modifies the N4 rule to establish an additional N3 / N9 tunnel between the second access point and the UPF.

[0284] Step 20. With 3GPP TS 23.502 v18.3.0 Figure 4 Steps 11-21 of .3.2.2.1-1 are the same, except that in step 16c, the SMF includes the DS association ID in the registration of the PDU session, as in step 8.

[0285] Alternative Option 2: Limited AMF Impact

[0286] The following steps are in Figure 14 As shown in the image.

[0287] Step 1: UE1 uses SUPI1 to register with 5GC via AMF1 and receive DS URSP rules.

[0288] Step 2: UE1 sends a PDU session establishment request of type Initial Request, and includes the DS association ID in the MM part of the NAS message and the SM container.

[0289] Step 3: Select an SMF that supports DS functionality in the AMF.

[0290] Step 4: See the reference above. Figure 13 Steps 4-9 are described.

[0291] Step 5: UE2 sends a PDU session establishment request of type Existing PDU Session, including the DS association ID in the MM part of the NAS message and the SM container. Since Existing PDU Session is selected for the request type, existing DSPDU parameters are not required.

[0292] • Step 6: AMF2 uses the DS SUPI field from the access and mobility subscription data to discover SUPI1 and uses it to obtain the list of PDU sessions from UDM1. Then, it obtains the SMF ID of SMF1 by using the DS association ID.

[0293] • Step 7: See the reference above. Figure 13 Steps 16-20 are described.

[0294] Since AMF2 directly selects SMF1, the SMF redirection steps (steps 12-15) are skipped.

[0295] As an example, a new request type, DS session request, can be used in the above PDU session establishment request.

[0296] Changes to the proposal regarding ? ?

[0297]

[0298] 6 solutions

[0299] The mapping from the 6.0 solution to the key issues is shown in underlined italics.

[0300] Table 6.0-1: Mapping of Dual-Booting Solutions to Key Issues

[0301]

[0302] Table 6.0-2: Mapping of ATSSS_Ph4 Solution to Key Issues

[0303]

[0304]

[0305] Solution 6.1.Y #1.Y: Supports dual-boot connections via ATSSS

[0306] 6.1.Y.1 General Description

[0307] 6.1.Y.1.1 Introduction

[0308] The proposed solution is based on the following principles:

[0309] • The impact on the AMF is zero or minimal. This allows the DS function to be enabled when only the HPLMN supports it and the VPLMN can remain unchanged or requires minimal enhancements to the AMF. Here, we propose two alternatives:

[0310] ○Alternative 1: No AMF impact: This alternative is based on SMF redirection and requires an isomorphic implementation of SMF for DNN / S-NSSAI DS.

[0311] ○ Alternative 2: Limited AMF impact: This alternative enables non-isomorphic implementations of SMF that support DS.

[0312] • This solution treats both SUPIs the same way; for example, either of the two SUPIs can be used to register first or request the establishment of a PDU session.

[0313] • This solution treats the DS device as acting as one or two UEs facing the network, but does not discuss the UE architecture. Requirements for the DS device are listed in the Impact section.

[0314] • Service switching and bootstrapping are based on ATSSS functionality with public SMF and UPF.

[0315] • UPF treats DS PDU sessions in the same way as MA PDU sessions. However, the establishment and management of DS PDU sessions differ from that of MA PDU sessions.

[0316] 6.1.Y.1.2 Architecture

[0317] This solution is based on providing a common anchor (UPF) and SMF for DS services from two 3GPP access networks within 5GC. The non-roaming and roaming architectures are shown below.

[0318] Figure 15 This demonstrates a non-roaming dual-boot architecture.

[0319] Figure 16 This illustrates a dual-boot architecture with roaming in an access point.

[0320] Figure 17 This illustrates a dual-boot architecture with roaming in two access points with a common VPN.

[0321] Figure 18 This illustrates a dual-boot architecture with roaming in two accesses with two different VPLMNs.

[0322] 6.1.Y.1.3 Registration

[0323] Alternative Option 1: No AMF Impact: It has no impact on the registration process.

[0324] Alternative 2: Limited AMF impact: AMF can indicate network support for DS PDU sessions in the initial registration acceptance message to the UE.

[0325] 6.1.Y.1.4 Strategy

[0326] URSP rules: To support the establishment of DS PDU sessions, URSP rules have been extended. Specifically, the access type preference in the routing descriptor has been extended to include dual-booting indication.

[0327] PCC Rules: Considering that data segmentation is not supported, the allowed bootstrapping modes are Active-Standby and Minimum Latency. For Active-Standby mode, the access type and the PLMN of the connection may be important. Therefore, the session control section of the MA PDU in the PCC rules is enhanced as follows:

[0328] A new field, Access Descriptor, has been added to the PCC rule. It consists of a 4-tuple (Access 1-Type, Access 1-PLMN-ID, Access 2-Type, Access 2-PLMN-ID) to identify Access 1 and Access 2. The Access Type can be one of the following: T-NR, GEO, LEO, LTE, Non-3GPP, or Other.

[0329] -

[0330] - The field used for non-3GPP access billing / monitoring keys has been expanded to include billing / monitoring keys used for access 2.

[0331] Table 6.1.Y.1.4-1: Enhancements to PCC rules for dual-booting

[0332]

[0333] The PCF should subscribe to changes in RAT, access type, and PLMN from the SMF for both SUPI1 and SUPI2, and it can update PCC rules based on notifications.

[0334] ATSSS Rule: To implement the DS policy in the UL direction, the ATSSS rule is enhanced with new access descriptor parameters. This is the same 4-tuple described in Table 6.1.Y.1.4-1, and it guides the DS device to identify which of the accesses is access 1 and which is access 2.

[0335] Table 6.1.Y.1.4-2: ATSSS rule structure for supporting DS

[0336]

[0337] N4 rule: The same mechanism used for MA PDU sessions can be implemented for DS PDU sessions, i.e., SMF generates two FARs that route services to two access points, and one MAR that points to one of the FARs depending on whether the active or standby path is selected for downlink services (in active-standby mode).

[0338] Note: How to guide the DS device to connect to the additional 3GPP access is assumed to be covered by other solutions.

[0339] 6.1.Y.1.5 Subscription and UE Context Data in UDM / UDR

[0340] The connection between the two SUPIs is maintained in the UDM. For this purpose, a new field, DS SUPI, has been added to the session management subscription data for both SUPI1 (containing SUPI2) and SUPI2 (containing SUPI1). Additionally, for Alternative 2, the same field is added to the access and mobility subscription data for both SUPIs.

[0341] A new parameter, DS Association ID (see Clause 6.1.Y.1.7), used to connect two PDU session requests, is added to the UE context in the SMF data of the UDM / UDR.

[0342] The following procedure describes how to use these new parameters.

[0343] 6.1.Y.1.6 Session Management

[0344] This solution is based on creating DS PDU sessions, which are anchored in a public UPF and managed by a public SMF. To achieve this:

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

[0346] • In the PDU session establishment request, the UE provides a new parameter (DS association ID) to identify which two PDU session requests correspond to the same DS PDU session.

[0347] • Both AMFs choose the same (H-)SMF. To achieve this, two alternatives have been proposed:

[0348] ○Alternative 1: No AMF impact: The selection of the public SMF is done via HPTT redirection, requested by the SMF.

[0349] Alternative 2: Limited AMF Impact: The selection of the public SMF is made by matching the DS-associated IDs of the AMF.

[0350] 6.1.Y.2 Process

[0351] 6.1.Y.2.1 Session Management

[0352] Based on the impact on AMF, two alternatives were considered for creating DS PDU sessions.

[0353] 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 HPLMN, it can be assumed that the subscription data of the two SUPIs are managed in a single UDM.

[0354] Alternative Option 1: No AMF impact:

[0355] Figure 19 This illustrates the establishment of a dual-boot PDU session according to Alternative Solution 1.

[0356] Step 1: UE1 uses SUPI1 to register with 5GC via AMF1 and receive DS URSP rules.

[0357] Step 2. UE1 sends a PDU session establishment request with an initial request type using SUPI1, and includes a new parameter DS association ID in the N1SM container. The DS association ID is generated by the DS device and should uniquely identify the DSPDU session across the two UEs.

[0358] Step 3. AMF selects SMF1 according to the current specification. Here, all SMFs supporting the requested DNN / S-NSSAI assume isomorphic implementations of DS. Therefore, AMF does not consider the ability of SMFs to support DS.

[0359] Step 4: AMF sends an Nsmf_PDUSession_CreateSMContext (Nsmf_PDU Session_CreateSMContext) request to SMF1.

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

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

[0362] Step 7. SMF1 establishes an N4 session with UPF. N4 rules are generated similarly to those in the SMF and MA PDU sessions.

[0363] Step 8. SMF registers the PDU session with UDM. Additionally, it includes the DS association ID as a new parameter in the registration request.

[0364] Step 9: If the DS device has not yet been registered using SUPI2 via the second access, it registers and receives DS URSP rules in this step.

[0365] Editor's Note: How step 9 is triggered is assumed to be solved by other solutions.

[0366] Step 10: This step is the same as Step 2, except that the SM container has a new parameter "Existing DS PDU", which indicates that a PDU session for SUPI1 has been created. The dual-boot device sends the same DS association ID and the same DNN / S-NSSAI as in Step 2.

[0367] Step 11. AMF2 selects SMF (SMF2) based on the current mechanism.

[0368] Step 12. AMF sends an Nsmf_PDUSession_CreateSMContext (Nsmf_PDU Session_CreateSMContext) request to SMF2. In this step, SMF2 checks if a PDU session corresponding to the SUPI2 and DS association ID exists. If so, steps 13-16 are skipped (the same applies to SMF2 and SMF1).

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

[0370] Step 14: SMF2 uses SUPI1 to obtain the PDU session list from UDM, and then uses DS associated ID to obtain the SMF ID of SMF1.

[0371] Step 15: SMF sends a redirect response to AMF and provides the SMF1 ID.

[0372] Step 16: Same as step 4.

[0373] Step 17: Similar to step 5.

[0374] Step 18: The SMF triggers an SM policy association update request to update the policy information used for the PDU session, including DSSUPI (SUPI1). The PCF can modify the PCC rules based on the access type and PLMN of SUPI2.

[0375] Step 19: The SMF modifies the N4 rule to establish an additional N3 / N9 tunnel between the second access point and the UPF.

[0376] Step 20. With TS 23.502 [4] Figure 4Steps 11-21 of .3.2.2.1-1 are the same, except that in step 16c, the SMF includes the DS association ID in the registration of the PDU session, as in step 8.

[0377] Alternative Option 2: Limited AMF Impact

[0378] Figure 20 This illustrates the establishment of a dual-boot PDU session according to Alternative Solution 2.

[0379] • Step 1: UE1 uses SUPI1 to register with 5GC via AMF1 and receive DS URSP rules.

[0380] • Step 2: UE1 sends a PDU session establishment request of type Initial Request, and includes the DS association ID in the MM part of the NAS message and the SM container.

[0381] • Step 3: Select an SMF that supports DS functionality in the AMF.

[0382] • Step 5: UE2 sends a PDU session establishment request of type Existing PDU Session, including the DS association ID in the MM part of the NAS message and the SM container. Since Existing PDU Session is selected for the request type, existing DSPDU parameters are not required.

[0383] • Step 6: AMF2 uses the DS SUPI field in the access and mobility subscription data to discover SUPI1, obtains the UE context in the SMF data for SUPI1 from the UDM, and selects SMF1 based on the DS association ID.

[0384] • Step 7: Since AMF2 directly selects SMF1, the SMF redirection steps (steps 12-15) are skipped.

[0385] 6.1.Y.2.2 Interoperability with EPS:

[0386] In order to interoperate with EPS, follow the... Figure 6 The same mechanism as in .1.Y.2.1-1 has the following differences:

[0387] •Except in Figure 6 In addition to registering the PDU session for SUPI1 in step 8 of .1.Y.2.1-1, SMF1+PGW-C1 also registers the PDU session for SUPI2 in the HSS.

[0388] •exist Figure 6In step 11 of .1.Y.2.1-1, the MME directly selects SMF1+PGW-C1 according to the current specification because the PDU session is registered for SUPI2 using the same DNN / APN. Therefore, the SMF redirection step (steps 12-15) in Alternative 1 is skipped.

[0389] 6.1.Y.4 Impact

[0390] DS devices: should be registered using two separate SUPIs, and ATSSS functionality (bootstrapping and switching) should be handled across two PDU sessions associated with the two SUPIs. A unique DS association ID should be available in the N1 SM container within the PDU session establishment request for both SUPIs.

[0391] AMF: No impact on Alternative 1. For Alternative 2: Select an SMF with DS capabilities, based on the DS associated ID. S provides an indication of support for DS PDU sessions in the initial registration acceptance message.

[0392] UPF: No impact. Existing support for MA PDU sessions is reused.

[0393] SMF: Invoke HTTP redirection upon receiving a PDU session establishment request (Alternative 1). Create N4 and ATSSS rules for the DS PDU session.

[0394] UDM / UDR: Add a new parameter DS SUPI to the UE SM subscription data. Add a new parameter DS association ID to the PDU session context.

[0395] PCF: Creates PCC rules using dual-boot information.

[0396]

[0397] To perform the above-described method actions, the first session management node 111 is configured to process the DS in the wireless communication network 100. The first session management node 111 may include... Figure 21 The layout depicted in the text.

[0398] The first session management node 111 may include input and output interfaces 2100 configured to communicate with each other. The input and output interfaces 2100 may include a receiver (e.g., wired and / or wireless) (not shown) and a transmitter (e.g., wired or wireless) (not shown).

[0399] The embodiments described herein can be implemented using a corresponding processor or one or more processors, such as Figure 11The first session management node 111 depicted herein includes at least one processor 2110 of the processing circuitry, and computer program code for performing the functions and actions of the embodiments herein. The aforementioned program code may also be provided as a computer program product, for example, in the form of a data carrier carrying computer program code for executing the embodiments herein when loaded into the first session management node 111. One such carrier may be in the form of a CD-ROM. However, other data carriers such as memory sticks are feasible. The computer program code may also be provided as plain program code on a server and downloaded to the first session management node 111.

[0400] The first session management node 111 and / or processor 2110 are configured, for example, to process DS in the wireless communication network (100).

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

[0402] The first session management node 111 and / or processor 2110 are configured to establish a context for a DS session using a first SUPI, a DS association ID, and a first DS SUPI associated with the first SUPI and / or UE 121. The first DS SUPI indicates a second SUPI associated with UE 121.

[0403] The first session management node 111 and / or processor 2110 are configured to request the establishment of a policy association by sending a policy association establishment request to the policy control node 113. This request is suitable to include a first SUPI and a first DS SUPI.

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

[0405] The first session management node 111 and / or processor 2110 are configured to update the context for the DS session using the second SUPI, the DS association ID, and the second DS SUPI associated with the second SUPII and / or UE (121).

[0406] The first session management node 111 and / or processor 2110 are configured to update policy associations by sending a policy association modification request to the policy control node 113. This request is suitable for including a second SUPI and a second DS SUPI.

[0407] 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.

[0408] In some embodiments, the DS association ID is suitable for identifying a DS session.

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

[0410] In some embodiments, establishing a context is adapted to include obtaining subscription data for UE 121. The subscription data is adapted to include DS SUPI.

[0411] In some embodiments, establishing a context is adapted to include associating a DS session with a first SUPI and a second SUPI indicated in the DS SUPI.

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

[0413] In some embodiments, registration is also adapted to register the DS association ID in the UE context associated with the UE (121) in the user data node (114).

[0414] The first session management node 111 may also include a corresponding memory 2120, which includes one or more memory cells. The memory 2120 includes instructions executable by the processor 2110 in the first session management node 111.

[0415] The memory 2120 is arranged to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, streams, policies, session SUPIs, IDs, and applications to execute the methods described herein when executed in the first session management node 111.

[0416] In some embodiments, the computer program 2130 includes instructions that, when executed by at least one processor 2110, cause at least one processor 2110 of the first session management node 111 to perform the aforementioned actions.

[0417] In some embodiments, the corresponding carrier 2140 includes a corresponding computer program 2130, wherein the carrier 2140 is one of electronic signals, optical signals, electromagnetic signals, magnetic signals, electrical signals, radio signals, microwave signals, or computer-readable storage media.

[0418] Therefore, the embodiments described herein may disclose a first session management node 111 configured to process a DS in a wireless communication network 100. The first session management node 111 includes a processor 2110 and a memory 2120, the memory 2120 including instructions executable by the processor 2110, thereby enabling the first session management node 111 to operate to perform any of the methods described herein.

[0419] Those familiar with communication design will readily understand that functional devices or modules can 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 can 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. For example, some of the functions may be implemented on a processor shared with other functional components of a radio network node.

[0420] Alternatively, some of the functional elements of the processing apparatus discussed may be provided using dedicated hardware, while other functional elements may be provided with hardware associated with appropriate software or firmware for executing the software. Therefore, the terms "processor" or "controller" as used herein do not exclusively refer to hardware capable of executing software and may implicitly include, but are not limited to, 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 conventional and / or custom hardware may also be included. Designers of communication receivers will understand the inherent cost, performance, and maintenance trade-offs in these design choices.

[0421] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, and other digital hardware, including digital signal processors (DSPs), application-specific digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more techniques described herein. In some implementations, according to one or more embodiments of this disclosure, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions.

[0422] To perform the above-described method actions, the second session management node 112 is configured to process the DS in the wireless communication network 100. The second session management node 112 may include... Figure 22 The layout depicted in the text.

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

[0424] The embodiments described herein can be implemented using a corresponding processor or one or more processors, such as Figure 11 The second session management node 112 depicted herein includes at least one processor 2210 of the processing circuitry, and computer program code for performing the functions and actions of the embodiments described herein. The program code mentioned above may also be provided as a computer program product, for example, in the form of a data carrier carrying computer program code for executing the embodiments described herein when loaded into the second session management node 112. One such carrier may be in the form of a CD-ROM. However, other data carriers such as memory sticks are feasible. The computer program code may also be provided as plain program code on a server and downloaded to the second session management node 112.

[0425] The second session management node 112 and / or processor 2210 are configured, for example, to process DS in the wireless communication network (100).

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

[0427] The second session management node 112 and / or processor 2210 are configured to use the DS association ID and the second DS SUPI to obtain the ID of the first session management node (111) associated with 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).

[0428] The second session management node 112 and / or processor 2210 are configured to request the redirection of the DS session to the first session management node (111) by sending a redirection message to the second access and mobility node (117). The redirection message includes the ID of the first session management node (111).

[0429] The second session management node 112 may also include a corresponding memory 2220, which includes one or more memory cells. The memory 2220 includes instructions executable by the processor 2210 in the second session management node 112.

[0430] The memory 2220 is arranged to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, streams, policies, session SUPIs, IDs, and applications to execute the methods described herein when executed in the second session management node 112.

[0431] In some embodiments, the computer program 2230 includes instructions that, when executed by at least one processor 2210, cause at least one processor 2210 of the second session management node 112 to perform the aforementioned actions.

[0432] In some embodiments, the corresponding carrier 2240 includes a corresponding computer program 2230, wherein the carrier 2240 is one of electronic signals, optical signals, electromagnetic signals, magnetic signals, electrical signals, radio signals, microwave signals, or computer-readable storage media.

[0433] Therefore, embodiments herein may disclose a second session management node 112 configured to process a DS in a wireless communication network 100. The second session management node 112 includes a processor 2210 and a memory 2220, the memory 2220 including instructions executable by the processor 2210, thereby enabling the second session management node 112 to perform any of the methods described herein.

[0434] Those familiar with communication design will readily understand that functional devices or modules can 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 can 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. For example, some of the functions may be implemented on a processor shared with other functional components of a radio network node.

[0435] Alternatively, some of the functional elements of the processing apparatus discussed may be provided using dedicated hardware, while other functional elements may be provided with hardware associated with appropriate software or firmware for executing the software. Therefore, the terms "processor" or "controller" as used herein do not exclusively refer to hardware capable of executing software and may implicitly include, but are not limited to, 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 conventional and / or custom hardware may also be included. Designers of communication receivers will understand the inherent cost, performance, and maintenance trade-offs in these design choices.

[0436] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, and other digital hardware, including digital signal processors (DSPs), application-specific digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more techniques described herein. In some implementations, according to one or more embodiments of this disclosure, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions.

[0437] To perform the above-described method actions, the first access and mobility node 116 is configured to process the DS in the wireless communication network 100. The first access and mobility node 116 may include... Figure 23 The layout depicted in the text.

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

[0439] The embodiments described herein can be implemented using a corresponding processor or one or more processors, such as Figure 23 The first access and mobility node 116 depicted herein includes at least one processor 2310 of the processing circuitry, and 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 example, in the form of a data carrier carrying computer program code for performing the embodiments herein when loaded into the first access and mobility node 116. One such carrier may be in the form of a CD-ROM. However, the use of other data carriers such as memory sticks is feasible. The computer program code may also be provided as plain program code on a server and downloaded to the first access and mobility node 116.

[0440] The first access and mobility node 116 and / or processor 2310 are configured to receive a first session establishment request from UE 121. The first session establishment request includes a first SUPI and a DS association ID associated with UE 121. The first SUPI is associated with the first access. The DS association ID is included in the MM portion of the request and the SM container of the request.

[0441] The first access and mobility node 116 and / or processor 2310 are configured to select the first session management node 111.

[0442] The first access and mobility node 116 and / or processor 2310 are 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 include a first SUPI and DS association ID.

[0443] In some embodiments, selecting a first session management node 111 is adapted to include selecting a session management node that supports DS.

[0444] 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 will be selected.

[0445] The first access and mobility node 116 may also include a corresponding memory 2320, which includes one or more memory cells. The memory 2320 includes instructions executable by the processor 2310 in the first access and mobility node 116.

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

[0447] In some embodiments, the computer program 2330 includes instructions that, when executed by at least one processor 2310, cause at least one processor 2310 of the first access and mobility node 116 to perform the aforementioned actions.

[0448] In some embodiments, the corresponding carrier 2340 includes a corresponding computer program 2330, wherein the carrier 2340 is one of electronic signals, optical signals, electromagnetic signals, magnetic signals, electrical signals, radio signals, microwave signals, or computer-readable storage media.

[0449] Therefore, the embodiments described herein may disclose a first access and mobility node 116 configured to process a DS in a wireless communication network 100. The first access and mobility node 116 includes a processor 2310 and a memory 2320, the memory 2320 including instructions executable by the processor 2310, thereby enabling the first access and mobility node 116 to perform any of the methods described herein.

[0450] Those familiar with communication design will readily understand that functional devices or modules can 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 can 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. For example, some of the functions may be implemented on a processor shared with other functional components of a radio network node.

[0451] Alternatively, some of the functional elements of the processing apparatus discussed may be provided using dedicated hardware, while other functional elements may be provided with hardware associated with appropriate software or firmware for executing the software. Therefore, the terms "processor" or "controller" as used herein do not exclusively refer to hardware capable of executing software and may implicitly include, but are not limited to, 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 conventional and / or custom hardware may also be included. Designers of communication receivers will understand the inherent cost, performance, and maintenance trade-offs in these design choices.

[0452] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, and other digital hardware, including digital signal processors (DSPs), application-specific digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more techniques described herein. In some implementations, according to one or more embodiments of this disclosure, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions.

[0453] To perform the above-described method, the second access and mobility node 117 is configured to process the DS in the wireless communication network 100. The second access and mobility node 117 may include... Figure 24 The layout depicted in the text.

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

[0455] The embodiments described herein can be implemented using a corresponding processor or one or more processors, such as Figure 24The second access and mobility node 117 depicted herein includes at least one processor 2410 of the processing circuitry, and 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 example, in the form of a data carrier carrying computer program code for performing the embodiments herein when loaded into the second access and mobility node 117. One such carrier may be in the form of a CD-ROM. However, the use of other data carriers such as memory sticks is feasible. The computer program code may also be provided as plain program code on a server and downloaded to the second access and mobility node 117.

[0456] The second access and mobility node 117 and / or processor 2410 are configured to receive a second session establishment request from UE 121. The second session establishment request is adapted to include a second SUPI and a DS association ID associated with UE 121. The second SUPI is associated with the second access. The DS association ID is adapted to be included in the MM portion of the request and the SM container of the request.

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

[0458] The second access and mobility node 117 and / or processor 2410 are configured to send a session context establishment request to the selected first session management node 111. The session context establishment request includes a second SUPI and a DS association ID.

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

[0460] In some embodiments, selecting the first session management node 111 is further adapted to include obtaining subscription data for UE 121. The subscription data is adapted to include a second DS SUPI. The second DS SUPI is adapted to indicate the first SUPI associated with UE 121.

[0461] In some embodiments, selecting the first session management node 111 is also adapted to include obtaining a list of sessions for UE 121 based on the first SUPI.

[0462] In some embodiments, selecting the first session management node 111 is also adapted to include using a session list and a DS association ID to obtain the identifier of the first session management node 111.

[0463] The second access and mobility node 117 may also include a corresponding memory 2420, which includes one or more memory cells. The memory 2420 includes instructions executable by the processor 2410 in the second access and mobility node 117.

[0464] The memory 2420 is arranged to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, streams, policies, session SUPIs, IDs, and applications to execute the methods herein when performed in the second access and mobility node 117.

[0465] In some embodiments, the computer program 2430 includes instructions that, when executed by at least one processor 2410, cause at least one processor 2410 of the second access and mobility node 117 to perform the aforementioned actions.

[0466] In some embodiments, the corresponding carrier 2440 includes a corresponding computer program 2430, wherein the carrier 2440 is one of electronic signals, optical signals, electromagnetic signals, magnetic signals, electrical signals, radio signals, microwave signals, or computer-readable storage media.

[0467] Therefore, the embodiments described herein may disclose a second access and mobility node 117 configured to process a DS in a wireless communication network 100. The second access and mobility node 117 includes a processor 2410 and a memory 2420, the memory 2420 including instructions executable by the processor 2410, thereby enabling the second access and mobility node 117 to operate to perform any of the methods described herein.

[0468] Those familiar with communication design will readily understand that functional devices or modules can 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 can 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. For example, some of the functions may be implemented on a processor shared with other functional components of a radio network node.

[0469] Alternatively, some of the functional elements of the processing apparatus discussed may be provided using dedicated hardware, while other functional elements may be provided with hardware associated with appropriate software or firmware for executing the software. Therefore, the terms "processor" or "controller" as used herein do not exclusively refer to hardware capable of executing software and may implicitly include, but are not limited to, 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 conventional and / or custom hardware may also be included. Designers of communication receivers will understand the inherent cost, performance, and maintenance trade-offs in these design choices.

[0470] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, and other digital hardware, including digital signal processors (DSPs), application-specific digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more techniques described herein. In some implementations, according to one or more embodiments of this disclosure, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions.

[0471] To perform the above-described method actions, UE 121 is configured to process the DS in the wireless communication network 100. UE 121 may include Figure 25 The layout depicted in the text.

[0472] UE 121 may include input and output interfaces 2500 configured to communicate with each other. Input and output interfaces 2500 may include a receiver (e.g., wired and / or wireless) (not shown) and a transmitter (e.g., wired and / or wireless) (not shown).

[0473] The embodiments described herein can be implemented using a corresponding processor or one or more processors, such as Figure 25The UE 121 depicted herein includes at least one processor 2510 of the processing circuitry, and computer program code for performing the functions and actions of the embodiments described herein. The program code mentioned above may also be provided as a computer program product, for example, in the form of a data carrier carrying computer program code for executing the embodiments described herein when loaded into the UE 121. One such carrier may be in the form of a CD-ROM. However, the use of other data carriers such as memory sticks is feasible. The computer program code may also be provided as plain program code on a server and downloaded to the UE 121.

[0474] UE 121 and / or processor 2510 are configured to send a first session establishment request to first access and mobility node 116. The first session establishment request includes a first SUPI and a DS association ID associated with UE 121. The first SUPI is associated with the first access. The DS association ID is adapted to be included in both the first and second parts of the request.

[0475] UE 121 and / or processor 2510 are configured to send a second session establishment request to second access and mobility node 117. The second session establishment request includes a second SUPI associated with UE 121 and a DS association ID. The second SUPI is associated with a second access that is different from the first access. The DS association ID is adapted to be included in both the first and second parts of the request.

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

[0477] In some embodiments, the DS association ID is adapted to associate a first and a second DS session.

[0478] In some embodiments, a first session establishment request is adapted to include a request type initial request, and a second session establishment request is adapted to include a request type existing session.

[0479] UE 121 may also include a corresponding memory 2520, which includes one or more memory cells. Memory 2520 includes instructions executable by processor 2510 in UE 121.

[0480] The memory 2520 is arranged to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, streams, policies, session SUPIs, IDs, and applications to execute the methods described herein when executed in UE 121.

[0481] In some embodiments, the computer program 2530 includes instructions that, when executed by at least one processor 2510, cause at least one processor 2510 of the UE 121 to perform the aforementioned actions.

[0482] In some embodiments, the corresponding carrier 2540 includes a corresponding computer program 2530, wherein the carrier 2540 is one of electronic signals, optical signals, electromagnetic signals, magnetic signals, electrical signals, radio signals, microwave signals, or computer-readable storage media.

[0483] Therefore, the embodiments herein may disclose a UE 121 configured to process a DS in a wireless communication network 100. UE 121 includes a processor 2510 and a memory 2520, the memory 2520 including instructions executable by the processor 2510, thereby enabling UE 121 to perform any of the methods herein.

[0484] Those familiar with communication design will readily understand that functional devices or modules can 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 can 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. For example, some of the functions may be implemented on a processor shared with other functional components of a radio network node.

[0485] Alternatively, some of the functional elements of the processing apparatus discussed may be provided using dedicated hardware, while other functional elements may be provided with hardware associated with appropriate software or firmware for executing the software. Therefore, the terms "processor" or "controller" as used herein do not exclusively refer to hardware capable of executing software and may implicitly include, but are not limited to, 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 conventional and / or custom hardware may also be included. Designers of communication receivers will understand the inherent cost, performance, and maintenance trade-offs in these design choices.

[0486] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, and other digital hardware, including digital signal processors (DSPs), application-specific digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more techniques described herein. In some implementations, according to one or more embodiments of this disclosure, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions.

[0487] To perform the above-described method actions, policy control node 113 is configured to process DS in the wireless communication network 100. Policy control node 113 may include... Figure 26a The layout depicted in the text.

[0488] Policy control node 113 may include input and output interfaces 2600 configured to communicate with each other. Input and output interfaces 2600 may include a receiver (e.g., wired and / or wireless) (not shown) and a transmitter (e.g., wired and / or radio) (not shown).

[0489] The embodiments described herein can be implemented using a corresponding processor or one or more processors, such as Figure 26a The policy control node 113 depicted herein includes at least one processor 2610 of the processing circuitry, and computer program code for performing the functions and actions of the embodiments described herein. The aforementioned program code may also be provided as a computer program product, for example, in the form of a data carrier carrying computer program code for executing the embodiments described herein when loaded into the policy control node 113. One such carrier may be in the form of a CD-ROM. However, other data carriers such as memory sticks are feasible. The computer program code may also be provided as plain program code on a server and downloaded to the policy control node 113.

[0490] Policy control node 113 and / or processor 2610 are configured to establish a policy association with first session management node 111 for a DS session by receiving a request from first session management node 111. The request is adapted to include a first SUPI and a first DS SUPI. The establishment is adapted to include creating one or more policy rules by taking into account the first SUPI and the first DS SUPI.

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

[0492] Policy control node 113 and / or processor 2610 are configured to update the 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 is adapted to include a second SUPI and a second DS SUPI. The update is adapted to include updating one or more policy rules by taking into account the second SUPI and the second DS SUPI.

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

[0494] In some embodiments, one or more policy rules are adapted to include any one or more of URSP rules, PCC rules, and ATSSS rules.

[0495] In some embodiments, any one or more of the URSP rules include a DS indication, the PCC rule includes an access descriptor indicating the access type, and the ATSSS rule includes an access descriptor indicating the access type.

[0496] In some embodiments, the update policy association is adapted to include any one or more of the update URSP rules, PCC rules, and ATSSS rules.

[0497] In some embodiments, updating PCC rules and / or ATSS rules is adapted to include adding an access type associated with a second SUPI.

[0498] The policy control node 113 may also include a corresponding memory 2620, which includes one or more memory cells. The memory 2620 includes instructions executable by the processor 2610 in the policy control node 113.

[0499] The memory 2620 is arranged to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, streams, policies, session SUPIs, IDs, and applications to execute the methods described herein when executed in the policy control node 113.

[0500] In some embodiments, the computer program 2630 includes instructions that, when executed by at least one processor 2610, cause at least one processor 2610 of the policy control node 113 to perform the aforementioned actions.

[0501] In some embodiments, the corresponding carrier 2640 includes a corresponding computer program 2630, wherein the carrier 2640 is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electrical signal, a radio signal, a microwave signal, or a computer-readable storage medium.

[0502] Therefore, the embodiments herein may disclose a policy control node 113 configured to process DS in a wireless communication network 100. The policy control node 113 includes a processor 2610 and a memory 2620, the memory 2620 including instructions executable by the processor 2610, thereby enabling the policy control node 113 to operate to perform any of the methods described herein.

[0503] Those familiar with communication design will readily understand that functional devices or modules can 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 can 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. For example, some of the functions may be implemented on a processor shared with other functional components of a radio network node.

[0504] Alternatively, some of the functional elements of the processing apparatus discussed may be provided using dedicated hardware, while other functional elements may be provided with hardware associated with appropriate software or firmware for executing the software. Therefore, the terms "processor" or "controller" as used herein do not exclusively refer to hardware capable of executing software and may implicitly include, but are not limited to, 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 conventional and / or custom hardware may also be included. Designers of communication receivers will understand the inherent cost, performance, and maintenance trade-offs in these design choices.

[0505] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, and other digital hardware, including digital signal processors (DSPs), application-specific digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more techniques described herein. In some implementations, according to one or more embodiments of this disclosure, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions.

[0506] To perform the above-described method actions, the user data node 114 is configured to process the DS in the wireless communication network 100. The user data node 114 may include... Figure 26b The layout depicted in the text.

[0507] User data nodes 114 may include input and output interfaces 2700 configured to communicate with each other. Input and output interfaces 2700 may include receivers (e.g., wired and / or wireless) (not shown) and transmitters (e.g., wired and / or wireless) (not shown).

[0508] The embodiments described herein can be implemented using a corresponding processor or one or more processors, such as Figure 26b The user data node 114 depicted herein includes at least one processor 2710 of the processing circuitry, and 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 example, in the form of a data carrier carrying computer program code for executing the embodiments herein when loaded into the user data node 114. One such carrier may be in the form of a CD-ROM. However, the use of other data carriers such as memory sticks is feasible. The computer program code may also be provided as plain program code on a server and downloaded to the user data node 114.

[0509] User data node 114 and / or processor 2710 are configured to provide subscription data associated with a first SUPI and / or UE 121 to a first session management node 111. The subscription data is adapted to include a first DS SUPI indicating a second SUPI associated with UE 121.

[0510] User data node 114 and / or processor 2710 are configured to register a DS session by receiving a registration message indicating the DS association ID from the first session management node 111.

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

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

[0513] In some embodiments, registering a DS session includes registering a DS association ID in the subscription data associated with the first SUPI and / or UE 121.

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

[0515] In some embodiments, providing subscription data to the second access and mobility node 117 or the second session management node 112 is adapted to include receiving a request from the second access and mobility node 117 or the second session management node 112 and sending subscription data to the second access and mobility node 117 or the second session management node 112. The request is adapted to include a second SUPI associated with the UE 121.

[0516] In some embodiments, providing a session list for UE 121 to the second access and mobility node 117 or the second session management node 112 is adapted to include receiving a request from the second access and mobility node 117 or the second session management node 112 and sending the session list to the second access and mobility node 117 or the second session management node 112. The request is adapted to include a first SUPI associated with UE 121.

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

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

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

[0520] In some embodiments, providing subscription data to the first session management node 111 is adapted to include receiving a request from the first session management node 111 and sending subscription data to the first session management node 111. The request is adapted to include a second SUPI. The subscription data is adapted to include session management subscription data associated with the second SUPI and / or UE 121.

[0521] User data node 114 may also include a corresponding memory 2720, which includes one or more memory cells. Memory 2720 includes instructions executable by processor 2710 in user data node 114.

[0522] The memory 2720 is arranged to store instructions, data, configurations, identifiers, measurements, indications, notifications, resources, streams, policies, session SUPIs, IDs, and applications to execute the methods described herein when executed in the user data node 114.

[0523] In some embodiments, the computer program 2730 includes instructions that, when executed by at least one processor 2710, cause at least one processor 2710 of the user data node 114 to perform the aforementioned actions.

[0524] In some embodiments, the corresponding carrier 2740 includes a corresponding computer program 2730, wherein the carrier 2740 is one of electronic signals, optical signals, electromagnetic signals, magnetic signals, electrical signals, radio signals, microwave signals, or computer-readable storage media.

[0525] Therefore, the embodiments described herein may disclose a user data node 114 configured to process a DS in a wireless communication network 100. The user data node 114 includes a processor 2710 and a memory 2720, the memory 2720 including instructions executable by the processor 2710, thereby enabling the user data node 114 to operate to perform any of the methods described herein.

[0526] Those familiar with communication design will readily understand that functional devices or modules can 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 can 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. For example, some of the functions may be implemented on a processor shared with other functional components of a radio network node.

[0527] Alternatively, some of the functional elements of the processing apparatus discussed may be provided using dedicated hardware, while other functional elements may be provided with hardware associated with appropriate software or firmware for executing the software. Therefore, the terms "processor" or "controller" as used herein do not exclusively refer to hardware capable of executing software and may implicitly include, but are not limited to, 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 conventional and / or custom hardware may also be included. Designers of communication receivers will understand the inherent cost, performance, and maintenance trade-offs in these design choices.

[0528] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, and other digital hardware, including digital signal processors (DSPs), application-specific digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for executing one or more techniques described herein. In some implementations, according to one or more embodiments of this disclosure, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions.

[0529] Additional explanation

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

[0531] Figure 27An example of a communication system QQ100 according to some embodiments is shown.

[0532] In this example, the communication system QQ100 includes a telecommunications network QQ102 and a core network QQ106. The telecommunications network QQ102 includes an access network QQ104, such as a radio access network (RAN), and the core network QQ106 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 generally be referred to as network node QQ110), or any other similar 3GPP access node or non-3GPP access point. Furthermore, as those skilled in the art will understand, network nodes are not necessarily limited to implementations in which the radio and baseband portions are supplied and integrated by a single vendor. Therefore, it will be understood that network nodes include decomposed implementations or portions thereof. For example, in some embodiments, the telecommunications network QQ102 includes one or more Open RAN (ORAN) network nodes. An ORAN network node is a node in the QQ102 telecommunications network that supports ORAN specifications (e.g., specifications published by the O-RAN Alliance or any similar organization) and can operate alone or with other nodes to perform one or more functions of any node in the QQ102 telecommunications network (including one or more network nodes QQ110 and / or core network node QQ108).

[0533] Examples of ORAN network nodes include Open Radio Units (O-RUs), Open Distributed Units (O-DUs), Open Central Units (O-CUs) including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), RAN Intelligent Controllers (near real-time or non-real-time) hosting software or software plug-ins (such as near real-time control applications (e.g., xApp) or non-real-time control applications (e.g., rApp)), or any combination thereof (the adjective "open" indicates support for the ORAN specification). Network nodes can support the specification by, for example, supporting interfaces defined by the ORAN specification, such as A1, F1, W1, E1, E2, X2, Xn interfaces, Open Fronthaul User Plane Interfaces, or Open Fronthaul Management Plane Interfaces. Furthermore, ORAN access nodes can be logical nodes within physical nodes. Additionally, ORAN network nodes can be implemented in virtualized environments where one or more network functions are virtualized (described further below). For example, a virtualized environment can include an O-Cloud computing platform orchestrated by a service management and orchestration framework via an O-2 interface defined by the O-RAN Consortium or similar technologies. Network node QQ110 facilitates direct or indirect connections of user equipment (UE), such as connecting UE QQ112a, QQ112b, QQ112c and QQ112d (one or more of which may be generally referred to as UE QQ112) to core network QQ106 via one or more wireless connections.

[0534] Examples of wireless communication via wireless connection include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other conductors. Furthermore, in various 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 can facilitate or participate in the communication of data and / or signals, whether via a wired or wireless connection. The communication system QQ100 may include and interface with any type of communication, telecommunications, data, cellular, radio network, and / or other similar type of system.

[0535] UE QQ112 can be any of a variety of communication devices, including wireless devices that are deployed, configured, and / or operable to communicate wirelessly with network node QQ110 and other communication devices. Similarly, network node QQ110 is deployed, capable of, configured, and / or operable to communicate directly or indirectly with UE QQ112 and / or with other network nodes or devices in telecommunication network QQ102 to achieve and / or provide network access (such as wireless network access) and / or perform other functions (such as management in telecommunication network QQ102).

[0536] In the depicted example, core network QQ106 connects network node QQ110 to one or more host computing systems, such as host QQ116. These connections can be direct or indirect connections via one or more intermediate networks or devices. In other examples, network nodes can be directly coupled to hosts. Core network QQ106 includes one or more core network nodes (e.g., core network node QQ108) constructed with hardware and software components. The characteristics of these components can be substantially similar to those described with respect to UEs, network nodes, and / or hosts, such that the description generally applies to the corresponding components of core network node QQ108. Example core network nodes include functions of one or more of the following: 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 Dehiding Function (SIDF), Unified Data Management (UDM), Secure Edge Protection Agent (SEPP), Network Open Function (NEF), and / or User Plane Function (UPF).

[0537] The QQ116 host may be owned or controlled by a service provider other than the operator or provider of the access network QQ104 and / or the telecommunications network QQ102. The QQ116 host may host various applications to provide one or more services. Examples of such applications include real-time and pre-recorded audio / video content, data collection services (such as retrieving and editing data about various environmental conditions detected by multiple UEs), analytics functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by the server.

[0538] As a whole, Figure 27 The QQ100 communication system enables connections between the UE, network nodes, and the host. In this sense, the communication system can be configured to operate according to predefined rules or procedures such as specific standards, including but 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 standard (WiFi); and / or any other suitable wireless communication standards, such as 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.

[0539] In some examples, the QQ102 telecommunications network is a cellular network implementing 3GPP standardized features. Therefore, the QQ102 network can support network slicing to provide different logical networks to different devices connected to it. For example, the QQ102 network can 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) / massive IoT services to yet another UE.

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

[0541] In this example, the central hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UEQQ112c and / or QQ112d) and a network node (e.g., network node QQ110b). In some examples, the central hub QQ114 may be a controller, router, content source, and analytics, or any of the other communication devices described herein with respect to the UE. For example, the central hub QQ114 may be a broadband router that enables the UE to access the core network QQ106. As another example, the central hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UE. Commands or instructions may be received from the UE, network node QQ110, or via executable code, scripts, procedures, or other instructions in the central hub QQ114. As another example, the central hub QQ114 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, it may perform data analytics or other processing. As another example, the central hub QQ114 may be a content source. For example, for a UE acting as a VR device, display, speaker, or other media delivery device, the central QQ114 can retrieve VR assets, videos, audio, or other media or data related to sensory information via network nodes, and then provide them to the UE directly, after performing local processing, and / or after adding additional local content. In yet another example, the central QQ114 acts as a proxy server or coordinator for the UE, particularly when one or more devices in the UE are low-power IoT devices.

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

[0543] Figure 28 The UE QQ200 is shown according to some embodiments. The UE QQ200 presents... Figure 1 Additional details regarding some embodiments of UE QQ112 are provided below. As used herein, UE refers to a device capable of, configured to, positioned, and / or operable to wirelessly communicate with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, VoIP phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage / playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), augmented reality (AR) or virtual reality (VR) devices, wireless customer premises equipment (CPEs), vehicles, vehicle-mounted or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine-type communication (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0544] The UE can support device-to-device (D2D) communication, for example, by implementing 3GPP standards for sidelink communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, the UE may not necessarily be a user in the sense of a human user who owns and / or operates the associated equipment. Instead, the UE may represent equipment intended to be sold to or operated by a human user, but the equipment may not be associated with a particular human user, or may not have initially been associated with that particular human user (e.g., a smart sprinkler controller). Alternatively, the UE may represent equipment not intended to be sold to or operated by an end user, but the equipment may be associated with a user or operated for the user's benefit (e.g., a smart meter).

[0545] UE QQ200 includes processing circuitry QQ202, which is operatively coupled via bus QQ204 to input / output interface QQ206, power supply QQ208, memory QQ210, communication interface QQ212, and / or any other components, or any combination thereof. Some UEs may utilize... Figure 28 The components shown may be all or a subset of the components. The level of integration between components can vary from one UE to another. Furthermore, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0546] The processing circuit QQ202 is configured to process instructions and data and can be configured to implement any sequential state machine operable to execute instructions stored as a machine-readable computer program in memory QQ210. The processing circuit QQ202 can 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 and appropriate firmware; one or more stored computer programs, general-purpose processors such as microprocessors or digital signal processors (DSPs), and appropriate software; or any combination thereof. For example, the processing circuit QQ202 may include multiple central processing units (CPUs).

[0547] In this example, the input / output interface QQ206 can be configured to provide one or more interfaces to input devices, output devices, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, other output devices, or any combination thereof. Input devices can allow users to capture information into the UE QQ200. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital camcorders, webcams, etc.), microphones, sensors, mice, trackballs, steering wheels, scroll wheels, smart cards, etc. Presence-sensitive displays can include capacitive or resistive touch sensors to sense input from the user. Sensors can be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, biometric sensors, etc., or any combination thereof. Output devices can use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port can be used to provide both input and output devices.

[0548] In some embodiments, the power supply QQ208 is configured as a battery or battery pack. Other types of power sources can be used, such as external power sources (e.g., electrical outlets), photovoltaic devices, or power batteries. The power supply QQ208 may also include power circuitry for delivering power from the power supply QQ208 itself and / or an external power source to various parts of the UE QQ200 via input circuitry or an interface such as a power cable. The delivered power may be used, for example, to charge the power supply QQ208. The power circuitry may perform any formatting, conversion, or other modifications on the power from the power supply QQ208 to suit the power supply for the various components of the UE QQ200 to which power is supplied.

[0549] The memory QQ210 can be or is 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), disk, optical disk, hard disk, removable tape cartridge, flash drive, etc. In one example, the memory QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, widget, utility engine, or other application, and corresponding data QQ216. The memory QQ210 can store any operating system or combination of operating systems from various operating systems for use by the UE QQ200.

[0550] The QQ210 memory can be configured to include multiple physical drive units, such as a Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard drive, thumb drive, pen drive, key drive, high-density digital multifunction disc (HD-DVD) optical disc drive, internal hard drive, Blu-ray 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, smart card memory (such as a tamper-proof module in the form of a Universal Integrated Circuit Card (UICC), including one or more User Identity Modules (SIMs), such as USIM and / or ISIM), other memory, or any combination thereof. The UICC can be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card." The QQ210 memory allows the UE QQ200 to access instructions, applications, etc., stored on transient or non-transient storage media to offload or upload data. Articles of manufacture, such as those utilizing communication systems, may be tangibly embodied in or contained in memory QQ210, which may be or include a device-readable storage medium.

[0551] The processing circuitry QQ202 can be configured to communicate with an access network or other networks using a communication interface QQ212. The communication interface QQ212 may include 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 for communication, such as through one or more remote transceivers communicating with another device capable of wireless communication (e.g., another UE or network node in the access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 adapted to provide network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, 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, may be implemented separately.

[0552] In the illustrated embodiment, the communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a Global Positioning System (GPS) to determine location, another similar communication function, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiple 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 on.

[0553] Regardless of the sensor type, the UE can provide the output of data captured by its sensors via its communication interface QQ212, through a wireless connection to a network node. Data captured by the UE's sensors can be transmitted wirelessly to the network node via another UE. The output can be periodic (e.g., every 15 minutes if it reports sensed temperature), random (e.g., to load balance reports from multiple sensors), responsive to a triggered event (e.g., sending an alarm when humidity is detected), responsive to a request (e.g., a user-initiated request), or a continuous stream (e.g., real-time video feed of a patient).

[0554] As another example, the UE includes an actuator, motor, or switch associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch can change in response to the received wireless input. For example, the UE may include a motor that adjusts the control surfaces or rotors of a flying drone based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.

[0555] When taking the form of an Internet of Things (IoT) device, the UE can be a device used in one or more application areas, including but not limited to urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices include or embedded in the following devices: connected refrigerators or freezers, televisions, connected lighting fixtures, electricity meters, robotic vacuum cleaners, voice-activated smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, air conditioning systems (such as heat pumps), autonomous vehicles, surveillance systems, weather monitoring equipment, vehicle parking monitoring equipment, electric vehicle charging stations, smartwatches, fitness trackers, wearable devices for haptic or sensory enhancement, sprinklers, animal or object tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device (such as heart rate monitors or remotely controlled surgical robots). (Except for...) Figure 28 In addition to the other components described in UE QQ200 shown, UEs in the form of IoT devices include circuitry and / or software that depend on the intended application of the IoT device.

[0556] As another concrete example, in IoT scenarios, a UE can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE can be an M2M device, which can be referred to as an MTC device in the 3GPP context. As a specific example, the UE can implement the 3GPP NB-IoT standard. In other scenarios, the UE can represent a vehicle, such as a car, bus, truck, ship, and aircraft, or other device capable of monitoring and / or reporting its operational status or performing other functions associated with its operation.

[0557] In practice, for a single use case, any number of UEs can be used together. For example, the first UE might be or integrated into the drone and provide the drone's speed information (obtained via a speed sensor) to a second UE acting as a remote controller. When the user makes a change from the remote controller, the first UE can adjust the throttle on the drone (e.g., by controlling actuators) to increase or decrease the drone's speed. The first and / or second UEs may also include more than one of the functions described above. For example, the UE might include sensors and actuators and handle communication for data from the speed sensors and actuators.

[0558] Figure 29 A network node QQ300 according to some embodiments is illustrated. As used herein, a network node refers to a device that is capable of, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications 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 Node Bs (gNBs)), O-RAN nodes, or components of O-RAN nodes (e.g., O-RUs, O-DUs, O-CUs).

[0559] Base stations can be classified based on the coverage they provide (or, in other words, based on their transmit power levels); therefore, depending on the coverage provided, a base station can be referred to as a femtobase, picobase, microbase, or macrobase. A base station can be a relay node or a relay donor node controlling a relay. Network nodes can also include one or more (or all) portions of a distributed radio base station, such as centralized digital units, distributed units (e.g., in O-RAN access nodes), 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. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS).

[0560] Other examples of network nodes include multi-transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) devices such as MSR BS, network controllers such as radio network controllers (RNC) or base station controllers (BSC), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCE), operations and maintenance (O&M) nodes, operations support system (OSS) nodes, self-organizing network (SON) nodes, location nodes (e.g., evolved servicing mobile location centers (E-SMLC)), and / or minimized drive tests (MDT).

[0561] Network node QQ300 includes processing circuitry QQ302, memory QQ304, communication interface QQ306, and power supply QQ308. Network node QQ300 may consist of multiple physically separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each component may have its own corresponding components. In some scenarios where network node QQ300 includes 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 can control multiple NodeBs. In such scenarios, each unique NodeB and RNC pair may be considered a single separate network node in some cases. In some embodiments, 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., the same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of various illustrated components for integrating different wireless technologies (such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, RFID, or Bluetooth wireless technologies) into the network node QQ300. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node QQ300.

[0562] The processing circuitry QQ302 may include 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 coding logic, operable to provide the functionality of network node QQ300 alone or together with other network node QQ300 components (such as memory QQ304).

[0563] In some embodiments, the processing circuit QQ302 includes a system-on-a-chip (SOC). In some embodiments, the processing circuit QQ302 includes one or more of a radio frequency (RF) transceiver circuit QQ312 and a baseband processing circuit QQ314. In some embodiments, the RF transceiver circuit QQ312 and the baseband processing circuit QQ314 may be on separate chips (or chipsets), boards, or units, such as radio units and digital units. In alternative embodiments, some or all of the RF transceiver circuit QQ312 and the baseband processing circuit QQ314 may be on the same chip or chipset, board, or unit.

[0564] The memory QQ304 may include any form of volatile or non-volatile computer-readable memory, including but not limited to persistent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, compact discs (CDs), or digital video discs (DVDs)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including computer programs, software, and applications, including one or more of logic, rules, codes, tables, and / or other instructions that can be executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations performed by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and the memory QQ304 are integrated.

[0565] The communication interface QQ306 is used for wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, the communication interface QQ306 includes one or more ports / terminals QQ316 for transmitting and receiving data to and from the network, for example, via a wired connection. The communication interface QQ306 also includes a radio front-end circuit QQ318, which may be coupled to or is part of the antenna QQ310 in some embodiments. The radio front-end circuit QQ318 includes a filter QQ320 and an amplifier QQ322. The radio front-end circuit QQ318 may be connected to the antenna QQ310 and the processing circuit QQ302. The radio front-end circuit can be configured to regulate the signal transmitted between the antenna QQ310 and the processing circuit QQ302. The radio front-end circuit QQ318 can receive digital data to be transmitted to other network nodes or UEs via a wireless connection. The radio front-end circuit QQ318 can use a combination of the filter QQ320 and / or the amplifier QQ322 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal can then be transmitted via the antenna QQ310. Similarly, when receiving data, antenna QQ310 can collect radio signals, which are then converted into digital data by radio front-end circuitry QQ318. The digital data can then be passed to processing circuitry QQ302. In other embodiments, the communication interface may include different components and / or different combinations of components.

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

[0567] Antenna QQ310 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna QQ310 may be coupled to radio front-end circuitry QQ318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna QQ310 is decoupled from network node QQ300 and may be connected to network node QQ300 via an interface or port.

[0568] Antenna QQ310, communication interface QQ306, and / or processing circuitry QQ302 can be configured to perform any receive operation and / or certain acquisition operation described herein as being performed by a network node. Any information, data, and / or signals can be received from the UE, another network node, and / or any other network device. Similarly, antenna QQ310, communication interface QQ306, and / or processing circuitry QQ302 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to the UE, another network node, and / or any other network device.

[0569] The power supply QQ308 provides power to the various components of the network node QQ300 in a form suitable for each component (e.g., at the voltage and current levels required by each respective component). The power supply QQ308 may further include or be coupled to power management circuitry to supply power to the components of the network node QQ300 for performing the functions described herein. For example, the network node QQ300 may be connected to an external power source (e.g., mains, electrical outlet) via input circuitry or an interface such as a cable, whereby the external power source supplies power to the power circuitry of the power supply QQ308. As another example, the power supply QQ308 may include a power source in the form of a battery or battery pack, which is connected to or integrated into the power circuitry. The battery can provide backup power if the external power source fails.

[0570] Implementation examples of network node QQ300 may include Figure 29Additional components beyond those shown are used to provide certain aspects of the network node's functionality, including any of the functions described herein and / or any functions necessary to support the topics described herein. For example, network node QQ300 may include a user interface device to allow information to be input into and output from network node QQ300. This allows users to perform diagnostic, maintenance, repair, and other management functions on network node QQ300. In some embodiments that provide a core network node (such as core network node 108 of Figure QQ1), some components, such as radio front-end circuitry QQ318 and RF transceiver circuitry QQ312, may be omitted.

[0571] Figure 30 This is a block diagram illustrating a virtualized environment QQ400 in which some embodiments of functionality can be virtualized. In this context, virtualization means creating virtual versions of a device or apparatus, which may include virtualizing hardware platforms, storage devices, and network resources. As used herein, virtualization can be applied to any device or component thereof described herein and relates to implementations in which at least a portion of functionality is implemented as one or more virtual components. Some or all of the functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) in one or more virtualized environments QQ400 hosted by one or more hardware nodes, such as hardware computing devices operating as network nodes, UEs, core network nodes, or hosts. Furthermore, in embodiments where the virtual node does not require radio connectivity (e.g., a core network node or host), the node can be fully virtualized. In some embodiments, the virtualized environment QQ400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated via an O-2 interface by a service management and orchestration framework. Virtualization can facilitate distributed implementations of network nodes, UEs, core network nodes, or hosts.

[0572] The application QQ402 (which may also be referred to as a software instance, virtual device, network function, virtual node, virtual network function, etc.) runs in the virtualization environment Q400 to implement some of the features, functions and / or benefits of some of the embodiments disclosed herein.

[0573] Hardware QQ404 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices described herein, such as network interfaces, input / output interfaces, etc. Software can 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 VM QQ408a and QQ408b (one or more of which may generally be referred to as VM QQ408), and / or perform any functionality, features, and / or benefits described in conjunction with some embodiments described herein. Virtualization layer QQ406 can present a virtual operating platform to VM QQ408 that appears to be network hardware.

[0574] VM QQ408 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by the corresponding virtualization layer QQ406. Different embodiments of virtual device QQ402 instances can be implemented on one or more VM QQ408, and can be implemented in different ways. Hardware virtualization is referred to in some contexts as Network Functions Virtualization (NFV). NFV can be used to consolidate many types of network devices onto industry-standard high-capacity server hardware, physical switches, and physical storage, which can reside in data centers and customer premises.

[0575] In the context of NFV, a VM QQ408 can be a software implementation of a physical machine, whose running programs behave as if they were executing on a physical, non-virtualized machine. Each VM QQ408, and the portion of the hardware QQ404 that executes that VM—whether dedicated hardware for that VM or hardware shared by that VM and other VMs within it—forms a separate virtual network element. Still within the NFV context, the virtual network function is responsible for handling specific network functions running on one or more VM QQ408s above the hardware QQ404 and corresponds to the application QQ402.

[0576] The hardware QQ404 can be implemented in a standalone network node with general or specific components. Some functions of the hardware QQ404 can be implemented via virtualization. Alternatively, the hardware QQ404 can be part of a larger hardware cluster (e.g., in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration QQ410, which in particular oversees the lifecycle management of application QQ402. In some embodiments, the hardware QQ404 is coupled to one or more radio units, each radio unit including one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio units can communicate directly with other hardware nodes via one or more suitable network interfaces and can be used in combination with virtual components to provide radio capabilities to virtual nodes such as radio access nodes or base stations. In some embodiments, a control system QQ412 can be used to provide some signaling, which can alternatively be used for communication between hardware nodes and radio units.

[0577] While the computing devices (e.g., UE, network node) described herein may include the illustrated combinations of hardware components, other embodiments may include computing devices with different combinations of components. It should be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by processing circuitry that processes information by, for example, converting acquired information into other information, comparing the acquired or converted information with information stored in a network node, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing. Furthermore, although components are depicted as single boxes located within larger boxes or nested within multiple boxes, in practice, computing devices may include multiple different physical components constituting a single illustrated component, and functionality may be partitioned between individual components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of a component may be partitioned between processing circuitry and the communication interface. In another example, non-computationally intensive functions of any such component may be implemented in software or firmware, and computationally intensive functions may be implemented in hardware.

[0578] In some embodiments, some or all of the functions described herein may be provided by processing circuitry that executes instructions stored in memory, which in some 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 functions may be provided by 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 these particular embodiments, the processing circuitry may be configured to perform the described functions regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functions are not limited to the processing circuitry itself or other components of the computing device, but are enjoyed by the computing device as a whole and / or generally by the end user and wireless network.

[0579] When the words “include” or “contain” are used, they should be interpreted as non-restrictive, meaning “consisting of at least…”.

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

[0581] abbreviation explain

[0582] 5GC 5G core

[0583] DS Dual Boot

[0584] AMF Access and Mobility Management Functions

[0585] ATSSS Access Service Handover and Segmentation

[0586] DS Dual Boot

[0587] FAR forwarding action rules

[0588] MA Multi-access

[0589] MAR Multi-Access Rules

[0590] SMF Session Management Function

[0591] PCC Policy Control and Billing

[0592] PDR Group Detection Rules

[0593] UDM Unified Data Management

[0594] UDR Unified Data Repository

[0595] UPF User Plane Functions

Claims

1. A method for processing a dual-booted DS in a wireless communication network (100), executed by a first session management node (111), the method comprising: Receive (701) a first session context establishment request for establishing a DS session, the first session context establishment request including a first subscription permanent identifier (SUPI) associated with the user equipment (UE) (121) and a DS association identifier (ID), wherein the first SUPI is associated with a first access. A context for the DS session is established (702) using the first SUPI, the DS association ID, and the first DS SUPI associated with the first SUPI and / or the UE (121), wherein the first DS SUPI indicates the second SUPI associated with the UE (121). A policy association is requested (703) to be established by sending a policy association establishment request to the policy control node (113), the request including the first SUPI and the first DS SUPI. Receive (705) a third session context establishment request for establishing the DS session, the third session context establishment request including the second SUPI associated with the UE (121) and the DS association ID, wherein the second SUPI is associated with a second access different from the first access. The context for the DS session is updated (706) using the second SUPI, the DS association ID, and the second DS SUPI associated with the second SUPI and / or the UE (121). The policy association is updated (707) by sending a policy association modification request to the policy control node (113), the request including 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 one of claims 1-2, wherein, The DS association ID identifies the DS session.

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

5. The method according to any one of claims 1-4, wherein, Establishing the context (702) includes: obtaining subscription data for the UE (121), the subscription data including 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 to any one of claims 1-5, wherein, The method further includes: The DS session is registered (704) in the user data node (114) by sending a registration message indicating the DS associated ID to the user data node (114).

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

8. A method for processing dual-guided DS in a wireless communication network (100), performed by a first access and mobility node (116), the method comprising: A first session establishment request (901) is received from a user equipment (UE) (121), wherein the first session establishment request includes a first subscription permanent identifier (SUPI) and a DS association identifier (ID) associated with the UE (121), wherein the first SUPI is associated with a first access, and wherein the DS association ID is included in the mobility management (MM) portion of the request and the session management (SM) container of the request. Select (902) the first session management node (111). Send a (903) first session context establishment request to the selected first session management node (111), the first session context establishment request including the first SUPI and the DS association ID.

9. The method according to claim 8, wherein, Selecting (902) the first session management node (111) includes: selecting a session management node that supports DS.

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

11. A method performed by a second access and mobility node (117) for processing, for example, a dual-guided DS in a wireless communication network (100), the method comprising: A second session establishment request (1001) is received from the user equipment (UE) (121), wherein the second session establishment request includes a second subscription permanent identifier (SUPI) associated with the UE (121) and a DS association identifier (ID), wherein the second SUPI is associated with a second access, and wherein the DS association ID is included in the mobility management (MM) portion of the request and the session management (SM) container of the request. Select (1002) Session management node, wherein the selected session management node is the first session management node (111) selected by the first access and mobility node (116) for the DS session. Send a (1003) session context establishment request to the selected session management node (111), wherein the session context establishment request includes the second SUPI and the DS association ID.

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

13. The method according to any one of claims 11-12, wherein, Selecting the first session management node (111) further includes: obtaining subscription data for the UE (121), the subscription data including the second DS SUPI, wherein the second DS SUPI indicates a first SUPI associated with the UE (121), and obtaining a session list 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 includes: using the session list and the DS association ID to obtain the identifier of the first session management node (111).

15. A method performed by a user equipment (UE) (121) for processing a dual-boot DS in a wireless communication network (100), the method comprising: A first session establishment request (1101) is sent to the first access and mobility node (116), wherein the first session establishment request includes a first subscription permanent identifier (SUPI) associated with the UE (121) and a DS association identifier (ID), wherein the first SUPI is associated with the first access, and wherein the DS association ID is included in the first part and the second part of the request. Send a (1102) second session establishment request to the second access and mobility node (117), wherein the second session establishment request includes a second SUPI associated with the UE (121) and the DS association ID, wherein the second SUPI is associated with a second access different from the first access, and wherein the DS association ID is included in the first part and the second part of the request.

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

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

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

19. A method for processing dual-booted DS in a wireless communication network (100), executed by a policy control node (113), the method comprising: A policy association (1201) is established between a DS session and the first session management node (111) by receiving a request from the first session management node (111), the request including a first subscription persistent identifier (SUPI) and a first DS SUPI, the establishment including creating one or more policy rules taking into account the first SUPI and the first DS SUPI. Provide the first session management node (111) with (1202) the one or more policy rules for the DS session. The update is performed by receiving a request from the first session management node (111) to associate the DS session update (1203) with the policy of the first session management node (111), the request including a second SUPI and a second DS SUPI, the update including updating the one or more policy rules taking into account the second SUPI and the second DS SUPI. Provide the first session management node (111) with (1204) the one or more policy rules for the DS session.

20. The method according to claim 19, wherein, The one or more policy rules include any one or more of the following: - User Equipment Routing Policy (URSP) rules - Policy control and billing PCC rules, and - Access service guidance, switching, and splitting ATSSS rules.

21. The method according to claim 20, wherein, Any one or more of the following: - The URSP rules include DS indications. - The PCC rule includes an access descriptor, which indicates the access type, and - The ATSSS rule includes an access descriptor, which indicates the access type.

22. The method according to any one of claims 20-21, wherein, Updating the policy association includes 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 rules and / or ATSS rules includes adding an access type associated with the second SUPI.

24. A method for processing a dual-booted DS in a wireless communication network (100), performed by a user data node (114), the method comprising: Provide (1301) subscription data associated with a first subscription permanent identifier SUPI and / or the UE (121) to the first session management node (111), wherein the subscription data includes a first DS SUPI indicating a second SUPI associated with the UE (121). The DS session is registered (1302) by receiving a registration message indicating the DS associated identifier ID from the first session management node (111).

25. The method according to claim 24, wherein, Providing the subscription data (1301) includes: 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 includes a first SUPI associated with the UE (121).

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

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

28. The method according to any one of claims 24-27, wherein, The method further includes: Provide (1303) subscription data and / or session list for the UE (121) to the second access and mobility node (117) or the second session management node (112), wherein the subscription data includes 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) includes: 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 includes a second SUPI associated with the UE (121).

30. The method according to any one of claims 28-29, wherein, Providing (1303) the session list for the UE (121) to the second access and mobility node (117) or the second session management node (112) includes: receiving a request from the second access and mobility node (117) or the second session management node (112), and sending the session list to the second access and mobility node (117) or the second session management node (112), wherein the request includes the first SUPI associated with the UE (121).

31. The method according to any one of claims 28-30, wherein any one of the following: - The subscription data provided to the second access and mobility node (117) includes 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) includes session management subscription data associated with the second SUPI and / or the UE (121).

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

33. The method according to claim 32, wherein, Providing (1304) subscription data to the first session management node (111) includes: 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 includes the second SUPI, and wherein the subscription data includes session management subscription data associated with the second SUPI and / or the UE (121).

34. A first session management node (111) configured to process a dual-boot DS in a wireless communication network (100), the first session management node (111) further configured to: A first session context establishment request for establishing a DS session is received, the first session context establishment request being adapted to include a first subscription permanent identifier SUPI associated with the user equipment UE (121) and a DS association identifier ID, wherein, The first SUPI is adapted to be associated with the first access. A context for the DS session is established using the first SUPI, the DS association ID, and a first DS SUPI associated with the first SUPI and / or the UE (121), wherein the first DS SUPI is adapted to indicate a second SUPI associated with the UE (121). A policy association is requested to be established by sending a policy association establishment request to the policy control node (113), the request being adapted to include the first SUPI and the first DS SUPI. A third session context establishment request is received for establishing the DS session, the third session context establishment request being adapted to include the second SUPI associated with the UE (121) and the DS association ID, wherein the second SUPI is associated with a second access different from the first access. The context for the DS session is updated using the second SUPI, the DS association ID, and a second DS SUPI adapted to be associated with the second SUPI and / or the UE (121), and The policy association is updated by sending a policy association modification request to the policy control node (113), the request being adapted to include 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 wherein the second DS SUPI is adapted to indicate the first SUPI.

36. The first session management node (111) according to any one of claims 28-29, wherein, The DS association ID is suitable for identifying the DS session.

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

38. The first session management node (111) according to any one of claims 28-31, wherein, Establishing the context is adapted to include: obtaining subscription data for the UE (121), the subscription data being adapted to include the DS SUPI, and further associating 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 one of claims 28-32, wherein, The first session management node (111) is also configured as follows: The DS session is registered in the user data node (114) by sending a registration message indicating the DS association ID to the user data node (114).

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

41. A first access and mobility node (116) configured to process a dual-guided DS in a wireless communication network (100), the first access and mobility node (116) further configured to: Receives a first session establishment request from user equipment (UE) (121), wherein, The first session establishment request is adapted to include a first subscription permanent identifier (SUPI) and a DS association identifier (ID) associated with the UE (121), wherein the first SUPI is adapted to be associated with a first access, and wherein the DS association ID is adapted to be included in the mobility management (MM) portion of the request and the session management (SM) container of the request. Select the 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 being adapted to include the first SUPI and the DS association ID.

42. The first access and mobility node (116) according to claim 35, wherein, Selecting the first session management node (111) is suitable to include: selecting a session management node that supports DS.

43. The first access and mobility node (116) according to any one 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 will be selected.

44. A second access and mobility node (117) configured to process a dual-guided DS in a wireless communication network (100), the second access and mobility node (117) further configured to: Receive a second session establishment request from user equipment (UE) (121), wherein, The second session establishment request is adapted to include a second subscription permanent identifier (SUPI) and a DS association identifier (ID) associated with the UE (121), wherein the second SUPI is adapted to be associated with a second access, and wherein the DS association ID is adapted to be included in the mobility management (MM) portion of the request and the session management (SM) container of the request. Selecting a session management node, wherein the selected session management node is adapted to be the first session management node (111) selected by the first access and mobility node (116) for the DS session. Send a session context establishment request to the selected session management node (111), wherein the session context establishment request is adapted to include the second SUPI and the DS association ID.

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

46. ​​The second access and mobility node (117) according to any one of claims 38-39, wherein, Selecting the first session management node (111) is further adapted to include: obtaining subscription data for the UE (121), the subscription data being adapted to include the second DS SUPI, wherein the second DS SUPI is adapted to indicate a first SUPI associated with the UE (121), and obtaining a session list for the UE (121) based on the first SUPI.

47. The second access and mobility node (117) according to claim 40, wherein, Selecting the first session management node (111) is also adapted to include: using the session list and the DS association ID to obtain the identifier of the first session management node (111).

48. A user equipment (UE) (121) configured to process a dual-boot DS in a wireless communication network (100), the UE (121) further configured to: A first session establishment request is sent to the first access and mobility node (116), wherein, The first session establishment request is adapted to include a first subscription permanent identifier (SUPI) and a DS association identifier (ID) associated with the UE (121), wherein the first SUPI is adapted to be associated with a first access, and wherein the DS association ID is adapted to be included in the first part and the second part of the request. Send a second session establishment request to the second access and mobility node (117), wherein the second session establishment request is adapted to include a second SUPI associated with the UE (121) and the DS association ID, wherein the second SUPI is associated with a second access different from the first access, and wherein the DS association ID is adapted to be included in the first part and the second part of the request.

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

50. The UE (121) according to any one of claims 42-43, wherein, The DS association ID is suitable for use in associating the first and second sessions of the DS session.

51. The UE (121) according to any one of claims 42-44, wherein, The first session establishment request is adapted to include a request type initial request, and the second session establishment request is adapted to include a request type existing session.

52. A policy control node (113) configured to process dual-boot DS in a wireless communication network (100), the policy control node (113) further configured to: Establishing 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 being adapted to include a first subscription permanent identifier (SUPI) and a first DS SUPI, the establishment being adapted to include: Considering the first SUPI and the first DS SUPI, create one or more policy rules. Provide the first session management node (111) with one or more policy rules for the DS session. The update is performed by receiving a request from the first session management node (111) to update the policy association with the first session management node (111) for the DS session. The request is adapted to include a second SUPI and a second DS SUPI, and the update is adapted to include updating the one or more policy rules by taking into account the second SUPI and the second DS SUPI. Provide the first session management node (111) with one or more policy rules for the DS session.

53. The strategy control node (113) according to claim 46, wherein, The one or more policy rules are suitable for including any one or more of the following: - User Equipment Routing Policy (URSP) rules - Policy control and billing PCC rules, and - Access service guidance, switching, and splitting ATSSS rules.

54. The policy control node (113) according to claim 47, wherein, the following Any one or more of the following: - The URSP rules include DS indications. - The PCC rule includes an access descriptor, which indicates the access type, and - The ATSSS rule includes an access descriptor, which indicates the access type.

55. The strategy control node (113) according to any one of claims 47-48, wherein, Updating the policy association is suitable for including updating any one or more of the URSP rule, PCC rule, and ATSSS rule.

56. The strategy control node (113) according to claim 49, wherein, Updating the PCC rules and / or ATSS rules may include adding an access type associated with the second SUPI.

57. A user data node (114) configured to process a dual-boot DS in a wireless communication network (100), the user data node being further configured to: Provide the first session management node (111) with subscription data associated with the first subscription permanent identifier SUPI and / or the UE (121), wherein, The subscription data is adapted to include a first DSSUPI indicating a second SUPI associated with the UE (121). The DS session is registered by receiving a registration message indicating the DS associated identifier ID from the first session management node (111).

58. The user data node (114) according to claim 51, wherein, Providing the subscription data is adapted to include: 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 is adapted to include a first SUPI associated with the UE (121).

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

60. The user data node (114) according to any one of claims 51-53, wherein, Registering the DS session is adapted to include: registering the DS association ID in a UE context associated with the first SUPI and / or the UE (121), and associating the DS session with the DS association ID.

61. The user data node (114) according to any one of claims 57-60, wherein, The user data node (114) is also configured as follows: Provide subscription data and / or a session list for the UE (121) to the second access and mobility node (117) or the second session management node (112), wherein the subscription data is adapted to include a second DS SUPI associated with the second SUPI and / or the UE (121), the second DS SUPI indicating the first SUPI.

62. The user data node (114) according to claim 61, wherein, Providing subscription data to the second access and mobility node (117) or the second session management node (112) is adapted to include: 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 is adapted to include a second SUPI associated with the UE (121).

63. The user data node (114) according to any one of claims 61-62, wherein, Providing the session list for the UE (121) to the second access and mobility node (117) or the second session management node (112) is adapted to include: receiving a request from the second access and mobility node (117) or the second session management node (112), and sending the session list to the second access and mobility node (117) or the second session management node (112), wherein the request is adapted to include the first SUPI associated with the UE (121).

64. The user data node (114) according to any one of claims 61-63, wherein, the following Any one of them: - The subscription data provided to the second access and mobility node (117) is adapted to include 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 include session management subscription data associated with the second SUPI and / or the UE (121).

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

66. The user data node (114) according to claim 65, wherein, Providing the subscription data to the first session management node (111) is adapted to include: 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 is adapted to include the second SUPI, and wherein the subscription data is adapted to include session management subscription data associated with the second SUPI and / or the UE (121).

67. A computer program including instructions that, when executed on at least one processor, cause the at least one processor to perform a method according to any one of claims 1-33, which is respectively executed 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).

68. A carrier comprising the computer program according to claim 67, wherein, The carrier is one of the following: electronic signal, optical signal, electromagnetic signal, magnetic signal, electrical signal, radio signal, microwave signal, or computer-readable storage medium.

Images