WO2023037341A1

WO2023037341A1 - Exposure of redundant transmission in a cellular communications system

Info

Publication number: WO2023037341A1
Application number: PCT/IB2022/058591
Authority: WO
Inventors: György Miklós; Balázs VARGA; János FARKAS
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2021-09-10
Filing date: 2022-09-12
Publication date: 2023-03-16

Abstract

Systems and methods are disclosed related to exposure of redundant transmission in a cellular communications system. In one embodiment, a method performed by a network node for customization of redundancy for network traffic flows comprises obtaining, from a network entity, data indicative of a requested degree of redundancy for a network traffic flow and, based at least in part on the requested degree of redundancy, performing adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for the network traffic flow. In this manner, by exposing redundant transmission to the network entity, the network entity is enabled to request customization of redundancy mechanisms to provided the requested degree of redundancy for a network traffic flow.

Description

EXPOSURE OF REDUNDANT TRANSMISSION IN A CELLULAR COMMUNICA TIONS SYSTEM

Related Applications

[0001] This application claims the benefit of provisional patent application serial number 63/242,684, filed September 10, 2021, the disclosure of which is hereby incorporated herein by reference in its entirety.

Technical Field

[0002] The present disclosure relates to a cellular communications system (e.g., a Third Generation Partnership Project (3GPP) system) and, more specifically, to redundant transmission in such a system.

Background

[0003] The Third-Generation Partnership Program (3GPP) network architecture provides a number of mechanisms for redundant transmission of certain traffic flows within the 3GPP system. By redundant traffic handling, two (or more) copies of the data packets are sent and delivered through separate paths, where the paths are disjointed to the maximum extent possible at the given deployment. At the receiving side, the duplicate data packets are eliminated, and only a single copy is delivered further. The redundant traffic handling enables the effect of any error on one transmission path to be hidden without any additional delay. Hence, the use of redundancy mechanisms can significantly increase the availability of the communication system. In certain cases, the 3GPP network may provide the full redundancy solution, while in other cases the 3GPP network may provide some of the mechanisms for redundancy which are used in combination with other mechanisms defined by other industry(s) or standardization(s) so that in combination redundancy can be assured.

[0004] One method is to use Packet Data Convergence Protocol (PDCP) duplication (see e.g., 3GPP Technical Specification (TS) 38.300 (e.g., V16.6.0), section 16.1.3) within the Radio Access Network (RAN) to send the same packet over multiple data bearers. Using PDCP duplication, duplicate copies of the same packet can be sent via different RAN nodes using Dual Connectivity (DC), so that the receiving PDCP entity eliminates the duplicate copies. The use of PDCP duplication can be configured into the RAN and can be used based on the Fifth Generation (5G) Quality of Service (QoS) Identifier (5QI) values. The QoS Flow Identifier (QFI) carried in the packet header determines the 5QI of the given packet flow.

[0005] Support for redundant transmission on N3/N9 interfaces is defined in 3GPP TS 23.501 (see, e.g., V16.9.0) section 5.33.2.2. The mechanism allows the Session Management Function (SMF) to configure two redundant General Packet Radio Service (GPRS) Tunnelling Protocol (GTP) tunnels between the RAN node and the PDU Session Anchor (PSA) User Plane Function (UPF). The packets are duplicated and sent with the same GTP User Plane (GTP-U) sequence number, which is used by the receiving side to eliminate the duplicated transmissions. The use of the redundant transmission can be applied on a per flow basis based on the SMF's configuration.

[0006] Redundant data transmission on the N3/N9 can also be performed using redundancy mechanisms in the transport layer, as described in 3GPP TS 23.501 section 5.33.2.3. In this case, the redundancy mechanism is used in the transport layer to duplicate packets and eliminate duplicate copies in the receiving side, so that no new 3GPP mechanism is used for the duplication.

[0007] Annex F in 3GPP TS 23.501 describes the case of multiple User Equipments (UEs) per device, each connecting to the 3GPP network, such that the path over the 3GPP network is redundant. This is applicable for devices which are equipped with multiple UEs, and where the network supports this deployment

Summary

[0008] Systems and methods are disclosed related to exposure of redundant transmission in a cellular communications system. In one embodiment, a method performed by a network node for customization of redundancy for network traffic flows comprises obtaining, from a network entity, data indicative of a requested degree of redundancy for a network traffic flow and, based at least in part on the requested degree of redundancy, performing adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for the network traffic flow. In this manner, by exposing redundant transmission to the network entity, the network entity is enabled to request customization of redundancy mechanisms to provided the requested degree of redundancy for a network traffic flow.

[0009] In one embodiment, the network entity is an Application Function (AF). [0010] In one embodiment, prior to obtaining the data indicative of the requested degree of redundancy, the method comprises providing, to the network entity, data indicative of a current degree of redundancy for the network traffic flow. In one embodiment, prior to providing the data of the current degree of redundancy for the network traffic flow, the method comprises determining the current degree of redundancy for the network traffic flow based at least in part on a number of network redundancy mechanisms of the plurality of network redundancy mechanisms that are activated for the network traffic flow. In one embodiment, the data indicative of the current degree of redundancy for the network traffic flow is descriptive of an identity of each of the number of network redundancy mechanisms that are activated for the network traffic flow. In one embodiment, the adjustments to the one or more network redundancy mechanisms of the plurality of network redundancy mechanisms for the network traffic flow are based at least in part on the number of network redundancy mechanisms of the plurality of network redundancy mechanisms that are activated for the network traffic flow.

[0011] In one embodiment, prior to performing adjustments to one or more network redundancy mechanisms, the method comprises determining the adjustments to the one or more network redundancy mechanisms based at least in part on the requested degree of redundancy.

[0012] In one embodiment, the network node comprises a Network Exposure Function (NEF), wherein the network node, or NEF, obtains the data indicative of the requested degree of redundancy for the network traffic flow via a direct transmission from the network entity.

[0013] In one embodiment, the network node comprises a Policy Control Function (PCF), a Session Management Function (SMF), a User Plane Function (UPF), or at least portion of a Radio Access Network (RAN) node. In one embodiment, obtaining the data indicative of the requested degree of redundancy for the network traffic flow from the network entity comprises obtaining the data indicative of the requested degree of redundancy for the network traffic flow from the network entity indirectly via an additional network entity.

[0014] In one embodiment, the data indicative of the requested degree of redundancy for the network traffic flow is further indicative of the adjustments to the one or more network redundancy mechanisms of the plurality of network redundancy mechanisms for the network traffic flow.

[0015] In one embodiment, performing the adjustments to the one or more network redundancy mechanisms comprises applying Packet Data Convergence Protocol (PDCP) duplication for the network traffic flow. In one embodiment, performing the one or more adjustments further comprises applying a dual connectivity mechanism to the network traffic flow.

[0016] In one embodiment, performing the one or more adjustments comprises enabling, via a Session Management Function (SMF), a N3/N9 redundancy mechanism for the network traffic flow.

[0017] In one embodiment, performing the one or more adjustments comprises enabling, via a Software-Defined Networking (SDN) controller or via a communication endpoint, one or more transport network redundancy mechanisms for the network traffic flow.

[0018] In one embodiment, performing the one or more adjustments comprises establishing one or more redundant Protocol Data Unit (PDU) sessions for one or more PDU sessions.

[0019] In one embodiment, performing the one or more adjustments comprises determining that a Wireless Communication Device (WCD) associated with the network entity includes two sub-WCDs and establishing one sub-WCD of the two sub-WCDs as a duplicate carrier to enable a duplicate WCD-based redundancy mechanism for the network traffic flow.

