WO2022271185A1

WO2022271185A1 - Reliability in a communication system

Info

Publication number: WO2022271185A1
Application number: PCT/US2021/039121
Authority: WO
Inventors: Colin Kahn; Devaki Chandramouli
Original assignee: Nokia Technologies Oy; Nokia Of America Corporation
Priority date: 2021-06-25
Filing date: 2021-06-25
Publication date: 2022-12-29

Abstract

According to the disclosure there is provided an apparatus comprising means for performing: hosting an application function for running an application in a communication system; communicating a request with the communication system, the request comprising one or more required reliability parameters of the communication system for the application function; receiving a response from the communication system, the response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and operating the application function in accordance with the reliability configuration.

Description

RELIABILITY IN A COMMUNICATION SYSTEM

Field

The present disclosure relates to methods, apparatuses and computer program products in a communication system, and more particularly but not exclusively to reliability in a communication system.

Background

A communication system provides a facility communication between two or more devices such as user terminals, machine-like terminals, base stations and other access points, network functions, service producers, service consumers, and/or other devices. A communication system can be provided for example by means of a communication network and one or more compatible devices providing communication channels for carrying information between the communicating devices. Communication sessions may comprise, for example, communication of data for carrying communications for services such as voice, video, electronic mail (email), text message, multimedia, control data and/or content data and so on.

In a mobile or wireless communication system at least a part of a communications between at least two devices occurs over a wireless or radio link. Examples of wireless systems comprise public land mobile networks (PLMN), satellite-based communication systems and different wireless local networks, for example wireless local area networks (WLAN). A user can access the wider communication system via an access system means of an appropriate communication device or terminal. Non-limiting examples of communication devices are a user equipment (UE) or user device and various machine-like terminals. The wireless access can be provided by a base station of a radio access system or network (RAN). Radio access systems provide local coverage areas and are connected via an appropriate transport system to a larger communication system, known as the core network.

The core network comprises a wide variety of entities providing various functions and services. Similar functions and/or services may be provided by different entities in separate locations and/or by distributed data processing. At least some of the functions and/or services may be provided by virtual data processing instances. Providing data communications between the accessing devices and the service providing entities such as application functions can involve intermediate and otherwise associated entities, processes and functions.

A management system comprises a wide variety of entities providing various management services, e.g. provisioning, configuration, performance monitoring, fault supervision, and so on.

The communication system, services, functions and devices typically operate in accordance with a given standard or specification which sets out what the various entities associated with the system are permitted to do and how that should be achieved. Communication protocols and/or parameters which shall be used for the connection are also typically defined. Non-limiting examples of communication systems include those based on fifth generation (5G) networks standardized by the 3rd Generation Partnership Project (3GPP).

Some services that are provided in a network require a certain level of reliability to function adequately and/or safely. For example, industrial internet of things (IIoT) devices may require a certain reliability level to meet performance expectations.

Summary

According to a first aspect there is provided an apparatus comprising means for performing: hosting an application function for running an application in a communication system; communicating a request with the communication system, the request comprising one or more required reliability parameters of the communication system for the application function; and receiving a response from the communication system, the response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and operating the application function in accordance with the reliability configuration.

According to some examples, the response indicating that a reliability configuration has been configured does not provide details of the reliability configuration.

According to some examples, the response indicating that a reliability configuration has been configured additionally provides details of the reliability configuration.

According to some examples, the one or more reliability parameters comprise one or more of: a reliability level; one or more reliability related features.

According to some examples, the reliability level is expressed as a percentage.

According to some examples a reliability feature of the one or more reliability related features is a communication system capability that affects reliability.

According to some examples, the communicating a request with the communication system comprises one or more of: sending information pertaining to two or more redundant user equipment in the communication system having a same endpoint; sending information pertaining to one user equipment that may communicate over a redundant path in one or more segments of the communication system.

According to some examples, the means are further configured to perform communicating with the communication system to determine a reliability capability of the communication system.

According to some examples, the determining a reliability capability of the communication system comprises determining one or more of: whether the communication system supports redundant paths via dual connectivity or carrier aggregation; whether the communication system supports redundant packet data unit sessions; whether the communication system supports redundant transmission via packet data convergence protocol duplication; whether the communication system supports redundant transmission on N3 and/or N9 interfaces; whether the communication system supports redundant paths using two or more user equipment having a same endpoint; whether the communication system supports higher layer protocol for use with redundant paths; whether the communication system supports one or more percentage reliability levels.

According to some examples, the means are further configured to perform receiving and storing a mapping between the one or more reliability features and an indication of support for the one or more reliability features.

According to some examples, the means are further configured to perform sending a request for a notification when one or more of the one or more required reliability parameters is not met.

According to some examples, the means are further configured to perform receiving a notification of one or more of: a reliability level falling below a threshold value; failure of a redundant radio path due to radio conditions; failure of a redundant radio path due to radio access network failure; failure of a redundant path due to user equipment failure; failure of a redundant path due to failure of a node of the communication system; failure of a redundant path due to redundant transmission on N3 and/or N9 interface.

According to some examples, the means are further configured to perform sending an identifier of the application function to the communication system, for authorization of the application function to receive the response that the reliability configuration has been configured.

According to some examples, the communication system comprises a 5G system.

According to some examples, the means comprises at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

According to a second aspect there is provided an apparatus comprising at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: hosting an application function for running an application in a communication system; communicating a request with the communication system, the request comprising one or more required reliability parameters of the communication system for the application function; and receiving a response from the communication system, the response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and operating the application function in accordance with the reliability configuration.

According to a third aspect there is provided an apparatus comprising: circuitry for hosting an application function for running an application in a communication system; circuitry for communicating a request with the communication system, the request comprising one or more required reliability parameters of the communication system for the application function; circuitry for receiving a response from the communication system, the response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and circuitry for operating the application function in accordance with the reliability configuration.

According to a fourth aspect there is provided a method comprising: hosting an application function for running an application in a communication system; communicating a request with the communication system, the request comprising one or more required reliability parameters of the communication system for the application function; and receiving a response from the communication system, the response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and operating the application function in accordance with the reliability configuration.

