CN114902718A - First, second and third network entities for obtaining an average active time period for a QoS level - Google Patents

Abstract

The present invention relates to obtaining an average activity period for a quality of service (QoS) level, where the average activity period represents a length of time that a QoS flow may be expected to remain active at the QoS level. The first network entity (100) requests and receives from the second network entity (300) at least one of: a set of active time periods for a QoS level and an average active time period for the QoS level, where an active time period is a time period for which a QoS flow is active at the QoS level. Based on the information received from the second network entity (300), the first network entity (100) derives an average active time period for the QoS level.

Description

First, second and third network entities for obtaining an average active time period for a QoS level

Technical Field

The present invention relates to a first network entity, a second network entity and a third network entity for obtaining an average activity period of a quality of service (QoS) level. The invention also relates to a corresponding method and a computer program.

Background

The QoS model of the 5G system has an appropriate mechanism to ensure that the QoS of a QoS flow is guaranteed. However, due to e.g. unexpected demand and radio damage, the pre-agreed QoS for a QoS flow cannot always be maintained throughout the lifetime of the QoS flow. In the case of non-Guaranteed Bit Rate (GBR) traffic, the pre-promised QoS may fluctuate dynamically through a mechanism called reflected QoS. On the other hand, in the case of GBR traffic, the radio access network may generate notification control for a next-generation core (NGC) when it is difficult to meet QoS requirements of QoS flows, and it is decided by the NGC where to handle the current QoS flow.

Disclosure of Invention

It is an object of embodiments of the present invention to provide a solution to reduce or solve the disadvantages and problems of conventional solutions.

The above and other objects are achieved by the subject matter of the independent claims. Further advantageous embodiments of the invention can be found in the dependent claims.

According to a first aspect of the present invention, the above and other objects are achieved with a first network entity for:

transmitting a first message to a second network entity, wherein the first message indicates a request for at least one of: a set of active time periods of a QoS level and an average active time period of the QoS level, wherein an active time period is a time period during which a QoS flow is active at the QoS level;

receiving a second message from the second network entity, wherein the second message indicates at least one of: a set of active time periods for the QoS class and an average active time period for the QoS class; and

deriving an average active time period for the QoS class from the second message.

The first network entity may send first messages to one or more second network entities and receive one or more second messages from the one or more second network entities. Thus, in an embodiment, the first network entity may derive the average activity time period based on input from more than one second network entity.

An advantage of the first network entity according to the first aspect is that the first network entity may obtain a metric indicating the length of time a QoS flow may be expected to remain active at the QoS level, sometimes referred to as the maintenance of a QoS level. The average active time period for a QoS level provides an indication in an easily interpretable format.

In an implementation of the first network entity according to the first aspect, the average active time period of the QoS level is based on a ratio between the set of active time periods and at least one of: QoS flow number, radio link failure number, handover failure number, and beam failure number.

An advantage of this implementation is that the number of radio link failures, the number of handover failures and/or the number of beam failures can be reflected in the average active period of the QoS level. For example, the greater the number of occurrences of radio link failure, handover failure, and/or beam failure, the lower the value of the average active time period for the QoS level. Therefore, the average active period of the QoS level can correctly reflect the maintenance of the QoS level.

In an implementation of the first network entity according to the first aspect, the second message further indicates at least one of: the number of QoS flows, the number of radio link failures, the number of handover failures, and the number of beam failures.

An advantage of this implementation is that the first network entity may derive the number of radio link failures, handover failures and/or beam failures that occurred from the second network entity.

In an implementation form of the first network entity according to the first aspect, at least one of the set of active time periods of the QoS level and the average active time period of the QoS level is associated with at least one of cell and Network Slice Selection Assistance Information (NSSAI).

An advantage of this implementation is that the average active time period for a QoS level can be derived for a particular cell and/or NSSAI. Thus, the first network entity may determine the QoS level retention for each cell and/or NSSAI.

In an implementation form of the first network entity according to the first aspect, the derived active time period of the QoS level is associated with at least one of the cell and the NSSAI.

An advantage of this implementation is that QoS level retention can be derived and provided for a particular cell and/or NSSAI.

In an implementation form of the first network entity according to the first aspect, the first network entity is a network data analysis function (NWDAF).

An advantage of this implementation is that existing functionality in the NWDAF is enhanced to obtain an average active period that indicates the length of time that a QoS flow may be expected to remain active at a QoS level.

According to a second aspect of the present invention, the above and other objects are achieved with a second network entity for:

receiving a first message from a first network entity, wherein the first message indicates at least one of a set of active time periods for a requested QoS level and an average active time period for the QoS level, wherein an active time period is a time period for which a QoS flow is active at the QoS level;

acquiring at least one of an active time period set of the QoS level and an average active time period of the QoS level;

transmitting a second message to the first network entity, wherein the second message indicates at least one of the set of active time periods for the QoS level and the average active time period for the QoS level.

According to said second aspect, the second network entity has the advantage that the second network entity can acquire and exchange information related to the active time periods of the QoS levels. Thereby, retention of determining the QoS level is supported.

According to the second aspect, in an implementation manner of the second network entity, the obtaining the set of active time periods of the QoS class includes:

an activity time period of at least one QoS flow active at the QoS level is measured.