[0020] In one embodiment, performing the one or more adjustments comprises enabling one or more function-specific redundancy mechanisms to ensure high availability for at least a portion of the network traffic flow, wherein the one or more function-specific redundancy mechanisms comprise: (a) redundant handling within one or more network functions, (b) redundant execution of at least a portion of the one or more network functions, (c) application of redundant coding schemes within the one or more network functions, or (d) any two or more of (a) - (c).

[0021] Corresponding embodiments of a network node are also disclosed. In one embodiment, a network node for customization of redundancy for network traffic flows is adapted to obtain, from a network entity, data indicative of a requested degree of redundancy for a network traffic flow and, based at least in part on the requested degree of redundancy, perform adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for the network traffic flow.

[0022] In one embodiment, a network node for customization of redundancy for network traffic flows comprises processing circuitry configured to cause the network node to obtain, from a network entity, data indicative of a requested degree of redundancy for a network traffic flow and, based at least in part on the requested degree of redundancy, perform adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for the network traffic flow.

[0023] In another embodiment, a network node for exposure of redundancy for network traffic flow is adapted to receive, from an AF, a request for data indicative of a current degree of redundancy for a network traffic flow and provide, to the AF, the data indicative of the current degree of redundancy for the network traffic flow in response to the request.

[0024] In one embodiment, prior to providing the data of the current degree of redundancy for the network traffic flow, the network node is adapted to determine the current degree of redundancy for the network traffic flow based at least in part on a number of network redundancy mechanisms of a plurality of network redundancy mechanisms that are activated for the network traffic flow. In one embodiment, the network node is further adapted to obtain, from the AF, data indicative of a requested degree of redundancy for the network traffic flow. In one embodiment, the network node is further adapted to, based at least in part on the requested degree of redundancy, perform adjustments to one or more network redundancy mechanisms of the plurality of network redundancy mechanisms for the network traffic flow.

Brief Description of the Drawings

[0025] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0026] Figure 1 illustrates one example of a cellular communications system in which embodiments of the present disclosure may be implemented; [0027] Figure 2 illustrates a wireless communication system represented as a Fifth Generation (5G) network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point/interface;

[0028] Figure 3 illustrates a 5G network architecture using service-based interfaces between the NFs in the Control Plane (CP), instead of the point-to-point reference points/interfaces used in the 5G network architecture of Figure 2;

[0029] Figure 4A is a flow diagram for customization of redundancy for network traffic flows according to some embodiments of the present disclosure;

[0030] Figure 4B is a flow chart illustrating one example embodiment of step 408 of Figure 4A;

[0031] Figure 5A illustrates a block diagram for customization of redundancy for network traffic flows in accordance with one embodiment of the present disclosure;

[0032] Figure 5B is a block diagram that illustrates one example adjustment to the network redundancy mechanism(s) by applying Packet Data Convergence Protocol (PDCP) duplication according to some embodiments of the present disclosure;

[0033] Figure 5C is a block diagram that illustrates one example adjustment to the network redundancy mechanism(s) by enabling a N3/N9 redundancy mechanism for the network traffic flow via a Session Management Function (SMF) according to some embodiments of the present disclosure;

[0034] Figure 5D is a block diagram that illustrates an example of dual connectivity based network redundancy mechanism(s) according to some embodiments of the present disclosure;

[0035] Figure 5E is a block diagram that illustrates an example of duplicate subwireless communication device based network redundancy mechanism(s) according to some embodiments of the present disclosure;

[0036] Figures 6, 7, and 8 are schematic block diagrams of example embodiments of a network node; and

[0037] Figures 9 and 10 are schematic block diagrams of example embodiments of a wireless communication device. Detailed Description

[0038] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0039] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0040] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

[0041] Radio Node: As used herein, a "radio node" is either a radio access node or a wireless communication device.

[0042] Radio Access Node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.

[0043] Core Network Node: As used herein, a "core network node" is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.

[0044] Communication Device: As used herein, a "communication device" is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer-comprised, or vehiclemounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.

[0045] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (loT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection.

[0046] Network Node: As used herein, a "network node" is any node that is either part of the RAN or the core network of a cellular communications network/system.

[0047] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0048] Note that, in the description herein, reference may be made to the term "cell"; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0049] There currently exist certain challenge(s). Specifically, the 3GPP mechanism defined for redundancy is set up using configuration within the 3GPP system. However, in certain deployments, there may be a need for the 3GPP system to inform external entities as to whether or not redundancy mechanisms are in use for a given traffic flow. Additionally, or alternatively, in some circumstances, there may be a need for external entities to influence, on a per traffic flow basis, whether or not the redundancy mechanisms are in use. Such an external entity may, for example, be a configuration server or controller, or an Application Function (AF).

[0050] However, an external entity may not be aware of the specific 3GPP solutions for redundancy. It is desirable to hide the details of the 3GPP mechanisms from third parties, since such third-party entities and application providers may not understand the specifics of the 3GPP mechanisms (e.g., their advantages and disadvantages, their cost implications, etc.). Hence, it is desirable to have a solution for the exposure of the redundancy mechanism in such a way that the actual mechanisms to be used are determined in the 3GPP network, and the third-party entities do not need any awareness of the redundancy mechanism in question. [0051] Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. Specifically, a solution is proposed that incorporates an interface between the 3GPP network and an external entity (e.g., an AF, a Software- Defined Networking (SDN) controller, a network management server, etc.) to get information about the redundancy level applied to a given traffic flow, and to also enable the external entity to request redundant handling for a traffic flow. The external entity can receive and provide information about the redundancy level needed for a given traffic flow in an abstract way without having knowledge about which specific 3GPP mechanisms are to be used (e.g., a redundancy-level parameter may be received or provided by the application function to describe or otherwise indicate the degree of redundancy for traffic flows.). A 3GPP network function maps between the degree of redundancy and the specific combination of redundancy mechanisms in use. [0052] More particularly, an interface (e.g., an external Application Program Interface (API)) is proposed which provides information about the redundancy level (and possibly specific redundancy parameters) of the traffic flows, and allows external requests to be made to influence the 3GPP network's redundancy settings, including the degree of redundancy and possibly specific redundancy parameters. A 3GPP network function (e.g., the Network Exposure Function (NEF)) maps between the various degrees of redundancy and the specific combination of redundancy mechanisms in use. [0053] There are, proposed herein, various embodiments which address one or more of the issues disclosed herein. In one embodiment, a method performed by a network node for customization of redundancy for network traffic flows is proposed. The method includes obtaining, from a network entity, data indicative of a requested degree of redundancy for a network traffic flow. The method includes, based at least in part on the requested degree of redundancy, performing adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for the network traffic flow.

[0054] In some embodiments, prior to obtaining the data indicative of the requested degree of redundancy, the method comprises providing, to the network entity, data indicative of a current degree of redundancy for the network traffic flow.

[0055] In some embodiments, prior to providing the data of the current degree of redundancy for the network traffic flow, the method comprises determining the current degree of redundancy for the network traffic flow based at least in part on a number of network redundancy mechanisms of the plurality of network redundancy mechanisms that are activated for the network traffic flow.

[0056] In some embodiments, the data indicative of the current degree of redundancy for the network traffic flow is descriptive of an identity of each of the number of network redundancy mechanisms that are activated for the network traffic flow.

[0057] In some embodiments, the adjustments to the one or more network redundancy mechanisms of the plurality of network redundancy mechanisms for the network traffic flow are based at least in part on the number of network redundancy mechanisms of the plurality of network redundancy mechanisms that are activated for the network traffic flow.