According to some examples, the reliability level is expressed as a percentage.

According to some examples, the method comprises communicating with the communication system to determine a reliability capability of the communication system.

According to some examples, the method comprises receiving and storing a mapping between the one or more reliability features and an indication of support for the one or more reliability features. According to some examples, the method comprises sending a request for a notification when one or more of the one or more required reliability parameters is not met.

According to some examples, the method comprises receiving a notification of one or more of: a reliability level falling below a threshold value; failure of a redundant radio path due to radio conditions; failure of a redundant radio path due to radio access network failure; failure of a redundant path due to user equipment failure; failure of a redundant path due to failure of a node of the communication system; failure of a redundant path due to redundant transmission on N3 and/or N9 interface.

According to some examples, the method comprises sending an identifier of the application function to the communication system, for authorization of the application function to receive the response that the reliability configuration has been configured.

According to some examples, the communication system comprises a 5G system.

According to a fifth aspect there is provided a computer program comprising instructions for causing an apparatus to perform at least the following: hosting an application function for running an application in a communication system; communicating a request with the communication system, the request comprising one or more required reliability parameters of the communication system for the application function; and receiving a response from the communication system, the response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and operating the application function in accordance with the reliability configuration

According to a sixth aspect there is provided a computer program comprising instructions stored thereon for performing at least the following: hosting an application function for running an application in a communication system; communicating a request with the communication system, the request comprising one or more required reliability parameters of the communication system for the application function; and receiving a response from the communication system, the response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and operating the application function in accordance with the reliability configuration.

According to a seventh aspect there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the following: hosting an application function for running an application in a communication system; communicating a request with the communication system, the request comprising one or more required reliability parameters of the communication system for the application function; and receiving a response from the communication system, the response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and operating the application function in accordance with the reliability configuration. According to an eighth aspect there is provided a non-transitory computer readable medium comprising program instructions stored thereon for performing at least the following: hosting an application function for running an application in a communication system; communicating a request with the communication system, the request comprising one or more required reliability parameters of the communication system for the application function; and receiving a response from the communication system, the response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and operating the application function in accordance with the reliability configuration.

According to a ninth aspect there is provided an apparatus comprising means for performing: receiving, from an application function, a request comprising one or more required reliability parameters of a communication system for the application function; and responding to the request with a response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and causing the communication system to operate in accordance with the reliability configuration.

According to some examples, the one or more reliability parameters comprises one or more of: a reliability level; one or more reliability related features.

According to some examples, the reliability level is expressed as a percentage.

According to some examples, the means are further configured to perform receiving, from the application function, one or more of: information pertaining to two or more redundant user equipment in the communication system having a same endpoint; information pertaining to one user equipment that may communicate over a redundant path in one or more segments of the communication system.

According to some examples, the means are further configured to perform, in response to the receiving information pertaining to two or more redundant user equipment in the network having a same endpoint, informing at least one node so that resources of the two or more redundant user equipment can be re-allocated.

According to some examples, the causing the communication system to operate in accordance with the reliability configuration comprises triggering set-up of a high reliability configuration in the communication system. According to some examples, the causing the communication system to operate in accordance with the reliability configuration comprises triggering a new reliability configuration for one or more traffic flows.

According to some examples, the means are further configured to perform indicating to the application function at least one of: whether the communication system supports redundant paths via dual connectivity or carrier aggregation; whether the communication system supports redundant packet data unit sessions; whether the communication system supports redundant transmission via packet data convergence protocol duplication; whether the communication system supports redundant transmission on N3 and/or N9 interfaces; whether the communication system supports redundant paths using two or more user equipment having a same endpoint; whether the communication system supports higher layer protocol for use with redundant paths; whether the communication system supports one or more percentage reliability levels.

According to some examples, the means are further configured to perform sending to the application function a mapping between the one or more reliability features and an indication of support for the one or more reliability features.

According to some examples, the means are further configured to perform receiving a request for a notification when one or more of the one or more required reliability parameters is not met.

According to some examples, the means are further configured to perform sending a notification of one or more of: a reliability level falling below a threshold value; failure of a redundant radio path due to radio conditions; failure of a redundant radio path due to radio access network failure; failure of a redundant path due to user equipment failure; failure of a redundant path due to failure of a node of the communication system; failure of a redundant path due to redundant transmission on N3 and/or N9 interface.

According to some examples, the means are further configured to perform receiving an identifier of the application function, and authorizing the application function to receive the response that the reliability configuration has been configured.

According to some examples, the apparatus comprises one or more of a network exposure function, a policy control function and a new network function.

According to a tenth aspect, there is provided an apparatus comprising at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receiving, from an application function, a request comprising one or more required reliability parameters of a communication system for the application function; and responding to the request with a response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and causing the communication system to operate in accordance with the reliability configuration.

According to an eleventh aspect there is provided an apparatus comprising: circuitry for receiving, from an application function, a request comprising one or more required reliability parameters of a communication system for the application function; circuitry for responding to the request with a response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and circuitry for causing the communication system to operate in accordance with the reliability configuration.

According to a twelfth aspect there is provided a method comprising: receiving, from an application function, a request comprising one or more required reliability parameters of a communication system for the application function; responding to the request with a response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and causing the communication system to operate in accordance with the reliability configuration.

According to some examples, the reliability level is expressed as a percentage.

According to some examples, the method comprises receiving, from the application function, one or more of: information pertaining to two or more redundant user equipment in the communication system having a same endpoint; information pertaining to one user equipment that may communicate over a redundant path in one or more segments of the communication system.

According to some examples the method comprises, in response to the receiving information pertaining to two or more redundant user equipment in the network having a same endpoint, informing at least one node so that resources of the two or more redundant user equipment can be re-allocated.

According to some examples the method comprises indicating to the application function at least one of: whether the communication system supports redundant paths via dual connectivity or carrier aggregation; whether the communication system supports redundant packet data unit sessions; whether the communication system supports redundant transmission via packet data convergence protocol duplication; whether the communication system supports redundant transmission on N3 and/or N9 interfaces; whether the communication system supports redundant paths using two or more user equipment having a same endpoint; whether the communication system supports higher layer protocol for use with redundant paths; whether the communication system supports one or more percentage reliability levels.

