Apparatus and method for managing quality of service flow migration between PDU sessions of same UE

Abstract

The invention relates to a communication network. The disclosure relates to managing data traffic transmissions for multiple traffic flows associated with PDU session pairs. The UE connects with a first AN over a first PDU session, while connecting with a second AN over a second PDU session. The first AN and the second AN employ the same type of RAN. A first CPF is disclosed to obtain first indication information indicating whether data transmission of a UE supports a flow migration capability. The flow migration capability indicates a capability to switch data traffic transmissions between redundant transmissions and parallel transmissions. If the first PDU session supports the first PDU session, the first CPF determines flow migration information, and the flow migration information comprises mapping information between service flows in the first PDU session and the second PDU session; flow migration information is provided to the UE and / or the related UPF.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications. For example, this disclosure relates to apparatus and methods for managing quality-of-service (QoS) flow migration between PDU sessions of the same user equipment. This disclosure provides a control plane entity for managing one or more service flows of user equipment (UE). This disclosure also provides a UE that can be managed by the control plane entity. Furthermore, this disclosure provides corresponding methods and computer programs. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) SA1 TR22.856 Release 19 defines use cases for metaverse applications that require high reliability, extremely low latency, and high bandwidth. In mobile networks, this type of application is associated with Real-Time Broadband Communication (RTBC) services.

[0003] Extended reality (XR) and the metaverse are becoming increasingly important in medical procedures. For example, 3GPP SA1 TR 22.856 Release 19 defines a use case for the metaverse in critical healthcare services (FS_METAVERSE TR 22.856 Section 5.10). In this use case, physicians can perform surgery remotely using XR applications and can connect to the operating room via a mobile network through the UE. In this XR application, a 5G mechanism is proposed to achieve Ultra Reliable Low Latency Communication (URLLC), such as through Dual Connectivity (DC) with redundancy mechanisms as defined in TR 23.501. This mechanism specifies that two PDU sessions are established through different RAN nodes and UPFs, and these two PDU sessions are paired with each other. Paired PDU sessions may have the following general characteristics:

[0004] • Each corresponding PDU session contains two QoS streams configured with the same or similar QoS requirements to enable XR application data transmission.

[0005] • Data packets related to XR applications are repeated on the UE side and sent from the UE to the application (i.e., uplink), and then repeated on the UPF side and sent from the UPF to the UE (i.e., downlink).

[0006] • Insert a packet stream into the first paired PDU session (e.g., insert it into a suitable QoS stream).

[0007] • Insert another duplicate packet stream into the second paired PDU session (e.g., into another suitable QoS stream).

[0008] In this scenario, there are two non-overlapping paths between the UE (located in the operating room) and the XR application (located on the data network). Data traffic for the XR application (e.g., a stream requiring a 5 Mbps bit rate) is repeatedly transmitted through these two non-overlapping paths. In this case, although the actual data traffic required by the application is a 5 Mbps stream, the mobile operator actually uses 10 Mbps (5 Mbps for each path established in the paired PDU session) to provide a highly reliable connection for the application. Summary of the Invention

[0009] Consider an exemplary scenario: redundant transport implemented with dual connectivity for critical healthcare service data transmission, supporting the metaverse. This means two PDU sessions are paired, each configured with the same QoS parameters to handle data traffic. Packets associated with such applications are repeated. For example, assume a scenario where paired PDU sessions both use 5 Mbps GBR data traffic. During surgery, if a problem occurs on the patient side, such as a ruptured artery, a complete image of what happened on the patient side needs to be transmitted to the application. This means that, from the network's perspective, UE data traffic might suddenly jump from 5 Mbps to 10 Mbps. This results in a change in the QoS requirements for effective data traffic (i.e., the amount of data that needs to be transmitted (non-repeating data)). Therefore, to maintain the same reliability, the network needs 20 Mbps to handle the surge in application data traffic.

[0010] To handle sudden surges in data traffic during redundant transmissions implemented with dual connections, the following conventional methods can be used:

[0011] • Use triggering conditions to handle traffic surges: (a) the relevant UE or RAN node or control plane entity in the core network can trigger PDU session modification; (b) if the relevant RAN node in the scenario is unable to increase resources from 5 Mbps to 10 Mbps, PDU session release can be triggered on the core network side (e.g., to allow the establishment of new capable PDU sessions).

[0012] • Upon receiving the trigger condition, the core network side may perform the following actions: (a) The CN may attempt to perform PDU session modification in both paired PDU sessions to define new GBR QoS requirements (e.g., 10 Mbps) in both paired PDU sessions. However, this is still subject to the RAN nodes. Any RAN node associated with a paired PDU session may reject the PDU session modification if it lacks the necessary resources to support the new GBR QoS requirements. (b) The CN may release any PDU session in RAN nodes that do not meet the new GBR QoS requirements.

[0013] When the core network attempts to enforce these changes, critical data traffic for XR applications may be dropped on the RAN side due to the high control plane latency of the reconfigured PDU sessions. If one PDU session is released while another fails to meet the required QoS requirements associated with a surge in XR application traffic, the reliability of the XR application may be reduced by half or more. This prevents metaverse applications from updating with the necessary data in a timely manner. In this scenario, physicians are unable to respond promptly to problems arising on the patient side.

[0014] Furthermore, handling sudden surges in traffic can reduce network scalability in areas serving critical medical XR applications. This is because mobile networks may reserve resources in certain areas to dynamically increase QoS resources for paired PDU sessions during traffic spikes. This reduces the network's scalability to support more users simultaneously. Mobile operators may also be penalized for breaching reliability requirements for critical medical XR applications, such as failing to guarantee agreed-upon reliability levels by releasing paired PDU sessions.

[0015] In view of the foregoing, the purpose of this disclosure is to provide a solution to overcome these drawbacks. For example, one objective is to effectively handle traffic surges in XR applications by employing redundant transmissions with dual connectivity. Another objective is to avoid over-configuring QoS streams at the expected maximum possible bit rate. Yet another objective is to avoid causing permanent degradation of reliability requirements in paired PDU sessions associated with XR applications.

[0016] These and other objectives are achieved by means of the present disclosure as described in the independent claims. Advantageous implementations are further described in the dependent claims.

[0017] A first aspect of this disclosure provides a first control plane entity for managing data (traffic) transmission of multiple service flows of a UE. The multiple service flows of the UE are associated with a PDU session pair of the UE. A first PDU session in the PDU session pair can be connected to a data network via a first access network; a second PDU session in the PDU session pair can be connected to the data network via a second access network. The first access network and the second access network employ the same type of radio access technology.

[0018] The first control plane entity is used to acquire first indication information. The first indication information indicates whether one or more of the UE, the plurality of service flows, the first PDU session, the second PDU session, the PDU session pair, and the application support flow migration capability. The flow migration capability indicates the ability to switch data traffic transmission between redundant transmission and parallel transmission.

[0019] For redundant transmission, data packets associated with one or more first service flows among the plurality of service flows are repeated in one or more second service flows among the plurality of flows. The one or more first service flows are associated with the first PDU session, and the one or more second service flows are associated with the second PDU session.

[0020] For parallel transmission, the data packets (or data packets related to data transmission) associated with the one or more first service flows:

[0021] - Transmitted simultaneously in the first service stream and the second service stream, wherein data packets exceeding the capacity of the one or more first service streams are transmitted in the one or more second service streams, or

[0022] - Transmitted only in the one or more second service flows, wherein all data packets associated with the one or more first service flows are transmitted in the one or more second service flows.

[0023] The first control plane entity is also used for:

[0024] - Determine the UE, the plurality of service flows, the first PDU session, the second PDU session, the PDU session pair, and one or more support flow migration capabilities in the application based on the first indication information;

[0025] - Determine the flow migration information of the first PDU session and the second PDU session, wherein the flow migration information includes mapping information between the one or more first service flows in the first PDU session and the one or more second service flows in the second PDU session;

[0026] - Provide the flow migration information to one or more of the UE and user plane entities.

[0027] Optionally, the first control plane entity may be referred to as a QoS Flow Migration (QFM) manager. The first indication information may be referred to as a QFM capability indication or an indication of having QFM capability. The flow migration information may be referred to as QFM information.

[0028] According to this disclosure, resource shortages caused by sudden additional capacity requirements for XR applications can be mitigated, while the network can activate other mechanisms to reconfigure UEs in affected areas. By effectively employing and coordinating two paired paths based on flow migration information, burst packet loss experienced by XR UEs due to the need for additional data capacity for transmission can be reduced.

[0029] This approach improves network stability and robustness, for example, under various traffic conditions, and ensures the QoS of application data delivery.

[0030] In one implementation of the first aspect, the first control plane entity can also be used for:

[0031] Provide first handover information to one or more of the user plane entity and the UE, wherein the first handover information includes information for parallel transmission between the one or more first service flows and the one or more second service flows.

[0032] In another implementation of the first aspect, the first control plane entity can also be used for:

[0033] Provide second handover information to one or more of the user plane entity and the UE, wherein the second handover information includes information for redundant transmission between the one or more first service flows and the one or more second service flows.

[0034] In another implementation of the first aspect, the first indication information may include one or more of the following:

[0035] -Stream migration subscription indication;

[0036] - Indicators for application functionality during migration;

[0037] - Stream migration strategy indication.

[0038] In another implementation of the first aspect, the stream migration subscription indication is obtained from another entity that stores subscription information and the stream migration subscription indication, the stream migration subscription indication being used to indicate whether the stream migration capability is allowed or restricted based on one or more of the following information:

[0039] -UE identifier;

[0040] -Application information;

[0041] -Data network information;

[0042] -Network slice information;

[0043] -PLMN identifier;

[0044] -PDU session identifier;

[0045] -PDU session pair identifier;

[0046] - Stream description;

[0047] - Stream identifier.

[0048] In another implementation of the first aspect, the streaming migration application function indication is obtained from an application function entity, and the streaming migration application function indication is used to indicate whether the streaming migration capability is allowed or restricted based on one or more of the following information:

[0049] -UE identifier;

[0050] -Application information;

[0051] -Data network information;

[0052] -PDU session identifier;

[0053] -PDU session pair identifier;

[0054] - Transaction reference ID;

[0055] - Application session context identifier;

[0056] -Application session identifier;

[0057] - Stream description;

[0058] - Network slice information.

[0059] In another implementation of the first aspect, the flow migration policy indication is obtained from a second control plane entity or configured in the first control plane entity, the flow migration policy indication being used to indicate whether the flow migration capability is allowed or restricted based on one or more of the following information:

[0060] -UE identifier;

[0061] -Application information;

[0062] -Data network information;

[0063] - Network slice information.

[0064] In another implementation of the first aspect, the first control plane entity may also be used to acquire flow migration condition information, wherein the flow migration condition information includes monitoring information for activating or deactivating the flow migration capability.

[0065] The flow migration condition information can be referred to as QFM conditions.

[0066] In another implementation of the first aspect, the flow migration condition information is obtained through one or more of the following methods:

[0067] - Obtained together with the aforementioned stream migration subscription instruction;

[0068] - Acquired together with the aforementioned streaming migration application function indication;

[0069] - Acquired together with the aforementioned flow migration strategy indication;

[0070] - Configured in the first control plane entity;

[0071] -Included in the flow migration information.

[0072] In another implementation of the first aspect, the flow migration condition information includes one or more of the following:

[0073] - The upper limit of QoS-related measurements for activating the flow migration capability;

[0074] - Lower limit of QoS-related measurements to activate the flow migration capability;

[0075] - Maintain the maximum time interval for activating the aforementioned flow migration capability;

[0076] - Maintain the minimum time interval for activating the aforementioned flow migration capability;

[0077] - The threshold for deactivating the flow migration capability;

[0078] - Deactivate the degradation threshold for the flow migration capability.

[0079] In another implementation of the first aspect, the first control plane entity may also be used to obtain a flow migration trigger indication, wherein the flow migration trigger indication is a flag that indicates to the first control plane entity that establishing the first PDU session and / or the second PDU session requires the flow migration capability.

[0080] In another implementation of the first aspect, the first control plane entity may also be used to obtain the first indication information according to the flow migration trigger indication.

[0081] In another implementation of the first aspect, the mapping information includes information related to the operation of mapping one or more first service flows associated with the first PDU session to one or more second flows associated with the second PDU session, wherein the first PDU session and the second PDU session are associated with the same PDU session pair ID.

[0082] In another implementation of the first aspect, the mapping information further includes one or more of the following:

[0083] - Tunnel mapping information, used to map the core network tunnels and / or radio access network tunnels of the one or more first service flows associated with the first PDU session to one or more other core network tunnels and / or one or more other radio access network tunnels of the one or more second service flows associated with the second PDU session.

[0084] - Data traffic migration type, wherein the data traffic migration type defines the mapping of data traffic migrated from the one or more first service flows to the one or more second service flows.

[0085] In another implementation of the first aspect, the data traffic migration type indicates one of the following types:

[0086] -Reroute all data transmissions from the one or more first service flows to the one or more second service flows.

[0087] -Reroute data transmissions exceeding a specific bit rate from the one or more first service flows to the one or more second service flows.

[0088] - Reroute a certain percentage of data transmission from the one or more first service flows to the one or more second service flows.

[0089] For example, any of the following types are possible:

[0090] - Rerouting or moving all data transmissions to a single stream means moving all data transmissions from the first stream in the first PDU session to a second stream in the second PDU session.

[0091] - Splitting all data transmissions into multiple streams means moving all data transmissions from the first stream in the first PDU session to at least two second streams in the second PDU session.

[0092] - Rerouting data transmissions exceeding the bit rate to a single stream means moving data exceeding the first-order bit rate capacity of the first PDU session to a second stream in the second PDU session.

[0093] - Splitting data transmissions exceeding the bit rate into multiple streams means moving data exceeding the first-order bit rate capacity of the first PDU session to at least two second streams in the second PDU session.

[0094] - Rerouting or moving a certain percentage of data transmission to a single stream, which means moving a certain percentage of data transmission from the first stream in the first PDU session to a second stream in the second PDU session.

[0095] - Split a certain percentage of data transmission into a single stream, which means moving a certain percentage of data transmission from the first stream in the first PDU session to at least two second streams in the second PDU session.

[0096] In another implementation of the first aspect, the first control plane entity may also be used to send a notification to the application function entity, wherein the notification indicates one or more of the following:

[0097] - Allows the aforementioned stream migration capability;

[0098] - Limit the aforementioned flow migration capability;

[0099] -Activate the stream migration capability;

[0100] - Deactivate the aforementioned flow migration capability.

[0101] The notification that the above-mentioned application function has arrived can also be called a QFM status indication (or QFM status indication).

[0102] In another implementation of the first aspect, the first control plane entity may also be used to obtain one or more of the following:

[0103] - The user plane function and / or the network first handover indication of the UE, wherein the network first handover indication is used to indicate the need for or request to activate the flow migration capability;

[0104] - Application first switching indication of the application functional entity, wherein the application first switching indication is used to indicate the need for or request to activate the streaming migration capability.

[0105] In another implementation of the first aspect, the first control plane entity may also be used to determine the first handover information based on the network first handover indication, the application first handover indication, or an internal configuration or a combination thereof related to the first handover information.

[0106] In another implementation of the first aspect, the network first handover indication includes one or more of the following:

[0107] -UE identifier;

[0108] -PDU session pair identifier;

[0109] - First PDU session identifier and / or second PDU session identifier;

[0110] - First network candidate handover information and / or second network candidate handover information, wherein the first network candidate handover information and / or the second network candidate handover information are determined by the UP entity and / or the UE, the first network candidate handover information includes the first handover information, and the second network candidate handover information includes the second handover information.

[0111] In another implementation of the first aspect, the application first switching indication includes one or more of the following:

[0112] - Transaction reference ID;

[0113] - A flag indicating a request to activate the streaming migration capability to switch from redundant transmission to parallel transmission in the paired PDU session;

[0114] -Application information;

[0115] -Data network information;

[0116] -UE information;

[0117] - Stream description;

[0118] -The application session context identifier;

[0119] -PDU session pair ID;

[0120] -PDU Session ID;

[0121] -Network slice information;