[0058] In some embodiments, prior to performing adjustments to one or more network redundancy mechanisms, the method comprises determining the adjustments to the one or more network redundancy mechanisms based at least in part on the requested degree of redundancy.

[0059] In some embodiments, the current degree of redundancy for the network traffic flow is determined using at least one of a Network Exposure Function (NEF) or a Time Sensitive Communications Time Synchronization Function (TSCTSF).

[0060] In some embodiments, the network entity comprises an Application Function (AF). In some embodiments, the network node comprises a Network Exposure Function (NEF), and the network node obtains the data indicative of the requested degree of redundancy for the network traffic flow via a direct transmission from the network entity.

[0061] In some embodiments, the network node comprises a Policy Control Function (PCF), a Session Management Function (SMF), a User Plane Function (UPF), or a portion of a Radio Access Network (RAN). In some embodiments, the network node obtains the data indicative of the requested degree of redundancy for the network traffic flow from the network entity indirectly via transmission from an additional network entity.

[0062] In some embodiments, the data indicative of the requested degree of redundancy for the network traffic flow is further indicative of the adjustments to the one or more network redundancy mechanisms of the plurality of network redundancy mechanisms for the network traffic flow. [0063] In some embodiments, performing the adjustments to the one or more network redundancy mechanisms comprises applying a Fifth Generation (5G) Quality of Service (QoS) Identifier (5QI) in RAN to the network traffic flow to enable PDCP duplication.

[0064] In some embodiments, performing the one or more adjustments further comprises applying a dual connectivity mechanism to the network traffic flow.

[0065] In some embodiments, performing the one or more adjustments comprises enabling, via a SMF, a N3/N9 redundancy mechanism for the network traffic flow.

[0066] In some embodiments, performing the one or more adjustments comprises enabling, via a Software-Defined Networking (SDN) controller or via a communication endpoint, one or more transport network redundancy mechanisms for the network traffic flow.

[0067] In some embodiments, performing the one or more adjustments comprises establishing one or more redundant Protocol Data Unit (PDU) sessions for one or more PDU sessions.

[0068] In some embodiments, performing the one or more adjustments comprises determining that a Wireless Communication Device (WCD) associated with the network entity includes two sub-WCDs, and establishing one sub-WCD of the two sub-WCDs as a duplicate carrier to enable a duplicate WCD-based redundancy mechanism for the network traffic flow.

[0069] In some embodiments, performing the one or more adjustments comprises enabling one or more function-specific redundancy mechanisms to ensure high availability for at least a portion of the network traffic flow. The one or more functionspecific redundancy mechanisms comprise:

(a) redundant handling within one or more network functions;

(b) redundant execution of at least a portion of the one or more network functions;

(c) application of redundant coding schemes within the one or more network functions; or

(d) two or more of any of (a) - (c).

[0070] In some embodiments, a network node for customization of redundancy for network traffic flows is proposed. The network node is adapted to obtain, from a network entity, data indicative of a requested degree of redundancy for a network traffic flow. The network node is adapted to, based at least in part on the requested degree of redundancy, perform adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for the network traffic flow.

[0071] In some embodiments, a network node for customization of redundancy for network traffic flows is proposed. The network node includes one or more transmitters. The network node includes one or more receivers. The network node includes processing circuitry. The processing circuitry is configured to cause the network node to obtain, from a network entity, data indicative of a requested degree of redundancy for a network traffic flow. The processing circuitry is configured to cause the network node to, based at least in part on the requested degree of redundancy, perform adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for the network traffic flow.

[0072] In some embodiments, a network node for customization of redundancy for network traffic flows is proposed. The network node is adapted to receive, from an AF, a request for data indicative of a current degree of redundancy for a network traffic flow. The network node is adapted to provide, to the AF, the data indicative of the current degree of redundancy for the network traffic flow.

[0073] In some embodiments, prior to providing the data of the current degree of redundancy for the network traffic flow, the network node is adapted to determine the current degree of redundancy for the network traffic flow based at least in part on a number of network redundancy mechanisms of a plurality of network redundancy mechanisms that are activated for the network traffic flow.

[0074] In some embodiments, the network node is further adapted to obtain, from the AF, data indicative of a requested degree of redundancy for the network traffic flow. [0075] In some embodiments, the network node is further adapted to, based at least in part on the requested degree of redundancy, perform adjustments to one or more network redundancy mechanisms of the plurality of network redundancy mechanisms for the network traffic flow.

[0076] Certain embodiments may provide one or more of the following technical advantage(s). As one example technical advantage, information about the redundancy level and the specific redundancy mechanisms used for specific traffic flows allows the applications and management systems to prepare for the level of availability that can be expected from the system and plan accordingly. As another example technical advantage, the possibility for external requests to be made about the degree of redundancy necessary for applications traffic allows the 3GPP system to apply the appropriate degree of redundancy. That way, the system can provide redundancy where it is needed, but it can avoid the unnecessary cost and resource usage of traffic duplication where it is not justified. This can save costs for the network operator and at the same time improve the level of service quality. As another example technical advantage, external information about the degree of redundancy necessary for traffic flows can reduce the special configuration needs for redundancy configuration within the 3GPP system. The reduced configuration effort can lead to operational cost savings. As another example technical advantage, the use of a relative degree of redundancy avoids the need for third party entities to have a detailed knowledge about the specific 3GPP mechanisms in use. As yet another example technical advantage, a 3GPP operator can manage the redundancy mechanisms on its own, without having to expose the individual mechanisms themselves. By exposing the redundancy level, the 3GPP operator has flexibility to map the mechanisms to the various degrees of redundancy. [0077] Figure 1 illustrates one example of a cellular communications system 100 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system 100 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC) or an Evolved Packet System (EPS) including an Evolved Universal Terrestrial RAN (E-UTRAN) and an Evolved Packet Core (EPC). In this example, the RAN includes base stations 102-1 and 102-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC) and in the EPS include eNBs, controlling corresponding (macro) cells 104-1 and 104-2. The base stations 102- 1 and 102-2 are generally referred to herein collectively as base stations 102 and individually as base station 102. Likewise, the (macro) cells 104-1 and 104-2 are generally referred to herein collectively as (macro) cells 104 and individually as (macro) cell 104. The RAN may also include a number of low power nodes 106-1 through 106-4 controlling corresponding small cells 108-1 through 108-4. The low power nodes 106-1 through 106-4 can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not illustrated, one or more of the small cells 108-1 through 108-4 may alternatively be provided by the base stations 102. The low power nodes 106-1 through 106-4 are generally referred to herein collectively as low power nodes 106 and individually as low power node 106. Likewise, the small cells 108-1 through 108-4 are generally referred to herein collectively as small cells 108 and individually as small cell 108. The cellular communications system 100 also includes a core network 110, which in the 5G System (5GS) is referred to as the 5GC. The base stations 102 (and optionally the low power nodes 106) are connected to the core network 110.

[0078] The base stations 102 and the low power nodes 106 provide service to wireless communication devices 112-1 through 112-5 in the corresponding cells 104 and 108. The wireless communication devices 112-1 through 112-5 are generally referred to herein collectively as wireless communication devices 112 and individually as wireless communication device 112. In the following description, the wireless communication devices 112 are oftentimes UEs, but the present disclosure is not limited thereto. [0079] Figure 2 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point/interface. Figure 2 can be viewed as one particular implementation of the system 100 of Figure 1. It should be noted that in some embodiments, a network entity 200 of the present disclosure may be, include, or otherwise implement one or more of the NFs 200A-2001 [0080] Seen from the access side the 5G network architecture shown in Figure 2 comprises a plurality of UEs 112 connected to either a RAN 102 or an Access Network (AN) as well as an AMF 200D. Typically, the R(AN) 102 comprises base stations, e.g. such as eNBs or gNBs or similar. Seen from the core network side, the 5GC NFs shown in Figure 2 include a NSSF 200A, an AUSF 200B, a UDM 200C, the AMF 200, a SMF 200E, a PCF 200F, and an Application Function (AF) 200G.