According to some examples, the method comprises sending to the application function a mapping between the one or more reliability features and an indication of support for the one or more reliability features.

According to some examples, the method comprises receiving a request for a notification when one or more of the one or more required reliability parameters is not met.

According to some examples the method comprises sending a notification of one or more of: a reliability level falling below a threshold value; failure of a redundant radio path due to radio conditions; failure of a redundant radio path due to radio access network failure; failure of a redundant path due to user equipment failure; failure of a redundant path due to failure of a node of the communication system; failure of a redundant path due to redundant transmission on N3 and/or N9 interface.

According to some examples the method comprises receiving an identifier of the application function, and authorizing the application function to receive the response that the reliability configuration has been configured.

According to some examples the method is performed by one or more of: a network exposure function; a policy control function; a new network function.

According to a thirteenth aspect there is provided a computer program comprising instructions for causing an apparatus to perform at least the following: receiving, from an application function, a request comprising one or more required reliability parameters of a communication system for the application function; responding to the request with a response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and causing the communication system to operate in accordance with the reliability configuration. According to a fourteenth aspect there is provided a computer program comprising instructions stored thereon for performing at least the following: receiving, from an application function, a request comprising one or more required reliability parameters of a communication system for the application function; responding to the request with a response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and causing the communication system to operate in accordance with the reliability configuration.

According to a fifteenth aspect there is provided a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the following: receiving, from an application function, a request comprising one or more required reliability parameters of a communication system for the application function; responding to the request with a response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and causing the communication system to operate in accordance with the reliability configuration.

According to a sixteenth aspect there is provided a non-transitory computer readable medium comprising program instructions stored thereon for performing at least the following: receiving, from an application function, a request comprising one or more required reliability parameters of a communication system for the application function; responding to the request with a response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and causing the communication system to operate in accordance with the reliability configuration.

Brief description of Figures

Embodiments will now be described, by way of example only, with reference to the accompanying Figures in which:

Figure 1 shows a schematic representation of a 5G system;

Figure 2 is a signalling diagram schematically showing a method of exposing an application function to reliability information;

Figure 3 is a signalling diagram schematically showing a method for an application to request reliability information;

Figure 4 is a signalling diagram schematically showing a method of reliability parameter provisioning;

Figure 5 shows a schematic representation of a network apparatus;

Figure 6 shows a schematic representation of a user equipment;

Figure 7 shows an example method flow diagram performed by a network entity;

Figure 8 shows an example method flow diagram performed by a network entity; Figure 9 shows a schematic representation of a non-volatile memory medium storing instructions which when executed by a processor allow a processor to perform one or more of the steps of the method of Figures 7 or 8.

Detailed description

Before explaining in detail some examples of the present disclosure, certain general principles of a wireless communication system and mobile communication devices are briefly explained with reference to Figure 1 to assist in understanding the technology underlying the described examples.

Figure 1 shows a schematic representation of a 5G system (5GS) 100. The 5GS may comprise a terminal 102, a 5G access network (5G-AN) 106, a 5G core network (5GC) 104, one or more network functions (NF), one or more application function (AF) 108 and one or more data networks (DN) 110.

The 5G-AN 106 may comprise one or more gNodeB (gNB) distributed unit functions connected to one or more gNodeB (gNB) centralized unit functions.

The 5GC 104 may comprise an access management function (AMF) 112, a session management function (SMF) 114, an authentication server function (AUSF) 116, a user data management function (UDM) 118, a user plane function (UPF) 120, a network exposure function (NEF) 122 and/or other NFs. Some of the examples as shown below may be applicable to 3GPP 5G standards. However, some examples may also be applicable to 4G, 3G and other 3GPP standards.

In 3GPP Release 17, Exposure for Periodic Deterministic QoS (Quality of Service) was introduced in to 3GPP standards. According to some examples, deterministic QoS may be considered to mean that the delay between transmission of a message and receipt of the message at the destination address is stable (within bounds).. This capability allows an application function (AF) to provide deterministic application requirements to request time sensitive communication (TSC) services from the 5GS. Periodic Deterministic QoS is used to support guaranteed latency, and enables the 5GS to exploit periodic deterministic traffic characteristics known to the AF when IEEE TSN (time sensitive network) is not deployed external to the 5GS. The AF may request QoS with specified requirements and supply traffic characteristics (e.g. any one or more of: periodicity; burst arrival time; survival time) that can be used by the session management function (SMF) to derive TSCAI (time sensitive communication assistance information) for 5GS QoS flows, which is then used by the RAN to optimize scheduling and reduce latency.

Another service attribute is support for high reliability. High reliability may be required in an industrial internet of things (IIoT) setting, for example in factory automation. In some examples, reliability is a measure of how reliably the system is communicating data packets. Reliability may be lost where the system is losing packets, is delivering packets late, or the packets are delivered with errors. 3GPP has adopted several approaches for increasing communication service reliability by enabling multiple paths and redundant transmission via the 5GS. For example:

1. A UE may use dual connectivity to establish protocol data unit (PDU) sessions to separate UPFs as described in TS23.501 clause 5.33.2.1. To improve reliability, redundant paths are setup through different access nodes (Master RAN and Secondary RAN). The data network (DN) sees both paths, and techniques outside of the 5GS, such as FRER defined in IEEE 802.1CB may be used to generate duplicate traffic streams.

2. Redundant paths on the wired 5GS user plane interfaces (N3 and N9) may be established using redundant N3 or N9 tunnels (between the PSA UPF and the NG- RAN), as described in TS23.501 clause 5.33.2.2

3. Two UEs associated with a same endpoint may independently setup PDU sessions, eliminating the UE as a single point of failure as described in TS23.501 Annex F. The two UEs must select different gNBs and setup PDU Sessions to UPFs with orthogonal failure modes. As described in 23.501 Annex F, the selection of different gNBs may be realized by the concept of UE Reliability Groups for the UEs and the cells of gNBs. A UE assigned to a Reliability Group preferentially selects cells/gNBs associated with that Reliability Group. Hence UEs associated with the same endpoint may be simply assigned to different Reliability Groups.