An advantage of this implementation is that the active time period at the QoS level for each QoS flow can be determined in the second network entity.

According to the second aspect, in an implementation manner of the second network entity, the obtaining the set of active time periods of the QoS class includes:

an activity time period of at least one QoS flow active at the QoS level is measured based on at least one of a timer and a time window.

An advantage of this implementation is that the active time period of the QoS level can be determined in the second network entity using known methods.

According to the second aspect, in an implementation manner of the second network entity, the obtaining the set of active time periods of the QoS class includes:

sending a third message to a third network entity, wherein the third message indicates a set of active time periods for which the QoS level is requested;

receiving a fourth message from the third network entity, wherein the fourth message indicates a set of active time periods for the QoS level.

An advantage of this implementation is that different entities may participate in the active time period determining the QoS level, thereby providing a flexible and robust solution.

According to the second aspect, in an implementation manner of the second network entity, the obtaining the average active time period of the QoS class includes:

calculating an average active time period for the QoS level based on the set of active time periods for the QoS level and according to at least one of a QoS flow number, a radio link failure number, a switch failure number, and a beam failure number.

An advantage of this implementation is that the number of radio link failures, the number of handover failures and/or the number of beam failures can be reflected in the average active period of the QoS level. For example, the greater the number of occurrences of radio link failure, handover failure, and/or beam failure, the lower the value of the average active time period for the QoS level. Therefore, the average active period of the QoS level can correctly reflect the maintenance of the QoS level.

According to the second aspect, in an implementation form of a second network entity, at least one of the set of active time periods of the QoS level and the average active time period of the QoS level is associated with at least one of a cell and an NSSAI.

An advantage of this implementation is that the first network entity may determine the QoS level retention for each cell and/or NSSAI.

According to the second aspect, in an implementation of the second network entity, the second network entity is a Session Management Function (SMF), an access and mobility management function (AMF) or an operation, administration and maintenance (OAM) function.

An advantage of this implementation is that existing functionality in the SMF, AMF or OAM is enhanced, thereby enabling the SMF, AMF or OAM to acquire and exchange information relating to the active time periods of the QoS levels.

According to a third aspect of the present invention, the above and other objects are achieved with a third network entity for:

receiving a third message from a second network entity, wherein the third message indicates a set of active time periods for requesting a QoS level, wherein an active time period is a time period for which a QoS flow is active at the QoS level;

acquiring an active time period set of the QoS level;

transmitting a fourth message to the second network entity, wherein the fourth message indicates the acquired set of active time periods for the QoS level.

According to the third aspect, it is an advantage of the third network entity that the third network entity is also involved in determining the active time period of the QoS level. Thereby, the solution is made more flexible and robust.

According to the third aspect, in an implementation manner of a third network entity, the obtaining the set of active time periods for the QoS class includes:

an activity period of at least one QoS flow active at the QoS level is measured.

An advantage of this implementation is that the active time period of the QoS class can be determined in the third network entity by considering each QoS flow.

According to the third aspect, in an implementation manner of a third network entity, the obtaining the set of active time periods for the QoS class includes:

an activity time period of at least one QoS flow active at the QoS level is measured based on at least one of a timer and a time window.

An advantage of this implementation is that the active time period of the QoS level can be determined in the third network entity using known methods.

According to the third aspect, in an implementation form of a third network entity, the set of active time periods of the QoS level is associated with at least one of a cell and an NSSAI.

An advantage of this implementation is that the third network entity may provide information related to the active time period, which makes it possible to determine the maintenance of the QoS level of each cell or NSSAI.

In an implementation form of the third network entity according to the third aspect, the third network entity is a client device or a network access node.

An advantage of this implementation is that existing functionality in the client device or network access node is enhanced to obtain and exchange information relating to the active time periods of the QoS levels.

According to a fourth aspect of the present invention, the above and other objects are fulfilled by a method for a first network entity, the method comprising:

transmitting a first message to a second network entity, wherein the first message indicates a request for at least one of: a set of active time periods of a QoS level and an average active time period of the QoS level, wherein an active time period is a time period during which a QoS flow is active at the QoS level;

receiving a second message from the second network entity, wherein the second message indicates at least one of: a set of active time periods for the QoS class and an average active time period for the QoS class;

deriving an average active time period for the QoS class from the second message.

The method according to the fourth aspect may be extended to implementations corresponding to the implementations of the first network entity according to the first aspect. Accordingly, implementations of the method include one or more features of corresponding implementations of the first network entity.

The advantages of the method according to the fourth aspect are the same as the advantages of the corresponding implementation of the first network entity according to the first aspect.

According to a fifth aspect of the present invention, the above and other objects are fulfilled by a method for a second network entity, the method comprising:

receiving a first message from a first network entity, wherein the first message indicates at least one of a set of active time periods for a requested QoS level and an average active time period for the QoS level, wherein an active time period is a time period for which a QoS flow is active at the QoS level;

acquiring at least one of an active time period set of the QoS level and an average active time period of the QoS level;

transmitting a second message to the first network entity, wherein the second message indicates at least one of the set of active time periods for the QoS level and the average active time period for the QoS level.

The method according to the fifth aspect may be extended to implementations corresponding to the implementations of the second network entity according to the second aspect. Accordingly, implementations of the method include one or more features of a corresponding implementation of the second network entity.