[0081] Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the UE 112 and AMF 200D. The reference points for connecting between the AN 102 and AMF 200D and between the AN 102 and UPF 200H are defined as N2 and N3, respectively. There is a reference point, Nil, between the AMF 200D and SMF 200E, which implies that the SMF 200E is at least partly controlled by the AMF 200D. N4 is used by the SMF 200E and UPF 200H so that the UPF 200H can be set using the control signal generated by the SMF 200E, and the UPF 200H can report its state to the SMF 200E. N9 is the reference point for the connection between different UPFs 200H, and N14 is the reference point connecting between different AMFs 200, respectively. N15 and N7 are defined since the PCF 200F applies policy to the AMF 200D and SMF 200E, respectively. N12 is required for the AMF 200D to perform authentication of the UE 112. N8 and N10 are defined because the subscription data of the UE 112 is required for the AMF 200D and SMF 200E.

[0082] The 5GC network aims at separating UP and CP. The UP carries user traffic while the CP carries signaling in the network. In Figure 2, the UPF 200H is in the UP and all other NFs, i.e., the AMF 200, SMF 200E, PCF 200F, AF 200G, NSSF 200A, AUSF 200B, and UDM 200C, are in the CP. Separating the UP and CP guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from CP functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency.

[0083] The core 5G network architecture is composed of modularized functions. For example, the AMF 200D and SMF 200E are independent functions in the CP. Separated AMF 200D and SMF 200E allow independent evolution and scaling. Other CP functions like the PCF 200F and AUSF 200B can be separated as shown in Figure 2. Modularized function design enables the 5GC network to support various services flexibly.

[0084] Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the CP, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The UP supports interactions such as forwarding operations between different UPFs.

[0085] Figure 3 illustrates a 5G network architecture using service-based interfaces between the NFs in the CP, instead of the point-to-point reference points/interfaces used in the 5G network architecture of Figure 2. It should be noted that in some embodiments, a network entity 200 of the present disclosure may be, include, or otherwise implement one or more of the NFs 200A-2001 However, the NFs described above with reference to Figure 2 correspond to the NFs shown in Figure 3. The service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface. In Figure 3 the service based interfaces are indicated by the letter "N" followed by the name of the NF, e.g. Namf for the service based interface of the AMF 200D and Nsmf for the service based interface of the SMF 200E, etc. The NEF 2001 and the NRF 200J in Figure 3 are not shown in Figure 2 discussed above. However, it should be clarified that all NFs depicted in Figure 2 can interact with the NEF 2001 and the NRF 200J of Figure 3 as necessary, though not explicitly indicated in Figure 2.

[0086] Some properties of the NFs shown in Figures 2 and 3 may be described in the following manner. The AMF 200D provides UE-based authentication, authorization, mobility management, etc. A UE 112 even using multiple access technologies is basically connected to a single AMF 200D because the AMF 200D is independent of the access technologies. The SMF 200E is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF 200H for data transfer. If a UE 112 has multiple sessions, different SMFs 200E may be allocated to each session to manage them individually and possibly provide different functionalities per session. The AF 200G provides information on the packet flow to the PCF 200F responsible for policy control in order to support QoS. Based on the information, the PCF 200F determines policies about mobility and session management to make the AMF 200D and SMF 200E operate properly. The AUSF 200B supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM 200C stores subscription data of the UE 112. The Data Network (DN), not part of the 5GC network, provides Internet access or operator services and similar.

[0087] An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.

[0088] Figure 4A is a flow diagram for customization of redundancy for network traffic flows according to some embodiments of the present disclosure. Dashed boxes and lines represent steps that are optional according to some embodiments of the present disclosure. In some embodiments, at step 401, a network node 400 receives, from the AF 200G, a request for data indicative of a current degree of redundancy for a network traffic flow. The network node 400 may be, e.g., NEF 2001, PCF 200F, SMF 200E, UPF 200H, RAN node 102, or any other suitable network node for receiving and handling the request. Note that while the AF 200G is the source of the request in this example embodiment, the source of the request may alternatively be another third- party entity such as, e.g., a Time Sensitive Network (TSN) AF (TSNAF) or a Time Sensitive Communication and Time Synchronization Function (TSCTSF).

[0089] At step 402, in some embodiments, the network node 400 determines the current degree of redundancy for the network traffic flow based at least in part on a number of network redundancy mechanisms of a plurality of network redundancy mechanisms that are activated for the network traffic flow. In some embodiments, the data indicative of the current degree of redundancy for the network traffic flow is descriptive of an identity of each of the number of network redundancy mechanisms that are activated for the network traffic flow.

[0090] In some embodiments, the current degree of redundancy for the network traffic flow is determined using at least one of a NEF or a Time Sensitive Communications Time Synchronization Function (TSCTSF).

[0091] At step 404, in some embodiments, the network node 400 provides the data indicative of the current degree of redundancy for the network traffic flow to the AF 200G.

[0092] At step 406, the network node 400 obtains, from the AF 200G, data indicative of a requested degree of redundancy for a network traffic flow. In some embodiments, the network node 400 is, enables, or otherwise includes a NEF (e.g., 2001, etc.), and obtains the data indicative of the requested degree of redundancy for the network traffic flow via a direct transmission from the AF 200G.

[0093] Alternatively, in some embodiments, the network node 400 is, enables, or otherwise includes one or more separate net functions (e.g., a PCF, a SMF, a UPF, a portion of a RAN, etc.), and the network node 400 obtains the data indicative of the requested degree of redundancy for the network traffic flow from the network AF 200G indirectly via transmission from an additional network entity.

[0094] In some embodiments, the data indicative of the requested degree of redundancy for the network traffic flow is further indicative of adjustments to the one or more network redundancy mechanisms of the plurality of network redundancy mechanisms for the network traffic flow.

[0095] At step 407, in some embodiments, the network node 400 determines adjustments to the one or more network redundancy mechanisms based at least in part on the requested degree of redundancy. [0096] At step 408, based at least in part on the requested degree of redundancy, the network node 400 performs adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for the network traffic flow.

[0097] In some embodiments, the adjustments to the one or more network redundancy mechanisms of the plurality of network redundancy mechanisms for the network traffic flow are based at least in part on the number of network redundancy mechanisms of the plurality of network redundancy mechanisms that are activated for the network traffic flow.

[0098] It should be noted that the data flow of Figure 4A may be implemented by various network function(s). One example implementation of the data flow of Figure 4A is illustrated in Figure 5A.

[0099] Figure 5A illustrates a block diagram for customization of redundancy for network traffic flows. Turning to Figure 5A, a NEF 504 (e.g., the network node 400, a second network entity, etc.) may collect information 501 about the redundancy status of the traffic flows. The information 501 may be provided by the concerned network functions, such as a SMF 508 or a PCF 506. The information 501 may be provided to the NEF 504 via other entities, such as from the SMF 508 via the PCF 506, or directly. The NEF 504 may provide this information 501 to the AFs (e.g., AF 502, etc.) when they request or subscribe to such information. The information transfer may be triggered by a request from the AF 502, or alternatively a change in the redundancy status (i.e., when redundant handling is established or when it ceases). The NEF 504 may provide a redundancy level parameter (e.g., descriptive of a degree of redundancy) to the AF 502 based on a mapping of the information that it has collected. The degree of redundancy of a certain traffic flow may be an abstract parameter that indicates the level of redundancy protection that he traffic flow receives in the network, without explicitly defining the actual mechanism(s) used for achieving the degree of redundancy.