4. Packet data convergence protocol (PDCP) layer packet duplication. The NG-RAN (next generation RAN) and/or UE may be configured by RRC to duplicate packets across redundant radio paths, enabled by dual connectivity or carrier aggregation.

Note that these techniques may improve communication service reliability by increasing resiliency. Resiliency may be considered an ability to maintain service in the event of a failure, such as a failure of a wireless link, a network function or a UE. Currently the decision to configure and use high reliability communications is made by the UE or the 5GS.

For a single UE, the decision to establish two redundant PDU Sessions and duplicate application traffic to these PDU Sessions is based on URSP (uplink route selection policy) provided by a PCF or based on UE local configuration. Similarly, setup of redundant transmission on N3/N9 is decided by the SMF during or after an ultra reliable low latency communication (URLLC) QoS flow establishment. In some examples, the SMF decision is based on one or more of: 5QI (5G QoS identifier); NG-RAN node capability; operator configuration; and/or Redundant Transmission Experience analytics. When two UEs are associated with the same endpoint, it is left to implementation when or how redundant transmission is used, and for PDCP duplication RAN RRC determines when packet duplication is to occur. In all these cases, the decision to establish or use redundant paths is either internal to the 5GS or UE, or left to implementation. However, the present disclosure identifies that a need for redundant paths and more generally high reliability may in some instances be specific to an application and requirements of the application. For example, while applications using real-time deterministic communication between a robot and a controller might require ultra-high reliability, the same or a different application performing non-real -time management tasks may not. Currently there is no mechanism for an Application Function (AF) to discover the reliability options that may be provided by the 5GS. There is also no mechanism for an AF to request a reliability level or to request use of specific reliability features. Also, there is no mechanism for the 5GS to receive notifications when reliability requirements are not met.

Currently, an AF can request QoS and provide a QoS reference that corresponds to a URFFC 5QI (which may be selected by the PCF). The 5QI may result in provisioning by the PCF of a URSP on the UE, that results in redundant transmission. However, there is no mechanism for the AF to indicate reliability requirements separately from QoS requirements.

An AF can provide guidance for URSP determination to support edge computing as described in 3GPP 23.502 clause 4.15.6.10 and TS23.548. The AF can provide routing guidance to a UE so traffic may be directed to an “external party dedicated DNN and/or S-NSSAI” (typically a corporate network) vs an operator PFMN, for example based on the location of the UE.

While some aspects of the present disclosure also use URSP, it is to trigger redundant PDU session setup and routing of duplicated traffic over the redundant paths, rather than to direct traffic to a corporate versus public network.

The present disclosure provides apparatus, methods, and computer programs which enable reliability information to be exposed to an application function (AF). The application function may be hosted on an apparatus. The apparatus may for example be a network apparatus. The application function is configured to run one or more applications. In some examples, reliability may be expressed as a percentage. In some examples the percentage represents a number of packets successfully delivered by a communication service within a time constraint, divided by a total number of packets sent by the communication service. In some examples, the AF communicates with a network exposure function (NEF) to obtain reliability information. In some examples, the AF communicates directly with the policy control function (PCF) to obtain the reliability information. As will be described in more detail below, the AF may use the information to send a request for reliability. In some examples the request may be a request for specific reliability features. In some examples, the request may be a request for a reliability level (e.g. a certain percentage). For example, the reliability information may include the reliability provided without redundant transmission, and the reliability that may be attained with the use of one or more supported approaches for increasing communication service reliability by enabling multiple paths and redundant transmission. The AF may then use that information to formulate a request to the 5GS.

In some examples, the reliability information may pertain to reliability information of a 5GS (e.g. 5G system 100 of Figure 1) as a whole. In some examples, the reliability information may be associated with a part or section of the 5GS. In some examples, the reliability information may be associated with one or more UEs.

The present disclosure considers three procedures an AF may take to achieve a level of reliability required by an application hosted by the AF:

1. AF determines reliability capabilities of 5GS. The reliability capabilities of 5GS may include UE reliability capabilities.

2. AF requests a reliability from the 5GS, which may comprise a request for specific reliability features or a request for a reliability level which the 5GS then configures. The AF may request the reliability either directly from PCF or via NEF.

3. AF requests notifications and receives notifications when reliability requirements are not met.

It is to be noted that each of these three procedures may occur independently, or together with one or more of the other procedures. In some examples, procedure “2. AF requests a reliability from the 5GS” is considered a primary or initial procedure, with “1. AF determines reliability capabilities of 5GS” and “3. AF requests notifications and receives notifications when reliability requirements are not met” being considering secondary or subsequent procedures from the primary procedure. Each of these procedures is discussed in more detail below.

1. AF determines reliability capabilities of the 5GS

In some examples, determining reliability capabilities of 5GS may be specific to an AF. For example, 5GS reliability capabilities may be different for different AFs. In some examples, reliability capability may be dependent on authorization for an AF-ID by the 5GS. By way of example, an AF may send a request to the 5GS asking “what reliability can you support for me?”. The response from the 5GS may depend on which AF is asking (as identified by the AF-ID). For example, a robot/controller may be authorized for different reliability than an autonomous shop vacuum cleaner. The response to the AF could reflect that (see for example S2 in Figure 2). The capability information may include, for example:

(i) - Support for specific reliability levels (eg: 99.999% reliability). In some examples the 5GS provides a mapping between reliability features (see features in (ii) below for example) and reliability levels. For example, the 5GS provides a mapping between features of the 5GS and reliability levels of each respective feature.

(ii) - Support for specific reliability features may include:

• Support for redundant paths via dual connectivity or carrier aggregation (CA) • Support for redundant PDU sessions

• Support for redundant transmission via PDCP duplication

• Support for redundant transmission on N3/N9

• Support for redundant paths using two (or more) UEs associated with the same endpoint