The advantages of the method according to the fifth aspect are the same as the advantages of the corresponding implementation of the second network entity according to the second aspect.

According to a sixth aspect of the present invention, the above and other objects are fulfilled by a method for a third network entity, the method comprising:

receiving a third message from a second network entity, wherein the third message indicates a set of active time periods for requesting a QoS level, wherein an active time period is a time period for which a QoS flow is active at the QoS level;

acquiring an active time period set of the QoS level;

transmitting a fourth message to the second network entity, wherein the fourth message indicates the acquired set of active time periods for the QoS level.

The method according to the sixth aspect may be extended to implementations corresponding to the implementations of the third network entity according to the third aspect. Accordingly, implementations of the method include one or more features of corresponding implementations of the third network entity.

The advantages of the method according to the sixth aspect are the same as the advantages of the corresponding implementation of the third network entity according to the third aspect.

The invention also relates to a computer program, characterized in that the program code, when executed by at least one processor, causes the at least one processor to perform any of the methods according to embodiments of the invention. Furthermore, the invention relates to a computer program product comprising a computer readable medium and the computer program, wherein the computer program is comprised in the computer readable medium and comprises one or more of the group of: Read-Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), flash Memory, Electrically EPROM (EEPROM), and a hard disk drive.

Further applications and advantages of embodiments of the present invention will become apparent from the following detailed description.

Drawings

The drawings are intended to illustrate and explain various embodiments of the present invention. In the drawings:

fig. 1 shows a first network entity according to an embodiment of the invention;

fig. 2 shows a method for a first network entity according to an embodiment of the invention;

fig. 3 shows a second network entity according to an embodiment of the invention;

fig. 4 shows a method for a second network entity according to an embodiment of the invention;

fig. 5 shows a third network entity according to an embodiment of the invention;

fig. 6 shows a method for a third network entity according to an embodiment of the invention;

fig. 7 illustrates signaling between a first network entity and a second network entity according to an embodiment of the invention;

fig. 8 shows signaling between a second network entity and a third network entity according to an embodiment of the invention.

Detailed Description

Although the basic mechanism of alerting User Equipment (UE) whenever the QoS of a PDU session drops below a pre-agreed performance level is standardized in the Rel-16 time frame in 3GPP, the 5G system does not know how long the PDU session can be expected to last at the pre-agreed QoS when accepting a new PDU session. The length of time that the network is expected to achieve the pre-agreed QoS for a QoS flow is sometimes referred to as the QoS flow's retention.

In view of the inherent characteristics of packet-switched based 5G systems, it is desirable to measure how long a communication session can be maintained at a pre-agreed QoS level within a specific location or time, so that the measurement results can clearly and easily indicate/reflect/indicate the maintenance.

The 3GPP introduced a Key Performance Indicator (KPI) that shows how often an end user abnormally loses a QoS flow during its use. The retention KPI is measured in terms of the number of QoS flows in the buffer for which data is abnormally released and is normalized using the number of data session time units. One problem with this measure is that it mixes the number of times the release occurred with the session time, so the interpretation of the resulting value is not intuitive. Furthermore, the retention of any cellular network due to congestion depends on Radio Access Network (RAN) resources, as RAN is a bottleneck in the network. Therefore, it is more appropriate if the maintenance related measurements are made from the UE, RAN and Session Management Function (SMF).

According to one proposal, the measured KPIs are defined as the in-session activity time of a QoS flow. The measurement provides the cumulative active session time for the QoS flow in the cell. Alternatively, an in-session active time for the UE is defined, which provides an accumulated active session time for the UE in the cell. The measurement KPIs are divided into sub-counters for each QoS level. This measurement does not indicate whether the session is inactive due to lack of resources or lack of application data and therefore does not reflect the network's ability to meet the QoS requirements of the UE. The measure of retention must truly reflect network problems, and the way in which the QoS flow and the active time in the session of the UE are calculated does not enable this distinction.

According to embodiments of the present invention, an average active time period for a QoS level is introduced that reflects the network's ability to meet the QoS requirements of the UE by indicating the time period during which a QoS flow may be expected to remain active at the QoS level.

Fig. 1 shows a first network entity 100 according to an embodiment of the invention. In the embodiment shown in fig. 1, the first network entity 100 comprises a processor 102, a transceiver 104 and a memory 106. The processor 102 is coupled to the transceiver 104 and the memory 106 by a communication device 108 as is known in the art. The first network entity 100 may be configured for wireless communication and wired communication in a wireless communication system and a wired communication system, respectively. Wireless communication capabilities may be provided through an antenna or antenna array 110 coupled to the transceiver 104, while wired communication capabilities may be provided through a wired communication interface 112 coupled to the transceiver 104.

In the present invention, the first network entity 100 being configured to perform certain actions may be understood to mean that the first network entity 100 comprises suitable means, such as a processor 102 and a transceiver 104, for performing said actions.

According to an embodiment of the present invention, the first network entity 100 is configured to send a first message 510 to the second network entity 300, wherein the first message 510 indicates a request for at least one of: a set of active time periods for a QoS level and an average active time period for the QoS level, wherein an active time period is a time period for which a QoS flow is active at the QoS level. The first network entity 100 is further configured to receive a second message 520 from the second network entity 300, wherein the second message 520 indicates at least one of: the set of active time periods of the QoS level and the average active time period of the QoS level and is used to derive the average active time period of the QoS level from the second message 520.