[0122] - Application candidate first switching information and / or application candidate second switching information, wherein the application candidate first switching information and / or the application candidate second switching information are determined by the application function entity, the application candidate first switching information includes the first switching information, and the application candidate second switching information includes the second switching information.

[0123] In another implementation of the first aspect, the first switching information includes one or more of the following:

[0124] - Instructions to switch to parallel transmission;

[0125] -Information regarding the first PDU session and / or the second PDU session;

[0126] -Information regarding the first stream and / or the second stream;

[0127] -Information about the PDU session pair;

[0128] - Data traffic migration type;

[0129] - Modified flow migration information, wherein the modified flow migration information represents changes to the previously defined flow migration information for the PDU session in order to switch to parallel transmission.

[0130] In another implementation of the first aspect, the first switching information further includes one or more of the following:

[0131] -Accept confirmation of the first handover information of the network candidate received from the user plane entity and / or UE;

[0132] -Accept confirmation of the first application candidate switching information received from the application function;

[0133] - Modify the indication of the first handover information of the network candidate received from the user plane entity and / or the UE;

[0134] - Modify the indication of the first switching information of the application candidate received from the application function entity;

[0135] - An indication to reject the network candidate first handover information received from the user plane entity and / or the UE, wherein the indication to reject the network candidate first handover information indicates that the received network candidate first handover information cannot be applied;

[0136] - An indication to reject the first application candidate switching information received from the application function entity, wherein the indication to reject the first application candidate switching information indicates that the received first application candidate switching information cannot be applied.

[0137] In another implementation of the first aspect, the first switching information further includes a time indication for activating the stream migration capability.

[0138] In another implementation of the first aspect, the first control plane entity can also be used to send a notification to the application function entity. The notification indicates one of the following:

[0139] - Accept confirmation of the first switching information of the application candidate received from the application function entity;

[0140] - Modify the indication of the first switching information of the application candidate received from the application function entity;

[0141] - An indication to reject the application candidate first switching information received from the application function entity.

[0142] The notification that the above-mentioned application function has arrived can also be called a QFM status indication (or QFM status indication).

[0143] In another implementation of the first aspect, the first control plane entity may also be used to obtain one or more of the following:

[0144] - The user plane function and / or the network second handover indication of the UE, wherein the network second handover indication is used to indicate the need or request to deactivate the flow migration capability;

[0145] - Application second switching indication for application function, wherein the application second switching indication is used to indicate the need or request to activate the streaming migration capability.

[0146] In another implementation of the first aspect, the first control plane entity may also be used to determine the second handover information based on the network second handover indication, the application second handover indication, or an internal configuration or a combination thereof related to the second handover information.

[0147] In another implementation of the first aspect, the second switching information includes one or more of the following:

[0148] - Instructions to switch to redundant transmission;

[0149] -Information regarding the first PDU session and / or the second PDU session;

[0150] -Information regarding the first stream and / or the second stream;

[0151] -Information about the PDU session pair;

[0152] - Original stream migration information, wherein the original stream migration information represents the stream migration information previously defined for the PDU session pair before switching to parallel transmission;

[0153] - Instructions for using the original flow migration, wherein the instructions for using the original flow migration include a flag indicating previously defined flow migration information to be restored for the PDU session pair before switching to parallel transmission.

[0154] In another implementation of the first aspect, the first control plane entity may also be used to provide the flow migration condition information to one or more of the user plane entity and the UE, such that the user plane entity and one or more of the UE trigger the first network handover indication and / or the second network handover indication based on the received flow migration condition information.

[0155] In another implementation of the first aspect, the first control plane entity may also be used to monitor the flow migration condition information to determine whether to provide the first handover information and / or the second handover information to one or more of the user plane entity and the UE.

[0156] A second aspect of this disclosure provides a user plane flow migration entity associated with data transmission of multiple service flows of a UE. The multiple service flows of the UE are associated with a PDU session pair of the UE. A first PDU session in the PDU session pair can be connected to a data network via a first access network; a second PDU session in the PDU session pair can be connected to the data network via a second access network. The first access network and the second access network employ the same type of radio access technology. The user plane flow migration entity is used for:

[0157] - Receive flow migration information of the first PDU session and the second PDU session from the first control plane entity, wherein the flow migration information includes mapping information between one or more first service flows in the first PDU session and one or more second service flows in the second PDU session;

[0158] - Configure the first PDU session and the second PDU session to support flow migration capabilities based on the flow migration information.

[0159] The stream migration capability indicates the ability to switch data traffic transmission between redundant transmission and parallel transmission.

[0160] For redundant transmission, data packets associated with one or more first service flows among the plurality of service flows are repeated in one or more second service flows among the plurality of flows, wherein the one or more first service flows are associated with the first PDU session, and the one or more second service flows are associated with the second PDU session.

[0161] For parallel transmission, the data packets (or data packets related to data transmission) associated with the one or more first service flows:

[0162] - Transmitted simultaneously in the first service stream and the second service stream, wherein data packets exceeding the capacity of the one or more first service streams are transmitted in the one or more second service streams, or

[0163] - Transmitted only in the one or more second service flows, wherein all data packets associated with the one or more first service flows are transmitted in the one or more second service flows.

[0164] According to this disclosure, resource shortages caused by sudden additional capacity requirements from XR applications can be mitigated, while the network can activate other mechanisms to reconfigure UEs in affected areas. By effectively employing and coordinating two paired paths (e.g., paired PDU sessions) based on flow migration information, bursty packet loss experienced by XR UEs due to additional data capacity requirements can be reduced.

[0165] This approach improves network stability and robustness, for example, under various traffic conditions, and ensures the QoS of application data delivery.

[0166] In one implementation of the second aspect, the user plane flow migration entity may further be used to obtain first handover information from the first control plane entity, wherein the first handover information includes information for parallel transmission between the one or more first service flows associated with the first PDU session and the one or more second service flows associated with the second PDU session.

[0167] In another implementation of the second aspect, the user plane flow migration entity can also be used for:

[0168] The second handover information is obtained from the first control plane entity, wherein the second handover information includes information for redundant transmission between the one or more first service flows associated with the first PDU session and the one or more second service flows associated with the second PDU session.

[0169] In another implementation of the second aspect, the user plane flow migration entity may be at least a portion of the UE or a user plane entity.

[0170] In another implementation of the second aspect, the user plane flow migration entity is at least a part of the UE and is further configured to: provide a flow migration trigger indication to the first control plane entity, wherein the flow migration trigger indication is a flag indicating to the first control plane entity that establishing the first PDU session and / or the second PDU session requires the flow migration capability.

[0171] In another implementation of the second aspect, the user plane flow migration entity may also be used to provide one of the following to the first control plane entity:

[0172] - Network first handover indication, wherein the network first handover indication is used to indicate the need for or request to activate the flow migration capability;

[0173] - A second network handover indication, wherein the first network handover indication is used to indicate the need for or request to activate the flow migration capability.

[0174] In another implementation of the second aspect, the user plane flow migration entity can also be used for:

[0175] Receive flow migration condition information from the first control plane entity, wherein the flow migration condition information includes monitoring information for activating or deactivating the flow migration capability;

[0176] Based on the received flow migration condition information, send the first network handover instruction and / or the second network handover instruction.

[0177] A third aspect of this disclosure provides an application function (AF) entity associated with data traffic transmission of multiple service flows of a UE. The multiple service flows of the UE are associated with a PDU session pair of the UE. A first PDU session in the PDU session pair can be connected to a data network via a first access network; a second PDU session in the PDU session pair can be connected to the data network via a second access network. The first access network and the second access network employ the same type of radio access technology. The AF entity is used to obtain a notification from a first control plane entity including at least one of the following indications:

[0178] - Allows for stream migration capabilities

[0179] - Limit the flow migration capability.

[0180] - Activate the stream migration capability.

[0181] - Deactivate the aforementioned flow migration capability.

[0182] The stream migration capability indicates the ability to switch data traffic transmission between redundant transmission and parallel transmission.

[0183] For redundant transmission, data packets associated with one or more first service flows among the plurality of service flows are repeated in one or more second service flows among the plurality of flows, wherein the one or more first service flows are associated with the first PDU session, and the one or more second service flows are associated with the second PDU session.

[0184] For parallel transmission, the data packets associated with the one or more first service flows:

[0185] - Transmitted simultaneously in the first service stream and the second service stream, wherein data packets exceeding the capacity of the one or more first service streams are transmitted in the one or more second service streams, or

[0186] - Transmitted only in the one or more second service flows, wherein all data packets associated with the one or more first service flows are transmitted in the one or more second service flows.

[0187] According to this disclosure, resource shortages caused by sudden additional capacity requirements from XR applications can be mitigated, while the network can activate other mechanisms to reconfigure UEs in affected areas. By effectively employing and coordinating two paired paths (e.g., paired PDU sessions) based on flow migration information, bursty packet loss experienced by XR UEs due to additional data capacity requirements can be reduced.

[0188] This approach improves network stability and robustness, for example, under various traffic conditions, and ensures the QoS of application data delivery.

[0189] In one implementation of the third aspect, the AF entity may further be used to provide a flow migration application function indication to the first control plane entity, wherein the flow migration application function indication is used to indicate whether the flow migration capability is allowed or restricted based on one or more of the following information:

[0190] -UE identifier;

[0191] -Application information;

[0192] -Data network information;

[0193] -PDU session identifier;

[0194] -PDU session pair identifier;

[0195] - Transaction reference ID;

[0196] - Application session context identifier;

[0197] -Application session identifier;

[0198] - Stream description;

[0199] - Network slice information.

[0200] In another implementation of the third aspect, the AF entity can also be used to provide one of the following to the first control surface entity:

[0201] - Apply a first switching indication, wherein the application of the first switching indication is used to indicate the need for or request for activation of the streaming migration capability.

[0202] - Apply a second switching instruction, wherein the application of the second switching instruction is used to indicate the need or request to activate the streaming migration capability.

[0203] In another implementation of the third aspect, the application first switching indication includes one or more of the following:

[0204] - Transaction reference ID;

[0205] - A flag indicating a request to activate the streaming migration capability to switch from redundant transmission to parallel transmission in the paired PDU session;

[0206] -Application information;

[0207] -Data network information;

[0208] -UE information;

[0209] - Stream description;

[0210] -The application session context identifier;

[0211] -PDU session pair ID;

[0212] -PDU Session ID;

[0213] -Network slice information;

[0214] - Application candidate first switching information and / or application candidate second switching information, wherein the application candidate first switching information and / or the application candidate second switching information are determined by the application function entity, the application candidate first switching information includes the first switching information, and the application candidate second switching information includes the second switching information.

[0215] In another implementation of the third aspect, the AF entity may also be used to obtain a notification from the first control plane entity, wherein the notification indicates one of the following:

[0216] - Accept confirmation of the first switching information of the application candidate received from the application function entity;

[0217] - Modify the indication of the first switching information of the application candidate received from the application function entity;

[0218] - An indication to reject the application candidate first switching information received from the application function entity.

[0219] In another implementation of the third aspect, the AF entity may also be used to provide flow migration condition information to the first control plane entity, wherein the flow migration condition information includes monitoring information for activating or deactivating the flow migration capability.

[0220] In another implementation of the third aspect, the flow migration condition information, together with the flow migration application function indication, is provided by the AF entity to the first control plane entity.

[0221] A fourth aspect of this disclosure provides a method for managing data traffic transmission of multiple service flows of a UE. The multiple service flows of the UE are associated with a PDU session pair of the UE. A first PDU session in the PDU session pair can be connected to a data network via a first access network; a second PDU session in the PDU session pair can be connected to the data network via a second access network. The first access network and the second access network employ the same type of radio access technology. The method includes the following steps:

[0222] - The first control plane entity obtains first indication information, wherein the first indication information indicates whether one or more of the UE, the plurality of service flows, the first PDU session, the second PDU session, the PDU session pair and the application support flow migration capability;

[0223] - The first control plane entity determines the UE, the plurality of service flows, the first PDU session, the second PDU session, the PDU session pair, and one or more support flow migration capabilities in the application based on the first indication information;

[0224] - The first control plane entity determines the flow migration information of the first PDU session and the second PDU session, wherein the flow migration information includes mapping information between one or more first service flows in the first PDU session and one or more second service flows in the second PDU session;

[0225] - The first control plane entity provides the flow migration information to one or more of the UE and user plane entities.

[0226] The stream migration capability indicates the ability to switch data traffic transmission between redundant transmission and parallel transmission.

[0227] For redundant transmission, data packets associated with one or more first service flows among the plurality of service flows are repeated in one or more second service flows among the plurality of flows, wherein the one or more first service flows are associated with the first PDU session, and the one or more second service flows are associated with the second PDU session.

[0228] For parallel transmission, the data packets associated with the one or more first service flows:

[0229] - Transmitted simultaneously in the first service stream and the second service stream, wherein data packets exceeding the capacity of the one or more first service streams are transmitted in the one or more second service streams, or

[0230] - Transmitted only in the one or more second service flows, wherein all data packets associated with the one or more first service flows are transmitted in the one or more second service flows.

[0231] The implementation of the method in the fourth aspect can correspond to the implementation of the first control plane entity in the first aspect. The method and its implementation in the fourth aspect achieve the same advantages as the first control plane entity and its corresponding implementation in the first aspect.

[0232] A fifth aspect of this disclosure provides a method for managing data traffic transmission of multiple service flows of a UE. The multiple service flows of the UE are associated with a PDU session pair of the UE. A first PDU session in the PDU session pair can be connected to a data network via a first access network; a second PDU session in the PDU session pair can be connected to the data network via a second access network. The first access network and the second access network employ the same type of radio access technology. The method includes the following steps:

[0233] - The user plane flow migration entity receives flow migration information of the first PDU session and the second PDU session from the first control plane entity, wherein the flow migration information includes mapping information between one or more first service flows in the first PDU session and one or more second service flows in the second PDU session;

[0234] - The user plane flow migration entity configures the first PDU session and the second PDU session to support flow migration capabilities based on the flow migration information.

[0235] The stream migration capability indicates the ability to switch data traffic transmission between redundant transmission and parallel transmission.

[0236] For redundant transmission, data packets associated with one or more first service flows among the plurality of service flows are repeated in one or more second service flows among the plurality of flows, wherein the one or more first service flows are associated with the first PDU session, and the one or more second service flows are associated with the second PDU session.

[0237] For parallel transmission, the data packets associated with the one or more first service flows:

[0238] - Transmitted simultaneously in the first service stream and the second service stream, wherein data packets exceeding the capacity of the one or more first service streams are transmitted in the one or more second service streams, or

[0239] - Transmitted only in the one or more second service flows, wherein all data packets associated with the one or more first service flows are transmitted in the one or more second service flows.

[0240] The implementation of the method in the fifth aspect can correspond to the implementation of the user plane flow migration entity in the second aspect. The method and its implementation in the fifth aspect achieve the same advantages as the user plane flow migration entity and its corresponding implementation in the second aspect.

[0241] A sixth aspect of this disclosure provides a method for managing data traffic transmission of multiple service flows of a UE. The multiple service flows of the UE are associated with a PDU session pair of the UE. A first PDU session in the PDU session pair can be connected to a data network via a first access network; a second PDU session in the PDU session pair can be connected to the data network via a second access network. The first access network and the second access network employ the same type of radio access technology. The method includes: an application function entity obtaining a notification from a first control plane entity including at least one of the following indications:

[0242] - Allows flow migration capability, restricts said flow migration capability.

[0243] - Activate the stream migration capability.

[0244] - Deactivate the aforementioned flow migration capability.

[0245] The stream migration capability indicates the ability to switch data traffic transmission between redundant transmission and parallel transmission.

[0246] For redundant transmission, data packets associated with one or more first service flows among the plurality of service flows are repeated in one or more second service flows among the plurality of flows, wherein the one or more first service flows are associated with the first PDU session, and the one or more second service flows are associated with the second PDU session.

[0247] For parallel transmission, the data packets associated with the one or more first service flows:

[0248] - Transmitted simultaneously in the first service stream and the second service stream, wherein data packets exceeding the capacity of the one or more first service streams are transmitted in the one or more second service streams, or