• Support for a higher layer protocol such as Frame Replication and Elimination for Reliability (FRER) (802.1CB) or multi-path TCP (MPTCP) for use with redundant paths

• It should also be noted that in some examples the AF simply states a reliability level that the AF requires or supports, without requiring a mapping to specific reliability features. For example, the AF may advertise that it requires or supports 99.99% or 99.999% reliability.

2. _ AF requests reliability from the 5GS

In such examples, the AF may specify one or more reliability levels and/or one or more specific reliability features. In some examples, the request for reliability may be for communication path reliability with a specific UE. For example, the AF may request that the 5GS performs to a reliability level specified by the AF, or provides specific reliability features to the AF. If the request is accepted, the 5GS then takes actions to achieve the requested reliability level or activate the requested reliability features. In some examples, reliability for a specific UE may be considered a reliability of a communication path with that UE. In some examples, the request for reliability capability information may be for all UEs associated with a DNN/S-NSSAI (data network name / single network slice assistance information).

In some examples, the AF request, whether for specific reliability feature(s) or a reliability level, may:

(i). Trigger the setup of a high reliability configuration in the 5GS. For example, information from the AF request for reliability:

• can be stored in the 5GS (eg: UDM) and applied when the UE initiates a PDU Session request for a given DNN/S-NSSAI

• can be used to trigger URSP policy update in the UE for a given DNN/S- NSSAI. When the UE initiates a transaction, it will initiate setup of redundant sessions which may have independent failure modes, if not already setup.

• can be used to trigger the UE to setup dual connectivity or CA so PDCP duplication over redundant paths may be enabled.

• can be used by the 5GS to configure redundant tunnels on N3/N9

• may be used to trigger multiple UEs associated with the same endpoint to setup PDU sessions using paths with independent failure modes. (ii). Trigger use of new or existing reliability configuration for a traffic flow. For example, this may involve enabling a reliability configuration for a QoS Flow, or for multiple QoS flows (e.g. in the case of redundant PDU Sessions or multiple UEs associated with the same endpoint).

Note that in some examples (i) and (ii) may occur simultaneously (e.g. because of URSP policy update in the UE).

For a case of two (or more) UEs associated with a same endpoint, the AF request for reliability may identify redundant UEs to the 5GS. In examples, this allows the PCF to send PDU Session Pair information to the SMF(s) and the 5GS (including the RAN) to allocate resources for those UEs accordingly. For example, the request for reliability may include information pertaining to two or more redundant user equipment in the communication system having a same endpoint. Alternatively, the request for reliability may include information pertaining to one user equipment that may communicate over a redundant path in one or more segments of the communication system.

Where a reliability level is requested by AF, in some examples the 5GS provides a mapping between reliability level and reliability features. That is, in some examples the 5GS maps each reliability feature to a reliability level.

3. AF requests event notifications

In some examples, an AF may request that it is sent an event notification when a reliability service being provided for an application can no longer be met by the 5GS, for example due to a failure that affects reliability. In some examples, events may be generated by the RAN or the 5GC. Events may, for example, include:

Failure of redundant radio path due to radio conditions on a path;

Failure of redundant radio path due to RAN failure (e.g.: gNB failure);

Failure of redundant path due to UE failure;

Failure of redundant path due to 5GS Network Node (UPF, SMF) failure;

Failure of redundant transmission on N3/N9

Additionally or alternatively, a specific failure event may be mapped by the 5GS to reliability levels. For example:

99.999% reliability reduced to 99.99% due to radio path conditions;

99.999% reliability reduced to 99.99% due to RAN failure.

Some examples will now be explained in more detail with respect to Figures 2 to 4.

Figure 2 shows an example procedure for exposure to an AF of reliability capability information of a 5GS. Figure 2 shows communication between AF 208, NEF 222 and PCF 230. In examples, the AF 208 may use this procedure to determine options for a subsequent request for reliability. For example, the subsequent request for reliability may comprise a request for a certain level of reliability (e.g. 99.999%).

At SI, the AF 208 sends a request for 5GS Reliability Capability. In this example, the request is sent to NEF 222. Therefore, SI may be considered communicating a request with the communication system. In this example, the request is in the form of an Nnef_ReliabilityCapability_Request. In some examples, the request comprises one or more required reliability parameters of the communication system for the application function. The reliability parameters may comprise one or more of: a reliability level; one or more reliability related features. In some examples the AF 208 includes in the request an Application Identifier which identifies an application to which the AF 208 relates. In some examples the request comprises one or more MAC (media access control) addresses, GPSIs or IP addresses of one or more devices. For example, the one or more devices may be one or more devices that provide the communication path for the application. The one or more devices may be using the application, or the application may be used by a device behind the UE.

At S2, the NEF 222 performs an authorization procedure of the AF 208, to check whether the request is allowed. If the authorization is not granted, S3 and S4 are skipped and the NEF 222 replies to the AF 208 with a result indication value “authorization failed”, or similar.

If authorization is granted, then the method proceeds to S3. At S3, the NEF 222 sends the reliability capability request to PCF 230. In some examples, the request comprises a Npcf_ReliabilityCapability_Request.

At S4, the PCF 230 provides a response to the NEF indicating the capability of the 5GS. Thus in some examples it may be considered that the AF is configured to communicate with the communication system to determine a reliability capability of the communication system. In some examples the response comprises a Npcf_ReliabilityCapability_Response. As explained previously, the response may include:

(i)- Support for a specific reliability levels (eg: 99.999% reliability). This provides an indication to the NEF 222 of the 5GS communication service reliability levels that can be offered to the AF.

(ii)- Support for specific reliability features such as:

• redundant paths via dual connectivity or CA

• redundant PDU sessions

• redundant transmission via PDCP duplication

• redundant transmission on N3/N9

• redundant paths using two (or more) UEs associated with the same endpoint

• a higher layer protocol such as FRER (802.1CB) or MPTCP for use with redundant paths This provides an indication to NEF 222 of features supported by the 5GS.

It is to be noted that in some examples additional signaling may be used by the PCF 230 to determine some capabilities (eg: PDCP duplication in the RAN).