Fig. 2 shows a flow chart of a corresponding method 200 that may be performed in the first network entity 100 shown in fig. 1, for example. The method 200 comprises sending 202 a first message 510 to a second network entity 300, wherein the first message 510 indicates a request for at least one of: a set of active time periods for a QoS level and an average active time period for the QoS level, wherein an active time period is a time period for which a QoS flow is active at the QoS level. The method 200 further comprises: receiving 204 a second message 520 from the second network entity 300, wherein the second message 520 indicates at least one of: a set of active time periods for the QoS class and an average active time period for the QoS class; and deriving 206 an average active time period for the QoS level from the second message 520.

Fig. 3 shows a second network entity 300 according to an embodiment of the invention. In the embodiment shown in fig. 3, the second network entity 300 comprises a processor 302, a transceiver 304 and a memory 306. The processor 302 is coupled to the transceiver 304 and the memory 306 by a communication device 308 as is known in the art. The second network entity 300 may be configured for wireless communication and wired communication in a wireless communication system and a wired communication system, respectively. Wireless communication capabilities may be provided through an antenna or antenna array 310 coupled to the transceiver 304, while wired communication capabilities may be provided through a wired communication interface 312 coupled to the transceiver 304.

In the present invention, the use of the second network entity 300 for performing certain actions may be understood to mean that the second network entity 300 comprises suitable means, such as a processor 302 and a transceiver 304, for performing said actions.

According to an embodiment of the present invention, the second network entity 300 is configured to receive a first message 510 from the first network entity 100, wherein the first message 510 indicates at least one of a set of active time periods requesting a QoS level and an average active time period of the QoS level, wherein an active time period is a time period during which a QoS flow is active at the QoS level; the second network entity 300 is further configured to obtain at least one of the set of active time periods of the QoS level and the average active time period of the QoS level, and send a second message 520 to the first network entity 100, wherein the second message 520 indicates at least one of the set of active time periods of the QoS level and the average active time period of the QoS level.

Fig. 4 shows a flow chart of a corresponding method 400 that may be performed in the second network entity 300, e.g. shown in fig. 3. The method 400 comprises receiving 402 a first message 510 from a first network entity 100, wherein the first message 510 indicates at least one of a set of active time periods for requesting a QoS level and an average active time period for the QoS level, wherein an active time period is a time period during which a QoS flow is active at the QoS level. The method 400 further comprises obtaining 404 at least one of the set of active time periods of the QoS level and the average active time period of the QoS level and sending 406 a second message 520 to the first network entity 100, wherein the second message 520 indicates at least one of the set of active time periods of the QoS level and the average active time period of the QoS level.

Fig. 5 shows a third network entity 500 according to an embodiment of the invention. In the embodiment shown in fig. 5, the third network entity 500 comprises a processor 502, a transceiver 504 and a memory 506. The processor 502 is coupled to the transceiver 504 and the memory 506 through a communication device 508 as is known in the art. The third network entity 500 may be configured for wireless communication and wired communication in a wireless communication system and a wired communication system, respectively. Wireless communication capabilities may be provided through an antenna or antenna array 510 coupled to the transceiver 504, while wired communication capabilities may be provided through a wired communication interface 512 coupled to the transceiver 504.

In the present invention, the use of the third network entity 500 for performing certain actions is to be understood as meaning that the third network entity 500 comprises suitable means, such as a processor 502 and a transceiver 504, for performing said actions.

According to an embodiment of the present invention, the third network entity 500 is configured to receive a third message 530 from the second network entity 300, wherein the third message 530 indicates a set of active time periods requesting a QoS level, wherein an active time period is a time period during which a QoS flow is active at the QoS level. The third network entity 500 is further configured to obtain a set of active time periods for the QoS class and send a fourth message 540 to the second network entity 300, wherein the fourth message 540 indicates the obtained set of active time periods for the QoS class.

Fig. 6 shows a flow chart of a corresponding method 600 that may be performed in the third network entity 500, e.g. shown in fig. 5. The method 600 comprises receiving 602 a third message 530 from the second network entity 300, wherein the third message 530 indicates a set of active time periods for requesting a QoS level, wherein an active time period is a time period for which a QoS flow is active at the QoS level. The method 600 further comprises obtaining 604 a set of active time periods for the QoS level and sending 606 a fourth message 540 to the second network entity 300, wherein the fourth message 540 indicates the obtained set of active time periods for the QoS level.

Fig. 7 illustrates signaling between the first network entity 100 and the second network entity 300 for exchanging information associated with an active time period of a QoS level according to an embodiment of the present invention. In an embodiment, the first network entity 100 may be a network data analysis function (NWDAF), and the second network entity 300 may be a Session Management Function (SMF), an Access and Management Function (AMF), or an operation, administration, and maintenance (OAM) function.

In step I of fig. 7, the first network entity 100 sends a first message 510 to the second network entity 300. The first message 510 indicates a request for at least one of: a set of active time periods for a QoS class and an average active time period for a QoS class. Each active time period in the set of active time periods is a time period in which the QoS flow is active at the QoS level. A QoS level may correspond to a set of QoS requirements including QoS parameters and/or QoS characteristics. In an embodiment, a QoS level may be defined by a 5G QoS identifier (5G QoS identifier, 5 QI).