[0249] - Transmitted only in the one or more second service flows, wherein all data packets associated with the one or more first service flows are transmitted in the one or more second service flows.

[0250] The implementation of the method in the sixth aspect can correspond to the implementation of the application functional entity in the third aspect. The method and its implementation in the sixth aspect achieve the same advantages as the application functional entity and its corresponding implementation in the third aspect.

[0251] A seventh aspect of this disclosure provides a system comprising one or more of a first control plane entity according to the first aspect or any implementation thereof, a user plane flow migration entity according to the second aspect or any implementation thereof, and an application function entity according to the third aspect or any implementation thereof.

[0252] The eighth aspect of this disclosure provides a computer program including instructions, wherein, when the program is executed by a computer, the instructions cause the computer to perform the method according to the fourth, fifth, or sixth aspect or any implementation thereof.

[0253] A ninth aspect of this disclosure provides a non-transitory storage medium for storing executable program code, wherein, when the executable program code is executed by a processor, the executable program code causes the method described according to the fourth aspect, the fifth aspect, the sixth aspect, or any implementation thereof to be executed.

[0254] The tenth aspect of this disclosure provides a chipset for performing the methods described in accordance with the fourth, fifth, sixth aspects, or any implementation thereof.

[0255] This disclosure specifically describes the following features, taking the QFM manager as a control plane entity and the UE that can be managed by the QFM manager as examples, which have the following features.

[0256] • Feature 1 (Binding QoS flows to enable migration mechanisms between paired PDU sessions):

[0257] - The QoS Flow Manager identifies whether a PDU session, UE, or QFI has QoS flow migration (QFM) capability;

[0258] - The QoS Flow Manager sends QFM policies to the UE; this is optional.

[0259] • Feature 2 (Providing QoS flow migration information to entities in the network):

[0260] - The QoS Flow Manager configures QFM information (e.g., native and visited QoS flow information) for each paired PDU session.

[0261] - The QoS Flow Manager configures QFM information for the UE and / or UPF.

[0262] • Feature 3 (Triggering and forcing the start and stop of QoS flow migration):

[0263] - The QoS Flow Manager activates or deactivates QFI (or excess QFI) migration between paired PDU sessions based on QFM information;

[0264] - The QoS Flow Manager sends notifications to application function entities regarding the activation or deactivation of QFM capabilities.

[0265] It should be noted that all devices, elements, units, and components described in this application can be implemented in software or hardware elements or any combination thereof. All steps performed by the various entities described in this application, and the functions described to be performed by the various entities, are intended to indicate that each entity is suitable for or used to perform its respective steps and functions. Although the specific functions or steps performed by external entities are not reflected in the detailed description of the specific elements of the entities performing the specific steps or functions in the following description of specific embodiments, those skilled in the art will understand that these methods and functions can be implemented by corresponding software or hardware elements or any combination thereof. Attached Figure Description

[0266] The above aspects and implementations will be explained below in conjunction with the accompanying drawings, in which:

[0267] Figure 1 A schematic diagram of a system provided in this disclosure is shown;

[0268] Figure 2 An example of a system provided in this disclosure is shown;

[0269] Figure 3 An example of the steps performed by the QFM manager as provided in this disclosure is shown;

[0270] Figure 4 This illustrates an example of interaction between entities;

[0271] Figure 5 An example of obtaining QFM information is shown;

[0272] Figure 6 An example of providing QFM information is shown;

[0273] Figure 7An example of signaling for QFM capabilities triggered by the QFM manager and QFM capabilities triggered by the AF is shown;

[0274] Figure 8 An example of signaling for QFM capability triggered by an SM entity is shown;

[0275] Figure 9 An example is shown of activating the QFM capability for excess traffic in a paired PDU session;

[0276] Figure 10A and Figure 10B An example of the system architecture provided in this disclosure is shown;

[0277] Figure 11 This illustrates an application scenario of the present disclosure;

[0278] Figure 12 This disclosure illustrates one method provided in this disclosure;

[0279] Figure 13 Another method provided in this disclosure is shown;

[0280] Figure 14 Another method provided in this disclosure is shown.

[0281] Explanation of terms used in this disclosure

[0282] QFI flow or QoS flow: An abstract concept that associates data traffic with specific QoS processing. QFI also defines an identifier for this abstract concept. In this disclosure, the terms "QFI," "flow," and "QoS flow" are synonyms and are used interchangeably.

[0283] One or more QoS flow sessions: This term defines the logical association between the UE and the data network, through which one or more QoS flows of the UE are grouped and / or managed.

[0284] Interaction: This term refers to an entity's ability to provide information to other entities and / or obtain information from other entities.

[0285] XR applications refer to a class of applications, such as multimodal applications, multimodal QoS streams, and multimodal PDU sessions.

[0286] QoS requirements (or QoS features) define one or more parameters associated with QoS, which is related to data traffic. Examples of QoS requirements or features are listed in Section 5.7 of 3GPP TS 23.501 as follows: 5G QoS Identifier (5QI), Allocation and Retention Priority (ARP), Guaranteed Flow Bit Rate (GFBR), Maximum Flow Bit Rate (MFBR), GBR QoS Flow, Non-GBR QoS Flow, Packet Loss Rate, Packet Delay Budget (PDB), Average Window, and Maximum Data Burst Volume (MDBV).

[0287] Redundant (or duplicated) transmission in a paired PDU session refers to the data transmission of duplicate data packets from one paired PDU session to another paired PDU session. This means that the same content of the data packets is transmitted simultaneously in two different PDU sessions (note: not strict clock synchronization, but rather that the same data packets are inserted into two paired PDU sessions at the same time).

[0288] Parallel (or simultaneous) transmission in a paired PDU session refers to data transmission using two paired PDU sessions to transmit non-duplicating data packets. This means that different content is contained in different data packets, which are transmitted simultaneously in the two PDU sessions (note: not strict clock synchronization, but rather that if two paired PDU sessions are used simultaneously, different data packets are inserted into the paired PDU sessions at the same time).

[0289] QFM capability indicates the possibility of converting (or switching) redundant and simultaneous transmissions in paired PDU sessions. That is, it can convert data transmission that uses one paired PDU session to transmit duplicate packets (e.g., using paired PDU sessions repeatedly or redundantly to transmit data traffic, also known as repeated or redundant transmission) into data transmission that uses two paired PDU sessions to transmit non-duplicate packets (e.g., using paired PDU sessions in parallel or simultaneously to transmit non-duplicate packets, also known as parallel or simultaneous transmission), and vice versa.

[0290] An indication of QFM capability (or QFM capability indication) refers to information that determines that a UE, PDU session, PDU session pair, QoS flow, and / or application supports QFM capability (e.g., may have or be able to configure QFM capability).

[0291] QFM information refers to information related to the mapping (or linking, binding, or associating) of core network tunnel information and / or radio access network tunnel information from one PDU session to another PDU session, wherein the two PDU sessions share the same PDU session pair ID, so that one of the two PDU sessions can be used for redundant transmission (e.g., transmitting duplicate data traffic of the UE).

[0292] Native QFI stream / QoS stream refers to the QFI stream or QoS stream in a PDU session, for which parameters have been requested and / or established for the PDU session.

[0293] A visited QFI / QoS stream refers to a QFI / QoS stream within a PDU session. This stream identifies one or more parameters that map QFI / QoS streams in different PDU sessions (e.g., streams requested and / or established in another PDU session) to native QFI / QoS streams in the PDU session that define this mapping.

[0294] QoS Flow Migration (QFM) information: Defines the mapping between a flow in one PDU session and another flow in another PDU session, where the two PDU sessions are paired. Pairing PDU sessions indicates the use of redundant transmissions within the paired PDU sessions. This information may also include definitions of QoS requirement mappings to enable mapping between two flows in paired PDU sessions.

[0295] QFM capability: Information indicating whether a UE, PDU session, PDU session pair, application, flow descriptor (or flow description), and / or flow supports (or is able to support) the activation of QoS flow migration mechanisms. These mechanisms are associated with one or more operations that can be taken in the mobile network to perform any of the following:

[0296] (a) Stop packet duplication for a given QoS flow in one of the paired PDU sessions and use the capacity reserved for the stopped QoS flow to transmit data packets for the QoS flow in another paired PDU session;

[0297] (b) Stop QoS migration by removing the traffic mapping from one QoS flow in one PDU session to another QoS flow in another PDU session, and restart (or resume) transmission of packets associated with one QoS flow in one PDU session and copies of packets in another QoS flow in another PDU session.

[0298] QFM Capability Activation (or Deactivation) Indicator: Information that triggers the QFM Manager to evaluate and / or determine QFM activation information.

[0299] QFM Activation Information: Defines information on the usage mode transition of resources (e.g., streams or QoS streams) in a paired PDU session, to switch from reusing these resources to using them in parallel.

[0300] QFM deactivation information: Defines information on the usage mode transition of resources (e.g., streams or QoS streams) in a paired PDU session, to switch from using these resources in parallel to reusing them.

[0301] The QFM status indicator defines whether the configuration of QFM capability has been enforced (or executed) for one or more of the following: UE, PDU session, PDU session pair, application, flow descriptor (or flow description), and AF-related flow; or defines whether QFM capability has been activated or deactivated to switch from reusing paired PDU sessions for data transmission to using paired PDU sessions in parallel for data transmission (or vice versa).

[0302] QFM subscription information determines or indicates whether paired PDU sessions associated with QFM filtering information allow and / or restrict QFM capabilities.

[0303] QFM filtering condition information defines features or parameters associated with PDU session information and / or UE information.

[0304] The QFM AF indicator determines whether paired PDU sessions associated with QFM AF filtering conditions allow and / or restrict QFM capabilities.

[0305] QFM AF filtering conditions define one or more features or parameters associated with application information, UE information, and flow description.

[0306] QFM policy indicators provide information to determine whether to allow and / or restrict the use of QFM capabilities for paired PDU sessions associated with QFM policy filtering conditions.

[0307] QFM policy filtering conditions define one or more features or parameters associated with application information, UE information, and network-related information. Detailed Implementation

[0308] Figure 1A schematic diagram of a system provided in this disclosure is shown. A first control plane (CP) entity 110 applied to the system is disclosed. The first CP entity 110 is used to manage the data (traffic) transmission of multiple service flows 121, 122, 141, 142 associated with UE 130. Data transmission of the multiple service flows can occur between UE application 137 (UE-side application) and network application 190 (network-side application). The multiple service flows 121, 122, 141, 142 of the UE are associated with UE PDU session pairs 120, 140. The first PDU session 120 in the PDU session pair can be connected to the data network through a first access network (AN) 151. The second PDU session 140 in the PDU session pair can be connected to the data network through a second AN 152. The first AN 151 and the second AN 152 use the same type of radio access technology. That is, the first AN 310 and the second AN 320 in this disclosure are not based on different radio access technologies. For example, both the first AN 151 and the second AN 152 can be 5GRAN or 6GRAN.

[0309] The first CP 110 (also referred to as QFM manager 110) is used to acquire first indication information. The first indication information (also referred to herein as QFM capability information) indicates whether UE 130, multiple service flows 121, 122, 141, 142, the first PDU session 120, the second PDU session 140, PDU session pairs, and one or more in the application support flow migration capability. Typically, the first indication information indicates whether flow migration capability is supported for data traffic transmission. Flow migration capability refers to the ability to switch data traffic transmission between redundant transmission (or repeated transmission) and parallel transmission (or simultaneous transmission).

[0310] In redundant transmission, data packets associated with one or more first service flows among multiple service flows are repeated in one or more second service flows among multiple flows. One or more first service flows are associated with a first PDU session, and one or more second service flows are associated with a second PDU session 220.

[0311] In parallel transmission, the data packets transmitted by the data flow are:

[0312] - Simultaneously transmitted in the first service stream and the second service stream, wherein data packets exceeding the capacity of one or more first service streams are transmitted in one or more second service streams, or

[0313] - Transmitted only in one or more second service flows, wherein all data packets associated with one or more first service flows are transmitted in one or more second service flows.

[0314] Figure 1 The example depicts two first service flows and two second service flows. However, it should be understood that the number of service flows included in each PDU session 120, 140 is not limited. The number of one or more first flows and the number of one or more second flows may be the same or different.