At S5 the NEF responds to the AF with Reliability Capability information. In some examples the Reliability Capability information is sent in a Nnef_ReliabilityCapability_Response message.

In some examples a reliability capability is provided for each UE. In some examples the Reliability Capability information is for a specific application (identified by the AF) on a specific (unique)

UE. In some example, different applications on a same UE can experience different reliability levels (just as they can experience different QoS). Alternatively, the Reliability Capability information may be for all UEs or a group of UEs that are using the application.

In some examples, the response at S5 indicates that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters requested by the AF at SI. In some examples, the response indicating that a reliability configuration has been configured does not provide details of the reliability configuration (e.g. it could be a simple response indicating “success”). In some examples the response indicating that a reliability configuration has been configured additionally provides details of the reliability configuration (e.g. details of reliability features that have been activated). Then, the AF 208 (and 5GS) may then operate in accordance with the configured reliability configuration. According to some examples, causing the communication system to operate in accordance with the reliability configuration comprises triggering set-up of a high reliability configuration in the communication system, and /or triggering a new reliability configuration for one or more traffic flows.

Figure 3 shows an example procedure for AF 308 to request reliability and/or to request a notification when reliability criteria cannot be met.

As shown at SI, AF 308 sends a request to NEF 322 to reserve resources for reliability, and/or to receive reliability related event notifications for an AF session. By reserving resources, this may help ensure that a reliability requirement can be met. As shown in Figure 3, this request may be in the form Nnef_AFsessionWithReliability_Create_request.

At S2 the NEF 322 checks if the AF request is authorized. If the authorisation is not granted,

S3 and S4 are skipped and the NEF 322 replies to the AF 308 with a Result value indicating that the authorisation failed.

If the authorization is granted, then the procedure continues to S3.

At S3 the NEF 322 interacts with the PCF 330 by triggering a policy request. The policy request may be in the form Npcf_PolicyAuthorization_Create request. In some examples the policy request comprises one or more of: UE address(es); AF Identifier; Flow description(s); requested reliability.

At S4 the PCF 330 determines whether the requested reliability is authorized. As shown at S5, the PCF 330 notifies the NEF 322 whether or not the request is authorized.

For example, this may be in the form of an Npcf_PolicyAuthorization_Createresponse

If the request is authorized, the PCF 330 may determine a reliability configuration, and performs one or more actions. For example, the PCF may one or more of:

• Update a UE’s Route Selection Policy (URSP) by triggering the UE Configuration Update Procedure (see TS 23.502 clause 4.2A3) to send the UE policy container including UE policy information to the UE

• Alter packet handling by invoking the PCF initiated SM Policy Association Modification (see TS 23.502 clause 4.16.5.2) to provide the SMF with updated policy information (which may trigger a PDU Session modification and the sending of updated N2 SM information to the RAN).

• If PDU Session Pair information was provided by the AF to identify PDU Sessions of different UEs associated with a same endpoint, then the PCF 330 may include this in information sent to the SMF. The SMF may use the information to aid UPF selection and may inform the RAN (the RAN and the UPF may use the information to allocate resources with independent failure modes for the two UEs).

At S6, the NEF 322 sends a response message to the AF 308 indicating whether the request of SI is granted or not. For example, the message at S5 may be in the form of Nnef_AFsessionWithReliabilityCreateResponse.

If the AF 308 requested event notification related to reliability, then at S7 NEF 322 subscribes to the PCF 330 for the events. Subscription requests may be forwarded to other NFs or the RAN as needed for a reliability event.

At S8, when a reliability event condition is met, the PCF 330 sends a notification to the NEF 322 notifying the NEF 322 about the event. In some examples, this message is in the form Npcf_PolicyAuthorization_Notify message.

At S9, the NEF 322 sends a notification message with the event reported by the PCF 330 to the AF 308. In some examples, this message is in the form Nnef_AFsessionWithReliability_Notify.

Figure 4 shows a further example. Figure 4 shows signalling between a UE 402, RAN 406, AMF 412, PCF 430, UDM 418, UDR 432, NEF 422, and AF 408, where service specific information is provisioned in the 5GS. For example, the AF 408 provisions reliability information to the UDR 432 that may, for example, result in updating the URSP in the UE 402 so that the UE 402 will establish redundant PDU sessions.

As shown at SI, the AF 408 creates a request for service specific information related to reliability to be provisioned in the 5GS. To this end, in some examples the AF 408 invokes an Nnef_ServiceParameter_Create service operation. According to some examples, to update or remove an existing request, the AF 408 invokes an Nnef_ServiceParameter_Update or Nnef_ServiceParameter_Delete service operation together with a corresponding Transaction Reference ID which was provided to the AF in Nnef_ServiceParameter_Create response message.

In some examples, the content of the service operation (AF request at SI) includes reliability information requested by the AF (a reliability level or one or more specific reliability features).

As shown at S2, the AF 408 sends its request to the NEF 422. The NEF 422 may also carry out authorization of the AF request.

As shown at S3, where new service parameters are created or service parameters are updated (e.g. Nnef_ServiceParameter_Create or Update), the NEF 422 causes the UDR 432 to store the AF request information in the UDR as “Application Data”. Where one or more service parameters is being deleted (e.g. Nnef_ServiceParameter_delete), the NEF 422 causes the AF request information to be deleted from the UDR.

At S4, the NEF 422 responds to the AF 408. For example, this response may confirm that the UDR 432 has been updated. For example, the response may be in the form Nnef_ServiceParameter_Create or Nnef_ServiceParameter_delete.

According to some examples, if the UE 402 is registered to the network and the PCF 430 performs the subscription to notification to the data modified in the UDR by invoking Nudr_DM_Subscribe (AF service parameter provisioning information, SUPI, Data Set setting to "Application Data", Data Subset setting to "Service specific information") at SO, the following steps are performed:

At S5 the PCF(s) 430 receive(s) a notification of data change from the UDR 432 containing the information of the AF request for reliability. For example, the notification may be in the form Nudr_DM_Notify.