[0100] In some embodiments, the AF 502 may provide a request 501 to set up (or release) redundancy handling, as well as parameters determining the way of redundancy handling. The AF 502 may also express its intention for redundancy handling by providing redundancy information 501 indicative of the degree of redundancy associated with a given traffic flow, which may be mapped by the NEF 504 (or another network function) to the actual redundancy mechanism and its parameters. The AF 502 I the NEF 504 may forward the request to the concerned network functions, such as the SMF 508 or the PCF 506. The signaling may take place directly, or via other entities such as via the PCF 506 to the SMF 508. The concerned network functions may execute the redundancy handling based on the request, and may provide an acknowledgement signaling back to the NEF 504 and further back to the AF 502 on whether or not the request could be satisfied (and if not, an error cause may also be provided).

[0101] It should be noted that, in some embodiments, the use of NEF 504 is optional. In case the NEF 504 is not present in the signaling, the AF 502 may signal directly with the network entities, and may also have signaling via intermediate network functions such as the PCF 506. In some embodiments, there may be multiple network entities involved with signaling with the AF 502 for a given WCD. Instead of the AF 502, other entities may also make use of the exposure of redundancy functions, such as a TSN AF, or a TSCTSF. Additionally, or alternatively, in some embodiments, the redundancy information and the requests may be signaled to/from another network entity, e.g., beyond the AF 502.

[0102] Figure 4B is a flow chart illustrating a process for performing adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for a network traffic flow according to some embodiments of the present disclosure. Dashed boxes and lines represent steps that are optional according to some embodiments of the present disclosure. The process of Figure 4B is one example of step 408 of Figure 4A.

[0103] To perform the adjustments to the one or more network redundancy mechanisms, in some embodiments, at step 408A, the network node 400 applies PDCP duplication to the network traffic flow in the RAN. This may be done by applying a 5QI to the network traffic flow to enable PDCP duplication. Additionally, or alternatively, in in some embodiments, at step 408B, the network node 400 applies a dual connectivity mechanism to the network traffic flow. One example is illustrated in Figure 5B, which is a block diagram that illustrates one example adjustment to the network redundancy mechanism(s) by applying a 5QI in RAN to the network traffic flow to enable PDCP duplication according to some embodiments of the present disclosure. [0104] Turning to Figure 5B, one way of redundancy handling via adjustment of redundancy mechanism(s) is to apply PDCP duplication 515 to specific traffic flows in RAN 512, and optionally apply dual connectivity in combination with PDCP duplication 515, so that the traffic flows are duplicated over the air interface. For example, this function may be controlled by applying a 5QI (e.g., 5QI(s) 506A) (e.g., determined or selected at the PCF 506, etc.) for the concerned traffic flows for which PDCP duplication 515 (and optionally dual connectivity) is configured into RAN 512. The PCF 506 may provide information to the NEF 504 about which traffic flows (specified by their filtering criteria) apply a 5QI 506A for which PDCP duplication 515 is configured into RAN 512. For example, the PCF 506 may determine the concerned 5QIs 506A based on preconfiguration.) The PCF 506 may also provide information to the NEF 504 about which traffic flows apply PDCP duplication 515 in combination with dual connectivity.

[0105] The PCF 506 may also get requests 501 (e.g., from the AF 502 via the NEF504) to apply redundancy (and also an optional request 501 to also apply dual connectivity) in RAN 512 using PDCP duplication 515. The PCF 506 may then select a 5QI 506A for the traffic flow based on this request when possible, so that the request for redundant handling is observed. Feedback signaling about the success or failure for using the given 5QI 506A may be provided back to the originator of the request [0106] Returning to Figure 4B, additionally, or alternatively, in in some embodiments, at step 408C, the network node 400 enables, via a SMF, a N3/N9 redundancy mechanism for the network traffic flow. One example is illustrated in Figure 5C, which is a block diagram that illustrates one example adjustment to the network redundancy mechanism(s) by enabling a N3/N9 redundancy mechanism for the network traffic flow via a SMF according to some embodiments of the present disclosure.

[0107] Turning to Figure 5C, a method is illustrated to utilize duplicated GTP packets on the N3/N9 interface 508A, which is controlled by the SMF 508. The SMF 508 may provide information about which traffic flows are subject to the N3/N9 redundancy mechanism 515A mechanism. The information may be provided directly from the SMF 508 to the NEF 508, or indirectly via the PCF 506. The information may be sent when the redundancy 508A is established, or when there is a change in the traffic flows to which this redundancy mechanism 515 is applied.

[0108] The SMF 508 may also get requests (e.g., from the AF 502 via the NEF 504, which may be sent via the PCF 506) to handle certain flows with N3/N9 redundancy 508A (or to stop handling certain flows with N3/N9 redundancy 508A). The SMF 508 may consider the request and when possible it can try to satisfy the requests. The SMF 508 may provide feedback regarding the success or the failure of satisfying the request. [0109] Returning to Figure 4B, additionally, or alternatively, in in some embodiments, at step 408D, the network node 400 enables, via a SDN controller or via a communication endpoint, one or more transport network redundancy mechanisms for the network traffic flow. Specifically, adjustment(s) to the network redundancy mechanism(s) can be implemented via reliance on transport network redundancy mechanisms. In effect, this can appear similar to N3/N9 redundancy, as illustrated in Figure 5C, but the redundancy mechanism is instead realized within the transport network domain. The transport network redundancy mechanisms may be triggered e.g., by a controller, such as an SDN controller, or also by the communication endpoints, i.e., UPF and RAN node. The NEF may collect information about the redundancy handling in the transport network from these entities, and may forward external requests from these entities as well.

[0110] Additionally, or alternatively, in in some embodiments, at step 408E, the network node 400 establishes one or more redundant PDU sessions for one or more PDU sessions. One example is illustrated in Figure 5D, which is a block diagram that illustrates an example of dual connectivity based network redundancy mechanism(s) according to some embodiments of the present disclosure.

[0111] Turning to Figure 5D, the network can perform the adjustments to the redundancy mechanism(s) by applying a dual connectivity redundancy mechanism 515B based on redundant PDU Sessions connectivity as defined in 3GPP TS 23.501 section 5.33.2.1. The SMFs 508 are aware when such redundant handling is in effect based on the (DNN, S-NSSAI) parameters of the PDU sessions, or based on the (RSN, PDU Session Pair ID) dual connectivity information 508B from the WCD 516. In this case, the 3GPP system may indicate that the redundant handling is applicable to the given PDU Sessions, which may be identified based on the IP address, or Medium Access Control (MAC) address used over those PDU Sessions. It should be noted, however, that with a dual connectivity based mechanism, it may be possible that only some of the traffic over the PDU sessions is made redundant. This can be dependent on the upper layers. Hence, when the 3GPP system exposes information that the given PDU sessions (identified by certain endpoint addresses or range of addresses), it may also indicate that the system provides the possibility for redundant handling, but it is up to the upper layers, beyond 3GPP scope, whether or not redundancy is actually used.

[0112] The 3GPP system may also get a request (e.g., from the AF 502, possibly via the NEF 504) that the dual connectivity redundancy mechanism 515B should be used. If the 3GPP system possesses mechanisms to trigger the WCD 516 to establish redundant PDU sessions, the 3GPP system can attempt to satisfy the request.