[0315] The first CP entity 110 is further configured to determine, based on the first indication information, one or more of the following: UE 130, multiple service flows 121, 122, 141, 142, first PDU session 120, second PDU session 140, PDU session pairs, and application support for flow migration capabilities. The first CP entity 110 is also configured to determine flow migration information (also referred to as QFM information) for the first PDU session 120 and the second PDU session 140. The flow migration information includes mapping information between one or more first service flows 121, 122 in the first PDU session 120 and one or more second service flows 141, 142 in the second PDU session 140. The first CP entity 110 is also configured to provide flow migration information to one or more of the following: UE 130 and user plane (UP) entities (also referred to as user plane functions (UPF)) 171, 172. Figure 1 Two UPFs are depicted exemplarily in the diagram. However, it should be understood that the number of one or more UPFs is not limited. For example, a first AN 151 and a second AN 152 may also be connected to a common UPF ( Figure 1 (Not shown in the image).

[0316] Based on the received flow migration information, the UE and / or UPF configure the first PDU session 120 and the second PDU session 140 to support flow migration capability according to the flow migration information.

[0317] In one possible scenario, the first CP entity 110 may be used to provide first handover information to one or more of UPF 171 and UE 172. The first handover information includes information for parallel transmission between one or more first traffic flows 121, 122 and one or more second traffic flows 141, 142.

[0318] In another possible scenario, the first CP entity 110 can be used to provide second handover information to one or more of the UPF and UE 130. The second handover information includes information for redundant transmission between one or more first service flows and one or more second service flows.

[0319] According to this disclosure, the first CP entity has the following characteristics or capabilities:

[0320] F110: Binding QoS flows to enable migration mechanisms between paired PDU sessions:

[0321] - Capable of identifying PDU sessions, UEs, or QFIs with QFM capabilities.

[0322] - Capable of issuing QFM policies to the UE (optional, depending on the implementation);

[0323] F120: Provides QoS flow migration information to entities in the network.

[0324] - Configure QFM information (e.g., native and visited QoS flow information) for each paired PDU session.

[0325] - Capable of configuring QFM information for UE and / or UPF;

[0326] F130: Trigger and enforce the start and stop of QoS flow migration:

[0327] - Activate or deactivate QFI (or excess QFI) migration between paired PDU sessions based on QFM information.

[0328] - Send a notification to the AF regarding the activation or deactivation of QFM capabilities.

[0329] Figure 2 An example of a system provided in this disclosure is shown. Figure 2 The system shown can be based on Figure 1 The system structure shown. Figure 1 and Figure 2 Corresponding elements in the same structure can have the same characteristics and functions.

[0330] In the control plane, the QFM manager 110 can be a new CP network function (NF) or included in an existing CP NF (such as a PCF or SMF). Therefore, any CP NF with QFM manager functionality can be simply referred to as a QFM manager. AF 180 is also extended via a QFM-capable AF agent to support the exchange of QFM-related information. UE 130 and UPF 171 / 172 are extended via a QFM-capable UE agent and a QFM-capable UPF agent, respectively. The extensions to UE 130 and UPF 171 / 172 enable these entities to support receiving and processing QFM information 111 and, based on QFM information 111, enforce the migration of QoS flows (e.g., the entire QoS flow or excess traffic of a QoS flow) from one PDU session to another suitable QoS flow in a paired PDU session. This stops the duplication of QoS flow traffic within the paired PDU session.

[0331] The QFM Manager 110 can be configured with one or more of the following capabilities:

[0332] -F201: Obtain an indication of QFM capability from AF and / or other CP functions and / or according to configuration. The indication of QFM capability determines that the UE and / or PDU session and / or PDU session pair and / or apply and / or one or more flow descriptors (or flow descriptions) and / or one or more flows have QFM capability (i.e., it is possible to have or be able to configure QFM capability). QFM capability defines the conversion (or switching) of data transmission that uses paired PDU sessions to transmit duplicate packets (e.g., duplicate or redundant data traffic using paired PDU sessions, also known as duplicate or redundant transmission) to data transmission that uses two paired PDU sessions to transmit non-duplicate packets (e.g., parallel or simultaneous transmission of non-duplicate packets using paired PDU sessions, also known as parallel or simultaneous transmission), and vice versa. This switching also enables a UE served by two RAN nodes using the same type of RAT to stop packet duplication using resources of one or more flows in one paired PDU session, and to switch the entire data traffic of a QoS flow or excess data traffic of one QoS flow to the QoS flow in the other paired PDU session.

[0333] -F202: Manages QFM-capable QoS flows based on QFM information for each paired PDU session (e.g., using or controlling QFM information or leveraging QFM information). QFM information defines the mapping between flows in one paired PDU session and flows in the other. Both paired PDU sessions are identified as QFM-capable.

[0334] -F203: Provide QFM information to the SM entity associated with the paired PDU session;

[0335] -F204: Apply and / or one or more flow descriptors (or flow descriptions) and / or one or more flows to obtain QFM capability activation (or deactivation) indication for UE and / or PDU sessions and / or PDU session pairs and / or apply and / or one or more flow descriptors (or flow descriptions) and / or one or more flows;

[0336] -F205: Determine QFM activation information based on QFM capability activation or deactivation indication and / or QFM information. QFM activation information defines information on the transition of resource (flow or QoS flow) usage mode in a paired PDU session, to switch from reusing these resources to using them in parallel (or vice versa);

[0337] -F206: Provide QFM activation information to the SM entity associated with the paired PDU session.

[0338] Alternatively, the QFM Manager 100 can also be configured with one or more of the following optional capabilities:

[0339] F207: The QFM manager can also be used to provide the AF with a QFM status indication describing whether the configuration of QFM capability has been enforced (or executed) for the UE and / or PDU session and / or PDU session pair and / or applied and / or one or more flow descriptors (or flow descriptions) and / or one or more flows associated with the AF; or whether QFM capability has been activated or deactivated to switch from reusing paired PDU sessions for data transmission to using paired PDU sessions in parallel for data transmission (or vice versa).

[0340] F208: The QFM Manager can also be used to obtain instructions with QFM capabilities. Instructions with QFM capabilities can be obtained through one of the following possible methods:

[0341] - (a) Subscription information extended via QFM subscription information is retrieved from the UDM. In this case, the indication of QFM capability is QFM subscription information.

[0342] - (b) Receive QFM AF indications directly from the AF (or via other control plane functions or as an intermediate CP between the SMF and the AF). In this case, the indication with QFM capability is the QFM AF indication.

[0343] - (c) Associated with UE policy. For example, the UE registration process is extended by the UE providing a QFM indication. The AMF triggers a UE policy association process extended with the QFM indication on the PCF side. The PCF triggers an extended UE configuration update process to provide the UE with a QFM policy, including the QFM policy indication and / or QFM conditions, during the UE's registration with the network.

[0344] F209: The QFM manager can be triggered by the QFM indication of an SM entity (e.g., UE) to request, subscribe to, or query other CP entities to obtain indications with QFM capabilities.

[0345] F210: The QFM Manager can be used to obtain QFM capability activation (or deactivation) instructions through one of the following possible methods:

[0346] a. The QFM manager identifies the data traffic associated with paired PDU sessions that have QFM capabilities based on QFM conditions and / or local information and / or local policies and / or local monitoring.

[0347] b. Obtain network-triggered candidate QFM activation information from at least one SM entity associated with a paired PDU session that has QFM capability.

[0348] c. Obtain AF-triggered candidate QFM activation information from the AF to switch duplicate transmissions in the paired PDU session to parallel transmissions (or vice versa).

[0349] F211: The QFM Manager can be used to obtain QFM conditions in one of the following ways:

[0350] (a) QFM conditions are configured (e.g., local policies as QFM managers).

[0351] (b) Obtained with QFM subscription instructions;

[0352] (c) Acquired together with QFM AF indication;

[0353] (d) Acquired together with QFM policy indications;

[0354] (e) Retrieve during SM strategy association.

[0355] F212: The QFM information determined by the QFM manager may include (among other things):

[0356] (a) Native QFI (or QoS flow) information (i.e., information associated with one of the paired PDU sessions that defines the QoS flows or one or more QFIs that have been requested and established for that PDU session).

[0357] (b) One or more visited QFI (or QoS flow) information (i.e., defining a QoS flow or one or more QFIs associated with the native QoS flow, for example, a QoS flow or one or more QFIs having the same and / or equivalent QoS requirements as the native QoS flow, but which has been requested and established in the paired PDU session).

[0358] F213: The QFM Manager can be used to obtain QFM policies. A QFM policy defines the QFM capabilities that should be activated against QFM policy filter conditions and / or QFM conditions, to activate and / or deactivate the QFM capabilities of paired PDU sessions associated with QFM information. QFM policies can be obtained in one of the following ways:

[0359] (a) By local decision (or based on local policy). The QFM manager identifies when a QFM policy needs to be defined and defines its parameters;

[0360] (b) Receive QFM policies from other CP entities (e.g., PCFs) that are capable of defining policies in the network;

[0361] (c) By examining and requesting other CP entities (e.g., PCF) that can define policies in the mobile network, determine whether there are any QFM policies to be applied to the UE and / or paired PDU sessions.

[0362] F214: The QFM manager can also be used to provide QFM policies to SM entities.

[0363] F215: The QFM Manager can also be used to receive QFM capability activation indications. The SM entity can determine the QFM capability activation indication based on QFM policies and / or monitoring information. The QFM capability activation indication may include network-triggered candidate QFM activation information.

[0364] Figure 3 An example of the steps performed by the QFM manager as provided in this disclosure is shown. Figure 3 The system in the middle can be based on Figure 1 and Figure 2 System construction in. Figures 1 to 3 Corresponding elements in the same structure can have the same characteristics and functions. For simplicity, Figure 3 The part with is omitted in the middle. Figure 1 and Figure 2 The same element in the attached figure is the same as the element in the figure.

[0365] Figure 3 Three exemplary steps are described. Figure 3 Step 301 illustrates a new capability of the QFM manager: binding QoS flows to prepare for activating or deactivating QFM capabilities (also known as feature F310). Steps 302 and 303 depict a new capability of the QFM manager: providing QFM information to entities in the network.

[0366] Step 301: For each service request in a PDU session (e.g., PDU session A) and / or for each PDU session request, the QFM manager uses:

[0367] (a) Identify whether QoS flows and / or specific QoS flows and / or applications in the requested paired PDU session support and should be activated for the UE. The QFM manager uses information during PDU session establishment (and / or service request) to check QFM capabilities. There may be different schemes for checking QFM capabilities, which further involves Figure 5 .

[0368] (b) In response to determining that the QFM capability associated with the PDU session should be activated, configure QFM information to enable mapping between QoS flows in the paired PDU sessions.

[0369] Step 302: During the configuration of QoS flows in a PDU session, the QFM manager can be used to provide (or configure) QFM information to SM entities (e.g., UEs and / or UPFs associated with the paired PDU session).

[0370] Step 303: The QFM manager can be used to provide (e.g., inform or notify) a QFM status indication to the AF. The QFM status indication informs the AF that QFM capabilities have been configured for the UE and / or PDU session and / or PDU session pair and / or application and / or one or more flow descriptors (or flow descriptions) and / or one or more flows associated with the AF.

[0371] Figure 4 An example of interaction between entities provided in this disclosure is shown. Figure 4 The system in the middle can be based on Figures 1 to 3 System construction in. Figures 1 to 4 Corresponding elements in the same structure can have the same characteristics and functions. For simplicity, Figure 4 The part with is omitted in the middle. Figure 1 and Figure 2 The same element in the attached figure is the same as the element in the figure.

[0372] Figure 4 The interaction between entities is described to enable a new capability: activating or deactivating the use of QFM capabilities in a paired PDU session with QFM information. To activate or deactivate QFM capabilities for a paired PDU session with QFM information (or configured with or associated with QFM information), there may be three main steps 304, 305, and 306 executed sequentially.

[0373] Step 304 (304a to 304d): The entity can be used to monitor data traffic and QoS satisfaction conditions in a paired PDU session (e.g., this can be done through the mechanism defined in TS 23.501).

[0374] Step 305 (305a to 305d) may include three operations performed by the corresponding entity: determining whether QFM capability needs to be activated or deactivated for the paired PDU session; defining QFM activation information; and configuring QFM activation information for the SM entity (UE and associated UPF).

[0375] Step 306: The QFM manager can be used to inform the AF of the QFM status indication, which describes the activation of QFM capability for the paired PDU session.

[0376] For steps 304 and 305, there can be different implementations 304a to 304d and 305a to 305d:

[0377] - Scenario 310 (QFM capability triggered by QFM manager): In this case, steps 304, 305 and 306 are executed by the QFM manager and are referred to as 304a, 305a and 306.

[0378] - Scheme 320 (SM Entity-Triggered QFM Capability): In this scheme, in steps 304 and 305 (referred to as steps 304c and 304d), the required UE and / or UPF are identified for activating QFM capability for paired PDU sessions with QFM information. In steps 305c and 305d, the UE and / or UPF may be used to determine network-triggered candidate QFM activation information (including QFM information change suggestions (or proposals)) to enable switching from duplicate data traffic transmission to parallel data traffic transmission (or from parallel data traffic transmission to duplicate data traffic transmission). The UE and / or UPF may be used to provide such information to the QFM manager. Step 305a, related to defining the QFM activation information and configuring the QFM activation information for the SM entity (UE and associated UPF), is performed by the QFM manager. The QFM manager performs step 306.

[0379] - Scenario 330 (AF-triggered QFM capability): In this scenario, the AF performs step 304 (referred to as step 304b) to monitor UE and / or PDU sessions and / or PDU session pairs and / or applications and / or one or more flow descriptors (or flow descriptions) and / or one or more flows associated with QFM information. In step 305 (referred to as step 305b), the AF determines whether QFM capability activation or deactivation needs to be triggered and provides such an indication to the QFM manager (e.g., a QFM capability activation or deactivation indication). The QFM manager performs other tasks described in step 305 (or 305a), such as defining QFM activation information and configuring QFM activation information for SM entities (UE and associated UPF). The QFM manager also performs step 306.

[0380] Generally, in all three schemes, whether activating or deactivating QFM capabilities, the common feature is defining the information used to achieve the actual migration of data traffic between paired PDU sessions. Furthermore, regardless of the scheme used, activating or deactivating QFM capabilities produces the same effect in the system.

[0381] Applicable to all three scenarios, the QFM activation information used to switch from reusing paired PDU sessions to using paired PDU sessions in parallel may include one or more of the following:

[0382] -QFM capability activation type: Switch from reusing paired PDU sessions to using paired PDU sessions in parallel.

[0383] - Pair the selected source PDU session and target PDU session in the PDU session.

[0384] - One or more selected native QFIs in the source PDU session,

[0385] -One or more selected visitor QFIs,

[0386] -One or more selected native QFIs in the target PDU session to stop transmitting their duplicate data traffic.

[0387] - The mapping between the selected native QFI and one or more selected visited QFIs, wherein duplicate traffic is stopped and data traffic associated with the native QFI is started.

[0388] - Data traffic migration type: Defines how data traffic from the native QFI is migrated to the visited QFI (e.g., to the QFI in the paired PDU session).

[0389] Data traffic migration type can indicate one of the following:

[0390] - All traffic to the selected native QFI is rerouted to the selected visited QFI. This approach is suitable when the RAN node serving the native QFI cannot provide the required QoS through PDU sessions on that RAN node and other RAN nodes.

[0391] - Excess traffic of the native QFI relative to the configured bit rate is transmitted in one or more selected visited QFIs (for example, if more than one visited QFI is needed to support the native QFI, the excess data traffic can be further split).

[0392] The QFM activation information used to deactivate a switch from parallel use of paired PDU sessions to repeated use of paired PDU sessions may include one or more of the following:

[0393] -QFM capability activation type: Switch from parallel use of paired PDU sessions to repeated use of paired PDU sessions.

[0394] - A list of one or more visited QFIs in the source PDU session, which are used for parallel data traffic transmission associated with a selected native QFI. The mapping between the visited QFI and the native QFI needs to be removed.

[0395] - One or more selected native QFIs in the target PDU session to restart the transmission of its duplicate data traffic.

[0396] When the QFM activation information includes an indication to switch from repeated (or redundant) use of a paired PDU session to parallel use of a paired PDU session, the QFM activation information is equivalent to the first handover information. When the QFM activation information includes an indication to switch from parallel (or simultaneous) use of a paired PDU session to repeated (or redundant) use of a paired PDU session, the QFM activation information is equivalent to the second handover information.

[0397] Furthermore, QFM activation information (e.g., first handover information during QFM flow migration activation) may also include modified QFM information (e.g., the mapping of tunnel information changes if compared with QFM information determined before identifying the need to activate QFM capability or before activating QFM capability (e.g., the original QFM information)). When QFM capability deactivation is enforced, QFM activation information may include the original QFM information (e.g., QFM information previously defined for the PDU session pair before activating the switch to parallel transmission).

[0398] Optionally, the QFM activation information may also include one or more of the following:

[0399] - Confirm that the obtained network-triggered or AF-triggered candidate QFM activation information can be used without making any changes.

[0400] - Updated network-triggered or AF-triggered candidate QFM activation information. At this point, the QFM manager determines that the information obtained from the SM entity and / or AF can only be used if changes are made. Then, the QFM manager updates the appropriate fields and derives the updated QFM activation information.

[0401] - Deny the acquisition of candidate QFM activation information triggered by network and / or AF, indicating to the SM entity or AF that the acquired information cannot be used to activate the QFM capability.

[0402] For steps 303 and 306, SMF can be used to open the QFM capability as a new event type. Users of the event can subscribe to it by setting the event type to "QFM capability," and other optional parameters for subscription can include one or more of the information listed in the QFM AF filter criteria.

[0403] The information included in the notifications generated by the SMF to the user determines, for a given QFM AF filtering condition information for the subscription, the SMF uses to notify the user of one or more of the following:

[0404] - Allows QFM capability;

[0405] -Activate QFM capabilities;

[0406] -Activate QFM capabilities.

[0407] There are several possible ways for QFM capability event notifications to reach the AF. For example, it can be achieved by extending the Nnef_AFsessionWithQoS_Notify service opened by the NEF, using the same mechanism defined for opening PCF notifications to the AF. In this case, the PCF needs to subscribe to the QFM capability events opened by the SMF. This information can then be passed from the PCF to the NEF, and finally to the AF. Alternatively, if the AF is an operator-trusted NF, it can directly subscribe to the SMF to use the information.

[0408] Figure 5 An example of obtaining QFM information provided in this disclosure is shown. Figure 5 Based on Figures 1 to 4 The features are constructed publicly. Figures 1 to 5 Corresponding elements in the same text can have similar characteristics and functions.

[0409] Figure 5 The control plane entity used as the QFM manager is shown (e.g., Figure 5 The SMF (110) in the example obtains useful information to determine whether QFM capabilities should be used for paired PDU sessions. In some other examples, the PCF can be used as a QFM manager. Figure 5 Different alternative implementations of step 301 are shown.

[0410] Typically, SMF can be used to verify QFM capabilities via subscription information (Alternative 510) or via AF (Alternatives 520 and 530). Figure 5 The top steps 1 to 3 illustrate the interactions related to alternative 510. The bottom steps 3 (a, b) and 4 illustrate the interactions related to alternatives 520 and 530, so that SMF 110 prepares to evaluate whether QFM capability should be activated for the paired PDU session. In this case, the SMF obtains the information needed in step 4 to determine whether the paired PDU session is allowed (or not) to use QFM capability.

[0411] Even if the SMF does not explicitly receive the paired PDU session identifier in Alternative 520 or Alternative 530: at least based on the UE information and / or flow description and / or application information received from the AF and / or PCF, the SMF can, in step 4 of Alternatives 520 and 530, map the information (such as UE information) in the PDU session request in step 3 (a, b) and the indication for using redundant transmission (e.g., paired PDU session ID) to the information received by the SMF from the AF or PCF in step 2 of Alternative 520 to determine whether the paired PDU session requested by the UE is allowed (or not allowed) to use QFM capability. In the following, step X of Alternative Y may be referred to as step YX. Because Figure 5 Steps 3a, 3b, and 4 at the bottom can be shared by alternatives 520 and 530, and they are referred to as steps 523-3a, 523-3b, and 523-4.

[0412] Optionally, a QFM indication may be used in steps 510-1 (a, b) and 523-3 (a, b). A QFM indication is a parameter that may be included in information sent by the UE (e.g., as an SM entity) to the core network, such as through a PDU session request via the RAN node and AMF (N2 container) or during the UE registration process. The SMF can be used to receive the QFM indication. This parameter can be implemented as a flag indicating to the SMF that a UE requesting a PDU session is requested to use QFM capability for one or more paired PDU sessions. When a QFM indication is sent during UE registration, this information reaches the SMF during the SM policy association process. A QFM indication may also be referred to as a flow migration trigger condition indication.

[0413] For alternatives 510 and 530, when the SMF receives a PDU session request, it checks whether QFM capability should be activated for the paired PDU session (and then performs a check on subscription information or receives information related to the SM policy). However, in alternative 520, when the SMF receives a QFM AF indication, a PDU session may or may not be established.

[0414] It should be noted that Alternative 520 is not exclusive; it can be implemented even if the UE and SMF can operate with other alternatives. For example, the UE can request a PDU session without a QFM indication. The AF can determine whether QFM capability should be activated for the UE's paired PDU session (or a set of flow descriptions). Accordingly, the AF provides a QFM AF indication that allows the SMF to modify the PDU session to use QFM capability and QFM information for the paired PDU session.

[0415] The details of each alternative are explained below.

[0416] Alternative 510: Verify subscription information

[0417] SMF retrieves subscription information extended with QFM subscription information by interacting with UDM or PCF (which interacts with UDR). For example, session management subscription data in UDM can be extended with QFM subscription information and / or QFM conditions. QFM subscription information can also be referred to as stream migration subscription indication.

[0418] Alternative solution 510 may include the following steps:

[0419] Step 510-1a: UE 130 can be used to provide SMF 110 with a redundant PDU session request, PDU session pairing ID, and QFM indication via the first RAN 151 and AMF.

[0420] Step 510-1b: UE 130 can be used to provide SMF 110 with a redundant PDU session request, PDU session pairing ID, and QFM indication via the second RAN 1552 and AMF.

[0421] Step 510-2a: SMF can be used to provide UE subscription information to UDM.

[0422] Step 510-2b: SMF can be used to receive subscription data including QFM subscription information.

[0423] Step 510-3: SMF can be used to determine QFM information. QFM information can be associated with the paired PDU session.

[0424] SMF can use QFM subscription information to determine whether QFM capabilities are permitted based on one or more of the following QFM filtering conditions:

[0425] -UE identifier (e.g., SUPI);

[0426] - One or more application information;

[0427] - One or more data network information (e.g., DNN and / or DNAI);

[0428] - One or more network slices (e.g., S-NSSAI);

[0429] - One or more PLMN identifiers (e.g., PLMN ID);

[0430] - One or more PDU session identifiers;

[0431] - Identifier of the PDU session pair;

[0432] - One or more stream descriptors (or stream descriptions);

[0433] - One or more stream identifiers.

[0434] For example, the SMF, acting as the QFM manager, can send a request to the UDM using the Nudm_SDM_Get service. The input parameters of this request include one or more of the following: SUPI, the selected DNN, the S-NSSAI of the HPLMN, and the serving PLMN ID. In response, the SMF receives session management subscription data including QFM subscription information. This indicates that QFM capabilities are permitted based on any indicated input parameters in the service (e.g., UE, selected DNN, S-NSSAI, PLMN ID) or a combination thereof. Therefore, when the SMF receives a PDU session request including a pairing PDU session indication for redundant transmission, if this indication includes UE ID (SUPI), DNN, S-NSSAI, and PLMN ID with the same values ​​as the QFM subscription information, the SMF is allowed to activate QFM capabilities and define the QFM information to be used for the pairing PDU session.

[0435] If the PCF is a QFM manager and the PCF retrieves subscription information from the UDR via the Nudr_DM_Query service operation, the above principles also apply.

[0436] QFM subscription information can be implemented using one or more of the following methods:

[0437] - A flag (e.g., QFM Allow) indicating that QFM capability is allowed based on any QFM filtering condition parameter (e.g., SUPI, DNN, S-NSSAI, PLMN ID) included in the service for retrieving subscription information.

[0438] - A flag (e.g., deny QFM) indicating that QFM capability is not allowed based on any QFM filtering condition parameters (e.g., SUPI, DNN, S-NSSAI, PLMN ID) included in the service for retrieving subscription information.

[0439] - Flags (e.g., QFM allowed) and a list of QFM filtering conditions, indicating whether QFM capability is allowed based on the given QFM filtering condition information. For example, QFM can be allowed based on a specific UE ID and a specific DNN.

[0440] - Flags (e.g., deny QFM) and a list of QFM filtering conditions that indicate whether QFM capability is not allowed based on the given QFM filtering condition information. For example, QFM can be disallowed based on a specific UE ID and a specific DNN.

[0441] Alternative 520: Providing information to the control plane via AF

[0442] The AF can provide information to the control plane via the Nnef_AFsessionWithQoS service through the NEF and / or via the Npcf_PolicyAuthorization service through the PCF. The AF providing information to the control plane includes QFM AF indications and / or QFM conditions when requesting or updating an AF session identified by a transaction reference ID (or by other means of identifying the application and its associated QoS flows).

[0443] The information provided by the AF is either stored in the PCF for transmission to the SMF (QFM Manager) during SM policy association, or stored in an NF such as a UDM or UDR for retrieval by the SMF when needed.

[0444] Alternative solution 520 may include the following steps:

[0445] Step 520-1: PCF and AF establish an AF session with QoS requirements, including QFM AF indication.

[0446] Step 520-2: SM policy association update process between SMF 110 and PCF, including QFM AF indication.

[0447] Step 523-3a: UE 130 can be used to provide SMF 110 with a redundant PDU session request, PDU session pairing ID and optional QFM indication via the first RAN 151 and AMF.

[0448] Step 523-3b: UE 130 can be used to provide SMF 110 with a redundant PDU session request, PDU session pairing ID and optional QFM indication via the second RAN 1552 and AMF.

[0449] SMF can use the QFM AF indicator to determine whether QFM capability is allowed based on any of the following QFM AF filtering conditions:

[0450] - Application information (e.g., application ID, external application identifier);

[0451] - Data network information (e.g., DNN and / or DNAI);

[0452] -UE information (e.g., IP address, MAC address, or SUPI);

[0453] - One or more flow descriptions (e.g., source IP address, destination IP address, port number, protocol information);

[0454] - Identifier of the application session context;

[0455] -Identification and / or reference of the AF session;

[0456] - Transaction reference ID;

[0457] - Paired PDU session identifier;

[0458] - Indicator for paired flow description;

[0459] - One or more PDU session identifiers;

[0460] - One or more network slices (e.g., S-NSSAI).

[0461] QFM AF indication can be implemented according to one or more of the following schemes:

[0462] - A flag (e.g., Allow QFM) indicates that QFM capability is allowed based on any QFM AF filter condition parameter included in one or more services for creating or updating AF sessions.

[0463] - A flag (e.g., deny QFM) indicates that QFM capability is not allowed based on any QFM AF filtering condition parameter included in one or more services for creating or updating AF sessions.

[0464] - Flags (e.g., Allow QFM) and a list of QFM AF filtering conditions, indicating whether QFM capability is allowed based on a given QFM AF filtering condition information included in one or more services for creating or updating AF sessions.

[0465] - Flags (e.g., deny QFM) and a list of QFM filtering conditions that indicate that QFM capabilities are not allowed based on a given QFM AF filtering condition information included in one or more services for creating or updating AF sessions.

[0466] QFM AF indicators can also be called flow migration application function indicators.

[0467] Alternative Solution 530: Association via UE Policy

[0468] For example, during registration, the UE provides a UE policy container that includes a QFM indication. The same QFM indication defined for alternatives 510 and 530 can be reused. In alternative 530, the QFM indication first arrives at the PCF. The PCF is able to determine (e.g., by retrieving subscription information associated with policy data) which UE policy including the QFM policy should be configured for the UE.

[0469] The QFM indication during registration is the trigger condition for the PCF (with or without QFM manager capability) to define the QFM policy. The PCF requests policy data information associated with the UE subscription from the UDR. This policy data information on the UDR side is extended through the QFM policy indication and / or QFM conditions.

[0470] Alternative solution 530 may include the following steps:

[0471] Step 530-1: UE 130 performs UE registration including QFM instructions.

[0472] Step 530-2b: UE 130 performs UE policy association including QFM policy.

[0473] Step 530-2c: SM (UE) policy association update process between SMF 110 and PCF, including QFM AF indication.

[0474] Step 523-3a: UE 130 can be used to provide SMF 110 with a redundant PDU session request, PDU session pairing ID and optional QFM indication via the first RAN 151 and AMF.

[0475] Step 523-3b: UE 130 can be used to provide SMF 110 with a redundant PDU session request, PDU session pairing ID and optional QFM indication via the second RAN 1552 and AMF.

[0476] QFM policy indicators determine whether QFM capabilities are permitted based on one or more of the following QFM policy filtering conditions:

[0477] - Application information (e.g., application ID, external application identifier)

[0478] - Data network information (e.g., DNN and / or DNAI)

[0479] -UE information (e.g., IP address and / or MAC address and / or SUPI)

[0480] - One or more network slices (e.g., S-NSSAI)

[0481] The SMF (QFM Manager) can obtain the QFM policy from the PCF, or determine the QFM policy based on information provided to the SMF by the PCF, URD, or UDM.

[0482] QFM policy indications can also be called flow migration policy indications.

[0483] The existing processes in the network can be extended as follows:

[0484] - (a) The UE registration process can be extended by the UE providing a QFM instruction in the UE policy container;

[0485] - (b) The AMF triggers an extension process on the PCF side to include a UE policy container with a QFM indication;

[0486] - (c) When this request is received from the AMF, the PCF triggers an extended UE configuration update procedure to provide the UE with the QFM policy.

[0487] The QFM policy indication in Alternative 530 may include information related to allowing or restricting QFM capabilities, including any of the following:

[0488] - A flag (e.g., QFM allowed) indicates that QFM capability is allowed based on any QFM policy filtering condition parameter included in one or more services for creating or updating UE policies.

[0489] - Flags (e.g., QFM allowed) and a list of QFM policy filtering conditions, indicating whether QFM capability is allowed based on a given QFM policy filtering condition information included in one or more services for creating or updating UE policies.

[0490] - Flags (e.g., deny QFM) and a list of QFM policy filtering conditions that indicate that QFM capabilities are not allowed based on a given QFM policy filtering condition information included in one or more services for creating or updating UE policies.

[0491] - Flags (e.g., deny QFM) and a list of QFM filtering conditions that indicate that QFM capability is not allowed based on a given QFM AF filtering condition information included in one or more services for creating or updating UE policies.

[0492] QFM conditions may include one or more parameters that can be used in alternatives 510, 520, and 530. QFM conditions may be provided to the QFM manager (e.g., SMF) 110 along with information issued in alternatives 510 and 520. Additionally, the SMF may be configured with QFM conditions, but this information is only used during the activation or deactivation of QFM capabilities. For alternative 530, QFM conditions may be stored in the UDR. When the PCF is triggered to define a UE policy, the PCF requests policy data including the QFM conditions from the UDR.

[0493] QFM conditions may include information related to the decision (or triggering conditions or information) to activate or deactivate the QFM capability (e.g., parameters and / or parameter and associated values ​​and / or monitored information). For example, QFM conditions may include one or more of the following:

[0494] - The upper limit of QoS-related measurements defines the upper limit of one or more QoS-related measurements, and QFM capability should be activated;

[0495] - The lower limit of QoS-related measurements defines the upper limit of one or more QoS-related measurements, and QFM capabilities should be deactivated;

[0496] - The maximum time interval at which QFM capability can be activated (i.e., when packets stop repeating in one of the paired PDU sessions, where one or more QoS flows in that PDU session are used for simultaneous data transmission in both paired PDU sessions, i.e., packets are not repeated in either PDU session).

[0497] - The minimum time interval at which QFM capability can be activated (i.e., packets stop repeating in one of the paired PDU sessions, where one or more QoS flows in that PDU session are used for simultaneous data transmission in two paired PDU sessions, i.e., packets are not repeated in either PDU session).

[0498] - Reliability degradation threshold indicates the minimum tolerable reduction in data transmission reliability when QFM capability is activated (QFM capability should be deactivated if this threshold is exceeded).

[0499] - The upper limit of QoS-related measurements defines the upper limit of one or more QoS-related measurements, and QFM capability should be activated;

[0500] -QoS-related measurements are monitored and / or calculated information that indicates specific values ​​of QoS parameters themselves and / or QoS satisfaction information related to QoS flows.

[0501] Optionally, QoS-related measurements may include one or more of the following: buffered data traffic of the stream, peak bit rate, packet delay budget (PDB), packet jitter, packet loss rate, number of GFBR notification control messages, packet error rate (PER), and aggregate average bit rate (AABR).

[0502] Figure 6 An example of providing QFM information as provided in this disclosure is shown. Figure 6 Based on Figures 1 to 5 The features are constructed publicly. Figure 5 Optional features for performing step 302 are shown. Figures 1 to 6 Corresponding elements in the same text can have similar characteristics and functions.

[0503] like Figure 6 As shown, the SMF, acting as the QFM manager 110, determines to activate QFM capability for the PDU session pair of UE 130, such as... Figure 6 As shown in step 1, the SMF receives a PDU session establishment request for a PDU session pair, which is to be used for redundant transmission based on QFM capability. The SMF is used to configure QFM information for each paired PDU session, such as... Figure 6Step 2 is shown in the description. Further details regarding the possible implementations of QFM information will be elaborated upon in the description.

[0504] Once the QFM information is configured, the SMF is used to provide this information to the SM entities associated with such PDU sessions. Examples of SM entities can be one or more UPFs associated with the PDU session pair and the UE.

[0505] During the N4 session establishment process, the SMF is used to provide appropriate QFM information to one or more UPFs for each PDU session, such as Figure 6 As shown in step 3a. Optionally, if the UPF needs to determine the activation of QFM capability, the QFM conditions can also be provided by the SMF. The UPF (e.g., including a UPF agent with QFM capability) receives the QFM information and establishes an appropriate mapping between CN tunnels, such as... Figure 6 As shown in step 3b.

[0506] The SMF provides the UE with QFM information for each paired PDU session via the AMF N2 message transfer procedure. The AMF-side Namf_Communication_N1N2MessageTransfer service and the NAS signaling between the AMF and the UE are extended to include QFM information and / or QFM conditions, such as... Figure 6 As shown in step 4a, the UE is used to configure QFM information (e.g., to perform tasks using a UE agent with QFM capabilities).

[0507] Furthermore, if the UE and / or UPF need to monitor and trigger QFM activation, both the UE and UPF are used to begin monitoring QFM conditions (such as...). Figure 6 (See steps 5a and 5b in the text). This can correspond to... Figure 3 The QFM capability triggered by SM entities introduced in [the document]. If using... Figure 3 The QFM capability triggered by the QFM manager introduced in the code then allows SMF to begin monitoring the QFM conditions of PDU session pairs (such as...). Figure 6 (See step 5c in the diagram).

[0508] PDU session information includes essential information for the SMF to control the path from the UE to the data network (DN) (e.g., DNN), as well as other optional features (e.g., QoS requirements, routing policies, redundant transmissions). The SMF also controls some important information in the PDU session (in addition to QoS-related information), as described below:

[0509] -PDU Session ID

[0510] - PDU session ID (or paired PDU session ID).

[0511] - QoS Flow ID (QFI) identifies the flow in which data traffic is transmitted or associated;

[0512] - Associated N3 (e.g., a path or link between a RAN node and a UPF), optional N9 (a path or link between two or more UPFs), and N6 (a path or link between a UPF and a DN) CN tunnels for PDU sessions and / or each QFI.

[0513] - CN tunnels (or CN tunnel identifiers or CN tunnel information) associated with QFI and / or PDU sessions for redundant transmission.

[0514] - The RAN node associated with QFI (which can also be known to SMF through the mapping from N3 to RAN nodes).

[0515] The UE (e.g., the SM entity) also controls important information related to the flow in the PDU session, such as one or more of the following:

[0516] -PDU Session ID

[0517] - PDU session ID (or paired PDU session ID).

[0518] - QoS Flow ID (QFI) identifies the flow in which data traffic is transmitted or associated.

[0519] - RAN tunnel information (e.g., Data Radio Bearer (DRB) or AN resources, such as primary cell, secondary cell, and secondary primary cell, that can be used for data traffic associated with the UE's QFI).

[0520] Therefore, when two PDU sessions share the same PDU session pair ID, and one of the PDU sessions is used for redundant transmission (e.g., transmitting duplicate data traffic of the UE), QFM information can be used to map (or link or associate) CN tunnel information and / or RAN tunnel information from one PDU session to another PDU session.

[0521] In this disclosure, possible implementations of QFM information can be based on the definition of logical flows: native and visited QoS flows (or flows or QFIs). A logical flow (or one or more flow abstractions or one or more logical concepts or one or more logical references or one or more virtual flows) is a reference (or pointer) that enables a cross-link (or cross-reference or mapping) between flows requested (and / or configured and / or established) in one PDU session to be mapped to one or more flows in another PDU session, wherein the two PDU sessions use the same paired PDU session identifier.

[0522] The native stream is used to identify information that has been requested and / or established and / or configured for a PDU session, including QoS streams (or streams, stream descriptions, or QFIs).

[0523] The visited flow is used to identify information that has been requested and / or established and / or configured for another paired PDU session, such as a QoS flow (or flow description or QFI).

[0524] For each PDU session that is requested and established (e.g., identified by the PDU session ID) along with the paired PDU session, according to this embodiment, the SMF associates one or more of the following information, including QFM information, with the PDU session information and / or each QoS flow (or QFI or flow descriptor or process description), involving one or more native and visited QFI concepts, such as... Figure 3 As shown:

[0525] - A list of one or more native QFIs,

[0526] -The status of each QFI,

[0527] -A list of one or more visiting QFIs,

[0528] -PDU Session Pair ID

[0529] - One or more native QFI PDU session IDs,

[0530] -One or more PDU session IDs visiting the QFI

[0531] - CN tunnel information for each native QFI

[0532] - RAN tunnel information for each native QFI

[0533] -QFM tunnel mapping defines the information for mapping data traffic from the native QFI to the visited QFI.

[0534] Examples of QFM tunnel mapping information can be tuples that include one or more of the following:

[0535] - Native QFI

[0536] -One or more visiting QFIs,

[0537] - One or more PDU session IDs that visit the QFI.

[0538] -PDU Session Pair ID

[0539] - Data traffic migration type, possible values ​​are: move all data traffic, move data traffic exceeding the bit rate, move a certain percentage of data traffic;

[0540] -One or more CN tunnel information for visiting QFI

[0541] - RAN tunnel information for one or more visited QFIs

[0542] - The usage mode of each native QFI's paired PDU session defines whether the QFI is used for repeating data traffic or for transmitting non-repeating data packets (i.e., simultaneous or parallel transmission).

[0543] Another possible implementation of QFM information is to associate a simplified set of information with a PDU session based on the QFM tunnel mapping. In this case, for each PDU session associated with a PDU session pairing ID, the QFM information may include one or more of the following:

[0544] - A list of one or more QFIs in a paired PDU session.

[0545] - PDU session ID for pairing PDU sessions

[0546] -PDU Session Pair ID

[0547] - CN tunnel information for each QFI in the PDU session

[0548] - RAN tunnel information for each QFI in the PDU pairing session

[0549] -QFM tunneling mapping, which is a tuple that includes any of the following:

[0550] -- Pairing a PDU session with one or more (or a list or set) mappings of QFIs to one or more QFIs.

[0551] --Mapping of QFI CN tunnel information to one or more (or a column or a set) of CN tunnel information of one or more QFIs in a paired PDU session

[0552] --Mapping of one or more (or a column or a set) of RAN tunnel information from one or more QFIs in a paired PDU session to one or more QFIs' RAN tunnel information.

[0553] --Data traffic migration type, possible values ​​are: move all data traffic, move data traffic exceeding the bit rate, move a certain percentage of data traffic.

[0554] The data traffic migration type may be information listed directly in the QFM information, rather than necessarily being part of the QFM tunnel mapping information. Furthermore, the data traffic migration type may be included therein, or its value may be defined when defining the QFM activation information.

[0555] The concepts of native and visited flows enable precise mapping of tunnel information (CN and RAN), i.e., abstraction of tunnel IDs. For example, if a UE moves to a different RAN node and uses the native / visited abstraction, the UE (e.g., with a UE agent possessing QFM capability) can update the tunnel ID information for radio resources without any changes or notifications to the SMF. Furthermore, when a UE moves, if the CN tunnel connecting to the new RAN node serving the UE is not associated with a different N3 interface, there is no need to additionally notify the CN tunnel ID change to update the QFM information. This CN tunnel change is also abstracted within the native and visited flow concepts.

[0556] Figure 7 An example of signaling for QFM capabilities triggered by the QFM manager (scheme 310) and QFM capabilities triggered by the AF (scheme 330) is shown. Figure 7 Features can be applied Figures 1 to 6 .

[0557] Figure 7 Step 1 illustrates the key difference between Scheme 310 (QFM capability triggered by the QFM manager) and Scheme 330 (QFM capability triggered by the AF). The difference lies in the entity that performs monitoring for QFM conditions or any other information related to QoS flows. For example, Figure 7 Step 1b1 shows that the AF identifies the need to trigger QFM capability activation. This activation is achieved through step 1b2, where the AF provides the SMF with candidate QFM activation information triggered by the AF.

[0558] This information exchange can be achieved using the PCF as an intermediate NF, through indirect communication between the AF and the SMF (QFM Manager). In this case, the AF uses the Nnef_AFsessionWithQoS service via the NEF and / or the Npcf_PolicyAuthorization service via the PCF, which includes information contained in the AF-triggered candidate QFM activation information. Once the PCF provides the SMF with an SM policy association update based on the received AF-triggered candidate QFM activation information (either directly from the AF or via the NEF in an AF session related to the QoS process), this information reaches the SMF. In this case, the AF-triggered candidate QFM activation information reaching the SMF may include one or more of the following:

[0559] -Transaction reference ID,

[0560] - A flag indicating that QFM capability should begin to activate, switching from reusing paired PDU sessions to using paired PDU sessions in parallel.

[0561] - A flag indicating that QFM capability should begin to activate, switching from parallel use of paired PDU sessions to reuse of paired PDU sessions.

[0562] - Application information (e.g., application ID, external application identifier).

[0563] - Data network information (e.g., DNN and / or DNAI).

[0564] -UE information (e.g., IP address, MAC address, or SUPI).

[0565] - One or more flow descriptions (e.g., source IP address, destination IP address, port number, protocol information).

[0566] -Identifier of the application session context,

[0567] - Pair PDU session identifier

[0568] -One or more PDU session identifiers,

[0569] - One or more network slices (e.g., S-NSSAI).

[0570] When the candidate QFM activation information triggered by the AF includes an indication to switch from repeated (or redundant) use of a paired PDU session to parallel use of a paired PDU session, the QFM activation information is equivalent to applying the first handover indication. When the candidate QFM activation information triggered by the AF includes an indication to switch from parallel (or simultaneous) use of a paired PDU session to repeated (or redundant) use of a paired PDU session, the candidate QFM activation information triggered by the AF is equivalent to applying the second handover information.

[0571] Another alternative to implementing step 1b2 is through direct interaction between the SMF and AF. This can be achieved by the AF opening an event called "AF-triggered QFM capability" and the SMF subscribing to this event for paired PDU sessions with QFM capability. Subscription input parameters may include one or more of the following:

[0572] • Transaction reference ID,

[0573] • Application information (e.g., application ID, external application identifier).

[0574] • Data network information (e.g., DNN and / or DNAI).

[0575] • UE information (e.g., IP address, MAC address, or SUPI).

[0576] • One or more flow descriptions (e.g., source IP address, destination IP address, port number, protocol information).

[0577] • Identifier of the application session context,

[0578] • Pair PDU session identifier

[0579] • One or more PDU session identifiers

[0580] • One or more network slices (e.g., S-NSSAI).

[0581] The notification message received by SMF is the candidate QFM activation information triggered by AF. The parameters in this message may include:

[0582] • Subscription relevance identifier (associating notification messages with specific parameters requested in the subscription input), and / or

[0583] • A flag indicating that the QFM capability to switch from reusing paired PDU sessions to using paired PDU sessions in parallel should be activated for paired PDU sessions associated with the parameters included in the subscription input parameters.

[0584] If the AF is capable, the candidate QFM activation information triggered by the AF may also include information related to the QFM information, such as candidate QFM information, which the AF sends so that the SMF can use the candidate QFM information from the AF as input to determine the QFM activation information.

[0585] When the candidate QFM activation information triggered by the AF includes an indication to switch from repeated (or redundant) use of a paired PDU session to parallel use of a paired PDU session, the candidate QFM information is equivalent to applying the first candidate handover indication if the AF can provide candidate QFM information. When the candidate QFM activation information triggered by the AF includes an indication to switch from parallel (or simultaneous) use of a paired PDU session to repeated (or redundant) use of a paired PDU session, the candidate QFM information is equivalent to applying the second candidate handover indication if the AF can provide candidate QFM information.

[0586] When the SMF recognizes that QFM capabilities should be activated, it determines the QFM activation information, for example, deciding (or choosing) to switch from repetitive data traffic transmission to parallel use of resources associated with the visited flow for application data traffic data transmission without repetitive packets in the native and visited flows (e.g., ...). Figure 7 (See step 2 in the diagram). SMF determines the values ​​of the previously defined QFM activation information parameters (or fields).

[0587] The SMF may provide one or two QFM activation messages to each UE and / or UFP. This may occur if QFM capability should be activated for UL traffic and / or DL ​​traffic. Alternatively, the SMF may also include the same QFM activation information for each UE and / or UFP, along with information on QFM capability activation for UL and DL, in the same QFM activation message.

[0588] (One or more) QFM activation information is prepared by the SMF and provided to the UPF via an N4 session update (e.g.) Figure 7 (as shown in step 3a), while the QFM activation prepared by the SMF is provided to the UE through the extension of the N2 SM information (e.g. Figure 7 (See step 3b in the text).

[0589] SMF in Figure 7 In step 4, the AF is notified, which can be based on the mechanisms described in steps 303 and 306. The SMF then notifies the AF that the QFM capability has been activated. Additionally, the SMF can also notify the AF that the requested AF-triggered candidate QFM activation information has been accepted (without any changes), rejected, or modified to activate the QFM capability.

[0590] exist Figure 7 Following step 3, QFM information changes are enforced in both the UE and UPF based on the QFM activation information received directly or indirectly from the SMF (via AMF, N2 SM information). This results in the parallel use of resources in the paired PDU session based on the QFM activation information.

[0591] SMF (in Scenario 310) or AF (in Scenario 330) is used to continuously monitor QFM conditions and / or other application-level information to determine when QFM capabilities should be deactivated (e.g. Figure 7 (See step 5 in the diagram). When the conditions are met, the SMF determines the QFM activation information again, this time to switch from using resources in a paired PDU session in parallel to reusing resources in a paired PDU session. Figure 7 Steps 6 and 7 are used to deactivate the QFM capability and send a notification to the AF that the QFM capability has been deactivated. Figure 6 and Figure 7 It can be adopted with Figure 7 Steps 3 and 4 in the previous section are implemented in a similar way.

[0592] Figure 8 An example of signaling for a QFM capability (scheme 320) triggered by an SM entity is shown. Figure 8 Features can be applied Figures 1 to 6 In this scenario, the UE and UPF serve as examples of SM entities used to trigger / activate QFM capabilities. The UE and UPF may receive the QFM conditions in advance.

[0593] Based on the received QFM conditions, the UE and UPF ( Figure 8 Step 1) begins monitoring QFM conditions. The UE and / or UPF may identify QFM conditions that meet the activation QFM capability ( Figure 8 Step 2a or 2b in the text). In fact, Figure 8 Steps 2a and 2b can be executed simultaneously, or only one of them can be executed.

[0594] Optionally, the UE may be able to detect the conditions that activate QFM capability for UL traffic (i.e., from the UE to the DN). Due to the issues with DL traffic from the DN to the UE, the UPF may be better at identifying the conditions that trigger QFM capability activation.

[0595] The UE and / or UPF provide network-triggered candidate QFM activation information to the SMF. For the UE, this information can be provided to the SMF via N2SM information, where the UE requests PDU session modification, including the network-triggered candidate QFM activation information. For the UPF, the network-triggered candidate QFM activation information may include a report to be sent from the UPF to the SMF. Alternatively, there may be a service open by the UPF that the SMF can invoke to request and retrieve information, or the SMF may subscribe to the service to receive notifications about network-triggered candidate QFM activation information.

[0596] When the network-triggered candidate QFM activation information includes an indication to switch from repeated (or redundant) use of paired PDU sessions to parallel use of paired PDU sessions, the network-triggered candidate QFM activation information is equivalent to the network's first handover indication. When the network-triggered candidate QFM activation information includes an indication to switch from parallel (or simultaneous) use of paired PDU sessions to repeated (or redundant) use of paired PDU sessions, the network-triggered candidate QFM activation information is equivalent to the network's second handover information.

[0597] Network-triggered candidate QFM activation information may include one or more of the following:

[0598] -UE identifier (SUPI or IP address).

[0599] -PDU Session Pair ID

[0600] -One or more PDU session identifiers,

[0601] - A proposal for QFM activation information (or candidate QFM activation information), which is a proposal to configure resources (e.g., QoS flows or streams) in a paired PDU session to switch from resource reuse to parallel resource use. In other words, a proposal for QFM activation information includes relevant information for activating or deactivating QFM capabilities (e.g., QFM tunnel information associated with QFM information, etc.) or candidate QFM information.

[0602] - A flag indicating that QFM capability should begin to activate, switching from reusing paired PDU sessions to using paired PDU sessions in parallel.

[0603] - Flag indicating that QFM capability should be deactivated (i.e., switching from parallel use of resources in a paired PDU session to reuse of resources in a paired PDU session).

[0604] When the network-triggered candidate QFM activation information includes an indication to switch from repeated (or redundant) use of paired PDU sessions to parallel use of paired PDU sessions, and candidate QFM information, the candidate QFM information included in the network-triggered candidate QFM activation information is equivalent to the network candidate first handover indication. When the network-triggered candidate QFM activation information includes an indication to switch from parallel (or simultaneous) use of paired PDU sessions to repeated (or redundant) use of paired PDU sessions, and candidate QFM information, the candidate QFM information is equivalent to the network candidate second handover indication.

[0605] The SMF receives network-triggered candidate QFM activation information from the UE and / or UPF. If a QFM activation proposal (or candidate QFM activation) exists, the SMF evaluates whether a proposed resource usage mode switch (from repeated use of paired PDU sessions to parallel use of paired PDU sessions) in the paired PDU session is appropriate. If no candidate QFM activation information exists, the SMF determines the QFM activation information itself.

[0606] exist Figure 8 In steps 4a and 4b, the SMF provides the UE and / or UPF with specific QFM activation information. The specific implementation of sending this information to the UE and UPF can follow... Figure 7 The same method described in step 3. The SMF uses the same implementation scheme presented in steps 303 and 306 to notify the AF of QFM capability activation.

[0607] The UE and / or UPF, based on the QFM activation information received (directly or indirectly) from the SMF, enforce the QFM information changes they control and begin monitoring QFM conditions to determine when to stop using resources in a paired PDU session in parallel and switch back to reusing resources in a paired PDU session. Figure 8 Step 6 in the process. When the QFM conditions are met, the UE and / or UPF send other network-triggered candidate QFM activation information to the SMF, including an indication to stop switching from parallel use of paired PDU sessions to repeated use of paired PDU sessions (i.e., deactivating QFM capability), such as... Figure 8 Step 7 is shown in the diagram.

[0608] SMF in Figure 8 The execution is performed in steps 8 and 9, and its execution method is the same as... Figure 8 Steps 3 and 4 are similar. The difference is that all information sent to the UE and / or UPF is used to deactivate the QFM capability, and a deactivation notification is sent to the AF using the same implementation mechanism described in steps 303 and 306.

[0609] QFM activation information may also include a time indication, indicating the time interval at which the QFM migration should be activated. For example, this time indication can be implemented by defining start and end segments; or it can be implemented as a numerical value (or delay or timer) indicating that the QFM migration should automatically deactivate after a given numerical value, delay, or timer has elapsed. In this case, in Figure 8 In step 7a, the UPF and / or UE provide QFM activation information to the SMF, including an indication that a timer (or time indicator) has been reached for the deactivation of the QFM. In this case, depending on the implementation, the UPF and / or UE can automatically revert to using the original QFM information without needing to... Figure 8In steps 9a and 9b, additional QFM activation information is received. In this case, deactivation is performed automatically.

[0610] Figure 9 An example is shown where QFM capability is activated for excess traffic of flows within a paired PDU session. In this example, for PDU session A, the visiting QFI #B1 is used to transmit excess traffic of QFI A#1 in PDU session A. For PDU session A, QFI #B1 is a visited flow because it is associated with PDU session B. Similarly, for PDU session B, QFI #A1 is a visited flow. The native and visited flow abstractions implement the association between mapped flows within a paired PDU session.

[0611] Figure 10A and Figure 10B An example of the architecture provided in this disclosure is shown.

[0612] Figure 10A An architecture conforming to 3GPP 5G principles, derived from Prose and ATSSS traffic offloading, is shown. This architecture may be complex but relatively fast. The QFM manager can be implemented in the SMF or PCF. QFM capabilities can be identified through subscription information or by associating QFM policies with UE policies. Triggering flow migration via the UE and / or UPF (Scheme 320) is a fast method to activate QFM capabilities. However, triggering QFM capabilities via the QFM manager itself is also permitted (Scheme 310).

[0613] Figure 10B An architecture conforming to 3GPP 5G principles is shown, supporting AF (Automatic Feedback) to influence QoS and redundant transmission using DC (Distributed Data Capability). This architecture may be simple, but it may be relatively slow. The QFM manager is implemented in SMF (Self-Managed Flowmeter) or PCF (Programmable Flowmeter). QFM capabilities are identified through AF information.

[0614] exist Figure 10A and Figure 10B In this implementation, when the QFM Manager is part of the PCF NF, the processes and services associated with SM policies are extended, enabling the PCF to provide the SMF with information related to any of the following: QFM capability indications, QFM information, QFM policies and QFM subscription information, QFM conditions, and QFM activation information (which is then forwarded to the SM entity via the SMF). Furthermore, the PCF can also obtain AF-triggered QFM activation information from the AF, provide QFM status indications to the AF, and use the SMF as an intermediary entity to obtain network-triggered QFM activation information from the UPF and / or UE, which provides or forwards this information to the PCF through SM policy-related processes.

[0615] Figure 11The application scenario of this disclosure is illustrated. This disclosure is applicable to 5G networks as defined by 3GPP in 3GPP TS 23.501. For simplicity, Figure 11 The specific CP functions used in this scenario are abstracted. Typically, AMF, SMF, PCF, UDR, and UDM are examples of CP NF. Figure 11 It also demonstrates dual connectivity (DC) that supports redundant transmission for critical healthcare applications in the metaverse. Figure 11 The two PDU sessions shown are paired, with one PDU session used to repeat data traffic from the UE to the DN to provide a certain level of data transmission reliability. The paired PDU sessions use the same type of radio access technology within the same mobile network (e.g., a single PLMN) (i.e., both PDU sessions use a single or identical RAT). If there is additional data traffic that a single PDU session A cannot handle, QFM capability can be activated for PDU session B according to this disclosure, which is consistent with... Figure 9 similar.

[0616] Figure 12 A method 1200 provided in this disclosure is illustrated. Method 1200 is used to manage data traffic transmission of multiple service flows of a UE. The multiple service flows of the UE are associated with a PDU session pair of the UE. A first PDU session in the PDU session pair can be connected to a data network via a first access network; a second PDU session in the PDU session pair can be connected to the data network via a second access network. The first access network and the second access network employ the same type of radio access technology.

[0617] Method 1200 is executed by the first control plane entity 110 and includes the following steps:

[0618] - Step 1201: The first control plane entity obtains the first indication information, wherein the first indication information indicates whether one or more of the UE, multiple service flows, the first PDU session, the second PDU session, the PDU session pair, and the application support flow migration capability;

[0619] - Step 1202: The first control plane entity determines the UE, multiple service flows, the first PDU session, the second PDU session, the PDU session pair, and one or more support flow migration capabilities in the application based on the first indication information;

[0620] - Step 1203: The first control plane entity determines the flow migration information of the first PDU session and the second PDU session, wherein the flow migration information includes mapping information between one or more first service flows in the first PDU session and one or more second service flows in the second PDU session;

[0621] - Step 1204: The first control plane entity provides flow migration information to one or more of the UE and user plane entities.

[0622] Stream migration capability indicates the ability to switch data traffic transmission between redundant and parallel transmissions.

[0623] For redundant transmission, data packets associated with one or more first service flows in multiple service flows are repeated in one or more second service flows in multiple flows, wherein one or more first service flows are associated with a first PDU session and one or more second service flows are associated with a second PDU session.

[0624] For parallel transmission, data packets associated with one or more first service flows:

[0625] - Simultaneously transmitted in the first service stream and the second service stream, wherein data packets exceeding the capacity of one or more first service streams are transmitted in one or more second service streams, or

[0626] - Transmitted only in one or more second service flows, wherein all data packets associated with one or more first service flows are transmitted in one or more second service flows.

[0627] Figure 13 Method 1300 provided in this disclosure is illustrated. Method 1300 is used to manage data traffic transmission of multiple service flows of a UE. The multiple service flows of the UE are associated with a PDU session pair of the UE. A first PDU session in the PDU session pair can be connected to a data network through a first access network; a second PDU session in the PDU session pair can be connected to the data network through a second access network. The first access network and the second access network employ the same type of radio access technology.

[0628] Method 1300 is executed by user plane flow migration entities 130, 171, and 172, and includes the following steps:

[0629] - Step 1301: The user plane flow migration entity receives flow migration information of the first PDU session and the second PDU session from the first control plane entity, wherein the flow migration information includes mapping information between one or more first service flows in the first PDU session and one or more second service flows in the second PDU session;

[0630] - Step 1302: The user plane flow migration entity configures the first PDU session and the second PDU session to support flow migration capability based on the flow migration information.

[0631] Figure 14A method 1400 provided in this disclosure is illustrated. Method 1400 is used to manage data traffic transmission of multiple service flows of a UE. The multiple service flows of the UE are associated with a PDU session pair of the UE. A first PDU session in the PDU session pair can be connected to a data network via a first access network; a second PDU session in the PDU session pair can be connected to the data network via a second access network. The first access network and the second access network employ the same type of radio access technology.

[0632] Method 1400 is executed by application function entity 190 and includes:

[0633] - Step 1401: The application functional entity obtains a notification from the first control plane entity that includes at least one of the following indications: allow flow migration capability, restrict flow migration capability, activate flow migration capability, deactivate flow migration capability, wherein the flow migration capability indicates the ability to switch data traffic transmission between redundant transmission and parallel transmission.

[0634] Figures 12 to 14 Methods can be shared and combined Figures 1 to 11 The publicly known identical or corresponding features will not be elaborated here.

[0635] For example, this disclosure provides QFM capability indicators, which can be implemented as: QFM subscription information, QFM AF indicators, or QFM policy indicators. For example, this disclosure also provides QFM information including QFM tunnel mapping information. QFM information can indicate the native and visited flow logic definitions for each paired PDU session. For example, this disclosure also provides:

[0636] - Supports QFM Manager triggering checks to obtain QFM capability indications;

[0637] - Allows the QFM manager or SM entity to trigger QFM conditions that activate or deactivate QFM capabilities;

[0638] - The QFM manager provides the AF with notifications about the QFM capability status of a given UE.

[0639] Tunnel mapping information can also be called QFM tunnel mapping.

[0640] In this way, network operators are able to alleviate resource shortages caused by sudden additional capacity requirements from XR applications, while the network activates other mechanisms to reconfigure UEs in the affected areas.

[0641] For example, this disclosure also provides instructions for activating or deactivating QFM capabilities, which can be implemented as follows:

[0642] -Local strategy;

[0643] - Network-triggered candidate QFM activation information;

[0644] -AF-triggered candidate QFM activation information.

[0645] For example, this disclosure also provides QFM activation information for switching between redundant and parallel transmissions, and QFM policies for determining the activation or deactivation conditions of QFM capabilities for paired PDU sessions.

[0646] In this way, by effectively using two paired paths, packet loss caused by sudden additional capacity requirements in XR UE flows can be eliminated or reduced.

[0647] This disclosure has been described in conjunction with various embodiments as examples and implementations. However, based on a study of the drawings, this disclosure, and the independent claims, those skilled in the art will be able to understand and implement other variations when carrying out the claimed subject matter. In the claims and the description, the word "comprising" does not exclude other elements or steps, and the quantifier "a" does not exclude a plurality. A single element or other unit may fulfill the function of several entities or items described in the claims. Listing certain measures in dissimilar dependent claims does not imply that combinations of these measures cannot be used in advantageous implementations.

Claims

1. A first control plane entity (110) for managing data traffic transmission of multiple service flows of a user equipment (UE) (130), wherein, The plurality of service flows of the UE (130) are associated with a packet data network PDU session pair of the UE (130). The first PDU session (120) in the PDU session pair is connected to the data network through a first access network (151), and the second PDU session (140) in the PDU session pair is connected to the data network through a second access network (152). The first access network (151) and the second access network (152) adopt the same type of radio access technology. The first control plane entity (110) is used for: Obtain first indication information, wherein the first indication information indicates whether one or more of the UE (130), the plurality of service flows, the first PDU session (120), the second PDU session (140), the PDU session pair and the application support flow migration capability; The stream migration capability refers to the ability to switch data traffic transmission between redundant transmission and parallel transmission. For redundant transmission, data packets associated with one or more first service flows among the plurality of service flows are repeated in one or more second service flows among the plurality of flows, wherein the one or more first service flows are associated with the first PDU session (120), and the one or more second service flows are associated with the second PDU session (140). For parallel transmission, the data packets associated with the one or more first service flows are: transmitted simultaneously in the first service flow and the second service flow, wherein data packets exceeding the capacity of the one or more first service flows are transmitted in the one or more second service flows; or transmitted only in the one or more second service flows, wherein all data packets associated with the one or more first service flows are transmitted in the one or more second service flows. The UE (130), the plurality of service flows, the first PDU session (120), the second PDU session (140), the PDU session pair, and one or more support flow migration capabilities in the application are determined based on the first indication information. Determine the flow migration information of the first PDU session (120) and the second PDU session (140), wherein the flow migration information (111) includes mapping information between the one or more first service flows in the first PDU session (120) and the one or more second service flows in the second PDU session (140); The flow migration information (111) is provided to one or more of the UE (130) and user plane entities.

2. The first control surface entity (110) according to claim 1 is further used for: Provide first handover information to one or more of the user plane entity and the UE (130), wherein, The first switching information includes information for parallel transmission between the one or more first service flows and the one or more second service flows.

3. The first control surface entity (110) according to claim 1 or 2 is further used for: Provide second handover information to one or more of the user plane entity and the UE (130), wherein, The second switching information includes information for redundant transmission between the one or more first service flows and the one or more second service flows.

4. The first control surface entity (110) according to claims 1 to 3, wherein, The first indication information includes one or more of the following: -Stream migration subscription indication; - Indicators for application functionality during migration; - Stream migration strategy indication.

5. The first control surface entity (110) according to claim 4, wherein, The stream migration subscription indication is obtained from other entities that store subscription information and the stream migration subscription indication, and the stream migration subscription indication is used to indicate whether the stream migration capability is allowed or restricted based on one or more of the following information: -UE identifier; -Application information; -Data network information; -Network slice information; -PLMN identifier; -PDU session identifier; -PDU session pair identifier; - Stream description; - Stream identifier.

6. The first control surface entity (110) according to claim 4, wherein, The stream migration application function indication is obtained from the application function entity, and the stream migration application function indication is used to indicate whether the stream migration capability is allowed or restricted based on one or more of the following information: -UE identifier; -Application information; -Data network information; -PDU session identifier; -PDU session pair identifier; - Transaction reference ID; - Application session context identifier; -Application session identifier; - Stream description; - Network slice information.

7. The first control surface entity (110) according to claim 4, wherein, The flow migration policy indication is obtained from the second control plane entity or configured in the first control plane entity (110), and the flow migration policy indication is used to indicate whether the flow migration capability is allowed or restricted based on one or more of the following information: -UE identifier; -Application information; -Data network information; - Network slice information.

8. The first control plane entity (110) according to any one of claims 4 to 7 is further configured to: acquire flow migration condition information, wherein, The flow migration condition information includes monitoring information used to activate or deactivate the flow migration capability.

9. The first control surface entity (110) according to claim 8, wherein, The flow migration condition information is obtained through one or more of the following methods: - Obtained together with the aforementioned stream migration subscription instruction; - Acquired together with the aforementioned streaming migration application function indication; - Acquired together with the aforementioned flow migration strategy indication; - Configured in the first control plane entity (110); -Included in the flow migration information (111).

10. The first control surface entity (110) according to claim 8 or 9, wherein, The migration condition information includes one or more of the following: - The upper limit of QoS-related measurements for activating the flow migration capability; - Lower limit of QoS-related measurements to activate the flow migration capability; - Maintain the maximum time interval for activating the aforementioned flow migration capability; - Maintain the minimum time interval for activating the aforementioned flow migration capability; - The threshold for deactivating the flow migration capability; - Deactivate the degradation threshold for the flow migration capability.

11. The first control plane entity (110) according to any one of claims 1 to 10 is further configured to: acquire a flow migration trigger indication, wherein, The flow migration trigger indication is a flag that indicates to the first control plane entity (110) that the flow migration capability is required to establish the first PDU session (120) and / or the second PDU session (140).

12. The first control plane entity (110) according to claim 11 is further configured to: obtain the first indication information according to the flow migration trigger indication.

13. The first control surface entity (110) according to any one of claims 1 to 12, wherein, The mapping information includes information related to the following operation: mapping one or more first service flows associated with the first PDU session (120) to one or more second flows associated with the second PDU session (140), wherein the first PDU session (120) and the second PDU session (140) are associated with the same PDU session pair ID.

14. The first control surface entity (110) according to claim 13, wherein, The mapping information also includes one or more of the following: - Tunnel mapping information, used to map the core network tunnels and / or radio access network tunnels of the one or more first service flows associated with the first PDU session (120) to one or more other core network tunnels and / or one or more other radio access network tunnels of the one or more second service flows associated with the second PDU session (140); - Data traffic migration type, wherein the data traffic migration type defines the mapping of data traffic migrated from the one or more first service flows to the one or more second service flows.

15. The first control surface entity (110) according to claim 14, wherein, The data traffic migration type indicates one of the following types: -Reroute all data transmissions from the one or more first service flows to the one or more second service flows. -Reroute data transmissions exceeding a specific bit rate from the one or more first service flows to the one or more second service flows. - Reroute a certain percentage of data transmission from the one or more first service flows to the one or more second service flows.

16. The first control surface entity (110) according to any one of claims 1 to 13, wherein, The first control plane entity (110) is used to send a notification to the application function entity, wherein the notification indicates one or more of the following: - Allows the aforementioned stream migration capability; - Limit the aforementioned flow migration capability; -Activate the stream migration capability; - Deactivate the aforementioned flow migration capability.

17. The first control surface entity (110) according to any one of claims 1 to 16, wherein, The first control plane entity (110) is also used to acquire one or more of the following: - The user plane function and / or the network first handover indication of the UE (130), wherein the network first handover indication is used to indicate the need for or request to activate the flow migration capability; - Application first switching indication of the application functional entity, wherein the application first switching indication is used to indicate the need for or request to activate the streaming migration capability.

18. The first control surface entity (110) according to any one of claims 1 to 17, wherein, The first control plane entity (110) is further configured to determine the first handover information based on the network first handover indication, the application first handover indication, or an internal configuration related to the first handover information, or a combination thereof.

19. The first control surface entity (110) according to claim 17 or 18, wherein, The first network handover indication includes one or more of the following: -UE identifier; -PDU session pair identifier; - First PDU session (120) identifier and / or second PDU session (140) identifier; - First network candidate handover information and / or second network candidate handover information, wherein the first network candidate handover information and / or the second network candidate handover information are determined by the UP entity and / or the UE (130), the first network candidate handover information includes the first handover information, and the second network candidate handover information includes the second handover information.

20. The first control surface entity (110) according to any one of claims 17 to 19, wherein, The first application switching instruction includes one or more of the following: - Transaction reference ID; - A flag indicating a request to activate the streaming migration capability to switch from redundant transmission to parallel transmission in the paired PDU session; -Application information; -Data network information; -UE information; - Stream description; - The identifier of the application session context; -PDU session pair ID; -PDU Session ID; -Network slice information; - Application candidate first switching information and / or application candidate second switching information, wherein the application candidate first switching information and / or the application candidate second switching information are determined by the application function entity, the application candidate first switching information includes the first switching information, and the application candidate second switching information includes the second switching information.

21. The first control surface entity (110) according to any one of claims 2 to 20, wherein, The first switching information includes one or more of the following: - Instructions to switch to parallel transmission; - Information about the first PDU session (120) and / or the second PDU session (140); -Information regarding the first stream and / or the second stream; -Information about the PDU session pair; - Data traffic migration type; - Modified flow migration information, wherein the modified flow migration information represents changes to the previously defined flow migration information for the PDU session in order to switch to parallel transmission.

22. The first control surface entity (110) according to any one of claims 2 to 21, wherein, The first switching information also includes one or more of the following: -Accept confirmation of the first handover information of the network candidate received from the user plane entity and / or UE (130); -Accept confirmation of the first application candidate switching information received from the application function; - Modify the indication of the first handover information of the network candidate received from the user plane entity and / or the UE (130); - Modify the indication of the first switching information of the application candidate received from the application function entity; - An indication to reject the network candidate first handover information received from the user plane entity and / or the UE (130), wherein the indication to reject the network candidate first handover information indicates that the received network candidate first handover information cannot be applied; - An indication to reject the first application candidate switching information received from the application function entity, wherein the indication to reject the first application candidate switching information indicates that the received first application candidate switching information cannot be applied.

23. The first control surface entity (110) according to any one of claims 2 to 22, wherein, The first switching information also includes a time indication for activating the streaming migration capability.

24. The first control surface entity (110) according to any one of claims 20 to 23, wherein, The first control plane entity (110) is also configured to send a notification to the application function entity, wherein the notification indicates one of the following: - Accept confirmation of the first switching information of the application candidate received from the application function entity; - Modify the indication of the first switching information of the application candidate received from the application function entity; - An indication to reject the application candidate first switching information received from the application function entity.

25. The first control surface entity (110) according to any one of claims 1 to 23, wherein, The first control plane entity (110) is also used to acquire one or more of the following: - The user plane function and / or the network second handover indication of the UE (130), wherein the network second handover indication is used to indicate the need or request to deactivate the flow migration capability; - Application second switching indication for application function, wherein the application second switching indication is used to indicate the need or request to activate the streaming migration capability.

26. The first control surface entity (110) according to any one of claims 1 to 25, wherein, The first control plane entity (110) is also configured to determine the second handover information based on the network second handover indication, the application second handover indication, or an internal configuration related to the second handover information, or a combination thereof.

27. The first control surface entity (110) according to any one of claims 3 to 26, wherein, The second switching information includes one or more of the following: - Instructions to switch to redundant transmission; - Information about the first PDU session (120) and / or the second PDU session (140); -Information regarding the first stream and / or the second stream; -Information about the PDU session pair; - Original stream migration information, wherein the original stream migration information represents the stream migration information previously defined for the PDU session pair before switching to parallel transmission; - Instructions for using the original flow migration, wherein the instructions for using the original flow migration include a flag indicating previously defined flow migration information to be restored for the PDU session pair before switching to parallel transmission.

28. The first control plane entity (110) according to any one of claims 25 to 27 is further configured to: provide the flow migration condition information to one or more of the user plane entity and the UE (130), such that one or more of the user plane entity and the UE (130) trigger the first network handover indication and / or the second network handover indication according to the received flow migration condition information.

29. The first control surface entity (110) according to any one of claims 2 to 27, wherein, The first control plane entity (110) is also configured to monitor the flow migration condition information to determine whether to provide the first handover information and / or the second handover information to one or more of the user plane entity and the UE (130).

30. A user plane flow migration entity associated with data traffic transmission of multiple service flows of a user equipment (UE) (130), wherein, The multiple service flows of the UE (130) are associated with a packet data network PDU session pair of the UE (130). The first PDU session (120) in the PDU session pair is connected to the data network through a first access network (151), and the second PDU session (140) in the PDU session pair is connected to the data network through a second access network (152). The first access network (151) and the second access network (152) adopt the same type of radio access technology. The user plane flow migration entity is used for: Receive flow migration information (111) of the first PDU session (120) and the second PDU session (140) from the first control plane entity (110), wherein the flow migration information (111) includes mapping information between one or more first service flows in the first PDU session (120) and one or more second service flows in the second PDU session (140); Configure the first PDU session (120) and the second PDU session (140) to support flow migration capabilities according to the flow migration information (111). The stream migration capability refers to the ability to switch data traffic transmission between redundant transmission and parallel transmission. For redundant transmission, data packets associated with one or more first service flows among the plurality of service flows are repeated in one or more second service flows among the plurality of flows, wherein the one or more first service flows are associated with the first PDU session (120), and the one or more second service flows are associated with the second PDU session (140). For parallel transmission, the data packets associated with the one or more first service flows are transmitted simultaneously in the first service flow and the second service flow, wherein data packets exceeding the capacity of the one or more first service flows are transmitted in the one or more second service flows; or transmitted only in the one or more second service flows, wherein all data packets associated with the one or more first service flows are transmitted in the one or more second service flows.

31. The user plane flow migration entity according to claim 30 is further used for: First switching information is obtained from the first control plane entity (110), wherein, The first switching information includes information for parallel transmission between the one or more first service flows associated with the first PDU session (120) and the one or more second service flows associated with the second PDU session (140).

32. The user plane flow migration entity according to claim 30 or 31 is further used for: Second switching information is obtained from the first control plane entity (110), wherein, The second switching information includes information for redundant transmission between the one or more first service flows associated with the first PDU session (120) and the one or more second service flows associated with the second PDU session (140).

33. The user plane flow migration entity according to any one of claims 30 to 32, wherein, The user plane flow migration entity is at least a part of the UE (130) or a user plane entity.

34. The user plane flow migration entity according to claim 33, wherein, The user plane flow migration entity is at least a part of the UE (130) and is further configured to: provide a flow migration trigger indication to the first control plane entity (110), wherein the flow migration trigger indication is a flag indicating to the first control plane entity (110) that the flow migration capability is required to establish the first PDU session (120) and / or the second PDU session (140).

35. The user plane flow migration entity according to any one of claims 30 to 34, further configured to: provide one of the following to the first control plane entity (110): - First network handover indication, where The first network handover indication is used to indicate the need for or request to activate the flow migration capability; - A second network handover indication, wherein the first network handover indication is used to indicate the need for or request to activate the flow migration capability.

36. The user plane flow migration entity according to claim 35 is further used for: Receive flow migration condition information from the first control plane entity (110), wherein, The flow migration condition information includes monitoring information used to activate or deactivate the flow migration capability; Based on the received flow migration condition information, send the first network handover instruction and / or the second network handover instruction.

37. An application function entity associated with data traffic transmission of multiple service flows of a user equipment (UE) (130), wherein, The multiple service flows of the UE (130) are associated with a packet data network PDU session pair of the UE (130). The first PDU session (120) in the PDU session pair is connected to the data network through a first access network (151), and the second PDU session (140) in the PDU session pair is connected to the data network through a second access network (152). The first access network (151) and the second access network (152) adopt the same type of radio access technology. The application function entity is used for: Obtain a notification from the first control plane entity (110) including at least one of the following indications: allow flow migration capability, restrict the flow migration capability, activate the flow migration capability, deactivate the flow migration capability, wherein the flow migration capability indicates the ability to switch data traffic transmission between redundant transmission and parallel transmission; For redundant transmission, data packets associated with one or more first service flows among the plurality of service flows are repeated in one or more second service flows among the plurality of flows, wherein the one or more first service flows are associated with the first PDU session (120), and the one or more second service flows are associated with the second PDU session (140). For parallel transmission, the data packets associated with the one or more first service flows are transmitted simultaneously in the first service flows and the second service flows, wherein data packets exceeding the capacity of the one or more first service flows are transmitted in the one or more second service flows; or transmitted only in the one or more second service flows, wherein all data packets associated with the one or more first service flows are transmitted in the one or more second service flows.

38. The application function entity according to claim 37 is further configured to: provide a flow migration application function indication to the first control plane entity (110), wherein, The stream migration application function indicator is used to indicate whether to allow or restrict the stream migration capability based on one or more of the following information: -UE identifier; -Application information; -Data network information; -PDU session identifier; -PDU session pair identifier; - Transaction reference ID; - Application session context identifier; -Application session identifier; - Stream description; - Network slice information.

39. The application functional entity according to claim 37 or 38, further configured to: provide one of the following to the first control plane entity (110): - Apply the first switching instruction, where The first application switching indication is used to indicate whether the streaming migration capability needs to be activated or is requested. - Apply a second switching instruction, wherein the application of the second switching instruction is used to indicate the need or request to activate the streaming migration capability.

40. The application functional entity according to claim 39, wherein, The first application switching instruction includes one or more of the following: - Transaction reference ID; - A flag indicating a request to activate the streaming migration capability to switch from redundant transmission to parallel transmission in the paired PDU session; -Application information; -Data network information; -UE information; - Stream description; -The application session context identifier; -PDU session pair ID; -PDU Session ID; -Network slice information; - Application candidate first switching information and / or application candidate second switching information, wherein the application candidate first switching information and / or the application candidate second switching information are determined by the application function entity, the application candidate first switching information includes the first switching information, and the application candidate second switching information includes the second switching information.

41. The application function entity according to claim 40, further configured to: obtain a notification from the first control plane entity (110), wherein, The notification indicates one of the following: - Accept confirmation of the first switching information of the application candidate received from the application function entity; - Modify the indication of the first switching information of the application candidate received from the application function entity; - An indication to reject the application candidate first switching information received from the application function entity.

42. The application functional entity according to any one of claims 37 to 41, further configured to: provide flow migration condition information to the first control plane entity (110), wherein, The flow migration condition information includes monitoring information used to activate or deactivate the flow migration capability.

43. The application functional entity according to claim 42, wherein, The migration condition information, together with the migration application function indication, is provided to the first control plane entity (110).

44. A method (1200) for managing data traffic transmission of multiple service flows of a user equipment (UE), wherein, The multiple service flows of the UE are associated with a packet data network PDU session pair of the UE. A first PDU session in the PDU session pair is connected to the data network via a first access network, and a second PDU session in the PDU session pair is connected to the data network via a second access network. The first access network and the second access network employ the same type of radio access technology. The method includes: The first control plane entity obtains (1201) first indication information, wherein the first indication information indicates whether the UE, the plurality of service flows, the first PDU session, the second PDU session, the PDU session pair, and one or more of the applications support flow migration capability. The stream migration capability refers to the ability to switch data traffic transmission between redundant transmission and parallel transmission. For redundant transmission, data packets associated with one or more first service flows among the plurality of service flows are repeated in one or more second service flows among the plurality of flows, wherein the one or more first service flows are associated with the first PDU session, and the one or more second service flows are associated with the second PDU session. For parallel transmission, the data packets associated with the one or more first service flows are: transmitted simultaneously in the first service flow and the second service flow, wherein data packets exceeding the capacity of the one or more first service flows are transmitted in the one or more second service flows; or transmitted only in the one or more second service flows, wherein all data packets associated with the one or more first service flows are transmitted in the one or more second service flows. The first control plane entity determines (1202) the UE, the plurality of service flows, the first PDU session, the second PDU session, the PDU session pair, and one or more support flow migration capabilities in the application based on the first indication information; The first control plane entity determines (1203) the flow migration information of the first PDU session and the second PDU session, wherein the flow migration information includes mapping information between the one or more first service flows in the first PDU session and the one or more second service flows in the second PDU session; The first control plane entity provides the flow migration information (1204) to one or more of the UE and the user plane entity.

45. A method (1300) for transmitting data traffic for multiple service flows of a user equipment (UE), wherein, The multiple service flows of the UE are associated with a packet data network PDU session pair of the UE. A first PDU session in the PDU session pair is connected to the data network via a first access network, and a second PDU session in the PDU session pair is connected to the data network via a second access network. The first access network and the second access network employ the same type of radio access technology. The method includes: The user plane flow migration entity receives (1301) flow migration information of the first PDU session and the second PDU session from the first control plane entity, wherein the flow migration information includes mapping information between one or more first service flows in the first PDU session and one or more second service flows in the second PDU session; The user plane flow migration entity configures (1302) the first PDU session and the second PDU session to support flow migration capabilities based on the flow migration information. The stream migration capability refers to the ability to switch data traffic transmission between redundant transmission and parallel transmission. For redundant transmission, data packets associated with one or more first service flows among the plurality of service flows are repeated in one or more second service flows among the plurality of flows, wherein the one or more first service flows are associated with the first PDU session, and the one or more second service flows are associated with the second PDU session. For parallel transmission, the data packets associated with the one or more first service flows are transmitted simultaneously in the first service flows and the second service flows, wherein data packets exceeding the capacity of the one or more first service flows are transmitted in the one or more second service flows; or transmitted only in the one or more second service flows, wherein all data packets associated with the one or more first service flows are transmitted in the one or more second service flows.

46. ​​A method (1400) for transmitting data traffic for multiple service flows of a user equipment (UE), wherein, The multiple service flows of the UE are associated with a packet data network PDU session pair of the UE. A first PDU session in the PDU session pair is connected to the data network via a first access network, and a second PDU session in the PDU session pair is connected to the data network via a second access network. The first access network and the second access network employ the same type of radio access technology. The method includes: The application functional entity obtains (1401) a notification from the first control plane entity including at least one of the following indications: enabling flow migration capability, restricting the flow migration capability, activating the flow migration capability, and deactivating the flow migration capability, wherein the flow migration capability indicates the ability to switch data traffic transmission between redundant transmission and parallel transmission. For redundant transmission, data packets associated with one or more first service flows among the plurality of service flows are repeated in one or more second service flows among the plurality of flows, wherein the one or more first service flows are associated with the first PDU session, and the one or more second service flows are associated with the second PDU session. For parallel transmission, the data packets associated with the one or more first service flows are transmitted simultaneously in the first service flows and the second service flows, wherein data packets exceeding the capacity of the one or more first service flows are transmitted in the one or more second service flows; or transmitted only in the one or more second service flows, wherein all data packets associated with the one or more first service flows are transmitted in the one or more second service flows.

47. A system comprising one or more of a first control plane entity according to any one of claims 1 to 29, a user plane flow migration entity according to any one of claims 30 to 36, and an application function entity according to any one of claims 37 to 43.

48. A computer program comprising instructions that, when executed by a computer, cause the computer to perform the method according to any one of claims 44 to 46.

Images