At S6 the PCF 430 initiates UE Policy delivery as specified in clause 4.2.4.3 of 3GPP TS23.502. The UE policy may contain a URSP that triggers setup of a redundant PDU session and directs duplicated traffic over the redundant session.

Figure 5 illustrates an example of a control apparatus 500 for controlling a function of the 5G-AN or the 5GC as illustrated in Figure 1. The control apparatus may comprise at least one random access memory (RAM) 51 la, at least one read only memory (ROM) 511b, at least one processor 512, 513 and an input/output interface 514. The at least one processor 512, 513 may be coupled to the RAM 511a and the ROM 511b. The at least one processor 512, 513 may be configured to execute an appropriate software code 515. The software code 515 may for example allow to perform one or more steps to perform one or more of the present aspects. The software code 515 may be stored in the ROM 511b. The control apparatus 500 may be interconnected with another control apparatus 500 controlling another function of the 5G-AN or the 5GC. In some examples, each function of the 5G-AN or the 5GC comprises a control apparatus 500. In alternative examples, two or more functions of the 5G-AN or the 5GC may share a control apparatus.

Figure 6 illustrates an example of a terminal 600, such as the terminal or UE 102 illustrated in Figure 1. The terminal 600 may be provided by any device capable of sending and receiving radio signals. Non-limiting examples comprise a user equipment, a mobile station (MS) or mobile device such as a mobile phone or what is known as a ’smart phone’, a computer provided with a wireless interface card or other wireless interface facility (e.g., USB dongle), a personal data assistant (PDA) or a tablet provided with wireless communication capabilities, a machine-type communications (MTC) device, a Cellular Internet of things (CIoT) device or any combinations of these or the like. The terminal 600 may provide, for example, communication of data for carrying communications. The communications may be one or more of voice, electronic mail (email), text message, multimedia, data, machine data and so on.

The terminal 600 may receive signals over an air or radio interface 607 via appropriate apparatus for receiving and may transmit signals via appropriate apparatus for transmitting radio signals. In Figure 6 transceiver apparatus is designated schematically by block 606. The transceiver apparatus 606 may be provided for example by means of a radio part and associated antenna arrangement. The antenna arrangement may be arranged internally or externally to the mobile device.

The terminal 600 may be provided with at least one processor 601, at least one memory ROM 602a, at least one RAM 602b and other possible components 603 for use in software and hardware aided execution of tasks it is designed to perform, including control of access to and communications with access systems and other communication devices. The at least one processor 601 is coupled to the ROM 602a and the RAM 602b. The at least one processor 601 may be configured to execute an appropriate software code 608. The software code 608 may for example allow to perform one or more of the present aspects. The software code 608 may be stored in the ROM 602a.

The processor, storage and other relevant control apparatus may be provided on an appropriate circuit board and/or in chipsets. This feature is denoted by reference 604. The device may optionally have a user interface such as keypad 605, touch sensitive screen or pad, combinations thereof or the like. Optionally one or more of a display, a speaker and a microphone may be provided depending on the type of the device.

Figure 7 is a flow-chart of a method according to an example. The flow chart of Figure 7 is viewed from the perspective of an apparatus. The apparatus may for example be a network apparatus. The apparatus may for example comprise an application function.

As shown at SI the method comprises hosting an application function for running an application in a communication system. At S2, the method comprises communicating a request with the communication system, the request comprising one or more required reliability parameters of the communication system for the application function.

At S3, the method comprises receiving a response from the communication system, the response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters.

At S4, the method comprises operating the application function in accordance with the reliability configuration.

Figure 8 is a flow-chart of a method according to an example. The flow chart of Figure 8 is viewed from the perspective of an apparatus. The apparatus may for example be a network apparatus. The apparatus may for example comprise a network exposure function or a policy control function.

As shown at SI, the method comprises receiving, from an application function, a request comprising one or more required reliability parameters of a communication system for the application function.

At S2, the method comprises responding to the request with a response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters.

At S3, the method comprises causing the communication system to operate in accordance with the reliability configuration.

Figure 9 shows a schematic representation of non-volatile memory media 900a (e.g. computer disc (CD) or digital versatile disc (DVD)) and 900b (e.g. universal serial bus (USB) memory stick) storing instructions and/or parameters 902 which when executed by a processor allow the processor to perform one or more of the steps of the method of Figure 7 and/or Figure 8.

It is noted that while the above describes example embodiments, there are several variations and modifications which may be made to the disclosed solution without departing from the scope of the present invention.

The examples may thus vary within the scope of the attached claims. In general, some embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although embodiments are not limited thereto. While various embodiments may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof. The examples may be implemented by computer software stored in a memory and executable by at least one data processor of the involved entities or by hardware, or by a combination of software and hardware. Further in this regard it should be noted that any procedures may represent program steps, or interconnected logic circuits, blocks and functions, or a combination of program steps and logic circuits, blocks and functions. The software may be stored on such physical media as memory chips, or memory blocks implemented within the processor, magnetic media such as hard disk or floppy disks, and optical media such as for example DVD and the data variants thereof, CD.

The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory. The data processors may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), application specific integrated circuits (ASIC), gate level circuits and processors based on multi core processor architecture, as non-limiting examples.

Alternatively, or additionally some examples may be implemented using circuitry. The circuitry may be configured to perform one or more of the functions and/or method steps previously described. That circuitry may be provided in the base station and/or in the communications device.

As used in this application, the term “circuitry” may refer to one or more or all of the following:

(a) hardware-only circuit implementations (such as implementations in only analogue and/or digital circuitry);

(b) combinations of hardware circuits and software, such as:

(i) a combination of analogue and/or digital hardware circuit(s) with software/firmware and