[0113] Additionally, or alternatively, in in some embodiments, at step 408F1, the network node 400 determines that a WCD (e.g., WCD 112, etc.) associated with the network entity 200 includes two sub-WCDs (e.g., WCD 112 includes two UEs where these two UEs are sometimes referred to herein as "sub-WCDs"), and at step 408F2, establishes one sub-WCD of the two sub-WCDs as a duplicate carrier to enable a duplicate WCD-based redundancy mechanism for the network traffic flow. One example is illustrated in Figure 5E, which is a block diagram that illustrates an example of duplicate sub-WCD based network redundancy mechanism(s) according to some embodiments of the present disclosure.

[0114] Turning to Figure 5E, the 3GPP network may support scenarios where the single WCD 516 is equipped with multiple sub-WCDs 516A and 516B, and both sub- WCDs 516A and 516B connect to the network to send and receive redundant traffic. It should be noted that in some embodiments, separate AMF, SMF, or PCF entities may be utilized for the two sub-WCDs 516A and 516B. For example, a first UPF 514A and second UPF 514B may, in some embodiments, be utilized respectively for the two sub- WCDs 516A and 516B. Additionally, or alternatively, in some embodiments, two NEFs can respectively be used for the two sub-WCDs 516A and 516B. Additional configuration signaling may be employed from the network to the terminal to indicate whether or not to use the duplicate sub-WCD-based redundancy scheme, and if so, for which traffic. The signaling may be based on the AF 502provided information over the exposure interface.

[0115] Returning to Figure 4B, additionally, or alternatively, in in some embodiments, at step 408, the network node 400 enables one or more function-specific redundancy mechanisms to ensure high availability for at least a portion of the network traffic flow. The one or more function-specific redundancy mechanisms may include, but are not limited to, (a) redundant handling within one or more network functions, (b) redundant execution of at least a portion of the one or more network functions, (c) application of redundant coding schemes within the one or more network functions, or (d) two or more of any of (a) - (c). As an example, to apply redundant coding schemes within the one or more network functions, the network node may send or store data using added redundancy (e.g., multiple copies of the data, alternative coding schemes, etc.).

[0116] Additionally, or alternatively, in some embodiments, the network node 400 may utilize other mechanisms to ensure high availability for at least part of the end-to- end traffic flow (e.g., redundant transmission coding, redundant modulation schemes, and/or redundant transmission in multiple frequencies, etc.). In some embodiments, network functions (e.g., the RAN node, the UPF, or the SMF, PCF) can indicate to the NEF and further to the AF, that redundant handling is used within the network function (or user plane node). The indication may also include the type of redundancy and an indication about which network function or node it applies to, as well as a specification of the traffic flow. The indication may be sent from the network function or node to the NEF directly, or via other intermediate network functions.

[0117] Additionally, in some embodiments, the 3GPP system ca receive external requests (e.g., from an AF via the NEF) to handle certain traffic with redundancy at a given network function or node. This can facilitate allocation of redundant resources in an efficient way, so that the redundancy mechanisms apply where necessary.

[0118] In some embodiments, an AF or other external entity may not prefer utilization of any specific mechanisms for high availability. The AF may be interested only in which flows get extra redundant treatment, and the AF may advice the 3GPP network about which flows it requests redundant treatment. The decision about which specific mechanisms to employ in the 3GPP system may be left to the 3GPP network itself, and can be determined e.g., in the NEF or other network functions.

[0119] In some embodiments, a 3GPP network function, (e.g., a NEF a PCF, etc.), may be used to make a decision about which specific redundancy mechanism to use. To aid this, the network entity 200 (such as the AF) can indicate a degree of redundancy which can indicate the importance of giving redundancy to the given flow. For example, the AF may indicate a request for a high degree of redundancy for a given flow. Then the NEF, based on knowledge of the given network deployment and its limitations, may select which redundancy mechanism to use for a given flow. Then, the NEF may notify the concerned network functions to set up redundancy handling accordingly. For example, the NEF may determine, based on an AF request for high redundancy for a given flow, that the flow should be using PDCP duplication as well as N3 redundancy, even though the external AF may not explicitly indicate these mechanisms. The NEF may also determine the need for network function specific other redundancy mechanisms.

[0120] Similarly, in some embodiments, the NEF may collect information about which flows get redundant treatment using the redundant mechanisms in the system. The NEF may map this to a degree of redundancy. One example is where the degree of redundancy only reflects whether or not the given flow gets redundancy, and the NEF may provide only this information to the AF. Alternatively, the NEF may provide simplified information, where the degree of redundancy may be represented as a redundancy level (e.g., 1, 2, 3, etc.) depending on which mechanisms are used. This mapping can be based on configuration of the network done 400 and/or the network entity 200. In this way, the NEF may provide information about redundant treatment without giving details about specific 3GPP mechanisms which the external AF may not be interested in.

[0121] In some embodiments, the interpretation of certain redundancy levels can be specified. For example, redundancy levels 1, 2, 3 may correspond to No, Medium and High redundancy levels. Based on local configuration, the NEF may map it to specific mechanisms and its parameters.

[0122] Additionally, or alternatively, in some embodiments, the degrees of redundancy may be represented as seven levels of redundancy, and may correspond in the following manner:

• Level 1 - No redundancy

• Level 2 - Node level redundancy in the user plane nodes.

• Level 3 - Node level redundancy in the user plane nodes and control plane functions

• Level 4 - Node level redundancy in the user plane nodes and control plane functions and transport network redundancy

• Level 5 - Node level redundancy in the user plane nodes and control plane functions and PDCP redundancy and N3/N9 redundancy

• Level 6 - Dual connectivity based redundancy

• Level 7 - Dual UE based redundancy. [0123] In some embodiments, some of the parameter values of the redundancy level can be standardized, and other parameter values may be left as deployment or vendor specific. Besides the single parameter redundancy level in some embodiments, multiple values can be defined as parameters that are exposed without directly exposing the specific mechanisms. For example, separate parameters can exist for Redundancy Levels at the RAN, and the CN and at the transport network. Additionally, in some embodiments, separate redundancy level parameters cane exist for the individual network functions.

[0124] Figure 6 is a schematic block diagram of a network node 600 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The network node 600 may be, for example, a core network node that implements a NF or a network node that implements all or part of the functionality of an NF (e.g., all or part of the functionality of the AMF 200A, the SMF 200E, the PCF 200F, the AMF 200D, the AUSF 100B, the UDM 200C, the UPF 100H, the NEF 2001, the NRF 200J, etc.). As illustrated, the network node 600 includes a one or more processors 604 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 606, and a network interface 608. The one or more processors 604 are also referred to herein as processing circuitry. The one or more processors 604 operate to provide one or more functions of the network node 600 as described herein (e.g., one or more functions of the AMF 200A, the SMF 200E, the PCF 200F, the AMF 200D, the AUSF 100B, the UDM 200C, the UPF 100H, the NEF 2001, the NRF 200J, etc.). In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 606 and executed by the one or more processors 604.

[0125] Figure 7 is a schematic block diagram that illustrates a virtualized embodiment of the network node 600 according to some embodiments of the present disclosure. Again, optional features are represented by dashed boxes. As used herein, a "virtualized" network node is an implementation of the network node 600 in which at least a portion of the functionality of the network node 600 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the network node 600 includes one or more processing nodes 700 coupled to or included as part of a networks) 702. Each processing node 700 includes one or more processors 704 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 706, and a network interface 708. In this example, functions 710 of the network node 600 described herein (e.g., one or more functions of the AMF 200A, the SMF 200E, the PCF 200F, the AMF 200D, the AUSF 100B, the UDM 200C, the UPF 100H, the NEF 2001, the NRF 200J, etc.) are implemented at the one or more processing nodes 700 or distributed across the two or more processing nodes 700 in any desired manner. In some particular embodiments, some or all of the functions 710 of the network node 600 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 700.