The first network entity 100 may send a first message 510 to the second network entity 300 to acquire or subscribe to information associated with an active time period of a QoS level. Accordingly, the first message 510 may be a request to obtain information associated with an active time period of a QoS level. However, the first message 510 may also be a request to subscribe to information associated with an active time period of a QoS level. In the latter case, the first message 510 may trigger monitoring of information associated with the active time period of the QoS level in the second network entity 300 and reporting of these information to the first network entity 100 at predetermined intervals.

In embodiments where the first network entity 100 is an NWDAF and the second network entity 300 is an SMF, AMF, or OAM, the first message 510 may correspond to an Nsmf _ EventExposure _ Subscribe message or a Namf _ EventExposure _ Subscribe message according to the 3GPP standards, as well as one or more additional information elements.

The second network entity 300 receives the first message 510 from the first network entity 100 and thus receives a request for at least one of a set of active time periods of a QoS level and an average active time period of a QoS level. In step II of fig. 7, based on the received first message 510, the second network entity 300 obtains at least one of a set of active time periods of the QoS level and an average active time period of the QoS level. The second network entity 300 may obtain at least one of the set of activity time periods of the QoS level and the average activity time period of the QoS level based on measurements in the second network entity 300 and/or based on measurements obtained from a further network entity (e.g. the third network entity 500).

When the first message 510 indicates that a set of active time periods of a QoS level is requested, the second network entity 300 may obtain the set of active time periods of the QoS level based on the measurement results in the second network entity 300. The second network entity 300 may obtain the set of active time periods for the QoS level by measuring active time periods for at least one QoS flow active at the QoS level. The second network entity 300 may measure the activity time period for each QoS flow that is active at the QoS level in the second network entity 300 or that is active in a further entity that reports to the second network entity 300. Thus, the set of active time periods for a QoS class may include the active time periods for each active QoS flow at the QoS class. The second network entity 300 may also measure an activity period of each QoS flow active at the QoS level in the cell and/or in Network Slice Selection Assistance Information (NSSAI), such that a set of active periods of the QoS level is associated with at least one of the cell and the NSSAI, as described further below.

In an embodiment, the second network entity 300 may measure an activity period of at least one QoS flow active at the QoS level based on at least one of a timer and a time window. The timer may be a timer that measures the time a QoS flow with a particular QoS level (e.g., a particular 5QI) has been active and may begin when the QoS flow is started or moved to a particular QoS level. The timer may stop when the QoS flow is interrupted, for example due to radio link failure, handover failure or beam failure. The timer may also stop if the QoS is modified such that it is no longer at the same QoS level, i.e. moved to a different QoS level. The time window may be a sliding time window defining a time period during which an active time period of at least one QoS flow active at the QoS level is to be measured. The timer may be triggered per QoS level for each QoS flow such that multiple timers are active for a particular QoS level. Thus, the set of active time periods for a QoS level may be measured based on the number of timers for the QoS level.

The second network entity 300 may also obtain the set of active time periods for the QoS level from the third network entity 500 with a request for the set of active time periods for the QoS level from the third network entity 500. Further details regarding the signaling of the set of active time periods for exchanging QoS levels between the second network entity 300 and the third network entity 500 will be described below with reference to fig. 8.

When the first message 510 indicates that an average active time period of a QoS level is requested, the second network entity 300 may obtain the average active time period of the QoS level based on the set of active time periods of the QoS level. The set of active time periods of the QoS level may be obtained as described above, i.e. based on measurements in the second network entity 300 and/or based on the set of active time periods of the QoS level received from the third network entity 500.

The second network entity 300 may obtain the average active time period of the QoS class by calculating the average active time period of the QoS class based on the set of active time periods of the QoS class and according to at least one of the number of QoS flows, the number of radio link failures, the number of handover failures and the number of beam failures. At least one of the number of QoS flows, the number of radio link failures, the number of handover failures and the number of beam failures may be obtained from measurements in the second network entity 300 or from another network entity, such as the third network entity 500. The average active time period of the QoS class may be a ratio between a set of active time periods of the QoS class and at least one of a number of QoS flows, a number of radio link failures, a number of handover failures, and a number of beam failures.

In step III of fig. 7, the second network entity 300 sends a second message 520 to the first network entity 100. The second message 520 indicates at least one of the set of active time periods of the QoS level and the average active time period of the QoS level acquired by the second network entity 300 in step II of fig. 7.

In embodiments where the first network entity 100 is an NWDAF and the second network entity 300 is an SMF, AMF or OAM, the second message 520 may correspond to an Nsmf _ EventExposure _ Notify message or an Nsmf _ EventExposure _ Notify message according to the 3GPP standards, and one or more additional information elements.

The first network entity 100 receives the second message 520 from the second network entity 300 and thus obtains at least one of the set of active time periods of the QoS level and the average active time period of the QoS level indicated in the second message 520.