(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as the communications device or base station to perform the various functions previously described; and

(c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example integrated device.

The foregoing description has provided by way of exemplary and non-limiting examples a full and informative description of some embodiments However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings will still fall within the scope as defined in the appended claims.

Claims

1. An apparatus comprising means for performing: hosting an application function for running an application in a communication system; communicating a request with the communication system, the request comprising one or more required reliability parameters of the communication system for the application function; receiving a response from the communication system, the response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and operating the application function in accordance with the reliability configuration.

2. An apparatus according to claim 1, wherein the one or more reliability parameters comprise one or more of: a reliability level; one or more reliability related features.

3. An apparatus according to claim 1 or claim 2, wherein the communicating a request with the communication system comprises one or more of: sending information pertaining to two or more redundant user equipment in the communication system having a same endpoint; sending information pertaining to one user equipment that may communicate over a redundant path in one or more segments of the communication system.

4. An apparatus according to any of claims 1 to 3, wherein the means are further configured to perform communicating with the communication system to determine a reliability capability of the communication system.

5. An apparatus according to claim 4, wherein the determining a reliability capability of the communication system comprises determining one or more of: whether the communication system supports redundant paths via dual connectivity or carrier aggregation; whether the communication system supports redundant packet data unit sessions; whether the communication system supports redundant transmission via packet data convergence protocol duplication; whether the communication system supports redundant transmission on N3 and/or N9 interfaces; whether the communication system supports redundant paths using two or more user equipment having a same endpoint; whether the communication system supports higher layer protocol for use with redundant paths; whether the communication system supports one or more percentage reliability levels.

6. An apparatus according to claim 5, wherein the means are further configured to perform receiving and storing a mapping between the one or more reliability features and an indication of support for the one or more reliability features.

7. An apparatus according to any of claims 1 to 6, wherein the means are further configured to perform sending a request for a notification when one or more of the one or more required reliability parameters is not met.

8. An apparatus according to claim 7, wherein the means are further configured to perform receiving a notification of one or more of: a reliability level falling below a threshold value; failure of a redundant radio path due to radio conditions; failure of a redundant radio path due to radio access network failure; failure of a redundant path due to user equipment failure; failure of a redundant path due to failure of a node of the communication system; failure of a redundant path due to redundant transmission on N3 and/or N9 interface.

9. An apparatus according to any of claims 1 to 8, wherein the means are further configured to perform sending an identifier of the application function to the communication system, for authorization of the application function to receive the response that the reliability configuration has been configured.

10. An apparatus according to any of claims 1 to 9, wherein the means comprises at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

11. An apparatus comprising means for performing: receiving, from an application function, a request comprising one or more required reliability parameters of a communication system for the application function; responding to the request with a response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and causing the communication system to operate in accordance with the reliability configuration.

12. An apparatus according to claim 11, wherein the one or more reliability parameters comprises one or more of: a reliability level; one or more reliability related features.

13. An apparatus according to claim 11 or claim 12, wherein the means are further configured to perform receiving, from the application function, one or more of: information pertaining to two or more redundant user equipment in the communication system having a same endpoint; information pertaining to one user equipment that may communicate over a redundant path in one or more segments of the communication system.

14. An apparatus according to claim 13, wherein the means are further configured to perform, in response to the receiving information pertaining to two or more redundant user equipment in the network having a same endpoint, informing at least one node so that resources of the two or more redundant user equipment can be re-allocated.

15. An apparatus according to any of claims 11 to 14, wherein the causing the communication system to operate in accordance with the reliability configuration comprises triggering set-up of a high reliability configuration in the communication system.

16. An apparatus according to any of claims 11 to 15, wherein the causing the communication system to operate in accordance with the reliability configuration comprises triggering a new reliability configuration for one or more traffic flows.

17. An apparatus according to any of claims 11 to 16, wherein the means are further configured to perform indicating to the application function at least one of: whether the communication system supports redundant paths via dual connectivity or carrier aggregation; whether the communication system supports redundant packet data unit sessions; whether the communication system supports redundant transmission via packet data convergence protocol duplication; whether the communication system supports redundant transmission on N3 and/or N9 interfaces; whether the communication system supports redundant paths using two or more user equipment having a same endpoint; whether the communication system supports higher layer protocol for use with redundant paths; whether the communication system supports one or more percentage reliability levels.

18. An apparatus according to claim 17, wherein the means are further configured to perform sending to the application function a mapping between the one or more reliability features and an indication of support for the one or more reliability features.

19. An apparatus according to any of claims 11 to 18, wherein the means are further configured to perform receiving a request for a notification when one or more of the one or more required reliability parameters is not met.

20. An apparatus according to claim 19, wherein the means are further configured to perform sending a notification of one or more of: a reliability level falling below a threshold value; failure of a redundant radio path due to radio conditions; failure of a redundant radio path due to radio access network failure; failure of a redundant path due to user equipment failure; failure of a redundant path due to failure of a node of the communication system; failure of a redundant path due to redundant transmission on N3 and/or N9 interface.

21. An apparatus according to any of claims 11 to 19, wherein the means are further configured to perform receiving an identifier of the application function, and authorizing the application function to receive the response that the reliability configuration has been configured.

22. An apparatus according to any of claims 11 to 21, wherein the apparatus comprises one or more of: a network exposure function: a policy control function; a new network function.

23. An apparatus according to any of claims 11 to 22, wherein the means comprises at least one processor; and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

24. A method comprising: hosting an application function for running an application in a communication system; communicating a request with the communication system, the request comprising one or more required reliability parameters of the communication system for the application function; receiving a response from the communication system, the response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and operating the application function in accordance with the reliability configuration.

25. A method comprising: receiving, from an application function, a request comprising one or more required reliability parameters of a communication system for the application function; responding to the request with a response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and causing the communication system to operate in accordance with the reliability configuration.

26. A computer program comprising instructions for causing an apparatus to perform at least the following: hosting an application function for running an application in a communication system; communicating a request with the communication system, the request comprising one or more required reliability parameters of the communication system for the application function; receiving a response from the communication system, the response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and operating the application function in accordance with the reliability configuration.

27. A computer program comprising instructions for causing an apparatus to perform at least the following: receiving, from an application function, a request comprising one or more required reliability parameters of a communication system for the application function; responding to the request with a response indicating that a reliability configuration has been configured in the communication system to meet the one or more reliability parameters; and causing the communication system to operate in accordance with the reliability configuration.