[0126] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the network node 600 or a node (e.g., a processing node 700) implementing one or more of the functions 710 of the network node 600 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0127] Figure 8 is a schematic block diagram of the network node 600 according to some other embodiments of the present disclosure. The network node 600 includes one or more modules 800, each of which is implemented in software. The module(s) 800 provide the functionality of the network node 600 described herein. This discussion is equally applicable to the processing node 700 of Figure 7 where the modules 800 may be implemented at one of the processing nodes 700 or distributed across multiple processing nodes 700.

[0128] Figure 9 is a schematic block diagram of a wireless communication device 900 according to some embodiments of the present disclosure. As illustrated, the wireless communication device 900 includes one or more processors 902 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 904, and one or more transceivers 906 each including one or more transmitters 908 and one or more receivers 910 coupled to one or more antennas 912. The transceiver(s) 906 includes radio-front end circuitry connected to the antenna(s) 912 that is configured to condition signals communicated between the antenna(s) 912 and the processor(s) 902, as will be appreciated by on of ordinary skill in the art. The processors 902 are also referred to herein as processing circuitry. The transceivers 906 are also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device 900 described above may be fully or partially implemented in software that is, e.g., stored in the memory 904 and executed by the processor(s) 902. Note that the wireless communication device 900 may include additional components not illustrated in Figure 9 such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device 900 and/or allowing output of information from the wireless communication device 900), a power supply (e.g., a battery and associated power circuitry), etc.

[0129] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device 900 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0130] Figure 10 is a schematic block diagram of the wireless communication device 900 according to some other embodiments of the present disclosure. The wireless communication device 900 includes one or more modules 1000, each of which is implemented in software. The module(s) 1000 provide the functionality of the wireless communication device 900 described herein.

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

[0132] While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

[0133] Some example embodiments of the present disclosure are as follows:

[0134] Embodiment 1: A method performed by a network node (400) for customization of redundancy for network traffic flows, the method comprising: obtaining (406), from a network entity (200G), data indicative of a requested degree of redundancy for a network traffic flow; and, based at least in part on the requested degree of redundancy, performing (408) adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for the network traffic flow.

[0135] Embodiment 2: The method of embodiment 1, wherein, prior to obtaining (406) the data indicative of the requested degree of redundancy, the method comprises providing (404), to the network entity (200G), data indicative of a current degree of redundancy for the network traffic flow.

[0136] Embodiment 3: The method of embodiment 2, wherein, prior to providing (404) the data of the current degree of redundancy for the network traffic flow, the method comprises determining (402) the current degree of redundancy for the network traffic flow based at least in part on a number of network redundancy mechanisms of the plurality of network redundancy mechanisms that are activated for the network traffic flow.

[0137] Embodiment 4: The method of embodiment 3, wherein the data indicative of the current degree of redundancy for the network traffic flow is descriptive of an identity of each of the number of network redundancy mechanisms that are activated for the network traffic flow. [0138] Embodiment 5: The method of any of embodiments 2-4, wherein the adjustments to the one or more network redundancy mechanisms of the plurality of network redundancy mechanisms for the network traffic flow are based at least in part on the number of network redundancy mechanisms of the plurality of network redundancy mechanisms that are activated for the network traffic flow.

[0139] Embodiment 6: The method of any of embodiments 1-5, wherein, prior to performing (408) adjustments to one or more network redundancy mechanisms, the method comprises determining (407) the adjustments to the one or more network redundancy mechanisms based at least in part on the requested degree of redundancy. [0140] Embodiment 7: The method of any of embodiments 1-6, wherein the current degree of redundancy for the network traffic flow is determined using at least one of a Network Exposure Function, NEF, or a Time Sensitive Communications Time Synchronization Function, TSCTSF.

[0141] Embodiment 8: The method of any of embodiments 1-7, wherein the network entity (200G) comprises an Application Function, AF (200G).

[0142] Embodiment 9: The method of embodiment 8, wherein the network node (400) comprises a Network Exposure Function, NEF, and wherein the network node (400) obtains the data indicative of the requested degree of redundancy for the network traffic flow via a direct transmission from the network entity (200).

[0143] Embodiment 10: The method of embodiment 8, wherein the network node (400) comprises: a Policy Control Function, PCF; a Session Management Function, SMF; a User Plane Function, UPF; or a portion of a Radio Access Network, RAN; and wherein the network node obtains the data indicative of the requested degree of redundancy for the network traffic flow from the network entity (200G) indirectly via transmission from an additional network entity.

[0144] Embodiment 11: The method of any of embodiments 1-10, wherein the data indicative of the requested degree of redundancy for the network traffic flow is further indicative of the adjustments to the one or more network redundancy mechanisms of the plurality of network redundancy mechanisms for the network traffic flow.

[0145] Embodiment 12: The method of any of embodiments 1-11, wherein performing the adjustments to the one or more network redundancy mechanisms comprises: applying (408A) a Fifth Generation, 5G, Quality of Service, QoS, Identifier, 5QI, in RAN to the network traffic flow to enable PDCP duplication. [0146] Embodiment 13: The method of embodiment 12, wherein performing the one or more adjustments further comprises applying (408B) a dual connectivity mechanism to the network traffic flow.

[0147] Embodiment 14: The method of any of embodiments 1-13, wherein performing the one or more adjustments comprises enabling (408C), via a SMF, a N3/N9 redundancy mechanism for the network traffic flow.

[0148] Embodiment 15: The method of any of embodiments 1-14, wherein performing the one or more adjustments comprises enabling (408D), via a Software- Defined Networking, SDN, controller or via a communication endpoint, one or more transport network redundancy mechanisms for the network traffic flow.

[0149] Embodiment 16: The method of any of embodiments 1-15, wherein performing the one or more adjustments comprises establishing (408E) one or more redundant Protocol Data Unit, PDU, sessions for one or more PDU sessions.

[0150] Embodiment 17: The method of any of embodiments 1-16, wherein performing the one or more adjustments comprises: determining (408F1) that a Wireless Communication Device, WCD (112), associated with the network entity (200) includes two sub-WCDs; and establishing (408F2) one sub-WCD of the two sub-WCDs as a duplicate carrier to enable a duplicate WCD-based redundancy mechanism for the network traffic flow.

[0151] Embodiment 18: A method of any of embodiments 1-17, wherein performing the one or more adjustments comprises enabling (408G) one or more function-specific redundancy mechanisms to ensure high availability for at least a portion of the network traffic flow, wherein the one or more function-specific redundancy mechanisms comprise:

(a) redundant handling within one or more network functions;

(d) two or more of any of (a) - (c).

[0152] Embodiment 19: A network node (400) for customization of redundancy for network traffic flows, the network node (400) adapted to: obtain (406), from a network entity (200), data indicative of a requested degree of redundancy for a network traffic flow; and, based at least in part on the requested degree of redundancy, perform (408) adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for the network traffic flow.

[0153] Embodiment 20: The network node of embodiment 19, wherein the network node (400) is further adapted to perform the method of any of embodiments 1-18.

[0154] Embodiment 21: A network node (600) for customization of redundancy for network traffic flows, the network node (600) comprising: one or more transmitters (612); one or more receivers (614); and processing circuitry (604) configured to cause the network node (600) to obtain (406), from a network entity (200), data indicative of a requested degree of redundancy for a network traffic flow and, based at least in part on the requested degree of redundancy, perform (408) adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for the network traffic flow.

[0155] Embodiment 22: The network node (600) of embodiment 21, wherein the processing circuitry (604) is further configured to cause the network node (600) to perform the method of any of embodiments 1-18.