In step IV of fig. 7, the first network entity 100 derives the average active time period of the QoS level based on the received second message 520. Thus, the first network entity 100 may derive the average active time period for the QoS level based on at least one of the set of active time periods for the QoS level and the average active time period for the QoS level indicated in the second message 520. The second message 520 may include other information that may also be used to derive an average activity period. The derived average active time period for a QoS level is a measure of the length of time that a QoS flow is expected to remain active at the QoS level and therefore may be used to indicate the likelihood that an enabled QoS flow at the QoS level may remain active at that QoS level.

In an embodiment, when a Packet Data Unit (PDU) session is to be established, the first network entity 100 may provide the derived average activity period of the QoS level to other network entities, such as an Application Function (AF) or a client application running in the client device. The AF or client application may use the derived average activity period for the QoS level as input to the determination function/algorithm. In the case of, for example, vehicle-to-anything (V2X) applications, the resulting average activity period for a QoS level may help the AF switch to a physical path with higher retention at the required QoS level.

In an embodiment, the average active time period of the QoS level is based on a ratio between a set of active time periods of the QoS level and at least one of: QoS flow number, radio link failure number, handover failure number, and beam failure number. At least one of the number of QoS flows, the number of radio link failures, the number of handover failures and the number of beam failures may be obtained from the second network entity 300 or from a further network entity, e.g. in the second message 520. Thus, in an embodiment, the second message 520 may also indicate at least one of: QoS flow number, radio link failure number, switching failure number, and beam failure number. However, this information may be received in another message or retrieved from another network entity or database.

In an embodiment, the first network entity 100 may derive the average activity period based on the following equation:

where 5QIx is the QoS level, Σ, to be calculated for the average activity period _i The active time period 5QIx is the sum of i active time periods in the set of active time periods for 5QIx, totnbrqqsflo 5QI _x Is the total number of QoS flows of 5QIx, totalnbrrlfs, hofs bfs is the total number of radio link failures, handover failures and beam failures.

The average activity period may be derived based on a sliding time window defining the period of time over which the average period is to be calculated. This is similar to a moving average (rolling or sliding) which is a calculation that analyzes data points by creating a series of averages for different subsets of the complete data set. By having a sliding time window, the goal is to time average a random or arbitrary time variable over different moving time windows.

When the second message 520 indicates an average active time period of a QoS level, the first network entity 100 may derive the average active time period of the QoS level based on the received average active time period of the QoS level. The derived average activity time period for the QoS level may for example correspond to the average activity time period for the QoS level received in the second message 520 or be a function of the average activity time periods for the QoS levels received in one or more second messages 520 from one or more second network entities 300 for the same QoS level. In this way, the first network entity 100 may derive the activity time periods for one or more QoS levels based on input from one or more second network entities 300.

According to an embodiment of the invention, at least one of the set of active time periods of the QoS level and the average active time period of the QoS level is associated with at least one of a cell and an NSSAI. In these embodiments, the first network entity 100 may request and receive a set of active time periods of QoS levels and/or an average active time period of QoS levels for a particular cell and/or NSSAI. A cell may be identified, for example, by a Physical Cell Identifier (PCI), an NR Cell Global Identifier (NCGI), an E-UTRAN cell global identifier (ECGI). The first network entity 100 may also derive an average active time period for a particular cell and/or NSSAI. Thus, in an embodiment, the resulting average activity period for the QoS level may be associated with at least one of a cell and NSSAI. Thus, the derived activity time period may indicate an expected time in a cell and/or NSSAI at which a QoS flow may remain active at a QoS level.

In the embodiment described with reference to fig. 7, the first network entity 100 requests information associated with the activity time period from a second network entity 300 and receives a second message 520. However, in an embodiment, the first network entity 100 may request and receive information associated with the active time period from more than one second network entity 300 and further receive one or more second messages 520 from each second network entity 300.

The first network entity 100 may derive the average active time period for the QoS level based on part or all of the information received from more than one second network entity 300. For example, the first network entity 100 may receive a plurality of average activity time periods of a QoS level from a different second network entity 300 and derive an average activity time period of the QoS level based on the received plurality of average activity time periods. The derived average active time period for the QoS level may be, for example, an average or mean of a number of average active time periods received. Furthermore, the first network entity 100 may for example receive a set of active time periods from each second network entity 300 serving a cell and derive an average active time period for a QoS level based on the received set of active time periods and further derive an average active time period for the QoS level of the cell.

Fig. 8 illustrates the signaling of a set of active time periods for exchanging QoS levels between the second network entity 300 and the third network entity 500 according to an embodiment of the present invention. In an embodiment, the second network entity 300 may be an SMF, an AMF, or an OAM, and the third network entity 500 may be a client device or a network access node, such as a cell or a next generation node B (gNB).

In step I of fig. 8, the second network entity 300 sends a third message 530 to the third network entity 500. The third message 530 indicates a set of active time periods for which a QoS level is requested.

When the second network entity 300 receives the first message 510 from the first network entity 100, the second network entity 300 may send a third message 530. The second network entity 300 may further send a third message 530 when the second network entity 300 receives an indication that the third network entity 500 is initiating a PDU session. In an embodiment, the third message 530 may correspond to a non-access stratum (NAS) configuration message (e.g., a NAS transport message according to the 3GPP standard), and one or more additional information elements. For example, when exchanging between the AMF and the UE.

The third network entity 500 receives the third message 530 from the second network entity 300 and thus receives a request for a set of active time periods for a QoS level. In step II of fig. 8, the third network entity 500 obtains a set of active time periods for the QoS level based on the third message 530. The third network entity 500 may obtain the set of active time periods for the QoS level by measuring active time periods for at least one QoS flow active at the QoS level. This may be achieved, for example, by measuring in the third network entity 500 the activity time period of each QoS flow active at the QoS level. Thus, the set of active time periods of the QoS level may comprise the active time periods of each QoS flow active at the QoS level in the third network entity 500.

In an embodiment, the third network entity 500 may measure an activity time period of at least one QoS flow active at the QoS level based on at least one of a timer and a time window. This occurs in the same way as described above for the second network entity 300 with reference to step II in fig. 7.

According to an embodiment of the present invention, the third network entity 500 may further calculate an average active time period of the QoS class based on the acquired set of active time periods of the QoS class. The third network entity 500 may calculate the average activity time period for the QoS level in the same way as described above for the second network entity 300 with reference to step II in fig. 7. In embodiments where the third network entity 500 calculates the average active time period for the QoS level, the third message 530 may also indicate the average active time period for the requested QoS level.

As previously described, the set of active time periods and/or the average time period of the QoS level may be associated with at least one of a cell and an NSSAI. In this case, the third network entity 500 may further acquire the set of active time periods of the QoS level based on the cell and/or NSSAI. Thus, in an embodiment, the active time period is obtained for a QoS flow in a particular cell and/or NSSAI.

In step III of fig. 8, the third network entity 500 sends a fourth message 540 to the second network entity 300. The fourth message 540 indicates the set of active time periods for the acquired QoS level and/or the average time period for the acquired QoS level. The second network entity 300 receives the fourth message 540 from the third network entity 500 and thus obtains the set of active time periods of the indicated QoS level and/or the average time period of the indicated QoS level. Upon receiving the set of active time periods of the obtained QoS level and/or the average time period of the obtained QoS level, the second network entity 300 may forward the set of active time periods of the obtained QoS level and/or the average time period of the obtained QoS level to the first network entity 100 without modification or use the set of active time periods of the obtained QoS level and/or the average time period to derive/calculate, for example, an average active time period, as described above with reference to step II in fig. 7. The second network entity 300 may derive the average activity time period based on input from one or more third network entities 500. Similarly, the first network entity 100 may derive the average activity time period based on input from one or more of the second network entity 300 and/or the third network entity 500.

The first network entity 100 herein may be denoted as a network data analysis function (NWDAF). The NWDAF may be a function configured for communication in 3 GPP-related LTE and LTE-Advanced, in WiMAX and its evolution, and in fifth generation wireless technologies such as New Radio (NR). The NWDAF may be a function configured for communication in accordance with TS 23.288 of 3 GPP.

The second network entity 300 herein may be denoted as a Session Management Function (SMF), an Access and Management Function (AMF) or an OAM. The SMF, AMF, or OAM may be a function configured for communication in 3 GPP-related LTE and LTE-Advanced, in WiMAX and its evolution, and in fifth generation wireless technologies such as New Radio (NR).

The third network entity 500 herein may represent a client device or a network access node. The client devices, which may in turn be referred to as User Equipment (UE), mobile stations, internet of things (IoT) devices, sensor devices, wireless terminals, and/or mobile terminals, are capable of wireless communication in a wireless communication system (also sometimes referred to as a cellular radio system). The UE may also be referred to as a mobile phone, a cellular phone, a computer tablet or a laptop with wireless functionality. In this context, a UE may be, for example, a portable, pocket-storage, hand-held, computer-included, or vehicle-mounted mobile device capable of communicating voice and/or data with another entity (e.g., another receiver or server) via a radio access network. The UE may be a Station (STA), which is any device that includes IEEE 802.11 compliant Media Access Control (MAC) and Physical Layer (PHY) interfaces to the Wireless Medium (WM). The UE may also be configured for communication in 3 GPP-related LTE and LTE-Advanced, in WiMAX and its evolution, and in fifth generation wireless technologies such as new radios.

The network access node may in turn be denoted as a Radio network access node, access point, or Base Station, e.g. a Radio Base Station (RBS), which in some networks may be referred to as transmitter, "gNB", "gdnodeb", "eNB", "eNodeB", "NodeB" or "B node", depending on the technology and terminology used. Depending on the transmission power and thus also on the cell size, the radio network access nodes may be of different classes, e.g. macro eNodeB, home eNodeB or pico base station. A radio network Access node may be a Station (STA), which is any device that includes IEEE 802.11 compliant Media Access Control (MAC) and Physical Layer (PHY) interfaces to the Wireless Medium (WM). The radio network access node may also be a base station corresponding to a fifth generation (5G) wireless system. The radio network access node herein may also be denoted as a road side unit, e.g. in V2X applications. The roadside units may be any devices/nodes deployed along a road to improve vehicle network performance and extend coverage. The road side unit may be a stand-alone device/node or may be integrated with, for example, a network access node.

Furthermore, any of the methods according to embodiments of the invention may be implemented in a computer program with a codec unit, which when run by a processing apparatus, causes the processing apparatus to perform the method steps. The computer program is embodied in a computer readable medium of a computer program product. The computer-readable medium may include substantially any Memory, such as a Read-Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable PROM (EPROM), a flash Memory, an Electrically Erasable PROM (EEPROM), or a hard drive.