[0156] Embodiment 23: A network node (400) for customization of redundancy for network traffic flows, wherein the network node (400) is adapted to: receive (401), from an Application Function, AF, (200G) a request for data indicative of a current degree of redundancy for a network traffic flow; and provide (404), to the AF (200G), the data indicative of the current degree of redundancy for the network traffic flow. [0157] Embodiment 24: The network node embodiment 23, wherein, prior to providing (404) the data of the current degree of redundancy for the network traffic flow, the network node (400) is adapted to determine (402) the current degree of redundancy for the network traffic flow based at least in part on a number of network redundancy mechanisms of a plurality of network redundancy mechanisms that are activated for the network traffic flow.

[0158] Embodiment 25: The network node of embodiment 24, wherein the network node (400) is further adapted to obtain (406), from the AF (212), data indicative of a requested degree of redundancy for the network traffic flow.

[0159] Embodiment 26: The method of embodiment 25, wherein the network node (400) is further adapted to, based at least in part on the requested degree of redundancy, perform (408) adjustments to one or more network redundancy mechanisms of the plurality of network redundancy mechanisms for the network traffic flow.

[0160] Embodiment 27: The method of embodiment 26, wherein the network node (400) is further adapted to perform the method of any of embodiments 4-18. [0161] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

1. A method performed by a network node (400; 504; 506; 508; 514; 510; 512) for customization of redundancy for network traffic flows, the method comprising: obtaining (406), from a network entity (200G; 502), data indicative of a requested degree of redundancy for a network traffic flow; and based at least in part on the requested degree of redundancy, performing (408) adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for the network traffic flow.

2. The method of claim 1, wherein the network entity (200G; 502) is an Application Function, AF, (200G; 502).

3. The method of claim 1 or 2, wherein, prior to obtaining (406) the data indicative of the requested degree of redundancy, the method comprises providing (404), to the network entity (200G; 502), data indicative of a current degree of redundancy for the network traffic flow.

4. The method of claim 3, wherein, prior to providing (404) the data of the current degree of redundancy for the network traffic flow, the method comprises determining (402) the current degree of redundancy for the network traffic flow based at least in part on a number of network redundancy mechanisms of the plurality of network redundancy mechanisms that are activated for the network traffic flow.

5. The method of claim 4, wherein the data indicative of the current degree of redundancy for the network traffic flow is descriptive of an identity of each of the number of network redundancy mechanisms that are activated for the network traffic flow.

6. The method of any of claims 3-5, wherein the adjustments to the one or more network redundancy mechanisms of the plurality of network redundancy mechanisms for the network traffic flow are based at least in part on the number of network redundancy mechanisms of the plurality of network redundancy mechanisms that are activated for the network traffic flow.

34

7. The method of any of claims 1-6, wherein, prior to performing (408) adjustments to one or more network redundancy mechanisms, the method comprises determining (407) the adjustments to the one or more network redundancy mechanisms based at least in part on the requested degree of redundancy.

8. The method of any of claims 1-7, wherein the network node (400) comprises a Network Exposure Function, NEF, and wherein the network node (400) obtains the data indicative of the requested degree of redundancy for the network traffic flow via a direct transmission from the network entity (200G; 502).

9. The method of any of claims 1-7, wherein the network node (400) comprises: a Policy Control Function, PCF; a Session Management Function, SMF; a User Plane Function, UPF; or at least portion of a Radio Access Network, RAN, node.

10. The method of claim 9, wherein obtaining the data indicative of the requested degree of redundancy for the network traffic flow from the network entity (200G; 502) comprises obtaining the data indicative of the requested degree of redundancy for the network traffic flow from the network entity (200G) indirectly via an additional network entity (504).

11. The method of any of claims 1-10, wherein the data indicative of the requested degree of redundancy for the network traffic flow is further indicative of the adjustments to the one or more network redundancy mechanisms of the plurality of network redundancy mechanisms for the network traffic flow.

12. The method of any of claims 1-11, wherein performing the adjustments to the one or more network redundancy mechanisms comprises: applying (408A) Packet Data Convergence Protocol, PDCP, duplication for the network traffic flow.

35

13. The method of claim 12, wherein performing the one or more adjustments further comprises applying (408B) a dual connectivity mechanism to the network traffic flow.

14. The method of any of claims 1-13, wherein performing the one or more adjustments comprises enabling (408C), via a Session Management Function, SMF, (508), a N3/N9 redundancy mechanism for the network traffic flow.

15. The method of any of claims 1-14, wherein performing the one or more adjustments comprises enabling (408D), via a Software-Defined Networking, SDN, controller or via a communication endpoint, one or more transport network redundancy mechanisms for the network traffic flow.

16. The method of any of claims 1-15, wherein performing the one or more adjustments comprises establishing (408E) one or more redundant Protocol Data Unit, PDU, sessions for one or more PDU sessions.

17. The method of any of claims 1-16, wherein performing the one or more adjustments comprises: determining (408F1) that a Wireless Communication Device, WCD (112), associated with the network entity (200) includes two sub-WCDs; and establishing (408F2) one sub-WCD of the two sub-WCDs as a duplicate carrier to enable a duplicate WCD-based redundancy mechanism for the network traffic flow.

18. The method of any of claims 1-17, wherein performing the one or more adjustments comprises enabling (408G) one or more function-specific redundancy mechanisms to ensure high availability for at least a portion of the network traffic flow, wherein the one or more function-specific redundancy mechanisms comprise:

(a) redundant handling within one or more network functions;

(c) application of redundant coding schemes within the one or more network functions; or (d) any two or more of (a) - (c).

19. A network node (400) for customization of redundancy for network traffic flows, the network node (400) adapted to: obtain (406), from a network entity (200), data indicative of a requested degree of redundancy for a network traffic flow; and based at least in part on the requested degree of redundancy, perform (408) adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for the network traffic flow.

20. The network node of claim 19, wherein the network node (400) is further adapted to perform the method of any of claims 2-18.

21. A network node (600) for exposure of redundancy for network traffic flows, the network node (600) comprising: processing circuitry (604) configured to cause the network node (600) to: obtain (406), from a network entity (200), data indicative of a requested degree of redundancy for a network traffic flow; and based at least in part on the requested degree of redundancy, perform (408) adjustments to one or more network redundancy mechanisms of a plurality of network redundancy mechanisms for the network traffic flow.

22. The network node (600) of claim 21, wherein the processing circuitry (604) is further configured to cause the network node (600) to perform the method of any of claims 2-18.

23. A network node (400) for exposure of redundancy for network traffic flows, wherein the network node (400) is adapted to: receive (401), from an Application Function, AF, (200G), a request for data indicative of a current degree of redundancy for a network traffic flow; and provide (404), to the AF (200G), the data indicative of the current degree of redundancy for the network traffic flow.

24. The network node claim 23, wherein, prior to providing (404) the data of the current degree of redundancy for the network traffic flow, the network node (400) is adapted to determine (402) the current degree of redundancy for the network traffic flow based at least in part on a number of network redundancy mechanisms of a plurality of network redundancy mechanisms that are activated for the network traffic flow.

25. The network node of claim 24, wherein the network node (400) is further adapted to obtain (406), from the AF (212), data indicative of a requested degree of redundancy for the network traffic flow.

26. The method of claim 25, wherein the network node (400) is further adapted to, based at least in part on the requested degree of redundancy, perform (408) adjustments to one or more network redundancy mechanisms of the plurality of network redundancy mechanisms for the network traffic flow.

27. The method of claim 26, wherein the network node (400) is further adapted to perform the method of any of claims 5-18.

38