Furthermore, the skilled person realizes that embodiments of the first network entity 100, the second network entity 300 and the third network entity 500 comprise necessary communication capabilities in the form of, for example, functions, devices, units, elements, etc. for performing the scheme. Examples of other such devices, units, elements and functions include: processors, memories, buffers, control logic, encoders, decoders, rate matchers, de-rate matchers, mapping units, multipliers, decision units, selection units, switches, interleavers, de-interleavers, modulators, demodulators, inputs, outputs, antennas, amplifiers, receiver units, transmitter units, DSPs, MSDs, TCM encoders, TCM decoders, power supply units, power feeders, communication interfaces, communication protocols, etc., suitably arranged together to implement a scheme.

In particular, the one or more processors of first network entity 100, second network entity 300, and third network entity 500 may include, for example, one or more instances of a Central Processing Unit (CPU), a Processing Unit, a Processing Circuit, a processor, an Application Specific Integrated Circuit (ASIC), a microprocessor, or other Processing logic that may interpret and execute instructions. The expression "processor" may thus denote processing circuitry comprising a plurality of processing circuits, such as any, some or all of the above-listed items. The processing circuitry may also perform data processing functions for inputting, outputting, and processing data, including data buffering and device control functions, such as call processing control, user interface control, and the like.

Finally, it is to be understood that the invention is not limited to the embodiments described above, but that it also relates to and encompasses all embodiments within the scope of the appended independent claims.

Claims (15)

1. A first network entity (100) configured to:

sending a first message (510) to a second network entity (300), wherein the first message (510) indicates a request for at least one of: a set of active time periods of a QoS level and an average active time period of the QoS level, wherein an active time period is a time period during which a QoS flow is active at the QoS level;

receiving a second message (520) from the second network entity (300), wherein the second message (520) indicates at least one of: a set of active time periods for the QoS class and an average active time period for the QoS class; and

deriving an average active time period for the QoS level from the second message (520).

2. The first network entity (100) of claim 1, wherein the average active time period of the QoS level is based on a ratio between the set of active time periods and at least one of: QoS flow number, radio link failure number, switching failure number, and beam failure number.

3. The first network entity (100) of claim 2, wherein the second message (520) further indicates at least one of: the number of QoS flows, the number of radio link failures, the number of handover failures, and the number of beam failures.

4. The first network entity (100) of any of claims 1 to 3, wherein at least one of the set of active time periods of the QoS level and the average active time period of the QoS level is associated with at least one of cell and network slice selection assistance information, NSSAI.

5. The first network entity (100) of claim 4, wherein the derived active time period of the QoS level is associated with at least one of the cell and the NSSAI.

6. A second network entity (300) configured to:

receiving a first message (510) from a first network entity (100), wherein the first message (510) indicates at least one of a set of active time periods for requesting a QoS level and an average active time period for the QoS level, wherein an active time period is a time period for which a QoS flow is active at the QoS level;

acquiring at least one of an activity time period set of the QoS level and an average activity time period of the QoS level;

transmitting a second message (520) to the first network entity (100), wherein the second message (520) indicates at least one of the set of active time periods of the QoS level and the average active time period of the QoS level.

7. The second network entity (300) of claim 6, wherein obtaining the set of active time periods for the QoS level comprises:

an activity time period of at least one QoS flow active at the QoS level is measured.

8. The second network entity (300) of claim 7, wherein obtaining the set of active time periods for the QoS level comprises:

an activity time period of at least one QoS flow active at the QoS level is measured based on at least one of a timer and a time window.

9. The second network entity (300) of any of claims 6-8, wherein obtaining the set of active time periods for the QoS level comprises:

sending a third message (530) to a third network entity (500), wherein the third message (530) indicates a set of active time periods for which the QoS level is requested;

receiving a fourth message (540) from the third network entity (500), wherein the fourth message (540) indicates a set of active time periods for the QoS level.

10. The second network entity (300) of any of claims 6-9, wherein obtaining the average active time period for the QoS level comprises:

calculating an average active time period for the QoS level based on the set of active time periods for the QoS level and according to at least one of a QoS flow number, a radio link failure number, a switch failure number, and a beam failure number.

11. The second network entity (300) according to any of claims 6-10, wherein at least one of the set of active time periods of the QoS level and the average active time period of the QoS level is associated with at least one of a cell and a NSSAI.

12. A third network entity (500) configured to:

receiving a third message (530) from a second network entity (300), wherein the third message (530) indicates a set of active time periods requesting a QoS level, wherein an active time period is a time period during which a QoS flow is active at the QoS level;

acquiring an active time period set of the QoS level;

sending a fourth message (540) to the second network entity (300), wherein the fourth message (540) indicates the acquired set of active time periods for the QoS level.

13. The third network entity (500) of claim 12 wherein obtaining the set of active time periods for the QoS level comprises:

an activity time period of at least one QoS flow active at the QoS level is measured.

14. The third network entity (500) of claim 13, wherein obtaining the set of active time periods for the QoS level comprises:

an activity time period of at least one QoS flow active at the QoS level is measured based on at least one of a timer and a time window.

15. The third network entity (500) of any of claims 12 or 14, wherein the set of active time periods of the QoS level is associated with at least one of a cell and an NSSAI.

Images